From 0255757831443c45e48828e76f597c555cc7b0bd Mon Sep 17 00:00:00 2001
From: Aleksey Kravchenko <al.kravchenko@yadro.com>
Date: Fri, 10 Jan 2025 19:00:25 +0300
Subject: [PATCH] [#1] Add frostfs backend docs

Signed-off-by: Aleksey Kravchenko <al.kravchenko@yadro.com>
---
 MANUAL.html                     | 37880 ++++++++++++++++++++++--------
 MANUAL.md                       |   485 +-
 MANUAL.txt                      |   851 +-
 bin/make_manual.py              |     1 +
 docs/content/_index.md          |     1 +
 docs/content/commands/rclone.md |    17 +-
 docs/content/flags.md           |    17 +-
 docs/content/frostfs.md         |   466 +
 rclone.1                        | 14092 +++++------
 9 files changed, 37339 insertions(+), 16471 deletions(-)
 create mode 100644 docs/content/frostfs.md

diff --git a/MANUAL.html b/MANUAL.html
index b29676b37..3c480012e 100644
--- a/MANUAL.html
+++ b/MANUAL.html
@@ -7,15 +7,167 @@
   <meta name="author" content="Nick Craig-Wood" />
   <title>rclone(1) User Manual</title>
   <style>
+    html {
+      color: #1a1a1a;
+      background-color: #fdfdfd;
+    }
+    body {
+      margin: 0 auto;
+      max-width: 36em;
+      padding-left: 50px;
+      padding-right: 50px;
+      padding-top: 50px;
+      padding-bottom: 50px;
+      hyphens: auto;
+      overflow-wrap: break-word;
+      text-rendering: optimizeLegibility;
+      font-kerning: normal;
+    }
+    @media (max-width: 600px) {
+      body {
+        font-size: 0.9em;
+        padding: 12px;
+      }
+      h1 {
+        font-size: 1.8em;
+      }
+    }
+    @media print {
+      html {
+        background-color: white;
+      }
+      body {
+        background-color: transparent;
+        color: black;
+        font-size: 12pt;
+      }
+      p, h2, h3 {
+        orphans: 3;
+        widows: 3;
+      }
+      h2, h3, h4 {
+        page-break-after: avoid;
+      }
+    }
+    p {
+      margin: 1em 0;
+    }
+    a {
+      color: #1a1a1a;
+    }
+    a:visited {
+      color: #1a1a1a;
+    }
+    img {
+      max-width: 100%;
+    }
+    h1, h2, h3, h4, h5, h6 {
+      margin-top: 1.4em;
+    }
+    h5, h6 {
+      font-size: 1em;
+      font-style: italic;
+    }
+    h6 {
+      font-weight: normal;
+    }
+    ol, ul {
+      padding-left: 1.7em;
+      margin-top: 1em;
+    }
+    li > ol, li > ul {
+      margin-top: 0;
+    }
+    blockquote {
+      margin: 1em 0 1em 1.7em;
+      padding-left: 1em;
+      border-left: 2px solid #e6e6e6;
+      color: #606060;
+    }
+    code {
+      font-family: Menlo, Monaco, Consolas, 'Lucida Console', monospace;
+      font-size: 85%;
+      margin: 0;
+      hyphens: manual;
+    }
+    pre {
+      margin: 1em 0;
+      overflow: auto;
+    }
+    pre code {
+      padding: 0;
+      overflow: visible;
+      overflow-wrap: normal;
+    }
+    .sourceCode {
+     background-color: transparent;
+     overflow: visible;
+    }
+    hr {
+      background-color: #1a1a1a;
+      border: none;
+      height: 1px;
+      margin: 1em 0;
+    }
+    table {
+      margin: 1em 0;
+      border-collapse: collapse;
+      width: 100%;
+      overflow-x: auto;
+      display: block;
+      font-variant-numeric: lining-nums tabular-nums;
+    }
+    table caption {
+      margin-bottom: 0.75em;
+    }
+    tbody {
+      margin-top: 0.5em;
+      border-top: 1px solid #1a1a1a;
+      border-bottom: 1px solid #1a1a1a;
+    }
+    th {
+      border-top: 1px solid #1a1a1a;
+      padding: 0.25em 0.5em 0.25em 0.5em;
+    }
+    td {
+      padding: 0.125em 0.5em 0.25em 0.5em;
+    }
+    header {
+      margin-bottom: 4em;
+      text-align: center;
+    }
+    #TOC li {
+      list-style: none;
+    }
+    #TOC ul {
+      padding-left: 1.3em;
+    }
+    #TOC > ul {
+      padding-left: 0;
+    }
+    #TOC a:not(:hover) {
+      text-decoration: none;
+    }
     code{white-space: pre-wrap;}
     span.smallcaps{font-variant: small-caps;}
-    span.underline{text-decoration: underline;}
-    div.column{display: inline-block; vertical-align: top; width: 50%;}
+    div.columns{display: flex; gap: min(4vw, 1.5em);}
+    div.column{flex: auto; overflow-x: auto;}
     div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
-    ul.task-list{list-style: none;}
+    /* The extra [class] is a hack that increases specificity enough to
+       override a similar rule in reveal.js */
+    ul.task-list[class]{list-style: none;}
+    ul.task-list li input[type="checkbox"] {
+      font-size: inherit;
+      width: 0.8em;
+      margin: 0 0.8em 0.2em -1.6em;
+      vertical-align: middle;
+    }
+    .display.math{display: block; text-align: center; margin: 0.5rem auto;}
+    /* CSS for syntax highlighting */
     pre > code.sourceCode { white-space: pre; position: relative; }
-    pre > code.sourceCode > span { display: inline-block; line-height: 1.25; }
+    pre > code.sourceCode > span { line-height: 1.25; }
     pre > code.sourceCode > span:empty { height: 1.2em; }
+    .sourceCode { overflow: visible; }
     code.sourceCode > span { color: inherit; text-decoration: inherit; }
     div.sourceCode { margin: 1em 0; }
     pre.sourceCode { margin: 0; }
@@ -50,7 +202,7 @@
     code span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */
     code span.at { color: #7d9029; } /* Attribute */
     code span.bn { color: #40a070; } /* BaseN */
-    code span.bu { } /* BuiltIn */
+    code span.bu { color: #008000; } /* BuiltIn */
     code span.cf { color: #007020; font-weight: bold; } /* ControlFlow */
     code span.ch { color: #4070a0; } /* Char */
     code span.cn { color: #880000; } /* Constant */
@@ -63,7 +215,7 @@
     code span.ex { } /* Extension */
     code span.fl { color: #40a070; } /* Float */
     code span.fu { color: #06287e; } /* Function */
-    code span.im { } /* Import */
+    code span.im { color: #008000; font-weight: bold; } /* Import */
     code span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */
     code span.kw { color: #007020; font-weight: bold; } /* Keyword */
     code span.op { color: #666666; } /* Operator */
@@ -81,9 +233,10 @@
 <header id="title-block-header">
 <h1 class="title">rclone(1) User Manual</h1>
 <p class="author">Nick Craig-Wood</p>
-<p class="date">Nov 15, 2024</p>
+<p class="date">Jan 10, 2025</p>
 </header>
-<h1 id="rclone-syncs-your-files-to-cloud-storage">Rclone syncs your files to cloud storage</h1>
+<h1 id="rclone-syncs-your-files-to-cloud-storage">Rclone syncs your
+files to cloud storage</h1>
 <p><img width="50%" src="https://rclone.org/img/logo_on_light__horizontal_color.svg" alt="rclone logo" style="float:right; padding: 5px;" ></p>
 <ul>
 <li><a href="#about">About rclone</a></li>
@@ -95,15 +248,51 @@
 <li><a href="https://rclone.org/donate/">Donate.</a></li>
 </ul>
 <h2 id="about">About rclone</h2>
-<p>Rclone is a command-line program to manage files on cloud storage. It is a feature-rich alternative to cloud vendors' web storage interfaces. <a href="#providers">Over 70 cloud storage products</a> support rclone including S3 object stores, business &amp; consumer file storage services, as well as standard transfer protocols.</p>
-<p>Rclone has powerful cloud equivalents to the unix commands rsync, cp, mv, mount, ls, ncdu, tree, rm, and cat. Rclone's familiar syntax includes shell pipeline support, and <code>--dry-run</code> protection. It is used at the command line, in scripts or via its <a href="/rc">API</a>.</p>
-<p>Users call rclone <em>"The Swiss army knife of cloud storage"</em>, and <em>"Technology indistinguishable from magic"</em>.</p>
-<p>Rclone really looks after your data. It preserves timestamps and verifies checksums at all times. Transfers over limited bandwidth; intermittent connections, or subject to quota can be restarted, from the last good file transferred. You can <a href="https://rclone.org/commands/rclone_check/">check</a> the integrity of your files. Where possible, rclone employs server-side transfers to minimise local bandwidth use and transfers from one provider to another without using local disk.</p>
-<p>Virtual backends wrap local and cloud file systems to apply <a href="https://rclone.org/crypt/">encryption</a>, <a href="https://rclone.org/compress/">compression</a>, <a href="https://rclone.org/chunker/">chunking</a>, <a href="https://rclone.org/hasher/">hashing</a> and <a href="https://rclone.org/union/">joining</a>.</p>
-<p>Rclone <a href="https://rclone.org/commands/rclone_mount/">mounts</a> any local, cloud or virtual filesystem as a disk on Windows, macOS, linux and FreeBSD, and also serves these over <a href="https://rclone.org/commands/rclone_serve_sftp/">SFTP</a>, <a href="https://rclone.org/commands/rclone_serve_http/">HTTP</a>, <a href="https://rclone.org/commands/rclone_serve_webdav/">WebDAV</a>, <a href="https://rclone.org/commands/rclone_serve_ftp/">FTP</a> and <a href="https://rclone.org/commands/rclone_serve_dlna/">DLNA</a>.</p>
-<p>Rclone is mature, open-source software originally inspired by rsync and written in <a href="https://golang.org">Go</a>. The friendly support community is familiar with varied use cases. Official Ubuntu, Debian, Fedora, Brew and Chocolatey repos. include rclone. For the latest version <a href="https://rclone.org/downloads/">downloading from rclone.org</a> is recommended.</p>
-<p>Rclone is widely used on Linux, Windows and Mac. Third-party developers create innovative backup, restore, GUI and business process solutions using the rclone command line or API.</p>
-<p>Rclone does the heavy lifting of communicating with cloud storage.</p>
+<p>Rclone is a command-line program to manage files on cloud storage. It
+is a feature-rich alternative to cloud vendors' web storage interfaces.
+<a href="#providers">Over 70 cloud storage products</a> support rclone
+including S3 object stores, business &amp; consumer file storage
+services, as well as standard transfer protocols.</p>
+<p>Rclone has powerful cloud equivalents to the unix commands rsync, cp,
+mv, mount, ls, ncdu, tree, rm, and cat. Rclone's familiar syntax
+includes shell pipeline support, and <code>--dry-run</code> protection.
+It is used at the command line, in scripts or via its <a
+href="/rc">API</a>.</p>
+<p>Users call rclone <em>"The Swiss army knife of cloud storage"</em>,
+and <em>"Technology indistinguishable from magic"</em>.</p>
+<p>Rclone really looks after your data. It preserves timestamps and
+verifies checksums at all times. Transfers over limited bandwidth;
+intermittent connections, or subject to quota can be restarted, from the
+last good file transferred. You can <a
+href="https://rclone.org/commands/rclone_check/">check</a> the integrity
+of your files. Where possible, rclone employs server-side transfers to
+minimise local bandwidth use and transfers from one provider to another
+without using local disk.</p>
+<p>Virtual backends wrap local and cloud file systems to apply <a
+href="https://rclone.org/crypt/">encryption</a>, <a
+href="https://rclone.org/compress/">compression</a>, <a
+href="https://rclone.org/chunker/">chunking</a>, <a
+href="https://rclone.org/hasher/">hashing</a> and <a
+href="https://rclone.org/union/">joining</a>.</p>
+<p>Rclone <a href="https://rclone.org/commands/rclone_mount/">mounts</a>
+any local, cloud or virtual filesystem as a disk on Windows, macOS,
+linux and FreeBSD, and also serves these over <a
+href="https://rclone.org/commands/rclone_serve_sftp/">SFTP</a>, <a
+href="https://rclone.org/commands/rclone_serve_http/">HTTP</a>, <a
+href="https://rclone.org/commands/rclone_serve_webdav/">WebDAV</a>, <a
+href="https://rclone.org/commands/rclone_serve_ftp/">FTP</a> and <a
+href="https://rclone.org/commands/rclone_serve_dlna/">DLNA</a>.</p>
+<p>Rclone is mature, open-source software originally inspired by rsync
+and written in <a href="https://golang.org">Go</a>. The friendly support
+community is familiar with varied use cases. Official Ubuntu, Debian,
+Fedora, Brew and Chocolatey repos. include rclone. For the latest
+version <a href="https://rclone.org/downloads/">downloading from
+rclone.org</a> is recommended.</p>
+<p>Rclone is widely used on Linux, Windows and Mac. Third-party
+developers create innovative backup, restore, GUI and business process
+solutions using the rclone command line or API.</p>
+<p>Rclone does the heavy lifting of communicating with cloud
+storage.</p>
 <h2 id="what">What can rclone do for you?</h2>
 <p>Rclone helps you:</p>
 <ul>
@@ -111,9 +300,15 @@
 <li>Restore (and decrypt) files from cloud storage</li>
 <li>Mirror cloud data to other cloud services or locally</li>
 <li>Migrate data to the cloud, or between cloud storage vendors</li>
-<li>Mount multiple, encrypted, cached or diverse cloud storage as a disk</li>
-<li>Analyse and account for data held on cloud storage using <a href="https://rclone.org/commands/rclone_lsf/">lsf</a>, <a href="https://rclone.org/commands/rclone_lsjson/">ljson</a>, <a href="https://rclone.org/commands/rclone_size/">size</a>, <a href="https://rclone.org/commands/rclone_ncdu/">ncdu</a></li>
-<li><a href="https://rclone.org/union/">Union</a> file systems together to present multiple local and/or cloud file systems as one</li>
+<li>Mount multiple, encrypted, cached or diverse cloud storage as a
+disk</li>
+<li>Analyse and account for data held on cloud storage using <a
+href="https://rclone.org/commands/rclone_lsf/">lsf</a>, <a
+href="https://rclone.org/commands/rclone_lsjson/">ljson</a>, <a
+href="https://rclone.org/commands/rclone_size/">size</a>, <a
+href="https://rclone.org/commands/rclone_ncdu/">ncdu</a></li>
+<li><a href="https://rclone.org/union/">Union</a> file systems together
+to present multiple local and/or cloud file systems as one</li>
 </ul>
 <h2 id="features">Features</h2>
 <ul>
@@ -125,17 +320,31 @@
 <li>Can be to and from network, e.g. two different cloud providers</li>
 <li>Can use multi-threaded downloads to local disk</li>
 </ul></li>
-<li><a href="https://rclone.org/commands/rclone_copy/">Copy</a> new or changed files to cloud storage</li>
-<li><a href="https://rclone.org/commands/rclone_sync/">Sync</a> (one way) to make a directory identical</li>
-<li><a href="https://rclone.org/bisync/">Bisync</a> (two way) to keep two directories in sync bidirectionally</li>
-<li><a href="https://rclone.org/commands/rclone_move/">Move</a> files to cloud storage deleting the local after verification</li>
-<li><a href="https://rclone.org/commands/rclone_check/">Check</a> hashes and for missing/extra files</li>
-<li><a href="https://rclone.org/commands/rclone_mount/">Mount</a> your cloud storage as a network disk</li>
-<li><a href="https://rclone.org/commands/rclone_serve/">Serve</a> local or remote files over <a href="https://rclone.org/commands/rclone_serve_http/">HTTP</a>/<a href="https://rclone.org/commands/rclone_serve_webdav/">WebDav</a>/<a href="https://rclone.org/commands/rclone_serve_ftp/">FTP</a>/<a href="https://rclone.org/commands/rclone_serve_sftp/">SFTP</a>/<a href="https://rclone.org/commands/rclone_serve_dlna/">DLNA</a></li>
-<li>Experimental <a href="https://rclone.org/gui/">Web based GUI</a></li>
+<li><a href="https://rclone.org/commands/rclone_copy/">Copy</a> new or
+changed files to cloud storage</li>
+<li><a href="https://rclone.org/commands/rclone_sync/">Sync</a> (one
+way) to make a directory identical</li>
+<li><a href="https://rclone.org/bisync/">Bisync</a> (two way) to keep
+two directories in sync bidirectionally</li>
+<li><a href="https://rclone.org/commands/rclone_move/">Move</a> files to
+cloud storage deleting the local after verification</li>
+<li><a href="https://rclone.org/commands/rclone_check/">Check</a> hashes
+and for missing/extra files</li>
+<li><a href="https://rclone.org/commands/rclone_mount/">Mount</a> your
+cloud storage as a network disk</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">Serve</a> local
+or remote files over <a
+href="https://rclone.org/commands/rclone_serve_http/">HTTP</a>/<a
+href="https://rclone.org/commands/rclone_serve_webdav/">WebDav</a>/<a
+href="https://rclone.org/commands/rclone_serve_ftp/">FTP</a>/<a
+href="https://rclone.org/commands/rclone_serve_sftp/">SFTP</a>/<a
+href="https://rclone.org/commands/rclone_serve_dlna/">DLNA</a></li>
+<li>Experimental <a href="https://rclone.org/gui/">Web based
+GUI</a></li>
 </ul>
 <h2 id="providers">Supported providers</h2>
-<p>(There are many others, built on standard protocols such as WebDAV or S3, that work out of the box.)</p>
+<p>(There are many others, built on standard protocols such as WebDAV or
+S3, that work out of the box.)</p>
 <ul>
 <li>1Fichier</li>
 <li>Akamai Netstorage</li>
@@ -155,6 +364,7 @@
 <li>Enterprise File Fabric</li>
 <li>Fastmail Files</li>
 <li>Files.com</li>
+<li>FrostFS</li>
 <li>FTP</li>
 <li>Gofile</li>
 <li>Google Cloud Storage</li>
@@ -239,7 +449,8 @@
 <h2 id="links">Links</h2>
 <ul>
 <li><a href="https://rclone.org/">Home page</a></li>
-<li><a href="https://github.com/rclone/rclone">GitHub project page for source and bug tracker</a></li>
+<li><a href="https://github.com/rclone/rclone">GitHub project page for
+source and bug tracker</a></li>
 <li><a href="https://forum.rclone.org">Rclone Forum</a></li>
 <li><a href="https://rclone.org/downloads/">Downloads</a></li>
 </ul>
@@ -247,21 +458,32 @@
 <p>Rclone is a Go program and comes as a single binary file.</p>
 <h2 id="quickstart">Quickstart</h2>
 <ul>
-<li><a href="https://rclone.org/downloads/">Download</a> the relevant binary.</li>
-<li>Extract the <code>rclone</code> executable, <code>rclone.exe</code> on Windows, from the archive.</li>
-<li>Run <code>rclone config</code> to setup. See <a href="https://rclone.org/docs/">rclone config docs</a> for more details.</li>
-<li>Optionally configure <a href="#autostart">automatic execution</a>.</li>
+<li><a href="https://rclone.org/downloads/">Download</a> the relevant
+binary.</li>
+<li>Extract the <code>rclone</code> executable, <code>rclone.exe</code>
+on Windows, from the archive.</li>
+<li>Run <code>rclone config</code> to setup. See <a
+href="https://rclone.org/docs/">rclone config docs</a> for more
+details.</li>
+<li>Optionally configure <a href="#autostart">automatic
+execution</a>.</li>
 </ul>
 <p>See below for some expanded Linux / macOS / Windows instructions.</p>
-<p>See the <a href="https://rclone.org/docs/">usage</a> docs for how to use rclone, or run <code>rclone -h</code>.</p>
-<p>Already installed rclone can be easily updated to the latest version using the <a href="https://rclone.org/commands/rclone_selfupdate/">rclone selfupdate</a> command.</p>
-<p>See <a href="https://rclone.org/release_signing/">the release signing docs</a> for how to verify signatures on the release.</p>
+<p>See the <a href="https://rclone.org/docs/">usage</a> docs for how to
+use rclone, or run <code>rclone -h</code>.</p>
+<p>Already installed rclone can be easily updated to the latest version
+using the <a
+href="https://rclone.org/commands/rclone_selfupdate/">rclone
+selfupdate</a> command.</p>
+<p>See <a href="https://rclone.org/release_signing/">the release signing
+docs</a> for how to verify signatures on the release.</p>
 <h2 id="script-installation">Script installation</h2>
 <p>To install rclone on Linux/macOS/BSD systems, run:</p>
 <pre><code>sudo -v ; curl https://rclone.org/install.sh | sudo bash</code></pre>
 <p>For beta installation, run:</p>
 <pre><code>sudo -v ; curl https://rclone.org/install.sh | sudo bash -s beta</code></pre>
-<p>Note that this script checks the version of rclone installed first and won't re-download if not needed.</p>
+<p>Note that this script checks the version of rclone installed first
+and won't re-download if not needed.</p>
 <h2 id="linux">Linux installation</h2>
 <h3 id="linux-precompiled">Precompiled binary</h3>
 <p>Fetch and unpack</p>
@@ -276,84 +498,154 @@ sudo chmod 755 /usr/bin/rclone</code></pre>
 <pre><code>sudo mkdir -p /usr/local/share/man/man1
 sudo cp rclone.1 /usr/local/share/man/man1/
 sudo mandb</code></pre>
-<p>Run <code>rclone config</code> to setup. See <a href="https://rclone.org/docs/">rclone config docs</a> for more details.</p>
+<p>Run <code>rclone config</code> to setup. See <a
+href="https://rclone.org/docs/">rclone config docs</a> for more
+details.</p>
 <pre><code>rclone config</code></pre>
 <h2 id="macos">macOS installation</h2>
 <h3 id="macos-brew">Installation with brew</h3>
 <pre><code>brew install rclone</code></pre>
-<p>NOTE: This version of rclone will not support <code>mount</code> any more (see <a href="https://github.com/rclone/rclone/issues/5373">#5373</a>). If mounting is wanted on macOS, either install a precompiled binary or enable the relevant option when <a href="#source">installing from source</a>.</p>
-<p>Note that this is a third party installer not controlled by the rclone developers so it may be out of date. Its current version is as below.</p>
-<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/version-for-repo/homebrew/rclone.svg" alt="Homebrew package" /></a></p>
+<p>NOTE: This version of rclone will not support <code>mount</code> any
+more (see <a
+href="https://github.com/rclone/rclone/issues/5373">#5373</a>). If
+mounting is wanted on macOS, either install a precompiled binary or
+enable the relevant option when <a href="#source">installing from
+source</a>.</p>
+<p>Note that this is a third party installer not controlled by the
+rclone developers so it may be out of date. Its current version is as
+below.</p>
+<p><a href="https://repology.org/project/rclone/versions"><img
+src="https://repology.org/badge/version-for-repo/homebrew/rclone.svg"
+alt="Homebrew package" /></a></p>
 <h3 id="macos-macports">Installation with MacPorts</h3>
-<p>On macOS, rclone can also be installed via <a href="https://www.macports.org">MacPorts</a>:</p>
+<p>On macOS, rclone can also be installed via <a
+href="https://www.macports.org">MacPorts</a>:</p>
 <pre><code>sudo port install rclone</code></pre>
-<p>Note that this is a third party installer not controlled by the rclone developers so it may be out of date. Its current version is as below.</p>
-<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/version-for-repo/macports/rclone.svg" alt="MacPorts port" /></a></p>
-<p>More information <a href="https://ports.macports.org/port/rclone/">here</a>.</p>
+<p>Note that this is a third party installer not controlled by the
+rclone developers so it may be out of date. Its current version is as
+below.</p>
+<p><a href="https://repology.org/project/rclone/versions"><img
+src="https://repology.org/badge/version-for-repo/macports/rclone.svg"
+alt="MacPorts port" /></a></p>
+<p>More information <a
+href="https://ports.macports.org/port/rclone/">here</a>.</p>
 <h3 id="macos-precompiled">Precompiled binary, using curl</h3>
-<p>To avoid problems with macOS gatekeeper enforcing the binary to be signed and notarized it is enough to download with <code>curl</code>.</p>
+<p>To avoid problems with macOS gatekeeper enforcing the binary to be
+signed and notarized it is enough to download with
+<code>curl</code>.</p>
 <p>Download the latest version of rclone.</p>
 <pre><code>cd &amp;&amp; curl -O https://downloads.rclone.org/rclone-current-osx-amd64.zip</code></pre>
 <p>Unzip the download and cd to the extracted folder.</p>
 <pre><code>unzip -a rclone-current-osx-amd64.zip &amp;&amp; cd rclone-*-osx-amd64</code></pre>
-<p>Move rclone to your $PATH. You will be prompted for your password.</p>
+<p>Move rclone to your $PATH. You will be prompted for your
+password.</p>
 <pre><code>sudo mkdir -p /usr/local/bin
 sudo mv rclone /usr/local/bin/</code></pre>
-<p>(the <code>mkdir</code> command is safe to run, even if the directory already exists).</p>
+<p>(the <code>mkdir</code> command is safe to run, even if the directory
+already exists).</p>
 <p>Remove the leftover files.</p>
 <pre><code>cd .. &amp;&amp; rm -rf rclone-*-osx-amd64 rclone-current-osx-amd64.zip</code></pre>
-<p>Run <code>rclone config</code> to setup. See <a href="https://rclone.org/docs/">rclone config docs</a> for more details.</p>
+<p>Run <code>rclone config</code> to setup. See <a
+href="https://rclone.org/docs/">rclone config docs</a> for more
+details.</p>
 <pre><code>rclone config</code></pre>
-<h3 id="macos-precompiled-web">Precompiled binary, using a web browser</h3>
-<p>When downloading a binary with a web browser, the browser will set the macOS gatekeeper quarantine attribute. Starting from Catalina, when attempting to run <code>rclone</code>, a pop-up will appear saying:</p>
+<h3 id="macos-precompiled-web">Precompiled binary, using a web
+browser</h3>
+<p>When downloading a binary with a web browser, the browser will set
+the macOS gatekeeper quarantine attribute. Starting from Catalina, when
+attempting to run <code>rclone</code>, a pop-up will appear saying:</p>
 <pre><code>&quot;rclone&quot; cannot be opened because the developer cannot be verified.
 macOS cannot verify that this app is free from malware.</code></pre>
 <p>The simplest fix is to run</p>
 <pre><code>xattr -d com.apple.quarantine rclone</code></pre>
 <h2 id="windows">Windows installation</h2>
 <h3 id="windows-precompiled">Precompiled binary</h3>
-<p>Fetch the correct binary for your processor type by clicking on these links. If not sure, use the first link.</p>
+<p>Fetch the correct binary for your processor type by clicking on these
+links. If not sure, use the first link.</p>
 <ul>
-<li><a href="https://downloads.rclone.org/rclone-current-windows-amd64.zip">Intel/AMD - 64 Bit</a></li>
-<li><a href="https://downloads.rclone.org/rclone-current-windows-386.zip">Intel/AMD - 32 Bit</a></li>
-<li><a href="https://downloads.rclone.org/rclone-current-windows-arm64.zip">ARM - 64 Bit</a></li>
+<li><a
+href="https://downloads.rclone.org/rclone-current-windows-amd64.zip">Intel/AMD
+- 64 Bit</a></li>
+<li><a
+href="https://downloads.rclone.org/rclone-current-windows-386.zip">Intel/AMD
+- 32 Bit</a></li>
+<li><a
+href="https://downloads.rclone.org/rclone-current-windows-arm64.zip">ARM
+- 64 Bit</a></li>
 </ul>
-<p>Open this file in the Explorer and extract <code>rclone.exe</code>. Rclone is a portable executable so you can place it wherever is convenient.</p>
-<p>Open a CMD window (or powershell) and run the binary. Note that rclone does not launch a GUI by default, it runs in the CMD Window.</p>
+<p>Open this file in the Explorer and extract <code>rclone.exe</code>.
+Rclone is a portable executable so you can place it wherever is
+convenient.</p>
+<p>Open a CMD window (or powershell) and run the binary. Note that
+rclone does not launch a GUI by default, it runs in the CMD Window.</p>
 <ul>
-<li>Run <code>rclone.exe config</code> to setup. See <a href="https://rclone.org/docs/">rclone config docs</a> for more details.</li>
-<li>Optionally configure <a href="#autostart">automatic execution</a>.</li>
+<li>Run <code>rclone.exe config</code> to setup. See <a
+href="https://rclone.org/docs/">rclone config docs</a> for more
+details.</li>
+<li>Optionally configure <a href="#autostart">automatic
+execution</a>.</li>
 </ul>
-<p>If you are planning to use the <a href="https://rclone.org/commands/rclone_mount/">rclone mount</a> feature then you will need to install the third party utility <a href="https://winfsp.dev/">WinFsp</a> also.</p>
+<p>If you are planning to use the <a
+href="https://rclone.org/commands/rclone_mount/">rclone mount</a>
+feature then you will need to install the third party utility <a
+href="https://winfsp.dev/">WinFsp</a> also.</p>
 <h3 id="windows-chocolatey">Windows package manager (Winget)</h3>
-<p><a href="https://learn.microsoft.com/en-us/windows/package-manager/">Winget</a> comes pre-installed with the latest versions of Windows. If not, update the <a href="https://www.microsoft.com/p/app-installer/9nblggh4nns1">App Installer</a> package from the Microsoft store.</p>
+<p><a
+href="https://learn.microsoft.com/en-us/windows/package-manager/">Winget</a>
+comes pre-installed with the latest versions of Windows. If not, update
+the <a href="https://www.microsoft.com/p/app-installer/9nblggh4nns1">App
+Installer</a> package from the Microsoft store.</p>
 <p>To install rclone</p>
 <pre><code>winget install Rclone.Rclone</code></pre>
 <p>To uninstall rclone</p>
 <pre><code>winget uninstall Rclone.Rclone --force</code></pre>
 <h3 id="windows-chocolatey">Chocolatey package manager</h3>
-<p>Make sure you have <a href="https://chocolatey.org/">Choco</a> installed</p>
+<p>Make sure you have <a href="https://chocolatey.org/">Choco</a>
+installed</p>
 <pre><code>choco search rclone
 choco install rclone</code></pre>
-<p>This will install rclone on your Windows machine. If you are planning to use <a href="https://rclone.org/commands/rclone_mount/">rclone mount</a> then</p>
+<p>This will install rclone on your Windows machine. If you are planning
+to use <a href="https://rclone.org/commands/rclone_mount/">rclone
+mount</a> then</p>
 <pre><code>choco install winfsp</code></pre>
 <p>will install that too.</p>
-<p>Note that this is a third party installer not controlled by the rclone developers so it may be out of date. Its current version is as below.</p>
-<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/version-for-repo/chocolatey/rclone.svg" alt="Chocolatey package" /></a></p>
+<p>Note that this is a third party installer not controlled by the
+rclone developers so it may be out of date. Its current version is as
+below.</p>
+<p><a href="https://repology.org/project/rclone/versions"><img
+src="https://repology.org/badge/version-for-repo/chocolatey/rclone.svg"
+alt="Chocolatey package" /></a></p>
 <h3 id="windows-scoop">Scoop package manager</h3>
-<p>Make sure you have <a href="https://scoop.sh/">Scoop</a> installed</p>
+<p>Make sure you have <a href="https://scoop.sh/">Scoop</a>
+installed</p>
 <pre><code>scoop install rclone</code></pre>
-<p>Note that this is a third party installer not controlled by the rclone developers so it may be out of date. Its current version is as below.</p>
-<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/version-for-repo/scoop/rclone.svg" alt="Scoop package" /></a></p>
+<p>Note that this is a third party installer not controlled by the
+rclone developers so it may be out of date. Its current version is as
+below.</p>
+<p><a href="https://repology.org/project/rclone/versions"><img
+src="https://repology.org/badge/version-for-repo/scoop/rclone.svg"
+alt="Scoop package" /></a></p>
 <h2 id="package-manager">Package manager installation</h2>
-<p>Many Linux, Windows, macOS and other OS distributions package and distribute rclone.</p>
-<p>The distributed versions of rclone are often quite out of date and for this reason we recommend one of the other installation methods if possible.</p>
-<p>You can get an idea of how up to date or not your OS distribution's package is here.</p>
-<p><a href="https://repology.org/project/rclone/versions"><img src="https://repology.org/badge/vertical-allrepos/rclone.svg?columns=3" alt="Packaging status" /></a></p>
+<p>Many Linux, Windows, macOS and other OS distributions package and
+distribute rclone.</p>
+<p>The distributed versions of rclone are often quite out of date and
+for this reason we recommend one of the other installation methods if
+possible.</p>
+<p>You can get an idea of how up to date or not your OS distribution's
+package is here.</p>
+<p><a href="https://repology.org/project/rclone/versions"><img
+src="https://repology.org/badge/vertical-allrepos/rclone.svg?columns=3"
+alt="Packaging status" /></a></p>
 <h2 id="docker">Docker installation</h2>
-<p>The rclone developers maintain a <a href="https://hub.docker.com/r/rclone/rclone">docker image for rclone</a>.</p>
-<p>These images are built as part of the release process based on a minimal Alpine Linux.</p>
-<p>The <code>:latest</code> tag will always point to the latest stable release. You can use the <code>:beta</code> tag to get the latest build from master. You can also use version tags, e.g. <code>:1.49.1</code>, <code>:1.49</code> or <code>:1</code>.</p>
+<p>The rclone developers maintain a <a
+href="https://hub.docker.com/r/rclone/rclone">docker image for
+rclone</a>.</p>
+<p>These images are built as part of the release process based on a
+minimal Alpine Linux.</p>
+<p>The <code>:latest</code> tag will always point to the latest stable
+release. You can use the <code>:beta</code> tag to get the latest build
+from master. You can also use version tags, e.g. <code>:1.49.1</code>,
+<code>:1.49</code> or <code>:1</code>.</p>
 <pre><code>$ docker pull rclone/rclone:latest
 latest: Pulling from rclone/rclone
 Digest: sha256:0e0ced72671989bb837fea8e88578b3fc48371aa45d209663683e24cfdaa0e11
@@ -362,17 +654,39 @@ $ docker run --rm rclone/rclone:latest version
 rclone v1.49.1
 - os/arch: linux/amd64
 - go version: go1.12.9</code></pre>
-<p>There are a few command line options to consider when starting an rclone Docker container from the rclone image.</p>
+<p>There are a few command line options to consider when starting an
+rclone Docker container from the rclone image.</p>
 <ul>
-<li><p>You need to mount the host rclone config dir at <code>/config/rclone</code> into the Docker container. Due to the fact that rclone updates tokens inside its config file, and that the update process involves a file rename, you need to mount the whole host rclone config dir, not just the single host rclone config file.</p></li>
-<li><p>You need to mount a host data dir at <code>/data</code> into the Docker container.</p></li>
-<li><p>By default, the rclone binary inside a Docker container runs with UID=0 (root). As a result, all files created in a run will have UID=0. If your config and data files reside on the host with a non-root UID:GID, you need to pass these on the container start command line.</p></li>
-<li><p>If you want to access the RC interface (either via the API or the Web UI), it is required to set the <code>--rc-addr</code> to <code>:5572</code> in order to connect to it from outside the container. An explanation about why this is necessary is present <a href="https://web.archive.org/web/20200808071950/https://pythonspeed.com/articles/docker-connection-refused/">here</a>.</p>
+<li><p>You need to mount the host rclone config dir at
+<code>/config/rclone</code> into the Docker container. Due to the fact
+that rclone updates tokens inside its config file, and that the update
+process involves a file rename, you need to mount the whole host rclone
+config dir, not just the single host rclone config file.</p></li>
+<li><p>You need to mount a host data dir at <code>/data</code> into the
+Docker container.</p></li>
+<li><p>By default, the rclone binary inside a Docker container runs with
+UID=0 (root). As a result, all files created in a run will have UID=0.
+If your config and data files reside on the host with a non-root
+UID:GID, you need to pass these on the container start command
+line.</p></li>
+<li><p>If you want to access the RC interface (either via the API or the
+Web UI), it is required to set the <code>--rc-addr</code> to
+<code>:5572</code> in order to connect to it from outside the container.
+An explanation about why this is necessary is present <a
+href="https://web.archive.org/web/20200808071950/https://pythonspeed.com/articles/docker-connection-refused/">here</a>.</p>
 <ul>
-<li>NOTE: Users running this container with the docker network set to <code>host</code> should probably set it to listen to localhost only, with <code>127.0.0.1:5572</code> as the value for <code>--rc-addr</code></li>
+<li>NOTE: Users running this container with the docker network set to
+<code>host</code> should probably set it to listen to localhost only,
+with <code>127.0.0.1:5572</code> as the value for
+<code>--rc-addr</code></li>
 </ul></li>
-<li><p>It is possible to use <code>rclone mount</code> inside a userspace Docker container, and expose the resulting fuse mount to the host. The exact <code>docker run</code> options to do that might vary slightly between hosts. See, e.g. the discussion in this <a href="https://github.com/moby/moby/issues/9448">thread</a>.</p>
-<p>You also need to mount the host <code>/etc/passwd</code> and <code>/etc/group</code> for fuse to work inside the container.</p></li>
+<li><p>It is possible to use <code>rclone mount</code> inside a
+userspace Docker container, and expose the resulting fuse mount to the
+host. The exact <code>docker run</code> options to do that might vary
+slightly between hosts. See, e.g. the discussion in this <a
+href="https://github.com/moby/moby/issues/9448">thread</a>.</p>
+<p>You also need to mount the host <code>/etc/passwd</code> and
+<code>/etc/group</code> for fuse to work inside the container.</p></li>
 </ul>
 <p>Here are some commands tested on an Ubuntu 18.04.3 host:</p>
 <pre><code># config on host at ~/.config/rclone/rclone.conf
@@ -405,97 +719,317 @@ docker run --rm \
 ls ~/data/mount
 kill %1</code></pre>
 <h2 id="snap">Snap installation</h2>
-<p><a href="https://snapcraft.io/rclone"><img src="https://snapcraft.io/static/images/badges/en/snap-store-black.svg" alt="Get it from the Snap Store" /></a></p>
-<p>Make sure you have <a href="https://snapcraft.io/docs/installing-snapd">Snapd installed</a></p>
-<div class="sourceCode" id="cb23"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" aria-hidden="true"></a>$ <span class="fu">sudo</span> snap install rclone</span></code></pre></div>
-<p>Due to the strict confinement of Snap, rclone snap cannot access real /home/$USER/.config/rclone directory, default config path is as below.</p>
+<p><a href="https://snapcraft.io/rclone"><img
+src="https://snapcraft.io/static/images/badges/en/snap-store-black.svg"
+alt="Get it from the Snap Store" /></a></p>
+<p>Make sure you have <a
+href="https://snapcraft.io/docs/installing-snapd">Snapd
+installed</a></p>
+<div class="sourceCode" id="cb23"><pre
+class="sourceCode bash"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" aria-hidden="true" tabindex="-1"></a><span class="ex">$</span> sudo snap install rclone</span></code></pre></div>
+<p>Due to the strict confinement of Snap, rclone snap cannot access real
+/home/$USER/.config/rclone directory, default config path is as
+below.</p>
 <ul>
 <li>Default config directory:
 <ul>
 <li>/home/$USER/snap/rclone/current/.config/rclone</li>
 </ul></li>
 </ul>
-<p>Note: Due to the strict confinement of Snap, <code>rclone mount</code> feature is <code>not</code> supported.</p>
-<p>If mounting is wanted, either install a precompiled binary or enable the relevant option when <a href="#source">installing from source</a>.</p>
-<p>Note that this is controlled by <a href="https://github.com/boukendesho/rclone-snap">community maintainer</a> not the rclone developers so it may be out of date. Its current version is as below.</p>
-<p><a href="https://snapcraft.io/rclone"><img src="https://snapcraft.io/rclone/badge.svg" alt="rclone" /></a></p>
+<p>Note: Due to the strict confinement of Snap,
+<code>rclone mount</code> feature is <code>not</code> supported.</p>
+<p>If mounting is wanted, either install a precompiled binary or enable
+the relevant option when <a href="#source">installing from
+source</a>.</p>
+<p>Note that this is controlled by <a
+href="https://github.com/boukendesho/rclone-snap">community
+maintainer</a> not the rclone developers so it may be out of date. Its
+current version is as below.</p>
+<p><a href="https://snapcraft.io/rclone"><img
+src="https://snapcraft.io/rclone/badge.svg" alt="rclone" /></a></p>
 <h2 id="source">Source installation</h2>
-<p>Make sure you have git and <a href="https://golang.org/">Go</a> installed. Go version 1.18 or newer is required, the latest release is recommended. You can get it from your package manager, or download it from <a href="https://golang.org/dl/">golang.org/dl</a>. Then you can run the following:</p>
+<p>Make sure you have git and <a href="https://golang.org/">Go</a>
+installed. Go version 1.18 or newer is required, the latest release is
+recommended. You can get it from your package manager, or download it
+from <a href="https://golang.org/dl/">golang.org/dl</a>. Then you can
+run the following:</p>
 <pre><code>git clone https://github.com/rclone/rclone.git
 cd rclone
 go build</code></pre>
-<p>This will check out the rclone source in subfolder rclone, which you can later modify and send pull requests with. Then it will build the rclone executable in the same folder. As an initial check you can now run <code>./rclone version</code> (<code>.\rclone version</code> on Windows).</p>
-<p>Note that on macOS and Windows the <a href="https://rclone.org/commands/rclone_mount/">mount</a> command will not be available unless you specify an additional build tag <code>cmount</code>.</p>
+<p>This will check out the rclone source in subfolder rclone, which you
+can later modify and send pull requests with. Then it will build the
+rclone executable in the same folder. As an initial check you can now
+run <code>./rclone version</code> (<code>.\rclone version</code> on
+Windows).</p>
+<p>Note that on macOS and Windows the <a
+href="https://rclone.org/commands/rclone_mount/">mount</a> command will
+not be available unless you specify an additional build tag
+<code>cmount</code>.</p>
 <pre><code>go build -tags cmount</code></pre>
-<p>This assumes you have a GCC compatible C compiler (GCC or Clang) in your PATH, as it uses <a href="https://pkg.go.dev/cmd/cgo">cgo</a>. But on Windows, the <a href="https://github.com/winfsp/cgofuse">cgofuse</a> library that the cmount implementation is based on, also supports building <a href="https://github.com/golang/go/wiki/WindowsDLLs">without cgo</a>, i.e. by setting environment variable CGO_ENABLED to value 0 (static linking). This is how the official Windows release of rclone is being built, starting with version 1.59. It is still possible to build with cgo on Windows as well, by using the MinGW port of GCC, e.g. by installing it in a <a href="https://www.msys2.org">MSYS2</a> distribution (make sure you install it in the classic mingw64 subsystem, the ucrt64 version is not compatible).</p>
-<p>Additionally, to build with mount on Windows, you must install the third party utility <a href="https://winfsp.dev/">WinFsp</a>, with the "Developer" feature selected. If building with cgo, you must also set environment variable CPATH pointing to the fuse include directory within the WinFsp installation (normally <code>C:\Program Files (x86)\WinFsp\inc\fuse</code>).</p>
-<p>You may add arguments <code>-ldflags -s</code> to omit symbol table and debug information, making the executable file smaller, and <code>-trimpath</code> to remove references to local file system paths. The official rclone releases are built with both of these.</p>
+<p>This assumes you have a GCC compatible C compiler (GCC or Clang) in
+your PATH, as it uses <a href="https://pkg.go.dev/cmd/cgo">cgo</a>. But
+on Windows, the <a href="https://github.com/winfsp/cgofuse">cgofuse</a>
+library that the cmount implementation is based on, also supports
+building <a href="https://github.com/golang/go/wiki/WindowsDLLs">without
+cgo</a>, i.e. by setting environment variable CGO_ENABLED to value 0
+(static linking). This is how the official Windows release of rclone is
+being built, starting with version 1.59. It is still possible to build
+with cgo on Windows as well, by using the MinGW port of GCC, e.g. by
+installing it in a <a href="https://www.msys2.org">MSYS2</a>
+distribution (make sure you install it in the classic mingw64 subsystem,
+the ucrt64 version is not compatible).</p>
+<p>Additionally, to build with mount on Windows, you must install the
+third party utility <a href="https://winfsp.dev/">WinFsp</a>, with the
+"Developer" feature selected. If building with cgo, you must also set
+environment variable CPATH pointing to the fuse include directory within
+the WinFsp installation (normally
+<code>C:\Program Files (x86)\WinFsp\inc\fuse</code>).</p>
+<p>You may add arguments <code>-ldflags -s</code> to omit symbol table
+and debug information, making the executable file smaller, and
+<code>-trimpath</code> to remove references to local file system paths.
+The official rclone releases are built with both of these.</p>
 <pre><code>go build -trimpath -ldflags -s -tags cmount</code></pre>
-<p>If you want to customize the version string, as reported by the <code>rclone version</code> command, you can set one of the variables <code>fs.Version</code>, <code>fs.VersionTag</code> (to keep default suffix but customize the number), or <code>fs.VersionSuffix</code> (to keep default number but customize the suffix). This can be done from the build command, by adding to the <code>-ldflags</code> argument value as shown below.</p>
+<p>If you want to customize the version string, as reported by the
+<code>rclone version</code> command, you can set one of the variables
+<code>fs.Version</code>, <code>fs.VersionTag</code> (to keep default
+suffix but customize the number), or <code>fs.VersionSuffix</code> (to
+keep default number but customize the suffix). This can be done from the
+build command, by adding to the <code>-ldflags</code> argument value as
+shown below.</p>
 <pre><code>go build -trimpath -ldflags &quot;-s -X github.com/rclone/rclone/fs.Version=v9.9.9-test&quot; -tags cmount</code></pre>
-<p>On Windows, the official executables also have the version information, as well as a file icon, embedded as binary resources. To get that with your own build you need to run the following command <strong>before</strong> the build command. It generates a Windows resource system object file, with extension .syso, e.g. <code>resource_windows_amd64.syso</code>, that will be automatically picked up by future build commands.</p>
+<p>On Windows, the official executables also have the version
+information, as well as a file icon, embedded as binary resources. To
+get that with your own build you need to run the following command
+<strong>before</strong> the build command. It generates a Windows
+resource system object file, with extension .syso, e.g.
+<code>resource_windows_amd64.syso</code>, that will be automatically
+picked up by future build commands.</p>
 <pre><code>go run bin/resource_windows.go</code></pre>
-<p>The above command will generate a resource file containing version information based on the fs.Version variable in source at the time you run the command, which means if the value of this variable changes you need to re-run the command for it to be reflected in the version information. Also, if you override this version variable in the build command as described above, you need to do that also when generating the resource file, or else it will still use the value from the source.</p>
+<p>The above command will generate a resource file containing version
+information based on the fs.Version variable in source at the time you
+run the command, which means if the value of this variable changes you
+need to re-run the command for it to be reflected in the version
+information. Also, if you override this version variable in the build
+command as described above, you need to do that also when generating the
+resource file, or else it will still use the value from the source.</p>
 <pre><code>go run bin/resource_windows.go -version v9.9.9-test</code></pre>
-<p>Instead of executing the <code>go build</code> command directly, you can run it via the Makefile. The default target changes the version suffix from "-DEV" to "-beta" followed by additional commit details, embeds version information binary resources on Windows, and copies the resulting rclone executable into your GOPATH bin folder (<code>$(go env GOPATH)/bin</code>, which corresponds to <code>~/go/bin/rclone</code> by default).</p>
+<p>Instead of executing the <code>go build</code> command directly, you
+can run it via the Makefile. The default target changes the version
+suffix from "-DEV" to "-beta" followed by additional commit details,
+embeds version information binary resources on Windows, and copies the
+resulting rclone executable into your GOPATH bin folder
+(<code>$(go env GOPATH)/bin</code>, which corresponds to
+<code>~/go/bin/rclone</code> by default).</p>
 <pre><code>make</code></pre>
-<p>To include mount command on macOS and Windows with Makefile build:</p>
+<p>To include mount command on macOS and Windows with Makefile
+build:</p>
 <pre><code>make GOTAGS=cmount</code></pre>
-<p>There are other make targets that can be used for more advanced builds, such as cross-compiling for all supported os/architectures, and packaging results into release artifacts. See <a href="https://github.com/rclone/rclone/blob/master/Makefile">Makefile</a> and <a href="https://github.com/rclone/rclone/blob/master/bin/cross-compile.go">cross-compile.go</a> for details.</p>
-<p>Another alternative method for source installation is to download the source, build and install rclone - all in one operation, as a regular Go package. The source will be stored it in the Go module cache, and the resulting executable will be in your GOPATH bin folder (<code>$(go env GOPATH)/bin</code>, which corresponds to <code>~/go/bin/rclone</code> by default).</p>
+<p>There are other make targets that can be used for more advanced
+builds, such as cross-compiling for all supported os/architectures, and
+packaging results into release artifacts. See <a
+href="https://github.com/rclone/rclone/blob/master/Makefile">Makefile</a>
+and <a
+href="https://github.com/rclone/rclone/blob/master/bin/cross-compile.go">cross-compile.go</a>
+for details.</p>
+<p>Another alternative method for source installation is to download the
+source, build and install rclone - all in one operation, as a regular Go
+package. The source will be stored it in the Go module cache, and the
+resulting executable will be in your GOPATH bin folder
+(<code>$(go env GOPATH)/bin</code>, which corresponds to
+<code>~/go/bin/rclone</code> by default).</p>
 <pre><code>go install github.com/rclone/rclone@latest</code></pre>
-<p>In some situations, rclone executable size might be too big for deployment in very restricted environments when all backends with large SDKs are included. To limit binary size unused backends can be commented out in <code>backends/all/all.go</code> and unused commands in <code>cmd/all/all.go</code> before building with <code>go build</code> or <code>make</code></p>
+<p>In some situations, rclone executable size might be too big for
+deployment in very restricted environments when all backends with large
+SDKs are included. To limit binary size unused backends can be commented
+out in <code>backends/all/all.go</code> and unused commands in
+<code>cmd/all/all.go</code> before building with <code>go build</code>
+or <code>make</code></p>
 <h2 id="ansible">Ansible installation</h2>
-<p>This can be done with <a href="https://github.com/stefangweichinger/ansible-rclone">Stefan Weichinger's ansible role</a>.</p>
+<p>This can be done with <a
+href="https://github.com/stefangweichinger/ansible-rclone">Stefan
+Weichinger's ansible role</a>.</p>
 <p>Instructions</p>
 <ol type="1">
-<li><code>git clone https://github.com/stefangweichinger/ansible-rclone.git</code> into your local roles-directory</li>
+<li><code>git clone https://github.com/stefangweichinger/ansible-rclone.git</code>
+into your local roles-directory</li>
 <li>add the role to the hosts you want rclone installed to:</li>
 </ol>
 <pre><code>    - hosts: rclone-hosts
       roles:
           - rclone</code></pre>
 <h2 id="portable">Portable installation</h2>
-<p>As mentioned <a href="https://rclone.org/install/#quickstart">above</a>, rclone is single executable (<code>rclone</code>, or <code>rclone.exe</code> on Windows) that you can download as a zip archive and extract into a location of your choosing. When executing different commands, it may create files in different locations, such as a configuration file and various temporary files. By default the locations for these are according to your operating system, e.g. configuration file in your user profile directory and temporary files in the standard temporary directory, but you can customize all of them, e.g. to make a completely self-contained, portable installation.</p>
-<p>Run the <a href="https://rclone.org/commands/rclone_config_paths/">config paths</a> command to see the locations that rclone will use.</p>
-<p>To override them set the corresponding options (as command-line arguments, or as <a href="https://rclone.org/docs/#environment-variables">environment variables</a>): - <a href="https://rclone.org/docs/#config-config-file">--config</a> - <a href="https://rclone.org/docs/#cache-dir-dir">--cache-dir</a> - <a href="https://rclone.org/docs/#temp-dir-dir">--temp-dir</a></p>
+<p>As mentioned <a
+href="https://rclone.org/install/#quickstart">above</a>, rclone is
+single executable (<code>rclone</code>, or <code>rclone.exe</code> on
+Windows) that you can download as a zip archive and extract into a
+location of your choosing. When executing different commands, it may
+create files in different locations, such as a configuration file and
+various temporary files. By default the locations for these are
+according to your operating system, e.g. configuration file in your user
+profile directory and temporary files in the standard temporary
+directory, but you can customize all of them, e.g. to make a completely
+self-contained, portable installation.</p>
+<p>Run the <a
+href="https://rclone.org/commands/rclone_config_paths/">config paths</a>
+command to see the locations that rclone will use.</p>
+<p>To override them set the corresponding options (as command-line
+arguments, or as <a
+href="https://rclone.org/docs/#environment-variables">environment
+variables</a>): - <a
+href="https://rclone.org/docs/#config-config-file">--config</a> - <a
+href="https://rclone.org/docs/#cache-dir-dir">--cache-dir</a> - <a
+href="https://rclone.org/docs/#temp-dir-dir">--temp-dir</a></p>
 <h2 id="autostart">Autostart</h2>
-<p>After installing and configuring rclone, as described above, you are ready to use rclone as an interactive command line utility. If your goal is to perform <em>periodic</em> operations, such as a regular <a href="https://rclone.org/commands/rclone_sync/">sync</a>, you will probably want to configure your rclone command in your operating system's scheduler. If you need to expose <em>service</em>-like features, such as <a href="https://rclone.org/rc/">remote control</a>, <a href="https://rclone.org/gui/">GUI</a>, <a href="https://rclone.org/commands/rclone_serve/">serve</a> or <a href="https://rclone.org/commands/rclone_mount/">mount</a>, you will often want an rclone command always running in the background, and configuring it to run in a service infrastructure may be a better option. Below are some alternatives on how to achieve this on different operating systems.</p>
-<p>NOTE: Before setting up autorun it is highly recommended that you have tested your command manually from a Command Prompt first.</p>
+<p>After installing and configuring rclone, as described above, you are
+ready to use rclone as an interactive command line utility. If your goal
+is to perform <em>periodic</em> operations, such as a regular <a
+href="https://rclone.org/commands/rclone_sync/">sync</a>, you will
+probably want to configure your rclone command in your operating
+system's scheduler. If you need to expose <em>service</em>-like
+features, such as <a href="https://rclone.org/rc/">remote control</a>,
+<a href="https://rclone.org/gui/">GUI</a>, <a
+href="https://rclone.org/commands/rclone_serve/">serve</a> or <a
+href="https://rclone.org/commands/rclone_mount/">mount</a>, you will
+often want an rclone command always running in the background, and
+configuring it to run in a service infrastructure may be a better
+option. Below are some alternatives on how to achieve this on different
+operating systems.</p>
+<p>NOTE: Before setting up autorun it is highly recommended that you
+have tested your command manually from a Command Prompt first.</p>
 <h3 id="autostart-on-windows">Autostart on Windows</h3>
-<p>The most relevant alternatives for autostart on Windows are: - Run at user log on using the Startup folder - Run at user log on, at system startup or at schedule using Task Scheduler - Run at system startup using Windows service</p>
+<p>The most relevant alternatives for autostart on Windows are: - Run at
+user log on using the Startup folder - Run at user log on, at system
+startup or at schedule using Task Scheduler - Run at system startup
+using Windows service</p>
 <h4 id="running-in-background">Running in background</h4>
-<p>Rclone is a console application, so if not starting from an existing Command Prompt, e.g. when starting rclone.exe from a shortcut, it will open a Command Prompt window. When configuring rclone to run from task scheduler and windows service you are able to set it to run hidden in background. From rclone version 1.54 you can also make it run hidden from anywhere by adding option <code>--no-console</code> (it may still flash briefly when the program starts). Since rclone normally writes information and any error messages to the console, you must redirect this to a file to be able to see it. Rclone has a built-in option <code>--log-file</code> for that.</p>
+<p>Rclone is a console application, so if not starting from an existing
+Command Prompt, e.g. when starting rclone.exe from a shortcut, it will
+open a Command Prompt window. When configuring rclone to run from task
+scheduler and windows service you are able to set it to run hidden in
+background. From rclone version 1.54 you can also make it run hidden
+from anywhere by adding option <code>--no-console</code> (it may still
+flash briefly when the program starts). Since rclone normally writes
+information and any error messages to the console, you must redirect
+this to a file to be able to see it. Rclone has a built-in option
+<code>--log-file</code> for that.</p>
 <p>Example command to run a sync in background:</p>
 <pre><code>c:\rclone\rclone.exe sync c:\files remote:/files --no-console --log-file c:\rclone\logs\sync_files.txt</code></pre>
 <h4 id="user-account">User account</h4>
-<p>As mentioned in the <a href="https://rclone.org/commands/rclone_mount/">mount</a> documentation, mounted drives created as Administrator are not visible to other accounts, not even the account that was elevated as Administrator. By running the mount command as the built-in <code>SYSTEM</code> user account, it will create drives accessible for everyone on the system. Both scheduled task and Windows service can be used to achieve this.</p>
-<p>NOTE: Remember that when rclone runs as the <code>SYSTEM</code> user, the user profile that it sees will not be yours. This means that if you normally run rclone with configuration file in the default location, to be able to use the same configuration when running as the system user you must explicitly tell rclone where to find it with the <a href="https://rclone.org/docs/#config-config-file"><code>--config</code></a> option, or else it will look in the system users profile path (<code>C:\Windows\System32\config\systemprofile</code>). To test your command manually from a Command Prompt, you can run it with the <a href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a> utility from Microsoft's Sysinternals suite, which takes option <code>-s</code> to execute commands as the <code>SYSTEM</code> user.</p>
+<p>As mentioned in the <a
+href="https://rclone.org/commands/rclone_mount/">mount</a>
+documentation, mounted drives created as Administrator are not visible
+to other accounts, not even the account that was elevated as
+Administrator. By running the mount command as the built-in
+<code>SYSTEM</code> user account, it will create drives accessible for
+everyone on the system. Both scheduled task and Windows service can be
+used to achieve this.</p>
+<p>NOTE: Remember that when rclone runs as the <code>SYSTEM</code> user,
+the user profile that it sees will not be yours. This means that if you
+normally run rclone with configuration file in the default location, to
+be able to use the same configuration when running as the system user
+you must explicitly tell rclone where to find it with the <a
+href="https://rclone.org/docs/#config-config-file"><code>--config</code></a>
+option, or else it will look in the system users profile path
+(<code>C:\Windows\System32\config\systemprofile</code>). To test your
+command manually from a Command Prompt, you can run it with the <a
+href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a>
+utility from Microsoft's Sysinternals suite, which takes option
+<code>-s</code> to execute commands as the <code>SYSTEM</code> user.</p>
 <h4 id="start-from-startup-folder">Start from Startup folder</h4>
-<p>To quickly execute an rclone command you can simply create a standard Windows Explorer shortcut for the complete rclone command you want to run. If you store this shortcut in the special "Startup" start-menu folder, Windows will automatically run it at login. To open this folder in Windows Explorer, enter path <code>%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup</code>, or <code>C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp</code> if you want the command to start for <em>every</em> user that logs in.</p>
-<p>This is the easiest approach to autostarting of rclone, but it offers no functionality to set it to run as different user, or to set conditions or actions on certain events. Setting up a scheduled task as described below will often give you better results.</p>
+<p>To quickly execute an rclone command you can simply create a standard
+Windows Explorer shortcut for the complete rclone command you want to
+run. If you store this shortcut in the special "Startup" start-menu
+folder, Windows will automatically run it at login. To open this folder
+in Windows Explorer, enter path
+<code>%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup</code>, or
+<code>C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp</code>
+if you want the command to start for <em>every</em> user that logs
+in.</p>
+<p>This is the easiest approach to autostarting of rclone, but it offers
+no functionality to set it to run as different user, or to set
+conditions or actions on certain events. Setting up a scheduled task as
+described below will often give you better results.</p>
 <h4 id="start-from-task-scheduler">Start from Task Scheduler</h4>
-<p>Task Scheduler is an administrative tool built into Windows, and it can be used to configure rclone to be started automatically in a highly configurable way, e.g. periodically on a schedule, on user log on, or at system startup. It can run be configured to run as the current user, or for a mount command that needs to be available to all users it can run as the <code>SYSTEM</code> user. For technical information, see https://docs.microsoft.com/windows/win32/taskschd/task-scheduler-start-page.</p>
+<p>Task Scheduler is an administrative tool built into Windows, and it
+can be used to configure rclone to be started automatically in a highly
+configurable way, e.g. periodically on a schedule, on user log on, or at
+system startup. It can run be configured to run as the current user, or
+for a mount command that needs to be available to all users it can run
+as the <code>SYSTEM</code> user. For technical information, see
+https://docs.microsoft.com/windows/win32/taskschd/task-scheduler-start-page.</p>
 <h4 id="run-as-service">Run as service</h4>
-<p>For running rclone at system startup, you can create a Windows service that executes your rclone command, as an alternative to scheduled task configured to run at startup.</p>
-<h5 id="mount-command-built-in-service-integration">Mount command built-in service integration</h5>
-<p>For mount commands, rclone has a built-in Windows service integration via the third-party WinFsp library it uses. Registering as a regular Windows service easy, as you just have to execute the built-in PowerShell command <code>New-Service</code> (requires administrative privileges).</p>
-<p>Example of a PowerShell command that creates a Windows service for mounting some <code>remote:/files</code> as drive letter <code>X:</code>, for <em>all</em> users (service will be running as the local system account):</p>
+<p>For running rclone at system startup, you can create a Windows
+service that executes your rclone command, as an alternative to
+scheduled task configured to run at startup.</p>
+<h5 id="mount-command-built-in-service-integration">Mount command
+built-in service integration</h5>
+<p>For mount commands, rclone has a built-in Windows service integration
+via the third-party WinFsp library it uses. Registering as a regular
+Windows service easy, as you just have to execute the built-in
+PowerShell command <code>New-Service</code> (requires administrative
+privileges).</p>
+<p>Example of a PowerShell command that creates a Windows service for
+mounting some <code>remote:/files</code> as drive letter
+<code>X:</code>, for <em>all</em> users (service will be running as the
+local system account):</p>
 <pre><code>New-Service -Name Rclone -BinaryPathName &#39;c:\rclone\rclone.exe mount remote:/files X: --config c:\rclone\config\rclone.conf --log-file c:\rclone\logs\mount.txt&#39;</code></pre>
-<p>The <a href="https://github.com/billziss-gh/winfsp/wiki/WinFsp-Service-Architecture">WinFsp service infrastructure</a> supports incorporating services for file system implementations, such as rclone, into its own launcher service, as kind of "child services". This has the additional advantage that it also implements a network provider that integrates into Windows standard methods for managing network drives. This is currently not officially supported by Rclone, but with WinFsp version 2019.3 B2 / v1.5B2 or later it should be possible through path rewriting as described <a href="https://github.com/rclone/rclone/issues/3340">here</a>.</p>
-<h5 id="third-party-service-integration">Third-party service integration</h5>
-<p>To Windows service running any rclone command, the excellent third-party utility <a href="http://nssm.cc">NSSM</a>, the "Non-Sucking Service Manager", can be used. It includes some advanced features such as adjusting process priority, defining process environment variables, redirect to file anything written to stdout, and customized response to different exit codes, with a GUI to configure everything from (although it can also be used from command line ).</p>
-<p>There are also several other alternatives. To mention one more, <a href="https://github.com/winsw/winsw">WinSW</a>, "Windows Service Wrapper", is worth checking out. It requires .NET Framework, but it is preinstalled on newer versions of Windows, and it also provides alternative standalone distributions which includes necessary runtime (.NET 5). WinSW is a command-line only utility, where you have to manually create an XML file with service configuration. This may be a drawback for some, but it can also be an advantage as it is easy to back up and reuse the configuration settings, without having go through manual steps in a GUI. One thing to note is that by default it does not restart the service on error, one have to explicit enable this in the configuration file (via the "onfailure" parameter).</p>
+<p>The <a
+href="https://github.com/billziss-gh/winfsp/wiki/WinFsp-Service-Architecture">WinFsp
+service infrastructure</a> supports incorporating services for file
+system implementations, such as rclone, into its own launcher service,
+as kind of "child services". This has the additional advantage that it
+also implements a network provider that integrates into Windows standard
+methods for managing network drives. This is currently not officially
+supported by Rclone, but with WinFsp version 2019.3 B2 / v1.5B2 or later
+it should be possible through path rewriting as described <a
+href="https://github.com/rclone/rclone/issues/3340">here</a>.</p>
+<h5 id="third-party-service-integration">Third-party service
+integration</h5>
+<p>To Windows service running any rclone command, the excellent
+third-party utility <a href="http://nssm.cc">NSSM</a>, the "Non-Sucking
+Service Manager", can be used. It includes some advanced features such
+as adjusting process priority, defining process environment variables,
+redirect to file anything written to stdout, and customized response to
+different exit codes, with a GUI to configure everything from (although
+it can also be used from command line ).</p>
+<p>There are also several other alternatives. To mention one more, <a
+href="https://github.com/winsw/winsw">WinSW</a>, "Windows Service
+Wrapper", is worth checking out. It requires .NET Framework, but it is
+preinstalled on newer versions of Windows, and it also provides
+alternative standalone distributions which includes necessary runtime
+(.NET 5). WinSW is a command-line only utility, where you have to
+manually create an XML file with service configuration. This may be a
+drawback for some, but it can also be an advantage as it is easy to back
+up and reuse the configuration settings, without having go through
+manual steps in a GUI. One thing to note is that by default it does not
+restart the service on error, one have to explicit enable this in the
+configuration file (via the "onfailure" parameter).</p>
 <h3 id="autostart-on-linux">Autostart on Linux</h3>
 <h4 id="start-as-a-service">Start as a service</h4>
-<p>To always run rclone in background, relevant for mount commands etc, you can use systemd to set up rclone as a system or user service. Running as a system service ensures that it is run at startup even if the user it is running as has no active session. Running rclone as a user service ensures that it only starts after the configured user has logged into the system.</p>
+<p>To always run rclone in background, relevant for mount commands etc,
+you can use systemd to set up rclone as a system or user service.
+Running as a system service ensures that it is run at startup even if
+the user it is running as has no active session. Running rclone as a
+user service ensures that it only starts after the configured user has
+logged into the system.</p>
 <h4 id="run-periodically-from-cron">Run periodically from cron</h4>
-<p>To run a periodic command, such as a copy/sync, you can set up a cron job.</p>
+<p>To run a periodic command, such as a copy/sync, you can set up a cron
+job.</p>
 <h1 id="usage">Usage</h1>
-<p>Rclone is a command line program to manage files on cloud storage. After <a href="https://rclone.org/downloads/">download</a> and <a href="/install">install</a>, continue here to learn how to use it: Initial <a href="#configure">configuration</a>, what the <a href="#basic-syntax">basic syntax</a> looks like, describes the various <a href="#subcommands">subcommands</a>, the various <a href="#options">options</a>, and more.</p>
+<p>Rclone is a command line program to manage files on cloud storage.
+After <a href="https://rclone.org/downloads/">download</a> and <a
+href="/install">install</a>, continue here to learn how to use it:
+Initial <a href="#configure">configuration</a>, what the <a
+href="#basic-syntax">basic syntax</a> looks like, describes the various
+<a href="#subcommands">subcommands</a>, the various <a
+href="#options">options</a>, and more.</p>
 <h2 id="configure">Configure</h2>
-<p>First, you'll need to configure rclone. As the object storage systems have quite complicated authentication these are kept in a config file. (See the <a href="#config-config-file"><code>--config</code></a> entry for how to find the config file and choose its location.)</p>
-<p>The easiest way to make the config is to run rclone with the config option:</p>
+<p>First, you'll need to configure rclone. As the object storage systems
+have quite complicated authentication these are kept in a config file.
+(See the <a href="#config-config-file"><code>--config</code></a> entry
+for how to find the config file and choose its location.)</p>
+<p>The easiest way to make the config is to run rclone with the config
+option:</p>
 <pre><code>rclone config</code></pre>
 <p>See the following for detailed instructions for</p>
 <ul>
@@ -505,39 +1039,52 @@ go build</code></pre>
 <li><a href="https://rclone.org/s3/">Amazon S3</a></li>
 <li><a href="https://rclone.org/b2/">Backblaze B2</a></li>
 <li><a href="https://rclone.org/box/">Box</a></li>
-<li><a href="https://rclone.org/chunker/">Chunker</a> - transparently splits large files for other remotes</li>
+<li><a href="https://rclone.org/chunker/">Chunker</a> - transparently
+splits large files for other remotes</li>
 <li><a href="https://rclone.org/sharefile/">Citrix ShareFile</a></li>
 <li><a href="https://rclone.org/compress/">Compress</a></li>
 <li><a href="https://rclone.org/combine/">Combine</a></li>
-<li><a href="https://rclone.org/crypt/">Crypt</a> - to encrypt other remotes</li>
-<li><a href="https://rclone.org/s3/#digitalocean-spaces">DigitalOcean Spaces</a></li>
-<li><a href="https://rclone.org/koofr/#digi-storage">Digi Storage</a></li>
+<li><a href="https://rclone.org/crypt/">Crypt</a> - to encrypt other
+remotes</li>
+<li><a href="https://rclone.org/s3/#digitalocean-spaces">DigitalOcean
+Spaces</a></li>
+<li><a href="https://rclone.org/koofr/#digi-storage">Digi
+Storage</a></li>
 <li><a href="https://rclone.org/dropbox/">Dropbox</a></li>
-<li><a href="https://rclone.org/filefabric/">Enterprise File Fabric</a></li>
+<li><a href="https://rclone.org/filefabric/">Enterprise File
+Fabric</a></li>
 <li><a href="https://rclone.org/filescom/">Files.com</a></li>
 <li><a href="https://rclone.org/ftp/">FTP</a></li>
 <li><a href="https://rclone.org/gofile/">Gofile</a></li>
-<li><a href="https://rclone.org/googlecloudstorage/">Google Cloud Storage</a></li>
+<li><a href="https://rclone.org/googlecloudstorage/">Google Cloud
+Storage</a></li>
 <li><a href="https://rclone.org/drive/">Google Drive</a></li>
 <li><a href="https://rclone.org/googlephotos/">Google Photos</a></li>
-<li><a href="https://rclone.org/hasher/">Hasher</a> - to handle checksums for other remotes</li>
+<li><a href="https://rclone.org/hasher/">Hasher</a> - to handle
+checksums for other remotes</li>
 <li><a href="https://rclone.org/hdfs/">HDFS</a></li>
-<li><a href="https://rclone.org/sftp/#hetzner-storage-box">Hetzner Storage Box</a></li>
+<li><a href="https://rclone.org/sftp/#hetzner-storage-box">Hetzner
+Storage Box</a></li>
 <li><a href="https://rclone.org/hidrive/">HiDrive</a></li>
 <li><a href="https://rclone.org/http/">HTTP</a></li>
-<li><a href="https://rclone.org/internetarchive/">Internet Archive</a></li>
+<li><a href="https://rclone.org/internetarchive/">Internet
+Archive</a></li>
 <li><a href="https://rclone.org/jottacloud/">Jottacloud</a></li>
 <li><a href="https://rclone.org/koofr/">Koofr</a></li>
 <li><a href="https://rclone.org/linkbox/">Linkbox</a></li>
 <li><a href="https://rclone.org/mailru/">Mail.ru Cloud</a></li>
 <li><a href="https://rclone.org/mega/">Mega</a></li>
 <li><a href="https://rclone.org/memory/">Memory</a></li>
-<li><a href="https://rclone.org/azureblob/">Microsoft Azure Blob Storage</a></li>
-<li><a href="https://rclone.org/azurefiles/">Microsoft Azure Files Storage</a></li>
+<li><a href="https://rclone.org/azureblob/">Microsoft Azure Blob
+Storage</a></li>
+<li><a href="https://rclone.org/azurefiles/">Microsoft Azure Files
+Storage</a></li>
 <li><a href="https://rclone.org/onedrive/">Microsoft OneDrive</a></li>
-<li><a href="https://rclone.org/swift/">OpenStack Swift / Rackspace Cloudfiles / Blomp Cloud Storage / Memset Memstore</a></li>
+<li><a href="https://rclone.org/swift/">OpenStack Swift / Rackspace
+Cloudfiles / Blomp Cloud Storage / Memset Memstore</a></li>
 <li><a href="https://rclone.org/opendrive/">OpenDrive</a></li>
-<li><a href="https://rclone.org/oracleobjectstorage/">Oracle Object Storage</a></li>
+<li><a href="https://rclone.org/oracleobjectstorage/">Oracle Object
+Storage</a></li>
 <li><a href="https://rclone.org/pcloud/">Pcloud</a></li>
 <li><a href="https://rclone.org/pikpak/">PikPak</a></li>
 <li><a href="https://rclone.org/pixeldrain/">Pixeldrain</a></li>
@@ -565,13 +1112,31 @@ go build</code></pre>
 <p>Rclone syncs a directory tree from one storage system to another.</p>
 <p>Its syntax is like this</p>
 <pre><code>rclone subcommand [options] &lt;parameters&gt; &lt;parameters...&gt;</code></pre>
-<p>A <code>subcommand</code> is a the rclone operation required, (e.g. <code>sync</code>, <code>copy</code>, <code>ls</code>).</p>
-<p>An <code>option</code> is a single letter flag (e.g. <code>-v</code>) or a group of single letter flags (e.g. <code>-Pv</code>) or a long flag (e.g. <code>--progress</code>). No options are required. Options can come after the <code>subcommand</code> or in between parameters too or on the end, but only global options can be used before the <code>subcommand</code>. Anything after a <code>--</code> option will not be interpreted as an option so if you need to add a parameter which starts with a <code>-</code> then put a <code>--</code> on its own first, eg</p>
+<p>A <code>subcommand</code> is a the rclone operation required, (e.g.
+<code>sync</code>, <code>copy</code>, <code>ls</code>).</p>
+<p>An <code>option</code> is a single letter flag (e.g. <code>-v</code>)
+or a group of single letter flags (e.g. <code>-Pv</code>) or a long flag
+(e.g. <code>--progress</code>). No options are required. Options can
+come after the <code>subcommand</code> or in between parameters too or
+on the end, but only global options can be used before the
+<code>subcommand</code>. Anything after a <code>--</code> option will
+not be interpreted as an option so if you need to add a parameter which
+starts with a <code>-</code> then put a <code>--</code> on its own
+first, eg</p>
 <pre><code>rclone lsf -- -directory-starting-with-dash</code></pre>
-<p>A <code>parameter</code> is usually a file path or <a href="#syntax-of-remote-paths">rclone remote</a>, eg <code>/path/to/file</code> or <code>remote:path/to/file</code> but it can be other things - the <code>subcommand</code> help will tell you what.</p>
-<p>Source and destination paths are specified by the name you gave the storage system in the config file then the sub path, e.g. "drive:myfolder" to look at "myfolder" in Google drive.</p>
-<p>You can define as many storage paths as you like in the config file.</p>
-<p>Please use the <a href="#interactive"><code>--interactive</code>/<code>-i</code></a> flag while learning rclone to avoid accidental data loss.</p>
+<p>A <code>parameter</code> is usually a file path or <a
+href="#syntax-of-remote-paths">rclone remote</a>, eg
+<code>/path/to/file</code> or <code>remote:path/to/file</code> but it
+can be other things - the <code>subcommand</code> help will tell you
+what.</p>
+<p>Source and destination paths are specified by the name you gave the
+storage system in the config file then the sub path, e.g.
+"drive:myfolder" to look at "myfolder" in Google drive.</p>
+<p>You can define as many storage paths as you like in the config
+file.</p>
+<p>Please use the <a
+href="#interactive"><code>--interactive</code>/<code>-i</code></a> flag
+while learning rclone to avoid accidental data loss.</p>
 <h2 id="subcommands">Subcommands</h2>
 <p>rclone uses a system of subcommands. For example</p>
 <pre><code>rclone ls remote:path # lists a remote
@@ -580,38 +1145,79 @@ rclone sync --interactive /local/path remote:path # syncs /local/path to the rem
 <h1 id="rclone-config">rclone config</h1>
 <p>Enter an interactive configuration session.</p>
 <h2 id="synopsis">Synopsis</h2>
-<p>Enter an interactive configuration session where you can setup new remotes and manage existing ones. You may also set or remove a password to protect your configuration.</p>
+<p>Enter an interactive configuration session where you can setup new
+remotes and manage existing ones. You may also set or remove a password
+to protect your configuration.</p>
 <pre><code>rclone config [flags]</code></pre>
 <h2 id="options">Options</h2>
 <pre><code>  -h, --help   help for config</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
-<li><a href="https://rclone.org/commands/rclone_config_create/">rclone config create</a> - Create a new remote with name, type and options.</li>
-<li><a href="https://rclone.org/commands/rclone_config_delete/">rclone config delete</a> - Delete an existing remote.</li>
-<li><a href="https://rclone.org/commands/rclone_config_disconnect/">rclone config disconnect</a> - Disconnects user from remote</li>
-<li><a href="https://rclone.org/commands/rclone_config_dump/">rclone config dump</a> - Dump the config file as JSON.</li>
-<li><a href="https://rclone.org/commands/rclone_config_edit/">rclone config edit</a> - Enter an interactive configuration session.</li>
-<li><a href="https://rclone.org/commands/rclone_config_encryption/">rclone config encryption</a> - set, remove and check the encryption for the config file</li>
-<li><a href="https://rclone.org/commands/rclone_config_file/">rclone config file</a> - Show path of configuration file in use.</li>
-<li><a href="https://rclone.org/commands/rclone_config_password/">rclone config password</a> - Update password in an existing remote.</li>
-<li><a href="https://rclone.org/commands/rclone_config_paths/">rclone config paths</a> - Show paths used for configuration, cache, temp etc.</li>
-<li><a href="https://rclone.org/commands/rclone_config_providers/">rclone config providers</a> - List in JSON format all the providers and options.</li>
-<li><a href="https://rclone.org/commands/rclone_config_reconnect/">rclone config reconnect</a> - Re-authenticates user with remote.</li>
-<li><a href="https://rclone.org/commands/rclone_config_redacted/">rclone config redacted</a> - Print redacted (decrypted) config file, or the redacted config for a single remote.</li>
-<li><a href="https://rclone.org/commands/rclone_config_show/">rclone config show</a> - Print (decrypted) config file, or the config for a single remote.</li>
-<li><a href="https://rclone.org/commands/rclone_config_touch/">rclone config touch</a> - Ensure configuration file exists.</li>
-<li><a href="https://rclone.org/commands/rclone_config_update/">rclone config update</a> - Update options in an existing remote.</li>
-<li><a href="https://rclone.org/commands/rclone_config_userinfo/">rclone config userinfo</a> - Prints info about logged in user of remote.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone_config_create/">rclone
+config create</a> - Create a new remote with name, type and
+options.</li>
+<li><a href="https://rclone.org/commands/rclone_config_delete/">rclone
+config delete</a> - Delete an existing remote.</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_disconnect/">rclone
+config disconnect</a> - Disconnects user from remote</li>
+<li><a href="https://rclone.org/commands/rclone_config_dump/">rclone
+config dump</a> - Dump the config file as JSON.</li>
+<li><a href="https://rclone.org/commands/rclone_config_edit/">rclone
+config edit</a> - Enter an interactive configuration session.</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption/">rclone
+config encryption</a> - set, remove and check the encryption for the
+config file</li>
+<li><a href="https://rclone.org/commands/rclone_config_file/">rclone
+config file</a> - Show path of configuration file in use.</li>
+<li><a href="https://rclone.org/commands/rclone_config_password/">rclone
+config password</a> - Update password in an existing remote.</li>
+<li><a href="https://rclone.org/commands/rclone_config_paths/">rclone
+config paths</a> - Show paths used for configuration, cache, temp
+etc.</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_providers/">rclone
+config providers</a> - List in JSON format all the providers and
+options.</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_reconnect/">rclone
+config reconnect</a> - Re-authenticates user with remote.</li>
+<li><a href="https://rclone.org/commands/rclone_config_redacted/">rclone
+config redacted</a> - Print redacted (decrypted) config file, or the
+redacted config for a single remote.</li>
+<li><a href="https://rclone.org/commands/rclone_config_show/">rclone
+config show</a> - Print (decrypted) config file, or the config for a
+single remote.</li>
+<li><a href="https://rclone.org/commands/rclone_config_touch/">rclone
+config touch</a> - Ensure configuration file exists.</li>
+<li><a href="https://rclone.org/commands/rclone_config_update/">rclone
+config update</a> - Update options in an existing remote.</li>
+<li><a href="https://rclone.org/commands/rclone_config_userinfo/">rclone
+config userinfo</a> - Prints info about logged in user of remote.</li>
 </ul>
 <h1 id="rclone-copy">rclone copy</h1>
 <p>Copy files from source to dest, skipping identical files.</p>
 <h2 id="synopsis-1">Synopsis</h2>
-<p>Copy the source to the destination. Does not transfer files that are identical on source and destination, testing by size and modification time or MD5SUM. Doesn't delete files from the destination. If you want to also delete files from destination, to make it match source, use the <a href="https://rclone.org/commands/rclone_sync/">sync</a> command instead.</p>
-<p>Note that it is always the contents of the directory that is synced, not the directory itself. So when source:path is a directory, it's the contents of source:path that are copied, not the directory name and contents.</p>
-<p>To copy single files, use the <a href="https://rclone.org/commands/rclone_copyto/">copyto</a> command instead.</p>
-<p>If dest:path doesn't exist, it is created and the source:path contents go there.</p>
+<p>Copy the source to the destination. Does not transfer files that are
+identical on source and destination, testing by size and modification
+time or MD5SUM. Doesn't delete files from the destination. If you want
+to also delete files from destination, to make it match source, use the
+<a href="https://rclone.org/commands/rclone_sync/">sync</a> command
+instead.</p>
+<p>Note that it is always the contents of the directory that is synced,
+not the directory itself. So when source:path is a directory, it's the
+contents of source:path that are copied, not the directory name and
+contents.</p>
+<p>To copy single files, use the <a
+href="https://rclone.org/commands/rclone_copyto/">copyto</a> command
+instead.</p>
+<p>If dest:path doesn't exist, it is created and the source:path
+contents go there.</p>
 <p>For example</p>
 <pre><code>rclone copy source:sourcepath dest:destpath</code></pre>
 <p>Let's say there are two files in sourcepath</p>
@@ -623,19 +1229,38 @@ destpath/two.txt</code></pre>
 <p>Not to</p>
 <pre><code>destpath/sourcepath/one.txt
 destpath/sourcepath/two.txt</code></pre>
-<p>If you are familiar with <code>rsync</code>, rclone always works as if you had written a trailing <code>/</code> - meaning "copy the contents of this directory". This applies to all commands and whether you are talking about the source or destination.</p>
-<p>See the <a href="https://rclone.org/docs/#no-traverse">--no-traverse</a> option for controlling whether rclone lists the destination directory or not. Supplying this option when copying a small number of files into a large destination can speed transfers up greatly.</p>
-<p>For example, if you have many files in /path/to/src but only a few of them change every day, you can copy all the files which have changed recently very efficiently like this:</p>
+<p>If you are familiar with <code>rsync</code>, rclone always works as
+if you had written a trailing <code>/</code> - meaning "copy the
+contents of this directory". This applies to all commands and whether
+you are talking about the source or destination.</p>
+<p>See the <a
+href="https://rclone.org/docs/#no-traverse">--no-traverse</a> option for
+controlling whether rclone lists the destination directory or not.
+Supplying this option when copying a small number of files into a large
+destination can speed transfers up greatly.</p>
+<p>For example, if you have many files in /path/to/src but only a few of
+them change every day, you can copy all the files which have changed
+recently very efficiently like this:</p>
 <pre><code>rclone copy --max-age 24h --no-traverse /path/to/src remote:</code></pre>
-<p>Rclone will sync the modification times of files and directories if the backend supports it. If metadata syncing is required then use the <code>--metadata</code> flag.</p>
-<p>Note that the modification time and metadata for the root directory will <strong>not</strong> be synced. See https://github.com/rclone/rclone/issues/7652 for more info.</p>
-<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics.</p>
-<p><strong>Note</strong>: Use the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag to test without copying anything.</p>
+<p>Rclone will sync the modification times of files and directories if
+the backend supports it. If metadata syncing is required then use the
+<code>--metadata</code> flag.</p>
+<p>Note that the modification time and metadata for the root directory
+will <strong>not</strong> be synced. See
+https://github.com/rclone/rclone/issues/7652 for more info.</p>
+<p><strong>Note</strong>: Use the
+<code>-P</code>/<code>--progress</code> flag to view real-time transfer
+statistics.</p>
+<p><strong>Note</strong>: Use the <code>--dry-run</code> or the
+<code>--interactive</code>/<code>-i</code> flag to test without copying
+anything.</p>
 <pre><code>rclone copy source:path dest:path [flags]</code></pre>
 <h2 id="options-1">Options</h2>
 <pre><code>      --create-empty-src-dirs   Create empty source dirs on destination after copy
   -h, --help                    help for copy</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="copy-options">Copy Options</h3>
 <p>Flags for anything which can copy a file</p>
 <pre><code>      --check-first                                 Do all the checks before starting transfers
@@ -705,42 +1330,98 @@ destpath/sourcepath/two.txt</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-1">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-sync">rclone sync</h1>
 <p>Make source and dest identical, modifying destination only.</p>
 <h2 id="synopsis-2">Synopsis</h2>
-<p>Sync the source to the destination, changing the destination only. Doesn't transfer files that are identical on source and destination, testing by size and modification time or MD5SUM. Destination is updated to match source, including deleting files if necessary (except duplicate objects, see below). If you don't want to delete files from destination, use the <a href="https://rclone.org/commands/rclone_copy/">copy</a> command instead.</p>
-<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
+<p>Sync the source to the destination, changing the destination only.
+Doesn't transfer files that are identical on source and destination,
+testing by size and modification time or MD5SUM. Destination is updated
+to match source, including deleting files if necessary (except duplicate
+objects, see below). If you don't want to delete files from destination,
+use the <a href="https://rclone.org/commands/rclone_copy/">copy</a>
+command instead.</p>
+<p><strong>Important</strong>: Since this can cause data loss, test
+first with the <code>--dry-run</code> or the
+<code>--interactive</code>/<code>-i</code> flag.</p>
 <pre><code>rclone sync --interactive SOURCE remote:DESTINATION</code></pre>
-<p>Note that files in the destination won't be deleted if there were any errors at any point. Duplicate objects (files with the same name, on those providers that support it) are also not yet handled.</p>
-<p>It is always the contents of the directory that is synced, not the directory itself. So when source:path is a directory, it's the contents of source:path that are copied, not the directory name and contents. See extended explanation in the <a href="https://rclone.org/commands/rclone_copy/">copy</a> command if unsure.</p>
-<p>If dest:path doesn't exist, it is created and the source:path contents go there.</p>
-<p>It is not possible to sync overlapping remotes. However, you may exclude the destination from the sync with a filter rule or by putting an exclude-if-present file inside the destination directory and sync to a destination that is inside the source directory.</p>
-<p>Rclone will sync the modification times of files and directories if the backend supports it. If metadata syncing is required then use the <code>--metadata</code> flag.</p>
-<p>Note that the modification time and metadata for the root directory will <strong>not</strong> be synced. See https://github.com/rclone/rclone/issues/7652 for more info.</p>
-<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics</p>
-<p><strong>Note</strong>: Use the <code>rclone dedupe</code> command to deal with "Duplicate object/directory found in source/destination - ignoring" errors. See <a href="https://forum.rclone.org/t/sync-not-clearing-duplicates/14372">this forum post</a> for more info.</p>
+<p>Note that files in the destination won't be deleted if there were any
+errors at any point. Duplicate objects (files with the same name, on
+those providers that support it) are also not yet handled.</p>
+<p>It is always the contents of the directory that is synced, not the
+directory itself. So when source:path is a directory, it's the contents
+of source:path that are copied, not the directory name and contents. See
+extended explanation in the <a
+href="https://rclone.org/commands/rclone_copy/">copy</a> command if
+unsure.</p>
+<p>If dest:path doesn't exist, it is created and the source:path
+contents go there.</p>
+<p>It is not possible to sync overlapping remotes. However, you may
+exclude the destination from the sync with a filter rule or by putting
+an exclude-if-present file inside the destination directory and sync to
+a destination that is inside the source directory.</p>
+<p>Rclone will sync the modification times of files and directories if
+the backend supports it. If metadata syncing is required then use the
+<code>--metadata</code> flag.</p>
+<p>Note that the modification time and metadata for the root directory
+will <strong>not</strong> be synced. See
+https://github.com/rclone/rclone/issues/7652 for more info.</p>
+<p><strong>Note</strong>: Use the
+<code>-P</code>/<code>--progress</code> flag to view real-time transfer
+statistics</p>
+<p><strong>Note</strong>: Use the <code>rclone dedupe</code> command to
+deal with "Duplicate object/directory found in source/destination -
+ignoring" errors. See <a
+href="https://forum.rclone.org/t/sync-not-clearing-duplicates/14372">this
+forum post</a> for more info.</p>
 <h1 id="logger-flags">Logger Flags</h1>
-<p>The <code>--differ</code>, <code>--missing-on-dst</code>, <code>--missing-on-src</code>, <code>--match</code> and <code>--error</code> flags write paths, one per line, to the file name (or stdout if it is <code>-</code>) supplied. What they write is described in the help below. For example <code>--differ</code> will write all paths which are present on both the source and destination but different.</p>
-<p>The <code>--combined</code> flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.</p>
+<p>The <code>--differ</code>, <code>--missing-on-dst</code>,
+<code>--missing-on-src</code>, <code>--match</code> and
+<code>--error</code> flags write paths, one per line, to the file name
+(or stdout if it is <code>-</code>) supplied. What they write is
+described in the help below. For example <code>--differ</code> will
+write all paths which are present on both the source and destination but
+different.</p>
+<p>The <code>--combined</code> flag will write a file (or stdout) which
+contains all file paths with a symbol and then a space and then the path
+to tell you what happened to it. These are reminiscent of diff
+files.</p>
 <ul>
-<li><code>= path</code> means path was found in source and destination and was identical</li>
-<li>`- path` means path was missing on the source, so only in the destination</li>
-<li>`+ path` means path was missing on the destination, so only in the source</li>
-<li>`* path` means path was present in source and destination but different.</li>
-<li><code>! path</code> means there was an error reading or hashing the source or dest.</li>
+<li><code>= path</code> means path was found in source and destination
+and was identical</li>
+<li><code>- path</code> means path was missing on the source, so only in
+the destination</li>
+<li><code>+ path</code> means path was missing on the destination, so
+only in the source</li>
+<li><code>* path</code> means path was present in source and destination
+but different.</li>
+<li><code>! path</code> means there was an error reading or hashing the
+source or dest.</li>
 </ul>
-<p>The <code>--dest-after</code> flag writes a list file using the same format flags as <a href="https://rclone.org/commands/rclone_lsf/#synopsis"><code>lsf</code></a> (including <a href="https://rclone.org/commands/rclone_lsf/#synopsis">customizable options for hash, modtime, etc.</a>) Conceptually it is similar to rsync's <code>--itemize-changes</code>, but not identical -- it should output an accurate list of what will be on the destination after the sync.</p>
-<p>Note that these logger flags have a few limitations, and certain scenarios are not currently supported:</p>
+<p>The <code>--dest-after</code> flag writes a list file using the same
+format flags as <a
+href="https://rclone.org/commands/rclone_lsf/#synopsis"><code>lsf</code></a>
+(including <a
+href="https://rclone.org/commands/rclone_lsf/#synopsis">customizable
+options for hash, modtime, etc.</a>) Conceptually it is similar to
+rsync's <code>--itemize-changes</code>, but not identical -- it should
+output an accurate list of what will be on the destination after the
+sync.</p>
+<p>Note that these logger flags have a few limitations, and certain
+scenarios are not currently supported:</p>
 <ul>
 <li><code>--max-duration</code> / <code>CutoffModeHard</code></li>
 <li><code>--compare-dest</code> / <code>--copy-dest</code></li>
 <li>server-side moves of an entire dir at once</li>
-<li>High-level retries, because there would be duplicates (use <code>--retries 1</code> to disable)</li>
+<li>High-level retries, because there would be duplicates (use
+<code>--retries 1</code> to disable)</li>
 <li>Possibly some unusual error scenarios</li>
 </ul>
-<p>Note also that each file is logged during the sync, as opposed to after, so it is most useful as a predictor of what SHOULD happen to each file (which may or may not match what actually DID.)</p>
+<p>Note also that each file is logged during the sync, as opposed to
+after, so it is most useful as a predictor of what SHOULD happen to each
+file (which may or may not match what actually DID.)</p>
 <pre><code>rclone sync source:path dest:path [flags]</code></pre>
 <h2 id="options-2">Options</h2>
 <pre><code>      --absolute                Put a leading / in front of path names
@@ -761,7 +1442,9 @@ destpath/sourcepath/two.txt</code></pre>
       --missing-on-src string   Report all files missing from the source to this file
   -s, --separator string        Separator for the items in the format (default &quot;;&quot;)
   -t, --timeformat string       Specify a custom time format, or &#39;max&#39; for max precision supported by remote (default: 2006-01-02 15:04:05)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="copy-options-1">Copy Options</h3>
 <p>Flags for anything which can copy a file</p>
 <pre><code>      --check-first                                 Do all the checks before starting transfers
@@ -845,27 +1528,53 @@ destpath/sourcepath/two.txt</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-2">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-move">rclone move</h1>
 <p>Move files from source to dest.</p>
 <h2 id="synopsis-3">Synopsis</h2>
-<p>Moves the contents of the source directory to the destination directory. Rclone will error if the source and destination overlap and the remote does not support a server-side directory move operation.</p>
-<p>To move single files, use the <a href="https://rclone.org/commands/rclone_moveto/">moveto</a> command instead.</p>
-<p>If no filters are in use and if possible this will server-side move <code>source:path</code> into <code>dest:path</code>. After this <code>source:path</code> will no longer exist.</p>
-<p>Otherwise for each file in <code>source:path</code> selected by the filters (if any) this will move it into <code>dest:path</code>. If possible a server-side move will be used, otherwise it will copy it (server-side if possible) into <code>dest:path</code> then delete the original (if no errors on copy) in <code>source:path</code>.</p>
-<p>If you want to delete empty source directories after move, use the <code>--delete-empty-src-dirs</code> flag.</p>
-<p>See the <a href="https://rclone.org/docs/#no-traverse">--no-traverse</a> option for controlling whether rclone lists the destination directory or not. Supplying this option when moving a small number of files into a large destination can speed transfers up greatly.</p>
-<p>Rclone will sync the modification times of files and directories if the backend supports it. If metadata syncing is required then use the <code>--metadata</code> flag.</p>
-<p>Note that the modification time and metadata for the root directory will <strong>not</strong> be synced. See https://github.com/rclone/rclone/issues/7652 for more info.</p>
-<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
-<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics.</p>
+<p>Moves the contents of the source directory to the destination
+directory. Rclone will error if the source and destination overlap and
+the remote does not support a server-side directory move operation.</p>
+<p>To move single files, use the <a
+href="https://rclone.org/commands/rclone_moveto/">moveto</a> command
+instead.</p>
+<p>If no filters are in use and if possible this will server-side move
+<code>source:path</code> into <code>dest:path</code>. After this
+<code>source:path</code> will no longer exist.</p>
+<p>Otherwise for each file in <code>source:path</code> selected by the
+filters (if any) this will move it into <code>dest:path</code>. If
+possible a server-side move will be used, otherwise it will copy it
+(server-side if possible) into <code>dest:path</code> then delete the
+original (if no errors on copy) in <code>source:path</code>.</p>
+<p>If you want to delete empty source directories after move, use the
+<code>--delete-empty-src-dirs</code> flag.</p>
+<p>See the <a
+href="https://rclone.org/docs/#no-traverse">--no-traverse</a> option for
+controlling whether rclone lists the destination directory or not.
+Supplying this option when moving a small number of files into a large
+destination can speed transfers up greatly.</p>
+<p>Rclone will sync the modification times of files and directories if
+the backend supports it. If metadata syncing is required then use the
+<code>--metadata</code> flag.</p>
+<p>Note that the modification time and metadata for the root directory
+will <strong>not</strong> be synced. See
+https://github.com/rclone/rclone/issues/7652 for more info.</p>
+<p><strong>Important</strong>: Since this can cause data loss, test
+first with the <code>--dry-run</code> or the
+<code>--interactive</code>/<code>-i</code> flag.</p>
+<p><strong>Note</strong>: Use the
+<code>-P</code>/<code>--progress</code> flag to view real-time transfer
+statistics.</p>
 <pre><code>rclone move source:path dest:path [flags]</code></pre>
 <h2 id="options-3">Options</h2>
 <pre><code>      --create-empty-src-dirs   Create empty source dirs on destination after move
       --delete-empty-src-dirs   Delete empty source dirs after move
   -h, --help                    help for move</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="copy-options-2">Copy Options</h3>
 <p>Flags for anything which can copy a file</p>
 <pre><code>      --check-first                                 Do all the checks before starting transfers
@@ -935,26 +1644,42 @@ destpath/sourcepath/two.txt</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-3">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-delete">rclone delete</h1>
 <p>Remove the files in path.</p>
 <h2 id="synopsis-4">Synopsis</h2>
-<p>Remove the files in path. Unlike <a href="https://rclone.org/commands/rclone_purge/">purge</a> it obeys include/exclude filters so can be used to selectively delete files.</p>
-<p><code>rclone delete</code> only deletes files but leaves the directory structure alone. If you want to delete a directory and all of its contents use the <a href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
-<p>If you supply the <code>--rmdirs</code> flag, it will remove all empty directories along with it. You can also use the separate command <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> or <a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> to delete empty directories only.</p>
-<p>For example, to delete all files bigger than 100 MiB, you may first want to check what would be deleted (use either):</p>
+<p>Remove the files in path. Unlike <a
+href="https://rclone.org/commands/rclone_purge/">purge</a> it obeys
+include/exclude filters so can be used to selectively delete files.</p>
+<p><code>rclone delete</code> only deletes files but leaves the
+directory structure alone. If you want to delete a directory and all of
+its contents use the <a
+href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
+<p>If you supply the <code>--rmdirs</code> flag, it will remove all
+empty directories along with it. You can also use the separate command
+<a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> or <a
+href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> to delete
+empty directories only.</p>
+<p>For example, to delete all files bigger than 100 MiB, you may first
+want to check what would be deleted (use either):</p>
 <pre><code>rclone --min-size 100M lsl remote:path
 rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <p>Then proceed with the actual delete:</p>
 <pre><code>rclone --min-size 100M delete remote:path</code></pre>
-<p>That reads "delete everything with a minimum size of 100 MiB", hence delete all files bigger than 100 MiB.</p>
-<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
+<p>That reads "delete everything with a minimum size of 100 MiB", hence
+delete all files bigger than 100 MiB.</p>
+<p><strong>Important</strong>: Since this can cause data loss, test
+first with the <code>--dry-run</code> or the
+<code>--interactive</code>/<code>-i</code> flag.</p>
 <pre><code>rclone delete remote:path [flags]</code></pre>
 <h2 id="options-4">Options</h2>
 <pre><code>  -h, --help     help for delete
       --rmdirs   rmdirs removes empty directories but leaves root intact</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-3">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -990,17 +1715,28 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-4">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-purge">rclone purge</h1>
 <p>Remove the path and all of its contents.</p>
 <h2 id="synopsis-5">Synopsis</h2>
-<p>Remove the path and all of its contents. Note that this does not obey include/exclude filters - everything will be removed. Use the <a href="https://rclone.org/commands/rclone_delete/">delete</a> command if you want to selectively delete files. To delete empty directories only, use command <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> or <a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a>.</p>
-<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
+<p>Remove the path and all of its contents. Note that this does not obey
+include/exclude filters - everything will be removed. Use the <a
+href="https://rclone.org/commands/rclone_delete/">delete</a> command if
+you want to selectively delete files. To delete empty directories only,
+use command <a
+href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> or <a
+href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a>.</p>
+<p><strong>Important</strong>: Since this can cause data loss, test
+first with the <code>--dry-run</code> or the
+<code>--interactive</code>/<code>-i</code> flag.</p>
 <pre><code>rclone purge remote:path [flags]</code></pre>
 <h2 id="options-5">Options</h2>
 <pre><code>  -h, --help   help for purge</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-4">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -1008,14 +1744,17 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-5">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-mkdir">rclone mkdir</h1>
 <p>Make the path if it doesn't already exist.</p>
 <pre><code>rclone mkdir remote:path [flags]</code></pre>
 <h2 id="options-6">Options</h2>
 <pre><code>  -h, --help   help for mkdir</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-5">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -1023,17 +1762,25 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-6">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-rmdir">rclone rmdir</h1>
 <p>Remove the empty directory at path.</p>
 <h2 id="synopsis-6">Synopsis</h2>
-<p>This removes empty directory given by path. Will not remove the path if it has any objects in it, not even empty subdirectories. Use command <a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> (or <a href="https://rclone.org/commands/rclone_delete/">delete</a> with option <code>--rmdirs</code>) to do that.</p>
-<p>To delete a path and any objects in it, use <a href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
+<p>This removes empty directory given by path. Will not remove the path
+if it has any objects in it, not even empty subdirectories. Use command
+<a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> (or <a
+href="https://rclone.org/commands/rclone_delete/">delete</a> with option
+<code>--rmdirs</code>) to do that.</p>
+<p>To delete a path and any objects in it, use <a
+href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
 <pre><code>rclone rmdir remote:path [flags]</code></pre>
 <h2 id="options-7">Options</h2>
 <pre><code>  -h, --help   help for rmdir</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-6">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -1041,27 +1788,58 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-7">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-check">rclone check</h1>
 <p>Checks the files in the source and destination match.</p>
 <h2 id="synopsis-7">Synopsis</h2>
-<p>Checks the files in the source and destination match. It compares sizes and hashes (MD5 or SHA1) and logs a report of files that don't match. It doesn't alter the source or destination.</p>
-<p>For the <a href="https://rclone.org/crypt/">crypt</a> remote there is a dedicated command, <a href="https://rclone.org/commands/rclone_cryptcheck/">cryptcheck</a>, that are able to check the checksums of the encrypted files.</p>
-<p>If you supply the <code>--size-only</code> flag, it will only compare the sizes not the hashes as well. Use this for a quick check.</p>
-<p>If you supply the <code>--download</code> flag, it will download the data from both remotes and check them against each other on the fly. This can be useful for remotes that don't support hashes or if you really want to check all the data.</p>
-<p>If you supply the <code>--checkfile HASH</code> flag with a valid hash name, the <code>source:path</code> must point to a text file in the SUM format.</p>
-<p>If you supply the <code>--one-way</code> flag, it will only check that files in the source match the files in the destination, not the other way around. This means that extra files in the destination that are not in the source will not be detected.</p>
-<p>The <code>--differ</code>, <code>--missing-on-dst</code>, <code>--missing-on-src</code>, <code>--match</code> and <code>--error</code> flags write paths, one per line, to the file name (or stdout if it is <code>-</code>) supplied. What they write is described in the help below. For example <code>--differ</code> will write all paths which are present on both the source and destination but different.</p>
-<p>The <code>--combined</code> flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.</p>
+<p>Checks the files in the source and destination match. It compares
+sizes and hashes (MD5 or SHA1) and logs a report of files that don't
+match. It doesn't alter the source or destination.</p>
+<p>For the <a href="https://rclone.org/crypt/">crypt</a> remote there is
+a dedicated command, <a
+href="https://rclone.org/commands/rclone_cryptcheck/">cryptcheck</a>,
+that are able to check the checksums of the encrypted files.</p>
+<p>If you supply the <code>--size-only</code> flag, it will only compare
+the sizes not the hashes as well. Use this for a quick check.</p>
+<p>If you supply the <code>--download</code> flag, it will download the
+data from both remotes and check them against each other on the fly.
+This can be useful for remotes that don't support hashes or if you
+really want to check all the data.</p>
+<p>If you supply the <code>--checkfile HASH</code> flag with a valid
+hash name, the <code>source:path</code> must point to a text file in the
+SUM format.</p>
+<p>If you supply the <code>--one-way</code> flag, it will only check
+that files in the source match the files in the destination, not the
+other way around. This means that extra files in the destination that
+are not in the source will not be detected.</p>
+<p>The <code>--differ</code>, <code>--missing-on-dst</code>,
+<code>--missing-on-src</code>, <code>--match</code> and
+<code>--error</code> flags write paths, one per line, to the file name
+(or stdout if it is <code>-</code>) supplied. What they write is
+described in the help below. For example <code>--differ</code> will
+write all paths which are present on both the source and destination but
+different.</p>
+<p>The <code>--combined</code> flag will write a file (or stdout) which
+contains all file paths with a symbol and then a space and then the path
+to tell you what happened to it. These are reminiscent of diff
+files.</p>
 <ul>
-<li><code>= path</code> means path was found in source and destination and was identical</li>
-<li>`- path` means path was missing on the source, so only in the destination</li>
-<li>`+ path` means path was missing on the destination, so only in the source</li>
-<li>`* path` means path was present in source and destination but different.</li>
-<li><code>! path</code> means there was an error reading or hashing the source or dest.</li>
+<li><code>= path</code> means path was found in source and destination
+and was identical</li>
+<li><code>- path</code> means path was missing on the source, so only in
+the destination</li>
+<li><code>+ path</code> means path was missing on the destination, so
+only in the source</li>
+<li><code>* path</code> means path was present in source and destination
+but different.</li>
+<li><code>! path</code> means there was an error reading or hashing the
+source or dest.</li>
 </ul>
-<p>The default number of parallel checks is 8. See the <a href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for more information.</p>
+<p>The default number of parallel checks is 8. See the <a
+href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for
+more information.</p>
 <pre><code>rclone check source:path dest:path [flags]</code></pre>
 <h2 id="options-8">Options</h2>
 <pre><code>  -C, --checkfile string        Treat source:path as a SUM file with hashes of given type
@@ -1074,7 +1852,9 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --missing-on-dst string   Report all files missing from the destination to this file
       --missing-on-src string   Report all files missing from the source to this file
       --one-way                 Check one way only, source files must exist on remote</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="check-options">Check Options</h3>
 <p>Flags used for check commands</p>
 <pre><code>      --max-backlog int   Maximum number of objects in sync or check backlog (default 10000)</code></pre>
@@ -1108,12 +1888,14 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-8">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-ls">rclone ls</h1>
 <p>List the objects in the path with size and path.</p>
 <h2 id="synopsis-8">Synopsis</h2>
-<p>Lists the objects in the source path to standard output in a human readable format with size and path. Recurses by default.</p>
+<p>Lists the objects in the source path to standard output in a human
+readable format with size and path. Recurses by default.</p>
 <p>Eg</p>
 <pre><code>$ rclone ls swift:bucket
     60295 bevajer5jef
@@ -1124,19 +1906,32 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <p>There are several related list commands</p>
 <ul>
 <li><code>ls</code> to list size and path of objects only</li>
-<li><code>lsl</code> to list modification time, size and path of objects only</li>
+<li><code>lsl</code> to list modification time, size and path of objects
+only</li>
 <li><code>lsd</code> to list directories only</li>
-<li><code>lsf</code> to list objects and directories in easy to parse format</li>
-<li><code>lsjson</code> to list objects and directories in JSON format</li>
+<li><code>lsf</code> to list objects and directories in easy to parse
+format</li>
+<li><code>lsjson</code> to list objects and directories in JSON
+format</li>
 </ul>
-<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
-<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
-<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
-<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
+<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be
+human-readable. <code>lsf</code> is designed to be human and
+machine-readable. <code>lsjson</code> is designed to be
+machine-readable.</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default -
+use <code>--max-depth 1</code> to stop the recursion.</p>
+<p>The other list commands
+<code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by
+default - use <code>-R</code> to make them recurse.</p>
+<p>Listing a nonexistent directory will produce an error except for
+remotes which can't have empty directories (e.g. s3, swift, or gcs - the
+bucket-based remotes).</p>
 <pre><code>rclone ls remote:path [flags]</code></pre>
 <h2 id="options-9">Options</h2>
 <pre><code>  -h, --help   help for ls</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-5">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -1167,13 +1962,18 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-9">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-lsd">rclone lsd</h1>
 <p>List all directories/containers/buckets in the path.</p>
 <h2 id="synopsis-9">Synopsis</h2>
-<p>Lists the directories in the source path to standard output. Does not recurse by default. Use the <code>-R</code> flag to recurse.</p>
-<p>This command lists the total size of the directory (if known, -1 if not), the modification time (if known, the current time if not), the number of objects in the directory (if known, -1 if not) and the name of the directory, Eg</p>
+<p>Lists the directories in the source path to standard output. Does not
+recurse by default. Use the <code>-R</code> flag to recurse.</p>
+<p>This command lists the total size of the directory (if known, -1 if
+not), the modification time (if known, the current time if not), the
+number of objects in the directory (if known, -1 if not) and the name of
+the directory, Eg</p>
 <pre><code>$ rclone lsd swift:
       494000 2018-04-26 08:43:20     10000 10000files
           65 2018-04-26 08:43:20         1 1File</code></pre>
@@ -1182,25 +1982,39 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
           -1 2016-10-17 17:41:53        -1 1000files
           -1 2017-01-03 14:40:54        -1 2500files
           -1 2017-07-08 14:39:28        -1 4000files</code></pre>
-<p>If you just want the directory names use <code>rclone lsf --dirs-only</code>.</p>
+<p>If you just want the directory names use
+<code>rclone lsf --dirs-only</code>.</p>
 <p>Any of the filtering options can be applied to this command.</p>
 <p>There are several related list commands</p>
 <ul>
 <li><code>ls</code> to list size and path of objects only</li>
-<li><code>lsl</code> to list modification time, size and path of objects only</li>
+<li><code>lsl</code> to list modification time, size and path of objects
+only</li>
 <li><code>lsd</code> to list directories only</li>
-<li><code>lsf</code> to list objects and directories in easy to parse format</li>
-<li><code>lsjson</code> to list objects and directories in JSON format</li>
+<li><code>lsf</code> to list objects and directories in easy to parse
+format</li>
+<li><code>lsjson</code> to list objects and directories in JSON
+format</li>
 </ul>
-<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
-<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
-<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
-<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
+<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be
+human-readable. <code>lsf</code> is designed to be human and
+machine-readable. <code>lsjson</code> is designed to be
+machine-readable.</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default -
+use <code>--max-depth 1</code> to stop the recursion.</p>
+<p>The other list commands
+<code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by
+default - use <code>-R</code> to make them recurse.</p>
+<p>Listing a nonexistent directory will produce an error except for
+remotes which can't have empty directories (e.g. s3, swift, or gcs - the
+bucket-based remotes).</p>
 <pre><code>rclone lsd remote:path [flags]</code></pre>
 <h2 id="options-10">Options</h2>
 <pre><code>  -h, --help        help for lsd
   -R, --recursive   Recurse into the listing</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-6">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -1231,12 +2045,15 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-10">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-lsl">rclone lsl</h1>
 <p>List the objects in path with modification time, size and path.</p>
 <h2 id="synopsis-10">Synopsis</h2>
-<p>Lists the objects in the source path to standard output in a human readable format with modification time, size and path. Recurses by default.</p>
+<p>Lists the objects in the source path to standard output in a human
+readable format with modification time, size and path. Recurses by
+default.</p>
 <p>Eg</p>
 <pre><code>$ rclone lsl swift:bucket
     60295 2016-06-25 18:55:41.062626927 bevajer5jef
@@ -1247,19 +2064,32 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
 <p>There are several related list commands</p>
 <ul>
 <li><code>ls</code> to list size and path of objects only</li>
-<li><code>lsl</code> to list modification time, size and path of objects only</li>
+<li><code>lsl</code> to list modification time, size and path of objects
+only</li>
 <li><code>lsd</code> to list directories only</li>
-<li><code>lsf</code> to list objects and directories in easy to parse format</li>
-<li><code>lsjson</code> to list objects and directories in JSON format</li>
+<li><code>lsf</code> to list objects and directories in easy to parse
+format</li>
+<li><code>lsjson</code> to list objects and directories in JSON
+format</li>
 </ul>
-<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
-<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
-<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
-<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
+<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be
+human-readable. <code>lsf</code> is designed to be human and
+machine-readable. <code>lsjson</code> is designed to be
+machine-readable.</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default -
+use <code>--max-depth 1</code> to stop the recursion.</p>
+<p>The other list commands
+<code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by
+default - use <code>-R</code> to make them recurse.</p>
+<p>Listing a nonexistent directory will produce an error except for
+remotes which can't have empty directories (e.g. s3, swift, or gcs - the
+bucket-based remotes).</p>
 <pre><code>rclone lsl remote:path [flags]</code></pre>
 <h2 id="options-11">Options</h2>
 <pre><code>  -h, --help   help for lsl</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-7">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -1290,15 +2120,26 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-11">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-md5sum">rclone md5sum</h1>
 <p>Produces an md5sum file for all the objects in the path.</p>
 <h2 id="synopsis-11">Synopsis</h2>
-<p>Produces an md5sum file for all the objects in the path. This is in the same format as the standard md5sum tool produces.</p>
-<p>By default, the hash is requested from the remote. If MD5 is not supported by the remote, no hash will be returned. With the download flag, the file will be downloaded from the remote and hashed locally enabling MD5 for any remote.</p>
-<p>For other algorithms, see the <a href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command. Running <code>rclone md5sum remote:path</code> is equivalent to running <code>rclone hashsum MD5 remote:path</code>.</p>
-<p>This command can also hash data received on standard input (stdin), by not passing a remote:path, or by passing a hyphen as remote:path when there is data to read (if not, the hyphen will be treated literally, as a relative path).</p>
+<p>Produces an md5sum file for all the objects in the path. This is in
+the same format as the standard md5sum tool produces.</p>
+<p>By default, the hash is requested from the remote. If MD5 is not
+supported by the remote, no hash will be returned. With the download
+flag, the file will be downloaded from the remote and hashed locally
+enabling MD5 for any remote.</p>
+<p>For other algorithms, see the <a
+href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command.
+Running <code>rclone md5sum remote:path</code> is equivalent to running
+<code>rclone hashsum MD5 remote:path</code>.</p>
+<p>This command can also hash data received on standard input (stdin),
+by not passing a remote:path, or by passing a hyphen as remote:path when
+there is data to read (if not, the hyphen will be treated literally, as
+a relative path).</p>
 <pre><code>rclone md5sum remote:path [flags]</code></pre>
 <h2 id="options-12">Options</h2>
 <pre><code>      --base64               Output base64 encoded hashsum
@@ -1306,7 +2147,9 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --download             Download the file and hash it locally; if this flag is not specified, the hash is requested from the remote
   -h, --help                 help for md5sum
       --output-file string   Output hashsums to a file rather than the terminal</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-8">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -1337,16 +2180,28 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-12">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-sha1sum">rclone sha1sum</h1>
 <p>Produces an sha1sum file for all the objects in the path.</p>
 <h2 id="synopsis-12">Synopsis</h2>
-<p>Produces an sha1sum file for all the objects in the path. This is in the same format as the standard sha1sum tool produces.</p>
-<p>By default, the hash is requested from the remote. If SHA-1 is not supported by the remote, no hash will be returned. With the download flag, the file will be downloaded from the remote and hashed locally enabling SHA-1 for any remote.</p>
-<p>For other algorithms, see the <a href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command. Running <code>rclone sha1sum remote:path</code> is equivalent to running <code>rclone hashsum SHA1 remote:path</code>.</p>
-<p>This command can also hash data received on standard input (stdin), by not passing a remote:path, or by passing a hyphen as remote:path when there is data to read (if not, the hyphen will be treated literally, as a relative path).</p>
-<p>This command can also hash data received on STDIN, if not passing a remote:path.</p>
+<p>Produces an sha1sum file for all the objects in the path. This is in
+the same format as the standard sha1sum tool produces.</p>
+<p>By default, the hash is requested from the remote. If SHA-1 is not
+supported by the remote, no hash will be returned. With the download
+flag, the file will be downloaded from the remote and hashed locally
+enabling SHA-1 for any remote.</p>
+<p>For other algorithms, see the <a
+href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command.
+Running <code>rclone sha1sum remote:path</code> is equivalent to running
+<code>rclone hashsum SHA1 remote:path</code>.</p>
+<p>This command can also hash data received on standard input (stdin),
+by not passing a remote:path, or by passing a hyphen as remote:path when
+there is data to read (if not, the hyphen will be treated literally, as
+a relative path).</p>
+<p>This command can also hash data received on STDIN, if not passing a
+remote:path.</p>
 <pre><code>rclone sha1sum remote:path [flags]</code></pre>
 <h2 id="options-13">Options</h2>
 <pre><code>      --base64               Output base64 encoded hashsum
@@ -1354,7 +2209,9 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --download             Download the file and hash it locally; if this flag is not specified, the hash is requested from the remote
   -h, --help                 help for sha1sum
       --output-file string   Output hashsums to a file rather than the terminal</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-9">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -1385,20 +2242,33 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-13">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-size">rclone size</h1>
 <p>Prints the total size and number of objects in remote:path.</p>
 <h2 id="synopsis-13">Synopsis</h2>
-<p>Counts objects in the path and calculates the total size. Prints the result to standard output.</p>
-<p>By default the output is in human-readable format, but shows values in both human-readable format as well as the raw numbers (global option <code>--human-readable</code> is not considered). Use option <code>--json</code> to format output as JSON instead.</p>
-<p>Recurses by default, use <code>--max-depth 1</code> to stop the recursion.</p>
-<p>Some backends do not always provide file sizes, see for example <a href="https://rclone.org/googlephotos/#size">Google Photos</a> and <a href="https://rclone.org/drive/#limitations-of-google-docs">Google Docs</a>. Rclone will then show a notice in the log indicating how many such files were encountered, and count them in as empty files in the output of the size command.</p>
+<p>Counts objects in the path and calculates the total size. Prints the
+result to standard output.</p>
+<p>By default the output is in human-readable format, but shows values
+in both human-readable format as well as the raw numbers (global option
+<code>--human-readable</code> is not considered). Use option
+<code>--json</code> to format output as JSON instead.</p>
+<p>Recurses by default, use <code>--max-depth 1</code> to stop the
+recursion.</p>
+<p>Some backends do not always provide file sizes, see for example <a
+href="https://rclone.org/googlephotos/#size">Google Photos</a> and <a
+href="https://rclone.org/drive/#limitations-of-google-docs">Google
+Docs</a>. Rclone will then show a notice in the log indicating how many
+such files were encountered, and count them in as empty files in the
+output of the size command.</p>
 <pre><code>rclone size remote:path [flags]</code></pre>
 <h2 id="options-14">Options</h2>
 <pre><code>  -h, --help   help for size
       --json   Format output as JSON</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-10">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -1429,12 +2299,15 @@ rclone --dry-run --min-size 100M delete remote:path</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-14">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-version">rclone version</h1>
 <p>Show the version number.</p>
 <h2 id="synopsis-14">Synopsis</h2>
-<p>Show the rclone version number, the go version, the build target OS and architecture, the runtime OS and kernel version and bitness, build tags and the type of executable (static or dynamic).</p>
+<p>Show the rclone version number, the go version, the build target OS
+and architecture, the runtime OS and kernel version and bitness, build
+tags and the type of executable (static or dynamic).</p>
 <p>For example:</p>
 <pre><code>$ rclone version
 rclone v1.55.0
@@ -1445,8 +2318,10 @@ rclone v1.55.0
 - go/version: go1.16
 - go/linking: static
 - go/tags: none</code></pre>
-<p>Note: before rclone version 1.55 the os/type and os/arch lines were merged, and the "go/version" line was tagged as "go version".</p>
-<p>If you supply the --check flag, then it will do an online check to compare your version with the latest release and the latest beta.</p>
+<p>Note: before rclone version 1.55 the os/type and os/arch lines were
+merged, and the "go/version" line was tagged as "go version".</p>
+<p>If you supply the --check flag, then it will do an online check to
+compare your version with the latest release and the latest beta.</p>
 <pre><code>$ rclone version --check
 yours:  1.42.0.6
 latest: 1.42          (released 2018-06-16)
@@ -1462,19 +2337,24 @@ beta:   1.42.0.5      (released 2018-06-17)
 <h2 id="options-15">Options</h2>
 <pre><code>      --check   Check for new version
   -h, --help    help for version</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-15">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-cleanup">rclone cleanup</h1>
 <p>Clean up the remote if possible.</p>
 <h2 id="synopsis-15">Synopsis</h2>
-<p>Clean up the remote if possible. Empty the trash or delete old file versions. Not supported by all remotes.</p>
+<p>Clean up the remote if possible. Empty the trash or delete old file
+versions. Not supported by all remotes.</p>
 <pre><code>rclone cleanup remote:path [flags]</code></pre>
 <h2 id="options-16">Options</h2>
 <pre><code>  -h, --help   help for cleanup</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-7">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -1482,19 +2362,43 @@ beta:   1.42.0.5      (released 2018-06-17)
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-16">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-dedupe">rclone dedupe</h1>
 <p>Interactively find duplicate filenames and delete/rename them.</p>
 <h2 id="synopsis-16">Synopsis</h2>
-<p>By default <code>dedupe</code> interactively finds files with duplicate names and offers to delete all but one or rename them to be different. This is known as deduping by name.</p>
-<p>Deduping by name is only useful with a small group of backends (e.g. Google Drive, Opendrive) that can have duplicate file names. It can be run on wrapping backends (e.g. crypt) if they wrap a backend which supports duplicate file names.</p>
-<p>However if <code>--by-hash</code> is passed in then dedupe will find files with duplicate hashes instead which will work on any backend which supports at least one hash. This can be used to find files with duplicate content. This is known as deduping by hash.</p>
-<p>If deduping by name, first rclone will merge directories with the same name. It will do this iteratively until all the identically named directories have been merged.</p>
-<p>Next, if deduping by name, for every group of duplicate file names / hashes, it will delete all but one identical file it finds without confirmation. This means that for most duplicated files the <code>dedupe</code> command will not be interactive.</p>
-<p><code>dedupe</code> considers files to be identical if they have the same file path and the same hash. If the backend does not support hashes (e.g. crypt wrapping Google Drive) then they will never be found to be identical. If you use the <code>--size-only</code> flag then files will be considered identical if they have the same size (any hash will be ignored). This can be useful on crypt backends which do not support hashes.</p>
-<p>Next rclone will resolve the remaining duplicates. Exactly which action is taken depends on the dedupe mode. By default, rclone will interactively query the user for each one.</p>
-<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
+<p>By default <code>dedupe</code> interactively finds files with
+duplicate names and offers to delete all but one or rename them to be
+different. This is known as deduping by name.</p>
+<p>Deduping by name is only useful with a small group of backends (e.g.
+Google Drive, Opendrive) that can have duplicate file names. It can be
+run on wrapping backends (e.g. crypt) if they wrap a backend which
+supports duplicate file names.</p>
+<p>However if <code>--by-hash</code> is passed in then dedupe will find
+files with duplicate hashes instead which will work on any backend which
+supports at least one hash. This can be used to find files with
+duplicate content. This is known as deduping by hash.</p>
+<p>If deduping by name, first rclone will merge directories with the
+same name. It will do this iteratively until all the identically named
+directories have been merged.</p>
+<p>Next, if deduping by name, for every group of duplicate file names /
+hashes, it will delete all but one identical file it finds without
+confirmation. This means that for most duplicated files the
+<code>dedupe</code> command will not be interactive.</p>
+<p><code>dedupe</code> considers files to be identical if they have the
+same file path and the same hash. If the backend does not support hashes
+(e.g. crypt wrapping Google Drive) then they will never be found to be
+identical. If you use the <code>--size-only</code> flag then files will
+be considered identical if they have the same size (any hash will be
+ignored). This can be useful on crypt backends which do not support
+hashes.</p>
+<p>Next rclone will resolve the remaining duplicates. Exactly which
+action is taken depends on the dedupe mode. By default, rclone will
+interactively query the user for each one.</p>
+<p><strong>Important</strong>: Since this can cause data loss, test
+first with the <code>--dry-run</code> or the
+<code>--interactive</code>/<code>-i</code> flag.</p>
 <p>Here is an example run.</p>
 <p>Before - with duplicates</p>
 <pre><code>$ rclone lsl drive:dupes
@@ -1537,19 +2441,30 @@ two-3.txt: renamed from: two.txt</code></pre>
    564374 2016-03-05 16:22:52.118000000 two-1.txt
   6048320 2016-03-05 16:22:46.185000000 two-2.txt
   1744073 2016-03-05 16:22:38.104000000 two-3.txt</code></pre>
-<p>Dedupe can be run non interactively using the <code>--dedupe-mode</code> flag or by using an extra parameter with the same value</p>
+<p>Dedupe can be run non interactively using the
+<code>--dedupe-mode</code> flag or by using an extra parameter with the
+same value</p>
 <ul>
 <li><code>--dedupe-mode interactive</code> - interactive as above.</li>
-<li><code>--dedupe-mode skip</code> - removes identical files then skips anything left.</li>
-<li><code>--dedupe-mode first</code> - removes identical files then keeps the first one.</li>
-<li><code>--dedupe-mode newest</code> - removes identical files then keeps the newest one.</li>
-<li><code>--dedupe-mode oldest</code> - removes identical files then keeps the oldest one.</li>
-<li><code>--dedupe-mode largest</code> - removes identical files then keeps the largest one.</li>
-<li><code>--dedupe-mode smallest</code> - removes identical files then keeps the smallest one.</li>
-<li><code>--dedupe-mode rename</code> - removes identical files then renames the rest to be different.</li>
-<li><code>--dedupe-mode list</code> - lists duplicate dirs and files only and changes nothing.</li>
+<li><code>--dedupe-mode skip</code> - removes identical files then skips
+anything left.</li>
+<li><code>--dedupe-mode first</code> - removes identical files then
+keeps the first one.</li>
+<li><code>--dedupe-mode newest</code> - removes identical files then
+keeps the newest one.</li>
+<li><code>--dedupe-mode oldest</code> - removes identical files then
+keeps the oldest one.</li>
+<li><code>--dedupe-mode largest</code> - removes identical files then
+keeps the largest one.</li>
+<li><code>--dedupe-mode smallest</code> - removes identical files then
+keeps the smallest one.</li>
+<li><code>--dedupe-mode rename</code> - removes identical files then
+renames the rest to be different.</li>
+<li><code>--dedupe-mode list</code> - lists duplicate dirs and files
+only and changes nothing.</li>
 </ul>
-<p>For example, to rename all the identically named photos in your Google Photos directory, do</p>
+<p>For example, to rename all the identically named photos in your
+Google Photos directory, do</p>
 <pre><code>rclone dedupe --dedupe-mode rename &quot;drive:Google Photos&quot;</code></pre>
 <p>Or</p>
 <pre><code>rclone dedupe rename &quot;drive:Google Photos&quot;</code></pre>
@@ -1558,7 +2473,9 @@ two-3.txt: renamed from: two.txt</code></pre>
 <pre><code>      --by-hash              Find identical hashes rather than names
       --dedupe-mode string   Dedupe mode interactive|skip|first|newest|oldest|largest|smallest|rename (default &quot;interactive&quot;)
   -h, --help                 help for dedupe</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-8">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -1566,12 +2483,14 @@ two-3.txt: renamed from: two.txt</code></pre>
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-17">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-about">rclone about</h1>
 <p>Get quota information from the remote.</p>
 <h2 id="synopsis-17">Synopsis</h2>
-<p>Prints quota information about a remote to standard output. The output is typically used, free, quota and trash contents.</p>
+<p>Prints quota information about a remote to standard output. The
+output is typically used, free, quota and trash contents.</p>
 <p>E.g. Typical output from <code>rclone about remote:</code> is:</p>
 <pre><code>Total:   17 GiB
 Used:    7.444 GiB
@@ -1584,17 +2503,20 @@ Other:   8.241 GiB</code></pre>
 <li>Used: Total size used.</li>
 <li>Free: Total space available to this user.</li>
 <li>Trashed: Total space used by trash.</li>
-<li>Other: Total amount in other storage (e.g. Gmail, Google Photos).</li>
+<li>Other: Total amount in other storage (e.g. Gmail, Google
+Photos).</li>
 <li>Objects: Total number of objects in the storage.</li>
 </ul>
 <p>All sizes are in number of bytes.</p>
-<p>Applying a <code>--full</code> flag to the command prints the bytes in full, e.g.</p>
+<p>Applying a <code>--full</code> flag to the command prints the bytes
+in full, e.g.</p>
 <pre><code>Total:   18253611008
 Used:    7993453766
 Free:    1411001220
 Trashed: 104857602
 Other:   8849156022</code></pre>
-<p>A <code>--json</code> flag generates conveniently machine-readable output, e.g.</p>
+<p>A <code>--json</code> flag generates conveniently machine-readable
+output, e.g.</p>
 <pre><code>{
     &quot;total&quot;: 18253611008,
     &quot;used&quot;: 7993453766,
@@ -1602,54 +2524,76 @@ Other:   8849156022</code></pre>
     &quot;other&quot;: 8849156022,
     &quot;free&quot;: 1411001220
 }</code></pre>
-<p>Not all backends print all fields. Information is not included if it is not provided by a backend. Where the value is unlimited it is omitted.</p>
-<p>Some backends does not support the <code>rclone about</code> command at all, see complete list in <a href="https://rclone.org/overview/#optional-features">documentation</a>.</p>
+<p>Not all backends print all fields. Information is not included if it
+is not provided by a backend. Where the value is unlimited it is
+omitted.</p>
+<p>Some backends does not support the <code>rclone about</code> command
+at all, see complete list in <a
+href="https://rclone.org/overview/#optional-features">documentation</a>.</p>
 <pre><code>rclone about remote: [flags]</code></pre>
 <h2 id="options-18">Options</h2>
 <pre><code>      --full   Full numbers instead of human-readable
   -h, --help   help for about
       --json   Format output as JSON</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-18">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-authorize">rclone authorize</h1>
 <p>Remote authorization.</p>
 <h2 id="synopsis-18">Synopsis</h2>
-<p>Remote authorization. Used to authorize a remote or headless rclone from a machine with a browser - use as instructed by rclone config.</p>
-<p>Use --auth-no-open-browser to prevent rclone to open auth link in default browser automatically.</p>
-<p>Use --template to generate HTML output via a custom Go template. If a blank string is provided as an argument to this flag, the default template is used.</p>
+<p>Remote authorization. Used to authorize a remote or headless rclone
+from a machine with a browser - use as instructed by rclone config.</p>
+<p>Use --auth-no-open-browser to prevent rclone to open auth link in
+default browser automatically.</p>
+<p>Use --template to generate HTML output via a custom Go template. If a
+blank string is provided as an argument to this flag, the default
+template is used.</p>
 <pre><code>rclone authorize [flags]</code></pre>
 <h2 id="options-19">Options</h2>
 <pre><code>      --auth-no-open-browser   Do not automatically open auth link in default browser
   -h, --help                   help for authorize
       --template string        The path to a custom Go template for generating HTML responses</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-19">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-backend">rclone backend</h1>
 <p>Run a backend-specific command.</p>
 <h2 id="synopsis-19">Synopsis</h2>
-<p>This runs a backend-specific command. The commands themselves (except for "help" and "features") are defined by the backends and you should see the backend docs for definitions.</p>
+<p>This runs a backend-specific command. The commands themselves (except
+for "help" and "features") are defined by the backends and you should
+see the backend docs for definitions.</p>
 <p>You can discover what commands a backend implements by using</p>
 <pre><code>rclone backend help remote:
 rclone backend help &lt;backendname&gt;</code></pre>
-<p>You can also discover information about the backend using (see <a href="https://rclone.org/rc/#operations-fsinfo">operations/fsinfo</a> in the remote control docs for more info).</p>
+<p>You can also discover information about the backend using (see <a
+href="https://rclone.org/rc/#operations-fsinfo">operations/fsinfo</a> in
+the remote control docs for more info).</p>
 <pre><code>rclone backend features remote:</code></pre>
-<p>Pass options to the backend command with -o. This should be key=value or key, e.g.:</p>
+<p>Pass options to the backend command with -o. This should be key=value
+or key, e.g.:</p>
 <pre><code>rclone backend stats remote:path stats -o format=json -o long</code></pre>
-<p>Pass arguments to the backend by placing them on the end of the line</p>
+<p>Pass arguments to the backend by placing them on the end of the
+line</p>
 <pre><code>rclone backend cleanup remote:path file1 file2 file3</code></pre>
-<p>Note to run these commands on a running backend then see <a href="https://rclone.org/rc/#backend-command">backend/command</a> in the rc docs.</p>
+<p>Note to run these commands on a running backend then see <a
+href="https://rclone.org/rc/#backend-command">backend/command</a> in the
+rc docs.</p>
 <pre><code>rclone backend &lt;command&gt; remote:path [opts] &lt;args&gt; [flags]</code></pre>
 <h2 id="options-20">Options</h2>
 <pre><code>  -h, --help                 help for backend
       --json                 Always output in JSON format
   -o, --option stringArray   Option in the form name=value or name</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-9">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -1657,15 +2601,29 @@ rclone backend help &lt;backendname&gt;</code></pre>
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-20">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-bisync">rclone bisync</h1>
 <p>Perform bidirectional synchronization between two paths.</p>
 <h2 id="synopsis-20">Synopsis</h2>
 <p>Perform bidirectional synchronization between two paths.</p>
-<p><a href="https://rclone.org/bisync/">Bisync</a> provides a bidirectional cloud sync solution in rclone. It retains the Path1 and Path2 filesystem listings from the prior run. On each successive run it will: - list files on Path1 and Path2, and check for changes on each side. Changes include <code>New</code>, <code>Newer</code>, <code>Older</code>, and <code>Deleted</code> files. - Propagate changes on Path1 to Path2, and vice-versa.</p>
-<p>Bisync is <strong>in beta</strong> and is considered an <strong>advanced command</strong>, so use with care. Make sure you have read and understood the entire <a href="https://rclone.org/bisync">manual</a> (especially the <a href="https://rclone.org/bisync/#limitations">Limitations</a> section) before using, or data loss can result. Questions can be asked in the <a href="https://forum.rclone.org/">Rclone Forum</a>.</p>
-<p>See <a href="https://rclone.org/bisync/">full bisync description</a> for details.</p>
+<p><a href="https://rclone.org/bisync/">Bisync</a> provides a
+bidirectional cloud sync solution in rclone. It retains the Path1 and
+Path2 filesystem listings from the prior run. On each successive run it
+will: - list files on Path1 and Path2, and check for changes on each
+side. Changes include <code>New</code>, <code>Newer</code>,
+<code>Older</code>, and <code>Deleted</code> files. - Propagate changes
+on Path1 to Path2, and vice-versa.</p>
+<p>Bisync is <strong>in beta</strong> and is considered an
+<strong>advanced command</strong>, so use with care. Make sure you have
+read and understood the entire <a
+href="https://rclone.org/bisync">manual</a> (especially the <a
+href="https://rclone.org/bisync/#limitations">Limitations</a> section)
+before using, or data loss can result. Questions can be asked in the <a
+href="https://forum.rclone.org/">Rclone Forum</a>.</p>
+<p>See <a href="https://rclone.org/bisync/">full bisync description</a>
+for details.</p>
 <pre><code>rclone bisync remote1:path1 remote2:path2 [flags]</code></pre>
 <h2 id="options-21">Options</h2>
 <pre><code>      --backup-dir1 string                   --backup-dir for Path1. Must be a non-overlapping path on the same remote.
@@ -1693,7 +2651,9 @@ rclone backend help &lt;backendname&gt;</code></pre>
       --resync-mode string                   During resync, prefer the version that is: path1, path2, newer, older, larger, smaller (default: path1 if --resync, otherwise none for no resync.) (default &quot;none&quot;)
       --slow-hash-sync-only                  Ignore slow checksums for listings and deltas, but still consider them during sync calls.
       --workdir string                       Use custom working dir - useful for testing. (default: {WORKDIR})</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="copy-options-3">Copy Options</h3>
 <p>Flags for anything which can copy a file</p>
 <pre><code>      --check-first                                 Do all the checks before starting transfers
@@ -1759,7 +2719,8 @@ rclone backend help &lt;backendname&gt;</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-21">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-cat">rclone cat</h1>
 <p>Concatenates any files and sends them to stdout.</p>
@@ -1769,10 +2730,18 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <pre><code>rclone cat remote:path/to/file</code></pre>
 <p>Or like this to output any file in dir or its subdirectories.</p>
 <pre><code>rclone cat remote:path/to/dir</code></pre>
-<p>Or like this to output any .txt files in dir or its subdirectories.</p>
+<p>Or like this to output any .txt files in dir or its
+subdirectories.</p>
 <pre><code>rclone --include &quot;*.txt&quot; cat remote:path/to/dir</code></pre>
-<p>Use the <code>--head</code> flag to print characters only at the start, <code>--tail</code> for the end and <code>--offset</code> and <code>--count</code> to print a section in the middle. Note that if offset is negative it will count from the end, so <code>--offset -1 --count 1</code> is equivalent to <code>--tail 1</code>.</p>
-<p>Use the <code>--separator</code> flag to print a separator value between files. Be sure to shell-escape special characters. For example, to print a newline between files, use:</p>
+<p>Use the <code>--head</code> flag to print characters only at the
+start, <code>--tail</code> for the end and <code>--offset</code> and
+<code>--count</code> to print a section in the middle. Note that if
+offset is negative it will count from the end, so
+<code>--offset -1 --count 1</code> is equivalent to
+<code>--tail 1</code>.</p>
+<p>Use the <code>--separator</code> flag to print a separator value
+between files. Be sure to shell-escape special characters. For example,
+to print a newline between files, use:</p>
 <ul>
 <li><p>bash:</p>
 <pre><code>rclone --include &quot;*.txt&quot; --separator $&#39;\n&#39; cat remote:path/to/dir</code></pre></li>
@@ -1788,7 +2757,9 @@ rclone backend help &lt;backendname&gt;</code></pre>
       --offset int         Start printing at offset N (or from end if -ve)
       --separator string   Separator to use between objects when printing multiple files
       --tail int           Only print the last N characters</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-12">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -1819,26 +2790,53 @@ rclone backend help &lt;backendname&gt;</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-22">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-checksum">rclone checksum</h1>
 <p>Checks the files in the destination against a SUM file.</p>
 <h2 id="synopsis-22">Synopsis</h2>
-<p>Checks that hashsums of destination files match the SUM file. It compares hashes (MD5, SHA1, etc) and logs a report of files which don't match. It doesn't alter the file system.</p>
-<p>The sumfile is treated as the source and the dst:path is treated as the destination for the purposes of the output.</p>
-<p>If you supply the <code>--download</code> flag, it will download the data from the remote and calculate the content hash on the fly. This can be useful for remotes that don't support hashes or if you really want to check all the data.</p>
-<p>Note that hash values in the SUM file are treated as case insensitive.</p>
-<p>If you supply the <code>--one-way</code> flag, it will only check that files in the source match the files in the destination, not the other way around. This means that extra files in the destination that are not in the source will not be detected.</p>
-<p>The <code>--differ</code>, <code>--missing-on-dst</code>, <code>--missing-on-src</code>, <code>--match</code> and <code>--error</code> flags write paths, one per line, to the file name (or stdout if it is <code>-</code>) supplied. What they write is described in the help below. For example <code>--differ</code> will write all paths which are present on both the source and destination but different.</p>
-<p>The <code>--combined</code> flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.</p>
+<p>Checks that hashsums of destination files match the SUM file. It
+compares hashes (MD5, SHA1, etc) and logs a report of files which don't
+match. It doesn't alter the file system.</p>
+<p>The sumfile is treated as the source and the dst:path is treated as
+the destination for the purposes of the output.</p>
+<p>If you supply the <code>--download</code> flag, it will download the
+data from the remote and calculate the content hash on the fly. This can
+be useful for remotes that don't support hashes or if you really want to
+check all the data.</p>
+<p>Note that hash values in the SUM file are treated as case
+insensitive.</p>
+<p>If you supply the <code>--one-way</code> flag, it will only check
+that files in the source match the files in the destination, not the
+other way around. This means that extra files in the destination that
+are not in the source will not be detected.</p>
+<p>The <code>--differ</code>, <code>--missing-on-dst</code>,
+<code>--missing-on-src</code>, <code>--match</code> and
+<code>--error</code> flags write paths, one per line, to the file name
+(or stdout if it is <code>-</code>) supplied. What they write is
+described in the help below. For example <code>--differ</code> will
+write all paths which are present on both the source and destination but
+different.</p>
+<p>The <code>--combined</code> flag will write a file (or stdout) which
+contains all file paths with a symbol and then a space and then the path
+to tell you what happened to it. These are reminiscent of diff
+files.</p>
 <ul>
-<li><code>= path</code> means path was found in source and destination and was identical</li>
-<li>`- path` means path was missing on the source, so only in the destination</li>
-<li>`+ path` means path was missing on the destination, so only in the source</li>
-<li>`* path` means path was present in source and destination but different.</li>
-<li><code>! path</code> means there was an error reading or hashing the source or dest.</li>
+<li><code>= path</code> means path was found in source and destination
+and was identical</li>
+<li><code>- path</code> means path was missing on the source, so only in
+the destination</li>
+<li><code>+ path</code> means path was missing on the destination, so
+only in the source</li>
+<li><code>* path</code> means path was present in source and destination
+but different.</li>
+<li><code>! path</code> means there was an error reading or hashing the
+source or dest.</li>
 </ul>
-<p>The default number of parallel checks is 8. See the <a href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for more information.</p>
+<p>The default number of parallel checks is 8. See the <a
+href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for
+more information.</p>
 <pre><code>rclone checksum &lt;hash&gt; sumfile dst:path [flags]</code></pre>
 <h2 id="options-23">Options</h2>
 <pre><code>      --combined string         Make a combined report of changes to this file
@@ -1850,7 +2848,9 @@ rclone backend help &lt;backendname&gt;</code></pre>
       --missing-on-dst string   Report all files missing from the destination to this file
       --missing-on-src string   Report all files missing from the source to this file
       --one-way                 Check one way only, source files must exist on remote</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-13">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -1881,22 +2881,32 @@ rclone backend help &lt;backendname&gt;</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-23">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-completion">rclone completion</h1>
 <p>Output completion script for a given shell.</p>
 <h2 id="synopsis-23">Synopsis</h2>
-<p>Generates a shell completion script for rclone. Run with <code>--help</code> to list the supported shells.</p>
+<p>Generates a shell completion script for rclone. Run with
+<code>--help</code> to list the supported shells.</p>
 <h2 id="options-24">Options</h2>
 <pre><code>  -h, --help   help for completion</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-24">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
-<li><a href="https://rclone.org/commands/rclone_completion_bash/">rclone completion bash</a> - Output bash completion script for rclone.</li>
-<li><a href="https://rclone.org/commands/rclone_completion_fish/">rclone completion fish</a> - Output fish completion script for rclone.</li>
-<li><a href="https://rclone.org/commands/rclone_completion_powershell/">rclone completion powershell</a> - Output powershell completion script for rclone.</li>
-<li><a href="https://rclone.org/commands/rclone_completion_zsh/">rclone completion zsh</a> - Output zsh completion script for rclone.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone_completion_bash/">rclone
+completion bash</a> - Output bash completion script for rclone.</li>
+<li><a href="https://rclone.org/commands/rclone_completion_fish/">rclone
+completion fish</a> - Output fish completion script for rclone.</li>
+<li><a
+href="https://rclone.org/commands/rclone_completion_powershell/">rclone
+completion powershell</a> - Output powershell completion script for
+rclone.</li>
+<li><a href="https://rclone.org/commands/rclone_completion_zsh/">rclone
+completion zsh</a> - Output zsh completion script for rclone.</li>
 </ul>
 <h1 id="rclone-completion-bash">rclone completion bash</h1>
 <p>Output bash completion script for rclone.</p>
@@ -1907,37 +2917,48 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <p>the generated script will be written to</p>
 <pre><code>/etc/bash_completion.d/rclone</code></pre>
 <p>and so rclone will probably need to be run as root, or with sudo.</p>
-<p>If you supply a path to a file as the command line argument, then the generated script will be written to that file, in which case you should not need root privileges.</p>
+<p>If you supply a path to a file as the command line argument, then the
+generated script will be written to that file, in which case you should
+not need root privileges.</p>
 <p>If output_file is "-", then the output will be written to stdout.</p>
-<p>If you have installed the script into the default location, you can logout and login again to use the autocompletion script.</p>
+<p>If you have installed the script into the default location, you can
+logout and login again to use the autocompletion script.</p>
 <p>Alternatively, you can source the script directly</p>
 <pre><code>. /path/to/my_bash_completion_scripts/rclone</code></pre>
-<p>and the autocompletion functionality will be added to your current shell.</p>
+<p>and the autocompletion functionality will be added to your current
+shell.</p>
 <pre><code>rclone completion bash [output_file] [flags]</code></pre>
 <h2 id="options-25">Options</h2>
 <pre><code>  -h, --help   help for bash</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-25">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_completion/">rclone completion</a> - Output completion script for a given shell.</li>
+<li><a href="https://rclone.org/commands/rclone_completion/">rclone
+completion</a> - Output completion script for a given shell.</li>
 </ul>
 <h1 id="rclone-completion-fish">rclone completion fish</h1>
 <p>Output fish completion script for rclone.</p>
 <h2 id="synopsis-25">Synopsis</h2>
 <p>Generates a fish autocompletion script for rclone.</p>
-<p>This writes to /etc/fish/completions/rclone.fish by default so will probably need to be run with sudo or as root, e.g.</p>
+<p>This writes to /etc/fish/completions/rclone.fish by default so will
+probably need to be run with sudo or as root, e.g.</p>
 <pre><code>sudo rclone completion fish</code></pre>
-<p>Logout and login again to use the autocompletion scripts, or source them directly</p>
+<p>Logout and login again to use the autocompletion scripts, or source
+them directly</p>
 <pre><code>. /etc/fish/completions/rclone.fish</code></pre>
-<p>If you supply a command line argument the script will be written there.</p>
+<p>If you supply a command line argument the script will be written
+there.</p>
 <p>If output_file is "-", then the output will be written to stdout.</p>
 <pre><code>rclone completion fish [output_file] [flags]</code></pre>
 <h2 id="options-26">Options</h2>
 <pre><code>  -h, --help   help for fish</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-26">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_completion/">rclone completion</a> - Output completion script for a given shell.</li>
+<li><a href="https://rclone.org/commands/rclone_completion/">rclone
+completion</a> - Output completion script for a given shell.</li>
 </ul>
 <h1 id="rclone-completion-powershell">rclone completion powershell</h1>
 <p>Output powershell completion script for rclone.</p>
@@ -1945,47 +2966,77 @@ rclone backend help &lt;backendname&gt;</code></pre>
 <p>Generate the autocompletion script for powershell.</p>
 <p>To load completions in your current shell session:</p>
 <pre><code>rclone completion powershell | Out-String | Invoke-Expression</code></pre>
-<p>To load completions for every new session, add the output of the above command to your powershell profile.</p>
-<p>If output_file is "-" or missing, then the output will be written to stdout.</p>
+<p>To load completions for every new session, add the output of the
+above command to your powershell profile.</p>
+<p>If output_file is "-" or missing, then the output will be written to
+stdout.</p>
 <pre><code>rclone completion powershell [output_file] [flags]</code></pre>
 <h2 id="options-27">Options</h2>
 <pre><code>  -h, --help   help for powershell</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-27">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_completion/">rclone completion</a> - Output completion script for a given shell.</li>
+<li><a href="https://rclone.org/commands/rclone_completion/">rclone
+completion</a> - Output completion script for a given shell.</li>
 </ul>
 <h1 id="rclone-completion-zsh">rclone completion zsh</h1>
 <p>Output zsh completion script for rclone.</p>
 <h2 id="synopsis-27">Synopsis</h2>
 <p>Generates a zsh autocompletion script for rclone.</p>
-<p>This writes to /usr/share/zsh/vendor-completions/_rclone by default so will probably need to be run with sudo or as root, e.g.</p>
+<p>This writes to /usr/share/zsh/vendor-completions/_rclone by default
+so will probably need to be run with sudo or as root, e.g.</p>
 <pre><code>sudo rclone completion zsh</code></pre>
-<p>Logout and login again to use the autocompletion scripts, or source them directly</p>
+<p>Logout and login again to use the autocompletion scripts, or source
+them directly</p>
 <pre><code>autoload -U compinit &amp;&amp; compinit</code></pre>
-<p>If you supply a command line argument the script will be written there.</p>
+<p>If you supply a command line argument the script will be written
+there.</p>
 <p>If output_file is "-", then the output will be written to stdout.</p>
 <pre><code>rclone completion zsh [output_file] [flags]</code></pre>
 <h2 id="options-28">Options</h2>
 <pre><code>  -h, --help   help for zsh</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-28">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_completion/">rclone completion</a> - Output completion script for a given shell.</li>
+<li><a href="https://rclone.org/commands/rclone_completion/">rclone
+completion</a> - Output completion script for a given shell.</li>
 </ul>
 <h1 id="rclone-config-create">rclone config create</h1>
 <p>Create a new remote with name, type and options.</p>
 <h2 id="synopsis-28">Synopsis</h2>
-<p>Create a new remote of <code>name</code> with <code>type</code> and options. The options should be passed in pairs of <code>key</code> <code>value</code> or as <code>key=value</code>.</p>
-<p>For example, to make a swift remote of name myremote using auto config you would do:</p>
+<p>Create a new remote of <code>name</code> with <code>type</code> and
+options. The options should be passed in pairs of <code>key</code>
+<code>value</code> or as <code>key=value</code>.</p>
+<p>For example, to make a swift remote of name myremote using auto
+config you would do:</p>
 <pre><code>rclone config create myremote swift env_auth true
 rclone config create myremote swift env_auth=true</code></pre>
-<p>So for example if you wanted to configure a Google Drive remote but using remote authorization you would do this:</p>
+<p>So for example if you wanted to configure a Google Drive remote but
+using remote authorization you would do this:</p>
 <pre><code>rclone config create mydrive drive config_is_local=false</code></pre>
-<p>Note that if the config process would normally ask a question the default is taken (unless <code>--non-interactive</code> is used). Each time that happens rclone will print or DEBUG a message saying how to affect the value taken.</p>
-<p>If any of the parameters passed is a password field, then rclone will automatically obscure them if they aren't already obscured before putting them in the config file.</p>
-<p><strong>NB</strong> If the password parameter is 22 characters or longer and consists only of base64 characters then rclone can get confused about whether the password is already obscured or not and put unobscured passwords into the config file. If you want to be 100% certain that the passwords get obscured then use the <code>--obscure</code> flag, or if you are 100% certain you are already passing obscured passwords then use <code>--no-obscure</code>. You can also set obscured passwords using the <code>rclone config password</code> command.</p>
-<p>The flag <code>--non-interactive</code> is for use by applications that wish to configure rclone themselves, rather than using rclone's text based configuration questions. If this flag is set, and rclone needs to ask the user a question, a JSON blob will be returned with the question in it.</p>
+<p>Note that if the config process would normally ask a question the
+default is taken (unless <code>--non-interactive</code> is used). Each
+time that happens rclone will print or DEBUG a message saying how to
+affect the value taken.</p>
+<p>If any of the parameters passed is a password field, then rclone will
+automatically obscure them if they aren't already obscured before
+putting them in the config file.</p>
+<p><strong>NB</strong> If the password parameter is 22 characters or
+longer and consists only of base64 characters then rclone can get
+confused about whether the password is already obscured or not and put
+unobscured passwords into the config file. If you want to be 100%
+certain that the passwords get obscured then use the
+<code>--obscure</code> flag, or if you are 100% certain you are already
+passing obscured passwords then use <code>--no-obscure</code>. You can
+also set obscured passwords using the
+<code>rclone config password</code> command.</p>
+<p>The flag <code>--non-interactive</code> is for use by applications
+that wish to configure rclone themselves, rather than using rclone's
+text based configuration questions. If this flag is set, and rclone
+needs to ask the user a question, a JSON blob will be returned with the
+question in it.</p>
 <p>This will look something like (some irrelevant detail removed):</p>
 <pre><code>{
     &quot;State&quot;: &quot;*oauth-islocal,teamdrive,,&quot;,
@@ -2010,25 +3061,42 @@ rclone config create myremote swift env_auth=true</code></pre>
     },
     &quot;Error&quot;: &quot;&quot;,
 }</code></pre>
-<p>The format of <code>Option</code> is the same as returned by <code>rclone config providers</code>. The question should be asked to the user and returned to rclone as the <code>--result</code> option along with the <code>--state</code> parameter.</p>
+<p>The format of <code>Option</code> is the same as returned by
+<code>rclone config providers</code>. The question should be asked to
+the user and returned to rclone as the <code>--result</code> option
+along with the <code>--state</code> parameter.</p>
 <p>The keys of <code>Option</code> are used as follows:</p>
 <ul>
 <li><code>Name</code> - name of variable - show to user</li>
-<li><code>Help</code> - help text. Hard wrapped at 80 chars. Any URLs should be clicky.</li>
-<li><code>Default</code> - default value - return this if the user just wants the default.</li>
-<li><code>Examples</code> - the user should be able to choose one of these</li>
+<li><code>Help</code> - help text. Hard wrapped at 80 chars. Any URLs
+should be clicky.</li>
+<li><code>Default</code> - default value - return this if the user just
+wants the default.</li>
+<li><code>Examples</code> - the user should be able to choose one of
+these</li>
 <li><code>Required</code> - the value should be non-empty</li>
-<li><code>IsPassword</code> - the value is a password and should be edited as such</li>
-<li><code>Type</code> - type of value, eg <code>bool</code>, <code>string</code>, <code>int</code> and others</li>
-<li><code>Exclusive</code> - if set no free-form entry allowed only the <code>Examples</code></li>
-<li>Irrelevant keys <code>Provider</code>, <code>ShortOpt</code>, <code>Hide</code>, <code>NoPrefix</code>, <code>Advanced</code></li>
+<li><code>IsPassword</code> - the value is a password and should be
+edited as such</li>
+<li><code>Type</code> - type of value, eg <code>bool</code>,
+<code>string</code>, <code>int</code> and others</li>
+<li><code>Exclusive</code> - if set no free-form entry allowed only the
+<code>Examples</code></li>
+<li>Irrelevant keys <code>Provider</code>, <code>ShortOpt</code>,
+<code>Hide</code>, <code>NoPrefix</code>, <code>Advanced</code></li>
 </ul>
-<p>If <code>Error</code> is set then it should be shown to the user at the same time as the question.</p>
+<p>If <code>Error</code> is set then it should be shown to the user at
+the same time as the question.</p>
 <pre><code>rclone config update name --continue --state &quot;*oauth-islocal,teamdrive,,&quot; --result &quot;true&quot;</code></pre>
-<p>Note that when using <code>--continue</code> all passwords should be passed in the clear (not obscured). Any default config values should be passed in with each invocation of <code>--continue</code>.</p>
-<p>At the end of the non interactive process, rclone will return a result with <code>State</code> as empty string.</p>
-<p>If <code>--all</code> is passed then rclone will ask all the config questions, not just the post config questions. Any parameters are used as defaults for questions as usual.</p>
-<p>Note that <code>bin/config.py</code> in the rclone source implements this protocol as a readable demonstration.</p>
+<p>Note that when using <code>--continue</code> all passwords should be
+passed in the clear (not obscured). Any default config values should be
+passed in with each invocation of <code>--continue</code>.</p>
+<p>At the end of the non interactive process, rclone will return a
+result with <code>State</code> as empty string.</p>
+<p>If <code>--all</code> is passed then rclone will ask all the config
+questions, not just the post config questions. Any parameters are used
+as defaults for questions as usual.</p>
+<p>Note that <code>bin/config.py</code> in the rclone source implements
+this protocol as a readable demonstration.</p>
 <pre><code>rclone config create name type [key value]* [flags]</code></pre>
 <h2 id="options-29">Options</h2>
 <pre><code>      --all               Ask the full set of config questions
@@ -2039,225 +3107,330 @@ rclone config create myremote swift env_auth=true</code></pre>
       --obscure           Force any passwords to be obscured
       --result string     Result - use with --continue
       --state string      State - use with --continue</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-29">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-delete">rclone config delete</h1>
 <p>Delete an existing remote.</p>
 <pre><code>rclone config delete name [flags]</code></pre>
 <h2 id="options-30">Options</h2>
 <pre><code>  -h, --help   help for delete</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-30">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-disconnect">rclone config disconnect</h1>
 <p>Disconnects user from remote</p>
 <h2 id="synopsis-29">Synopsis</h2>
-<p>This disconnects the remote: passed in to the cloud storage system.</p>
+<p>This disconnects the remote: passed in to the cloud storage
+system.</p>
 <p>This normally means revoking the oauth token.</p>
 <p>To reconnect use "rclone config reconnect".</p>
 <pre><code>rclone config disconnect remote: [flags]</code></pre>
 <h2 id="options-31">Options</h2>
 <pre><code>  -h, --help   help for disconnect</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-31">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-dump">rclone config dump</h1>
 <p>Dump the config file as JSON.</p>
 <pre><code>rclone config dump [flags]</code></pre>
 <h2 id="options-32">Options</h2>
 <pre><code>  -h, --help   help for dump</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-32">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-edit">rclone config edit</h1>
 <p>Enter an interactive configuration session.</p>
 <h2 id="synopsis-30">Synopsis</h2>
-<p>Enter an interactive configuration session where you can setup new remotes and manage existing ones. You may also set or remove a password to protect your configuration.</p>
+<p>Enter an interactive configuration session where you can setup new
+remotes and manage existing ones. You may also set or remove a password
+to protect your configuration.</p>
 <pre><code>rclone config edit [flags]</code></pre>
 <h2 id="options-33">Options</h2>
 <pre><code>  -h, --help   help for edit</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-33">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-encryption">rclone config encryption</h1>
 <p>set, remove and check the encryption for the config file</p>
 <h2 id="synopsis-31">Synopsis</h2>
-<p>This command sets, clears and checks the encryption for the config file using the subcommands below.</p>
+<p>This command sets, clears and checks the encryption for the config
+file using the subcommands below.</p>
 <h2 id="options-34">Options</h2>
 <pre><code>  -h, --help   help for encryption</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-34">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
-<li><a href="https://rclone.org/commands/rclone_config_encryption_check/">rclone config encryption check</a> - Check that the config file is encrypted</li>
-<li><a href="https://rclone.org/commands/rclone_config_encryption_remove/">rclone config encryption remove</a> - Remove the config file encryption password</li>
-<li><a href="https://rclone.org/commands/rclone_config_encryption_set/">rclone config encryption set</a> - Set or change the config file encryption password</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption_check/">rclone
+config encryption check</a> - Check that the config file is
+encrypted</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption_remove/">rclone
+config encryption remove</a> - Remove the config file encryption
+password</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption_set/">rclone
+config encryption set</a> - Set or change the config file encryption
+password</li>
 </ul>
-<h1 id="rclone-config-encryption-check">rclone config encryption check</h1>
+<h1 id="rclone-config-encryption-check">rclone config encryption
+check</h1>
 <p>Check that the config file is encrypted</p>
 <h2 id="synopsis-32">Synopsis</h2>
-<p>This checks the config file is encrypted and that you can decrypt it.</p>
-<p>It will attempt to decrypt the config using the password you supply.</p>
-<p>If decryption fails it will return a non-zero exit code if using <code>--password-command</code>, otherwise it will prompt again for the password.</p>
-<p>If the config file is not encrypted it will return a non zero exit code.</p>
+<p>This checks the config file is encrypted and that you can decrypt
+it.</p>
+<p>It will attempt to decrypt the config using the password you
+supply.</p>
+<p>If decryption fails it will return a non-zero exit code if using
+<code>--password-command</code>, otherwise it will prompt again for the
+password.</p>
+<p>If the config file is not encrypted it will return a non zero exit
+code.</p>
 <pre><code>rclone config encryption check [flags]</code></pre>
 <h2 id="options-35">Options</h2>
 <pre><code>  -h, --help   help for check</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-35">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config_encryption/">rclone config encryption</a> - set, remove and check the encryption for the config file</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption/">rclone
+config encryption</a> - set, remove and check the encryption for the
+config file</li>
 </ul>
-<h1 id="rclone-config-encryption-remove">rclone config encryption remove</h1>
+<h1 id="rclone-config-encryption-remove">rclone config encryption
+remove</h1>
 <p>Remove the config file encryption password</p>
 <h2 id="synopsis-33">Synopsis</h2>
 <p>Remove the config file encryption password</p>
-<p>This removes the config file encryption, returning it to un-encrypted.</p>
-<p>If <code>--password-command</code> is in use, this will be called to supply the old config password.</p>
-<p>If the config was not encrypted then no error will be returned and this command will do nothing.</p>
+<p>This removes the config file encryption, returning it to
+un-encrypted.</p>
+<p>If <code>--password-command</code> is in use, this will be called to
+supply the old config password.</p>
+<p>If the config was not encrypted then no error will be returned and
+this command will do nothing.</p>
 <pre><code>rclone config encryption remove [flags]</code></pre>
 <h2 id="options-36">Options</h2>
 <pre><code>  -h, --help   help for remove</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-36">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config_encryption/">rclone config encryption</a> - set, remove and check the encryption for the config file</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption/">rclone
+config encryption</a> - set, remove and check the encryption for the
+config file</li>
 </ul>
 <h1 id="rclone-config-encryption-set">rclone config encryption set</h1>
 <p>Set or change the config file encryption password</p>
 <h2 id="synopsis-34">Synopsis</h2>
 <p>This command sets or changes the config file encryption password.</p>
-<p>If there was no config password set then it sets a new one, otherwise it changes the existing config password.</p>
-<p>Note that if you are changing an encryption password using <code>--password-command</code> then this will be called once to decrypt the config using the old password and then again to read the new password to re-encrypt the config.</p>
-<p>When <code>--password-command</code> is called to change the password then the environment variable <code>RCLONE_PASSWORD_CHANGE=1</code> will be set. So if changing passwords programatically you can use the environment variable to distinguish which password you must supply.</p>
-<p>Alternatively you can remove the password first (with <code>rclone config encryption remove</code>), then set it again with this command which may be easier if you don't mind the unecrypted config file being on the disk briefly.</p>
+<p>If there was no config password set then it sets a new one, otherwise
+it changes the existing config password.</p>
+<p>Note that if you are changing an encryption password using
+<code>--password-command</code> then this will be called once to decrypt
+the config using the old password and then again to read the new
+password to re-encrypt the config.</p>
+<p>When <code>--password-command</code> is called to change the password
+then the environment variable <code>RCLONE_PASSWORD_CHANGE=1</code> will
+be set. So if changing passwords programatically you can use the
+environment variable to distinguish which password you must supply.</p>
+<p>Alternatively you can remove the password first (with
+<code>rclone config encryption remove</code>), then set it again with
+this command which may be easier if you don't mind the unecrypted config
+file being on the disk briefly.</p>
 <pre><code>rclone config encryption set [flags]</code></pre>
 <h2 id="options-37">Options</h2>
 <pre><code>  -h, --help   help for set</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-37">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config_encryption/">rclone config encryption</a> - set, remove and check the encryption for the config file</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption/">rclone
+config encryption</a> - set, remove and check the encryption for the
+config file</li>
 </ul>
 <h1 id="rclone-config-file">rclone config file</h1>
 <p>Show path of configuration file in use.</p>
 <pre><code>rclone config file [flags]</code></pre>
 <h2 id="options-38">Options</h2>
 <pre><code>  -h, --help   help for file</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-38">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-password">rclone config password</h1>
 <p>Update password in an existing remote.</p>
 <h2 id="synopsis-35">Synopsis</h2>
-<p>Update an existing remote's password. The password should be passed in pairs of <code>key</code> <code>password</code> or as <code>key=password</code>. The <code>password</code> should be passed in in clear (unobscured).</p>
-<p>For example, to set password of a remote of name myremote you would do:</p>
+<p>Update an existing remote's password. The password should be passed
+in pairs of <code>key</code> <code>password</code> or as
+<code>key=password</code>. The <code>password</code> should be passed in
+in clear (unobscured).</p>
+<p>For example, to set password of a remote of name myremote you would
+do:</p>
 <pre><code>rclone config password myremote fieldname mypassword
 rclone config password myremote fieldname=mypassword</code></pre>
-<p>This command is obsolete now that "config update" and "config create" both support obscuring passwords directly.</p>
+<p>This command is obsolete now that "config update" and "config create"
+both support obscuring passwords directly.</p>
 <pre><code>rclone config password name [key value]+ [flags]</code></pre>
 <h2 id="options-39">Options</h2>
 <pre><code>  -h, --help   help for password</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-39">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-paths">rclone config paths</h1>
 <p>Show paths used for configuration, cache, temp etc.</p>
 <pre><code>rclone config paths [flags]</code></pre>
 <h2 id="options-40">Options</h2>
 <pre><code>  -h, --help   help for paths</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-40">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-providers">rclone config providers</h1>
 <p>List in JSON format all the providers and options.</p>
 <pre><code>rclone config providers [flags]</code></pre>
 <h2 id="options-41">Options</h2>
 <pre><code>  -h, --help   help for providers</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-41">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-reconnect">rclone config reconnect</h1>
 <p>Re-authenticates user with remote.</p>
 <h2 id="synopsis-36">Synopsis</h2>
 <p>This reconnects remote: passed in to the cloud storage system.</p>
 <p>To disconnect the remote use "rclone config disconnect".</p>
-<p>This normally means going through the interactive oauth flow again.</p>
+<p>This normally means going through the interactive oauth flow
+again.</p>
 <pre><code>rclone config reconnect remote: [flags]</code></pre>
 <h2 id="options-42">Options</h2>
 <pre><code>  -h, --help   help for reconnect</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-42">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-redacted">rclone config redacted</h1>
-<p>Print redacted (decrypted) config file, or the redacted config for a single remote.</p>
+<p>Print redacted (decrypted) config file, or the redacted config for a
+single remote.</p>
 <h2 id="synopsis-37">Synopsis</h2>
-<p>This prints a redacted copy of the config file, either the whole config file or for a given remote.</p>
-<p>The config file will be redacted by replacing all passwords and other sensitive info with XXX.</p>
-<p>This makes the config file suitable for posting online for support.</p>
-<p>It should be double checked before posting as the redaction may not be perfect.</p>
+<p>This prints a redacted copy of the config file, either the whole
+config file or for a given remote.</p>
+<p>The config file will be redacted by replacing all passwords and other
+sensitive info with XXX.</p>
+<p>This makes the config file suitable for posting online for
+support.</p>
+<p>It should be double checked before posting as the redaction may not
+be perfect.</p>
 <pre><code>rclone config redacted [&lt;remote&gt;] [flags]</code></pre>
 <h2 id="options-43">Options</h2>
 <pre><code>  -h, --help   help for redacted</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-43">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-show">rclone config show</h1>
 <p>Print (decrypted) config file, or the config for a single remote.</p>
 <pre><code>rclone config show [&lt;remote&gt;] [flags]</code></pre>
 <h2 id="options-44">Options</h2>
 <pre><code>  -h, --help   help for show</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-44">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-touch">rclone config touch</h1>
 <p>Ensure configuration file exists.</p>
 <pre><code>rclone config touch [flags]</code></pre>
 <h2 id="options-45">Options</h2>
 <pre><code>  -h, --help   help for touch</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-45">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-update">rclone config update</h1>
 <p>Update options in an existing remote.</p>
 <h2 id="synopsis-38">Synopsis</h2>
-<p>Update an existing remote's options. The options should be passed in pairs of <code>key</code> <code>value</code> or as <code>key=value</code>.</p>
-<p>For example, to update the env_auth field of a remote of name myremote you would do:</p>
+<p>Update an existing remote's options. The options should be passed in
+pairs of <code>key</code> <code>value</code> or as
+<code>key=value</code>.</p>
+<p>For example, to update the env_auth field of a remote of name
+myremote you would do:</p>
 <pre><code>rclone config update myremote env_auth true
 rclone config update myremote env_auth=true</code></pre>
-<p>If the remote uses OAuth the token will be updated, if you don't require this add an extra parameter thus:</p>
+<p>If the remote uses OAuth the token will be updated, if you don't
+require this add an extra parameter thus:</p>
 <pre><code>rclone config update myremote env_auth=true config_refresh_token=false</code></pre>
-<p>Note that if the config process would normally ask a question the default is taken (unless <code>--non-interactive</code> is used). Each time that happens rclone will print or DEBUG a message saying how to affect the value taken.</p>
-<p>If any of the parameters passed is a password field, then rclone will automatically obscure them if they aren't already obscured before putting them in the config file.</p>
-<p><strong>NB</strong> If the password parameter is 22 characters or longer and consists only of base64 characters then rclone can get confused about whether the password is already obscured or not and put unobscured passwords into the config file. If you want to be 100% certain that the passwords get obscured then use the <code>--obscure</code> flag, or if you are 100% certain you are already passing obscured passwords then use <code>--no-obscure</code>. You can also set obscured passwords using the <code>rclone config password</code> command.</p>
-<p>The flag <code>--non-interactive</code> is for use by applications that wish to configure rclone themselves, rather than using rclone's text based configuration questions. If this flag is set, and rclone needs to ask the user a question, a JSON blob will be returned with the question in it.</p>
+<p>Note that if the config process would normally ask a question the
+default is taken (unless <code>--non-interactive</code> is used). Each
+time that happens rclone will print or DEBUG a message saying how to
+affect the value taken.</p>
+<p>If any of the parameters passed is a password field, then rclone will
+automatically obscure them if they aren't already obscured before
+putting them in the config file.</p>
+<p><strong>NB</strong> If the password parameter is 22 characters or
+longer and consists only of base64 characters then rclone can get
+confused about whether the password is already obscured or not and put
+unobscured passwords into the config file. If you want to be 100%
+certain that the passwords get obscured then use the
+<code>--obscure</code> flag, or if you are 100% certain you are already
+passing obscured passwords then use <code>--no-obscure</code>. You can
+also set obscured passwords using the
+<code>rclone config password</code> command.</p>
+<p>The flag <code>--non-interactive</code> is for use by applications
+that wish to configure rclone themselves, rather than using rclone's
+text based configuration questions. If this flag is set, and rclone
+needs to ask the user a question, a JSON blob will be returned with the
+question in it.</p>
 <p>This will look something like (some irrelevant detail removed):</p>
 <pre><code>{
     &quot;State&quot;: &quot;*oauth-islocal,teamdrive,,&quot;,
@@ -2282,25 +3455,42 @@ rclone config update myremote env_auth=true</code></pre>
     },
     &quot;Error&quot;: &quot;&quot;,
 }</code></pre>
-<p>The format of <code>Option</code> is the same as returned by <code>rclone config providers</code>. The question should be asked to the user and returned to rclone as the <code>--result</code> option along with the <code>--state</code> parameter.</p>
+<p>The format of <code>Option</code> is the same as returned by
+<code>rclone config providers</code>. The question should be asked to
+the user and returned to rclone as the <code>--result</code> option
+along with the <code>--state</code> parameter.</p>
 <p>The keys of <code>Option</code> are used as follows:</p>
 <ul>
 <li><code>Name</code> - name of variable - show to user</li>
-<li><code>Help</code> - help text. Hard wrapped at 80 chars. Any URLs should be clicky.</li>
-<li><code>Default</code> - default value - return this if the user just wants the default.</li>
-<li><code>Examples</code> - the user should be able to choose one of these</li>
+<li><code>Help</code> - help text. Hard wrapped at 80 chars. Any URLs
+should be clicky.</li>
+<li><code>Default</code> - default value - return this if the user just
+wants the default.</li>
+<li><code>Examples</code> - the user should be able to choose one of
+these</li>
 <li><code>Required</code> - the value should be non-empty</li>
-<li><code>IsPassword</code> - the value is a password and should be edited as such</li>
-<li><code>Type</code> - type of value, eg <code>bool</code>, <code>string</code>, <code>int</code> and others</li>
-<li><code>Exclusive</code> - if set no free-form entry allowed only the <code>Examples</code></li>
-<li>Irrelevant keys <code>Provider</code>, <code>ShortOpt</code>, <code>Hide</code>, <code>NoPrefix</code>, <code>Advanced</code></li>
+<li><code>IsPassword</code> - the value is a password and should be
+edited as such</li>
+<li><code>Type</code> - type of value, eg <code>bool</code>,
+<code>string</code>, <code>int</code> and others</li>
+<li><code>Exclusive</code> - if set no free-form entry allowed only the
+<code>Examples</code></li>
+<li>Irrelevant keys <code>Provider</code>, <code>ShortOpt</code>,
+<code>Hide</code>, <code>NoPrefix</code>, <code>Advanced</code></li>
 </ul>
-<p>If <code>Error</code> is set then it should be shown to the user at the same time as the question.</p>
+<p>If <code>Error</code> is set then it should be shown to the user at
+the same time as the question.</p>
 <pre><code>rclone config update name --continue --state &quot;*oauth-islocal,teamdrive,,&quot; --result &quot;true&quot;</code></pre>
-<p>Note that when using <code>--continue</code> all passwords should be passed in the clear (not obscured). Any default config values should be passed in with each invocation of <code>--continue</code>.</p>
-<p>At the end of the non interactive process, rclone will return a result with <code>State</code> as empty string.</p>
-<p>If <code>--all</code> is passed then rclone will ask all the config questions, not just the post config questions. Any parameters are used as defaults for questions as usual.</p>
-<p>Note that <code>bin/config.py</code> in the rclone source implements this protocol as a readable demonstration.</p>
+<p>Note that when using <code>--continue</code> all passwords should be
+passed in the clear (not obscured). Any default config values should be
+passed in with each invocation of <code>--continue</code>.</p>
+<p>At the end of the non interactive process, rclone will return a
+result with <code>State</code> as empty string.</p>
+<p>If <code>--all</code> is passed then rclone will ask all the config
+questions, not just the post config questions. Any parameters are used
+as defaults for questions as usual.</p>
+<p>Note that <code>bin/config.py</code> in the rclone source implements
+this protocol as a readable demonstration.</p>
 <pre><code>rclone config update name [key value]+ [flags]</code></pre>
 <h2 id="options-46">Options</h2>
 <pre><code>      --all               Ask the full set of config questions
@@ -2311,44 +3501,59 @@ rclone config update myremote env_auth=true</code></pre>
       --obscure           Force any passwords to be obscured
       --result string     Result - use with --continue
       --state string      State - use with --continue</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-46">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-config-userinfo">rclone config userinfo</h1>
 <p>Prints info about logged in user of remote.</p>
 <h2 id="synopsis-39">Synopsis</h2>
-<p>This prints the details of the person logged in to the cloud storage system.</p>
+<p>This prints the details of the person logged in to the cloud storage
+system.</p>
 <pre><code>rclone config userinfo remote: [flags]</code></pre>
 <h2 id="options-47">Options</h2>
 <pre><code>  -h, --help   help for userinfo
       --json   Format output as JSON</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-47">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config/">rclone config</a> - Enter an interactive configuration session.</li>
+<li><a href="https://rclone.org/commands/rclone_config/">rclone
+config</a> - Enter an interactive configuration session.</li>
 </ul>
 <h1 id="rclone-copyto">rclone copyto</h1>
 <p>Copy files from source to dest, skipping identical files.</p>
 <h2 id="synopsis-40">Synopsis</h2>
-<p>If source:path is a file or directory then it copies it to a file or directory named dest:path.</p>
-<p>This can be used to upload single files to other than their current name. If the source is a directory then it acts exactly like the <a href="https://rclone.org/commands/rclone_copy/">copy</a> command.</p>
+<p>If source:path is a file or directory then it copies it to a file or
+directory named dest:path.</p>
+<p>This can be used to upload single files to other than their current
+name. If the source is a directory then it acts exactly like the <a
+href="https://rclone.org/commands/rclone_copy/">copy</a> command.</p>
 <p>So</p>
 <pre><code>rclone copyto src dst</code></pre>
-<p>where src and dst are rclone paths, either remote:path or /path/to/local or C:.</p>
+<p>where src and dst are rclone paths, either remote:path or
+/path/to/local or C:.</p>
 <p>This will:</p>
 <pre><code>if src is file
     copy it to dst, overwriting an existing file if it exists
 if src is directory
     copy it to dst, overwriting existing files if they exist
     see copy command for full details</code></pre>
-<p>This doesn't transfer files that are identical on src and dst, testing by size and modification time or MD5SUM. It doesn't delete files from the destination.</p>
-<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics</p>
+<p>This doesn't transfer files that are identical on src and dst,
+testing by size and modification time or MD5SUM. It doesn't delete files
+from the destination.</p>
+<p><strong>Note</strong>: Use the
+<code>-P</code>/<code>--progress</code> flag to view real-time transfer
+statistics</p>
 <pre><code>rclone copyto source:path dest:path [flags]</code></pre>
 <h2 id="options-48">Options</h2>
 <pre><code>  -h, --help   help for copyto</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="copy-options-4">Copy Options</h3>
 <p>Flags for anything which can copy a file</p>
 <pre><code>      --check-first                                 Do all the checks before starting transfers
@@ -2418,23 +3623,37 @@ if src is directory
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-48">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-copyurl">rclone copyurl</h1>
 <p>Copy the contents of the URL supplied content to dest:path.</p>
 <h2 id="synopsis-41">Synopsis</h2>
-<p>Download a URL's content and copy it to the destination without saving it in temporary storage.</p>
-<p>Setting <code>--auto-filename</code> will attempt to automatically determine the filename from the URL (after any redirections) and used in the destination path.</p>
-<p>With <code>--auto-filename-header</code> in addition, if a specific filename is set in HTTP headers, it will be used instead of the name from the URL. With <code>--print-filename</code> in addition, the resulting file name will be printed.</p>
-<p>Setting <code>--no-clobber</code> will prevent overwriting file on the destination if there is one with the same name.</p>
-<p>Setting <code>--stdout</code> or making the output file name <code>-</code> will cause the output to be written to standard output.</p>
+<p>Download a URL's content and copy it to the destination without
+saving it in temporary storage.</p>
+<p>Setting <code>--auto-filename</code> will attempt to automatically
+determine the filename from the URL (after any redirections) and used in
+the destination path.</p>
+<p>With <code>--auto-filename-header</code> in addition, if a specific
+filename is set in HTTP headers, it will be used instead of the name
+from the URL. With <code>--print-filename</code> in addition, the
+resulting file name will be printed.</p>
+<p>Setting <code>--no-clobber</code> will prevent overwriting file on
+the destination if there is one with the same name.</p>
+<p>Setting <code>--stdout</code> or making the output file name
+<code>-</code> will cause the output to be written to standard
+output.</p>
 <h2 id="troublshooting">Troublshooting</h2>
-<p>If you can't get <code>rclone copyurl</code> to work then here are some things you can try:</p>
+<p>If you can't get <code>rclone copyurl</code> to work then here are
+some things you can try:</p>
 <ul>
-<li><code>--disable-http2</code> rclone will use HTTP2 if available - try disabling it</li>
-<li><code>--bind 0.0.0.0</code> rclone will use IPv6 if available - try disabling it</li>
+<li><code>--disable-http2</code> rclone will use HTTP2 if available -
+try disabling it</li>
+<li><code>--bind 0.0.0.0</code> rclone will use IPv6 if available - try
+disabling it</li>
 <li><code>--bind ::0</code> to disable IPv4</li>
-<li><code>--user agent curl</code> - some sites have whitelists for curl's user-agent - try that</li>
+<li><code>--user agent curl</code> - some sites have whitelists for
+curl's user-agent - try that</li>
 <li>Make sure the site works with <code>curl</code> directly</li>
 </ul>
 <pre><code>rclone copyurl https://example.com dest:path [flags]</code></pre>
@@ -2445,7 +3664,9 @@ if src is directory
       --no-clobber        Prevent overwriting file with same name
   -p, --print-filename    Print the resulting name from --auto-filename
       --stdout            Write the output to stdout rather than a file</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-12">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -2453,30 +3674,59 @@ if src is directory
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-49">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-cryptcheck">rclone cryptcheck</h1>
 <p>Cryptcheck checks the integrity of an encrypted remote.</p>
 <h2 id="synopsis-42">Synopsis</h2>
-<p>Checks a remote against a <a href="https://rclone.org/crypt/">crypted</a> remote. This is the equivalent of running rclone <a href="https://rclone.org/commands/rclone_check/">check</a>, but able to check the checksums of the encrypted remote.</p>
-<p>For it to work the underlying remote of the cryptedremote must support some kind of checksum.</p>
-<p>It works by reading the nonce from each file on the cryptedremote: and using that to encrypt each file on the remote:. It then checks the checksum of the underlying file on the cryptedremote: against the checksum of the file it has just encrypted.</p>
+<p>Checks a remote against a <a
+href="https://rclone.org/crypt/">crypted</a> remote. This is the
+equivalent of running rclone <a
+href="https://rclone.org/commands/rclone_check/">check</a>, but able to
+check the checksums of the encrypted remote.</p>
+<p>For it to work the underlying remote of the cryptedremote must
+support some kind of checksum.</p>
+<p>It works by reading the nonce from each file on the cryptedremote:
+and using that to encrypt each file on the remote:. It then checks the
+checksum of the underlying file on the cryptedremote: against the
+checksum of the file it has just encrypted.</p>
 <p>Use it like this</p>
 <pre><code>rclone cryptcheck /path/to/files encryptedremote:path</code></pre>
-<p>You can use it like this also, but that will involve downloading all the files in remote:path.</p>
+<p>You can use it like this also, but that will involve downloading all
+the files in remote:path.</p>
 <pre><code>rclone cryptcheck remote:path encryptedremote:path</code></pre>
 <p>After it has run it will log the status of the encryptedremote:.</p>
-<p>If you supply the <code>--one-way</code> flag, it will only check that files in the source match the files in the destination, not the other way around. This means that extra files in the destination that are not in the source will not be detected.</p>
-<p>The <code>--differ</code>, <code>--missing-on-dst</code>, <code>--missing-on-src</code>, <code>--match</code> and <code>--error</code> flags write paths, one per line, to the file name (or stdout if it is <code>-</code>) supplied. What they write is described in the help below. For example <code>--differ</code> will write all paths which are present on both the source and destination but different.</p>
-<p>The <code>--combined</code> flag will write a file (or stdout) which contains all file paths with a symbol and then a space and then the path to tell you what happened to it. These are reminiscent of diff files.</p>
+<p>If you supply the <code>--one-way</code> flag, it will only check
+that files in the source match the files in the destination, not the
+other way around. This means that extra files in the destination that
+are not in the source will not be detected.</p>
+<p>The <code>--differ</code>, <code>--missing-on-dst</code>,
+<code>--missing-on-src</code>, <code>--match</code> and
+<code>--error</code> flags write paths, one per line, to the file name
+(or stdout if it is <code>-</code>) supplied. What they write is
+described in the help below. For example <code>--differ</code> will
+write all paths which are present on both the source and destination but
+different.</p>
+<p>The <code>--combined</code> flag will write a file (or stdout) which
+contains all file paths with a symbol and then a space and then the path
+to tell you what happened to it. These are reminiscent of diff
+files.</p>
 <ul>
-<li><code>= path</code> means path was found in source and destination and was identical</li>
-<li>`- path` means path was missing on the source, so only in the destination</li>
-<li>`+ path` means path was missing on the destination, so only in the source</li>
-<li>`* path` means path was present in source and destination but different.</li>
-<li><code>! path</code> means there was an error reading or hashing the source or dest.</li>
+<li><code>= path</code> means path was found in source and destination
+and was identical</li>
+<li><code>- path</code> means path was missing on the source, so only in
+the destination</li>
+<li><code>+ path</code> means path was missing on the destination, so
+only in the source</li>
+<li><code>* path</code> means path was present in source and destination
+but different.</li>
+<li><code>! path</code> means there was an error reading or hashing the
+source or dest.</li>
 </ul>
-<p>The default number of parallel checks is 8. See the <a href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for more information.</p>
+<p>The default number of parallel checks is 8. See the <a
+href="https://rclone.org/docs/#checkers-n">--checkers=N</a> option for
+more information.</p>
 <pre><code>rclone cryptcheck remote:path cryptedremote:path [flags]</code></pre>
 <h2 id="options-50">Options</h2>
 <pre><code>      --combined string         Make a combined report of changes to this file
@@ -2487,7 +3737,9 @@ if src is directory
       --missing-on-dst string   Report all files missing from the destination to this file
       --missing-on-src string   Report all files missing from the source to this file
       --one-way                 Check one way only, source files must exist on remote</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="check-options-1">Check Options</h3>
 <p>Flags used for check commands</p>
 <pre><code>      --max-backlog int   Maximum number of objects in sync or check backlog (default 10000)</code></pre>
@@ -2521,35 +3773,47 @@ if src is directory
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-50">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-cryptdecode">rclone cryptdecode</h1>
 <p>Cryptdecode returns unencrypted file names.</p>
 <h2 id="synopsis-43">Synopsis</h2>
-<p>Returns unencrypted file names when provided with a list of encrypted file names. List limit is 10 items.</p>
-<p>If you supply the <code>--reverse</code> flag, it will return encrypted file names.</p>
+<p>Returns unencrypted file names when provided with a list of encrypted
+file names. List limit is 10 items.</p>
+<p>If you supply the <code>--reverse</code> flag, it will return
+encrypted file names.</p>
 <p>use it like this</p>
 <pre><code>rclone cryptdecode encryptedremote: encryptedfilename1 encryptedfilename2
 
 rclone cryptdecode --reverse encryptedremote: filename1 filename2</code></pre>
-<p>Another way to accomplish this is by using the <code>rclone backend encode</code> (or <code>decode</code>) command. See the documentation on the <a href="https://rclone.org/crypt/">crypt</a> overlay for more info.</p>
+<p>Another way to accomplish this is by using the
+<code>rclone backend encode</code> (or <code>decode</code>) command. See
+the documentation on the <a href="https://rclone.org/crypt/">crypt</a>
+overlay for more info.</p>
 <pre><code>rclone cryptdecode encryptedremote: encryptedfilename [flags]</code></pre>
 <h2 id="options-51">Options</h2>
 <pre><code>  -h, --help      help for cryptdecode
       --reverse   Reverse cryptdecode, encrypts filenames</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-51">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-deletefile">rclone deletefile</h1>
 <p>Remove a single file from remote.</p>
 <h2 id="synopsis-44">Synopsis</h2>
-<p>Remove a single file from remote. Unlike <code>delete</code> it cannot be used to remove a directory and it doesn't obey include/exclude filters - if the specified file exists, it will always be removed.</p>
+<p>Remove a single file from remote. Unlike <code>delete</code> it
+cannot be used to remove a directory and it doesn't obey include/exclude
+filters - if the specified file exists, it will always be removed.</p>
 <pre><code>rclone deletefile remote:path [flags]</code></pre>
 <h2 id="options-52">Options</h2>
 <pre><code>  -h, --help   help for deletefile</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-13">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -2557,69 +3821,108 @@ rclone cryptdecode --reverse encryptedremote: filename1 filename2</code></pre>
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-52">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-gendocs">rclone gendocs</h1>
 <p>Output markdown docs for rclone to the directory supplied.</p>
 <h2 id="synopsis-45">Synopsis</h2>
-<p>This produces markdown docs for the rclone commands to the directory supplied. These are in a format suitable for hugo to render into the rclone.org website.</p>
+<p>This produces markdown docs for the rclone commands to the directory
+supplied. These are in a format suitable for hugo to render into the
+rclone.org website.</p>
 <pre><code>rclone gendocs output_directory [flags]</code></pre>
 <h2 id="options-53">Options</h2>
 <pre><code>  -h, --help   help for gendocs</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-53">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-gitannex">rclone gitannex</h1>
 <p>Speaks with git-annex over stdin/stdout.</p>
 <h2 id="synopsis-46">Synopsis</h2>
-<p>Rclone's <code>gitannex</code> subcommand enables <a href="https://git-annex.branchable.com/">git-annex</a> to store and retrieve content from an rclone remote. It is meant to be run by git-annex, not directly by users.</p>
+<p>Rclone's <code>gitannex</code> subcommand enables <a
+href="https://git-annex.branchable.com/">git-annex</a> to store and
+retrieve content from an rclone remote. It is meant to be run by
+git-annex, not directly by users.</p>
 <h2 id="installation-on-linux">Installation on Linux</h2>
 <ol type="1">
-<li><p>Skip this step if your version of git-annex is <a href="https://git-annex.branchable.com/news/version_10.20240430/">10.20240430</a> or newer. Otherwise, you must create a symlink somewhere on your PATH with a particular name. This symlink helps git-annex tell rclone it wants to run the "gitannex" subcommand.</p>
-<div class="sourceCode" id="cb253"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb253-1"><a href="#cb253-1" aria-hidden="true"></a><span class="co"># Create the helper symlink in &quot;$HOME/bin&quot;.</span></span>
-<span id="cb253-2"><a href="#cb253-2" aria-hidden="true"></a><span class="fu">ln</span> -s <span class="st">&quot;</span><span class="va">$(</span><span class="ex">realpath</span> rclone<span class="va">)</span><span class="st">&quot;</span> <span class="st">&quot;</span><span class="va">$HOME</span><span class="st">/bin/git-annex-remote-rclone-builtin&quot;</span></span>
-<span id="cb253-3"><a href="#cb253-3" aria-hidden="true"></a></span>
-<span id="cb253-4"><a href="#cb253-4" aria-hidden="true"></a><span class="co"># Verify the new symlink is on your PATH.</span></span>
-<span id="cb253-5"><a href="#cb253-5" aria-hidden="true"></a><span class="fu">which</span> git-annex-remote-rclone-builtin</span></code></pre></div></li>
-<li><p>Add a new remote to your git-annex repo. This new remote will connect git-annex with the <code>rclone gitannex</code> subcommand.</p>
-<p>Start by asking git-annex to describe the remote's available configuration parameters.</p>
-<div class="sourceCode" id="cb254"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb254-1"><a href="#cb254-1" aria-hidden="true"></a><span class="co"># If you skipped step 1:</span></span>
-<span id="cb254-2"><a href="#cb254-2" aria-hidden="true"></a><span class="fu">git</span> annex initremote MyRemote type=rclone --whatelse</span>
-<span id="cb254-3"><a href="#cb254-3" aria-hidden="true"></a></span>
-<span id="cb254-4"><a href="#cb254-4" aria-hidden="true"></a><span class="co"># If you created a symlink in step 1:</span></span>
-<span id="cb254-5"><a href="#cb254-5" aria-hidden="true"></a><span class="fu">git</span> annex initremote MyRemote type=external externaltype=rclone-builtin --whatelse</span></code></pre></div>
+<li><p>Skip this step if your version of git-annex is <a
+href="https://git-annex.branchable.com/news/version_10.20240430/">10.20240430</a>
+or newer. Otherwise, you must create a symlink somewhere on your PATH
+with a particular name. This symlink helps git-annex tell rclone it
+wants to run the "gitannex" subcommand.</p>
+<div class="sourceCode" id="cb253"><pre
+class="sourceCode sh"><code class="sourceCode bash"><span id="cb253-1"><a href="#cb253-1" aria-hidden="true" tabindex="-1"></a><span class="co"># Create the helper symlink in &quot;$HOME/bin&quot;.</span></span>
+<span id="cb253-2"><a href="#cb253-2" aria-hidden="true" tabindex="-1"></a><span class="fu">ln</span> <span class="at">-s</span> <span class="st">&quot;</span><span class="va">$(</span><span class="fu">realpath</span> rclone<span class="va">)</span><span class="st">&quot;</span> <span class="st">&quot;</span><span class="va">$HOME</span><span class="st">/bin/git-annex-remote-rclone-builtin&quot;</span></span>
+<span id="cb253-3"><a href="#cb253-3" aria-hidden="true" tabindex="-1"></a></span>
+<span id="cb253-4"><a href="#cb253-4" aria-hidden="true" tabindex="-1"></a><span class="co"># Verify the new symlink is on your PATH.</span></span>
+<span id="cb253-5"><a href="#cb253-5" aria-hidden="true" tabindex="-1"></a><span class="fu">which</span> git-annex-remote-rclone-builtin</span></code></pre></div></li>
+<li><p>Add a new remote to your git-annex repo. This new remote will
+connect git-annex with the <code>rclone gitannex</code> subcommand.</p>
+<p>Start by asking git-annex to describe the remote's available
+configuration parameters.</p>
+<div class="sourceCode" id="cb254"><pre
+class="sourceCode sh"><code class="sourceCode bash"><span id="cb254-1"><a href="#cb254-1" aria-hidden="true" tabindex="-1"></a><span class="co"># If you skipped step 1:</span></span>
+<span id="cb254-2"><a href="#cb254-2" aria-hidden="true" tabindex="-1"></a><span class="fu">git</span> annex initremote MyRemote type=rclone <span class="at">--whatelse</span></span>
+<span id="cb254-3"><a href="#cb254-3" aria-hidden="true" tabindex="-1"></a></span>
+<span id="cb254-4"><a href="#cb254-4" aria-hidden="true" tabindex="-1"></a><span class="co"># If you created a symlink in step 1:</span></span>
+<span id="cb254-5"><a href="#cb254-5" aria-hidden="true" tabindex="-1"></a><span class="fu">git</span> annex initremote MyRemote type=external externaltype=rclone-builtin <span class="at">--whatelse</span></span></code></pre></div>
 <blockquote>
-<p><strong>NOTE</strong>: If you're porting an existing <a href="https://github.com/git-annex-remote-rclone/git-annex-remote-rclone">git-annex-remote-rclone</a> remote to use <code>rclone gitannex</code>, you can probably reuse the configuration parameters verbatim without renaming them. Check parameter synonyms with <code>--whatelse</code> as shown above.</p>
+<p><strong>NOTE</strong>: If you're porting an existing <a
+href="https://github.com/git-annex-remote-rclone/git-annex-remote-rclone">git-annex-remote-rclone</a>
+remote to use <code>rclone gitannex</code>, you can probably reuse the
+configuration parameters verbatim without renaming them. Check parameter
+synonyms with <code>--whatelse</code> as shown above.</p>
 </blockquote>
-<p>The following example creates a new git-annex remote named "MyRemote" that will use the rclone remote named "SomeRcloneRemote". That rclone remote must be one configured in your rclone.conf file, which can be located with <code>rclone config file</code>.</p>
-<div class="sourceCode" id="cb255"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb255-1"><a href="#cb255-1" aria-hidden="true"></a><span class="fu">git</span> annex initremote MyRemote         <span class="kw">\</span></span>
-<span id="cb255-2"><a href="#cb255-2" aria-hidden="true"></a>    <span class="va">type=</span>external                     <span class="kw">\</span></span>
-<span id="cb255-3"><a href="#cb255-3" aria-hidden="true"></a>    <span class="va">externaltype=</span>rclone-builtin       <span class="kw">\</span></span>
-<span id="cb255-4"><a href="#cb255-4" aria-hidden="true"></a>    <span class="va">encryption=</span>none                   <span class="kw">\</span></span>
-<span id="cb255-5"><a href="#cb255-5" aria-hidden="true"></a>    <span class="va">rcloneremotename=</span>SomeRcloneRemote <span class="kw">\</span></span>
-<span id="cb255-6"><a href="#cb255-6" aria-hidden="true"></a>    <span class="va">rcloneprefix=</span>git-annex-content    <span class="kw">\</span></span>
-<span id="cb255-7"><a href="#cb255-7" aria-hidden="true"></a>    <span class="va">rclonelayout=</span>nodir</span></code></pre></div></li>
-<li><p>Before you trust this command with your precious data, be sure to <strong>test the remote</strong>. This command is very new and has not been tested on many rclone backends. Caveat emptor!</p>
-<div class="sourceCode" id="cb256"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb256-1"><a href="#cb256-1" aria-hidden="true"></a><span class="fu">git</span> annex testremote MyRemote</span></code></pre></div></li>
+<p>The following example creates a new git-annex remote named "MyRemote"
+that will use the rclone remote named "SomeRcloneRemote". That rclone
+remote must be one configured in your rclone.conf file, which can be
+located with <code>rclone config file</code>.</p>
+<div class="sourceCode" id="cb255"><pre
+class="sourceCode sh"><code class="sourceCode bash"><span id="cb255-1"><a href="#cb255-1" aria-hidden="true" tabindex="-1"></a><span class="fu">git</span> annex initremote MyRemote         <span class="dt">\</span></span>
+<span id="cb255-2"><a href="#cb255-2" aria-hidden="true" tabindex="-1"></a>    type=external                     <span class="dt">\</span></span>
+<span id="cb255-3"><a href="#cb255-3" aria-hidden="true" tabindex="-1"></a>    externaltype=rclone-builtin       <span class="dt">\</span></span>
+<span id="cb255-4"><a href="#cb255-4" aria-hidden="true" tabindex="-1"></a>    encryption=none                   <span class="dt">\</span></span>
+<span id="cb255-5"><a href="#cb255-5" aria-hidden="true" tabindex="-1"></a>    rcloneremotename=SomeRcloneRemote <span class="dt">\</span></span>
+<span id="cb255-6"><a href="#cb255-6" aria-hidden="true" tabindex="-1"></a>    rcloneprefix=git-annex-content    <span class="dt">\</span></span>
+<span id="cb255-7"><a href="#cb255-7" aria-hidden="true" tabindex="-1"></a>    rclonelayout=nodir</span></code></pre></div></li>
+<li><p>Before you trust this command with your precious data, be sure to
+<strong>test the remote</strong>. This command is very new and has not
+been tested on many rclone backends. Caveat emptor!</p>
+<div class="sourceCode" id="cb256"><pre
+class="sourceCode sh"><code class="sourceCode bash"><span id="cb256-1"><a href="#cb256-1" aria-hidden="true" tabindex="-1"></a><span class="fu">git</span> annex testremote MyRemote</span></code></pre></div></li>
 </ol>
 <p>Happy annexing!</p>
 <pre><code>rclone gitannex [flags]</code></pre>
 <h2 id="options-54">Options</h2>
 <pre><code>  -h, --help   help for gitannex</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-54">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-hashsum">rclone hashsum</h1>
 <p>Produces a hashsum file for all the objects in the path.</p>
 <h2 id="synopsis-47">Synopsis</h2>
-<p>Produces a hash file for all the objects in the path using the hash named. The output is in the same format as the standard md5sum/sha1sum tool.</p>
-<p>By default, the hash is requested from the remote. If the hash is not supported by the remote, no hash will be returned. With the download flag, the file will be downloaded from the remote and hashed locally enabling any hash for any remote.</p>
-<p>For the MD5 and SHA1 algorithms there are also dedicated commands, <a href="https://rclone.org/commands/rclone_md5sum/">md5sum</a> and <a href="https://rclone.org/commands/rclone_sha1sum/">sha1sum</a>.</p>
-<p>This command can also hash data received on standard input (stdin), by not passing a remote:path, or by passing a hyphen as remote:path when there is data to read (if not, the hyphen will be treated literally, as a relative path).</p>
+<p>Produces a hash file for all the objects in the path using the hash
+named. The output is in the same format as the standard md5sum/sha1sum
+tool.</p>
+<p>By default, the hash is requested from the remote. If the hash is not
+supported by the remote, no hash will be returned. With the download
+flag, the file will be downloaded from the remote and hashed locally
+enabling any hash for any remote.</p>
+<p>For the MD5 and SHA1 algorithms there are also dedicated commands, <a
+href="https://rclone.org/commands/rclone_md5sum/">md5sum</a> and <a
+href="https://rclone.org/commands/rclone_sha1sum/">sha1sum</a>.</p>
+<p>This command can also hash data received on standard input (stdin),
+by not passing a remote:path, or by passing a hyphen as remote:path when
+there is data to read (if not, the hyphen will be treated literally, as
+a relative path).</p>
 <p>Run without a hash to see the list of all supported hashes, e.g.</p>
 <pre><code>$ rclone hashsum
 Supported hashes are:
@@ -2630,7 +3933,8 @@ Supported hashes are:
   * sha256</code></pre>
 <p>Then</p>
 <pre><code>$ rclone hashsum MD5 remote:path</code></pre>
-<p>Note that hash names are case insensitive and values are output in lower case.</p>
+<p>Note that hash names are case insensitive and values are output in
+lower case.</p>
 <pre><code>rclone hashsum [&lt;hash&gt; remote:path] [flags]</code></pre>
 <h2 id="options-55">Options</h2>
 <pre><code>      --base64               Output base64 encoded hashsum
@@ -2638,7 +3942,9 @@ Supported hashes are:
       --download             Download the file and hash it locally; if this flag is not specified, the hash is requested from the remote
   -h, --help                 help for hashsum
       --output-file string   Output hashsums to a file rather than the terminal</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-16">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -2669,35 +3975,57 @@ Supported hashes are:
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-55">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-link">rclone link</h1>
 <p>Generate public link to file/folder.</p>
 <h2 id="synopsis-48">Synopsis</h2>
-<p>Create, retrieve or remove a public link to the given file or folder.</p>
+<p>Create, retrieve or remove a public link to the given file or
+folder.</p>
 <pre><code>rclone link remote:path/to/file
 rclone link remote:path/to/folder/
 rclone link --unlink remote:path/to/folder/
 rclone link --expire 1d remote:path/to/file</code></pre>
-<p>If you supply the --expire flag, it will set the expiration time otherwise it will use the default (100 years). <strong>Note</strong> not all backends support the --expire flag - if the backend doesn't support it then the link returned won't expire.</p>
-<p>Use the --unlink flag to remove existing public links to the file or folder. <strong>Note</strong> not all backends support "--unlink" flag - those that don't will just ignore it.</p>
-<p>If successful, the last line of the output will contain the link. Exact capabilities depend on the remote, but the link will always by default be created with the least constraints – e.g. no expiry, no password protection, accessible without account.</p>
+<p>If you supply the --expire flag, it will set the expiration time
+otherwise it will use the default (100 years). <strong>Note</strong> not
+all backends support the --expire flag - if the backend doesn't support
+it then the link returned won't expire.</p>
+<p>Use the --unlink flag to remove existing public links to the file or
+folder. <strong>Note</strong> not all backends support "--unlink" flag -
+those that don't will just ignore it.</p>
+<p>If successful, the last line of the output will contain the link.
+Exact capabilities depend on the remote, but the link will always by
+default be created with the least constraints – e.g. no expiry, no
+password protection, accessible without account.</p>
 <pre><code>rclone link remote:path [flags]</code></pre>
 <h2 id="options-56">Options</h2>
 <pre><code>      --expire Duration   The amount of time that the link will be valid (default off)
   -h, --help              help for link
       --unlink            Remove existing public link to file/folder</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-56">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-listremotes">rclone listremotes</h1>
-<p>List all the remotes in the config file and defined in environment variables.</p>
+<p>List all the remotes in the config file and defined in environment
+variables.</p>
 <h2 id="synopsis-49">Synopsis</h2>
-<p>Lists all the available remotes from the config file, or the remotes matching an optional filter.</p>
-<p>Prints the result in human-readable format by default, and as a simple list of remote names, or if used with flag <code>--long</code> a tabular format including the remote names, types and descriptions. Using flag <code>--json</code> produces machine-readable output instead, which always includes all attributes - including the source (file or environment).</p>
-<p>Result can be filtered by a filter argument which applies to all attributes, and/or filter flags specific for each attribute. The values must be specified according to regular rclone filtering pattern syntax.</p>
+<p>Lists all the available remotes from the config file, or the remotes
+matching an optional filter.</p>
+<p>Prints the result in human-readable format by default, and as a
+simple list of remote names, or if used with flag <code>--long</code> a
+tabular format including the remote names, types and descriptions. Using
+flag <code>--json</code> produces machine-readable output instead, which
+always includes all attributes - including the source (file or
+environment).</p>
+<p>Result can be filtered by a filter argument which applies to all
+attributes, and/or filter flags specific for each attribute. The values
+must be specified according to regular rclone filtering pattern
+syntax.</p>
 <pre><code>rclone listremotes [&lt;filter&gt;] [flags]</code></pre>
 <h2 id="options-57">Options</h2>
 <pre><code>      --description string   Filter remotes by description
@@ -2708,15 +4036,21 @@ rclone link --expire 1d remote:path/to/file</code></pre>
       --order-by string      Instructions on how to order the result, e.g. &#39;type,name=descending&#39;
       --source string        Filter remotes by source, e.g. &#39;file&#39; or &#39;environment&#39;
       --type string          Filter remotes by type</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-57">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-lsf">rclone lsf</h1>
-<p>List directories and objects in remote:path formatted for parsing.</p>
+<p>List directories and objects in remote:path formatted for
+parsing.</p>
 <h2 id="synopsis-50">Synopsis</h2>
-<p>List the contents of the source path (directories and objects) to standard output in a form which is easy to parse by scripts. By default this will just be the names of the objects and directories, one per line. The directories will have a / suffix.</p>
+<p>List the contents of the source path (directories and objects) to
+standard output in a form which is easy to parse by scripts. By default
+this will just be the names of the objects and directories, one per
+line. The directories will have a / suffix.</p>
 <p>Eg</p>
 <pre><code>$ rclone lsf swift:bucket
 bevajer5jef
@@ -2724,7 +4058,9 @@ canole
 diwogej7
 ferejej3gux/
 fubuwic</code></pre>
-<p>Use the <code>--format</code> option to control what gets listed. By default this is just the path, but you can use these parameters to control the output:</p>
+<p>Use the <code>--format</code> option to control what gets listed. By
+default this is just the path, but you can use these parameters to
+control the output:</p>
 <pre><code>p - path
 s - size
 t - modification time
@@ -2735,7 +4071,9 @@ m - MimeType of object if known
 e - encrypted name
 T - tier of storage if known, e.g. &quot;Hot&quot; or &quot;Cool&quot;
 M - Metadata of object in JSON blob format, eg {&quot;key&quot;:&quot;value&quot;}</code></pre>
-<p>So if you wanted the path, size and modification time, you would use <code>--format "pst"</code>, or maybe <code>--format "tsp"</code> to put the path last.</p>
+<p>So if you wanted the path, size and modification time, you would use
+<code>--format "pst"</code>, or maybe <code>--format "tsp"</code> to put
+the path last.</p>
 <p>Eg</p>
 <pre><code>$ rclone lsf  --format &quot;tsp&quot; swift:bucket
 2016-06-25 18:55:41;60295;bevajer5jef
@@ -2743,7 +4081,12 @@ M - Metadata of object in JSON blob format, eg {&quot;key&quot;:&quot;value&quot
 2016-06-25 18:55:43;94467;diwogej7
 2018-04-26 08:50:45;0;ferejej3gux/
 2016-06-25 18:55:40;37600;fubuwic</code></pre>
-<p>If you specify "h" in the format you will get the MD5 hash by default, use the <code>--hash</code> flag to change which hash you want. Note that this can be returned as an empty string if it isn't available on the object (and for directories), "ERROR" if there was an error reading it from the object and "UNSUPPORTED" if that object does not support that hash type.</p>
+<p>If you specify "h" in the format you will get the MD5 hash by
+default, use the <code>--hash</code> flag to change which hash you want.
+Note that this can be returned as an empty string if it isn't available
+on the object (and for directories), "ERROR" if there was an error
+reading it from the object and "UNSUPPORTED" if that object does not
+support that hash type.</p>
 <p>For example, to emulate the md5sum command you can use</p>
 <pre><code>rclone lsf -R --hash MD5 --format hp --separator &quot;  &quot; --files-only .</code></pre>
 <p>Eg</p>
@@ -2754,7 +4097,9 @@ cd65ac234e6fea5925974a51cdd865cc  canole
 8fd37c3810dd660778137ac3a66cc06d  fubuwic
 99713e14a4c4ff553acaf1930fad985b  gixacuh7ku</code></pre>
 <p>(Though "rclone md5sum ." is an easier way of typing this.)</p>
-<p>By default the separator is ";" this can be changed with the <code>--separator</code> flag. Note that separators aren't escaped in the path so putting it last is a good strategy.</p>
+<p>By default the separator is ";" this can be changed with the
+<code>--separator</code> flag. Note that separators aren't escaped in
+the path so putting it last is a good strategy.</p>
 <p>Eg</p>
 <pre><code>$ rclone lsf  --separator &quot;,&quot; --format &quot;tshp&quot; swift:bucket
 2016-06-25 18:55:41,60295,7908e352297f0f530b84a756f188baa3,bevajer5jef
@@ -2762,37 +4107,56 @@ cd65ac234e6fea5925974a51cdd865cc  canole
 2016-06-25 18:55:43,94467,03b5341b4f234b9d984d03ad076bae91,diwogej7
 2018-04-26 08:52:53,0,,ferejej3gux/
 2016-06-25 18:55:40,37600,8fd37c3810dd660778137ac3a66cc06d,fubuwic</code></pre>
-<p>You can output in CSV standard format. This will escape things in " if they contain ,</p>
+<p>You can output in CSV standard format. This will escape things in "
+if they contain ,</p>
 <p>Eg</p>
 <pre><code>$ rclone lsf --csv --files-only --format ps remote:path
 test.log,22355
 test.sh,449
 &quot;this file contains a comma, in the file name.txt&quot;,6</code></pre>
-<p>Note that the <code>--absolute</code> parameter is useful for making lists of files to pass to an rclone copy with the <code>--files-from-raw</code> flag.</p>
-<p>For example, to find all the files modified within one day and copy those only (without traversing the whole directory structure):</p>
+<p>Note that the <code>--absolute</code> parameter is useful for making
+lists of files to pass to an rclone copy with the
+<code>--files-from-raw</code> flag.</p>
+<p>For example, to find all the files modified within one day and copy
+those only (without traversing the whole directory structure):</p>
 <pre><code>rclone lsf --absolute --files-only --max-age 1d /path/to/local &gt; new_files
 rclone copy --files-from-raw new_files /path/to/local remote:path</code></pre>
-<p>The default time format is <code>'2006-01-02 15:04:05'</code>. <a href="https://pkg.go.dev/time#pkg-constants">Other formats</a> can be specified with the <code>--time-format</code> flag. Examples:</p>
+<p>The default time format is <code>'2006-01-02 15:04:05'</code>. <a
+href="https://pkg.go.dev/time#pkg-constants">Other formats</a> can be
+specified with the <code>--time-format</code> flag. Examples:</p>
 <pre><code>rclone lsf remote:path --format pt --time-format &#39;Jan 2, 2006 at 3:04pm (MST)&#39;
 rclone lsf remote:path --format pt --time-format &#39;2006-01-02 15:04:05.000000000&#39;
 rclone lsf remote:path --format pt --time-format &#39;2006-01-02T15:04:05.999999999Z07:00&#39;
 rclone lsf remote:path --format pt --time-format RFC3339
 rclone lsf remote:path --format pt --time-format DateOnly
 rclone lsf remote:path --format pt --time-format max</code></pre>
-<p><code>--time-format max</code> will automatically truncate '<code>2006-01-02 15:04:05.000000000</code>' to the maximum precision supported by the remote.</p>
+<p><code>--time-format max</code> will automatically truncate
+'<code>2006-01-02 15:04:05.000000000</code>' to the maximum precision
+supported by the remote.</p>
 <p>Any of the filtering options can be applied to this command.</p>
 <p>There are several related list commands</p>
 <ul>
 <li><code>ls</code> to list size and path of objects only</li>
-<li><code>lsl</code> to list modification time, size and path of objects only</li>
+<li><code>lsl</code> to list modification time, size and path of objects
+only</li>
 <li><code>lsd</code> to list directories only</li>
-<li><code>lsf</code> to list objects and directories in easy to parse format</li>
-<li><code>lsjson</code> to list objects and directories in JSON format</li>
+<li><code>lsf</code> to list objects and directories in easy to parse
+format</li>
+<li><code>lsjson</code> to list objects and directories in JSON
+format</li>
 </ul>
-<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
-<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
-<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
-<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
+<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be
+human-readable. <code>lsf</code> is designed to be human and
+machine-readable. <code>lsjson</code> is designed to be
+machine-readable.</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default -
+use <code>--max-depth 1</code> to stop the recursion.</p>
+<p>The other list commands
+<code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by
+default - use <code>-R</code> to make them recurse.</p>
+<p>Listing a nonexistent directory will produce an error except for
+remotes which can't have empty directories (e.g. s3, swift, or gcs - the
+bucket-based remotes).</p>
 <pre><code>rclone lsf remote:path [flags]</code></pre>
 <h2 id="options-58">Options</h2>
 <pre><code>      --absolute             Put a leading / in front of path names
@@ -2806,7 +4170,9 @@ rclone lsf remote:path --format pt --time-format max</code></pre>
   -R, --recursive            Recurse into the listing
   -s, --separator string     Separator for the items in the format (default &quot;;&quot;)
   -t, --time-format string   Specify a custom time format, or &#39;max&#39; for max precision supported by remote (default: 2006-01-02 15:04:05)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-17">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -2837,7 +4203,8 @@ rclone lsf remote:path --format pt --time-format max</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-58">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-lsjson">rclone lsjson</h1>
 <p>List directories and objects in the path in JSON format.</p>
@@ -2865,39 +4232,87 @@ rclone lsf remote:path --format pt --time-format max</code></pre>
 }</code></pre>
 <p>The exact set of properties included depends on the backend:</p>
 <ul>
-<li>The property IsBucket will only be included for bucket-based remotes, and only for directories that are buckets. It will always be omitted when value is not true.</li>
-<li>Properties Encrypted and EncryptedPath will only be included for encrypted remotes, and (as mentioned below) only if the <code>--encrypted</code> option is set.</li>
+<li>The property IsBucket will only be included for bucket-based
+remotes, and only for directories that are buckets. It will always be
+omitted when value is not true.</li>
+<li>Properties Encrypted and EncryptedPath will only be included for
+encrypted remotes, and (as mentioned below) only if the
+<code>--encrypted</code> option is set.</li>
 </ul>
 <p>Different options may also affect which properties are included:</p>
 <ul>
-<li>If <code>--hash</code> is not specified, the Hashes property will be omitted. The types of hash can be specified with the <code>--hash-type</code> parameter (which may be repeated). If <code>--hash-type</code> is set then it implies <code>--hash</code>.</li>
-<li>If <code>--no-modtime</code> is specified then ModTime will be blank. This can speed things up on remotes where reading the ModTime takes an extra request (e.g. s3, swift).</li>
-<li>If <code>--no-mimetype</code> is specified then MimeType will be blank. This can speed things up on remotes where reading the MimeType takes an extra request (e.g. s3, swift).</li>
-<li>If <code>--encrypted</code> is not specified the Encrypted and EncryptedPath properties will be omitted - even for encrypted remotes.</li>
-<li>If <code>--metadata</code> is set then an additional Metadata property will be returned. This will have <a href="https://rclone.org/docs/#metadata">metadata</a> in rclone standard format as a JSON object.</li>
+<li>If <code>--hash</code> is not specified, the Hashes property will be
+omitted. The types of hash can be specified with the
+<code>--hash-type</code> parameter (which may be repeated). If
+<code>--hash-type</code> is set then it implies
+<code>--hash</code>.</li>
+<li>If <code>--no-modtime</code> is specified then ModTime will be
+blank. This can speed things up on remotes where reading the ModTime
+takes an extra request (e.g. s3, swift).</li>
+<li>If <code>--no-mimetype</code> is specified then MimeType will be
+blank. This can speed things up on remotes where reading the MimeType
+takes an extra request (e.g. s3, swift).</li>
+<li>If <code>--encrypted</code> is not specified the Encrypted and
+EncryptedPath properties will be omitted - even for encrypted
+remotes.</li>
+<li>If <code>--metadata</code> is set then an additional Metadata
+property will be returned. This will have <a
+href="https://rclone.org/docs/#metadata">metadata</a> in rclone standard
+format as a JSON object.</li>
 </ul>
-<p>The default is to list directories and files/objects, but this can be changed with the following options:</p>
+<p>The default is to list directories and files/objects, but this can be
+changed with the following options:</p>
 <ul>
-<li>If <code>--dirs-only</code> is specified then directories will be returned only, no files/objects.</li>
-<li>If <code>--files-only</code> is specified then files will be returned only, no directories.</li>
+<li>If <code>--dirs-only</code> is specified then directories will be
+returned only, no files/objects.</li>
+<li>If <code>--files-only</code> is specified then files will be
+returned only, no directories.</li>
 </ul>
-<p>If <code>--stat</code> is set then the the output is not an array of items, but instead a single JSON blob will be returned about the item pointed to. This will return an error if the item isn't found, however on bucket based backends (like s3, gcs, b2, azureblob etc) if the item isn't found it will return an empty directory, as it isn't possible to tell empty directories from missing directories there.</p>
-<p>The Path field will only show folders below the remote path being listed. If "remote:path" contains the file "subfolder/file.txt", the Path for "file.txt" will be "subfolder/file.txt", not "remote:path/subfolder/file.txt". When used without <code>--recursive</code> the Path will always be the same as Name.</p>
-<p>The time is in RFC3339 format with up to nanosecond precision. The number of decimal digits in the seconds will depend on the precision that the remote can hold the times, so if times are accurate to the nearest millisecond (e.g. Google Drive) then 3 digits will always be shown ("2017-05-31T16:15:57.034+01:00") whereas if the times are accurate to the nearest second (Dropbox, Box, WebDav, etc.) no digits will be shown ("2017-05-31T16:15:57+01:00").</p>
-<p>The whole output can be processed as a JSON blob, or alternatively it can be processed line by line as each item is written on individual lines (except with <code>--stat</code>).</p>
+<p>If <code>--stat</code> is set then the the output is not an array of
+items, but instead a single JSON blob will be returned about the item
+pointed to. This will return an error if the item isn't found, however
+on bucket based backends (like s3, gcs, b2, azureblob etc) if the item
+isn't found it will return an empty directory, as it isn't possible to
+tell empty directories from missing directories there.</p>
+<p>The Path field will only show folders below the remote path being
+listed. If "remote:path" contains the file "subfolder/file.txt", the
+Path for "file.txt" will be "subfolder/file.txt", not
+"remote:path/subfolder/file.txt". When used without
+<code>--recursive</code> the Path will always be the same as Name.</p>
+<p>The time is in RFC3339 format with up to nanosecond precision. The
+number of decimal digits in the seconds will depend on the precision
+that the remote can hold the times, so if times are accurate to the
+nearest millisecond (e.g. Google Drive) then 3 digits will always be
+shown ("2017-05-31T16:15:57.034+01:00") whereas if the times are
+accurate to the nearest second (Dropbox, Box, WebDav, etc.) no digits
+will be shown ("2017-05-31T16:15:57+01:00").</p>
+<p>The whole output can be processed as a JSON blob, or alternatively it
+can be processed line by line as each item is written on individual
+lines (except with <code>--stat</code>).</p>
 <p>Any of the filtering options can be applied to this command.</p>
 <p>There are several related list commands</p>
 <ul>
 <li><code>ls</code> to list size and path of objects only</li>
-<li><code>lsl</code> to list modification time, size and path of objects only</li>
+<li><code>lsl</code> to list modification time, size and path of objects
+only</li>
 <li><code>lsd</code> to list directories only</li>
-<li><code>lsf</code> to list objects and directories in easy to parse format</li>
-<li><code>lsjson</code> to list objects and directories in JSON format</li>
+<li><code>lsf</code> to list objects and directories in easy to parse
+format</li>
+<li><code>lsjson</code> to list objects and directories in JSON
+format</li>
 </ul>
-<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be human-readable. <code>lsf</code> is designed to be human and machine-readable. <code>lsjson</code> is designed to be machine-readable.</p>
-<p>Note that <code>ls</code> and <code>lsl</code> recurse by default - use <code>--max-depth 1</code> to stop the recursion.</p>
-<p>The other list commands <code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by default - use <code>-R</code> to make them recurse.</p>
-<p>Listing a nonexistent directory will produce an error except for remotes which can't have empty directories (e.g. s3, swift, or gcs - the bucket-based remotes).</p>
+<p><code>ls</code>,<code>lsl</code>,<code>lsd</code> are designed to be
+human-readable. <code>lsf</code> is designed to be human and
+machine-readable. <code>lsjson</code> is designed to be
+machine-readable.</p>
+<p>Note that <code>ls</code> and <code>lsl</code> recurse by default -
+use <code>--max-depth 1</code> to stop the recursion.</p>
+<p>The other list commands
+<code>lsd</code>,<code>lsf</code>,<code>lsjson</code> do not recurse by
+default - use <code>-R</code> to make them recurse.</p>
+<p>Listing a nonexistent directory will produce an error except for
+remotes which can't have empty directories (e.g. s3, swift, or gcs - the
+bucket-based remotes).</p>
 <pre><code>rclone lsjson remote:path [flags]</code></pre>
 <h2 id="options-59">Options</h2>
 <pre><code>      --dirs-only               Show only directories in the listing
@@ -2912,7 +4327,9 @@ rclone lsf remote:path --format pt --time-format max</code></pre>
       --original                Show the ID of the underlying Object
   -R, --recursive               Recurse into the listing
       --stat                    Just return the info for the pointed to file</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-18">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -2943,117 +4360,400 @@ rclone lsf remote:path --format pt --time-format max</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-59">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-mount">rclone mount</h1>
 <p>Mount the remote as file system on a mountpoint.</p>
 <h2 id="synopsis-52">Synopsis</h2>
-<p>Rclone mount allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
-<p>First set up your remote using <code>rclone config</code>. Check it works with <code>rclone ls</code> etc.</p>
-<p>On Linux and macOS, you can run mount in either foreground or background (aka daemon) mode. Mount runs in foreground mode by default. Use the <code>--daemon</code> flag to force background mode. On Windows you can run mount in foreground only, the flag is ignored.</p>
-<p>In background mode rclone acts as a generic Unix mount program: the main program starts, spawns background rclone process to setup and maintain the mount, waits until success or timeout and exits with appropriate code (killing the child process if it fails).</p>
-<p>On Linux/macOS/FreeBSD start the mount like this, where <code>/path/to/local/mount</code> is an <strong>empty</strong> <strong>existing</strong> directory:</p>
+<p>Rclone mount allows Linux, FreeBSD, macOS and Windows to mount any of
+Rclone's cloud storage systems as a file system with FUSE.</p>
+<p>First set up your remote using <code>rclone config</code>. Check it
+works with <code>rclone ls</code> etc.</p>
+<p>On Linux and macOS, you can run mount in either foreground or
+background (aka daemon) mode. Mount runs in foreground mode by default.
+Use the <code>--daemon</code> flag to force background mode. On Windows
+you can run mount in foreground only, the flag is ignored.</p>
+<p>In background mode rclone acts as a generic Unix mount program: the
+main program starts, spawns background rclone process to setup and
+maintain the mount, waits until success or timeout and exits with
+appropriate code (killing the child process if it fails).</p>
+<p>On Linux/macOS/FreeBSD start the mount like this, where
+<code>/path/to/local/mount</code> is an <strong>empty</strong>
+<strong>existing</strong> directory:</p>
 <pre><code>rclone mount remote:path/to/files /path/to/local/mount</code></pre>
-<p>On Windows you can start a mount in different ways. See <a href="#mounting-modes-on-windows">below</a> for details. If foreground mount is used interactively from a console window, rclone will serve the mount and occupy the console so another window should be used to work with the mount until rclone is interrupted e.g. by pressing Ctrl-C.</p>
-<p>The following examples will mount to an automatically assigned drive, to specific drive letter <code>X:</code>, to path <code>C:\path\parent\mount</code> (where parent directory or drive must exist, and mount must <strong>not</strong> exist, and is not supported when <a href="#mounting-modes-on-windows">mounting as a network drive</a>), and the last example will mount as network share <code>\\cloud\remote</code> and map it to an automatically assigned drive:</p>
+<p>On Windows you can start a mount in different ways. See <a
+href="#mounting-modes-on-windows">below</a> for details. If foreground
+mount is used interactively from a console window, rclone will serve the
+mount and occupy the console so another window should be used to work
+with the mount until rclone is interrupted e.g. by pressing Ctrl-C.</p>
+<p>The following examples will mount to an automatically assigned drive,
+to specific drive letter <code>X:</code>, to path
+<code>C:\path\parent\mount</code> (where parent directory or drive must
+exist, and mount must <strong>not</strong> exist, and is not supported
+when <a href="#mounting-modes-on-windows">mounting as a network
+drive</a>), and the last example will mount as network share
+<code>\\cloud\remote</code> and map it to an automatically assigned
+drive:</p>
 <pre><code>rclone mount remote:path/to/files *
 rclone mount remote:path/to/files X:
 rclone mount remote:path/to/files C:\path\parent\mount
 rclone mount remote:path/to/files \\cloud\remote</code></pre>
-<p>When the program ends while in foreground mode, either via Ctrl+C or receiving a SIGINT or SIGTERM signal, the mount should be automatically stopped.</p>
-<p>When running in background mode the user will have to stop the mount manually:</p>
+<p>When the program ends while in foreground mode, either via Ctrl+C or
+receiving a SIGINT or SIGTERM signal, the mount should be automatically
+stopped.</p>
+<p>When running in background mode the user will have to stop the mount
+manually:</p>
 <pre><code># Linux
 fusermount -u /path/to/local/mount
 #... or on some systems
 fusermount3 -u /path/to/local/mount
 # OS X or Linux when using nfsmount
 umount /path/to/local/mount</code></pre>
-<p>The umount operation can fail, for example when the mountpoint is busy. When that happens, it is the user's responsibility to stop the mount manually.</p>
-<p>The size of the mounted file system will be set according to information retrieved from the remote, the same as returned by the <a href="https://rclone.org/commands/rclone_about/">rclone about</a> command. Remotes with unlimited storage may report the used size only, then an additional 1 PiB of free space is assumed. If the remote does not <a href="https://rclone.org/overview/#optional-features">support</a> the about feature at all, then 1 PiB is set as both the total and the free size.</p>
+<p>The umount operation can fail, for example when the mountpoint is
+busy. When that happens, it is the user's responsibility to stop the
+mount manually.</p>
+<p>The size of the mounted file system will be set according to
+information retrieved from the remote, the same as returned by the <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a>
+command. Remotes with unlimited storage may report the used size only,
+then an additional 1 PiB of free space is assumed. If the remote does
+not <a href="https://rclone.org/overview/#optional-features">support</a>
+the about feature at all, then 1 PiB is set as both the total and the
+free size.</p>
 <h2 id="installing-on-windows">Installing on Windows</h2>
-<p>To run rclone mount on Windows, you will need to download and install <a href="http://www.secfs.net/winfsp/">WinFsp</a>.</p>
-<p><a href="https://github.com/winfsp/winfsp">WinFsp</a> is an open-source Windows File System Proxy which makes it easy to write user space file systems for Windows. It provides a FUSE emulation layer which rclone uses combination with <a href="https://github.com/winfsp/cgofuse">cgofuse</a>. Both of these packages are by Bill Zissimopoulos who was very helpful during the implementation of rclone mount for Windows.</p>
+<p>To run rclone mount on Windows, you will need to download and install
+<a href="http://www.secfs.net/winfsp/">WinFsp</a>.</p>
+<p><a href="https://github.com/winfsp/winfsp">WinFsp</a> is an
+open-source Windows File System Proxy which makes it easy to write user
+space file systems for Windows. It provides a FUSE emulation layer which
+rclone uses combination with <a
+href="https://github.com/winfsp/cgofuse">cgofuse</a>. Both of these
+packages are by Bill Zissimopoulos who was very helpful during the
+implementation of rclone mount for Windows.</p>
 <h3 id="mounting-modes-on-windows">Mounting modes on windows</h3>
-<p>Unlike other operating systems, Microsoft Windows provides a different filesystem type for network and fixed drives. It optimises access on the assumption fixed disk drives are fast and reliable, while network drives have relatively high latency and less reliability. Some settings can also be differentiated between the two types, for example that Windows Explorer should just display icons and not create preview thumbnails for image and video files on network drives.</p>
-<p>In most cases, rclone will mount the remote as a normal, fixed disk drive by default. However, you can also choose to mount it as a remote network drive, often described as a network share. If you mount an rclone remote using the default, fixed drive mode and experience unexpected program errors, freezes or other issues, consider mounting as a network drive instead.</p>
-<p>When mounting as a fixed disk drive you can either mount to an unused drive letter, or to a path representing a <strong>nonexistent</strong> subdirectory of an <strong>existing</strong> parent directory or drive. Using the special value <code>*</code> will tell rclone to automatically assign the next available drive letter, starting with Z: and moving backward. Examples:</p>
+<p>Unlike other operating systems, Microsoft Windows provides a
+different filesystem type for network and fixed drives. It optimises
+access on the assumption fixed disk drives are fast and reliable, while
+network drives have relatively high latency and less reliability. Some
+settings can also be differentiated between the two types, for example
+that Windows Explorer should just display icons and not create preview
+thumbnails for image and video files on network drives.</p>
+<p>In most cases, rclone will mount the remote as a normal, fixed disk
+drive by default. However, you can also choose to mount it as a remote
+network drive, often described as a network share. If you mount an
+rclone remote using the default, fixed drive mode and experience
+unexpected program errors, freezes or other issues, consider mounting as
+a network drive instead.</p>
+<p>When mounting as a fixed disk drive you can either mount to an unused
+drive letter, or to a path representing a <strong>nonexistent</strong>
+subdirectory of an <strong>existing</strong> parent directory or drive.
+Using the special value <code>*</code> will tell rclone to automatically
+assign the next available drive letter, starting with Z: and moving
+backward. Examples:</p>
 <pre><code>rclone mount remote:path/to/files *
 rclone mount remote:path/to/files X:
 rclone mount remote:path/to/files C:\path\parent\mount
 rclone mount remote:path/to/files X:</code></pre>
-<p>Option <code>--volname</code> can be used to set a custom volume name for the mounted file system. The default is to use the remote name and path.</p>
-<p>To mount as network drive, you can add option <code>--network-mode</code> to your mount command. Mounting to a directory path is not supported in this mode, it is a limitation Windows imposes on junctions, so the remote must always be mounted to a drive letter.</p>
+<p>Option <code>--volname</code> can be used to set a custom volume name
+for the mounted file system. The default is to use the remote name and
+path.</p>
+<p>To mount as network drive, you can add option
+<code>--network-mode</code> to your mount command. Mounting to a
+directory path is not supported in this mode, it is a limitation Windows
+imposes on junctions, so the remote must always be mounted to a drive
+letter.</p>
 <pre><code>rclone mount remote:path/to/files X: --network-mode</code></pre>
-<p>A volume name specified with <code>--volname</code> will be used to create the network share path. A complete UNC path, such as <code>\\cloud\remote</code>, optionally with path <code>\\cloud\remote\madeup\path</code>, will be used as is. Any other string will be used as the share part, after a default prefix <code>\\server\</code>. If no volume name is specified then <code>\\server\share</code> will be used. You must make sure the volume name is unique when you are mounting more than one drive, or else the mount command will fail. The share name will treated as the volume label for the mapped drive, shown in Windows Explorer etc, while the complete <code>\\server\share</code> will be reported as the remote UNC path by <code>net use</code> etc, just like a normal network drive mapping.</p>
-<p>If you specify a full network share UNC path with <code>--volname</code>, this will implicitly set the <code>--network-mode</code> option, so the following two examples have same result:</p>
+<p>A volume name specified with <code>--volname</code> will be used to
+create the network share path. A complete UNC path, such as
+<code>\\cloud\remote</code>, optionally with path
+<code>\\cloud\remote\madeup\path</code>, will be used as is. Any other
+string will be used as the share part, after a default prefix
+<code>\\server\</code>. If no volume name is specified then
+<code>\\server\share</code> will be used. You must make sure the volume
+name is unique when you are mounting more than one drive, or else the
+mount command will fail. The share name will treated as the volume label
+for the mapped drive, shown in Windows Explorer etc, while the complete
+<code>\\server\share</code> will be reported as the remote UNC path by
+<code>net use</code> etc, just like a normal network drive mapping.</p>
+<p>If you specify a full network share UNC path with
+<code>--volname</code>, this will implicitly set the
+<code>--network-mode</code> option, so the following two examples have
+same result:</p>
 <pre><code>rclone mount remote:path/to/files X: --network-mode
 rclone mount remote:path/to/files X: --volname \\server\share</code></pre>
-<p>You may also specify the network share UNC path as the mountpoint itself. Then rclone will automatically assign a drive letter, same as with <code>*</code> and use that as mountpoint, and instead use the UNC path specified as the volume name, as if it were specified with the <code>--volname</code> option. This will also implicitly set the <code>--network-mode</code> option. This means the following two examples have same result:</p>
+<p>You may also specify the network share UNC path as the mountpoint
+itself. Then rclone will automatically assign a drive letter, same as
+with <code>*</code> and use that as mountpoint, and instead use the UNC
+path specified as the volume name, as if it were specified with the
+<code>--volname</code> option. This will also implicitly set the
+<code>--network-mode</code> option. This means the following two
+examples have same result:</p>
 <pre><code>rclone mount remote:path/to/files \\cloud\remote
 rclone mount remote:path/to/files * --volname \\cloud\remote</code></pre>
-<p>There is yet another way to enable network mode, and to set the share path, and that is to pass the "native" libfuse/WinFsp option directly: <code>--fuse-flag --VolumePrefix=\server\share</code>. Note that the path must be with just a single backslash prefix in this case.</p>
-<p><em>Note:</em> In previous versions of rclone this was the only supported method.</p>
-<p><a href="https://en.wikipedia.org/wiki/Drive_mapping">Read more about drive mapping</a></p>
+<p>There is yet another way to enable network mode, and to set the share
+path, and that is to pass the "native" libfuse/WinFsp option directly:
+<code>--fuse-flag --VolumePrefix=\server\share</code>. Note that the
+path must be with just a single backslash prefix in this case.</p>
+<p><em>Note:</em> In previous versions of rclone this was the only
+supported method.</p>
+<p><a href="https://en.wikipedia.org/wiki/Drive_mapping">Read more about
+drive mapping</a></p>
 <p>See also <a href="#limitations">Limitations</a> section below.</p>
-<h3 id="windows-filesystem-permissions">Windows filesystem permissions</h3>
-<p>The FUSE emulation layer on Windows must convert between the POSIX-based permission model used in FUSE, and the permission model used in Windows, based on access-control lists (ACL).</p>
-<p>The mounted filesystem will normally get three entries in its access-control list (ACL), representing permissions for the POSIX permission scopes: Owner, group and others. By default, the owner and group will be taken from the current user, and the built-in group "Everyone" will be used to represent others. The user/group can be customized with FUSE options "UserName" and "GroupName", e.g. <code>-o UserName=user123 -o GroupName="Authenticated Users"</code>. The permissions on each entry will be set according to <a href="#options">options</a> <code>--dir-perms</code> and <code>--file-perms</code>, which takes a value in traditional Unix <a href="https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation">numeric notation</a>.</p>
-<p>The default permissions corresponds to <code>--file-perms 0666 --dir-perms 0777</code>, i.e. read and write permissions to everyone. This means you will not be able to start any programs from the mount. To be able to do that you must add execute permissions, e.g. <code>--file-perms 0777 --dir-perms 0777</code> to add it to everyone. If the program needs to write files, chances are you will have to enable <a href="#vfs-file-caching">VFS File Caching</a> as well (see also <a href="#limitations">limitations</a>). Note that the default write permission have some restrictions for accounts other than the owner, specifically it lacks the "write extended attributes", as explained next.</p>
-<p>The mapping of permissions is not always trivial, and the result you see in Windows Explorer may not be exactly like you expected. For example, when setting a value that includes write access for the group or others scope, this will be mapped to individual permissions "write attributes", "write data" and "append data", but not "write extended attributes". Windows will then show this as basic permission "Special" instead of "Write", because "Write" also covers the "write extended attributes" permission. When setting digit 0 for group or others, to indicate no permissions, they will still get individual permissions "read attributes", "read extended attributes" and "read permissions". This is done for compatibility reasons, e.g. to allow users without additional permissions to be able to read basic metadata about files like in Unix.</p>
-<p>WinFsp 2021 (version 1.9) introduced a new FUSE option "FileSecurity", that allows the complete specification of file security descriptors using <a href="https://docs.microsoft.com/en-us/windows/win32/secauthz/security-descriptor-string-format">SDDL</a>. With this you get detailed control of the resulting permissions, compared to use of the POSIX permissions described above, and no additional permissions will be added automatically for compatibility with Unix. Some example use cases will following.</p>
-<p>If you set POSIX permissions for only allowing access to the owner, using <code>--file-perms 0600 --dir-perms 0700</code>, the user group and the built-in "Everyone" group will still be given some special permissions, as described above. Some programs may then (incorrectly) interpret this as the file being accessible by everyone, for example an SSH client may warn about "unprotected private key file". You can work around this by specifying <code>-o FileSecurity="D:P(A;;FA;;;OW)"</code>, which sets file all access (FA) to the owner (OW), and nothing else.</p>
-<p>When setting write permissions then, except for the owner, this does not include the "write extended attributes" permission, as mentioned above. This may prevent applications from writing to files, giving permission denied error instead. To set working write permissions for the built-in "Everyone" group, similar to what it gets by default but with the addition of the "write extended attributes", you can specify <code>-o FileSecurity="D:P(A;;FRFW;;;WD)"</code>, which sets file read (FR) and file write (FW) to everyone (WD). If file execute (FX) is also needed, then change to <code>-o FileSecurity="D:P(A;;FRFWFX;;;WD)"</code>, or set file all access (FA) to get full access permissions, including delete, with <code>-o FileSecurity="D:P(A;;FA;;;WD)"</code>.</p>
+<h3 id="windows-filesystem-permissions">Windows filesystem
+permissions</h3>
+<p>The FUSE emulation layer on Windows must convert between the
+POSIX-based permission model used in FUSE, and the permission model used
+in Windows, based on access-control lists (ACL).</p>
+<p>The mounted filesystem will normally get three entries in its
+access-control list (ACL), representing permissions for the POSIX
+permission scopes: Owner, group and others. By default, the owner and
+group will be taken from the current user, and the built-in group
+"Everyone" will be used to represent others. The user/group can be
+customized with FUSE options "UserName" and "GroupName", e.g.
+<code>-o UserName=user123 -o GroupName="Authenticated Users"</code>. The
+permissions on each entry will be set according to <a
+href="#options">options</a> <code>--dir-perms</code> and
+<code>--file-perms</code>, which takes a value in traditional Unix <a
+href="https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation">numeric
+notation</a>.</p>
+<p>The default permissions corresponds to
+<code>--file-perms 0666 --dir-perms 0777</code>, i.e. read and write
+permissions to everyone. This means you will not be able to start any
+programs from the mount. To be able to do that you must add execute
+permissions, e.g. <code>--file-perms 0777 --dir-perms 0777</code> to add
+it to everyone. If the program needs to write files, chances are you
+will have to enable <a href="#vfs-file-caching">VFS File Caching</a> as
+well (see also <a href="#limitations">limitations</a>). Note that the
+default write permission have some restrictions for accounts other than
+the owner, specifically it lacks the "write extended attributes", as
+explained next.</p>
+<p>The mapping of permissions is not always trivial, and the result you
+see in Windows Explorer may not be exactly like you expected. For
+example, when setting a value that includes write access for the group
+or others scope, this will be mapped to individual permissions "write
+attributes", "write data" and "append data", but not "write extended
+attributes". Windows will then show this as basic permission "Special"
+instead of "Write", because "Write" also covers the "write extended
+attributes" permission. When setting digit 0 for group or others, to
+indicate no permissions, they will still get individual permissions
+"read attributes", "read extended attributes" and "read permissions".
+This is done for compatibility reasons, e.g. to allow users without
+additional permissions to be able to read basic metadata about files
+like in Unix.</p>
+<p>WinFsp 2021 (version 1.9) introduced a new FUSE option
+"FileSecurity", that allows the complete specification of file security
+descriptors using <a
+href="https://docs.microsoft.com/en-us/windows/win32/secauthz/security-descriptor-string-format">SDDL</a>.
+With this you get detailed control of the resulting permissions,
+compared to use of the POSIX permissions described above, and no
+additional permissions will be added automatically for compatibility
+with Unix. Some example use cases will following.</p>
+<p>If you set POSIX permissions for only allowing access to the owner,
+using <code>--file-perms 0600 --dir-perms 0700</code>, the user group
+and the built-in "Everyone" group will still be given some special
+permissions, as described above. Some programs may then (incorrectly)
+interpret this as the file being accessible by everyone, for example an
+SSH client may warn about "unprotected private key file". You can work
+around this by specifying
+<code>-o FileSecurity="D:P(A;;FA;;;OW)"</code>, which sets file all
+access (FA) to the owner (OW), and nothing else.</p>
+<p>When setting write permissions then, except for the owner, this does
+not include the "write extended attributes" permission, as mentioned
+above. This may prevent applications from writing to files, giving
+permission denied error instead. To set working write permissions for
+the built-in "Everyone" group, similar to what it gets by default but
+with the addition of the "write extended attributes", you can specify
+<code>-o FileSecurity="D:P(A;;FRFW;;;WD)"</code>, which sets file read
+(FR) and file write (FW) to everyone (WD). If file execute (FX) is also
+needed, then change to
+<code>-o FileSecurity="D:P(A;;FRFWFX;;;WD)"</code>, or set file all
+access (FA) to get full access permissions, including delete, with
+<code>-o FileSecurity="D:P(A;;FA;;;WD)"</code>.</p>
 <h3 id="windows-caveats">Windows caveats</h3>
-<p>Drives created as Administrator are not visible to other accounts, not even an account that was elevated to Administrator with the User Account Control (UAC) feature. A result of this is that if you mount to a drive letter from a Command Prompt run as Administrator, and then try to access the same drive from Windows Explorer (which does not run as Administrator), you will not be able to see the mounted drive.</p>
-<p>If you don't need to access the drive from applications running with administrative privileges, the easiest way around this is to always create the mount from a non-elevated command prompt.</p>
-<p>To make mapped drives available to the user account that created them regardless if elevated or not, there is a special Windows setting called <a href="https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command#detail-to-configure-the-enablelinkedconnections-registry-entry">linked connections</a> that can be enabled.</p>
-<p>It is also possible to make a drive mount available to everyone on the system, by running the process creating it as the built-in SYSTEM account. There are several ways to do this: One is to use the command-line utility <a href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a>, from Microsoft's Sysinternals suite, which has option <code>-s</code> to start processes as the SYSTEM account. Another alternative is to run the mount command from a Windows Scheduled Task, or a Windows Service, configured to run as the SYSTEM account. A third alternative is to use the <a href="https://github.com/winfsp/winfsp/wiki/WinFsp-Service-Architecture">WinFsp.Launcher infrastructure</a>). Read more in the <a href="https://rclone.org/install/">install documentation</a>. Note that when running rclone as another user, it will not use the configuration file from your profile unless you tell it to with the <a href="https://rclone.org/docs/#config-config-file"><code>--config</code></a> option. Note also that it is now the SYSTEM account that will have the owner permissions, and other accounts will have permissions according to the group or others scopes. As mentioned above, these will then not get the "write extended attributes" permission, and this may prevent writing to files. You can work around this with the FileSecurity option, see example above.</p>
-<p>Note that mapping to a directory path, instead of a drive letter, does not suffer from the same limitations.</p>
+<p>Drives created as Administrator are not visible to other accounts,
+not even an account that was elevated to Administrator with the User
+Account Control (UAC) feature. A result of this is that if you mount to
+a drive letter from a Command Prompt run as Administrator, and then try
+to access the same drive from Windows Explorer (which does not run as
+Administrator), you will not be able to see the mounted drive.</p>
+<p>If you don't need to access the drive from applications running with
+administrative privileges, the easiest way around this is to always
+create the mount from a non-elevated command prompt.</p>
+<p>To make mapped drives available to the user account that created them
+regardless if elevated or not, there is a special Windows setting called
+<a
+href="https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command#detail-to-configure-the-enablelinkedconnections-registry-entry">linked
+connections</a> that can be enabled.</p>
+<p>It is also possible to make a drive mount available to everyone on
+the system, by running the process creating it as the built-in SYSTEM
+account. There are several ways to do this: One is to use the
+command-line utility <a
+href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a>,
+from Microsoft's Sysinternals suite, which has option <code>-s</code> to
+start processes as the SYSTEM account. Another alternative is to run the
+mount command from a Windows Scheduled Task, or a Windows Service,
+configured to run as the SYSTEM account. A third alternative is to use
+the <a
+href="https://github.com/winfsp/winfsp/wiki/WinFsp-Service-Architecture">WinFsp.Launcher
+infrastructure</a>). Read more in the <a
+href="https://rclone.org/install/">install documentation</a>. Note that
+when running rclone as another user, it will not use the configuration
+file from your profile unless you tell it to with the <a
+href="https://rclone.org/docs/#config-config-file"><code>--config</code></a>
+option. Note also that it is now the SYSTEM account that will have the
+owner permissions, and other accounts will have permissions according to
+the group or others scopes. As mentioned above, these will then not get
+the "write extended attributes" permission, and this may prevent writing
+to files. You can work around this with the FileSecurity option, see
+example above.</p>
+<p>Note that mapping to a directory path, instead of a drive letter,
+does not suffer from the same limitations.</p>
 <h2 id="mounting-on-macos">Mounting on macOS</h2>
-<p>Mounting on macOS can be done either via <a href="https://rclone.org/commands/rclone_serve_nfs/">built-in NFS server</a>, <a href="https://osxfuse.github.io/">macFUSE</a> (also known as osxfuse) or <a href="https://www.fuse-t.org/">FUSE-T</a>. macFUSE is a traditional FUSE driver utilizing a macOS kernel extension (kext). FUSE-T is an alternative FUSE system which "mounts" via an NFSv4 local server.</p>
+<p>Mounting on macOS can be done either via <a
+href="https://rclone.org/commands/rclone_serve_nfs/">built-in NFS
+server</a>, <a href="https://osxfuse.github.io/">macFUSE</a> (also known
+as osxfuse) or <a href="https://www.fuse-t.org/">FUSE-T</a>. macFUSE is
+a traditional FUSE driver utilizing a macOS kernel extension (kext).
+FUSE-T is an alternative FUSE system which "mounts" via an NFSv4 local
+server.</p>
 <h4 id="unicode-normalization">Unicode Normalization</h4>
-<p>It is highly recommended to keep the default of <code>--no-unicode-normalization=false</code> for all <code>mount</code> and <code>serve</code> commands on macOS. For details, see <a href="https://rclone.org/commands/rclone_mount/#vfs-case-sensitivity">vfs-case-sensitivity</a>.</p>
+<p>It is highly recommended to keep the default of
+<code>--no-unicode-normalization=false</code> for all <code>mount</code>
+and <code>serve</code> commands on macOS. For details, see <a
+href="https://rclone.org/commands/rclone_mount/#vfs-case-sensitivity">vfs-case-sensitivity</a>.</p>
 <h3 id="nfs-mount">NFS mount</h3>
-<p>This method spins up an NFS server using <a href="https://rclone.org/commands/rclone_serve_nfs/">serve nfs</a> command and mounts it to the specified mountpoint. If you run this in background mode using |--daemon|, you will need to send SIGTERM signal to the rclone process using |kill| command to stop the mount.</p>
-<p>Note that <code>--nfs-cache-handle-limit</code> controls the maximum number of cached file handles stored by the <code>nfsmount</code> caching handler. This should not be set too low or you may experience errors when trying to access files. The default is 1000000, but consider lowering this limit if the server's system resource usage causes problems.</p>
+<p>This method spins up an NFS server using <a
+href="https://rclone.org/commands/rclone_serve_nfs/">serve nfs</a>
+command and mounts it to the specified mountpoint. If you run this in
+background mode using |--daemon|, you will need to send SIGTERM signal
+to the rclone process using |kill| command to stop the mount.</p>
+<p>Note that <code>--nfs-cache-handle-limit</code> controls the maximum
+number of cached file handles stored by the <code>nfsmount</code>
+caching handler. This should not be set too low or you may experience
+errors when trying to access files. The default is 1000000, but consider
+lowering this limit if the server's system resource usage causes
+problems.</p>
 <h3 id="macfuse-notes">macFUSE Notes</h3>
-<p>If installing macFUSE using <a href="https://github.com/osxfuse/osxfuse/releases">dmg packages</a> from the website, rclone will locate the macFUSE libraries without any further intervention. If however, macFUSE is installed using the <a href="https://www.macports.org/">macports</a> package manager, the following addition steps are required.</p>
+<p>If installing macFUSE using <a
+href="https://github.com/osxfuse/osxfuse/releases">dmg packages</a> from
+the website, rclone will locate the macFUSE libraries without any
+further intervention. If however, macFUSE is installed using the <a
+href="https://www.macports.org/">macports</a> package manager, the
+following addition steps are required.</p>
 <pre><code>sudo mkdir /usr/local/lib
 cd /usr/local/lib
 sudo ln -s /opt/local/lib/libfuse.2.dylib</code></pre>
-<h3 id="fuse-t-limitations-caveats-and-notes">FUSE-T Limitations, Caveats, and Notes</h3>
-<p>There are some limitations, caveats, and notes about how it works. These are current as of FUSE-T version 1.0.14.</p>
+<h3 id="fuse-t-limitations-caveats-and-notes">FUSE-T Limitations,
+Caveats, and Notes</h3>
+<p>There are some limitations, caveats, and notes about how it works.
+These are current as of FUSE-T version 1.0.14.</p>
 <h4 id="modtime-update-on-read">ModTime update on read</h4>
-<p>As per the <a href="https://github.com/macos-fuse-t/fuse-t/wiki#caveats">FUSE-T wiki</a>:</p>
+<p>As per the <a
+href="https://github.com/macos-fuse-t/fuse-t/wiki#caveats">FUSE-T
+wiki</a>:</p>
 <blockquote>
-<p>File access and modification times cannot be set separately as it seems to be an issue with the NFS client which always modifies both. Can be reproduced with 'touch -m' and 'touch -a' commands</p>
+<p>File access and modification times cannot be set separately as it
+seems to be an issue with the NFS client which always modifies both. Can
+be reproduced with 'touch -m' and 'touch -a' commands</p>
 </blockquote>
-<p>This means that viewing files with various tools, notably macOS Finder, will cause rlcone to update the modification time of the file. This may make rclone upload a full new copy of the file.</p>
+<p>This means that viewing files with various tools, notably macOS
+Finder, will cause rlcone to update the modification time of the file.
+This may make rclone upload a full new copy of the file.</p>
 <h4 id="read-only-mounts">Read Only mounts</h4>
-<p>When mounting with <code>--read-only</code>, attempts to write to files will fail <em>silently</em> as opposed to with a clear warning as in macFUSE.</p>
+<p>When mounting with <code>--read-only</code>, attempts to write to
+files will fail <em>silently</em> as opposed to with a clear warning as
+in macFUSE.</p>
 <h2 id="limitations">Limitations</h2>
-<p>Without the use of <code>--vfs-cache-mode</code> this can only write files sequentially, it can only seek when reading. This means that many applications won't work with their files on an rclone mount without <code>--vfs-cache-mode writes</code> or <code>--vfs-cache-mode full</code>. See the <a href="#vfs-file-caching">VFS File Caching</a> section for more info. When using NFS mount on macOS, if you don't specify |--vfs-cache-mode| the mount point will be read-only.</p>
-<p>The bucket-based remotes (e.g. Swift, S3, Google Compute Storage, B2) do not support the concept of empty directories, so empty directories will have a tendency to disappear once they fall out of the directory cache.</p>
-<p>When <code>rclone mount</code> is invoked on Unix with <code>--daemon</code> flag, the main rclone program will wait for the background mount to become ready or until the timeout specified by the <code>--daemon-wait</code> flag. On Linux it can check mount status using ProcFS so the flag in fact sets <strong>maximum</strong> time to wait, while the real wait can be less. On macOS / BSD the time to wait is constant and the check is performed only at the end. We advise you to set wait time on macOS reasonably.</p>
+<p>Without the use of <code>--vfs-cache-mode</code> this can only write
+files sequentially, it can only seek when reading. This means that many
+applications won't work with their files on an rclone mount without
+<code>--vfs-cache-mode writes</code> or
+<code>--vfs-cache-mode full</code>. See the <a
+href="#vfs-file-caching">VFS File Caching</a> section for more info.
+When using NFS mount on macOS, if you don't specify |--vfs-cache-mode|
+the mount point will be read-only.</p>
+<p>The bucket-based remotes (e.g. Swift, S3, Google Compute Storage, B2)
+do not support the concept of empty directories, so empty directories
+will have a tendency to disappear once they fall out of the directory
+cache.</p>
+<p>When <code>rclone mount</code> is invoked on Unix with
+<code>--daemon</code> flag, the main rclone program will wait for the
+background mount to become ready or until the timeout specified by the
+<code>--daemon-wait</code> flag. On Linux it can check mount status
+using ProcFS so the flag in fact sets <strong>maximum</strong> time to
+wait, while the real wait can be less. On macOS / BSD the time to wait
+is constant and the check is performed only at the end. We advise you to
+set wait time on macOS reasonably.</p>
 <p>Only supported on Linux, FreeBSD, OS X and Windows at the moment.</p>
-<h2 id="rclone-mount-vs-rclone-synccopy">rclone mount vs rclone sync/copy</h2>
-<p>File systems expect things to be 100% reliable, whereas cloud storage systems are a long way from 100% reliable. The rclone sync/copy commands cope with this with lots of retries. However rclone mount can't use retries in the same way without making local copies of the uploads. Look at the <a href="#vfs-file-caching">VFS File Caching</a> for solutions to make mount more reliable.</p>
+<h2 id="rclone-mount-vs-rclone-synccopy">rclone mount vs rclone
+sync/copy</h2>
+<p>File systems expect things to be 100% reliable, whereas cloud storage
+systems are a long way from 100% reliable. The rclone sync/copy commands
+cope with this with lots of retries. However rclone mount can't use
+retries in the same way without making local copies of the uploads. Look
+at the <a href="#vfs-file-caching">VFS File Caching</a> for solutions to
+make mount more reliable.</p>
 <h2 id="attribute-caching">Attribute caching</h2>
-<p>You can use the flag <code>--attr-timeout</code> to set the time the kernel caches the attributes (size, modification time, etc.) for directory entries.</p>
-<p>The default is <code>1s</code> which caches files just long enough to avoid too many callbacks to rclone from the kernel.</p>
-<p>In theory 0s should be the correct value for filesystems which can change outside the control of the kernel. However this causes quite a few problems such as <a href="https://github.com/rclone/rclone/issues/2157">rclone using too much memory</a>, <a href="https://forum.rclone.org/t/rclone-1-39-vs-1-40-mount-issue/5112">rclone not serving files to samba</a> and <a href="https://github.com/rclone/rclone/issues/2095#issuecomment-371141147">excessive time listing directories</a>.</p>
-<p>The kernel can cache the info about a file for the time given by <code>--attr-timeout</code>. You may see corruption if the remote file changes length during this window. It will show up as either a truncated file or a file with garbage on the end. With <code>--attr-timeout 1s</code> this is very unlikely but not impossible. The higher you set <code>--attr-timeout</code> the more likely it is. The default setting of "1s" is the lowest setting which mitigates the problems above.</p>
-<p>If you set it higher (<code>10s</code> or <code>1m</code> say) then the kernel will call back to rclone less often making it more efficient, however there is more chance of the corruption issue above.</p>
-<p>If files don't change on the remote outside of the control of rclone then there is no chance of corruption.</p>
-<p>This is the same as setting the attr_timeout option in mount.fuse.</p>
+<p>You can use the flag <code>--attr-timeout</code> to set the time the
+kernel caches the attributes (size, modification time, etc.) for
+directory entries.</p>
+<p>The default is <code>1s</code> which caches files just long enough to
+avoid too many callbacks to rclone from the kernel.</p>
+<p>In theory 0s should be the correct value for filesystems which can
+change outside the control of the kernel. However this causes quite a
+few problems such as <a
+href="https://github.com/rclone/rclone/issues/2157">rclone using too
+much memory</a>, <a
+href="https://forum.rclone.org/t/rclone-1-39-vs-1-40-mount-issue/5112">rclone
+not serving files to samba</a> and <a
+href="https://github.com/rclone/rclone/issues/2095#issuecomment-371141147">excessive
+time listing directories</a>.</p>
+<p>The kernel can cache the info about a file for the time given by
+<code>--attr-timeout</code>. You may see corruption if the remote file
+changes length during this window. It will show up as either a truncated
+file or a file with garbage on the end. With
+<code>--attr-timeout 1s</code> this is very unlikely but not impossible.
+The higher you set <code>--attr-timeout</code> the more likely it is.
+The default setting of "1s" is the lowest setting which mitigates the
+problems above.</p>
+<p>If you set it higher (<code>10s</code> or <code>1m</code> say) then
+the kernel will call back to rclone less often making it more efficient,
+however there is more chance of the corruption issue above.</p>
+<p>If files don't change on the remote outside of the control of rclone
+then there is no chance of corruption.</p>
+<p>This is the same as setting the attr_timeout option in
+mount.fuse.</p>
 <h2 id="filters">Filters</h2>
-<p>Note that all the rclone filters can be used to select a subset of the files to be visible in the mount.</p>
+<p>Note that all the rclone filters can be used to select a subset of
+the files to be visible in the mount.</p>
 <h2 id="systemd">systemd</h2>
-<p>When running rclone mount as a systemd service, it is possible to use Type=notify. In this case the service will enter the started state after the mountpoint has been successfully set up. Units having the rclone mount service specified as a requirement will see all files and folders immediately in this mode.</p>
-<p>Note that systemd runs mount units without any environment variables including <code>PATH</code> or <code>HOME</code>. This means that tilde (<code>~</code>) expansion will not work and you should provide <code>--config</code> and <code>--cache-dir</code> explicitly as absolute paths via rclone arguments. Since mounting requires the <code>fusermount</code> or <code>fusermount3</code> program, rclone will use the fallback PATH of <code>/bin:/usr/bin</code> in this scenario. Please ensure that <code>fusermount</code>/<code>fusermount3</code> is present on this PATH.</p>
+<p>When running rclone mount as a systemd service, it is possible to use
+Type=notify. In this case the service will enter the started state after
+the mountpoint has been successfully set up. Units having the rclone
+mount service specified as a requirement will see all files and folders
+immediately in this mode.</p>
+<p>Note that systemd runs mount units without any environment variables
+including <code>PATH</code> or <code>HOME</code>. This means that tilde
+(<code>~</code>) expansion will not work and you should provide
+<code>--config</code> and <code>--cache-dir</code> explicitly as
+absolute paths via rclone arguments. Since mounting requires the
+<code>fusermount</code> or <code>fusermount3</code> program, rclone will
+use the fallback PATH of <code>/bin:/usr/bin</code> in this scenario.
+Please ensure that <code>fusermount</code>/<code>fusermount3</code> is
+present on this PATH.</p>
 <h2 id="rclone-as-unix-mount-helper">Rclone as Unix mount helper</h2>
-<p>The core Unix program <code>/bin/mount</code> normally takes the <code>-t FSTYPE</code> argument then runs the <code>/sbin/mount.FSTYPE</code> helper program passing it mount options as <code>-o key=val,...</code> or <code>--opt=...</code>. Automount (classic or systemd) behaves in a similar way.</p>
-<p>rclone by default expects GNU-style flags <code>--key val</code>. To run it as a mount helper you should symlink rclone binary to <code>/sbin/mount.rclone</code> and optionally <code>/usr/bin/rclonefs</code>, e.g. <code>ln -s /usr/bin/rclone /sbin/mount.rclone</code>. rclone will detect it and translate command-line arguments appropriately.</p>
+<p>The core Unix program <code>/bin/mount</code> normally takes the
+<code>-t FSTYPE</code> argument then runs the
+<code>/sbin/mount.FSTYPE</code> helper program passing it mount options
+as <code>-o key=val,...</code> or <code>--opt=...</code>. Automount
+(classic or systemd) behaves in a similar way.</p>
+<p>rclone by default expects GNU-style flags <code>--key val</code>. To
+run it as a mount helper you should symlink rclone binary to
+<code>/sbin/mount.rclone</code> and optionally
+<code>/usr/bin/rclonefs</code>, e.g.
+<code>ln -s /usr/bin/rclone /sbin/mount.rclone</code>. rclone will
+detect it and translate command-line arguments appropriately.</p>
 <p>Now you can run classic mounts like this:</p>
 <pre><code>mount sftp1:subdir /mnt/data -t rclone -o vfs_cache_mode=writes,sftp_key_file=/path/to/pem</code></pre>
 <p>or create systemd mount units:</p>
@@ -3076,40 +4776,87 @@ TimeoutIdleSec=600
 WantedBy=multi-user.target</code></pre>
 <p>or add in <code>/etc/fstab</code> a line like</p>
 <pre><code>sftp1:subdir /mnt/data rclone rw,noauto,nofail,_netdev,x-systemd.automount,args2env,vfs_cache_mode=writes,config=/etc/rclone.conf,cache_dir=/var/cache/rclone 0 0</code></pre>
-<p>or use classic Automountd. Remember to provide explicit <code>config=...,cache-dir=...</code> as a workaround for mount units being run without <code>HOME</code>.</p>
-<p>Rclone in the mount helper mode will split <code>-o</code> argument(s) by comma, replace <code>_</code> by <code>-</code> and prepend <code>--</code> to get the command-line flags. Options containing commas or spaces can be wrapped in single or double quotes. Any inner quotes inside outer quotes of the same type should be doubled.</p>
-<p>Mount option syntax includes a few extra options treated specially:</p>
+<p>or use classic Automountd. Remember to provide explicit
+<code>config=...,cache-dir=...</code> as a workaround for mount units
+being run without <code>HOME</code>.</p>
+<p>Rclone in the mount helper mode will split <code>-o</code>
+argument(s) by comma, replace <code>_</code> by <code>-</code> and
+prepend <code>--</code> to get the command-line flags. Options
+containing commas or spaces can be wrapped in single or double quotes.
+Any inner quotes inside outer quotes of the same type should be
+doubled.</p>
+<p>Mount option syntax includes a few extra options treated
+specially:</p>
 <ul>
-<li><code>env.NAME=VALUE</code> will set an environment variable for the mount process. This helps with Automountd and Systemd.mount which don't allow setting custom environment for mount helpers. Typically you will use <code>env.HTTPS_PROXY=proxy.host:3128</code> or <code>env.HOME=/root</code></li>
-<li><code>command=cmount</code> can be used to run <code>cmount</code> or any other rclone command rather than the default <code>mount</code>.</li>
-<li><code>args2env</code> will pass mount options to the mount helper running in background via environment variables instead of command line arguments. This allows to hide secrets from such commands as <code>ps</code> or <code>pgrep</code>.</li>
-<li><code>vv...</code> will be transformed into appropriate <code>--verbose=N</code></li>
-<li>standard mount options like <code>x-systemd.automount</code>, <code>_netdev</code>, <code>nosuid</code> and alike are intended only for Automountd and ignored by rclone.</li>
+<li><code>env.NAME=VALUE</code> will set an environment variable for the
+mount process. This helps with Automountd and Systemd.mount which don't
+allow setting custom environment for mount helpers. Typically you will
+use <code>env.HTTPS_PROXY=proxy.host:3128</code> or
+<code>env.HOME=/root</code></li>
+<li><code>command=cmount</code> can be used to run <code>cmount</code>
+or any other rclone command rather than the default
+<code>mount</code>.</li>
+<li><code>args2env</code> will pass mount options to the mount helper
+running in background via environment variables instead of command line
+arguments. This allows to hide secrets from such commands as
+<code>ps</code> or <code>pgrep</code>.</li>
+<li><code>vv...</code> will be transformed into appropriate
+<code>--verbose=N</code></li>
+<li>standard mount options like <code>x-systemd.automount</code>,
+<code>_netdev</code>, <code>nosuid</code> and alike are intended only
+for Automountd and ignored by rclone.</li>
 </ul>
 <h2 id="vfs---virtual-file-system">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -3117,26 +4864,59 @@ WantedBy=multi-user.target</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -3145,76 +4925,207 @@ WantedBy=multi-user.target</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3 id="vfs-read-chunk-streams-0"><code>--vfs-read-chunk-streams</code>
+== 0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-1"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-1"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <pre><code>rclone mount remote:path /path/to/mountpoint [flags]</code></pre>
 <h2 id="options-60">Options</h2>
 <pre><code>      --allow-non-empty                        Allow mounting over a non-empty directory (not supported on Windows)
@@ -3268,7 +5179,9 @@ WantedBy=multi-user.target</code></pre>
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)
       --volname string                         Set the volume name (supported on Windows and OSX only)
       --write-back-cache                       Makes kernel buffer writes before sending them to rclone (without this, writethrough caching is used) (not supported on Windows)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-19">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -3295,29 +5208,43 @@ WantedBy=multi-user.target</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-60">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-moveto">rclone moveto</h1>
 <p>Move file or directory from source to dest.</p>
 <h2 id="synopsis-53">Synopsis</h2>
-<p>If source:path is a file or directory then it moves it to a file or directory named dest:path.</p>
-<p>This can be used to rename files or upload single files to other than their existing name. If the source is a directory then it acts exactly like the <a href="https://rclone.org/commands/rclone_move/">move</a> command.</p>
+<p>If source:path is a file or directory then it moves it to a file or
+directory named dest:path.</p>
+<p>This can be used to rename files or upload single files to other than
+their existing name. If the source is a directory then it acts exactly
+like the <a href="https://rclone.org/commands/rclone_move/">move</a>
+command.</p>
 <p>So</p>
 <pre><code>rclone moveto src dst</code></pre>
-<p>where src and dst are rclone paths, either remote:path or /path/to/local or C:.</p>
+<p>where src and dst are rclone paths, either remote:path or
+/path/to/local or C:.</p>
 <p>This will:</p>
 <pre><code>if src is file
     move it to dst, overwriting an existing file if it exists
 if src is directory
     move it to dst, overwriting existing files if they exist
     see move command for full details</code></pre>
-<p>This doesn't transfer files that are identical on src and dst, testing by size and modification time or MD5SUM. src will be deleted on successful transfer.</p>
-<p><strong>Important</strong>: Since this can cause data loss, test first with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
-<p><strong>Note</strong>: Use the <code>-P</code>/<code>--progress</code> flag to view real-time transfer statistics.</p>
+<p>This doesn't transfer files that are identical on src and dst,
+testing by size and modification time or MD5SUM. src will be deleted on
+successful transfer.</p>
+<p><strong>Important</strong>: Since this can cause data loss, test
+first with the <code>--dry-run</code> or the
+<code>--interactive</code>/<code>-i</code> flag.</p>
+<p><strong>Note</strong>: Use the
+<code>-P</code>/<code>--progress</code> flag to view real-time transfer
+statistics.</p>
 <pre><code>rclone moveto source:path dest:path [flags]</code></pre>
 <h2 id="options-61">Options</h2>
 <pre><code>  -h, --help   help for moveto</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="copy-options-5">Copy Options</h3>
 <p>Flags for anything which can copy a file</p>
 <pre><code>      --check-first                                 Do all the checks before starting transfers
@@ -3387,14 +5314,21 @@ if src is directory
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-61">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-ncdu">rclone ncdu</h1>
 <p>Explore a remote with a text based user interface.</p>
 <h2 id="synopsis-54">Synopsis</h2>
-<p>This displays a text based user interface allowing the navigation of a remote. It is most useful for answering the question - "What is using all my disk space?".</p>
-<p>To make the user interface it first scans the entire remote given and builds an in memory representation. rclone ncdu can be used during this scanning phase and you will see it building up the directory structure as it goes along.</p>
-<p>You can interact with the user interface using key presses, press '?' to toggle the help on and off. The supported keys are:</p>
+<p>This displays a text based user interface allowing the navigation of
+a remote. It is most useful for answering the question - "What is using
+all my disk space?".</p>
+<p>To make the user interface it first scans the entire remote given and
+builds an in memory representation. rclone ncdu can be used during this
+scanning phase and you will see it building up the directory structure
+as it goes along.</p>
+<p>You can interact with the user interface using key presses, press '?'
+to toggle the help on and off. The supported keys are:</p>
 <pre><code> ↑,↓ or k,j to Move
  →,l to enter
  ←,h to return
@@ -3415,7 +5349,9 @@ if src is directory
  ? to toggle help on and off
  ESC to close the menu box
  q/^c to quit</code></pre>
-<p>Listed files/directories may be prefixed by a one-character flag, some of them combined with a description in brackets at end of line. These flags have the following meaning:</p>
+<p>Listed files/directories may be prefixed by a one-character flag,
+some of them combined with a description in brackets at end of line.
+These flags have the following meaning:</p>
 <pre><code>e means this is an empty directory, i.e. contains no files (but
   may contain empty subdirectories)
 ~ means this is a directory where some of the files (possibly in
@@ -3426,13 +5362,23 @@ if src is directory
   therefore the directory size may be underestimated (and average
   size inaccurate)
 ! means an error occurred while reading this directory</code></pre>
-<p>This an homage to the <a href="https://dev.yorhel.nl/ncdu">ncdu tool</a> but for rclone remotes. It is missing lots of features at the moment but is useful as it stands. Unlike ncdu it does not show excluded files.</p>
-<p>Note that it might take some time to delete big files/directories. The UI won't respond in the meantime since the deletion is done synchronously.</p>
-<p>For a non-interactive listing of the remote, see the <a href="https://rclone.org/commands/rclone_tree/">tree</a> command. To just get the total size of the remote you can also use the <a href="https://rclone.org/commands/rclone_size/">size</a> command.</p>
+<p>This an homage to the <a href="https://dev.yorhel.nl/ncdu">ncdu
+tool</a> but for rclone remotes. It is missing lots of features at the
+moment but is useful as it stands. Unlike ncdu it does not show excluded
+files.</p>
+<p>Note that it might take some time to delete big files/directories.
+The UI won't respond in the meantime since the deletion is done
+synchronously.</p>
+<p>For a non-interactive listing of the remote, see the <a
+href="https://rclone.org/commands/rclone_tree/">tree</a> command. To
+just get the total size of the remote you can also use the <a
+href="https://rclone.org/commands/rclone_size/">size</a> command.</p>
 <pre><code>rclone ncdu remote:path [flags]</code></pre>
 <h2 id="options-62">Options</h2>
 <pre><code>  -h, --help   help for ncdu</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-21">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -3463,117 +5409,400 @@ if src is directory
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-62">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-nfsmount">rclone nfsmount</h1>
 <p>Mount the remote as file system on a mountpoint.</p>
 <h2 id="synopsis-55">Synopsis</h2>
-<p>Rclone nfsmount allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
-<p>First set up your remote using <code>rclone config</code>. Check it works with <code>rclone ls</code> etc.</p>
-<p>On Linux and macOS, you can run mount in either foreground or background (aka daemon) mode. Mount runs in foreground mode by default. Use the <code>--daemon</code> flag to force background mode. On Windows you can run mount in foreground only, the flag is ignored.</p>
-<p>In background mode rclone acts as a generic Unix mount program: the main program starts, spawns background rclone process to setup and maintain the mount, waits until success or timeout and exits with appropriate code (killing the child process if it fails).</p>
-<p>On Linux/macOS/FreeBSD start the mount like this, where <code>/path/to/local/mount</code> is an <strong>empty</strong> <strong>existing</strong> directory:</p>
+<p>Rclone nfsmount allows Linux, FreeBSD, macOS and Windows to mount any
+of Rclone's cloud storage systems as a file system with FUSE.</p>
+<p>First set up your remote using <code>rclone config</code>. Check it
+works with <code>rclone ls</code> etc.</p>
+<p>On Linux and macOS, you can run mount in either foreground or
+background (aka daemon) mode. Mount runs in foreground mode by default.
+Use the <code>--daemon</code> flag to force background mode. On Windows
+you can run mount in foreground only, the flag is ignored.</p>
+<p>In background mode rclone acts as a generic Unix mount program: the
+main program starts, spawns background rclone process to setup and
+maintain the mount, waits until success or timeout and exits with
+appropriate code (killing the child process if it fails).</p>
+<p>On Linux/macOS/FreeBSD start the mount like this, where
+<code>/path/to/local/mount</code> is an <strong>empty</strong>
+<strong>existing</strong> directory:</p>
 <pre><code>rclone nfsmount remote:path/to/files /path/to/local/mount</code></pre>
-<p>On Windows you can start a mount in different ways. See <a href="#mounting-modes-on-windows">below</a> for details. If foreground mount is used interactively from a console window, rclone will serve the mount and occupy the console so another window should be used to work with the mount until rclone is interrupted e.g. by pressing Ctrl-C.</p>
-<p>The following examples will mount to an automatically assigned drive, to specific drive letter <code>X:</code>, to path <code>C:\path\parent\mount</code> (where parent directory or drive must exist, and mount must <strong>not</strong> exist, and is not supported when <a href="#mounting-modes-on-windows">mounting as a network drive</a>), and the last example will mount as network share <code>\\cloud\remote</code> and map it to an automatically assigned drive:</p>
+<p>On Windows you can start a mount in different ways. See <a
+href="#mounting-modes-on-windows">below</a> for details. If foreground
+mount is used interactively from a console window, rclone will serve the
+mount and occupy the console so another window should be used to work
+with the mount until rclone is interrupted e.g. by pressing Ctrl-C.</p>
+<p>The following examples will mount to an automatically assigned drive,
+to specific drive letter <code>X:</code>, to path
+<code>C:\path\parent\mount</code> (where parent directory or drive must
+exist, and mount must <strong>not</strong> exist, and is not supported
+when <a href="#mounting-modes-on-windows">mounting as a network
+drive</a>), and the last example will mount as network share
+<code>\\cloud\remote</code> and map it to an automatically assigned
+drive:</p>
 <pre><code>rclone nfsmount remote:path/to/files *
 rclone nfsmount remote:path/to/files X:
 rclone nfsmount remote:path/to/files C:\path\parent\mount
 rclone nfsmount remote:path/to/files \\cloud\remote</code></pre>
-<p>When the program ends while in foreground mode, either via Ctrl+C or receiving a SIGINT or SIGTERM signal, the mount should be automatically stopped.</p>
-<p>When running in background mode the user will have to stop the mount manually:</p>
+<p>When the program ends while in foreground mode, either via Ctrl+C or
+receiving a SIGINT or SIGTERM signal, the mount should be automatically
+stopped.</p>
+<p>When running in background mode the user will have to stop the mount
+manually:</p>
 <pre><code># Linux
 fusermount -u /path/to/local/mount
 #... or on some systems
 fusermount3 -u /path/to/local/mount
 # OS X or Linux when using nfsmount
 umount /path/to/local/mount</code></pre>
-<p>The umount operation can fail, for example when the mountpoint is busy. When that happens, it is the user's responsibility to stop the mount manually.</p>
-<p>The size of the mounted file system will be set according to information retrieved from the remote, the same as returned by the <a href="https://rclone.org/commands/rclone_about/">rclone about</a> command. Remotes with unlimited storage may report the used size only, then an additional 1 PiB of free space is assumed. If the remote does not <a href="https://rclone.org/overview/#optional-features">support</a> the about feature at all, then 1 PiB is set as both the total and the free size.</p>
+<p>The umount operation can fail, for example when the mountpoint is
+busy. When that happens, it is the user's responsibility to stop the
+mount manually.</p>
+<p>The size of the mounted file system will be set according to
+information retrieved from the remote, the same as returned by the <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a>
+command. Remotes with unlimited storage may report the used size only,
+then an additional 1 PiB of free space is assumed. If the remote does
+not <a href="https://rclone.org/overview/#optional-features">support</a>
+the about feature at all, then 1 PiB is set as both the total and the
+free size.</p>
 <h2 id="installing-on-windows-1">Installing on Windows</h2>
-<p>To run rclone nfsmount on Windows, you will need to download and install <a href="http://www.secfs.net/winfsp/">WinFsp</a>.</p>
-<p><a href="https://github.com/winfsp/winfsp">WinFsp</a> is an open-source Windows File System Proxy which makes it easy to write user space file systems for Windows. It provides a FUSE emulation layer which rclone uses combination with <a href="https://github.com/winfsp/cgofuse">cgofuse</a>. Both of these packages are by Bill Zissimopoulos who was very helpful during the implementation of rclone nfsmount for Windows.</p>
+<p>To run rclone nfsmount on Windows, you will need to download and
+install <a href="http://www.secfs.net/winfsp/">WinFsp</a>.</p>
+<p><a href="https://github.com/winfsp/winfsp">WinFsp</a> is an
+open-source Windows File System Proxy which makes it easy to write user
+space file systems for Windows. It provides a FUSE emulation layer which
+rclone uses combination with <a
+href="https://github.com/winfsp/cgofuse">cgofuse</a>. Both of these
+packages are by Bill Zissimopoulos who was very helpful during the
+implementation of rclone nfsmount for Windows.</p>
 <h3 id="mounting-modes-on-windows-1">Mounting modes on windows</h3>
-<p>Unlike other operating systems, Microsoft Windows provides a different filesystem type for network and fixed drives. It optimises access on the assumption fixed disk drives are fast and reliable, while network drives have relatively high latency and less reliability. Some settings can also be differentiated between the two types, for example that Windows Explorer should just display icons and not create preview thumbnails for image and video files on network drives.</p>
-<p>In most cases, rclone will mount the remote as a normal, fixed disk drive by default. However, you can also choose to mount it as a remote network drive, often described as a network share. If you mount an rclone remote using the default, fixed drive mode and experience unexpected program errors, freezes or other issues, consider mounting as a network drive instead.</p>
-<p>When mounting as a fixed disk drive you can either mount to an unused drive letter, or to a path representing a <strong>nonexistent</strong> subdirectory of an <strong>existing</strong> parent directory or drive. Using the special value <code>*</code> will tell rclone to automatically assign the next available drive letter, starting with Z: and moving backward. Examples:</p>
+<p>Unlike other operating systems, Microsoft Windows provides a
+different filesystem type for network and fixed drives. It optimises
+access on the assumption fixed disk drives are fast and reliable, while
+network drives have relatively high latency and less reliability. Some
+settings can also be differentiated between the two types, for example
+that Windows Explorer should just display icons and not create preview
+thumbnails for image and video files on network drives.</p>
+<p>In most cases, rclone will mount the remote as a normal, fixed disk
+drive by default. However, you can also choose to mount it as a remote
+network drive, often described as a network share. If you mount an
+rclone remote using the default, fixed drive mode and experience
+unexpected program errors, freezes or other issues, consider mounting as
+a network drive instead.</p>
+<p>When mounting as a fixed disk drive you can either mount to an unused
+drive letter, or to a path representing a <strong>nonexistent</strong>
+subdirectory of an <strong>existing</strong> parent directory or drive.
+Using the special value <code>*</code> will tell rclone to automatically
+assign the next available drive letter, starting with Z: and moving
+backward. Examples:</p>
 <pre><code>rclone nfsmount remote:path/to/files *
 rclone nfsmount remote:path/to/files X:
 rclone nfsmount remote:path/to/files C:\path\parent\mount
 rclone nfsmount remote:path/to/files X:</code></pre>
-<p>Option <code>--volname</code> can be used to set a custom volume name for the mounted file system. The default is to use the remote name and path.</p>
-<p>To mount as network drive, you can add option <code>--network-mode</code> to your nfsmount command. Mounting to a directory path is not supported in this mode, it is a limitation Windows imposes on junctions, so the remote must always be mounted to a drive letter.</p>
+<p>Option <code>--volname</code> can be used to set a custom volume name
+for the mounted file system. The default is to use the remote name and
+path.</p>
+<p>To mount as network drive, you can add option
+<code>--network-mode</code> to your nfsmount command. Mounting to a
+directory path is not supported in this mode, it is a limitation Windows
+imposes on junctions, so the remote must always be mounted to a drive
+letter.</p>
 <pre><code>rclone nfsmount remote:path/to/files X: --network-mode</code></pre>
-<p>A volume name specified with <code>--volname</code> will be used to create the network share path. A complete UNC path, such as <code>\\cloud\remote</code>, optionally with path <code>\\cloud\remote\madeup\path</code>, will be used as is. Any other string will be used as the share part, after a default prefix <code>\\server\</code>. If no volume name is specified then <code>\\server\share</code> will be used. You must make sure the volume name is unique when you are mounting more than one drive, or else the mount command will fail. The share name will treated as the volume label for the mapped drive, shown in Windows Explorer etc, while the complete <code>\\server\share</code> will be reported as the remote UNC path by <code>net use</code> etc, just like a normal network drive mapping.</p>
-<p>If you specify a full network share UNC path with <code>--volname</code>, this will implicitly set the <code>--network-mode</code> option, so the following two examples have same result:</p>
+<p>A volume name specified with <code>--volname</code> will be used to
+create the network share path. A complete UNC path, such as
+<code>\\cloud\remote</code>, optionally with path
+<code>\\cloud\remote\madeup\path</code>, will be used as is. Any other
+string will be used as the share part, after a default prefix
+<code>\\server\</code>. If no volume name is specified then
+<code>\\server\share</code> will be used. You must make sure the volume
+name is unique when you are mounting more than one drive, or else the
+mount command will fail. The share name will treated as the volume label
+for the mapped drive, shown in Windows Explorer etc, while the complete
+<code>\\server\share</code> will be reported as the remote UNC path by
+<code>net use</code> etc, just like a normal network drive mapping.</p>
+<p>If you specify a full network share UNC path with
+<code>--volname</code>, this will implicitly set the
+<code>--network-mode</code> option, so the following two examples have
+same result:</p>
 <pre><code>rclone nfsmount remote:path/to/files X: --network-mode
 rclone nfsmount remote:path/to/files X: --volname \\server\share</code></pre>
-<p>You may also specify the network share UNC path as the mountpoint itself. Then rclone will automatically assign a drive letter, same as with <code>*</code> and use that as mountpoint, and instead use the UNC path specified as the volume name, as if it were specified with the <code>--volname</code> option. This will also implicitly set the <code>--network-mode</code> option. This means the following two examples have same result:</p>
+<p>You may also specify the network share UNC path as the mountpoint
+itself. Then rclone will automatically assign a drive letter, same as
+with <code>*</code> and use that as mountpoint, and instead use the UNC
+path specified as the volume name, as if it were specified with the
+<code>--volname</code> option. This will also implicitly set the
+<code>--network-mode</code> option. This means the following two
+examples have same result:</p>
 <pre><code>rclone nfsmount remote:path/to/files \\cloud\remote
 rclone nfsmount remote:path/to/files * --volname \\cloud\remote</code></pre>
-<p>There is yet another way to enable network mode, and to set the share path, and that is to pass the "native" libfuse/WinFsp option directly: <code>--fuse-flag --VolumePrefix=\server\share</code>. Note that the path must be with just a single backslash prefix in this case.</p>
-<p><em>Note:</em> In previous versions of rclone this was the only supported method.</p>
-<p><a href="https://en.wikipedia.org/wiki/Drive_mapping">Read more about drive mapping</a></p>
+<p>There is yet another way to enable network mode, and to set the share
+path, and that is to pass the "native" libfuse/WinFsp option directly:
+<code>--fuse-flag --VolumePrefix=\server\share</code>. Note that the
+path must be with just a single backslash prefix in this case.</p>
+<p><em>Note:</em> In previous versions of rclone this was the only
+supported method.</p>
+<p><a href="https://en.wikipedia.org/wiki/Drive_mapping">Read more about
+drive mapping</a></p>
 <p>See also <a href="#limitations">Limitations</a> section below.</p>
-<h3 id="windows-filesystem-permissions-1">Windows filesystem permissions</h3>
-<p>The FUSE emulation layer on Windows must convert between the POSIX-based permission model used in FUSE, and the permission model used in Windows, based on access-control lists (ACL).</p>
-<p>The mounted filesystem will normally get three entries in its access-control list (ACL), representing permissions for the POSIX permission scopes: Owner, group and others. By default, the owner and group will be taken from the current user, and the built-in group "Everyone" will be used to represent others. The user/group can be customized with FUSE options "UserName" and "GroupName", e.g. <code>-o UserName=user123 -o GroupName="Authenticated Users"</code>. The permissions on each entry will be set according to <a href="#options">options</a> <code>--dir-perms</code> and <code>--file-perms</code>, which takes a value in traditional Unix <a href="https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation">numeric notation</a>.</p>
-<p>The default permissions corresponds to <code>--file-perms 0666 --dir-perms 0777</code>, i.e. read and write permissions to everyone. This means you will not be able to start any programs from the mount. To be able to do that you must add execute permissions, e.g. <code>--file-perms 0777 --dir-perms 0777</code> to add it to everyone. If the program needs to write files, chances are you will have to enable <a href="#vfs-file-caching">VFS File Caching</a> as well (see also <a href="#limitations">limitations</a>). Note that the default write permission have some restrictions for accounts other than the owner, specifically it lacks the "write extended attributes", as explained next.</p>
-<p>The mapping of permissions is not always trivial, and the result you see in Windows Explorer may not be exactly like you expected. For example, when setting a value that includes write access for the group or others scope, this will be mapped to individual permissions "write attributes", "write data" and "append data", but not "write extended attributes". Windows will then show this as basic permission "Special" instead of "Write", because "Write" also covers the "write extended attributes" permission. When setting digit 0 for group or others, to indicate no permissions, they will still get individual permissions "read attributes", "read extended attributes" and "read permissions". This is done for compatibility reasons, e.g. to allow users without additional permissions to be able to read basic metadata about files like in Unix.</p>
-<p>WinFsp 2021 (version 1.9) introduced a new FUSE option "FileSecurity", that allows the complete specification of file security descriptors using <a href="https://docs.microsoft.com/en-us/windows/win32/secauthz/security-descriptor-string-format">SDDL</a>. With this you get detailed control of the resulting permissions, compared to use of the POSIX permissions described above, and no additional permissions will be added automatically for compatibility with Unix. Some example use cases will following.</p>
-<p>If you set POSIX permissions for only allowing access to the owner, using <code>--file-perms 0600 --dir-perms 0700</code>, the user group and the built-in "Everyone" group will still be given some special permissions, as described above. Some programs may then (incorrectly) interpret this as the file being accessible by everyone, for example an SSH client may warn about "unprotected private key file". You can work around this by specifying <code>-o FileSecurity="D:P(A;;FA;;;OW)"</code>, which sets file all access (FA) to the owner (OW), and nothing else.</p>
-<p>When setting write permissions then, except for the owner, this does not include the "write extended attributes" permission, as mentioned above. This may prevent applications from writing to files, giving permission denied error instead. To set working write permissions for the built-in "Everyone" group, similar to what it gets by default but with the addition of the "write extended attributes", you can specify <code>-o FileSecurity="D:P(A;;FRFW;;;WD)"</code>, which sets file read (FR) and file write (FW) to everyone (WD). If file execute (FX) is also needed, then change to <code>-o FileSecurity="D:P(A;;FRFWFX;;;WD)"</code>, or set file all access (FA) to get full access permissions, including delete, with <code>-o FileSecurity="D:P(A;;FA;;;WD)"</code>.</p>
+<h3 id="windows-filesystem-permissions-1">Windows filesystem
+permissions</h3>
+<p>The FUSE emulation layer on Windows must convert between the
+POSIX-based permission model used in FUSE, and the permission model used
+in Windows, based on access-control lists (ACL).</p>
+<p>The mounted filesystem will normally get three entries in its
+access-control list (ACL), representing permissions for the POSIX
+permission scopes: Owner, group and others. By default, the owner and
+group will be taken from the current user, and the built-in group
+"Everyone" will be used to represent others. The user/group can be
+customized with FUSE options "UserName" and "GroupName", e.g.
+<code>-o UserName=user123 -o GroupName="Authenticated Users"</code>. The
+permissions on each entry will be set according to <a
+href="#options">options</a> <code>--dir-perms</code> and
+<code>--file-perms</code>, which takes a value in traditional Unix <a
+href="https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation">numeric
+notation</a>.</p>
+<p>The default permissions corresponds to
+<code>--file-perms 0666 --dir-perms 0777</code>, i.e. read and write
+permissions to everyone. This means you will not be able to start any
+programs from the mount. To be able to do that you must add execute
+permissions, e.g. <code>--file-perms 0777 --dir-perms 0777</code> to add
+it to everyone. If the program needs to write files, chances are you
+will have to enable <a href="#vfs-file-caching">VFS File Caching</a> as
+well (see also <a href="#limitations">limitations</a>). Note that the
+default write permission have some restrictions for accounts other than
+the owner, specifically it lacks the "write extended attributes", as
+explained next.</p>
+<p>The mapping of permissions is not always trivial, and the result you
+see in Windows Explorer may not be exactly like you expected. For
+example, when setting a value that includes write access for the group
+or others scope, this will be mapped to individual permissions "write
+attributes", "write data" and "append data", but not "write extended
+attributes". Windows will then show this as basic permission "Special"
+instead of "Write", because "Write" also covers the "write extended
+attributes" permission. When setting digit 0 for group or others, to
+indicate no permissions, they will still get individual permissions
+"read attributes", "read extended attributes" and "read permissions".
+This is done for compatibility reasons, e.g. to allow users without
+additional permissions to be able to read basic metadata about files
+like in Unix.</p>
+<p>WinFsp 2021 (version 1.9) introduced a new FUSE option
+"FileSecurity", that allows the complete specification of file security
+descriptors using <a
+href="https://docs.microsoft.com/en-us/windows/win32/secauthz/security-descriptor-string-format">SDDL</a>.
+With this you get detailed control of the resulting permissions,
+compared to use of the POSIX permissions described above, and no
+additional permissions will be added automatically for compatibility
+with Unix. Some example use cases will following.</p>
+<p>If you set POSIX permissions for only allowing access to the owner,
+using <code>--file-perms 0600 --dir-perms 0700</code>, the user group
+and the built-in "Everyone" group will still be given some special
+permissions, as described above. Some programs may then (incorrectly)
+interpret this as the file being accessible by everyone, for example an
+SSH client may warn about "unprotected private key file". You can work
+around this by specifying
+<code>-o FileSecurity="D:P(A;;FA;;;OW)"</code>, which sets file all
+access (FA) to the owner (OW), and nothing else.</p>
+<p>When setting write permissions then, except for the owner, this does
+not include the "write extended attributes" permission, as mentioned
+above. This may prevent applications from writing to files, giving
+permission denied error instead. To set working write permissions for
+the built-in "Everyone" group, similar to what it gets by default but
+with the addition of the "write extended attributes", you can specify
+<code>-o FileSecurity="D:P(A;;FRFW;;;WD)"</code>, which sets file read
+(FR) and file write (FW) to everyone (WD). If file execute (FX) is also
+needed, then change to
+<code>-o FileSecurity="D:P(A;;FRFWFX;;;WD)"</code>, or set file all
+access (FA) to get full access permissions, including delete, with
+<code>-o FileSecurity="D:P(A;;FA;;;WD)"</code>.</p>
 <h3 id="windows-caveats-1">Windows caveats</h3>
-<p>Drives created as Administrator are not visible to other accounts, not even an account that was elevated to Administrator with the User Account Control (UAC) feature. A result of this is that if you mount to a drive letter from a Command Prompt run as Administrator, and then try to access the same drive from Windows Explorer (which does not run as Administrator), you will not be able to see the mounted drive.</p>
-<p>If you don't need to access the drive from applications running with administrative privileges, the easiest way around this is to always create the mount from a non-elevated command prompt.</p>
-<p>To make mapped drives available to the user account that created them regardless if elevated or not, there is a special Windows setting called <a href="https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command#detail-to-configure-the-enablelinkedconnections-registry-entry">linked connections</a> that can be enabled.</p>
-<p>It is also possible to make a drive mount available to everyone on the system, by running the process creating it as the built-in SYSTEM account. There are several ways to do this: One is to use the command-line utility <a href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a>, from Microsoft's Sysinternals suite, which has option <code>-s</code> to start processes as the SYSTEM account. Another alternative is to run the mount command from a Windows Scheduled Task, or a Windows Service, configured to run as the SYSTEM account. A third alternative is to use the <a href="https://github.com/winfsp/winfsp/wiki/WinFsp-Service-Architecture">WinFsp.Launcher infrastructure</a>). Read more in the <a href="https://rclone.org/install/">install documentation</a>. Note that when running rclone as another user, it will not use the configuration file from your profile unless you tell it to with the <a href="https://rclone.org/docs/#config-config-file"><code>--config</code></a> option. Note also that it is now the SYSTEM account that will have the owner permissions, and other accounts will have permissions according to the group or others scopes. As mentioned above, these will then not get the "write extended attributes" permission, and this may prevent writing to files. You can work around this with the FileSecurity option, see example above.</p>
-<p>Note that mapping to a directory path, instead of a drive letter, does not suffer from the same limitations.</p>
+<p>Drives created as Administrator are not visible to other accounts,
+not even an account that was elevated to Administrator with the User
+Account Control (UAC) feature. A result of this is that if you mount to
+a drive letter from a Command Prompt run as Administrator, and then try
+to access the same drive from Windows Explorer (which does not run as
+Administrator), you will not be able to see the mounted drive.</p>
+<p>If you don't need to access the drive from applications running with
+administrative privileges, the easiest way around this is to always
+create the mount from a non-elevated command prompt.</p>
+<p>To make mapped drives available to the user account that created them
+regardless if elevated or not, there is a special Windows setting called
+<a
+href="https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command#detail-to-configure-the-enablelinkedconnections-registry-entry">linked
+connections</a> that can be enabled.</p>
+<p>It is also possible to make a drive mount available to everyone on
+the system, by running the process creating it as the built-in SYSTEM
+account. There are several ways to do this: One is to use the
+command-line utility <a
+href="https://docs.microsoft.com/en-us/sysinternals/downloads/psexec">PsExec</a>,
+from Microsoft's Sysinternals suite, which has option <code>-s</code> to
+start processes as the SYSTEM account. Another alternative is to run the
+mount command from a Windows Scheduled Task, or a Windows Service,
+configured to run as the SYSTEM account. A third alternative is to use
+the <a
+href="https://github.com/winfsp/winfsp/wiki/WinFsp-Service-Architecture">WinFsp.Launcher
+infrastructure</a>). Read more in the <a
+href="https://rclone.org/install/">install documentation</a>. Note that
+when running rclone as another user, it will not use the configuration
+file from your profile unless you tell it to with the <a
+href="https://rclone.org/docs/#config-config-file"><code>--config</code></a>
+option. Note also that it is now the SYSTEM account that will have the
+owner permissions, and other accounts will have permissions according to
+the group or others scopes. As mentioned above, these will then not get
+the "write extended attributes" permission, and this may prevent writing
+to files. You can work around this with the FileSecurity option, see
+example above.</p>
+<p>Note that mapping to a directory path, instead of a drive letter,
+does not suffer from the same limitations.</p>
 <h2 id="mounting-on-macos-1">Mounting on macOS</h2>
-<p>Mounting on macOS can be done either via <a href="https://rclone.org/commands/rclone_serve_nfs/">built-in NFS server</a>, <a href="https://osxfuse.github.io/">macFUSE</a> (also known as osxfuse) or <a href="https://www.fuse-t.org/">FUSE-T</a>. macFUSE is a traditional FUSE driver utilizing a macOS kernel extension (kext). FUSE-T is an alternative FUSE system which "mounts" via an NFSv4 local server.</p>
+<p>Mounting on macOS can be done either via <a
+href="https://rclone.org/commands/rclone_serve_nfs/">built-in NFS
+server</a>, <a href="https://osxfuse.github.io/">macFUSE</a> (also known
+as osxfuse) or <a href="https://www.fuse-t.org/">FUSE-T</a>. macFUSE is
+a traditional FUSE driver utilizing a macOS kernel extension (kext).
+FUSE-T is an alternative FUSE system which "mounts" via an NFSv4 local
+server.</p>
 <h4 id="unicode-normalization-1">Unicode Normalization</h4>
-<p>It is highly recommended to keep the default of <code>--no-unicode-normalization=false</code> for all <code>mount</code> and <code>serve</code> commands on macOS. For details, see <a href="https://rclone.org/commands/rclone_mount/#vfs-case-sensitivity">vfs-case-sensitivity</a>.</p>
+<p>It is highly recommended to keep the default of
+<code>--no-unicode-normalization=false</code> for all <code>mount</code>
+and <code>serve</code> commands on macOS. For details, see <a
+href="https://rclone.org/commands/rclone_mount/#vfs-case-sensitivity">vfs-case-sensitivity</a>.</p>
 <h3 id="nfs-mount-1">NFS mount</h3>
-<p>This method spins up an NFS server using <a href="https://rclone.org/commands/rclone_serve_nfs/">serve nfs</a> command and mounts it to the specified mountpoint. If you run this in background mode using |--daemon|, you will need to send SIGTERM signal to the rclone process using |kill| command to stop the mount.</p>
-<p>Note that <code>--nfs-cache-handle-limit</code> controls the maximum number of cached file handles stored by the <code>nfsmount</code> caching handler. This should not be set too low or you may experience errors when trying to access files. The default is 1000000, but consider lowering this limit if the server's system resource usage causes problems.</p>
+<p>This method spins up an NFS server using <a
+href="https://rclone.org/commands/rclone_serve_nfs/">serve nfs</a>
+command and mounts it to the specified mountpoint. If you run this in
+background mode using |--daemon|, you will need to send SIGTERM signal
+to the rclone process using |kill| command to stop the mount.</p>
+<p>Note that <code>--nfs-cache-handle-limit</code> controls the maximum
+number of cached file handles stored by the <code>nfsmount</code>
+caching handler. This should not be set too low or you may experience
+errors when trying to access files. The default is 1000000, but consider
+lowering this limit if the server's system resource usage causes
+problems.</p>
 <h3 id="macfuse-notes-1">macFUSE Notes</h3>
-<p>If installing macFUSE using <a href="https://github.com/osxfuse/osxfuse/releases">dmg packages</a> from the website, rclone will locate the macFUSE libraries without any further intervention. If however, macFUSE is installed using the <a href="https://www.macports.org/">macports</a> package manager, the following addition steps are required.</p>
+<p>If installing macFUSE using <a
+href="https://github.com/osxfuse/osxfuse/releases">dmg packages</a> from
+the website, rclone will locate the macFUSE libraries without any
+further intervention. If however, macFUSE is installed using the <a
+href="https://www.macports.org/">macports</a> package manager, the
+following addition steps are required.</p>
 <pre><code>sudo mkdir /usr/local/lib
 cd /usr/local/lib
 sudo ln -s /opt/local/lib/libfuse.2.dylib</code></pre>
-<h3 id="fuse-t-limitations-caveats-and-notes-1">FUSE-T Limitations, Caveats, and Notes</h3>
-<p>There are some limitations, caveats, and notes about how it works. These are current as of FUSE-T version 1.0.14.</p>
+<h3 id="fuse-t-limitations-caveats-and-notes-1">FUSE-T Limitations,
+Caveats, and Notes</h3>
+<p>There are some limitations, caveats, and notes about how it works.
+These are current as of FUSE-T version 1.0.14.</p>
 <h4 id="modtime-update-on-read-1">ModTime update on read</h4>
-<p>As per the <a href="https://github.com/macos-fuse-t/fuse-t/wiki#caveats">FUSE-T wiki</a>:</p>
+<p>As per the <a
+href="https://github.com/macos-fuse-t/fuse-t/wiki#caveats">FUSE-T
+wiki</a>:</p>
 <blockquote>
-<p>File access and modification times cannot be set separately as it seems to be an issue with the NFS client which always modifies both. Can be reproduced with 'touch -m' and 'touch -a' commands</p>
+<p>File access and modification times cannot be set separately as it
+seems to be an issue with the NFS client which always modifies both. Can
+be reproduced with 'touch -m' and 'touch -a' commands</p>
 </blockquote>
-<p>This means that viewing files with various tools, notably macOS Finder, will cause rlcone to update the modification time of the file. This may make rclone upload a full new copy of the file.</p>
+<p>This means that viewing files with various tools, notably macOS
+Finder, will cause rlcone to update the modification time of the file.
+This may make rclone upload a full new copy of the file.</p>
 <h4 id="read-only-mounts-1">Read Only mounts</h4>
-<p>When mounting with <code>--read-only</code>, attempts to write to files will fail <em>silently</em> as opposed to with a clear warning as in macFUSE.</p>
+<p>When mounting with <code>--read-only</code>, attempts to write to
+files will fail <em>silently</em> as opposed to with a clear warning as
+in macFUSE.</p>
 <h2 id="limitations-1">Limitations</h2>
-<p>Without the use of <code>--vfs-cache-mode</code> this can only write files sequentially, it can only seek when reading. This means that many applications won't work with their files on an rclone mount without <code>--vfs-cache-mode writes</code> or <code>--vfs-cache-mode full</code>. See the <a href="#vfs-file-caching">VFS File Caching</a> section for more info. When using NFS mount on macOS, if you don't specify |--vfs-cache-mode| the mount point will be read-only.</p>
-<p>The bucket-based remotes (e.g. Swift, S3, Google Compute Storage, B2) do not support the concept of empty directories, so empty directories will have a tendency to disappear once they fall out of the directory cache.</p>
-<p>When <code>rclone mount</code> is invoked on Unix with <code>--daemon</code> flag, the main rclone program will wait for the background mount to become ready or until the timeout specified by the <code>--daemon-wait</code> flag. On Linux it can check mount status using ProcFS so the flag in fact sets <strong>maximum</strong> time to wait, while the real wait can be less. On macOS / BSD the time to wait is constant and the check is performed only at the end. We advise you to set wait time on macOS reasonably.</p>
+<p>Without the use of <code>--vfs-cache-mode</code> this can only write
+files sequentially, it can only seek when reading. This means that many
+applications won't work with their files on an rclone mount without
+<code>--vfs-cache-mode writes</code> or
+<code>--vfs-cache-mode full</code>. See the <a
+href="#vfs-file-caching">VFS File Caching</a> section for more info.
+When using NFS mount on macOS, if you don't specify |--vfs-cache-mode|
+the mount point will be read-only.</p>
+<p>The bucket-based remotes (e.g. Swift, S3, Google Compute Storage, B2)
+do not support the concept of empty directories, so empty directories
+will have a tendency to disappear once they fall out of the directory
+cache.</p>
+<p>When <code>rclone mount</code> is invoked on Unix with
+<code>--daemon</code> flag, the main rclone program will wait for the
+background mount to become ready or until the timeout specified by the
+<code>--daemon-wait</code> flag. On Linux it can check mount status
+using ProcFS so the flag in fact sets <strong>maximum</strong> time to
+wait, while the real wait can be less. On macOS / BSD the time to wait
+is constant and the check is performed only at the end. We advise you to
+set wait time on macOS reasonably.</p>
 <p>Only supported on Linux, FreeBSD, OS X and Windows at the moment.</p>
-<h2 id="rclone-nfsmount-vs-rclone-synccopy">rclone nfsmount vs rclone sync/copy</h2>
-<p>File systems expect things to be 100% reliable, whereas cloud storage systems are a long way from 100% reliable. The rclone sync/copy commands cope with this with lots of retries. However rclone nfsmount can't use retries in the same way without making local copies of the uploads. Look at the <a href="#vfs-file-caching">VFS File Caching</a> for solutions to make nfsmount more reliable.</p>
+<h2 id="rclone-nfsmount-vs-rclone-synccopy">rclone nfsmount vs rclone
+sync/copy</h2>
+<p>File systems expect things to be 100% reliable, whereas cloud storage
+systems are a long way from 100% reliable. The rclone sync/copy commands
+cope with this with lots of retries. However rclone nfsmount can't use
+retries in the same way without making local copies of the uploads. Look
+at the <a href="#vfs-file-caching">VFS File Caching</a> for solutions to
+make nfsmount more reliable.</p>
 <h2 id="attribute-caching-1">Attribute caching</h2>
-<p>You can use the flag <code>--attr-timeout</code> to set the time the kernel caches the attributes (size, modification time, etc.) for directory entries.</p>
-<p>The default is <code>1s</code> which caches files just long enough to avoid too many callbacks to rclone from the kernel.</p>
-<p>In theory 0s should be the correct value for filesystems which can change outside the control of the kernel. However this causes quite a few problems such as <a href="https://github.com/rclone/rclone/issues/2157">rclone using too much memory</a>, <a href="https://forum.rclone.org/t/rclone-1-39-vs-1-40-mount-issue/5112">rclone not serving files to samba</a> and <a href="https://github.com/rclone/rclone/issues/2095#issuecomment-371141147">excessive time listing directories</a>.</p>
-<p>The kernel can cache the info about a file for the time given by <code>--attr-timeout</code>. You may see corruption if the remote file changes length during this window. It will show up as either a truncated file or a file with garbage on the end. With <code>--attr-timeout 1s</code> this is very unlikely but not impossible. The higher you set <code>--attr-timeout</code> the more likely it is. The default setting of "1s" is the lowest setting which mitigates the problems above.</p>
-<p>If you set it higher (<code>10s</code> or <code>1m</code> say) then the kernel will call back to rclone less often making it more efficient, however there is more chance of the corruption issue above.</p>
-<p>If files don't change on the remote outside of the control of rclone then there is no chance of corruption.</p>
-<p>This is the same as setting the attr_timeout option in mount.fuse.</p>
+<p>You can use the flag <code>--attr-timeout</code> to set the time the
+kernel caches the attributes (size, modification time, etc.) for
+directory entries.</p>
+<p>The default is <code>1s</code> which caches files just long enough to
+avoid too many callbacks to rclone from the kernel.</p>
+<p>In theory 0s should be the correct value for filesystems which can
+change outside the control of the kernel. However this causes quite a
+few problems such as <a
+href="https://github.com/rclone/rclone/issues/2157">rclone using too
+much memory</a>, <a
+href="https://forum.rclone.org/t/rclone-1-39-vs-1-40-mount-issue/5112">rclone
+not serving files to samba</a> and <a
+href="https://github.com/rclone/rclone/issues/2095#issuecomment-371141147">excessive
+time listing directories</a>.</p>
+<p>The kernel can cache the info about a file for the time given by
+<code>--attr-timeout</code>. You may see corruption if the remote file
+changes length during this window. It will show up as either a truncated
+file or a file with garbage on the end. With
+<code>--attr-timeout 1s</code> this is very unlikely but not impossible.
+The higher you set <code>--attr-timeout</code> the more likely it is.
+The default setting of "1s" is the lowest setting which mitigates the
+problems above.</p>
+<p>If you set it higher (<code>10s</code> or <code>1m</code> say) then
+the kernel will call back to rclone less often making it more efficient,
+however there is more chance of the corruption issue above.</p>
+<p>If files don't change on the remote outside of the control of rclone
+then there is no chance of corruption.</p>
+<p>This is the same as setting the attr_timeout option in
+mount.fuse.</p>
 <h2 id="filters-1">Filters</h2>
-<p>Note that all the rclone filters can be used to select a subset of the files to be visible in the mount.</p>
+<p>Note that all the rclone filters can be used to select a subset of
+the files to be visible in the mount.</p>
 <h2 id="systemd-1">systemd</h2>
-<p>When running rclone nfsmount as a systemd service, it is possible to use Type=notify. In this case the service will enter the started state after the mountpoint has been successfully set up. Units having the rclone nfsmount service specified as a requirement will see all files and folders immediately in this mode.</p>
-<p>Note that systemd runs mount units without any environment variables including <code>PATH</code> or <code>HOME</code>. This means that tilde (<code>~</code>) expansion will not work and you should provide <code>--config</code> and <code>--cache-dir</code> explicitly as absolute paths via rclone arguments. Since mounting requires the <code>fusermount</code> or <code>fusermount3</code> program, rclone will use the fallback PATH of <code>/bin:/usr/bin</code> in this scenario. Please ensure that <code>fusermount</code>/<code>fusermount3</code> is present on this PATH.</p>
+<p>When running rclone nfsmount as a systemd service, it is possible to
+use Type=notify. In this case the service will enter the started state
+after the mountpoint has been successfully set up. Units having the
+rclone nfsmount service specified as a requirement will see all files
+and folders immediately in this mode.</p>
+<p>Note that systemd runs mount units without any environment variables
+including <code>PATH</code> or <code>HOME</code>. This means that tilde
+(<code>~</code>) expansion will not work and you should provide
+<code>--config</code> and <code>--cache-dir</code> explicitly as
+absolute paths via rclone arguments. Since mounting requires the
+<code>fusermount</code> or <code>fusermount3</code> program, rclone will
+use the fallback PATH of <code>/bin:/usr/bin</code> in this scenario.
+Please ensure that <code>fusermount</code>/<code>fusermount3</code> is
+present on this PATH.</p>
 <h2 id="rclone-as-unix-mount-helper-1">Rclone as Unix mount helper</h2>
-<p>The core Unix program <code>/bin/mount</code> normally takes the <code>-t FSTYPE</code> argument then runs the <code>/sbin/mount.FSTYPE</code> helper program passing it mount options as <code>-o key=val,...</code> or <code>--opt=...</code>. Automount (classic or systemd) behaves in a similar way.</p>
-<p>rclone by default expects GNU-style flags <code>--key val</code>. To run it as a mount helper you should symlink rclone binary to <code>/sbin/mount.rclone</code> and optionally <code>/usr/bin/rclonefs</code>, e.g. <code>ln -s /usr/bin/rclone /sbin/mount.rclone</code>. rclone will detect it and translate command-line arguments appropriately.</p>
+<p>The core Unix program <code>/bin/mount</code> normally takes the
+<code>-t FSTYPE</code> argument then runs the
+<code>/sbin/mount.FSTYPE</code> helper program passing it mount options
+as <code>-o key=val,...</code> or <code>--opt=...</code>. Automount
+(classic or systemd) behaves in a similar way.</p>
+<p>rclone by default expects GNU-style flags <code>--key val</code>. To
+run it as a mount helper you should symlink rclone binary to
+<code>/sbin/mount.rclone</code> and optionally
+<code>/usr/bin/rclonefs</code>, e.g.
+<code>ln -s /usr/bin/rclone /sbin/mount.rclone</code>. rclone will
+detect it and translate command-line arguments appropriately.</p>
 <p>Now you can run classic mounts like this:</p>
 <pre><code>mount sftp1:subdir /mnt/data -t rclone -o vfs_cache_mode=writes,sftp_key_file=/path/to/pem</code></pre>
 <p>or create systemd mount units:</p>
@@ -3596,40 +5825,87 @@ TimeoutIdleSec=600
 WantedBy=multi-user.target</code></pre>
 <p>or add in <code>/etc/fstab</code> a line like</p>
 <pre><code>sftp1:subdir /mnt/data rclone rw,noauto,nofail,_netdev,x-systemd.automount,args2env,vfs_cache_mode=writes,config=/etc/rclone.conf,cache_dir=/var/cache/rclone 0 0</code></pre>
-<p>or use classic Automountd. Remember to provide explicit <code>config=...,cache-dir=...</code> as a workaround for mount units being run without <code>HOME</code>.</p>
-<p>Rclone in the mount helper mode will split <code>-o</code> argument(s) by comma, replace <code>_</code> by <code>-</code> and prepend <code>--</code> to get the command-line flags. Options containing commas or spaces can be wrapped in single or double quotes. Any inner quotes inside outer quotes of the same type should be doubled.</p>
-<p>Mount option syntax includes a few extra options treated specially:</p>
+<p>or use classic Automountd. Remember to provide explicit
+<code>config=...,cache-dir=...</code> as a workaround for mount units
+being run without <code>HOME</code>.</p>
+<p>Rclone in the mount helper mode will split <code>-o</code>
+argument(s) by comma, replace <code>_</code> by <code>-</code> and
+prepend <code>--</code> to get the command-line flags. Options
+containing commas or spaces can be wrapped in single or double quotes.
+Any inner quotes inside outer quotes of the same type should be
+doubled.</p>
+<p>Mount option syntax includes a few extra options treated
+specially:</p>
 <ul>
-<li><code>env.NAME=VALUE</code> will set an environment variable for the mount process. This helps with Automountd and Systemd.mount which don't allow setting custom environment for mount helpers. Typically you will use <code>env.HTTPS_PROXY=proxy.host:3128</code> or <code>env.HOME=/root</code></li>
-<li><code>command=cmount</code> can be used to run <code>cmount</code> or any other rclone command rather than the default <code>mount</code>.</li>
-<li><code>args2env</code> will pass mount options to the mount helper running in background via environment variables instead of command line arguments. This allows to hide secrets from such commands as <code>ps</code> or <code>pgrep</code>.</li>
-<li><code>vv...</code> will be transformed into appropriate <code>--verbose=N</code></li>
-<li>standard mount options like <code>x-systemd.automount</code>, <code>_netdev</code>, <code>nosuid</code> and alike are intended only for Automountd and ignored by rclone.</li>
+<li><code>env.NAME=VALUE</code> will set an environment variable for the
+mount process. This helps with Automountd and Systemd.mount which don't
+allow setting custom environment for mount helpers. Typically you will
+use <code>env.HTTPS_PROXY=proxy.host:3128</code> or
+<code>env.HOME=/root</code></li>
+<li><code>command=cmount</code> can be used to run <code>cmount</code>
+or any other rclone command rather than the default
+<code>mount</code>.</li>
+<li><code>args2env</code> will pass mount options to the mount helper
+running in background via environment variables instead of command line
+arguments. This allows to hide secrets from such commands as
+<code>ps</code> or <code>pgrep</code>.</li>
+<li><code>vv...</code> will be transformed into appropriate
+<code>--verbose=N</code></li>
+<li>standard mount options like <code>x-systemd.automount</code>,
+<code>_netdev</code>, <code>nosuid</code> and alike are intended only
+for Automountd and ignored by rclone.</li>
 </ul>
 <h2 id="vfs---virtual-file-system-1">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-1">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-1">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-1">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -3637,26 +5913,59 @@ WantedBy=multi-user.target</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-1">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-1">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -3665,76 +5974,208 @@ WantedBy=multi-user.target</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-1">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-1">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-1">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-1">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-2"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-2"><code>--vfs-read-chunk-streams</code> ==
+0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-3"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-3"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-1">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-1">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-1">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-1">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-1">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <pre><code>rclone nfsmount remote:path /path/to/mountpoint [flags]</code></pre>
 <h2 id="options-63">Options</h2>
 <pre><code>      --addr string                            IPaddress:Port or :Port to bind server to
@@ -3793,7 +6234,9 @@ WantedBy=multi-user.target</code></pre>
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)
       --volname string                         Set the volume name (supported on Windows and OSX only)
       --write-back-cache                       Makes kernel buffer writes before sending them to rclone (without this, writethrough caching is used) (not supported on Windows)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-22">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -3820,50 +6263,86 @@ WantedBy=multi-user.target</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-63">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-obscure">rclone obscure</h1>
 <p>Obscure password for use in the rclone config file.</p>
 <h2 id="synopsis-56">Synopsis</h2>
-<p>In the rclone config file, human-readable passwords are obscured. Obscuring them is done by encrypting them and writing them out in base64. This is <strong>not</strong> a secure way of encrypting these passwords as rclone can decrypt them - it is to prevent "eyedropping" - namely someone seeing a password in the rclone config file by accident.</p>
-<p>Many equally important things (like access tokens) are not obscured in the config file. However it is very hard to shoulder surf a 64 character hex token.</p>
-<p>This command can also accept a password through STDIN instead of an argument by passing a hyphen as an argument. This will use the first line of STDIN as the password not including the trailing newline.</p>
+<p>In the rclone config file, human-readable passwords are obscured.
+Obscuring them is done by encrypting them and writing them out in
+base64. This is <strong>not</strong> a secure way of encrypting these
+passwords as rclone can decrypt them - it is to prevent "eyedropping" -
+namely someone seeing a password in the rclone config file by
+accident.</p>
+<p>Many equally important things (like access tokens) are not obscured
+in the config file. However it is very hard to shoulder surf a 64
+character hex token.</p>
+<p>This command can also accept a password through STDIN instead of an
+argument by passing a hyphen as an argument. This will use the first
+line of STDIN as the password not including the trailing newline.</p>
 <pre><code>echo &quot;secretpassword&quot; | rclone obscure -</code></pre>
-<p>If there is no data on STDIN to read, rclone obscure will default to obfuscating the hyphen itself.</p>
-<p>If you want to encrypt the config file then please use config file encryption - see <a href="https://rclone.org/commands/rclone_config/">rclone config</a> for more info.</p>
+<p>If there is no data on STDIN to read, rclone obscure will default to
+obfuscating the hyphen itself.</p>
+<p>If you want to encrypt the config file then please use config file
+encryption - see <a
+href="https://rclone.org/commands/rclone_config/">rclone config</a> for
+more info.</p>
 <pre><code>rclone obscure password [flags]</code></pre>
 <h2 id="options-64">Options</h2>
 <pre><code>  -h, --help   help for obscure</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-64">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-rc">rclone rc</h1>
 <p>Run a command against a running rclone.</p>
 <h2 id="synopsis-57">Synopsis</h2>
-<p>This runs a command against a running rclone. Use the <code>--url</code> flag to specify an non default URL to connect on. This can be either a ":port" which is taken to mean "http://localhost:port" or a "host:port" which is taken to mean "http://host:port"</p>
-<p>A username and password can be passed in with <code>--user</code> and <code>--pass</code>.</p>
-<p>Note that <code>--rc-addr</code>, <code>--rc-user</code>, <code>--rc-pass</code> will be read also for <code>--url</code>, <code>--user</code>, <code>--pass</code>.</p>
-<p>The <code>--unix-socket</code> flag can be used to connect over a unix socket like this</p>
+<p>This runs a command against a running rclone. Use the
+<code>--url</code> flag to specify an non default URL to connect on.
+This can be either a ":port" which is taken to mean
+"http://localhost:port" or a "host:port" which is taken to mean
+"http://host:port"</p>
+<p>A username and password can be passed in with <code>--user</code> and
+<code>--pass</code>.</p>
+<p>Note that <code>--rc-addr</code>, <code>--rc-user</code>,
+<code>--rc-pass</code> will be read also for <code>--url</code>,
+<code>--user</code>, <code>--pass</code>.</p>
+<p>The <code>--unix-socket</code> flag can be used to connect over a
+unix socket like this</p>
 <pre><code># start server on /tmp/my.socket
 rclone rcd --rc-addr unix:///tmp/my.socket
 # Connect to it
 rclone rc --unix-socket /tmp/my.socket core/stats</code></pre>
 <p>Arguments should be passed in as parameter=value.</p>
 <p>The result will be returned as a JSON object by default.</p>
-<p>The <code>--json</code> parameter can be used to pass in a JSON blob as an input instead of key=value arguments. This is the only way of passing in more complicated values.</p>
-<p>The <code>-o</code>/<code>--opt</code> option can be used to set a key "opt" with key, value options in the form <code>-o key=value</code> or <code>-o key</code>. It can be repeated as many times as required. This is useful for rc commands which take the "opt" parameter which by convention is a dictionary of strings.</p>
+<p>The <code>--json</code> parameter can be used to pass in a JSON blob
+as an input instead of key=value arguments. This is the only way of
+passing in more complicated values.</p>
+<p>The <code>-o</code>/<code>--opt</code> option can be used to set a
+key "opt" with key, value options in the form <code>-o key=value</code>
+or <code>-o key</code>. It can be repeated as many times as required.
+This is useful for rc commands which take the "opt" parameter which by
+convention is a dictionary of strings.</p>
 <pre><code>-o key=value -o key2</code></pre>
 <p>Will place this in the "opt" value</p>
 <pre><code>{&quot;key&quot;:&quot;value&quot;, &quot;key2&quot;,&quot;&quot;)</code></pre>
-<p>The <code>-a</code>/<code>--arg</code> option can be used to set strings in the "arg" value. It can be repeated as many times as required. This is useful for rc commands which take the "arg" parameter which by convention is a list of strings.</p>
+<p>The <code>-a</code>/<code>--arg</code> option can be used to set
+strings in the "arg" value. It can be repeated as many times as
+required. This is useful for rc commands which take the "arg" parameter
+which by convention is a list of strings.</p>
 <pre><code>-a value -a value2</code></pre>
 <p>Will place this in the "arg" value</p>
 <pre><code>[&quot;value&quot;, &quot;value2&quot;]</code></pre>
-<p>Use <code>--loopback</code> to connect to the rclone instance running <code>rclone rc</code>. This is very useful for testing commands without having to run an rclone rc server, e.g.:</p>
+<p>Use <code>--loopback</code> to connect to the rclone instance running
+<code>rclone rc</code>. This is very useful for testing commands without
+having to run an rclone rc server, e.g.:</p>
 <pre><code>rclone rc --loopback operations/about fs=/</code></pre>
-<p>Use <code>rclone rc</code> to see a list of all possible commands.</p>
+<p>Use <code>rclone rc</code> to see a list of all possible
+commands.</p>
 <pre><code>rclone rc commands parameter [flags]</code></pre>
 <h2 id="options-65">Options</h2>
 <pre><code>  -a, --arg stringArray      Argument placed in the &quot;arg&quot; array
@@ -3876,27 +6355,48 @@ rclone rc --unix-socket /tmp/my.socket core/stats</code></pre>
       --unix-socket string   Path to a unix domain socket to dial to, instead of opening a TCP connection directly
       --url string           URL to connect to rclone remote control (default &quot;http://localhost:5572/&quot;)
       --user string          Username to use to rclone remote control</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-65">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-rcat">rclone rcat</h1>
 <p>Copies standard input to file on remote.</p>
 <h2 id="synopsis-58">Synopsis</h2>
-<p>Reads from standard input (stdin) and copies it to a single remote file.</p>
+<p>Reads from standard input (stdin) and copies it to a single remote
+file.</p>
 <pre><code>echo &quot;hello world&quot; | rclone rcat remote:path/to/file
 ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <p>If the remote file already exists, it will be overwritten.</p>
-<p>rcat will try to upload small files in a single request, which is usually more efficient than the streaming/chunked upload endpoints, which use multiple requests. Exact behaviour depends on the remote. What is considered a small file may be set through <code>--streaming-upload-cutoff</code>. Uploading only starts after the cutoff is reached or if the file ends before that. The data must fit into RAM. The cutoff needs to be small enough to adhere the limits of your remote, please see there. Generally speaking, setting this cutoff too high will decrease your performance.</p>
-<p>Use the <code>--size</code> flag to preallocate the file in advance at the remote end and actually stream it, even if remote backend doesn't support streaming.</p>
-<p><code>--size</code> should be the exact size of the input stream in bytes. If the size of the stream is different in length to the <code>--size</code> passed in then the transfer will likely fail.</p>
-<p>Note that the upload cannot be retried because the data is not stored. If the backend supports multipart uploading then individual chunks can be retried. If you need to transfer a lot of data, you may be better off caching it locally and then <code>rclone move</code> it to the destination which can use retries.</p>
+<p>rcat will try to upload small files in a single request, which is
+usually more efficient than the streaming/chunked upload endpoints,
+which use multiple requests. Exact behaviour depends on the remote. What
+is considered a small file may be set through
+<code>--streaming-upload-cutoff</code>. Uploading only starts after the
+cutoff is reached or if the file ends before that. The data must fit
+into RAM. The cutoff needs to be small enough to adhere the limits of
+your remote, please see there. Generally speaking, setting this cutoff
+too high will decrease your performance.</p>
+<p>Use the <code>--size</code> flag to preallocate the file in advance
+at the remote end and actually stream it, even if remote backend doesn't
+support streaming.</p>
+<p><code>--size</code> should be the exact size of the input stream in
+bytes. If the size of the stream is different in length to the
+<code>--size</code> passed in then the transfer will likely fail.</p>
+<p>Note that the upload cannot be retried because the data is not
+stored. If the backend supports multipart uploading then individual
+chunks can be retried. If you need to transfer a lot of data, you may be
+better off caching it locally and then <code>rclone move</code> it to
+the destination which can use retries.</p>
 <pre><code>rclone rcat remote:path [flags]</code></pre>
 <h2 id="options-66">Options</h2>
 <pre><code>  -h, --help       help for rcat
       --size int   File size hint to preallocate (default -1)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-15">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -3904,34 +6404,79 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-66">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-rcd">rclone rcd</h1>
 <p>Run rclone listening to remote control commands only.</p>
 <h2 id="synopsis-59">Synopsis</h2>
-<p>This runs rclone so that it only listens to remote control commands.</p>
+<p>This runs rclone so that it only listens to remote control
+commands.</p>
 <p>This is useful if you are controlling rclone via the rc API.</p>
-<p>If you pass in a path to a directory, rclone will serve that directory for GET requests on the URL passed in. It will also open the URL in the browser when rclone is run.</p>
-<p>See the <a href="https://rclone.org/rc/">rc documentation</a> for more info on the rc flags.</p>
+<p>If you pass in a path to a directory, rclone will serve that
+directory for GET requests on the URL passed in. It will also open the
+URL in the browser when rclone is run.</p>
+<p>See the <a href="https://rclone.org/rc/">rc documentation</a> for
+more info on the rc flags.</p>
 <h2 id="server-options">Server options</h2>
-<p>Use <code>--rc-addr</code> to specify which IP address and port the server should listen on, eg <code>--rc-addr 1.2.3.4:8000</code> or <code>--rc-addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
-<p>If you set <code>--rc-addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
-<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
-<p><code>--rc-addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
-<p><code>--rc-server-read-timeout</code> and <code>--rc-server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
-<p><code>--rc-max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
-<p><code>--rc-baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--rc-baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--rc-baseurl</code>, so <code>--rc-baseurl "rclone"</code>, <code>--rc-baseurl "/rclone"</code> and <code>--rc-baseurl "/rclone/"</code> are all treated identically.</p>
+<p>Use <code>--rc-addr</code> to specify which IP address and port the
+server should listen on, eg <code>--rc-addr 1.2.3.4:8000</code> or
+<code>--rc-addr :8080</code> to listen to all IPs. By default it only
+listens on localhost. You can use port :0 to let the OS choose an
+available port.</p>
+<p>If you set <code>--rc-addr</code> to listen on a public or LAN
+accessible IP address then using Authentication is advised - see the
+next section for info.</p>
+<p>You can use a unix socket by setting the url to
+<code>unix:///path/to/socket</code> or just by using an absolute path
+name. Note that unix sockets bypass the authentication - this is
+expected to be done with file system permissions.</p>
+<p><code>--rc-addr</code> may be repeated to listen on multiple
+IPs/ports/sockets. Socket activation, described further below, can also
+be used to accomplish the same.</p>
+<p><code>--rc-server-read-timeout</code> and
+<code>--rc-server-write-timeout</code> can be used to control the
+timeouts on the server. Note that this is the total time for a
+transfer.</p>
+<p><code>--rc-max-header-bytes</code> controls the maximum number of
+bytes the server will accept in the HTTP header.</p>
+<p><code>--rc-baseurl</code> controls the URL prefix that rclone serves
+from. By default rclone will serve from the root. If you used
+<code>--rc-baseurl "/rclone"</code> then rclone would serve from a URL
+starting with "/rclone/". This is useful if you wish to proxy rclone
+serve. Rclone automatically inserts leading and trailing "/" on
+<code>--rc-baseurl</code>, so <code>--rc-baseurl "rclone"</code>,
+<code>--rc-baseurl "/rclone"</code> and
+<code>--rc-baseurl "/rclone/"</code> are all treated identically.</p>
 <h3 id="tls-ssl">TLS (SSL)</h3>
-<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--rc-cert</code> and <code>--rc-key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--rc-client-ca</code> also.</p>
-<p><code>--rc-cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--krc-ey</code> should be the PEM encoded private key and <code>--rc-client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
-<p><code>--rc-min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
+<p>By default this will serve over http. If you want you can serve over
+https. You will need to supply the <code>--rc-cert</code> and
+<code>--rc-key</code> flags. If you wish to do client side certificate
+validation then you will need to supply <code>--rc-client-ca</code>
+also.</p>
+<p><code>--rc-cert</code> should be a either a PEM encoded certificate
+or a concatenation of that with the CA certificate.
+<code>--krc-ey</code> should be the PEM encoded private key and
+<code>--rc-client-ca</code> should be the PEM encoded client certificate
+authority certificate.</p>
+<p><code>--rc-min-tls-version</code> is minimum TLS version that is
+acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3"
+(default "tls1.0").</p>
 <h2 id="socket-activation">Socket activation</h2>
-<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --rc-addr`).</p>
-<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
-<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
+<p>Instead of the listening addresses specified above, rclone will
+listen to all FDs passed by the service manager, if any (and ignore any
+arguments passed by --rc-addr`).</p>
+<p>This allows rclone to be a socket-activated service. It can be
+configured with .socket and .service unit files as described in
+https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
+<p>Socket activation can be tested ad-hoc with the
+<code>systemd-socket-activate</code>command</p>
 <pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
-<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ### Template</p>
-<p><code>--rc-template</code> allows a user to specify a custom markup template for HTTP and WebDAV serve functions. The server exports the following markup to be used within the template to server pages:</p>
+<p>This will socket-activate rclone on the first connection to port 8000
+over TCP. ### Template</p>
+<p><code>--rc-template</code> allows a user to specify a custom markup
+template for HTTP and WebDAV serve functions. The server exports the
+following markup to be used within the template to server pages:</p>
 <table>
 <colgroup>
 <col style="width: 50%" />
@@ -3954,15 +6499,18 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Sort</td>
-<td style="text-align: left;">The current sort used. This is changeable via ?sort= parameter</td>
+<td style="text-align: left;">The current sort used. This is changeable
+via ?sort= parameter</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;"></td>
-<td style="text-align: left;">Sort Options: namedirfirst,name,size,time (default namedirfirst)</td>
+<td style="text-align: left;">Sort Options: namedirfirst,name,size,time
+(default namedirfirst)</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Order</td>
-<td style="text-align: left;">The current ordering used. This is changeable via ?order= parameter</td>
+<td style="text-align: left;">The current ordering used. This is
+changeable via ?order= parameter</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;"></td>
@@ -3974,11 +6522,13 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 </tr>
 <tr class="even">
 <td style="text-align: left;">.Breadcrumb</td>
-<td style="text-align: left;">Allows for creating a relative navigation</td>
+<td style="text-align: left;">Allows for creating a relative
+navigation</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Link</td>
-<td style="text-align: left;">The relative to the root link of the Text.</td>
+<td style="text-align: left;">The relative to the root link of the
+Text.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .Text</td>
@@ -3986,7 +6536,8 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Entries</td>
-<td style="text-align: left;">Information about a specific file/directory.</td>
+<td style="text-align: left;">Information about a specific
+file/directory.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .URL</td>
@@ -3994,11 +6545,13 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Leaf</td>
-<td style="text-align: left;">Currently same as 'URL' but intended to be 'just' the name.</td>
+<td style="text-align: left;">Currently same as 'URL' but intended to be
+'just' the name.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .IsDir</td>
-<td style="text-align: left;">Boolean for if an entry is a directory or not.</td>
+<td style="text-align: left;">Boolean for if an entry is a directory or
+not.</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Size</td>
@@ -4010,7 +6563,10 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 </tr>
 </tbody>
 </table>
-<p>The server also makes the following functions available so that they can be used within the template. These functions help extend the options for dynamic rendering of HTML. They can be used to render HTML based on specific conditions.</p>
+<p>The server also makes the following functions available so that they
+can be used within the template. These functions help extend the options
+for dynamic rendering of HTML. They can be used to render HTML based on
+specific conditions.</p>
 <table>
 <colgroup>
 <col style="width: 50%" />
@@ -4025,38 +6581,52 @@ ffmpeg - | rclone rcat remote:path/to/file</code></pre>
 <tbody>
 <tr class="odd">
 <td style="text-align: left;">afterEpoch</td>
-<td style="text-align: left;">Returns the time since the epoch for the given time.</td>
+<td style="text-align: left;">Returns the time since the epoch for the
+given time.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">contains</td>
-<td style="text-align: left;">Checks whether a given substring is present or not in a given string.</td>
+<td style="text-align: left;">Checks whether a given substring is
+present or not in a given string.</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">hasPrefix</td>
-<td style="text-align: left;">Checks whether the given string begins with the specified prefix.</td>
+<td style="text-align: left;">Checks whether the given string begins
+with the specified prefix.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">hasSuffix</td>
-<td style="text-align: left;">Checks whether the given string end with the specified suffix.</td>
+<td style="text-align: left;">Checks whether the given string end with
+the specified suffix.</td>
 </tr>
 </tbody>
 </table>
 <h3 id="authentication">Authentication</h3>
 <p>By default this will serve files without needing a login.</p>
-<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--rc-user</code> and <code>--rc-pass</code> flags.</p>
-<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
-<p>Use <code>--rc-htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
+<p>You can either use an htpasswd file which can take lots of users, or
+set a single username and password with the <code>--rc-user</code> and
+<code>--rc-pass</code> flags.</p>
+<p>If no static users are configured by either of the above methods, and
+client certificates are required by the <code>--client-ca</code> flag
+passed to the server, the client certificate common name will be
+considered as the username.</p>
+<p>Use <code>--rc-htpasswd /path/to/htpasswd</code> to provide an
+htpasswd file. This is in standard apache format and supports MD5, SHA1
+and BCrypt for basic authentication. Bcrypt is recommended.</p>
 <p>To create an htpasswd file:</p>
 <pre><code>touch htpasswd
 htpasswd -B htpasswd user
 htpasswd -B htpasswd anotherUser</code></pre>
 <p>The password file can be updated while rclone is running.</p>
 <p>Use <code>--rc-realm</code> to set the authentication realm.</p>
-<p>Use <code>--rc-salt</code> to change the password hashing salt from the default.</p>
+<p>Use <code>--rc-salt</code> to change the password hashing salt from
+the default.</p>
 <pre><code>rclone rcd &lt;path to files to serve&gt;* [flags]</code></pre>
 <h2 id="options-67">Options</h2>
 <pre><code>  -h, --help   help for rcd</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="rc-options">RC Options</h3>
 <p>Flags to control the Remote Control API</p>
 <pre><code>      --rc                                 Enable the remote control server
@@ -4090,21 +6660,36 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --rc-web-gui-update                  Check and update to latest version of web gui</code></pre>
 <h2 id="see-also-67">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-rmdirs">rclone rmdirs</h1>
 <p>Remove empty directories under the path.</p>
 <h2 id="synopsis-60">Synopsis</h2>
-<p>This recursively removes any empty directories (including directories that only contain empty directories), that it finds under the path. The root path itself will also be removed if it is empty, unless you supply the <code>--leave-root</code> flag.</p>
-<p>Use command <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> to delete just the empty directory given by path, not recurse.</p>
-<p>This is useful for tidying up remotes that rclone has left a lot of empty directories in. For example the <a href="https://rclone.org/commands/rclone_delete/">delete</a> command will delete files but leave the directory structure (unless used with option <code>--rmdirs</code>).</p>
-<p>This will delete <code>--checkers</code> directories concurrently so if you have thousands of empty directories consider increasing this number.</p>
-<p>To delete a path and any objects in it, use the <a href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
+<p>This recursively removes any empty directories (including directories
+that only contain empty directories), that it finds under the path. The
+root path itself will also be removed if it is empty, unless you supply
+the <code>--leave-root</code> flag.</p>
+<p>Use command <a
+href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> to delete
+just the empty directory given by path, not recurse.</p>
+<p>This is useful for tidying up remotes that rclone has left a lot of
+empty directories in. For example the <a
+href="https://rclone.org/commands/rclone_delete/">delete</a> command
+will delete files but leave the directory structure (unless used with
+option <code>--rmdirs</code>).</p>
+<p>This will delete <code>--checkers</code> directories concurrently so
+if you have thousands of empty directories consider increasing this
+number.</p>
+<p>To delete a path and any objects in it, use the <a
+href="https://rclone.org/commands/rclone_purge/">purge</a> command.</p>
 <pre><code>rclone rmdirs remote:path [flags]</code></pre>
 <h2 id="options-68">Options</h2>
 <pre><code>  -h, --help         help for rmdirs
       --leave-root   Do not remove root directory if empty</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-16">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -4112,19 +6697,62 @@ htpasswd -B htpasswd anotherUser</code></pre>
   -v, --verbose count   Print lots more stuff (repeat for more)</code></pre>
 <h2 id="see-also-68">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-selfupdate">rclone selfupdate</h1>
 <p>Update the rclone binary.</p>
 <h2 id="synopsis-61">Synopsis</h2>
-<p>This command downloads the latest release of rclone and replaces the currently running binary. The download is verified with a hashsum and cryptographically signed signature; see <a href="https://rclone.org/release_signing/">the release signing docs</a> for details.</p>
-<p>If used without flags (or with implied <code>--stable</code> flag), this command will install the latest stable release. However, some issues may be fixed (or features added) only in the latest beta release. In such cases you should run the command with the <code>--beta</code> flag, i.e. <code>rclone selfupdate --beta</code>. You can check in advance what version would be installed by adding the <code>--check</code> flag, then repeat the command without it when you are satisfied.</p>
-<p>Sometimes the rclone team may recommend you a concrete beta or stable rclone release to troubleshoot your issue or add a bleeding edge feature. The <code>--version VER</code> flag, if given, will update to the concrete version instead of the latest one. If you omit micro version from <code>VER</code> (for example <code>1.53</code>), the latest matching micro version will be used.</p>
-<p>Upon successful update rclone will print a message that contains a previous version number. You will need it if you later decide to revert your update for some reason. Then you'll have to note the previous version and run the following command: <code>rclone selfupdate [--beta] OLDVER</code>. If the old version contains only dots and digits (for example <code>v1.54.0</code>) then it's a stable release so you won't need the <code>--beta</code> flag. Beta releases have an additional information similar to <code>v1.54.0-beta.5111.06f1c0c61</code>. (if you are a developer and use a locally built rclone, the version number will end with <code>-DEV</code>, you will have to rebuild it as it obviously can't be distributed).</p>
-<p>If you previously installed rclone via a package manager, the package may include local documentation or configure services. You may wish to update with the flag <code>--package deb</code> or <code>--package rpm</code> (whichever is correct for your OS) to update these too. This command with the default <code>--package zip</code> will update only the rclone executable so the local manual may become inaccurate after it.</p>
-<p>The <a href="https://rclone.org/commands/rclone_mount/">rclone mount</a> command may or may not support extended FUSE options depending on the build and OS. <code>selfupdate</code> will refuse to update if the capability would be discarded.</p>
-<p>Note: Windows forbids deletion of a currently running executable so this command will rename the old executable to 'rclone.old.exe' upon success.</p>
-<p>Please note that this command was not available before rclone version 1.55. If it fails for you with the message <code>unknown command "selfupdate"</code> then you will need to update manually following the install instructions located at https://rclone.org/install/</p>
+<p>This command downloads the latest release of rclone and replaces the
+currently running binary. The download is verified with a hashsum and
+cryptographically signed signature; see <a
+href="https://rclone.org/release_signing/">the release signing docs</a>
+for details.</p>
+<p>If used without flags (or with implied <code>--stable</code> flag),
+this command will install the latest stable release. However, some
+issues may be fixed (or features added) only in the latest beta release.
+In such cases you should run the command with the <code>--beta</code>
+flag, i.e. <code>rclone selfupdate --beta</code>. You can check in
+advance what version would be installed by adding the
+<code>--check</code> flag, then repeat the command without it when you
+are satisfied.</p>
+<p>Sometimes the rclone team may recommend you a concrete beta or stable
+rclone release to troubleshoot your issue or add a bleeding edge
+feature. The <code>--version VER</code> flag, if given, will update to
+the concrete version instead of the latest one. If you omit micro
+version from <code>VER</code> (for example <code>1.53</code>), the
+latest matching micro version will be used.</p>
+<p>Upon successful update rclone will print a message that contains a
+previous version number. You will need it if you later decide to revert
+your update for some reason. Then you'll have to note the previous
+version and run the following command:
+<code>rclone selfupdate [--beta] OLDVER</code>. If the old version
+contains only dots and digits (for example <code>v1.54.0</code>) then
+it's a stable release so you won't need the <code>--beta</code> flag.
+Beta releases have an additional information similar to
+<code>v1.54.0-beta.5111.06f1c0c61</code>. (if you are a developer and
+use a locally built rclone, the version number will end with
+<code>-DEV</code>, you will have to rebuild it as it obviously can't be
+distributed).</p>
+<p>If you previously installed rclone via a package manager, the package
+may include local documentation or configure services. You may wish to
+update with the flag <code>--package deb</code> or
+<code>--package rpm</code> (whichever is correct for your OS) to update
+these too. This command with the default <code>--package zip</code> will
+update only the rclone executable so the local manual may become
+inaccurate after it.</p>
+<p>The <a href="https://rclone.org/commands/rclone_mount/">rclone
+mount</a> command may or may not support extended FUSE options depending
+on the build and OS. <code>selfupdate</code> will refuse to update if
+the capability would be discarded.</p>
+<p>Note: Windows forbids deletion of a currently running executable so
+this command will rename the old executable to 'rclone.old.exe' upon
+success.</p>
+<p>Please note that this command was not available before rclone version
+1.55. If it fails for you with the message
+<code>unknown command "selfupdate"</code> then you will need to update
+manually following the install instructions located at
+https://rclone.org/install/</p>
 <pre><code>rclone selfupdate [flags]</code></pre>
 <h2 id="options-69">Options</h2>
 <pre><code>      --beta             Install beta release
@@ -4134,68 +6762,124 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --package string   Package format: zip|deb|rpm (default: zip)
       --stable           Install stable release (this is the default)
       --version string   Install the given rclone version (default: latest)</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-69">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-serve">rclone serve</h1>
 <p>Serve a remote over a protocol.</p>
 <h2 id="synopsis-62">Synopsis</h2>
-<p>Serve a remote over a given protocol. Requires the use of a subcommand to specify the protocol, e.g.</p>
+<p>Serve a remote over a given protocol. Requires the use of a
+subcommand to specify the protocol, e.g.</p>
 <pre><code>rclone serve http remote:</code></pre>
-<p>Each subcommand has its own options which you can see in their help.</p>
+<p>Each subcommand has its own options which you can see in their
+help.</p>
 <pre><code>rclone serve &lt;protocol&gt; [opts] &lt;remote&gt; [flags]</code></pre>
 <h2 id="options-70">Options</h2>
 <pre><code>  -h, --help   help for serve</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-70">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
-<li><a href="https://rclone.org/commands/rclone_serve_dlna/">rclone serve dlna</a> - Serve remote:path over DLNA</li>
-<li><a href="https://rclone.org/commands/rclone_serve_docker/">rclone serve docker</a> - Serve any remote on docker's volume plugin API.</li>
-<li><a href="https://rclone.org/commands/rclone_serve_ftp/">rclone serve ftp</a> - Serve remote:path over FTP.</li>
-<li><a href="https://rclone.org/commands/rclone_serve_http/">rclone serve http</a> - Serve the remote over HTTP.</li>
-<li><a href="https://rclone.org/commands/rclone_serve_nfs/">rclone serve nfs</a> - Serve the remote as an NFS mount</li>
-<li><a href="https://rclone.org/commands/rclone_serve_restic/">rclone serve restic</a> - Serve the remote for restic's REST API.</li>
-<li><a href="https://rclone.org/commands/rclone_serve_s3/">rclone serve s3</a> - Serve remote:path over s3.</li>
-<li><a href="https://rclone.org/commands/rclone_serve_sftp/">rclone serve sftp</a> - Serve the remote over SFTP.</li>
-<li><a href="https://rclone.org/commands/rclone_serve_webdav/">rclone serve webdav</a> - Serve remote:path over WebDAV.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone_serve_dlna/">rclone
+serve dlna</a> - Serve remote:path over DLNA</li>
+<li><a href="https://rclone.org/commands/rclone_serve_docker/">rclone
+serve docker</a> - Serve any remote on docker's volume plugin API.</li>
+<li><a href="https://rclone.org/commands/rclone_serve_ftp/">rclone serve
+ftp</a> - Serve remote:path over FTP.</li>
+<li><a href="https://rclone.org/commands/rclone_serve_http/">rclone
+serve http</a> - Serve the remote over HTTP.</li>
+<li><a href="https://rclone.org/commands/rclone_serve_nfs/">rclone serve
+nfs</a> - Serve the remote as an NFS mount</li>
+<li><a href="https://rclone.org/commands/rclone_serve_restic/">rclone
+serve restic</a> - Serve the remote for restic's REST API.</li>
+<li><a href="https://rclone.org/commands/rclone_serve_s3/">rclone serve
+s3</a> - Serve remote:path over s3.</li>
+<li><a href="https://rclone.org/commands/rclone_serve_sftp/">rclone
+serve sftp</a> - Serve the remote over SFTP.</li>
+<li><a href="https://rclone.org/commands/rclone_serve_webdav/">rclone
+serve webdav</a> - Serve remote:path over WebDAV.</li>
 </ul>
 <h1 id="rclone-serve-dlna">rclone serve dlna</h1>
 <p>Serve remote:path over DLNA</p>
 <h2 id="synopsis-63">Synopsis</h2>
-<p>Run a DLNA media server for media stored in an rclone remote. Many devices, such as the Xbox and PlayStation, can automatically discover this server in the LAN and play audio/video from it. VLC is also supported. Service discovery uses UDP multicast packets (SSDP) and will thus only work on LANs.</p>
-<p>Rclone will list all files present in the remote, without filtering based on media formats or file extensions. Additionally, there is no media transcoding support. This means that some players might show files that they are not able to play back correctly.</p>
-<p>Rclone will add external subtitle files (.srt) to videos if they have the same filename as the video file itself (except the extension), either in the same directory as the video, or in a "Subs" subdirectory.</p>
+<p>Run a DLNA media server for media stored in an rclone remote. Many
+devices, such as the Xbox and PlayStation, can automatically discover
+this server in the LAN and play audio/video from it. VLC is also
+supported. Service discovery uses UDP multicast packets (SSDP) and will
+thus only work on LANs.</p>
+<p>Rclone will list all files present in the remote, without filtering
+based on media formats or file extensions. Additionally, there is no
+media transcoding support. This means that some players might show files
+that they are not able to play back correctly.</p>
+<p>Rclone will add external subtitle files (.srt) to videos if they have
+the same filename as the video file itself (except the extension),
+either in the same directory as the video, or in a "Subs"
+subdirectory.</p>
 <h2 id="server-options-1">Server options</h2>
-<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, e.g. <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs.</p>
-<p>Use <code>--name</code> to choose the friendly server name, which is by default "rclone (hostname)".</p>
-<p>Use <code>--log-trace</code> in conjunction with <code>-vv</code> to enable additional debug logging of all UPNP traffic.</p>
+<p>Use <code>--addr</code> to specify which IP address and port the
+server should listen on, e.g. <code>--addr 1.2.3.4:8000</code> or
+<code>--addr :8080</code> to listen to all IPs.</p>
+<p>Use <code>--name</code> to choose the friendly server name, which is
+by default "rclone (hostname)".</p>
+<p>Use <code>--log-trace</code> in conjunction with <code>-vv</code> to
+enable additional debug logging of all UPNP traffic.</p>
 <h2 id="vfs---virtual-file-system-2">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-2">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-2">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-2">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -4203,26 +6887,59 @@ htpasswd -B htpasswd anotherUser</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-2">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-2">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -4231,76 +6948,208 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-2">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-2">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-2">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-2">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-4"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-4"><code>--vfs-read-chunk-streams</code> ==
+0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-5"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-5"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-2">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-2">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-2">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-2">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-2">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <pre><code>rclone serve dlna remote:path [flags]</code></pre>
 <h2 id="options-71">Options</h2>
 <pre><code>      --addr string                            The ip:port or :port to bind the DLNA http server to (default &quot;:7879&quot;)
@@ -4338,7 +7187,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
       --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-23">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -4365,42 +7216,102 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-71">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-serve-docker">rclone serve docker</h1>
 <p>Serve any remote on docker's volume plugin API.</p>
 <h2 id="synopsis-64">Synopsis</h2>
-<p>This command implements the Docker volume plugin API allowing docker to use rclone as a data storage mechanism for various cloud providers. rclone provides <a href="/docker">docker volume plugin</a> based on it.</p>
-<p>To create a docker plugin, one must create a Unix or TCP socket that Docker will look for when you use the plugin and then it listens for commands from docker daemon and runs the corresponding code when necessary. Docker plugins can run as a managed plugin under control of the docker daemon or as an independent native service. For testing, you can just run it directly from the command line, for example:</p>
+<p>This command implements the Docker volume plugin API allowing docker
+to use rclone as a data storage mechanism for various cloud providers.
+rclone provides <a href="/docker">docker volume plugin</a> based on
+it.</p>
+<p>To create a docker plugin, one must create a Unix or TCP socket that
+Docker will look for when you use the plugin and then it listens for
+commands from docker daemon and runs the corresponding code when
+necessary. Docker plugins can run as a managed plugin under control of
+the docker daemon or as an independent native service. For testing, you
+can just run it directly from the command line, for example:</p>
 <pre><code>sudo rclone serve docker --base-dir /tmp/rclone-volumes --socket-addr localhost:8787 -vv</code></pre>
-<p>Running <code>rclone serve docker</code> will create the said socket, listening for commands from Docker to create the necessary Volumes. Normally you need not give the <code>--socket-addr</code> flag. The API will listen on the unix domain socket at <code>/run/docker/plugins/rclone.sock</code>. In the example above rclone will create a TCP socket and a small file <code>/etc/docker/plugins/rclone.spec</code> containing the socket address. We use <code>sudo</code> because both paths are writeable only by the root user.</p>
-<p>If you later decide to change listening socket, the docker daemon must be restarted to reconnect to <code>/run/docker/plugins/rclone.sock</code> or parse new <code>/etc/docker/plugins/rclone.spec</code>. Until you restart, any volume related docker commands will timeout trying to access the old socket. Running directly is supported on <strong>Linux only</strong>, not on Windows or MacOS. This is not a problem with managed plugin mode described in details in the <a href="https://rclone.org/docker">full documentation</a>.</p>
-<p>The command will create volume mounts under the path given by <code>--base-dir</code> (by default <code>/var/lib/docker-volumes/rclone</code> available only to root) and maintain the JSON formatted file <code>docker-plugin.state</code> in the rclone cache directory with book-keeping records of created and mounted volumes.</p>
-<p>All mount and VFS options are submitted by the docker daemon via API, but you can also provide defaults on the command line as well as set path to the config file and cache directory or adjust logging verbosity.</p>
+<p>Running <code>rclone serve docker</code> will create the said socket,
+listening for commands from Docker to create the necessary Volumes.
+Normally you need not give the <code>--socket-addr</code> flag. The API
+will listen on the unix domain socket at
+<code>/run/docker/plugins/rclone.sock</code>. In the example above
+rclone will create a TCP socket and a small file
+<code>/etc/docker/plugins/rclone.spec</code> containing the socket
+address. We use <code>sudo</code> because both paths are writeable only
+by the root user.</p>
+<p>If you later decide to change listening socket, the docker daemon
+must be restarted to reconnect to
+<code>/run/docker/plugins/rclone.sock</code> or parse new
+<code>/etc/docker/plugins/rclone.spec</code>. Until you restart, any
+volume related docker commands will timeout trying to access the old
+socket. Running directly is supported on <strong>Linux only</strong>,
+not on Windows or MacOS. This is not a problem with managed plugin mode
+described in details in the <a href="https://rclone.org/docker">full
+documentation</a>.</p>
+<p>The command will create volume mounts under the path given by
+<code>--base-dir</code> (by default
+<code>/var/lib/docker-volumes/rclone</code> available only to root) and
+maintain the JSON formatted file <code>docker-plugin.state</code> in the
+rclone cache directory with book-keeping records of created and mounted
+volumes.</p>
+<p>All mount and VFS options are submitted by the docker daemon via API,
+but you can also provide defaults on the command line as well as set
+path to the config file and cache directory or adjust logging
+verbosity.</p>
 <h2 id="vfs---virtual-file-system-3">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-3">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-3">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-3">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -4408,26 +7319,59 @@ htpasswd -B htpasswd anotherUser</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-3">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-3">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -4436,76 +7380,208 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-3">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-3">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-3">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-3">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-6"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-6"><code>--vfs-read-chunk-streams</code> ==
+0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-7"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-7"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-3">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-3">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-3">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-3">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-3">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <pre><code>rclone serve docker [flags]</code></pre>
 <h2 id="options-72">Options</h2>
 <pre><code>      --allow-non-empty                        Allow mounting over a non-empty directory (not supported on Windows)
@@ -4564,7 +7640,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)
       --volname string                         Set the volume name (supported on Windows and OSX only)
       --write-back-cache                       Makes kernel buffer writes before sending them to rclone (without this, writethrough caching is used) (not supported on Windows)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-24">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -4591,42 +7669,78 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-72">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-serve-ftp">rclone serve ftp</h1>
 <p>Serve remote:path over FTP.</p>
 <h2 id="synopsis-65">Synopsis</h2>
-<p>Run a basic FTP server to serve a remote over FTP protocol. This can be viewed with a FTP client or you can make a remote of type FTP to read and write it.</p>
+<p>Run a basic FTP server to serve a remote over FTP protocol. This can
+be viewed with a FTP client or you can make a remote of type FTP to read
+and write it.</p>
 <h2 id="server-options-2">Server options</h2>
-<p>Use --addr to specify which IP address and port the server should listen on, e.g. --addr 1.2.3.4:8000 or --addr :8080 to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
-<p>If you set --addr to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
+<p>Use --addr to specify which IP address and port the server should
+listen on, e.g. --addr 1.2.3.4:8000 or --addr :8080 to listen to all
+IPs. By default it only listens on localhost. You can use port :0 to let
+the OS choose an available port.</p>
+<p>If you set --addr to listen on a public or LAN accessible IP address
+then using Authentication is advised - see the next section for
+info.</p>
 <h3 id="authentication-1">Authentication</h3>
 <p>By default this will serve files without needing a login.</p>
-<p>You can set a single username and password with the --user and --pass flags.</p>
+<p>You can set a single username and password with the --user and --pass
+flags.</p>
 <h2 id="vfs---virtual-file-system-4">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-4">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-4">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-4">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -4634,26 +7748,59 @@ htpasswd -B htpasswd anotherUser</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-4">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-4">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -4662,89 +7809,239 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-4">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-4">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-4">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-4">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-8"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-8"><code>--vfs-read-chunk-streams</code> ==
+0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-9"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-9"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-4">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-4">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-4">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-4">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-4">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <h2 id="auth-proxy">Auth Proxy</h2>
-<p>If you supply the parameter <code>--auth-proxy /path/to/program</code> then rclone will use that program to generate backends on the fly which then are used to authenticate incoming requests. This uses a simple JSON based protocol with input on STDIN and output on STDOUT.</p>
-<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and <code>--authorized-keys</code> cannot be used together, if <code>--auth-proxy</code> is set the authorized keys option will be ignored.</p>
-<p>There is an example program <a href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a> in the rclone source code.</p>
-<p>The program's job is to take a <code>user</code> and <code>pass</code> on the input and turn those into the config for a backend on STDOUT in JSON format. This config will have any default parameters for the backend added, but it won't use configuration from environment variables or command line options - it is the job of the proxy program to make a complete config.</p>
-<p>This config generated must have this extra parameter - <code>_root</code> - root to use for the backend</p>
-<p>And it may have this parameter - <code>_obscure</code> - comma separated strings for parameters to obscure</p>
-<p>If password authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
+<p>If you supply the parameter
+<code>--auth-proxy /path/to/program</code> then rclone will use that
+program to generate backends on the fly which then are used to
+authenticate incoming requests. This uses a simple JSON based protocol
+with input on STDIN and output on STDOUT.</p>
+<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and
+<code>--authorized-keys</code> cannot be used together, if
+<code>--auth-proxy</code> is set the authorized keys option will be
+ignored.</p>
+<p>There is an example program <a
+href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a>
+in the rclone source code.</p>
+<p>The program's job is to take a <code>user</code> and
+<code>pass</code> on the input and turn those into the config for a
+backend on STDOUT in JSON format. This config will have any default
+parameters for the backend added, but it won't use configuration from
+environment variables or command line options - it is the job of the
+proxy program to make a complete config.</p>
+<p>This config generated must have this extra parameter -
+<code>_root</code> - root to use for the backend</p>
+<p>And it may have this parameter - <code>_obscure</code> - comma
+separated strings for parameters to obscure</p>
+<p>If password authentication was used by the client, input to the proxy
+process (on STDIN) would look similar to this:</p>
 <pre><code>{
     &quot;user&quot;: &quot;me&quot;,
     &quot;pass&quot;: &quot;mypassword&quot;
 }</code></pre>
-<p>If public-key authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
+<p>If public-key authentication was used by the client, input to the
+proxy process (on STDIN) would look similar to this:</p>
 <pre><code>{
     &quot;user&quot;: &quot;me&quot;,
     &quot;public_key&quot;: &quot;AAAAB3NzaC1yc2EAAAADAQABAAABAQDuwESFdAe14hVS6omeyX7edc...JQdf&quot;
@@ -4758,10 +8055,25 @@ htpasswd -B htpasswd anotherUser</code></pre>
     &quot;pass&quot;: &quot;mypassword&quot;,
     &quot;host&quot;: &quot;sftp.example.com&quot;
 }</code></pre>
-<p>This would mean that an SFTP backend would be created on the fly for the <code>user</code> and <code>pass</code>/<code>public_key</code> returned in the output to the host given. Note that since <code>_obscure</code> is set to <code>pass</code>, rclone will obscure the <code>pass</code> parameter before creating the backend (which is required for sftp backends).</p>
-<p>The program can manipulate the supplied <code>user</code> in any way, for example to make proxy to many different sftp backends, you could make the <code>user</code> be <code>user@example.com</code> and then set the <code>host</code> to <code>example.com</code> in the output and the user to <code>user</code>. For security you'd probably want to restrict the <code>host</code> to a limited list.</p>
-<p>Note that an internal cache is keyed on <code>user</code> so only use that for configuration, don't use <code>pass</code> or <code>public_key</code>. This also means that if a user's password or public-key is changed the cache will need to expire (which takes 5 mins) before it takes effect.</p>
-<p>This can be used to build general purpose proxies to any kind of backend that rclone supports.</p>
+<p>This would mean that an SFTP backend would be created on the fly for
+the <code>user</code> and <code>pass</code>/<code>public_key</code>
+returned in the output to the host given. Note that since
+<code>_obscure</code> is set to <code>pass</code>, rclone will obscure
+the <code>pass</code> parameter before creating the backend (which is
+required for sftp backends).</p>
+<p>The program can manipulate the supplied <code>user</code> in any way,
+for example to make proxy to many different sftp backends, you could
+make the <code>user</code> be <code>user@example.com</code> and then set
+the <code>host</code> to <code>example.com</code> in the output and the
+user to <code>user</code>. For security you'd probably want to restrict
+the <code>host</code> to a limited list.</p>
+<p>Note that an internal cache is keyed on <code>user</code> so only use
+that for configuration, don't use <code>pass</code> or
+<code>public_key</code>. This also means that if a user's password or
+public-key is changed the cache will need to expire (which takes 5 mins)
+before it takes effect.</p>
+<p>This can be used to build general purpose proxies to any kind of
+backend that rclone supports.</p>
 <pre><code>rclone serve ftp remote:path [flags]</code></pre>
 <h2 id="options-73">Options</h2>
 <pre><code>      --addr string                            IPaddress:Port or :Port to bind server to (default &quot;localhost:2121&quot;)
@@ -4802,7 +8114,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
       --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-25">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -4829,34 +8143,78 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-73">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-serve-http">rclone serve http</h1>
 <p>Serve the remote over HTTP.</p>
 <h2 id="synopsis-66">Synopsis</h2>
-<p>Run a basic web server to serve a remote over HTTP. This can be viewed in a web browser or you can make a remote of type http read from it.</p>
-<p>You can use the filter flags (e.g. <code>--include</code>, <code>--exclude</code>) to control what is served.</p>
-<p>The server will log errors. Use <code>-v</code> to see access logs.</p>
-<p><code>--bwlimit</code> will be respected for file transfers. Use <code>--stats</code> to control the stats printing.</p>
+<p>Run a basic web server to serve a remote over HTTP. This can be
+viewed in a web browser or you can make a remote of type http read from
+it.</p>
+<p>You can use the filter flags (e.g. <code>--include</code>,
+<code>--exclude</code>) to control what is served.</p>
+<p>The server will log errors. Use <code>-v</code> to see access
+logs.</p>
+<p><code>--bwlimit</code> will be respected for file transfers. Use
+<code>--stats</code> to control the stats printing.</p>
 <h2 id="server-options-3">Server options</h2>
-<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, eg <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
-<p>If you set <code>--addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
-<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
-<p><code>--addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
-<p><code>--server-read-timeout</code> and <code>--server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
-<p><code>--max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
-<p><code>--baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--baseurl</code>, so <code>--baseurl "rclone"</code>, <code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code> are all treated identically.</p>
+<p>Use <code>--addr</code> to specify which IP address and port the
+server should listen on, eg <code>--addr 1.2.3.4:8000</code> or
+<code>--addr :8080</code> to listen to all IPs. By default it only
+listens on localhost. You can use port :0 to let the OS choose an
+available port.</p>
+<p>If you set <code>--addr</code> to listen on a public or LAN
+accessible IP address then using Authentication is advised - see the
+next section for info.</p>
+<p>You can use a unix socket by setting the url to
+<code>unix:///path/to/socket</code> or just by using an absolute path
+name. Note that unix sockets bypass the authentication - this is
+expected to be done with file system permissions.</p>
+<p><code>--addr</code> may be repeated to listen on multiple
+IPs/ports/sockets. Socket activation, described further below, can also
+be used to accomplish the same.</p>
+<p><code>--server-read-timeout</code> and
+<code>--server-write-timeout</code> can be used to control the timeouts
+on the server. Note that this is the total time for a transfer.</p>
+<p><code>--max-header-bytes</code> controls the maximum number of bytes
+the server will accept in the HTTP header.</p>
+<p><code>--baseurl</code> controls the URL prefix that rclone serves
+from. By default rclone will serve from the root. If you used
+<code>--baseurl "/rclone"</code> then rclone would serve from a URL
+starting with "/rclone/". This is useful if you wish to proxy rclone
+serve. Rclone automatically inserts leading and trailing "/" on
+<code>--baseurl</code>, so <code>--baseurl "rclone"</code>,
+<code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code>
+are all treated identically.</p>
 <h3 id="tls-ssl-1">TLS (SSL)</h3>
-<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--cert</code> and <code>--key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--client-ca</code> also.</p>
-<p><code>--cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--key</code> should be the PEM encoded private key and <code>--client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
-<p><code>--min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
+<p>By default this will serve over http. If you want you can serve over
+https. You will need to supply the <code>--cert</code> and
+<code>--key</code> flags. If you wish to do client side certificate
+validation then you will need to supply <code>--client-ca</code>
+also.</p>
+<p><code>--cert</code> should be a either a PEM encoded certificate or a
+concatenation of that with the CA certificate. <code>--key</code> should
+be the PEM encoded private key and <code>--client-ca</code> should be
+the PEM encoded client certificate authority certificate.</p>
+<p><code>--min-tls-version</code> is minimum TLS version that is
+acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3"
+(default "tls1.0").</p>
 <h2 id="socket-activation-1">Socket activation</h2>
-<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --addr`).</p>
-<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
-<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
+<p>Instead of the listening addresses specified above, rclone will
+listen to all FDs passed by the service manager, if any (and ignore any
+arguments passed by --addr`).</p>
+<p>This allows rclone to be a socket-activated service. It can be
+configured with .socket and .service unit files as described in
+https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
+<p>Socket activation can be tested ad-hoc with the
+<code>systemd-socket-activate</code>command</p>
 <pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
-<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ### Template</p>
-<p><code>--template</code> allows a user to specify a custom markup template for HTTP and WebDAV serve functions. The server exports the following markup to be used within the template to server pages:</p>
+<p>This will socket-activate rclone on the first connection to port 8000
+over TCP. ### Template</p>
+<p><code>--template</code> allows a user to specify a custom markup
+template for HTTP and WebDAV serve functions. The server exports the
+following markup to be used within the template to server pages:</p>
 <table>
 <colgroup>
 <col style="width: 50%" />
@@ -4879,15 +8237,18 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Sort</td>
-<td style="text-align: left;">The current sort used. This is changeable via ?sort= parameter</td>
+<td style="text-align: left;">The current sort used. This is changeable
+via ?sort= parameter</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;"></td>
-<td style="text-align: left;">Sort Options: namedirfirst,name,size,time (default namedirfirst)</td>
+<td style="text-align: left;">Sort Options: namedirfirst,name,size,time
+(default namedirfirst)</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Order</td>
-<td style="text-align: left;">The current ordering used. This is changeable via ?order= parameter</td>
+<td style="text-align: left;">The current ordering used. This is
+changeable via ?order= parameter</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;"></td>
@@ -4899,11 +8260,13 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 <tr class="even">
 <td style="text-align: left;">.Breadcrumb</td>
-<td style="text-align: left;">Allows for creating a relative navigation</td>
+<td style="text-align: left;">Allows for creating a relative
+navigation</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Link</td>
-<td style="text-align: left;">The relative to the root link of the Text.</td>
+<td style="text-align: left;">The relative to the root link of the
+Text.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .Text</td>
@@ -4911,7 +8274,8 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Entries</td>
-<td style="text-align: left;">Information about a specific file/directory.</td>
+<td style="text-align: left;">Information about a specific
+file/directory.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .URL</td>
@@ -4919,11 +8283,13 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Leaf</td>
-<td style="text-align: left;">Currently same as 'URL' but intended to be 'just' the name.</td>
+<td style="text-align: left;">Currently same as 'URL' but intended to be
+'just' the name.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .IsDir</td>
-<td style="text-align: left;">Boolean for if an entry is a directory or not.</td>
+<td style="text-align: left;">Boolean for if an entry is a directory or
+not.</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Size</td>
@@ -4935,7 +8301,10 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 </tbody>
 </table>
-<p>The server also makes the following functions available so that they can be used within the template. These functions help extend the options for dynamic rendering of HTML. They can be used to render HTML based on specific conditions.</p>
+<p>The server also makes the following functions available so that they
+can be used within the template. These functions help extend the options
+for dynamic rendering of HTML. They can be used to render HTML based on
+specific conditions.</p>
 <table>
 <colgroup>
 <col style="width: 50%" />
@@ -4950,58 +8319,97 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <tbody>
 <tr class="odd">
 <td style="text-align: left;">afterEpoch</td>
-<td style="text-align: left;">Returns the time since the epoch for the given time.</td>
+<td style="text-align: left;">Returns the time since the epoch for the
+given time.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">contains</td>
-<td style="text-align: left;">Checks whether a given substring is present or not in a given string.</td>
+<td style="text-align: left;">Checks whether a given substring is
+present or not in a given string.</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">hasPrefix</td>
-<td style="text-align: left;">Checks whether the given string begins with the specified prefix.</td>
+<td style="text-align: left;">Checks whether the given string begins
+with the specified prefix.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">hasSuffix</td>
-<td style="text-align: left;">Checks whether the given string end with the specified suffix.</td>
+<td style="text-align: left;">Checks whether the given string end with
+the specified suffix.</td>
 </tr>
 </tbody>
 </table>
 <h3 id="authentication-2">Authentication</h3>
 <p>By default this will serve files without needing a login.</p>
-<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--user</code> and <code>--pass</code> flags.</p>
-<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
-<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
+<p>You can either use an htpasswd file which can take lots of users, or
+set a single username and password with the <code>--user</code> and
+<code>--pass</code> flags.</p>
+<p>If no static users are configured by either of the above methods, and
+client certificates are required by the <code>--client-ca</code> flag
+passed to the server, the client certificate common name will be
+considered as the username.</p>
+<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd
+file. This is in standard apache format and supports MD5, SHA1 and
+BCrypt for basic authentication. Bcrypt is recommended.</p>
 <p>To create an htpasswd file:</p>
 <pre><code>touch htpasswd
 htpasswd -B htpasswd user
 htpasswd -B htpasswd anotherUser</code></pre>
 <p>The password file can be updated while rclone is running.</p>
 <p>Use <code>--realm</code> to set the authentication realm.</p>
-<p>Use <code>--salt</code> to change the password hashing salt from the default.</p>
+<p>Use <code>--salt</code> to change the password hashing salt from the
+default.</p>
 <h2 id="vfs---virtual-file-system-5">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-5">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-5">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-5">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -5009,26 +8417,59 @@ htpasswd -B htpasswd anotherUser</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-5">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-5">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -5037,89 +8478,239 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-5">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-5">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-5">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-5">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-10"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-10"><code>--vfs-read-chunk-streams</code>
+== 0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-11"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-11"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-5">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-5">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-5">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-5">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-5">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <h2 id="auth-proxy-1">Auth Proxy</h2>
-<p>If you supply the parameter <code>--auth-proxy /path/to/program</code> then rclone will use that program to generate backends on the fly which then are used to authenticate incoming requests. This uses a simple JSON based protocol with input on STDIN and output on STDOUT.</p>
-<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and <code>--authorized-keys</code> cannot be used together, if <code>--auth-proxy</code> is set the authorized keys option will be ignored.</p>
-<p>There is an example program <a href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a> in the rclone source code.</p>
-<p>The program's job is to take a <code>user</code> and <code>pass</code> on the input and turn those into the config for a backend on STDOUT in JSON format. This config will have any default parameters for the backend added, but it won't use configuration from environment variables or command line options - it is the job of the proxy program to make a complete config.</p>
-<p>This config generated must have this extra parameter - <code>_root</code> - root to use for the backend</p>
-<p>And it may have this parameter - <code>_obscure</code> - comma separated strings for parameters to obscure</p>
-<p>If password authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
+<p>If you supply the parameter
+<code>--auth-proxy /path/to/program</code> then rclone will use that
+program to generate backends on the fly which then are used to
+authenticate incoming requests. This uses a simple JSON based protocol
+with input on STDIN and output on STDOUT.</p>
+<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and
+<code>--authorized-keys</code> cannot be used together, if
+<code>--auth-proxy</code> is set the authorized keys option will be
+ignored.</p>
+<p>There is an example program <a
+href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a>
+in the rclone source code.</p>
+<p>The program's job is to take a <code>user</code> and
+<code>pass</code> on the input and turn those into the config for a
+backend on STDOUT in JSON format. This config will have any default
+parameters for the backend added, but it won't use configuration from
+environment variables or command line options - it is the job of the
+proxy program to make a complete config.</p>
+<p>This config generated must have this extra parameter -
+<code>_root</code> - root to use for the backend</p>
+<p>And it may have this parameter - <code>_obscure</code> - comma
+separated strings for parameters to obscure</p>
+<p>If password authentication was used by the client, input to the proxy
+process (on STDIN) would look similar to this:</p>
 <pre><code>{
     &quot;user&quot;: &quot;me&quot;,
     &quot;pass&quot;: &quot;mypassword&quot;
 }</code></pre>
-<p>If public-key authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
+<p>If public-key authentication was used by the client, input to the
+proxy process (on STDIN) would look similar to this:</p>
 <pre><code>{
     &quot;user&quot;: &quot;me&quot;,
     &quot;public_key&quot;: &quot;AAAAB3NzaC1yc2EAAAADAQABAAABAQDuwESFdAe14hVS6omeyX7edc...JQdf&quot;
@@ -5133,10 +8724,25 @@ htpasswd -B htpasswd anotherUser</code></pre>
     &quot;pass&quot;: &quot;mypassword&quot;,
     &quot;host&quot;: &quot;sftp.example.com&quot;
 }</code></pre>
-<p>This would mean that an SFTP backend would be created on the fly for the <code>user</code> and <code>pass</code>/<code>public_key</code> returned in the output to the host given. Note that since <code>_obscure</code> is set to <code>pass</code>, rclone will obscure the <code>pass</code> parameter before creating the backend (which is required for sftp backends).</p>
-<p>The program can manipulate the supplied <code>user</code> in any way, for example to make proxy to many different sftp backends, you could make the <code>user</code> be <code>user@example.com</code> and then set the <code>host</code> to <code>example.com</code> in the output and the user to <code>user</code>. For security you'd probably want to restrict the <code>host</code> to a limited list.</p>
-<p>Note that an internal cache is keyed on <code>user</code> so only use that for configuration, don't use <code>pass</code> or <code>public_key</code>. This also means that if a user's password or public-key is changed the cache will need to expire (which takes 5 mins) before it takes effect.</p>
-<p>This can be used to build general purpose proxies to any kind of backend that rclone supports.</p>
+<p>This would mean that an SFTP backend would be created on the fly for
+the <code>user</code> and <code>pass</code>/<code>public_key</code>
+returned in the output to the host given. Note that since
+<code>_obscure</code> is set to <code>pass</code>, rclone will obscure
+the <code>pass</code> parameter before creating the backend (which is
+required for sftp backends).</p>
+<p>The program can manipulate the supplied <code>user</code> in any way,
+for example to make proxy to many different sftp backends, you could
+make the <code>user</code> be <code>user@example.com</code> and then set
+the <code>host</code> to <code>example.com</code> in the output and the
+user to <code>user</code>. For security you'd probably want to restrict
+the <code>host</code> to a limited list.</p>
+<p>Note that an internal cache is keyed on <code>user</code> so only use
+that for configuration, don't use <code>pass</code> or
+<code>public_key</code>. This also means that if a user's password or
+public-key is changed the cache will need to expire (which takes 5 mins)
+before it takes effect.</p>
+<p>This can be used to build general purpose proxies to any kind of
+backend that rclone supports.</p>
 <pre><code>rclone serve http remote:path [flags]</code></pre>
 <h2 id="options-74">Options</h2>
 <pre><code>      --addr stringArray                       IPaddress:Port, :Port or [unix://]/path/to/socket to bind server to (default [127.0.0.1:8080])
@@ -5186,7 +8792,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
       --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-26">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -5213,51 +8821,116 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-74">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-serve-nfs">rclone serve nfs</h1>
 <p>Serve the remote as an NFS mount</p>
 <h2 id="synopsis-67">Synopsis</h2>
-<p>Create an NFS server that serves the given remote over the network.</p>
-<p>This implements an NFSv3 server to serve any rclone remote via NFS.</p>
-<p>The primary purpose for this command is to enable the <a href="https://rclone.org/commands/rclone_mount/">mount command</a> on recent macOS versions where installing FUSE is very cumbersome.</p>
-<p>This server does not implement any authentication so any client will be able to access the data. To limit access, you can use <code>serve nfs</code> on the loopback address or rely on secure tunnels (such as SSH) or use firewalling.</p>
-<p>For this reason, by default, a random TCP port is chosen and the loopback interface is used for the listening address by default; meaning that it is only available to the local machine. If you want other machines to access the NFS mount over local network, you need to specify the listening address and port using the <code>--addr</code> flag.</p>
-<p>Modifying files through the NFS protocol requires VFS caching. Usually you will need to specify <code>--vfs-cache-mode</code> in order to be able to write to the mountpoint (<code>full</code> is recommended). If you don't specify VFS cache mode, the mount will be read-only.</p>
-<p><code>--nfs-cache-type</code> controls the type of the NFS handle cache. By default this is <code>memory</code> where new handles will be randomly allocated when needed. These are stored in memory. If the server is restarted the handle cache will be lost and connected NFS clients will get stale handle errors.</p>
-<p><code>--nfs-cache-type disk</code> uses an on disk NFS handle cache. Rclone hashes the path of the object and stores it in a file named after the hash. These hashes are stored on disk the directory controlled by <code>--cache-dir</code> or the exact directory may be specified with <code>--nfs-cache-dir</code>. Using this means that the NFS server can be restarted at will without affecting the connected clients.</p>
-<p><code>--nfs-cache-type symlink</code> is similar to <code>--nfs-cache-type disk</code> in that it uses an on disk cache, but the cache entries are held as symlinks. Rclone will use the handle of the underlying file as the NFS handle which improves performance. This sort of cache can't be backed up and restored as the underlying handles will change. This is Linux only.</p>
-<p><code>--nfs-cache-handle-limit</code> controls the maximum number of cached NFS handles stored by the caching handler. This should not be set too low or you may experience errors when trying to access files. The default is <code>1000000</code>, but consider lowering this limit if the server's system resource usage causes problems. This is only used by the <code>memory</code> type cache.</p>
+<p>Create an NFS server that serves the given remote over the
+network.</p>
+<p>This implements an NFSv3 server to serve any rclone remote via
+NFS.</p>
+<p>The primary purpose for this command is to enable the <a
+href="https://rclone.org/commands/rclone_mount/">mount command</a> on
+recent macOS versions where installing FUSE is very cumbersome.</p>
+<p>This server does not implement any authentication so any client will
+be able to access the data. To limit access, you can use
+<code>serve nfs</code> on the loopback address or rely on secure tunnels
+(such as SSH) or use firewalling.</p>
+<p>For this reason, by default, a random TCP port is chosen and the
+loopback interface is used for the listening address by default; meaning
+that it is only available to the local machine. If you want other
+machines to access the NFS mount over local network, you need to specify
+the listening address and port using the <code>--addr</code> flag.</p>
+<p>Modifying files through the NFS protocol requires VFS caching.
+Usually you will need to specify <code>--vfs-cache-mode</code> in order
+to be able to write to the mountpoint (<code>full</code> is
+recommended). If you don't specify VFS cache mode, the mount will be
+read-only.</p>
+<p><code>--nfs-cache-type</code> controls the type of the NFS handle
+cache. By default this is <code>memory</code> where new handles will be
+randomly allocated when needed. These are stored in memory. If the
+server is restarted the handle cache will be lost and connected NFS
+clients will get stale handle errors.</p>
+<p><code>--nfs-cache-type disk</code> uses an on disk NFS handle cache.
+Rclone hashes the path of the object and stores it in a file named after
+the hash. These hashes are stored on disk the directory controlled by
+<code>--cache-dir</code> or the exact directory may be specified with
+<code>--nfs-cache-dir</code>. Using this means that the NFS server can
+be restarted at will without affecting the connected clients.</p>
+<p><code>--nfs-cache-type symlink</code> is similar to
+<code>--nfs-cache-type disk</code> in that it uses an on disk cache, but
+the cache entries are held as symlinks. Rclone will use the handle of
+the underlying file as the NFS handle which improves performance. This
+sort of cache can't be backed up and restored as the underlying handles
+will change. This is Linux only.</p>
+<p><code>--nfs-cache-handle-limit</code> controls the maximum number of
+cached NFS handles stored by the caching handler. This should not be set
+too low or you may experience errors when trying to access files. The
+default is <code>1000000</code>, but consider lowering this limit if the
+server's system resource usage causes problems. This is only used by the
+<code>memory</code> type cache.</p>
 <p>To serve NFS over the network use following command:</p>
 <pre><code>rclone serve nfs remote: --addr 0.0.0.0:$PORT --vfs-cache-mode=full</code></pre>
-<p>This specifies a port that can be used in the mount command. To mount the server under Linux/macOS, use the following command:</p>
+<p>This specifies a port that can be used in the mount command. To mount
+the server under Linux/macOS, use the following command:</p>
 <pre><code>mount -t nfs -o port=$PORT,mountport=$PORT,tcp $HOSTNAME:/ path/to/mountpoint</code></pre>
-<p>Where <code>$PORT</code> is the same port number used in the <code>serve nfs</code> command and <code>$HOSTNAME</code> is the network address of the machine that <code>serve nfs</code> was run on.</p>
+<p>Where <code>$PORT</code> is the same port number used in the
+<code>serve nfs</code> command and <code>$HOSTNAME</code> is the network
+address of the machine that <code>serve nfs</code> was run on.</p>
 <p>This command is only available on Unix platforms.</p>
 <h2 id="vfs---virtual-file-system-6">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-6">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-6">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-6">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -5265,26 +8938,59 @@ htpasswd -B htpasswd anotherUser</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-6">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-6">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -5293,76 +8999,208 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-6">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-6">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-6">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-6">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-12"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-12"><code>--vfs-read-chunk-streams</code>
+== 0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-13"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-13"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-6">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-6">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-6">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-6">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-6">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <pre><code>rclone serve nfs remote:path [flags]</code></pre>
 <h2 id="options-75">Options</h2>
 <pre><code>      --addr string                            IPaddress:Port or :Port to bind server to
@@ -5399,7 +9237,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
       --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-27">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -5426,28 +9266,48 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-75">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-serve-restic">rclone serve restic</h1>
 <p>Serve the remote for restic's REST API.</p>
 <h2 id="synopsis-68">Synopsis</h2>
-<p>Run a basic web server to serve a remote over restic's REST backend API over HTTP. This allows restic to use rclone as a data storage mechanism for cloud providers that restic does not support directly.</p>
-<p><a href="https://restic.net/">Restic</a> is a command-line program for doing backups.</p>
+<p>Run a basic web server to serve a remote over restic's REST backend
+API over HTTP. This allows restic to use rclone as a data storage
+mechanism for cloud providers that restic does not support directly.</p>
+<p><a href="https://restic.net/">Restic</a> is a command-line program
+for doing backups.</p>
 <p>The server will log errors. Use -v to see access logs.</p>
-<p><code>--bwlimit</code> will be respected for file transfers. Use <code>--stats</code> to control the stats printing.</p>
-<h2 id="setting-up-rclone-for-use-by-restic">Setting up rclone for use by restic</h2>
-<p>First <a href="https://rclone.org/docs/#configure">set up a remote for your chosen cloud provider</a>.</p>
-<p>Once you have set up the remote, check it is working with, for example "rclone lsd remote:". You may have called the remote something other than "remote:" - just substitute whatever you called it in the following instructions.</p>
+<p><code>--bwlimit</code> will be respected for file transfers. Use
+<code>--stats</code> to control the stats printing.</p>
+<h2 id="setting-up-rclone-for-use-by-restic">Setting up rclone for use
+by restic</h2>
+<p>First <a href="https://rclone.org/docs/#configure">set up a remote
+for your chosen cloud provider</a>.</p>
+<p>Once you have set up the remote, check it is working with, for
+example "rclone lsd remote:". You may have called the remote something
+other than "remote:" - just substitute whatever you called it in the
+following instructions.</p>
 <p>Now start the rclone restic server</p>
 <pre><code>rclone serve restic -v remote:backup</code></pre>
-<p>Where you can replace "backup" in the above by whatever path in the remote you wish to use.</p>
-<p>By default this will serve on "localhost:8080" you can change this with use of the <code>--addr</code> flag.</p>
+<p>Where you can replace "backup" in the above by whatever path in the
+remote you wish to use.</p>
+<p>By default this will serve on "localhost:8080" you can change this
+with use of the <code>--addr</code> flag.</p>
 <p>You might wish to start this server on boot.</p>
-<p>Adding <code>--cache-objects=false</code> will cause rclone to stop caching objects returned from the List call. Caching is normally desirable as it speeds up downloading objects, saves transactions and uses very little memory.</p>
-<h2 id="setting-up-restic-to-use-rclone">Setting up restic to use rclone</h2>
-<p>Now you can <a href="http://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html#rest-server">follow the restic instructions</a> on setting up restic.</p>
-<p>Note that you will need restic 0.8.2 or later to interoperate with rclone.</p>
-<p>For the example above you will want to use "http://localhost:8080/" as the URL for the REST server.</p>
+<p>Adding <code>--cache-objects=false</code> will cause rclone to stop
+caching objects returned from the List call. Caching is normally
+desirable as it speeds up downloading objects, saves transactions and
+uses very little memory.</p>
+<h2 id="setting-up-restic-to-use-rclone">Setting up restic to use
+rclone</h2>
+<p>Now you can <a
+href="http://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html#rest-server">follow
+the restic instructions</a> on setting up restic.</p>
+<p>Note that you will need restic 0.8.2 or later to interoperate with
+rclone.</p>
+<p>For the example above you will want to use "http://localhost:8080/"
+as the URL for the REST server.</p>
 <p>For example:</p>
 <pre><code>$ export RESTIC_REPOSITORY=rest:http://localhost:8080/
 $ export RESTIC_PASSWORD=yourpassword
@@ -5464,42 +9324,90 @@ scanned 189 directories, 312 files in 0:00
 duration: 0:00
 snapshot 45c8fdd8 saved</code></pre>
 <h3 id="multiple-repositories">Multiple repositories</h3>
-<p>Note that you can use the endpoint to host multiple repositories. Do this by adding a directory name or path after the URL. Note that these <strong>must</strong> end with /. Eg</p>
+<p>Note that you can use the endpoint to host multiple repositories. Do
+this by adding a directory name or path after the URL. Note that these
+<strong>must</strong> end with /. Eg</p>
 <pre><code>$ export RESTIC_REPOSITORY=rest:http://localhost:8080/user1repo/
 # backup user1 stuff
 $ export RESTIC_REPOSITORY=rest:http://localhost:8080/user2repo/
 # backup user2 stuff</code></pre>
 <h3 id="private-repositories">Private repositories</h3>
-<p>The<code>--private-repos</code> flag can be used to limit users to repositories starting with a path of <code>/&lt;username&gt;/</code>.</p>
+<p>The<code>--private-repos</code> flag can be used to limit users to
+repositories starting with a path of
+<code>/&lt;username&gt;/</code>.</p>
 <h2 id="server-options-4">Server options</h2>
-<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, eg <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
-<p>If you set <code>--addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
-<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
-<p><code>--addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
-<p><code>--server-read-timeout</code> and <code>--server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
-<p><code>--max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
-<p><code>--baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--baseurl</code>, so <code>--baseurl "rclone"</code>, <code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code> are all treated identically.</p>
+<p>Use <code>--addr</code> to specify which IP address and port the
+server should listen on, eg <code>--addr 1.2.3.4:8000</code> or
+<code>--addr :8080</code> to listen to all IPs. By default it only
+listens on localhost. You can use port :0 to let the OS choose an
+available port.</p>
+<p>If you set <code>--addr</code> to listen on a public or LAN
+accessible IP address then using Authentication is advised - see the
+next section for info.</p>
+<p>You can use a unix socket by setting the url to
+<code>unix:///path/to/socket</code> or just by using an absolute path
+name. Note that unix sockets bypass the authentication - this is
+expected to be done with file system permissions.</p>
+<p><code>--addr</code> may be repeated to listen on multiple
+IPs/ports/sockets. Socket activation, described further below, can also
+be used to accomplish the same.</p>
+<p><code>--server-read-timeout</code> and
+<code>--server-write-timeout</code> can be used to control the timeouts
+on the server. Note that this is the total time for a transfer.</p>
+<p><code>--max-header-bytes</code> controls the maximum number of bytes
+the server will accept in the HTTP header.</p>
+<p><code>--baseurl</code> controls the URL prefix that rclone serves
+from. By default rclone will serve from the root. If you used
+<code>--baseurl "/rclone"</code> then rclone would serve from a URL
+starting with "/rclone/". This is useful if you wish to proxy rclone
+serve. Rclone automatically inserts leading and trailing "/" on
+<code>--baseurl</code>, so <code>--baseurl "rclone"</code>,
+<code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code>
+are all treated identically.</p>
 <h3 id="tls-ssl-2">TLS (SSL)</h3>
-<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--cert</code> and <code>--key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--client-ca</code> also.</p>
-<p><code>--cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--key</code> should be the PEM encoded private key and <code>--client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
-<p><code>--min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
+<p>By default this will serve over http. If you want you can serve over
+https. You will need to supply the <code>--cert</code> and
+<code>--key</code> flags. If you wish to do client side certificate
+validation then you will need to supply <code>--client-ca</code>
+also.</p>
+<p><code>--cert</code> should be a either a PEM encoded certificate or a
+concatenation of that with the CA certificate. <code>--key</code> should
+be the PEM encoded private key and <code>--client-ca</code> should be
+the PEM encoded client certificate authority certificate.</p>
+<p><code>--min-tls-version</code> is minimum TLS version that is
+acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3"
+(default "tls1.0").</p>
 <h2 id="socket-activation-2">Socket activation</h2>
-<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --addr`).</p>
-<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
-<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
+<p>Instead of the listening addresses specified above, rclone will
+listen to all FDs passed by the service manager, if any (and ignore any
+arguments passed by --addr`).</p>
+<p>This allows rclone to be a socket-activated service. It can be
+configured with .socket and .service unit files as described in
+https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
+<p>Socket activation can be tested ad-hoc with the
+<code>systemd-socket-activate</code>command</p>
 <pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
-<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ### Authentication</p>
+<p>This will socket-activate rclone on the first connection to port 8000
+over TCP. ### Authentication</p>
 <p>By default this will serve files without needing a login.</p>
-<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--user</code> and <code>--pass</code> flags.</p>
-<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
-<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
+<p>You can either use an htpasswd file which can take lots of users, or
+set a single username and password with the <code>--user</code> and
+<code>--pass</code> flags.</p>
+<p>If no static users are configured by either of the above methods, and
+client certificates are required by the <code>--client-ca</code> flag
+passed to the server, the client certificate common name will be
+considered as the username.</p>
+<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd
+file. This is in standard apache format and supports MD5, SHA1 and
+BCrypt for basic authentication. Bcrypt is recommended.</p>
 <p>To create an htpasswd file:</p>
 <pre><code>touch htpasswd
 htpasswd -B htpasswd user
 htpasswd -B htpasswd anotherUser</code></pre>
 <p>The password file can be updated while rclone is running.</p>
 <p>Use <code>--realm</code> to set the authentication realm.</p>
-<p>Use <code>--salt</code> to change the password hashing salt from the default.</p>
+<p>Use <code>--salt</code> to change the password hashing salt from the
+default.</p>
 <pre><code>rclone serve restic remote:path [flags]</code></pre>
 <h2 id="options-76">Options</h2>
 <pre><code>      --addr stringArray                IPaddress:Port, :Port or [unix://]/path/to/socket to bind server to (default [127.0.0.1:8080])
@@ -5522,32 +9430,61 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --server-write-timeout Duration   Timeout for server writing data (default 1h0m0s)
       --stdio                           Run an HTTP2 server on stdin/stdout
       --user string                     User name for authentication</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-76">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-serve-s3">rclone serve s3</h1>
 <p>Serve remote:path over s3.</p>
 <h2 id="synopsis-69">Synopsis</h2>
-<p><code>serve s3</code> implements a basic s3 server that serves a remote via s3. This can be viewed with an s3 client, or you can make an <a href="https://rclone.org/s3/">s3 type remote</a> to read and write to it with rclone.</p>
-<p><code>serve s3</code> is considered <strong>Experimental</strong> so use with care.</p>
-<p>S3 server supports Signature Version 4 authentication. Just use <code>--auth-key accessKey,secretKey</code> and set the <code>Authorization</code> header correctly in the request. (See the <a href="https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html">AWS docs</a>).</p>
-<p><code>--auth-key</code> can be repeated for multiple auth pairs. If <code>--auth-key</code> is not provided then <code>serve s3</code> will allow anonymous access.</p>
-<p>Please note that some clients may require HTTPS endpoints. See <a href="#ssl-tls">the SSL docs</a> for more information.</p>
-<p>This command uses the <a href="#vfs-virtual-file-system">VFS directory cache</a>. All the functionality will work with <code>--vfs-cache-mode off</code>. Using <code>--vfs-cache-mode full</code> (or <code>writes</code>) can be used to cache objects locally to improve performance.</p>
-<p>Use <code>--force-path-style=false</code> if you want to use the bucket name as a part of the hostname (such as mybucket.local)</p>
-<p>Use <code>--etag-hash</code> if you want to change the hash uses for the <code>ETag</code>. Note that using anything other than <code>MD5</code> (the default) is likely to cause problems for S3 clients which rely on the Etag being the MD5.</p>
+<p><code>serve s3</code> implements a basic s3 server that serves a
+remote via s3. This can be viewed with an s3 client, or you can make an
+<a href="https://rclone.org/s3/">s3 type remote</a> to read and write to
+it with rclone.</p>
+<p><code>serve s3</code> is considered <strong>Experimental</strong> so
+use with care.</p>
+<p>S3 server supports Signature Version 4 authentication. Just use
+<code>--auth-key accessKey,secretKey</code> and set the
+<code>Authorization</code> header correctly in the request. (See the <a
+href="https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html">AWS
+docs</a>).</p>
+<p><code>--auth-key</code> can be repeated for multiple auth pairs. If
+<code>--auth-key</code> is not provided then <code>serve s3</code> will
+allow anonymous access.</p>
+<p>Please note that some clients may require HTTPS endpoints. See <a
+href="#ssl-tls">the SSL docs</a> for more information.</p>
+<p>This command uses the <a href="#vfs-virtual-file-system">VFS
+directory cache</a>. All the functionality will work with
+<code>--vfs-cache-mode off</code>. Using
+<code>--vfs-cache-mode full</code> (or <code>writes</code>) can be used
+to cache objects locally to improve performance.</p>
+<p>Use <code>--force-path-style=false</code> if you want to use the
+bucket name as a part of the hostname (such as mybucket.local)</p>
+<p>Use <code>--etag-hash</code> if you want to change the hash uses for
+the <code>ETag</code>. Note that using anything other than
+<code>MD5</code> (the default) is likely to cause problems for S3
+clients which rely on the Etag being the MD5.</p>
 <h2 id="quickstart-1">Quickstart</h2>
-<p>For a simple set up, to serve <code>remote:path</code> over s3, run the server like this:</p>
+<p>For a simple set up, to serve <code>remote:path</code> over s3, run
+the server like this:</p>
 <pre><code>rclone serve s3 --auth-key ACCESS_KEY_ID,SECRET_ACCESS_KEY remote:path</code></pre>
-<p>For example, to use a simple folder in the filesystem, run the server with a command like this:</p>
+<p>For example, to use a simple folder in the filesystem, run the server
+with a command like this:</p>
 <pre><code>rclone serve s3 --auth-key ACCESS_KEY_ID,SECRET_ACCESS_KEY local:/path/to/folder</code></pre>
 <p>The <code>rclone.conf</code> for the server could look like this:</p>
 <pre><code>[local]
 type = local</code></pre>
-<p>The <code>local</code> configuration is optional though. If you run the server with a <code>remote:path</code> like <code>/path/to/folder</code> (without the <code>local:</code> prefix and without an <code>rclone.conf</code> file), rclone will fall back to a default configuration, which will be visible as a warning in the logs. But it will run nonetheless.</p>
-<p>This will be compatible with an rclone (client) remote configuration which is defined like this:</p>
+<p>The <code>local</code> configuration is optional though. If you run
+the server with a <code>remote:path</code> like
+<code>/path/to/folder</code> (without the <code>local:</code> prefix and
+without an <code>rclone.conf</code> file), rclone will fall back to a
+default configuration, which will be visible as a warning in the logs.
+But it will run nonetheless.</p>
+<p>This will be compatible with an rclone (client) remote configuration
+which is defined like this:</p>
 <pre><code>[serves3]
 type = s3
 provider = Rclone
@@ -5555,19 +9492,44 @@ endpoint = http://127.0.0.1:8080/
 access_key_id = ACCESS_KEY_ID
 secret_access_key = SECRET_ACCESS_KEY
 use_multipart_uploads = false</code></pre>
-<p>Note that setting <code>disable_multipart_uploads = true</code> is to work around <a href="#bugs">a bug</a> which will be fixed in due course.</p>
+<p>Note that setting <code>disable_multipart_uploads = true</code> is to
+work around <a href="#bugs">a bug</a> which will be fixed in due
+course.</p>
 <h2 id="bugs">Bugs</h2>
-<p>When uploading multipart files <code>serve s3</code> holds all the parts in memory (see <a href="https://github.com/rclone/rclone/issues/7453">#7453</a>). This is a limitaton of the library rclone uses for serving S3 and will hopefully be fixed at some point.</p>
-<p>Multipart server side copies do not work (see <a href="https://github.com/rclone/rclone/issues/7454">#7454</a>). These take a very long time and eventually fail. The default threshold for multipart server side copies is 5G which is the maximum it can be, so files above this side will fail to be server side copied.</p>
-<p>For a current list of <code>serve s3</code> bugs see the <a href="https://github.com/rclone/rclone/labels/serve%20s3">serve s3</a> bug category on GitHub.</p>
+<p>When uploading multipart files <code>serve s3</code> holds all the
+parts in memory (see <a
+href="https://github.com/rclone/rclone/issues/7453">#7453</a>). This is
+a limitaton of the library rclone uses for serving S3 and will hopefully
+be fixed at some point.</p>
+<p>Multipart server side copies do not work (see <a
+href="https://github.com/rclone/rclone/issues/7454">#7454</a>). These
+take a very long time and eventually fail. The default threshold for
+multipart server side copies is 5G which is the maximum it can be, so
+files above this side will fail to be server side copied.</p>
+<p>For a current list of <code>serve s3</code> bugs see the <a
+href="https://github.com/rclone/rclone/labels/serve%20s3">serve s3</a>
+bug category on GitHub.</p>
 <h2 id="limitations-2">Limitations</h2>
-<p><code>serve s3</code> will treat all directories in the root as buckets and ignore all files in the root. You can use <code>CreateBucket</code> to create folders under the root, but you can't create empty folders under other folders not in the root.</p>
-<p>When using <code>PutObject</code> or <code>DeleteObject</code>, rclone will automatically create or clean up empty folders. If you don't want to clean up empty folders automatically, use <code>--no-cleanup</code>.</p>
-<p>When using <code>ListObjects</code>, rclone will use <code>/</code> when the delimiter is empty. This reduces backend requests with no effect on most operations, but if the delimiter is something other than <code>/</code> and empty, rclone will do a full recursive search of the backend, which can take some time.</p>
+<p><code>serve s3</code> will treat all directories in the root as
+buckets and ignore all files in the root. You can use
+<code>CreateBucket</code> to create folders under the root, but you
+can't create empty folders under other folders not in the root.</p>
+<p>When using <code>PutObject</code> or <code>DeleteObject</code>,
+rclone will automatically create or clean up empty folders. If you don't
+want to clean up empty folders automatically, use
+<code>--no-cleanup</code>.</p>
+<p>When using <code>ListObjects</code>, rclone will use <code>/</code>
+when the delimiter is empty. This reduces backend requests with no
+effect on most operations, but if the delimiter is something other than
+<code>/</code> and empty, rclone will do a full recursive search of the
+backend, which can take some time.</p>
 <p>Versioning is not currently supported.</p>
-<p>Metadata will only be saved in memory other than the rclone <code>mtime</code> metadata which will be set as the modification time of the file.</p>
+<p>Metadata will only be saved in memory other than the rclone
+<code>mtime</code> metadata which will be set as the modification time
+of the file.</p>
 <h2 id="supported-operations">Supported operations</h2>
-<p><code>serve s3</code> currently supports the following operations.</p>
+<p><code>serve s3</code> currently supports the following
+operations.</p>
 <ul>
 <li>Bucket
 <ul>
@@ -5593,57 +9555,128 @@ use_multipart_uploads = false</code></pre>
 <p>Other operations will return error <code>Unimplemented</code>.</p>
 <h3 id="authentication-3">Authentication</h3>
 <p>By default this will serve files without needing a login.</p>
-<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--user</code> and <code>--pass</code> flags.</p>
-<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
-<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
+<p>You can either use an htpasswd file which can take lots of users, or
+set a single username and password with the <code>--user</code> and
+<code>--pass</code> flags.</p>
+<p>If no static users are configured by either of the above methods, and
+client certificates are required by the <code>--client-ca</code> flag
+passed to the server, the client certificate common name will be
+considered as the username.</p>
+<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd
+file. This is in standard apache format and supports MD5, SHA1 and
+BCrypt for basic authentication. Bcrypt is recommended.</p>
 <p>To create an htpasswd file:</p>
 <pre><code>touch htpasswd
 htpasswd -B htpasswd user
 htpasswd -B htpasswd anotherUser</code></pre>
 <p>The password file can be updated while rclone is running.</p>
 <p>Use <code>--realm</code> to set the authentication realm.</p>
-<p>Use <code>--salt</code> to change the password hashing salt from the default.</p>
+<p>Use <code>--salt</code> to change the password hashing salt from the
+default.</p>
 <h2 id="server-options-5">Server options</h2>
-<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, eg <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
-<p>If you set <code>--addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
-<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
-<p><code>--addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
-<p><code>--server-read-timeout</code> and <code>--server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
-<p><code>--max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
-<p><code>--baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--baseurl</code>, so <code>--baseurl "rclone"</code>, <code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code> are all treated identically.</p>
+<p>Use <code>--addr</code> to specify which IP address and port the
+server should listen on, eg <code>--addr 1.2.3.4:8000</code> or
+<code>--addr :8080</code> to listen to all IPs. By default it only
+listens on localhost. You can use port :0 to let the OS choose an
+available port.</p>
+<p>If you set <code>--addr</code> to listen on a public or LAN
+accessible IP address then using Authentication is advised - see the
+next section for info.</p>
+<p>You can use a unix socket by setting the url to
+<code>unix:///path/to/socket</code> or just by using an absolute path
+name. Note that unix sockets bypass the authentication - this is
+expected to be done with file system permissions.</p>
+<p><code>--addr</code> may be repeated to listen on multiple
+IPs/ports/sockets. Socket activation, described further below, can also
+be used to accomplish the same.</p>
+<p><code>--server-read-timeout</code> and
+<code>--server-write-timeout</code> can be used to control the timeouts
+on the server. Note that this is the total time for a transfer.</p>
+<p><code>--max-header-bytes</code> controls the maximum number of bytes
+the server will accept in the HTTP header.</p>
+<p><code>--baseurl</code> controls the URL prefix that rclone serves
+from. By default rclone will serve from the root. If you used
+<code>--baseurl "/rclone"</code> then rclone would serve from a URL
+starting with "/rclone/". This is useful if you wish to proxy rclone
+serve. Rclone automatically inserts leading and trailing "/" on
+<code>--baseurl</code>, so <code>--baseurl "rclone"</code>,
+<code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code>
+are all treated identically.</p>
 <h3 id="tls-ssl-3">TLS (SSL)</h3>
-<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--cert</code> and <code>--key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--client-ca</code> also.</p>
-<p><code>--cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--key</code> should be the PEM encoded private key and <code>--client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
-<p><code>--min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
+<p>By default this will serve over http. If you want you can serve over
+https. You will need to supply the <code>--cert</code> and
+<code>--key</code> flags. If you wish to do client side certificate
+validation then you will need to supply <code>--client-ca</code>
+also.</p>
+<p><code>--cert</code> should be a either a PEM encoded certificate or a
+concatenation of that with the CA certificate. <code>--key</code> should
+be the PEM encoded private key and <code>--client-ca</code> should be
+the PEM encoded client certificate authority certificate.</p>
+<p><code>--min-tls-version</code> is minimum TLS version that is
+acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3"
+(default "tls1.0").</p>
 <h2 id="socket-activation-3">Socket activation</h2>
-<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --addr`).</p>
-<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
-<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
+<p>Instead of the listening addresses specified above, rclone will
+listen to all FDs passed by the service manager, if any (and ignore any
+arguments passed by --addr`).</p>
+<p>This allows rclone to be a socket-activated service. It can be
+configured with .socket and .service unit files as described in
+https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
+<p>Socket activation can be tested ad-hoc with the
+<code>systemd-socket-activate</code>command</p>
 <pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
-<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ## VFS - Virtual File System</p>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This will socket-activate rclone on the first connection to port 8000
+over TCP. ## VFS - Virtual File System</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-7">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-7">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-7">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -5651,26 +9684,59 @@ htpasswd -B htpasswd anotherUser</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-7">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-7">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -5679,76 +9745,208 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-7">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-7">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-7">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-7">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-14"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-14"><code>--vfs-read-chunk-streams</code>
+== 0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-15"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-15"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-7">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-7">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-7">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-7">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-7">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <pre><code>rclone serve s3 remote:path [flags]</code></pre>
 <h2 id="options-77">Options</h2>
 <pre><code>      --addr stringArray                       IPaddress:Port, :Port or [unix://]/path/to/socket to bind server to (default [127.0.0.1:8080])
@@ -5801,7 +9999,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
       --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-28">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -5828,53 +10028,121 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-77">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-serve-sftp">rclone serve sftp</h1>
 <p>Serve the remote over SFTP.</p>
 <h2 id="synopsis-70">Synopsis</h2>
-<p>Run an SFTP server to serve a remote over SFTP. This can be used with an SFTP client or you can make a remote of type <a href="/sftp">sftp</a> to use with it.</p>
-<p>You can use the <a href="/filtering">filter</a> flags (e.g. <code>--include</code>, <code>--exclude</code>) to control what is served.</p>
-<p>The server will respond to a small number of shell commands, mainly md5sum, sha1sum and df, which enable it to provide support for checksums and the about feature when accessed from an sftp remote.</p>
-<p>Note that this server uses standard 32 KiB packet payload size, which means you must not configure the client to expect anything else, e.g. with the <a href="https://rclone.org/sftp/#sftp-chunk-size">chunk_size</a> option on an sftp remote.</p>
-<p>The server will log errors. Use <code>-v</code> to see access logs.</p>
-<p><code>--bwlimit</code> will be respected for file transfers. Use <code>--stats</code> to control the stats printing.</p>
-<p>You must provide some means of authentication, either with <code>--user</code>/<code>--pass</code>, an authorized keys file (specify location with <code>--authorized-keys</code> - the default is the same as ssh), an <code>--auth-proxy</code>, or set the <code>--no-auth</code> flag for no authentication when logging in.</p>
-<p>If you don't supply a host <code>--key</code> then rclone will generate rsa, ecdsa and ed25519 variants, and cache them for later use in rclone's cache directory (see <code>rclone help flags cache-dir</code>) in the "serve-sftp" directory.</p>
-<p>By default the server binds to localhost:2022 - if you want it to be reachable externally then supply <code>--addr :2022</code> for example.</p>
-<p>This also supports being run with socket activation, in which case it will listen on the first passed FD. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
-<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command:</p>
+<p>Run an SFTP server to serve a remote over SFTP. This can be used with
+an SFTP client or you can make a remote of type <a href="/sftp">sftp</a>
+to use with it.</p>
+<p>You can use the <a href="/filtering">filter</a> flags (e.g.
+<code>--include</code>, <code>--exclude</code>) to control what is
+served.</p>
+<p>The server will respond to a small number of shell commands, mainly
+md5sum, sha1sum and df, which enable it to provide support for checksums
+and the about feature when accessed from an sftp remote.</p>
+<p>Note that this server uses standard 32 KiB packet payload size, which
+means you must not configure the client to expect anything else, e.g.
+with the <a
+href="https://rclone.org/sftp/#sftp-chunk-size">chunk_size</a> option on
+an sftp remote.</p>
+<p>The server will log errors. Use <code>-v</code> to see access
+logs.</p>
+<p><code>--bwlimit</code> will be respected for file transfers. Use
+<code>--stats</code> to control the stats printing.</p>
+<p>You must provide some means of authentication, either with
+<code>--user</code>/<code>--pass</code>, an authorized keys file
+(specify location with <code>--authorized-keys</code> - the default is
+the same as ssh), an <code>--auth-proxy</code>, or set the
+<code>--no-auth</code> flag for no authentication when logging in.</p>
+<p>If you don't supply a host <code>--key</code> then rclone will
+generate rsa, ecdsa and ed25519 variants, and cache them for later use
+in rclone's cache directory (see
+<code>rclone help flags cache-dir</code>) in the "serve-sftp"
+directory.</p>
+<p>By default the server binds to localhost:2022 - if you want it to be
+reachable externally then supply <code>--addr :2022</code> for
+example.</p>
+<p>This also supports being run with socket activation, in which case it
+will listen on the first passed FD. It can be configured with .socket
+and .service unit files as described in
+https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
+<p>Socket activation can be tested ad-hoc with the
+<code>systemd-socket-activate</code>command:</p>
 <pre><code>systemd-socket-activate -l 2222 -- rclone serve sftp :local:vfs/</code></pre>
-<p>This will socket-activate rclone on the first connection to port 2222 over TCP.</p>
-<p>Note that the default of <code>--vfs-cache-mode off</code> is fine for the rclone sftp backend, but it may not be with other SFTP clients.</p>
-<p>If <code>--stdio</code> is specified, rclone will serve SFTP over stdio, which can be used with sshd via ~/.ssh/authorized_keys, for example:</p>
+<p>This will socket-activate rclone on the first connection to port 2222
+over TCP.</p>
+<p>Note that the default of <code>--vfs-cache-mode off</code> is fine
+for the rclone sftp backend, but it may not be with other SFTP
+clients.</p>
+<p>If <code>--stdio</code> is specified, rclone will serve SFTP over
+stdio, which can be used with sshd via ~/.ssh/authorized_keys, for
+example:</p>
 <pre><code>restrict,command=&quot;rclone serve sftp --stdio ./photos&quot; ssh-rsa ...</code></pre>
-<p>On the client you need to set <code>--transfers 1</code> when using <code>--stdio</code>. Otherwise multiple instances of the rclone server are started by OpenSSH which can lead to "corrupted on transfer" errors. This is the case because the client chooses indiscriminately which server to send commands to while the servers all have different views of the state of the filing system.</p>
-<p>The "restrict" in authorized_keys prevents SHA1SUMs and MD5SUMs from being used. Omitting "restrict" and using <code>--sftp-path-override</code> to enable checksumming is possible but less secure and you could use the SFTP server provided by OpenSSH in this case.</p>
+<p>On the client you need to set <code>--transfers 1</code> when using
+<code>--stdio</code>. Otherwise multiple instances of the rclone server
+are started by OpenSSH which can lead to "corrupted on transfer" errors.
+This is the case because the client chooses indiscriminately which
+server to send commands to while the servers all have different views of
+the state of the filing system.</p>
+<p>The "restrict" in authorized_keys prevents SHA1SUMs and MD5SUMs from
+being used. Omitting "restrict" and using
+<code>--sftp-path-override</code> to enable checksumming is possible but
+less secure and you could use the SFTP server provided by OpenSSH in
+this case.</p>
 <h2 id="vfs---virtual-file-system-7">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-8">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-8">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-8">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -5882,26 +10150,59 @@ htpasswd -B htpasswd anotherUser</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-8">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-8">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -5910,89 +10211,239 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-8">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-8">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-8">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-8">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-16"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-16"><code>--vfs-read-chunk-streams</code>
+== 0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-17"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-17"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-8">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-8">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-8">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-8">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-8">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <h2 id="auth-proxy-2">Auth Proxy</h2>
-<p>If you supply the parameter <code>--auth-proxy /path/to/program</code> then rclone will use that program to generate backends on the fly which then are used to authenticate incoming requests. This uses a simple JSON based protocol with input on STDIN and output on STDOUT.</p>
-<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and <code>--authorized-keys</code> cannot be used together, if <code>--auth-proxy</code> is set the authorized keys option will be ignored.</p>
-<p>There is an example program <a href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a> in the rclone source code.</p>
-<p>The program's job is to take a <code>user</code> and <code>pass</code> on the input and turn those into the config for a backend on STDOUT in JSON format. This config will have any default parameters for the backend added, but it won't use configuration from environment variables or command line options - it is the job of the proxy program to make a complete config.</p>
-<p>This config generated must have this extra parameter - <code>_root</code> - root to use for the backend</p>
-<p>And it may have this parameter - <code>_obscure</code> - comma separated strings for parameters to obscure</p>
-<p>If password authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
+<p>If you supply the parameter
+<code>--auth-proxy /path/to/program</code> then rclone will use that
+program to generate backends on the fly which then are used to
+authenticate incoming requests. This uses a simple JSON based protocol
+with input on STDIN and output on STDOUT.</p>
+<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and
+<code>--authorized-keys</code> cannot be used together, if
+<code>--auth-proxy</code> is set the authorized keys option will be
+ignored.</p>
+<p>There is an example program <a
+href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a>
+in the rclone source code.</p>
+<p>The program's job is to take a <code>user</code> and
+<code>pass</code> on the input and turn those into the config for a
+backend on STDOUT in JSON format. This config will have any default
+parameters for the backend added, but it won't use configuration from
+environment variables or command line options - it is the job of the
+proxy program to make a complete config.</p>
+<p>This config generated must have this extra parameter -
+<code>_root</code> - root to use for the backend</p>
+<p>And it may have this parameter - <code>_obscure</code> - comma
+separated strings for parameters to obscure</p>
+<p>If password authentication was used by the client, input to the proxy
+process (on STDIN) would look similar to this:</p>
 <pre><code>{
     &quot;user&quot;: &quot;me&quot;,
     &quot;pass&quot;: &quot;mypassword&quot;
 }</code></pre>
-<p>If public-key authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
+<p>If public-key authentication was used by the client, input to the
+proxy process (on STDIN) would look similar to this:</p>
 <pre><code>{
     &quot;user&quot;: &quot;me&quot;,
     &quot;public_key&quot;: &quot;AAAAB3NzaC1yc2EAAAADAQABAAABAQDuwESFdAe14hVS6omeyX7edc...JQdf&quot;
@@ -6006,10 +10457,25 @@ htpasswd -B htpasswd anotherUser</code></pre>
     &quot;pass&quot;: &quot;mypassword&quot;,
     &quot;host&quot;: &quot;sftp.example.com&quot;
 }</code></pre>
-<p>This would mean that an SFTP backend would be created on the fly for the <code>user</code> and <code>pass</code>/<code>public_key</code> returned in the output to the host given. Note that since <code>_obscure</code> is set to <code>pass</code>, rclone will obscure the <code>pass</code> parameter before creating the backend (which is required for sftp backends).</p>
-<p>The program can manipulate the supplied <code>user</code> in any way, for example to make proxy to many different sftp backends, you could make the <code>user</code> be <code>user@example.com</code> and then set the <code>host</code> to <code>example.com</code> in the output and the user to <code>user</code>. For security you'd probably want to restrict the <code>host</code> to a limited list.</p>
-<p>Note that an internal cache is keyed on <code>user</code> so only use that for configuration, don't use <code>pass</code> or <code>public_key</code>. This also means that if a user's password or public-key is changed the cache will need to expire (which takes 5 mins) before it takes effect.</p>
-<p>This can be used to build general purpose proxies to any kind of backend that rclone supports.</p>
+<p>This would mean that an SFTP backend would be created on the fly for
+the <code>user</code> and <code>pass</code>/<code>public_key</code>
+returned in the output to the host given. Note that since
+<code>_obscure</code> is set to <code>pass</code>, rclone will obscure
+the <code>pass</code> parameter before creating the backend (which is
+required for sftp backends).</p>
+<p>The program can manipulate the supplied <code>user</code> in any way,
+for example to make proxy to many different sftp backends, you could
+make the <code>user</code> be <code>user@example.com</code> and then set
+the <code>host</code> to <code>example.com</code> in the output and the
+user to <code>user</code>. For security you'd probably want to restrict
+the <code>host</code> to a limited list.</p>
+<p>Note that an internal cache is keyed on <code>user</code> so only use
+that for configuration, don't use <code>pass</code> or
+<code>public_key</code>. This also means that if a user's password or
+public-key is changed the cache will need to expire (which takes 5 mins)
+before it takes effect.</p>
+<p>This can be used to build general purpose proxies to any kind of
+backend that rclone supports.</p>
 <pre><code>rclone serve sftp remote:path [flags]</code></pre>
 <h2 id="options-78">Options</h2>
 <pre><code>      --addr string                            IPaddress:Port or :Port to bind server to (default &quot;localhost:2022&quot;)
@@ -6050,7 +10516,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
       --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-29">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -6077,46 +10545,111 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-78">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-serve-webdav">rclone serve webdav</h1>
 <p>Serve remote:path over WebDAV.</p>
 <h2 id="synopsis-71">Synopsis</h2>
-<p>Run a basic WebDAV server to serve a remote over HTTP via the WebDAV protocol. This can be viewed with a WebDAV client, through a web browser, or you can make a remote of type WebDAV to read and write it.</p>
+<p>Run a basic WebDAV server to serve a remote over HTTP via the WebDAV
+protocol. This can be viewed with a WebDAV client, through a web
+browser, or you can make a remote of type WebDAV to read and write
+it.</p>
 <h2 id="webdav-options">WebDAV options</h2>
 <h3 id="etag-hash">--etag-hash</h3>
-<p>This controls the ETag header. Without this flag the ETag will be based on the ModTime and Size of the object.</p>
-<p>If this flag is set to "auto" then rclone will choose the first supported hash on the backend or you can use a named hash such as "MD5" or "SHA-1". Use the <a href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command to see the full list.</p>
+<p>This controls the ETag header. Without this flag the ETag will be
+based on the ModTime and Size of the object.</p>
+<p>If this flag is set to "auto" then rclone will choose the first
+supported hash on the backend or you can use a named hash such as "MD5"
+or "SHA-1". Use the <a
+href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command
+to see the full list.</p>
 <h2 id="access-webdav-on-windows">Access WebDAV on Windows</h2>
-<p>WebDAV shared folder can be mapped as a drive on Windows, however the default settings prevent it. Windows will fail to connect to the server using insecure Basic authentication. It will not even display any login dialog. Windows requires SSL / HTTPS connection to be used with Basic. If you try to connect via Add Network Location Wizard you will get the following error: "The folder you entered does not appear to be valid. Please choose another". However, you still can connect if you set the following registry key on a client machine: HKEY_LOCAL_MACHINEto 2. The BasicAuthLevel can be set to the following values: 0 - Basic authentication disabled 1 - Basic authentication enabled for SSL connections only 2 - Basic authentication enabled for SSL connections and for non-SSL connections If required, increase the FileSizeLimitInBytes to a higher value. Navigate to the Services interface, then restart the WebClient service.</p>
-<h2 id="access-office-applications-on-webdav">Access Office applications on WebDAV</h2>
-<p>Navigate to following registry HKEY_CURRENT_USER[14.0/15.0/16.0] Create a new DWORD BasicAuthLevel with value 2. 0 - Basic authentication disabled 1 - Basic authentication enabled for SSL connections only 2 - Basic authentication enabled for SSL and for non-SSL connections</p>
+<p>WebDAV shared folder can be mapped as a drive on Windows, however the
+default settings prevent it. Windows will fail to connect to the server
+using insecure Basic authentication. It will not even display any login
+dialog. Windows requires SSL / HTTPS connection to be used with Basic.
+If you try to connect via Add Network Location Wizard you will get the
+following error: "The folder you entered does not appear to be valid.
+Please choose another". However, you still can connect if you set the
+following registry key on a client machine: HKEY_LOCAL_MACHINEto 2. The
+BasicAuthLevel can be set to the following values: 0 - Basic
+authentication disabled 1 - Basic authentication enabled for SSL
+connections only 2 - Basic authentication enabled for SSL connections
+and for non-SSL connections If required, increase the
+FileSizeLimitInBytes to a higher value. Navigate to the Services
+interface, then restart the WebClient service.</p>
+<h2 id="access-office-applications-on-webdav">Access Office applications
+on WebDAV</h2>
+<p>Navigate to following registry HKEY_CURRENT_USER[14.0/15.0/16.0]
+Create a new DWORD BasicAuthLevel with value 2. 0 - Basic authentication
+disabled 1 - Basic authentication enabled for SSL connections only 2 -
+Basic authentication enabled for SSL and for non-SSL connections</p>
 <p>https://learn.microsoft.com/en-us/office/troubleshoot/powerpoint/office-opens-blank-from-sharepoint</p>
 <h2 id="serving-over-a-unix-socket">Serving over a unix socket</h2>
 <p>You can serve the webdav on a unix socket like this:</p>
 <pre><code>rclone serve webdav --addr unix:///tmp/my.socket remote:path</code></pre>
 <p>and connect to it like this using rclone and the webdav backend:</p>
 <pre><code>rclone --webdav-unix-socket /tmp/my.socket --webdav-url http://localhost lsf :webdav:</code></pre>
-<p>Note that there is no authentication on http protocol - this is expected to be done by the permissions on the socket.</p>
+<p>Note that there is no authentication on http protocol - this is
+expected to be done by the permissions on the socket.</p>
 <h2 id="server-options-6">Server options</h2>
-<p>Use <code>--addr</code> to specify which IP address and port the server should listen on, eg <code>--addr 1.2.3.4:8000</code> or <code>--addr :8080</code> to listen to all IPs. By default it only listens on localhost. You can use port :0 to let the OS choose an available port.</p>
-<p>If you set <code>--addr</code> to listen on a public or LAN accessible IP address then using Authentication is advised - see the next section for info.</p>
-<p>You can use a unix socket by setting the url to <code>unix:///path/to/socket</code> or just by using an absolute path name. Note that unix sockets bypass the authentication - this is expected to be done with file system permissions.</p>
-<p><code>--addr</code> may be repeated to listen on multiple IPs/ports/sockets. Socket activation, described further below, can also be used to accomplish the same.</p>
-<p><code>--server-read-timeout</code> and <code>--server-write-timeout</code> can be used to control the timeouts on the server. Note that this is the total time for a transfer.</p>
-<p><code>--max-header-bytes</code> controls the maximum number of bytes the server will accept in the HTTP header.</p>
-<p><code>--baseurl</code> controls the URL prefix that rclone serves from. By default rclone will serve from the root. If you used <code>--baseurl "/rclone"</code> then rclone would serve from a URL starting with "/rclone/". This is useful if you wish to proxy rclone serve. Rclone automatically inserts leading and trailing "/" on <code>--baseurl</code>, so <code>--baseurl "rclone"</code>, <code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code> are all treated identically.</p>
+<p>Use <code>--addr</code> to specify which IP address and port the
+server should listen on, eg <code>--addr 1.2.3.4:8000</code> or
+<code>--addr :8080</code> to listen to all IPs. By default it only
+listens on localhost. You can use port :0 to let the OS choose an
+available port.</p>
+<p>If you set <code>--addr</code> to listen on a public or LAN
+accessible IP address then using Authentication is advised - see the
+next section for info.</p>
+<p>You can use a unix socket by setting the url to
+<code>unix:///path/to/socket</code> or just by using an absolute path
+name. Note that unix sockets bypass the authentication - this is
+expected to be done with file system permissions.</p>
+<p><code>--addr</code> may be repeated to listen on multiple
+IPs/ports/sockets. Socket activation, described further below, can also
+be used to accomplish the same.</p>
+<p><code>--server-read-timeout</code> and
+<code>--server-write-timeout</code> can be used to control the timeouts
+on the server. Note that this is the total time for a transfer.</p>
+<p><code>--max-header-bytes</code> controls the maximum number of bytes
+the server will accept in the HTTP header.</p>
+<p><code>--baseurl</code> controls the URL prefix that rclone serves
+from. By default rclone will serve from the root. If you used
+<code>--baseurl "/rclone"</code> then rclone would serve from a URL
+starting with "/rclone/". This is useful if you wish to proxy rclone
+serve. Rclone automatically inserts leading and trailing "/" on
+<code>--baseurl</code>, so <code>--baseurl "rclone"</code>,
+<code>--baseurl "/rclone"</code> and <code>--baseurl "/rclone/"</code>
+are all treated identically.</p>
 <h3 id="tls-ssl-4">TLS (SSL)</h3>
-<p>By default this will serve over http. If you want you can serve over https. You will need to supply the <code>--cert</code> and <code>--key</code> flags. If you wish to do client side certificate validation then you will need to supply <code>--client-ca</code> also.</p>
-<p><code>--cert</code> should be a either a PEM encoded certificate or a concatenation of that with the CA certificate. <code>--key</code> should be the PEM encoded private key and <code>--client-ca</code> should be the PEM encoded client certificate authority certificate.</p>
-<p><code>--min-tls-version</code> is minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
+<p>By default this will serve over http. If you want you can serve over
+https. You will need to supply the <code>--cert</code> and
+<code>--key</code> flags. If you wish to do client side certificate
+validation then you will need to supply <code>--client-ca</code>
+also.</p>
+<p><code>--cert</code> should be a either a PEM encoded certificate or a
+concatenation of that with the CA certificate. <code>--key</code> should
+be the PEM encoded private key and <code>--client-ca</code> should be
+the PEM encoded client certificate authority certificate.</p>
+<p><code>--min-tls-version</code> is minimum TLS version that is
+acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3"
+(default "tls1.0").</p>
 <h2 id="socket-activation-4">Socket activation</h2>
-<p>Instead of the listening addresses specified above, rclone will listen to all FDs passed by the service manager, if any (and ignore any arguments passed by --addr`).</p>
-<p>This allows rclone to be a socket-activated service. It can be configured with .socket and .service unit files as described in https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
-<p>Socket activation can be tested ad-hoc with the <code>systemd-socket-activate</code>command</p>
+<p>Instead of the listening addresses specified above, rclone will
+listen to all FDs passed by the service manager, if any (and ignore any
+arguments passed by --addr`).</p>
+<p>This allows rclone to be a socket-activated service. It can be
+configured with .socket and .service unit files as described in
+https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html</p>
+<p>Socket activation can be tested ad-hoc with the
+<code>systemd-socket-activate</code>command</p>
 <pre><code>   systemd-socket-activate -l 8000 -- rclone serve</code></pre>
-<p>This will socket-activate rclone on the first connection to port 8000 over TCP. ### Template</p>
-<p><code>--template</code> allows a user to specify a custom markup template for HTTP and WebDAV serve functions. The server exports the following markup to be used within the template to server pages:</p>
+<p>This will socket-activate rclone on the first connection to port 8000
+over TCP. ### Template</p>
+<p><code>--template</code> allows a user to specify a custom markup
+template for HTTP and WebDAV serve functions. The server exports the
+following markup to be used within the template to server pages:</p>
 <table>
 <colgroup>
 <col style="width: 50%" />
@@ -6139,15 +10672,18 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Sort</td>
-<td style="text-align: left;">The current sort used. This is changeable via ?sort= parameter</td>
+<td style="text-align: left;">The current sort used. This is changeable
+via ?sort= parameter</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;"></td>
-<td style="text-align: left;">Sort Options: namedirfirst,name,size,time (default namedirfirst)</td>
+<td style="text-align: left;">Sort Options: namedirfirst,name,size,time
+(default namedirfirst)</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Order</td>
-<td style="text-align: left;">The current ordering used. This is changeable via ?order= parameter</td>
+<td style="text-align: left;">The current ordering used. This is
+changeable via ?order= parameter</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;"></td>
@@ -6159,11 +10695,13 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 <tr class="even">
 <td style="text-align: left;">.Breadcrumb</td>
-<td style="text-align: left;">Allows for creating a relative navigation</td>
+<td style="text-align: left;">Allows for creating a relative
+navigation</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Link</td>
-<td style="text-align: left;">The relative to the root link of the Text.</td>
+<td style="text-align: left;">The relative to the root link of the
+Text.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .Text</td>
@@ -6171,7 +10709,8 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">.Entries</td>
-<td style="text-align: left;">Information about a specific file/directory.</td>
+<td style="text-align: left;">Information about a specific
+file/directory.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .URL</td>
@@ -6179,11 +10718,13 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Leaf</td>
-<td style="text-align: left;">Currently same as 'URL' but intended to be 'just' the name.</td>
+<td style="text-align: left;">Currently same as 'URL' but intended to be
+'just' the name.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">-- .IsDir</td>
-<td style="text-align: left;">Boolean for if an entry is a directory or not.</td>
+<td style="text-align: left;">Boolean for if an entry is a directory or
+not.</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">-- .Size</td>
@@ -6195,7 +10736,10 @@ htpasswd -B htpasswd anotherUser</code></pre>
 </tr>
 </tbody>
 </table>
-<p>The server also makes the following functions available so that they can be used within the template. These functions help extend the options for dynamic rendering of HTML. They can be used to render HTML based on specific conditions.</p>
+<p>The server also makes the following functions available so that they
+can be used within the template. These functions help extend the options
+for dynamic rendering of HTML. They can be used to render HTML based on
+specific conditions.</p>
 <table>
 <colgroup>
 <col style="width: 50%" />
@@ -6210,58 +10754,97 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <tbody>
 <tr class="odd">
 <td style="text-align: left;">afterEpoch</td>
-<td style="text-align: left;">Returns the time since the epoch for the given time.</td>
+<td style="text-align: left;">Returns the time since the epoch for the
+given time.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">contains</td>
-<td style="text-align: left;">Checks whether a given substring is present or not in a given string.</td>
+<td style="text-align: left;">Checks whether a given substring is
+present or not in a given string.</td>
 </tr>
 <tr class="odd">
 <td style="text-align: left;">hasPrefix</td>
-<td style="text-align: left;">Checks whether the given string begins with the specified prefix.</td>
+<td style="text-align: left;">Checks whether the given string begins
+with the specified prefix.</td>
 </tr>
 <tr class="even">
 <td style="text-align: left;">hasSuffix</td>
-<td style="text-align: left;">Checks whether the given string end with the specified suffix.</td>
+<td style="text-align: left;">Checks whether the given string end with
+the specified suffix.</td>
 </tr>
 </tbody>
 </table>
 <h3 id="authentication-4">Authentication</h3>
 <p>By default this will serve files without needing a login.</p>
-<p>You can either use an htpasswd file which can take lots of users, or set a single username and password with the <code>--user</code> and <code>--pass</code> flags.</p>
-<p>If no static users are configured by either of the above methods, and client certificates are required by the <code>--client-ca</code> flag passed to the server, the client certificate common name will be considered as the username.</p>
-<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd file. This is in standard apache format and supports MD5, SHA1 and BCrypt for basic authentication. Bcrypt is recommended.</p>
+<p>You can either use an htpasswd file which can take lots of users, or
+set a single username and password with the <code>--user</code> and
+<code>--pass</code> flags.</p>
+<p>If no static users are configured by either of the above methods, and
+client certificates are required by the <code>--client-ca</code> flag
+passed to the server, the client certificate common name will be
+considered as the username.</p>
+<p>Use <code>--htpasswd /path/to/htpasswd</code> to provide an htpasswd
+file. This is in standard apache format and supports MD5, SHA1 and
+BCrypt for basic authentication. Bcrypt is recommended.</p>
 <p>To create an htpasswd file:</p>
 <pre><code>touch htpasswd
 htpasswd -B htpasswd user
 htpasswd -B htpasswd anotherUser</code></pre>
 <p>The password file can be updated while rclone is running.</p>
 <p>Use <code>--realm</code> to set the authentication realm.</p>
-<p>Use <code>--salt</code> to change the password hashing salt from the default.</p>
+<p>Use <code>--salt</code> to change the password hashing salt from the
+default.</p>
 <h2 id="vfs---virtual-file-system-8">VFS - Virtual File System</h2>
-<p>This command uses the VFS layer. This adapts the cloud storage objects that rclone uses into something which looks much more like a disk filing system.</p>
-<p>Cloud storage objects have lots of properties which aren't like disk files - you can't extend them or write to the middle of them, so the VFS layer has to deal with that. Because there is no one right way of doing this there are various options explained below.</p>
-<p>The VFS layer also implements a directory cache - this caches info about files and directories (but not the data) in memory.</p>
+<p>This command uses the VFS layer. This adapts the cloud storage
+objects that rclone uses into something which looks much more like a
+disk filing system.</p>
+<p>Cloud storage objects have lots of properties which aren't like disk
+files - you can't extend them or write to the middle of them, so the VFS
+layer has to deal with that. Because there is no one right way of doing
+this there are various options explained below.</p>
+<p>The VFS layer also implements a directory cache - this caches info
+about files and directories (but not the data) in memory.</p>
 <h2 id="vfs-directory-cache-9">VFS Directory Cache</h2>
-<p>Using the <code>--dir-cache-time</code> flag, you can control how long a directory should be considered up to date and not refreshed from the backend. Changes made through the VFS will appear immediately or invalidate the cache.</p>
+<p>Using the <code>--dir-cache-time</code> flag, you can control how
+long a directory should be considered up to date and not refreshed from
+the backend. Changes made through the VFS will appear immediately or
+invalidate the cache.</p>
 <pre><code>--dir-cache-time duration   Time to cache directory entries for (default 5m0s)
 --poll-interval duration    Time to wait between polling for changes. Must be smaller than dir-cache-time. Only on supported remotes. Set to 0 to disable (default 1m0s)</code></pre>
-<p>However, changes made directly on the cloud storage by the web interface or a different copy of rclone will only be picked up once the directory cache expires if the backend configured does not support polling for changes. If the backend supports polling, changes will be picked up within the polling interval.</p>
-<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush all directory caches, regardless of how old they are. Assuming only one rclone instance is running, you can reset the cache like this:</p>
+<p>However, changes made directly on the cloud storage by the web
+interface or a different copy of rclone will only be picked up once the
+directory cache expires if the backend configured does not support
+polling for changes. If the backend supports polling, changes will be
+picked up within the polling interval.</p>
+<p>You can send a <code>SIGHUP</code> signal to rclone for it to flush
+all directory caches, regardless of how old they are. Assuming only one
+rclone instance is running, you can reset the cache like this:</p>
 <pre><code>kill -SIGHUP $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use rclone rc to flush the whole directory cache:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use rclone rc to flush the whole directory cache:</p>
 <pre><code>rclone rc vfs/forget</code></pre>
 <p>Or individual files or directories:</p>
 <pre><code>rclone rc vfs/forget file=path/to/file dir=path/to/dir</code></pre>
 <h2 id="vfs-file-buffering-9">VFS File Buffering</h2>
-<p>The <code>--buffer-size</code> flag determines the amount of memory, that will be used to buffer data in advance.</p>
-<p>Each open file will try to keep the specified amount of data in memory at all times. The buffered data is bound to one open file and won't be shared.</p>
-<p>This flag is a upper limit for the used memory per open file. The buffer will only use memory for data that is downloaded but not not yet read. If the buffer is empty, only a small amount of memory will be used.</p>
-<p>The maximum memory used by rclone for buffering can be up to <code>--buffer-size * open files</code>.</p>
+<p>The <code>--buffer-size</code> flag determines the amount of memory,
+that will be used to buffer data in advance.</p>
+<p>Each open file will try to keep the specified amount of data in
+memory at all times. The buffered data is bound to one open file and
+won't be shared.</p>
+<p>This flag is a upper limit for the used memory per open file. The
+buffer will only use memory for data that is downloaded but not not yet
+read. If the buffer is empty, only a small amount of memory will be
+used.</p>
+<p>The maximum memory used by rclone for buffering can be up to
+<code>--buffer-size * open files</code>.</p>
 <h2 id="vfs-file-caching-9">VFS File Caching</h2>
-<p>These flags control the VFS file caching options. File caching is necessary to make the VFS layer appear compatible with a normal file system. It can be disabled at the cost of some compatibility.</p>
-<p>For example you'll need to enable VFS caching if you want to read and write simultaneously to a file. See below for more details.</p>
-<p>Note that the VFS cache is separate from the cache backend and you may find that you need one or the other or both.</p>
+<p>These flags control the VFS file caching options. File caching is
+necessary to make the VFS layer appear compatible with a normal file
+system. It can be disabled at the cost of some compatibility.</p>
+<p>For example you'll need to enable VFS caching if you want to read and
+write simultaneously to a file. See below for more details.</p>
+<p>Note that the VFS cache is separate from the cache backend and you
+may find that you need one or the other or both.</p>
 <pre><code>--cache-dir string                     Directory rclone will use for caching.
 --vfs-cache-mode CacheMode             Cache mode off|minimal|writes|full (default off)
 --vfs-cache-max-age duration           Max time since last access of objects in the cache (default 1h0m0s)
@@ -6269,26 +10852,59 @@ htpasswd -B htpasswd anotherUser</code></pre>
 --vfs-cache-min-free-space SizeSuffix  Target minimum free space on the disk containing the cache (default off)
 --vfs-cache-poll-interval duration     Interval to poll the cache for stale objects (default 1m0s)
 --vfs-write-back duration              Time to writeback files after last use when using cache (default 5s)</code></pre>
-<p>If run with <code>-vv</code> rclone will print the location of the file cache. The files are stored in the user cache file area which is OS dependent but can be controlled with <code>--cache-dir</code> or setting the appropriate environment variable.</p>
-<p>The cache has 4 different modes selected by <code>--vfs-cache-mode</code>. The higher the cache mode the more compatible rclone becomes at the cost of using disk space.</p>
-<p>Note that files are written back to the remote only when they are closed and if they haven't been accessed for <code>--vfs-write-back</code> seconds. If rclone is quit or dies with files that haven't been uploaded, these will be uploaded next time rclone is run with the same flags.</p>
-<p>If using <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> note that the cache may exceed these quotas for two reasons. Firstly because it is only checked every <code>--vfs-cache-poll-interval</code>. Secondly because open files cannot be evicted from the cache. When <code>--vfs-cache-max-size</code> or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will attempt to evict the least accessed files from the cache first. rclone will start with files that haven't been accessed for the longest. This cache flushing strategy is efficient and more relevant files are likely to remain cached.</p>
-<p>The <code>--vfs-cache-max-age</code> will evict files from the cache after the set time since last access has passed. The default value of 1 hour will start evicting files from cache that haven't been accessed for 1 hour. When a cached file is accessed the 1 hour timer is reset to 0 and will wait for 1 more hour before evicting. Specify the time with standard notation, s, m, h, d, w .</p>
-<p>You <strong>should not</strong> run two copies of rclone using the same VFS cache with the same or overlapping remotes if using <code>--vfs-cache-mode &gt; off</code>. This can potentially cause data corruption if you do. You can work around this by giving each rclone its own cache hierarchy with <code>--cache-dir</code>. You don't need to worry about this if the remotes in use don't overlap.</p>
+<p>If run with <code>-vv</code> rclone will print the location of the
+file cache. The files are stored in the user cache file area which is OS
+dependent but can be controlled with <code>--cache-dir</code> or setting
+the appropriate environment variable.</p>
+<p>The cache has 4 different modes selected by
+<code>--vfs-cache-mode</code>. The higher the cache mode the more
+compatible rclone becomes at the cost of using disk space.</p>
+<p>Note that files are written back to the remote only when they are
+closed and if they haven't been accessed for
+<code>--vfs-write-back</code> seconds. If rclone is quit or dies with
+files that haven't been uploaded, these will be uploaded next time
+rclone is run with the same flags.</p>
+<p>If using <code>--vfs-cache-max-size</code> or
+<code>--vfs-cache-min-free-size</code> note that the cache may exceed
+these quotas for two reasons. Firstly because it is only checked every
+<code>--vfs-cache-poll-interval</code>. Secondly because open files
+cannot be evicted from the cache. When <code>--vfs-cache-max-size</code>
+or <code>--vfs-cache-min-free-size</code> is exceeded, rclone will
+attempt to evict the least accessed files from the cache first. rclone
+will start with files that haven't been accessed for the longest. This
+cache flushing strategy is efficient and more relevant files are likely
+to remain cached.</p>
+<p>The <code>--vfs-cache-max-age</code> will evict files from the cache
+after the set time since last access has passed. The default value of 1
+hour will start evicting files from cache that haven't been accessed for
+1 hour. When a cached file is accessed the 1 hour timer is reset to 0
+and will wait for 1 more hour before evicting. Specify the time with
+standard notation, s, m, h, d, w .</p>
+<p>You <strong>should not</strong> run two copies of rclone using the
+same VFS cache with the same or overlapping remotes if using
+<code>--vfs-cache-mode &gt; off</code>. This can potentially cause data
+corruption if you do. You can work around this by giving each rclone its
+own cache hierarchy with <code>--cache-dir</code>. You don't need to
+worry about this if the remotes in use don't overlap.</p>
 <h3 id="vfs-cache-mode-off-9">--vfs-cache-mode off</h3>
-<p>In this mode (the default) the cache will read directly from the remote and write directly to the remote without caching anything on disk.</p>
+<p>In this mode (the default) the cache will read directly from the
+remote and write directly to the remote without caching anything on
+disk.</p>
 <p>This will mean some operations are not possible</p>
 <ul>
 <li>Files can't be opened for both read AND write</li>
 <li>Files opened for write can't be seeked</li>
 <li>Existing files opened for write must have O_TRUNC set</li>
 <li>Files open for read with O_TRUNC will be opened write only</li>
-<li>Files open for write only will behave as if O_TRUNC was supplied</li>
+<li>Files open for write only will behave as if O_TRUNC was
+supplied</li>
 <li>Open modes O_APPEND, O_TRUNC are ignored</li>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-minimal-9">--vfs-cache-mode minimal</h3>
-<p>This is very similar to "off" except that files opened for read AND write will be buffered to disk. This means that files opened for write will be a lot more compatible, but uses the minimal disk space.</p>
+<p>This is very similar to "off" except that files opened for read AND
+write will be buffered to disk. This means that files opened for write
+will be a lot more compatible, but uses the minimal disk space.</p>
 <p>These operations are not possible</p>
 <ul>
 <li>Files opened for write only can't be seeked</li>
@@ -6297,89 +10913,239 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <li>If an upload fails it can't be retried</li>
 </ul>
 <h3 id="vfs-cache-mode-writes-9">--vfs-cache-mode writes</h3>
-<p>In this mode files opened for read only are still read directly from the remote, write only and read/write files are buffered to disk first.</p>
+<p>In this mode files opened for read only are still read directly from
+the remote, write only and read/write files are buffered to disk
+first.</p>
 <p>This mode should support all normal file system operations.</p>
-<p>If an upload fails it will be retried at exponentially increasing intervals up to 1 minute.</p>
+<p>If an upload fails it will be retried at exponentially increasing
+intervals up to 1 minute.</p>
 <h3 id="vfs-cache-mode-full-9">--vfs-cache-mode full</h3>
-<p>In this mode all reads and writes are buffered to and from disk. When data is read from the remote this is buffered to disk as well.</p>
-<p>In this mode the files in the cache will be sparse files and rclone will keep track of which bits of the files it has downloaded.</p>
-<p>So if an application only reads the starts of each file, then rclone will only buffer the start of the file. These files will appear to be their full size in the cache, but they will be sparse files with only the data that has been downloaded present in them.</p>
-<p>This mode should support all normal file system operations and is otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
-<p>When reading a file rclone will read <code>--buffer-size</code> plus <code>--vfs-read-ahead</code> bytes ahead. The <code>--buffer-size</code> is buffered in memory whereas the <code>--vfs-read-ahead</code> is buffered on disk.</p>
-<p>When using this mode it is recommended that <code>--buffer-size</code> is not set too large and <code>--vfs-read-ahead</code> is set large if required.</p>
-<p><strong>IMPORTANT</strong> not all file systems support sparse files. In particular FAT/exFAT do not. Rclone will perform very badly if the cache directory is on a filesystem which doesn't support sparse files and it will log an ERROR message if one is detected.</p>
+<p>In this mode all reads and writes are buffered to and from disk. When
+data is read from the remote this is buffered to disk as well.</p>
+<p>In this mode the files in the cache will be sparse files and rclone
+will keep track of which bits of the files it has downloaded.</p>
+<p>So if an application only reads the starts of each file, then rclone
+will only buffer the start of the file. These files will appear to be
+their full size in the cache, but they will be sparse files with only
+the data that has been downloaded present in them.</p>
+<p>This mode should support all normal file system operations and is
+otherwise identical to <code>--vfs-cache-mode</code> writes.</p>
+<p>When reading a file rclone will read <code>--buffer-size</code> plus
+<code>--vfs-read-ahead</code> bytes ahead. The
+<code>--buffer-size</code> is buffered in memory whereas the
+<code>--vfs-read-ahead</code> is buffered on disk.</p>
+<p>When using this mode it is recommended that
+<code>--buffer-size</code> is not set too large and
+<code>--vfs-read-ahead</code> is set large if required.</p>
+<p><strong>IMPORTANT</strong> not all file systems support sparse files.
+In particular FAT/exFAT do not. Rclone will perform very badly if the
+cache directory is on a filesystem which doesn't support sparse files
+and it will log an ERROR message if one is detected.</p>
 <h3 id="fingerprinting-9">Fingerprinting</h3>
-<p>Various parts of the VFS use fingerprinting to see if a local file copy has changed relative to a remote file. Fingerprints are made from:</p>
+<p>Various parts of the VFS use fingerprinting to see if a local file
+copy has changed relative to a remote file. Fingerprints are made
+from:</p>
 <ul>
 <li>size</li>
 <li>modification time</li>
 <li>hash</li>
 </ul>
 <p>where available on an object.</p>
-<p>On some backends some of these attributes are slow to read (they take an extra API call per object, or extra work per object).</p>
-<p>For example <code>hash</code> is slow with the <code>local</code> and <code>sftp</code> backends as they have to read the entire file and hash it, and <code>modtime</code> is slow with the <code>s3</code>, <code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends because they need to do an extra API call to fetch it.</p>
-<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone will not include the slow operations in the fingerprint. This makes the fingerprinting less accurate but much faster and will improve the opening time of cached files.</p>
-<p>If you are running a vfs cache over <code>local</code>, <code>s3</code> or <code>swift</code> backends then using this flag is recommended.</p>
-<p>Note that if you change the value of this flag, the fingerprints of the files in the cache may be invalidated and the files will need to be downloaded again.</p>
+<p>On some backends some of these attributes are slow to read (they take
+an extra API call per object, or extra work per object).</p>
+<p>For example <code>hash</code> is slow with the <code>local</code> and
+<code>sftp</code> backends as they have to read the entire file and hash
+it, and <code>modtime</code> is slow with the <code>s3</code>,
+<code>swift</code>, <code>ftp</code> and <code>qinqstor</code> backends
+because they need to do an extra API call to fetch it.</p>
+<p>If you use the <code>--vfs-fast-fingerprint</code> flag then rclone
+will not include the slow operations in the fingerprint. This makes the
+fingerprinting less accurate but much faster and will improve the
+opening time of cached files.</p>
+<p>If you are running a vfs cache over <code>local</code>,
+<code>s3</code> or <code>swift</code> backends then using this flag is
+recommended.</p>
+<p>Note that if you change the value of this flag, the fingerprints of
+the files in the cache may be invalidated and the files will need to be
+downloaded again.</p>
 <h2 id="vfs-chunked-reading-9">VFS Chunked Reading</h2>
-<p>When rclone reads files from a remote it reads them in chunks. This means that rather than requesting the whole file rclone reads the chunk specified. This can reduce the used download quota for some remotes by requesting only chunks from the remote that are actually read, at the cost of an increased number of requests.</p>
+<p>When rclone reads files from a remote it reads them in chunks. This
+means that rather than requesting the whole file rclone reads the chunk
+specified. This can reduce the used download quota for some remotes by
+requesting only chunks from the remote that are actually read, at the
+cost of an increased number of requests.</p>
 <p>These flags control the chunking:</p>
 <pre><code>--vfs-read-chunk-size SizeSuffix        Read the source objects in chunks (default 128M)
 --vfs-read-chunk-size-limit SizeSuffix  Max chunk doubling size (default off)
 --vfs-read-chunk-streams int            The number of parallel streams to read at once</code></pre>
-<p>The chunking behaves differently depending on the <code>--vfs-read-chunk-streams</code> parameter.</p>
-<h3 id="vfs-read-chunk-streams-0-18"><code>--vfs-read-chunk-streams</code> == 0</h3>
-<p>Rclone will start reading a chunk of size <code>--vfs-read-chunk-size</code>, and then double the size for each read. When <code>--vfs-read-chunk-size-limit</code> is specified, and greater than <code>--vfs-read-chunk-size</code>, the chunk size for each open file will get doubled only until the specified value is reached. If the value is "off", which is the default, the limit is disabled and the chunk size will grow indefinitely.</p>
-<p>With <code>--vfs-read-chunk-size 100M</code> and <code>--vfs-read-chunk-size-limit 0</code> the following parts will be downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When <code>--vfs-read-chunk-size-limit 500M</code> is specified, the result would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so on.</p>
-<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off" disables chunked reading.</p>
+<p>The chunking behaves differently depending on the
+<code>--vfs-read-chunk-streams</code> parameter.</p>
+<h3
+id="vfs-read-chunk-streams-0-18"><code>--vfs-read-chunk-streams</code>
+== 0</h3>
+<p>Rclone will start reading a chunk of size
+<code>--vfs-read-chunk-size</code>, and then double the size for each
+read. When <code>--vfs-read-chunk-size-limit</code> is specified, and
+greater than <code>--vfs-read-chunk-size</code>, the chunk size for each
+open file will get doubled only until the specified value is reached. If
+the value is "off", which is the default, the limit is disabled and the
+chunk size will grow indefinitely.</p>
+<p>With <code>--vfs-read-chunk-size 100M</code> and
+<code>--vfs-read-chunk-size-limit 0</code> the following parts will be
+downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on. When
+<code>--vfs-read-chunk-size-limit 500M</code> is specified, the result
+would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
+on.</p>
+<p>Setting <code>--vfs-read-chunk-size</code> to <code>0</code> or "off"
+disables chunked reading.</p>
 <p>The chunks will not be buffered in memory.</p>
-<h3 id="vfs-read-chunk-streams-0-19"><code>--vfs-read-chunk-streams</code> &gt; 0</h3>
-<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size <code>--vfs-read-chunk-size</code> concurrently. The size for each read will stay constant.</p>
-<p>This improves performance performance massively on high latency links or very high bandwidth links to high performance object stores.</p>
-<p>Some experimentation will be needed to find the optimum values of <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-streams</code> as these will depend on the backend in use and the latency to the backend.</p>
-<p>For high performance object stores (eg AWS S3) a reasonable place to start might be <code>--vfs-read-chunk-streams 16</code> and <code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the performance scaled roughly as the <code>--vfs-read-chunk-streams</code> setting.</p>
-<p>Similar settings should work for high latency links, but depending on the latency they may need more <code>--vfs-read-chunk-streams</code> in order to get the throughput.</p>
+<h3
+id="vfs-read-chunk-streams-0-19"><code>--vfs-read-chunk-streams</code>
+&gt; 0</h3>
+<p>Rclone reads <code>--vfs-read-chunk-streams</code> chunks of size
+<code>--vfs-read-chunk-size</code> concurrently. The size for each read
+will stay constant.</p>
+<p>This improves performance performance massively on high latency links
+or very high bandwidth links to high performance object stores.</p>
+<p>Some experimentation will be needed to find the optimum values of
+<code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-streams</code> as these will depend on the
+backend in use and the latency to the backend.</p>
+<p>For high performance object stores (eg AWS S3) a reasonable place to
+start might be <code>--vfs-read-chunk-streams 16</code> and
+<code>--vfs-read-chunk-size 4M</code>. In testing with AWS S3 the
+performance scaled roughly as the <code>--vfs-read-chunk-streams</code>
+setting.</p>
+<p>Similar settings should work for high latency links, but depending on
+the latency they may need more <code>--vfs-read-chunk-streams</code> in
+order to get the throughput.</p>
 <h2 id="vfs-performance-9">VFS Performance</h2>
-<p>These flags may be used to enable/disable features of the VFS for performance or other reasons. See also the <a href="#vfs-chunked-reading">chunked reading</a> feature.</p>
-<p>In particular S3 and Swift benefit hugely from the <code>--no-modtime</code> flag (or use <code>--use-server-modtime</code> for a slightly different effect) as each read of the modification time takes a transaction.</p>
+<p>These flags may be used to enable/disable features of the VFS for
+performance or other reasons. See also the <a
+href="#vfs-chunked-reading">chunked reading</a> feature.</p>
+<p>In particular S3 and Swift benefit hugely from the
+<code>--no-modtime</code> flag (or use <code>--use-server-modtime</code>
+for a slightly different effect) as each read of the modification time
+takes a transaction.</p>
 <pre><code>--no-checksum     Don&#39;t compare checksums on up/download.
 --no-modtime      Don&#39;t read/write the modification time (can speed things up).
 --no-seek         Don&#39;t allow seeking in files.
 --read-only       Only allow read-only access.</code></pre>
-<p>Sometimes rclone is delivered reads or writes out of order. Rather than seeking rclone will wait a short time for the in sequence read or write to come in. These flags only come into effect when not using an on disk cache file.</p>
+<p>Sometimes rclone is delivered reads or writes out of order. Rather
+than seeking rclone will wait a short time for the in sequence read or
+write to come in. These flags only come into effect when not using an on
+disk cache file.</p>
 <pre><code>--vfs-read-wait duration   Time to wait for in-sequence read before seeking (default 20ms)
 --vfs-write-wait duration  Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>When using VFS write caching (<code>--vfs-cache-mode</code> with value writes or full), the global flag <code>--transfers</code> can be set to adjust the number of parallel uploads of modified files from the cache (the related global flag <code>--checkers</code> has no effect on the VFS).</p>
+<p>When using VFS write caching (<code>--vfs-cache-mode</code> with
+value writes or full), the global flag <code>--transfers</code> can be
+set to adjust the number of parallel uploads of modified files from the
+cache (the related global flag <code>--checkers</code> has no effect on
+the VFS).</p>
 <pre><code>--transfers int  Number of file transfers to run in parallel (default 4)</code></pre>
 <h2 id="vfs-case-sensitivity-9">VFS Case Sensitivity</h2>
-<p>Linux file systems are case-sensitive: two files can differ only by case, and the exact case must be used when opening a file.</p>
-<p>File systems in modern Windows are case-insensitive but case-preserving: although existing files can be opened using any case, the exact case used to create the file is preserved and available for programs to query. It is not allowed for two files in the same directory to differ only by case.</p>
-<p>Usually file systems on macOS are case-insensitive. It is possible to make macOS file systems case-sensitive but that is not the default.</p>
-<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone handles these two cases. If its value is "false", rclone passes file names to the remote as-is. If the flag is "true" (or appears without a value on the command line), rclone may perform a "fixup" as explained below.</p>
-<p>The user may specify a file name to open/delete/rename/etc with a case different than what is stored on the remote. If an argument refers to an existing file with exactly the same name, then the case of the existing file on the disk will be used. However, if a file name with exactly the same name is not found but a name differing only by case exists, rclone will transparently fixup the name. This fixup happens only when an existing file is requested. Case sensitivity of file names created anew by rclone is controlled by the underlying remote.</p>
-<p>Note that case sensitivity of the operating system running rclone (the target) may differ from case sensitivity of a file system presented by rclone (the source). The flag controls whether "fixup" is performed to satisfy the target.</p>
-<p>If the flag is not provided on the command line, then its default value depends on the operating system where rclone runs: "true" on Windows and macOS, "false" otherwise. If the flag is provided without a value, then it is "true".</p>
-<p>The <code>--no-unicode-normalization</code> flag controls whether a similar "fixup" is performed for filenames that differ but are <a href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically equivalent</a> with respect to unicode. Unicode normalization can be particularly helpful for users of macOS, which prefers form NFD instead of the NFC used by most other platforms. It is therefore highly recommended to keep the default of <code>false</code> on macOS, to avoid encoding compatibility issues.</p>
-<p>In the (probably unlikely) event that a directory has multiple duplicate filenames after applying case and unicode normalization, the <code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates. This comes with a performance tradeoff, as rclone will have to scan the entire directory for duplicates when listing a directory. For this reason, it is recommended to leave this disabled if not needed. However, macOS users may wish to consider using it, as otherwise, if a remote directory contains both NFC and NFD versions of the same filename, an odd situation will occur: both versions of the file will be visible in the mount, and both will appear to be editable, however, editing either version will actually result in only the NFD version getting edited under the hood. <code>--vfs-block- norm-dupes</code> prevents this confusion by detecting this scenario, hiding the duplicates, and logging an error, similar to how this is handled in <code>rclone sync</code>.</p>
+<p>Linux file systems are case-sensitive: two files can differ only by
+case, and the exact case must be used when opening a file.</p>
+<p>File systems in modern Windows are case-insensitive but
+case-preserving: although existing files can be opened using any case,
+the exact case used to create the file is preserved and available for
+programs to query. It is not allowed for two files in the same directory
+to differ only by case.</p>
+<p>Usually file systems on macOS are case-insensitive. It is possible to
+make macOS file systems case-sensitive but that is not the default.</p>
+<p>The <code>--vfs-case-insensitive</code> VFS flag controls how rclone
+handles these two cases. If its value is "false", rclone passes file
+names to the remote as-is. If the flag is "true" (or appears without a
+value on the command line), rclone may perform a "fixup" as explained
+below.</p>
+<p>The user may specify a file name to open/delete/rename/etc with a
+case different than what is stored on the remote. If an argument refers
+to an existing file with exactly the same name, then the case of the
+existing file on the disk will be used. However, if a file name with
+exactly the same name is not found but a name differing only by case
+exists, rclone will transparently fixup the name. This fixup happens
+only when an existing file is requested. Case sensitivity of file names
+created anew by rclone is controlled by the underlying remote.</p>
+<p>Note that case sensitivity of the operating system running rclone
+(the target) may differ from case sensitivity of a file system presented
+by rclone (the source). The flag controls whether "fixup" is performed
+to satisfy the target.</p>
+<p>If the flag is not provided on the command line, then its default
+value depends on the operating system where rclone runs: "true" on
+Windows and macOS, "false" otherwise. If the flag is provided without a
+value, then it is "true".</p>
+<p>The <code>--no-unicode-normalization</code> flag controls whether a
+similar "fixup" is performed for filenames that differ but are <a
+href="https://en.wikipedia.org/wiki/Unicode_equivalence">canonically
+equivalent</a> with respect to unicode. Unicode normalization can be
+particularly helpful for users of macOS, which prefers form NFD instead
+of the NFC used by most other platforms. It is therefore highly
+recommended to keep the default of <code>false</code> on macOS, to avoid
+encoding compatibility issues.</p>
+<p>In the (probably unlikely) event that a directory has multiple
+duplicate filenames after applying case and unicode normalization, the
+<code>--vfs-block-norm-dupes</code> flag allows hiding these duplicates.
+This comes with a performance tradeoff, as rclone will have to scan the
+entire directory for duplicates when listing a directory. For this
+reason, it is recommended to leave this disabled if not needed. However,
+macOS users may wish to consider using it, as otherwise, if a remote
+directory contains both NFC and NFD versions of the same filename, an
+odd situation will occur: both versions of the file will be visible in
+the mount, and both will appear to be editable, however, editing either
+version will actually result in only the NFD version getting edited
+under the hood. <code>--vfs-block- norm-dupes</code> prevents this
+confusion by detecting this scenario, hiding the duplicates, and logging
+an error, similar to how this is handled in
+<code>rclone sync</code>.</p>
 <h2 id="vfs-disk-options-9">VFS Disk Options</h2>
-<p>This flag allows you to manually set the statistics about the filing system. It can be useful when those statistics cannot be read correctly automatically.</p>
+<p>This flag allows you to manually set the statistics about the filing
+system. It can be useful when those statistics cannot be read correctly
+automatically.</p>
 <pre><code>--vfs-disk-space-total-size    Manually set the total disk space size (example: 256G, default: -1)</code></pre>
-<h2 id="alternate-report-of-used-bytes-9">Alternate report of used bytes</h2>
-<p>Some backends, most notably S3, do not report the amount of bytes used. If you need this information to be available when running <code>df</code> on the filesystem, then pass the flag <code>--vfs-used-is-size</code> to rclone. With this flag set, instead of relying on the backend to report this information, rclone will scan the whole remote similar to <code>rclone size</code> and compute the total used space itself.</p>
-<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag ignores filters so that the result is accurate. However, this is very inefficient and may cost lots of API calls resulting in extra charges. Use it as a last resort and only with caching.</p>
+<h2 id="alternate-report-of-used-bytes-9">Alternate report of used
+bytes</h2>
+<p>Some backends, most notably S3, do not report the amount of bytes
+used. If you need this information to be available when running
+<code>df</code> on the filesystem, then pass the flag
+<code>--vfs-used-is-size</code> to rclone. With this flag set, instead
+of relying on the backend to report this information, rclone will scan
+the whole remote similar to <code>rclone size</code> and compute the
+total used space itself.</p>
+<p><em>WARNING.</em> Contrary to <code>rclone size</code>, this flag
+ignores filters so that the result is accurate. However, this is very
+inefficient and may cost lots of API calls resulting in extra charges.
+Use it as a last resort and only with caching.</p>
 <h2 id="auth-proxy-3">Auth Proxy</h2>
-<p>If you supply the parameter <code>--auth-proxy /path/to/program</code> then rclone will use that program to generate backends on the fly which then are used to authenticate incoming requests. This uses a simple JSON based protocol with input on STDIN and output on STDOUT.</p>
-<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and <code>--authorized-keys</code> cannot be used together, if <code>--auth-proxy</code> is set the authorized keys option will be ignored.</p>
-<p>There is an example program <a href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a> in the rclone source code.</p>
-<p>The program's job is to take a <code>user</code> and <code>pass</code> on the input and turn those into the config for a backend on STDOUT in JSON format. This config will have any default parameters for the backend added, but it won't use configuration from environment variables or command line options - it is the job of the proxy program to make a complete config.</p>
-<p>This config generated must have this extra parameter - <code>_root</code> - root to use for the backend</p>
-<p>And it may have this parameter - <code>_obscure</code> - comma separated strings for parameters to obscure</p>
-<p>If password authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
+<p>If you supply the parameter
+<code>--auth-proxy /path/to/program</code> then rclone will use that
+program to generate backends on the fly which then are used to
+authenticate incoming requests. This uses a simple JSON based protocol
+with input on STDIN and output on STDOUT.</p>
+<p><strong>PLEASE NOTE:</strong> <code>--auth-proxy</code> and
+<code>--authorized-keys</code> cannot be used together, if
+<code>--auth-proxy</code> is set the authorized keys option will be
+ignored.</p>
+<p>There is an example program <a
+href="https://github.com/rclone/rclone/blob/master/bin/test_proxy.py">bin/test_proxy.py</a>
+in the rclone source code.</p>
+<p>The program's job is to take a <code>user</code> and
+<code>pass</code> on the input and turn those into the config for a
+backend on STDOUT in JSON format. This config will have any default
+parameters for the backend added, but it won't use configuration from
+environment variables or command line options - it is the job of the
+proxy program to make a complete config.</p>
+<p>This config generated must have this extra parameter -
+<code>_root</code> - root to use for the backend</p>
+<p>And it may have this parameter - <code>_obscure</code> - comma
+separated strings for parameters to obscure</p>
+<p>If password authentication was used by the client, input to the proxy
+process (on STDIN) would look similar to this:</p>
 <pre><code>{
     &quot;user&quot;: &quot;me&quot;,
     &quot;pass&quot;: &quot;mypassword&quot;
 }</code></pre>
-<p>If public-key authentication was used by the client, input to the proxy process (on STDIN) would look similar to this:</p>
+<p>If public-key authentication was used by the client, input to the
+proxy process (on STDIN) would look similar to this:</p>
 <pre><code>{
     &quot;user&quot;: &quot;me&quot;,
     &quot;public_key&quot;: &quot;AAAAB3NzaC1yc2EAAAADAQABAAABAQDuwESFdAe14hVS6omeyX7edc...JQdf&quot;
@@ -6393,10 +11159,25 @@ htpasswd -B htpasswd anotherUser</code></pre>
     &quot;pass&quot;: &quot;mypassword&quot;,
     &quot;host&quot;: &quot;sftp.example.com&quot;
 }</code></pre>
-<p>This would mean that an SFTP backend would be created on the fly for the <code>user</code> and <code>pass</code>/<code>public_key</code> returned in the output to the host given. Note that since <code>_obscure</code> is set to <code>pass</code>, rclone will obscure the <code>pass</code> parameter before creating the backend (which is required for sftp backends).</p>
-<p>The program can manipulate the supplied <code>user</code> in any way, for example to make proxy to many different sftp backends, you could make the <code>user</code> be <code>user@example.com</code> and then set the <code>host</code> to <code>example.com</code> in the output and the user to <code>user</code>. For security you'd probably want to restrict the <code>host</code> to a limited list.</p>
-<p>Note that an internal cache is keyed on <code>user</code> so only use that for configuration, don't use <code>pass</code> or <code>public_key</code>. This also means that if a user's password or public-key is changed the cache will need to expire (which takes 5 mins) before it takes effect.</p>
-<p>This can be used to build general purpose proxies to any kind of backend that rclone supports.</p>
+<p>This would mean that an SFTP backend would be created on the fly for
+the <code>user</code> and <code>pass</code>/<code>public_key</code>
+returned in the output to the host given. Note that since
+<code>_obscure</code> is set to <code>pass</code>, rclone will obscure
+the <code>pass</code> parameter before creating the backend (which is
+required for sftp backends).</p>
+<p>The program can manipulate the supplied <code>user</code> in any way,
+for example to make proxy to many different sftp backends, you could
+make the <code>user</code> be <code>user@example.com</code> and then set
+the <code>host</code> to <code>example.com</code> in the output and the
+user to <code>user</code>. For security you'd probably want to restrict
+the <code>host</code> to a limited list.</p>
+<p>Note that an internal cache is keyed on <code>user</code> so only use
+that for configuration, don't use <code>pass</code> or
+<code>public_key</code>. This also means that if a user's password or
+public-key is changed the cache will need to expire (which takes 5 mins)
+before it takes effect.</p>
+<p>This can be used to build general purpose proxies to any kind of
+backend that rclone supports.</p>
 <pre><code>rclone serve webdav remote:path [flags]</code></pre>
 <h2 id="options-79">Options</h2>
 <pre><code>      --addr stringArray                       IPaddress:Port, :Port or [unix://]/path/to/socket to bind server to (default [127.0.0.1:8080])
@@ -6448,7 +11229,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --vfs-used-is-size rclone size           Use the rclone size algorithm for Used size
       --vfs-write-back Duration                Time to writeback files after last use when using cache (default 5s)
       --vfs-write-wait Duration                Time to wait for in-sequence write before giving error (default 1s)</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-30">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -6475,26 +11258,36 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --min-size SizeSuffix                 Only transfer files bigger than this in KiB or suffix B|K|M|G|T|P (default off)</code></pre>
 <h2 id="see-also-79">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a> - Serve a remote over a protocol.</li>
+<li><a href="https://rclone.org/commands/rclone_serve/">rclone serve</a>
+- Serve a remote over a protocol.</li>
 </ul>
 <h1 id="rclone-settier">rclone settier</h1>
 <p>Changes storage class/tier of objects in remote.</p>
 <h2 id="synopsis-72">Synopsis</h2>
-<p>Changes storage tier or class at remote if supported. Few cloud storage services provides different storage classes on objects, for example AWS S3 and Glacier, Azure Blob storage - Hot, Cool and Archive, Google Cloud Storage, Regional Storage, Nearline, Coldline etc.</p>
-<p>Note that, certain tier changes make objects not available to access immediately. For example tiering to archive in azure blob storage makes objects in frozen state, user can restore by setting tier to Hot/Cool, similarly S3 to Glacier makes object inaccessible.true</p>
+<p>Changes storage tier or class at remote if supported. Few cloud
+storage services provides different storage classes on objects, for
+example AWS S3 and Glacier, Azure Blob storage - Hot, Cool and Archive,
+Google Cloud Storage, Regional Storage, Nearline, Coldline etc.</p>
+<p>Note that, certain tier changes make objects not available to access
+immediately. For example tiering to archive in azure blob storage makes
+objects in frozen state, user can restore by setting tier to Hot/Cool,
+similarly S3 to Glacier makes object inaccessible.true</p>
 <p>You can use it to tier single object</p>
 <pre><code>rclone settier Cool remote:path/file</code></pre>
 <p>Or use rclone filters to set tier on only specific files</p>
 <pre><code>rclone --include &quot;*.txt&quot; settier Hot remote:path/dir</code></pre>
-<p>Or just provide remote directory and all files in directory will be tiered</p>
+<p>Or just provide remote directory and all files in directory will be
+tiered</p>
 <pre><code>rclone settier tier remote:path/dir</code></pre>
 <pre><code>rclone settier tier remote:path [flags]</code></pre>
 <h2 id="options-80">Options</h2>
 <pre><code>  -h, --help   help for settier</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-80">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-test">rclone test</h1>
 <p>Run a test command</p>
@@ -6502,20 +11295,34 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <p>Rclone test is used to run test commands.</p>
 <p>Select which test command you want with the subcommand, eg</p>
 <pre><code>rclone test memory remote:</code></pre>
-<p>Each subcommand has its own options which you can see in their help.</p>
-<p><strong>NB</strong> Be careful running these commands, they may do strange things so reading their documentation first is recommended.</p>
+<p>Each subcommand has its own options which you can see in their
+help.</p>
+<p><strong>NB</strong> Be careful running these commands, they may do
+strange things so reading their documentation first is recommended.</p>
 <h2 id="options-81">Options</h2>
 <pre><code>  -h, --help   help for test</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-81">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
-<li><a href="https://rclone.org/commands/rclone_test_changenotify/">rclone test changenotify</a> - Log any change notify requests for the remote passed in.</li>
-<li><a href="https://rclone.org/commands/rclone_test_histogram/">rclone test histogram</a> - Makes a histogram of file name characters.</li>
-<li><a href="https://rclone.org/commands/rclone_test_info/">rclone test info</a> - Discovers file name or other limitations for paths.</li>
-<li><a href="https://rclone.org/commands/rclone_test_makefile/">rclone test makefile</a> - Make files with random contents of the size given</li>
-<li><a href="https://rclone.org/commands/rclone_test_makefiles/">rclone test makefiles</a> - Make a random file hierarchy in a directory</li>
-<li><a href="https://rclone.org/commands/rclone_test_memory/">rclone test memory</a> - Load all the objects at remote:path into memory and report memory stats.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
+<li><a
+href="https://rclone.org/commands/rclone_test_changenotify/">rclone test
+changenotify</a> - Log any change notify requests for the remote passed
+in.</li>
+<li><a href="https://rclone.org/commands/rclone_test_histogram/">rclone
+test histogram</a> - Makes a histogram of file name characters.</li>
+<li><a href="https://rclone.org/commands/rclone_test_info/">rclone test
+info</a> - Discovers file name or other limitations for paths.</li>
+<li><a href="https://rclone.org/commands/rclone_test_makefile/">rclone
+test makefile</a> - Make files with random contents of the size
+given</li>
+<li><a href="https://rclone.org/commands/rclone_test_makefiles/">rclone
+test makefiles</a> - Make a random file hierarchy in a directory</li>
+<li><a href="https://rclone.org/commands/rclone_test_memory/">rclone
+test memory</a> - Load all the objects at remote:path into memory and
+report memory stats.</li>
 </ul>
 <h1 id="rclone-test-changenotify">rclone test changenotify</h1>
 <p>Log any change notify requests for the remote passed in.</p>
@@ -6523,29 +11330,39 @@ htpasswd -B htpasswd anotherUser</code></pre>
 <h2 id="options-82">Options</h2>
 <pre><code>  -h, --help                     help for changenotify
       --poll-interval Duration   Time to wait between polling for changes (default 10s)</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-82">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
+<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> -
+Run a test command</li>
 </ul>
 <h1 id="rclone-test-histogram">rclone test histogram</h1>
 <p>Makes a histogram of file name characters.</p>
 <h2 id="synopsis-74">Synopsis</h2>
-<p>This command outputs JSON which shows the histogram of characters used in filenames in the remote:path specified.</p>
-<p>The data doesn't contain any identifying information but is useful for the rclone developers when developing filename compression.</p>
+<p>This command outputs JSON which shows the histogram of characters
+used in filenames in the remote:path specified.</p>
+<p>The data doesn't contain any identifying information but is useful
+for the rclone developers when developing filename compression.</p>
 <pre><code>rclone test histogram [remote:path] [flags]</code></pre>
 <h2 id="options-83">Options</h2>
 <pre><code>  -h, --help   help for histogram</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-83">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
+<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> -
+Run a test command</li>
 </ul>
 <h1 id="rclone-test-info">rclone test info</h1>
 <p>Discovers file name or other limitations for paths.</p>
 <h2 id="synopsis-75">Synopsis</h2>
-<p>Discovers what filenames and upload methods are possible to write to the paths passed in and how long they can be. It can take some time. It will write test files into the remote:path passed in. It outputs a bit of go code for each one.</p>
-<p><strong>NB</strong> this can create undeletable files and other hazards - use with care</p>
+<p>Discovers what filenames and upload methods are possible to write to
+the paths passed in and how long they can be. It can take some time. It
+will write test files into the remote:path passed in. It outputs a bit
+of go code for each one.</p>
+<p><strong>NB</strong> this can create undeletable files and other
+hazards - use with care</p>
 <pre><code>rclone test info [remote:path]+ [flags]</code></pre>
 <h2 id="options-84">Options</h2>
 <pre><code>      --all                    Run all tests
@@ -6558,10 +11375,12 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --keep-test-files        Keep test files after execution
       --upload-wait Duration   Wait after writing a file (default 0s)
       --write-json string      Write results to file</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-84">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
+<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> -
+Run a test command</li>
 </ul>
 <h1 id="rclone-test-makefile">rclone test makefile</h1>
 <p>Make files with random contents of the size given</p>
@@ -6574,10 +11393,12 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --seed int   Seed for the random number generator (0 for random) (default 1)
       --sparse     Make the files sparse (appear to be filled with ASCII 0x00)
       --zero       Fill files with ASCII 0x00</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-85">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
+<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> -
+Run a test command</li>
 </ul>
 <h1 id="rclone-test-makefiles">rclone test makefiles</h1>
 <p>Make a random file hierarchy in a directory</p>
@@ -6597,34 +11418,48 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --seed int                   Seed for the random number generator (0 for random) (default 1)
       --sparse                     Make the files sparse (appear to be filled with ASCII 0x00)
       --zero                       Fill files with ASCII 0x00</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-86">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
+<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> -
+Run a test command</li>
 </ul>
 <h1 id="rclone-test-memory">rclone test memory</h1>
-<p>Load all the objects at remote:path into memory and report memory stats.</p>
+<p>Load all the objects at remote:path into memory and report memory
+stats.</p>
 <pre><code>rclone test memory remote:path [flags]</code></pre>
 <h2 id="options-87">Options</h2>
 <pre><code>  -h, --help   help for memory</code></pre>
-<p>See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>See the <a href="https://rclone.org/flags/">global flags page</a> for
+global options not listed here.</p>
 <h2 id="see-also-87">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> - Run a test command</li>
+<li><a href="https://rclone.org/commands/rclone_test/">rclone test</a> -
+Run a test command</li>
 </ul>
 <h1 id="rclone-touch">rclone touch</h1>
 <p>Create new file or change file modification time.</p>
 <h2 id="synopsis-76">Synopsis</h2>
-<p>Set the modification time on file(s) as specified by remote:path to have the current time.</p>
-<p>If remote:path does not exist then a zero sized file will be created, unless <code>--no-create</code> or <code>--recursive</code> is provided.</p>
-<p>If <code>--recursive</code> is used then recursively sets the modification time on all existing files that is found under the path. Filters are supported, and you can test with the <code>--dry-run</code> or the <code>--interactive</code>/<code>-i</code> flag.</p>
-<p>If <code>--timestamp</code> is used then sets the modification time to that time instead of the current time. Times may be specified as one of:</p>
+<p>Set the modification time on file(s) as specified by remote:path to
+have the current time.</p>
+<p>If remote:path does not exist then a zero sized file will be created,
+unless <code>--no-create</code> or <code>--recursive</code> is
+provided.</p>
+<p>If <code>--recursive</code> is used then recursively sets the
+modification time on all existing files that is found under the path.
+Filters are supported, and you can test with the <code>--dry-run</code>
+or the <code>--interactive</code>/<code>-i</code> flag.</p>
+<p>If <code>--timestamp</code> is used then sets the modification time
+to that time instead of the current time. Times may be specified as one
+of:</p>
 <ul>
 <li>'YYMMDD' - e.g. 17.10.30</li>
 <li>'YYYY-MM-DDTHH:MM:SS' - e.g. 2006-01-02T15:04:05</li>
 <li>'YYYY-MM-DDTHH:MM:SS.SSS' - e.g. 2006-01-02T15:04:05.123456789</li>
 </ul>
-<p>Note that value of <code>--timestamp</code> is in UTC. If you want local time then add the <code>--localtime</code> flag.</p>
+<p>Note that value of <code>--timestamp</code> is in UTC. If you want
+local time then add the <code>--localtime</code> flag.</p>
 <pre><code>rclone touch remote:path [flags]</code></pre>
 <h2 id="options-88">Options</h2>
 <pre><code>  -h, --help               help for touch
@@ -6632,7 +11467,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
   -C, --no-create          Do not create the file if it does not exist (implied with --recursive)
   -R, --recursive          Recursively touch all files
   -t, --timestamp string   Use specified time instead of the current time of day</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="important-options-17">Important Options</h3>
 <p>Important flags useful for most commands</p>
 <pre><code>  -n, --dry-run         Do a trial run with no permanent changes
@@ -6668,12 +11505,14 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-88">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h1 id="rclone-tree">rclone tree</h1>
 <p>List the contents of the remote in a tree like fashion.</p>
 <h2 id="synopsis-77">Synopsis</h2>
-<p>Lists the contents of a remote in a similar way to the unix tree command.</p>
+<p>Lists the contents of a remote in a similar way to the unix tree
+command.</p>
 <p>For example</p>
 <pre><code>$ rclone tree remote:path
 /
@@ -6685,9 +11524,15 @@ htpasswd -B htpasswd anotherUser</code></pre>
     └── file5
 
 1 directories, 5 files</code></pre>
-<p>You can use any of the filtering options with the tree command (e.g. <code>--include</code> and <code>--exclude</code>. You can also use <code>--fast-list</code>.</p>
-<p>The tree command has many options for controlling the listing which are compatible with the tree command, for example you can include file sizes with <code>--size</code>. Note that not all of them have short options as they conflict with rclone's short options.</p>
-<p>For a more interactive navigation of the remote see the <a href="https://rclone.org/commands/rclone_ncdu/">ncdu</a> command.</p>
+<p>You can use any of the filtering options with the tree command (e.g.
+<code>--include</code> and <code>--exclude</code>. You can also use
+<code>--fast-list</code>.</p>
+<p>The tree command has many options for controlling the listing which
+are compatible with the tree command, for example you can include file
+sizes with <code>--size</code>. Note that not all of them have short
+options as they conflict with rclone's short options.</p>
+<p>For a more interactive navigation of the remote see the <a
+href="https://rclone.org/commands/rclone_ncdu/">ncdu</a> command.</p>
 <pre><code>rclone tree remote:path [flags]</code></pre>
 <h2 id="options-89">Options</h2>
 <pre><code>  -a, --all             All files are listed (list . files too)
@@ -6709,7 +11554,9 @@ htpasswd -B htpasswd anotherUser</code></pre>
   -r, --sort-reverse    Reverse the order of the sort
   -U, --unsorted        Leave files unsorted
       --version         Sort files alphanumerically by version</code></pre>
-<p>Options shared with other commands are described next. See the <a href="https://rclone.org/flags/">global flags page</a> for global options not listed here.</p>
+<p>Options shared with other commands are described next. See the <a
+href="https://rclone.org/flags/">global flags page</a> for global
+options not listed here.</p>
 <h3 id="filter-options-32">Filter Options</h3>
 <p>Flags for filtering directory listings</p>
 <pre><code>      --delete-excluded                     Delete files on dest excluded from sync
@@ -6740,155 +11587,325 @@ htpasswd -B htpasswd anotherUser</code></pre>
       --fast-list           Use recursive list if available; uses more memory but fewer transactions</code></pre>
 <h2 id="see-also-89">See Also</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help for rclone commands, flags and backends.</li>
+<li><a href="https://rclone.org/commands/rclone/">rclone</a> - Show help
+for rclone commands, flags and backends.</li>
 </ul>
 <h2 id="copying-single-files">Copying single files</h2>
-<p>rclone normally syncs or copies directories. However, if the source remote points to a file, rclone will just copy that file. The destination remote must point to a directory - rclone will give the error <code>Failed to create file system for "remote:file": is a file not a directory</code> if it isn't.</p>
-<p>For example, suppose you have a remote with a file in called <code>test.jpg</code>, then you could copy just that file like this</p>
+<p>rclone normally syncs or copies directories. However, if the source
+remote points to a file, rclone will just copy that file. The
+destination remote must point to a directory - rclone will give the
+error
+<code>Failed to create file system for "remote:file": is a file not a directory</code>
+if it isn't.</p>
+<p>For example, suppose you have a remote with a file in called
+<code>test.jpg</code>, then you could copy just that file like this</p>
 <pre><code>rclone copy remote:test.jpg /tmp/download</code></pre>
-<p>The file <code>test.jpg</code> will be placed inside <code>/tmp/download</code>.</p>
+<p>The file <code>test.jpg</code> will be placed inside
+<code>/tmp/download</code>.</p>
 <p>This is equivalent to specifying</p>
 <pre><code>rclone copy --files-from /tmp/files remote: /tmp/download</code></pre>
 <p>Where <code>/tmp/files</code> contains the single line</p>
 <pre><code>test.jpg</code></pre>
-<p>It is recommended to use <code>copy</code> when copying individual files, not <code>sync</code>. They have pretty much the same effect but <code>copy</code> will use a lot less memory.</p>
+<p>It is recommended to use <code>copy</code> when copying individual
+files, not <code>sync</code>. They have pretty much the same effect but
+<code>copy</code> will use a lot less memory.</p>
 <h2 id="syntax-of-remote-paths">Syntax of remote paths</h2>
-<p>The syntax of the paths passed to the rclone command are as follows.</p>
+<p>The syntax of the paths passed to the rclone command are as
+follows.</p>
 <h3 id="pathtodir">/path/to/dir</h3>
 <p>This refers to the local file system.</p>
-<p>On Windows <code>\</code> may be used instead of <code>/</code> in local paths <strong>only</strong>, non local paths must use <code>/</code>. See <a href="https://rclone.org/local/#paths-on-windows">local filesystem</a> documentation for more about Windows-specific paths.</p>
-<p>These paths needn't start with a leading <code>/</code> - if they don't then they will be relative to the current directory.</p>
+<p>On Windows <code>\</code> may be used instead of <code>/</code> in
+local paths <strong>only</strong>, non local paths must use
+<code>/</code>. See <a
+href="https://rclone.org/local/#paths-on-windows">local filesystem</a>
+documentation for more about Windows-specific paths.</p>
+<p>These paths needn't start with a leading <code>/</code> - if they
+don't then they will be relative to the current directory.</p>
 <h3 id="remotepathtodir">remote:path/to/dir</h3>
-<p>This refers to a directory <code>path/to/dir</code> on <code>remote:</code> as defined in the config file (configured with <code>rclone config</code>).</p>
+<p>This refers to a directory <code>path/to/dir</code> on
+<code>remote:</code> as defined in the config file (configured with
+<code>rclone config</code>).</p>
 <h3 id="remotepathtodir-1">remote:/path/to/dir</h3>
-<p>On most backends this is refers to the same directory as <code>remote:path/to/dir</code> and that format should be preferred. On a very small number of remotes (FTP, SFTP, Dropbox for business) this will refer to a different directory. On these, paths without a leading <code>/</code> will refer to your "home" directory and paths with a leading <code>/</code> will refer to the root.</p>
+<p>On most backends this is refers to the same directory as
+<code>remote:path/to/dir</code> and that format should be preferred. On
+a very small number of remotes (FTP, SFTP, Dropbox for business) this
+will refer to a different directory. On these, paths without a leading
+<code>/</code> will refer to your "home" directory and paths with a
+leading <code>/</code> will refer to the root.</p>
 <h3 id="backendpathtodir">:backend:path/to/dir</h3>
-<p>This is an advanced form for creating remotes on the fly. <code>backend</code> should be the name or prefix of a backend (the <code>type</code> in the config file) and all the configuration for the backend should be provided on the command line (or in environment variables).</p>
+<p>This is an advanced form for creating remotes on the fly.
+<code>backend</code> should be the name or prefix of a backend (the
+<code>type</code> in the config file) and all the configuration for the
+backend should be provided on the command line (or in environment
+variables).</p>
 <p>Here are some examples:</p>
 <pre><code>rclone lsd --http-url https://pub.rclone.org :http:</code></pre>
-<p>To list all the directories in the root of <code>https://pub.rclone.org/</code>.</p>
+<p>To list all the directories in the root of
+<code>https://pub.rclone.org/</code>.</p>
 <pre><code>rclone lsf --http-url https://example.com :http:path/to/dir</code></pre>
-<p>To list files and directories in <code>https://example.com/path/to/dir/</code></p>
+<p>To list files and directories in
+<code>https://example.com/path/to/dir/</code></p>
 <pre><code>rclone copy --http-url https://example.com :http:path/to/dir /tmp/dir</code></pre>
-<p>To copy files and directories in <code>https://example.com/path/to/dir</code> to <code>/tmp/dir</code>.</p>
+<p>To copy files and directories in
+<code>https://example.com/path/to/dir</code> to
+<code>/tmp/dir</code>.</p>
 <pre><code>rclone copy --sftp-host example.com :sftp:path/to/dir /tmp/dir</code></pre>
-<p>To copy files and directories from <code>example.com</code> in the relative directory <code>path/to/dir</code> to <code>/tmp/dir</code> using sftp.</p>
+<p>To copy files and directories from <code>example.com</code> in the
+relative directory <code>path/to/dir</code> to <code>/tmp/dir</code>
+using sftp.</p>
 <h3 id="connection-strings">Connection strings</h3>
-<p>The above examples can also be written using a connection string syntax, so instead of providing the arguments as command line parameters <code>--http-url https://pub.rclone.org</code> they are provided as part of the remote specification as a kind of connection string.</p>
+<p>The above examples can also be written using a connection string
+syntax, so instead of providing the arguments as command line parameters
+<code>--http-url https://pub.rclone.org</code> they are provided as part
+of the remote specification as a kind of connection string.</p>
 <pre><code>rclone lsd &quot;:http,url=&#39;https://pub.rclone.org&#39;:&quot;
 rclone lsf &quot;:http,url=&#39;https://example.com&#39;:path/to/dir&quot;
 rclone copy &quot;:http,url=&#39;https://example.com&#39;:path/to/dir&quot; /tmp/dir
 rclone copy :sftp,host=example.com:path/to/dir /tmp/dir</code></pre>
-<p>These can apply to modify existing remotes as well as create new remotes with the on the fly syntax. This example is equivalent to adding the <code>--drive-shared-with-me</code> parameter to the remote <code>gdrive:</code>.</p>
+<p>These can apply to modify existing remotes as well as create new
+remotes with the on the fly syntax. This example is equivalent to adding
+the <code>--drive-shared-with-me</code> parameter to the remote
+<code>gdrive:</code>.</p>
 <pre><code>rclone lsf &quot;gdrive,shared_with_me:path/to/dir&quot;</code></pre>
-<p>The major advantage to using the connection string style syntax is that it only applies to the remote, not to all the remotes of that type of the command line. A common confusion is this attempt to copy a file shared on google drive to the normal drive which <strong>does not work</strong> because the <code>--drive-shared-with-me</code> flag applies to both the source and the destination.</p>
+<p>The major advantage to using the connection string style syntax is
+that it only applies to the remote, not to all the remotes of that type
+of the command line. A common confusion is this attempt to copy a file
+shared on google drive to the normal drive which <strong>does not
+work</strong> because the <code>--drive-shared-with-me</code> flag
+applies to both the source and the destination.</p>
 <pre><code>rclone copy --drive-shared-with-me gdrive:shared-file.txt gdrive:</code></pre>
 <p>However using the connection string syntax, this does work.</p>
 <pre><code>rclone copy &quot;gdrive,shared_with_me:shared-file.txt&quot; gdrive:</code></pre>
-<p>Note that the connection string only affects the options of the immediate backend. If for example gdriveCrypt is a crypt based on gdrive, then the following command <strong>will not work</strong> as intended, because <code>shared_with_me</code> is ignored by the crypt backend:</p>
+<p>Note that the connection string only affects the options of the
+immediate backend. If for example gdriveCrypt is a crypt based on
+gdrive, then the following command <strong>will not work</strong> as
+intended, because <code>shared_with_me</code> is ignored by the crypt
+backend:</p>
 <pre><code>rclone copy &quot;gdriveCrypt,shared_with_me:shared-file.txt&quot; gdriveCrypt:</code></pre>
 <p>The connection strings have the following syntax</p>
 <pre><code>remote,parameter=value,parameter2=value2:path/to/dir
 :backend,parameter=value,parameter2=value2:path/to/dir</code></pre>
-<p>If the <code>parameter</code> has a <code>:</code> or <code>,</code> then it must be placed in quotes <code>"</code> or <code>'</code>, so</p>
+<p>If the <code>parameter</code> has a <code>:</code> or <code>,</code>
+then it must be placed in quotes <code>"</code> or <code>'</code>,
+so</p>
 <pre><code>remote,parameter=&quot;colon:value&quot;,parameter2=&quot;comma,value&quot;:path/to/dir
 :backend,parameter=&#39;colon:value&#39;,parameter2=&#39;comma,value&#39;:path/to/dir</code></pre>
-<p>If a quoted value needs to include that quote, then it should be doubled, so</p>
+<p>If a quoted value needs to include that quote, then it should be
+doubled, so</p>
 <pre><code>remote,parameter=&quot;with&quot;&quot;quote&quot;,parameter2=&#39;with&#39;&#39;quote&#39;:path/to/dir</code></pre>
-<p>This will make <code>parameter</code> be <code>with"quote</code> and <code>parameter2</code> be <code>with'quote</code>.</p>
-<p>If you leave off the <code>=parameter</code> then rclone will substitute <code>=true</code> which works very well with flags. For example, to use s3 configured in the environment you could use:</p>
+<p>This will make <code>parameter</code> be <code>with"quote</code> and
+<code>parameter2</code> be <code>with'quote</code>.</p>
+<p>If you leave off the <code>=parameter</code> then rclone will
+substitute <code>=true</code> which works very well with flags. For
+example, to use s3 configured in the environment you could use:</p>
 <pre><code>rclone lsd :s3,env_auth:</code></pre>
 <p>Which is equivalent to</p>
 <pre><code>rclone lsd :s3,env_auth=true:</code></pre>
-<p>Note that on the command line you might need to surround these connection strings with <code>"</code> or <code>'</code> to stop the shell interpreting any special characters within them.</p>
-<p>If you are a shell master then you'll know which strings are OK and which aren't, but if you aren't sure then enclose them in <code>"</code> and use <code>'</code> as the inside quote. This syntax works on all OSes.</p>
+<p>Note that on the command line you might need to surround these
+connection strings with <code>"</code> or <code>'</code> to stop the
+shell interpreting any special characters within them.</p>
+<p>If you are a shell master then you'll know which strings are OK and
+which aren't, but if you aren't sure then enclose them in <code>"</code>
+and use <code>'</code> as the inside quote. This syntax works on all
+OSes.</p>
 <pre><code>rclone copy &quot;:http,url=&#39;https://example.com&#39;:path/to/dir&quot; /tmp/dir</code></pre>
-<p>On Linux/macOS some characters are still interpreted inside <code>"</code> strings in the shell (notably <code>\</code> and <code>$</code> and <code>"</code>) so if your strings contain those you can swap the roles of <code>"</code> and <code>'</code> thus. (This syntax does not work on Windows.)</p>
+<p>On Linux/macOS some characters are still interpreted inside
+<code>"</code> strings in the shell (notably <code>\</code> and
+<code>$</code> and <code>"</code>) so if your strings contain those you
+can swap the roles of <code>"</code> and <code>'</code> thus. (This
+syntax does not work on Windows.)</p>
 <pre><code>rclone copy &#39;:http,url=&quot;https://example.com&quot;:path/to/dir&#39; /tmp/dir</code></pre>
-<h4 id="connection-strings-config-and-logging">Connection strings, config and logging</h4>
-<p>If you supply extra configuration to a backend by command line flag, environment variable or connection string then rclone will add a suffix based on the hash of the config to the name of the remote, eg</p>
+<h4 id="connection-strings-config-and-logging">Connection strings,
+config and logging</h4>
+<p>If you supply extra configuration to a backend by command line flag,
+environment variable or connection string then rclone will add a suffix
+based on the hash of the config to the name of the remote, eg</p>
 <pre><code>rclone -vv lsf --s3-chunk-size 20M s3:</code></pre>
 <p>Has the log message</p>
 <pre><code>DEBUG : s3: detected overridden config - adding &quot;{Srj1p}&quot; suffix to name</code></pre>
-<p>This is so rclone can tell the modified remote apart from the unmodified remote when caching the backends.</p>
+<p>This is so rclone can tell the modified remote apart from the
+unmodified remote when caching the backends.</p>
 <p>This should only be noticeable in the logs.</p>
 <p>This means that on the fly backends such as</p>
 <pre><code>rclone -vv lsf :s3,env_auth:</code></pre>
 <p>Will get their own names</p>
 <pre><code>DEBUG : :s3: detected overridden config - adding &quot;{YTu53}&quot; suffix to name</code></pre>
 <h3 id="valid-remote-names">Valid remote names</h3>
-<p>Remote names are case sensitive, and must adhere to the following rules: - May contain number, letter, <code>_</code>, <code>-</code>, <code>.</code>, <code>+</code>, <code>@</code> and space. - May not start with <code>-</code> or space. - May not end with space.</p>
-<p>Starting with rclone version 1.61, any Unicode numbers and letters are allowed, while in older versions it was limited to plain ASCII (0-9, A-Z, a-z). If you use the same rclone configuration from different shells, which may be configured with different character encoding, you must be cautious to use characters that are possible to write in all of them. This is mostly a problem on Windows, where the console traditionally uses a non-Unicode character set - defined by the so-called "code page".</p>
-<p>Do not use single character names on Windows as it creates ambiguity with Windows drives' names, e.g.: remote called <code>C</code> is indistinguishable from <code>C</code> drive. Rclone will always assume that single letter name refers to a drive.</p>
+<p>Remote names are case sensitive, and must adhere to the following
+rules: - May contain number, letter, <code>_</code>, <code>-</code>,
+<code>.</code>, <code>+</code>, <code>@</code> and space. - May not
+start with <code>-</code> or space. - May not end with space.</p>
+<p>Starting with rclone version 1.61, any Unicode numbers and letters
+are allowed, while in older versions it was limited to plain ASCII (0-9,
+A-Z, a-z). If you use the same rclone configuration from different
+shells, which may be configured with different character encoding, you
+must be cautious to use characters that are possible to write in all of
+them. This is mostly a problem on Windows, where the console
+traditionally uses a non-Unicode character set - defined by the
+so-called "code page".</p>
+<p>Do not use single character names on Windows as it creates ambiguity
+with Windows drives' names, e.g.: remote called <code>C</code> is
+indistinguishable from <code>C</code> drive. Rclone will always assume
+that single letter name refers to a drive.</p>
 <h2 id="quoting-and-the-shell">Quoting and the shell</h2>
-<p>When you are typing commands to your computer you are using something called the command line shell. This interprets various characters in an OS specific way.</p>
-<p>Here are some gotchas which may help users unfamiliar with the shell rules</p>
+<p>When you are typing commands to your computer you are using something
+called the command line shell. This interprets various characters in an
+OS specific way.</p>
+<p>Here are some gotchas which may help users unfamiliar with the shell
+rules</p>
 <h3 id="linux-osx">Linux / OSX</h3>
-<p>If your names have spaces or shell metacharacters (e.g. <code>*</code>, <code>?</code>, <code>$</code>, <code>'</code>, <code>"</code>, etc.) then you must quote them. Use single quotes <code>'</code> by default.</p>
+<p>If your names have spaces or shell metacharacters (e.g.
+<code>*</code>, <code>?</code>, <code>$</code>, <code>'</code>,
+<code>"</code>, etc.) then you must quote them. Use single quotes
+<code>'</code> by default.</p>
 <pre><code>rclone copy &#39;Important files?&#39; remote:backup</code></pre>
-<p>If you want to send a <code>'</code> you will need to use <code>"</code>, e.g.</p>
+<p>If you want to send a <code>'</code> you will need to use
+<code>"</code>, e.g.</p>
 <pre><code>rclone copy &quot;O&#39;Reilly Reviews&quot; remote:backup</code></pre>
-<p>The rules for quoting metacharacters are complicated and if you want the full details you'll have to consult the manual page for your shell.</p>
+<p>The rules for quoting metacharacters are complicated and if you want
+the full details you'll have to consult the manual page for your
+shell.</p>
 <h3 id="windows-1">Windows</h3>
-<p>If your names have spaces in you need to put them in <code>"</code>, e.g.</p>
+<p>If your names have spaces in you need to put them in <code>"</code>,
+e.g.</p>
 <pre><code>rclone copy &quot;E:\folder name\folder name\folder name&quot; remote:backup</code></pre>
-<p>If you are using the root directory on its own then don't quote it (see <a href="https://github.com/rclone/rclone/issues/464">#464</a> for why), e.g.</p>
+<p>If you are using the root directory on its own then don't quote it
+(see <a href="https://github.com/rclone/rclone/issues/464">#464</a> for
+why), e.g.</p>
 <pre><code>rclone copy E:\ remote:backup</code></pre>
-<h2 id="copying-files-or-directories-with-in-the-names">Copying files or directories with <code>:</code> in the names</h2>
-<p>rclone uses <code>:</code> to mark a remote name. This is, however, a valid filename component in non-Windows OSes. The remote name parser will only search for a <code>:</code> up to the first <code>/</code> so if you need to act on a file or directory like this then use the full path starting with a <code>/</code>, or use <code>./</code> as a current directory prefix.</p>
-<p>So to sync a directory called <code>sync:me</code> to a remote called <code>remote:</code> use</p>
+<h2 id="copying-files-or-directories-with-in-the-names">Copying files or
+directories with <code>:</code> in the names</h2>
+<p>rclone uses <code>:</code> to mark a remote name. This is, however, a
+valid filename component in non-Windows OSes. The remote name parser
+will only search for a <code>:</code> up to the first <code>/</code> so
+if you need to act on a file or directory like this then use the full
+path starting with a <code>/</code>, or use <code>./</code> as a current
+directory prefix.</p>
+<p>So to sync a directory called <code>sync:me</code> to a remote called
+<code>remote:</code> use</p>
 <pre><code>rclone sync --interactive ./sync:me remote:path</code></pre>
 <p>or</p>
 <pre><code>rclone sync --interactive /full/path/to/sync:me remote:path</code></pre>
 <h2 id="server-side-copy">Server Side Copy</h2>
-<p>Most remotes (but not all - see <a href="https://rclone.org/overview/#optional-features">the overview</a>) support server-side copy.</p>
-<p>This means if you want to copy one folder to another then rclone won't download all the files and re-upload them; it will instruct the server to copy them in place.</p>
+<p>Most remotes (but not all - see <a
+href="https://rclone.org/overview/#optional-features">the overview</a>)
+support server-side copy.</p>
+<p>This means if you want to copy one folder to another then rclone
+won't download all the files and re-upload them; it will instruct the
+server to copy them in place.</p>
 <p>Eg</p>
 <pre><code>rclone copy s3:oldbucket s3:newbucket</code></pre>
-<p>Will copy the contents of <code>oldbucket</code> to <code>newbucket</code> without downloading and re-uploading.</p>
-<p>Remotes which don't support server-side copy <strong>will</strong> download and re-upload in this case.</p>
-<p>Server side copies are used with <code>sync</code> and <code>copy</code> and will be identified in the log when using the <code>-v</code> flag. The <code>move</code> command may also use them if remote doesn't support server-side move directly. This is done by issuing a server-side copy then a delete which is much quicker than a download and re-upload.</p>
-<p>Server side copies will only be attempted if the remote names are the same.</p>
-<p>This can be used when scripting to make aged backups efficiently, e.g.</p>
+<p>Will copy the contents of <code>oldbucket</code> to
+<code>newbucket</code> without downloading and re-uploading.</p>
+<p>Remotes which don't support server-side copy <strong>will</strong>
+download and re-upload in this case.</p>
+<p>Server side copies are used with <code>sync</code> and
+<code>copy</code> and will be identified in the log when using the
+<code>-v</code> flag. The <code>move</code> command may also use them if
+remote doesn't support server-side move directly. This is done by
+issuing a server-side copy then a delete which is much quicker than a
+download and re-upload.</p>
+<p>Server side copies will only be attempted if the remote names are the
+same.</p>
+<p>This can be used when scripting to make aged backups efficiently,
+e.g.</p>
 <pre><code>rclone sync --interactive remote:current-backup remote:previous-backup
 rclone sync --interactive /path/to/files remote:current-backup</code></pre>
 <h2 id="metadata">Metadata support</h2>
-<p>Metadata is data about a file (or directory) which isn't the contents of the file (or directory). Normally rclone only preserves the modification time and the content (MIME) type where possible.</p>
-<p>Rclone supports preserving all the available metadata on files and directories when using the <code>--metadata</code> or <code>-M</code> flag.</p>
-<p>Exactly what metadata is supported and what that support means depends on the backend. Backends that support metadata have a metadata section in their docs and are listed in the <a href="https://rclone.org/overview/#features">features table</a> (Eg <a href="https://rclone.org/local/#metadata">local</a>, <a href="/s3/#metadata">s3</a>)</p>
-<p>Some backends don't support metadata, some only support metadata on files and some support metadata on both files and directories.</p>
-<p>Rclone only supports a one-time sync of metadata. This means that metadata will be synced from the source object to the destination object only when the source object has changed and needs to be re-uploaded. If the metadata subsequently changes on the source object without changing the object itself then it won't be synced to the destination object. This is in line with the way rclone syncs <code>Content-Type</code> without the <code>--metadata</code> flag.</p>
-<p>Using <code>--metadata</code> when syncing from local to local will preserve file attributes such as file mode, owner, extended attributes (not Windows).</p>
-<p>Note that arbitrary metadata may be added to objects using the <code>--metadata-set key=value</code> flag when the object is first uploaded. This flag can be repeated as many times as necessary.</p>
-<p>The <a href="#metadata-mapper">--metadata-mapper</a> flag can be used to pass the name of a program in which can transform metadata when it is being copied from source to destination.</p>
-<p>Rclone supports <code>--metadata-set</code> and <code>--metadata-mapper</code> when doing sever side <code>Move</code> and server side <code>Copy</code>, but not when doing server side <code>DirMove</code> (renaming a directory) as this would involve recursing into the directory. Note that you can disable <code>DirMove</code> with <code>--disable DirMove</code> and rclone will revert back to using <code>Move</code> for each individual object where <code>--metadata-set</code> and <code>--metadata-mapper</code> are supported.</p>
+<p>Metadata is data about a file (or directory) which isn't the contents
+of the file (or directory). Normally rclone only preserves the
+modification time and the content (MIME) type where possible.</p>
+<p>Rclone supports preserving all the available metadata on files and
+directories when using the <code>--metadata</code> or <code>-M</code>
+flag.</p>
+<p>Exactly what metadata is supported and what that support means
+depends on the backend. Backends that support metadata have a metadata
+section in their docs and are listed in the <a
+href="https://rclone.org/overview/#features">features table</a> (Eg <a
+href="https://rclone.org/local/#metadata">local</a>, <a
+href="/s3/#metadata">s3</a>)</p>
+<p>Some backends don't support metadata, some only support metadata on
+files and some support metadata on both files and directories.</p>
+<p>Rclone only supports a one-time sync of metadata. This means that
+metadata will be synced from the source object to the destination object
+only when the source object has changed and needs to be re-uploaded. If
+the metadata subsequently changes on the source object without changing
+the object itself then it won't be synced to the destination object.
+This is in line with the way rclone syncs <code>Content-Type</code>
+without the <code>--metadata</code> flag.</p>
+<p>Using <code>--metadata</code> when syncing from local to local will
+preserve file attributes such as file mode, owner, extended attributes
+(not Windows).</p>
+<p>Note that arbitrary metadata may be added to objects using the
+<code>--metadata-set key=value</code> flag when the object is first
+uploaded. This flag can be repeated as many times as necessary.</p>
+<p>The <a href="#metadata-mapper">--metadata-mapper</a> flag can be used
+to pass the name of a program in which can transform metadata when it is
+being copied from source to destination.</p>
+<p>Rclone supports <code>--metadata-set</code> and
+<code>--metadata-mapper</code> when doing sever side <code>Move</code>
+and server side <code>Copy</code>, but not when doing server side
+<code>DirMove</code> (renaming a directory) as this would involve
+recursing into the directory. Note that you can disable
+<code>DirMove</code> with <code>--disable DirMove</code> and rclone will
+revert back to using <code>Move</code> for each individual object where
+<code>--metadata-set</code> and <code>--metadata-mapper</code> are
+supported.</p>
 <h3 id="types-of-metadata">Types of metadata</h3>
-<p>Metadata is divided into two type. System metadata and User metadata.</p>
-<p>Metadata which the backend uses itself is called system metadata. For example on the local backend the system metadata <code>uid</code> will store the user ID of the file when used on a unix based platform.</p>
-<p>Arbitrary metadata is called user metadata and this can be set however is desired.</p>
-<p>When objects are copied from backend to backend, they will attempt to interpret system metadata if it is supplied. Metadata may change from being user metadata to system metadata as objects are copied between different backends. For example copying an object from s3 sets the <code>content-type</code> metadata. In a backend which understands this (like <code>azureblob</code>) this will become the Content-Type of the object. In a backend which doesn't understand this (like the <code>local</code> backend) this will become user metadata. However should the local object be copied back to s3, the Content-Type will be set correctly.</p>
+<p>Metadata is divided into two type. System metadata and User
+metadata.</p>
+<p>Metadata which the backend uses itself is called system metadata. For
+example on the local backend the system metadata <code>uid</code> will
+store the user ID of the file when used on a unix based platform.</p>
+<p>Arbitrary metadata is called user metadata and this can be set
+however is desired.</p>
+<p>When objects are copied from backend to backend, they will attempt to
+interpret system metadata if it is supplied. Metadata may change from
+being user metadata to system metadata as objects are copied between
+different backends. For example copying an object from s3 sets the
+<code>content-type</code> metadata. In a backend which understands this
+(like <code>azureblob</code>) this will become the Content-Type of the
+object. In a backend which doesn't understand this (like the
+<code>local</code> backend) this will become user metadata. However
+should the local object be copied back to s3, the Content-Type will be
+set correctly.</p>
 <h3 id="metadata-framework">Metadata framework</h3>
-<p>Rclone implements a metadata framework which can read metadata from an object and write it to the object when (and only when) it is being uploaded.</p>
-<p>This metadata is stored as a dictionary with string keys and string values.</p>
-<p>There are some limits on the names of the keys (these may be clarified further in the future).</p>
+<p>Rclone implements a metadata framework which can read metadata from
+an object and write it to the object when (and only when) it is being
+uploaded.</p>
+<p>This metadata is stored as a dictionary with string keys and string
+values.</p>
+<p>There are some limits on the names of the keys (these may be
+clarified further in the future).</p>
 <ul>
 <li>must be lower case</li>
-<li>may be <code>a-z</code> <code>0-9</code> containing <code>.</code> <code>-</code> or <code>_</code></li>
+<li>may be <code>a-z</code> <code>0-9</code> containing <code>.</code>
+<code>-</code> or <code>_</code></li>
 <li>length is backend dependent</li>
 </ul>
-<p>Each backend can provide system metadata that it understands. Some backends can also store arbitrary user metadata.</p>
-<p>Where possible the key names are standardized, so, for example, it is possible to copy object metadata from s3 to azureblob for example and metadata will be translated appropriately.</p>
-<p>Some backends have limits on the size of the metadata and rclone will give errors on upload if they are exceeded.</p>
+<p>Each backend can provide system metadata that it understands. Some
+backends can also store arbitrary user metadata.</p>
+<p>Where possible the key names are standardized, so, for example, it is
+possible to copy object metadata from s3 to azureblob for example and
+metadata will be translated appropriately.</p>
+<p>Some backends have limits on the size of the metadata and rclone will
+give errors on upload if they are exceeded.</p>
 <h3 id="metadata-preservation">Metadata preservation</h3>
 <p>The goal of the implementation is to</p>
 <ol type="1">
 <li>Preserve metadata if at all possible</li>
 <li>Interpret metadata if at all possible</li>
 </ol>
-<p>The consequences of 1 is that you can copy an S3 object to a local disk then back to S3 losslessly. Likewise you can copy a local file with file attributes and xattrs from local disk to s3 and back again losslessly.</p>
-<p>The consequence of 2 is that you can copy an S3 object with metadata to Azureblob (say) and have the metadata appear on the Azureblob object also.</p>
+<p>The consequences of 1 is that you can copy an S3 object to a local
+disk then back to S3 losslessly. Likewise you can copy a local file with
+file attributes and xattrs from local disk to s3 and back again
+losslessly.</p>
+<p>The consequence of 2 is that you can copy an S3 object with metadata
+to Azureblob (say) and have the metadata appear on the Azureblob object
+also.</p>
 <h3 id="standard-system-metadata">Standard system metadata</h3>
-<p>Here is a table of standard system metadata which, if appropriate, a backend may implement.</p>
+<p>Here is a table of standard system metadata which, if appropriate, a
+backend may implement.</p>
 <table>
 <colgroup>
 <col style="width: 48%" />
@@ -6970,14 +11987,30 @@ rclone sync --interactive /path/to/files remote:current-backup</code></pre>
 </tr>
 </tbody>
 </table>
-<p>The metadata keys <code>mtime</code> and <code>content-type</code> will take precedence if supplied in the metadata over reading the <code>Content-Type</code> or modification time of the source object.</p>
-<p>Hashes are not included in system metadata as there is a well defined way of reading those already.</p>
+<p>The metadata keys <code>mtime</code> and <code>content-type</code>
+will take precedence if supplied in the metadata over reading the
+<code>Content-Type</code> or modification time of the source object.</p>
+<p>Hashes are not included in system metadata as there is a well defined
+way of reading those already.</p>
 <h2 id="options-90">Options</h2>
 <p>Rclone has a number of options to control its behaviour.</p>
-<p>Options that take parameters can have the values passed in two ways, <code>--option=value</code> or <code>--option value</code>. However boolean (true/false) options behave slightly differently to the other options in that <code>--boolean</code> sets the option to <code>true</code> and the absence of the flag sets it to <code>false</code>. It is also possible to specify <code>--boolean=false</code> or <code>--boolean=true</code>. Note that <code>--boolean false</code> is not valid - this is parsed as <code>--boolean</code> and the <code>false</code> is parsed as an extra command line argument for rclone.</p>
+<p>Options that take parameters can have the values passed in two ways,
+<code>--option=value</code> or <code>--option value</code>. However
+boolean (true/false) options behave slightly differently to the other
+options in that <code>--boolean</code> sets the option to
+<code>true</code> and the absence of the flag sets it to
+<code>false</code>. It is also possible to specify
+<code>--boolean=false</code> or <code>--boolean=true</code>. Note that
+<code>--boolean false</code> is not valid - this is parsed as
+<code>--boolean</code> and the <code>false</code> is parsed as an extra
+command line argument for rclone.</p>
 <h3 id="time-option">Time or duration options</h3>
-<p>TIME or DURATION options can be specified as a duration string or a time string.</p>
-<p>A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Default units are seconds or the following abbreviations are valid:</p>
+<p>TIME or DURATION options can be specified as a duration string or a
+time string.</p>
+<p>A duration string is a possibly signed sequence of decimal numbers,
+each with optional fraction and a unit suffix, such as "300ms", "-1.5h"
+or "2h45m". Default units are seconds or the following abbreviations are
+valid:</p>
 <ul>
 <li><code>ms</code> - Milliseconds</li>
 <li><code>s</code> - Seconds</li>
@@ -6988,260 +12021,637 @@ rclone sync --interactive /path/to/files remote:current-backup</code></pre>
 <li><code>M</code> - Months</li>
 <li><code>y</code> - Years</li>
 </ul>
-<p>These can also be specified as an absolute time in the following formats:</p>
+<p>These can also be specified as an absolute time in the following
+formats:</p>
 <ul>
-<li>RFC3339 - e.g. <code>2006-01-02T15:04:05Z</code> or <code>2006-01-02T15:04:05+07:00</code></li>
-<li>ISO8601 Date and time, local timezone - <code>2006-01-02T15:04:05</code></li>
-<li>ISO8601 Date and time, local timezone - <code>2006-01-02 15:04:05</code></li>
+<li>RFC3339 - e.g. <code>2006-01-02T15:04:05Z</code> or
+<code>2006-01-02T15:04:05+07:00</code></li>
+<li>ISO8601 Date and time, local timezone -
+<code>2006-01-02T15:04:05</code></li>
+<li>ISO8601 Date and time, local timezone -
+<code>2006-01-02 15:04:05</code></li>
 <li>ISO8601 Date - <code>2006-01-02</code> (YYYY-MM-DD)</li>
 </ul>
 <h3 id="size-option">Size options</h3>
-<p>Options which use SIZE use KiB (multiples of 1024 bytes) by default. However, a suffix of <code>B</code> for Byte, <code>K</code> for KiB, <code>M</code> for MiB, <code>G</code> for GiB, <code>T</code> for TiB and <code>P</code> for PiB may be used. These are the binary units, e.g. 1, 2**10, 2**20, 2**30 respectively.</p>
+<p>Options which use SIZE use KiB (multiples of 1024 bytes) by default.
+However, a suffix of <code>B</code> for Byte, <code>K</code> for KiB,
+<code>M</code> for MiB, <code>G</code> for GiB, <code>T</code> for TiB
+and <code>P</code> for PiB may be used. These are the binary units, e.g.
+1, 2**10, 2**20, 2**30 respectively.</p>
 <h3 id="backup-dirdir">--backup-dir=DIR</h3>
-<p>When using <code>sync</code>, <code>copy</code> or <code>move</code> any files which would have been overwritten or deleted are moved in their original hierarchy into this directory.</p>
-<p>If <code>--suffix</code> is set, then the moved files will have the suffix added to them. If there is a file with the same path (after the suffix has been added) in DIR, then it will be overwritten.</p>
-<p>The remote in use must support server-side move or copy and you must use the same remote as the destination of the sync. The backup directory must not overlap the destination directory without it being excluded by a filter rule.</p>
+<p>When using <code>sync</code>, <code>copy</code> or <code>move</code>
+any files which would have been overwritten or deleted are moved in
+their original hierarchy into this directory.</p>
+<p>If <code>--suffix</code> is set, then the moved files will have the
+suffix added to them. If there is a file with the same path (after the
+suffix has been added) in DIR, then it will be overwritten.</p>
+<p>The remote in use must support server-side move or copy and you must
+use the same remote as the destination of the sync. The backup directory
+must not overlap the destination directory without it being excluded by
+a filter rule.</p>
 <p>For example</p>
 <pre><code>rclone sync --interactive /path/to/local remote:current --backup-dir remote:old</code></pre>
-<p>will sync <code>/path/to/local</code> to <code>remote:current</code>, but for any files which would have been updated or deleted will be stored in <code>remote:old</code>.</p>
-<p>If running rclone from a script you might want to use today's date as the directory name passed to <code>--backup-dir</code> to store the old files, or you might want to pass <code>--suffix</code> with today's date.</p>
+<p>will sync <code>/path/to/local</code> to <code>remote:current</code>,
+but for any files which would have been updated or deleted will be
+stored in <code>remote:old</code>.</p>
+<p>If running rclone from a script you might want to use today's date as
+the directory name passed to <code>--backup-dir</code> to store the old
+files, or you might want to pass <code>--suffix</code> with today's
+date.</p>
 <p>See <code>--compare-dest</code> and <code>--copy-dest</code>.</p>
 <h3 id="bind-string">--bind string</h3>
-<p>Local address to bind to for outgoing connections. This can be an IPv4 address (1.2.3.4), an IPv6 address (1234::789A) or host name. If the host name doesn't resolve or resolves to more than one IP address it will give an error.</p>
-<p>You can use <code>--bind 0.0.0.0</code> to force rclone to use IPv4 addresses and <code>--bind ::0</code> to force rclone to use IPv6 addresses.</p>
+<p>Local address to bind to for outgoing connections. This can be an
+IPv4 address (1.2.3.4), an IPv6 address (1234::789A) or host name. If
+the host name doesn't resolve or resolves to more than one IP address it
+will give an error.</p>
+<p>You can use <code>--bind 0.0.0.0</code> to force rclone to use IPv4
+addresses and <code>--bind ::0</code> to force rclone to use IPv6
+addresses.</p>
 <h3 id="bwlimitbandwidth_spec">--bwlimit=BANDWIDTH_SPEC</h3>
 <p>This option controls the bandwidth limit. For example</p>
 <pre><code>--bwlimit 10M</code></pre>
-<p>would mean limit the upload and download bandwidth to 10 MiB/s. <strong>NB</strong> this is <strong>bytes</strong> per second not <strong>bits</strong> per second. To use a single limit, specify the desired bandwidth in KiB/s, or use a suffix B|K|M|G|T|P. The default is <code>0</code> which means to not limit bandwidth.</p>
-<p>The upload and download bandwidth can be specified separately, as <code>--bwlimit UP:DOWN</code>, so</p>
+<p>would mean limit the upload and download bandwidth to 10 MiB/s.
+<strong>NB</strong> this is <strong>bytes</strong> per second not
+<strong>bits</strong> per second. To use a single limit, specify the
+desired bandwidth in KiB/s, or use a suffix B|K|M|G|T|P. The default is
+<code>0</code> which means to not limit bandwidth.</p>
+<p>The upload and download bandwidth can be specified separately, as
+<code>--bwlimit UP:DOWN</code>, so</p>
 <pre><code>--bwlimit 10M:100k</code></pre>
-<p>would mean limit the upload bandwidth to 10 MiB/s and the download bandwidth to 100 KiB/s. Either limit can be "off" meaning no limit, so to just limit the upload bandwidth you would use</p>
+<p>would mean limit the upload bandwidth to 10 MiB/s and the download
+bandwidth to 100 KiB/s. Either limit can be "off" meaning no limit, so
+to just limit the upload bandwidth you would use</p>
 <pre><code>--bwlimit 10M:off</code></pre>
-<p>this would limit the upload bandwidth to 10 MiB/s but the download bandwidth would be unlimited.</p>
-<p>When specified as above the bandwidth limits last for the duration of run of the rclone binary.</p>
-<p>It is also possible to specify a "timetable" of limits, which will cause certain limits to be applied at certain times. To specify a timetable, format your entries as <code>WEEKDAY-HH:MM,BANDWIDTH WEEKDAY-HH:MM,BANDWIDTH...</code> where: <code>WEEKDAY</code> is optional element.</p>
+<p>this would limit the upload bandwidth to 10 MiB/s but the download
+bandwidth would be unlimited.</p>
+<p>When specified as above the bandwidth limits last for the duration of
+run of the rclone binary.</p>
+<p>It is also possible to specify a "timetable" of limits, which will
+cause certain limits to be applied at certain times. To specify a
+timetable, format your entries as
+<code>WEEKDAY-HH:MM,BANDWIDTH WEEKDAY-HH:MM,BANDWIDTH...</code> where:
+<code>WEEKDAY</code> is optional element.</p>
 <ul>
-<li><code>BANDWIDTH</code> can be a single number, e.g.<code>100k</code> or a pair of numbers for upload:download, e.g.<code>10M:1M</code>.</li>
-<li><code>WEEKDAY</code> can be written as the whole word or only using the first 3 characters. It is optional.</li>
+<li><code>BANDWIDTH</code> can be a single number, e.g.<code>100k</code>
+or a pair of numbers for upload:download, e.g.<code>10M:1M</code>.</li>
+<li><code>WEEKDAY</code> can be written as the whole word or only using
+the first 3 characters. It is optional.</li>
 <li><code>HH:MM</code> is an hour from 00:00 to 23:59.</li>
 </ul>
 <p>Entries can be separated by spaces or semicolons.</p>
-<p><strong>Note:</strong> Semicolons can be used as separators instead of spaces to avoid parsing issues in environments like Docker.</p>
-<p>An example of a typical timetable to avoid link saturation during daytime working hours could be:</p>
-<p>Using spaces as separators: <code>--bwlimit "08:00,512k 12:00,10M 13:00,512k 18:00,30M 23:00,off"</code></p>
-<p>Using semicolons as separators: <code>--bwlimit "08:00,512k;12:00,10M;13:00,512k;18:00,30M;23:00,off"</code></p>
-<p>In these examples, the transfer bandwidth will be set to 512 KiB/s at 8am every day. At noon, it will rise to 10 MiB/s, and drop back to 512 KiB/sec at 1pm. At 6pm, the bandwidth limit will be set to 30 MiB/s, and at 11pm it will be completely disabled (full speed). Anything between 11pm and 8am will remain unlimited.</p>
+<p><strong>Note:</strong> Semicolons can be used as separators instead
+of spaces to avoid parsing issues in environments like Docker.</p>
+<p>An example of a typical timetable to avoid link saturation during
+daytime working hours could be:</p>
+<p>Using spaces as separators:
+<code>--bwlimit "08:00,512k 12:00,10M 13:00,512k 18:00,30M 23:00,off"</code></p>
+<p>Using semicolons as separators:
+<code>--bwlimit "08:00,512k;12:00,10M;13:00,512k;18:00,30M;23:00,off"</code></p>
+<p>In these examples, the transfer bandwidth will be set to 512 KiB/s at
+8am every day. At noon, it will rise to 10 MiB/s, and drop back to 512
+KiB/sec at 1pm. At 6pm, the bandwidth limit will be set to 30 MiB/s, and
+at 11pm it will be completely disabled (full speed). Anything between
+11pm and 8am will remain unlimited.</p>
 <p>An example of timetable with <code>WEEKDAY</code> could be:</p>
-<p>Using spaces as separators: <code>--bwlimit "Mon-00:00,512 Fri-23:59,10M Sat-10:00,1M Sun-20:00,off"</code></p>
-<p>Using semicolons as separators: <code>--bwlimit "Mon-00:00,512;Fri-23:59,10M;Sat-10:00,1M;Sun-20:00,off"</code></p>
-<p>It means that, the transfer bandwidth will be set to 512 KiB/s on Monday. It will rise to 10 MiB/s before the end of Friday. At 10:00 on Saturday it will be set to 1 MiB/s. From 20:00 on Sunday it will be unlimited.</p>
-<p>Timeslots without <code>WEEKDAY</code> are extended to the whole week. So this example:</p>
+<p>Using spaces as separators:
+<code>--bwlimit "Mon-00:00,512 Fri-23:59,10M Sat-10:00,1M Sun-20:00,off"</code></p>
+<p>Using semicolons as separators:
+<code>--bwlimit "Mon-00:00,512;Fri-23:59,10M;Sat-10:00,1M;Sun-20:00,off"</code></p>
+<p>It means that, the transfer bandwidth will be set to 512 KiB/s on
+Monday. It will rise to 10 MiB/s before the end of Friday. At 10:00 on
+Saturday it will be set to 1 MiB/s. From 20:00 on Sunday it will be
+unlimited.</p>
+<p>Timeslots without <code>WEEKDAY</code> are extended to the whole
+week. So this example:</p>
 <p><code>--bwlimit "Mon-00:00,512 12:00,1M Sun-20:00,off"</code></p>
 <p>Is equivalent to this:</p>
 <p><code>--bwlimit "Mon-00:00,512Mon-12:00,1M Tue-12:00,1M Wed-12:00,1M Thu-12:00,1M Fri-12:00,1M Sat-12:00,1M Sun-12:00,1M Sun-20:00,off"</code></p>
-<p>Bandwidth limit apply to the data transfer for all backends. For most backends the directory listing bandwidth is also included (exceptions being the non HTTP backends, <code>ftp</code>, <code>sftp</code> and <code>storj</code>).</p>
-<p>Note that the units are <strong>Byte/s</strong>, not <strong>bit/s</strong>. Typically connections are measured in bit/s - to convert divide by 8. For example, let's say you have a 10 Mbit/s connection and you wish rclone to use half of it - 5 Mbit/s. This is 5/8 = 0.625 MiB/s so you would use a <code>--bwlimit 0.625M</code> parameter for rclone.</p>
-<p>On Unix systems (Linux, macOS, …) the bandwidth limiter can be toggled by sending a <code>SIGUSR2</code> signal to rclone. This allows to remove the limitations of a long running rclone transfer and to restore it back to the value specified with <code>--bwlimit</code> quickly when needed. Assuming there is only one rclone instance running, you can toggle the limiter like this:</p>
+<p>Bandwidth limit apply to the data transfer for all backends. For most
+backends the directory listing bandwidth is also included (exceptions
+being the non HTTP backends, <code>ftp</code>, <code>sftp</code> and
+<code>storj</code>).</p>
+<p>Note that the units are <strong>Byte/s</strong>, not
+<strong>bit/s</strong>. Typically connections are measured in bit/s - to
+convert divide by 8. For example, let's say you have a 10 Mbit/s
+connection and you wish rclone to use half of it - 5 Mbit/s. This is 5/8
+= 0.625 MiB/s so you would use a <code>--bwlimit 0.625M</code> parameter
+for rclone.</p>
+<p>On Unix systems (Linux, macOS, …) the bandwidth limiter can be
+toggled by sending a <code>SIGUSR2</code> signal to rclone. This allows
+to remove the limitations of a long running rclone transfer and to
+restore it back to the value specified with <code>--bwlimit</code>
+quickly when needed. Assuming there is only one rclone instance running,
+you can toggle the limiter like this:</p>
 <pre><code>kill -SIGUSR2 $(pidof rclone)</code></pre>
-<p>If you configure rclone with a <a href="/rc">remote control</a> then you can use change the bwlimit dynamically:</p>
+<p>If you configure rclone with a <a href="/rc">remote control</a> then
+you can use change the bwlimit dynamically:</p>
 <pre><code>rclone rc core/bwlimit rate=1M</code></pre>
 <h3 id="bwlimit-filebandwidth_spec">--bwlimit-file=BANDWIDTH_SPEC</h3>
-<p>This option controls per file bandwidth limit. For the options see the <code>--bwlimit</code> flag.</p>
-<p>For example use this to allow no transfers to be faster than 1 MiB/s</p>
+<p>This option controls per file bandwidth limit. For the options see
+the <code>--bwlimit</code> flag.</p>
+<p>For example use this to allow no transfers to be faster than 1
+MiB/s</p>
 <pre><code>--bwlimit-file 1M</code></pre>
 <p>This can be used in conjunction with <code>--bwlimit</code>.</p>
-<p>Note that if a schedule is provided the file will use the schedule in effect at the start of the transfer.</p>
+<p>Note that if a schedule is provided the file will use the schedule in
+effect at the start of the transfer.</p>
 <h3 id="buffer-sizesize">--buffer-size=SIZE</h3>
-<p>Use this sized buffer to speed up file transfers. Each <code>--transfer</code> will use this much memory for buffering.</p>
-<p>When using <code>mount</code> or <code>cmount</code> each open file descriptor will use this much memory for buffering. See the <a href="https://rclone.org/commands/rclone_mount/#file-buffering">mount</a> documentation for more details.</p>
-<p>Set to <code>0</code> to disable the buffering for the minimum memory usage.</p>
-<p>Note that the memory allocation of the buffers is influenced by the <a href="#use-mmap">--use-mmap</a> flag.</p>
+<p>Use this sized buffer to speed up file transfers. Each
+<code>--transfer</code> will use this much memory for buffering.</p>
+<p>When using <code>mount</code> or <code>cmount</code> each open file
+descriptor will use this much memory for buffering. See the <a
+href="https://rclone.org/commands/rclone_mount/#file-buffering">mount</a>
+documentation for more details.</p>
+<p>Set to <code>0</code> to disable the buffering for the minimum memory
+usage.</p>
+<p>Note that the memory allocation of the buffers is influenced by the
+<a href="#use-mmap">--use-mmap</a> flag.</p>
 <h3 id="cache-dirdir">--cache-dir=DIR</h3>
-<p>Specify the directory rclone will use for caching, to override the default.</p>
-<p>Default value is depending on operating system: - Windows <code>%LocalAppData%\rclone</code>, if <code>LocalAppData</code> is defined. - macOS <code>$HOME/Library/Caches/rclone</code> if <code>HOME</code> is defined. - Unix <code>$XDG_CACHE_HOME/rclone</code> if <code>XDG_CACHE_HOME</code> is defined, else <code>$HOME/.cache/rclone</code> if <code>HOME</code> is defined. - Fallback (on all OS) to <code>$TMPDIR/rclone</code>, where <code>TMPDIR</code> is the value from <a href="#temp-dir-dir">--temp-dir</a>.</p>
-<p>You can use the <a href="https://rclone.org/commands/rclone_config_paths/">config paths</a> command to see the current value.</p>
-<p>Cache directory is heavily used by the <a href="https://rclone.org/commands/rclone_mount/#vfs-file-caching">VFS File Caching</a> mount feature, but also by <a href="https://rclone.org/commands/rclone_serve/">serve</a>, <a href="/gui">GUI</a> and other parts of rclone.</p>
+<p>Specify the directory rclone will use for caching, to override the
+default.</p>
+<p>Default value is depending on operating system: - Windows
+<code>%LocalAppData%\rclone</code>, if <code>LocalAppData</code> is
+defined. - macOS <code>$HOME/Library/Caches/rclone</code> if
+<code>HOME</code> is defined. - Unix <code>$XDG_CACHE_HOME/rclone</code>
+if <code>XDG_CACHE_HOME</code> is defined, else
+<code>$HOME/.cache/rclone</code> if <code>HOME</code> is defined. -
+Fallback (on all OS) to <code>$TMPDIR/rclone</code>, where
+<code>TMPDIR</code> is the value from <a
+href="#temp-dir-dir">--temp-dir</a>.</p>
+<p>You can use the <a
+href="https://rclone.org/commands/rclone_config_paths/">config paths</a>
+command to see the current value.</p>
+<p>Cache directory is heavily used by the <a
+href="https://rclone.org/commands/rclone_mount/#vfs-file-caching">VFS
+File Caching</a> mount feature, but also by <a
+href="https://rclone.org/commands/rclone_serve/">serve</a>, <a
+href="/gui">GUI</a> and other parts of rclone.</p>
 <h3 id="check-first">--check-first</h3>
-<p>If this flag is set then in a <code>sync</code>, <code>copy</code> or <code>move</code>, rclone will do all the checks to see whether files need to be transferred before doing any of the transfers. Normally rclone would start running transfers as soon as possible.</p>
-<p>This flag can be useful on IO limited systems where transfers interfere with checking.</p>
-<p>It can also be useful to ensure perfect ordering when using <code>--order-by</code>.</p>
-<p>If both <code>--check-first</code> and <code>--order-by</code> are set when doing <code>rclone move</code> then rclone will use the transfer thread to delete source files which don't need transferring. This will enable perfect ordering of the transfers and deletes but will cause the transfer stats to have more items in than expected.</p>
-<p>Using this flag can use more memory as it effectively sets <code>--max-backlog</code> to infinite. This means that all the info on the objects to transfer is held in memory before the transfers start.</p>
+<p>If this flag is set then in a <code>sync</code>, <code>copy</code> or
+<code>move</code>, rclone will do all the checks to see whether files
+need to be transferred before doing any of the transfers. Normally
+rclone would start running transfers as soon as possible.</p>
+<p>This flag can be useful on IO limited systems where transfers
+interfere with checking.</p>
+<p>It can also be useful to ensure perfect ordering when using
+<code>--order-by</code>.</p>
+<p>If both <code>--check-first</code> and <code>--order-by</code> are
+set when doing <code>rclone move</code> then rclone will use the
+transfer thread to delete source files which don't need transferring.
+This will enable perfect ordering of the transfers and deletes but will
+cause the transfer stats to have more items in than expected.</p>
+<p>Using this flag can use more memory as it effectively sets
+<code>--max-backlog</code> to infinite. This means that all the info on
+the objects to transfer is held in memory before the transfers
+start.</p>
 <h3 id="checkersn">--checkers=N</h3>
-<p>Originally controlling just the number of file checkers to run in parallel, e.g. by <code>rclone copy</code>. Now a fairly universal parallelism control used by <code>rclone</code> in several places.</p>
-<p>Note: checkers do the equality checking of files during a sync. For some storage systems (e.g. S3, Swift, Dropbox) this can take a significant amount of time so they are run in parallel.</p>
-<p>The default is to run 8 checkers in parallel. However, in case of slow-reacting backends you may need to lower (rather than increase) this default by setting <code>--checkers</code> to 4 or less threads. This is especially advised if you are experiencing backend server crashes during file checking phase (e.g. on subsequent or top-up backups where little or no file copying is done and checking takes up most of the time). Increase this setting only with utmost care, while monitoring your server health and file checking throughput.</p>
+<p>Originally controlling just the number of file checkers to run in
+parallel, e.g. by <code>rclone copy</code>. Now a fairly universal
+parallelism control used by <code>rclone</code> in several places.</p>
+<p>Note: checkers do the equality checking of files during a sync. For
+some storage systems (e.g. S3, Swift, Dropbox) this can take a
+significant amount of time so they are run in parallel.</p>
+<p>The default is to run 8 checkers in parallel. However, in case of
+slow-reacting backends you may need to lower (rather than increase) this
+default by setting <code>--checkers</code> to 4 or less threads. This is
+especially advised if you are experiencing backend server crashes during
+file checking phase (e.g. on subsequent or top-up backups where little
+or no file copying is done and checking takes up most of the time).
+Increase this setting only with utmost care, while monitoring your
+server health and file checking throughput.</p>
 <h3 id="c---checksum">-c, --checksum</h3>
-<p>Normally rclone will look at modification time and size of files to see if they are equal. If you set this flag then rclone will check the file hash and size to determine if files are equal.</p>
-<p>This is useful when the remote doesn't support setting modified time and a more accurate sync is desired than just checking the file size.</p>
-<p>This is very useful when transferring between remotes which store the same hash type on the object, e.g. Drive and Swift. For details of which remotes support which hash type see the table in the <a href="https://rclone.org/overview/">overview section</a>.</p>
-<p>Eg <code>rclone --checksum sync s3:/bucket swift:/bucket</code> would run much quicker than without the <code>--checksum</code> flag.</p>
-<p>When using this flag, rclone won't update mtimes of remote files if they are incorrect as it would normally.</p>
+<p>Normally rclone will look at modification time and size of files to
+see if they are equal. If you set this flag then rclone will check the
+file hash and size to determine if files are equal.</p>
+<p>This is useful when the remote doesn't support setting modified time
+and a more accurate sync is desired than just checking the file
+size.</p>
+<p>This is very useful when transferring between remotes which store the
+same hash type on the object, e.g. Drive and Swift. For details of which
+remotes support which hash type see the table in the <a
+href="https://rclone.org/overview/">overview section</a>.</p>
+<p>Eg <code>rclone --checksum sync s3:/bucket swift:/bucket</code> would
+run much quicker than without the <code>--checksum</code> flag.</p>
+<p>When using this flag, rclone won't update mtimes of remote files if
+they are incorrect as it would normally.</p>
 <h3 id="color-when">--color WHEN</h3>
-<p>Specify when colors (and other ANSI codes) should be added to the output.</p>
-<p><code>AUTO</code> (default) only allows ANSI codes when the output is a terminal</p>
+<p>Specify when colors (and other ANSI codes) should be added to the
+output.</p>
+<p><code>AUTO</code> (default) only allows ANSI codes when the output is
+a terminal</p>
 <p><code>NEVER</code> never allow ANSI codes</p>
-<p><code>ALWAYS</code> always add ANSI codes, regardless of the output format (terminal or file)</p>
+<p><code>ALWAYS</code> always add ANSI codes, regardless of the output
+format (terminal or file)</p>
 <h3 id="compare-destdir">--compare-dest=DIR</h3>
-<p>When using <code>sync</code>, <code>copy</code> or <code>move</code> DIR is checked in addition to the destination for files. If a file identical to the source is found that file is NOT copied from source. This is useful to copy just files that have changed since the last backup.</p>
-<p>You must use the same remote as the destination of the sync. The compare directory must not overlap the destination directory.</p>
+<p>When using <code>sync</code>, <code>copy</code> or <code>move</code>
+DIR is checked in addition to the destination for files. If a file
+identical to the source is found that file is NOT copied from source.
+This is useful to copy just files that have changed since the last
+backup.</p>
+<p>You must use the same remote as the destination of the sync. The
+compare directory must not overlap the destination directory.</p>
 <p>See <code>--copy-dest</code> and <code>--backup-dir</code>.</p>
 <h3 id="configconfig_file">--config=CONFIG_FILE</h3>
-<p>Specify the location of the rclone configuration file, to override the default. E.g. <code>rclone config --config="rclone.conf"</code>.</p>
-<p>The exact default is a bit complex to describe, due to changes introduced through different versions of rclone while preserving backwards compatibility, but in most cases it is as simple as:</p>
+<p>Specify the location of the rclone configuration file, to override
+the default. E.g. <code>rclone config --config="rclone.conf"</code>.</p>
+<p>The exact default is a bit complex to describe, due to changes
+introduced through different versions of rclone while preserving
+backwards compatibility, but in most cases it is as simple as:</p>
 <ul>
 <li><code>%APPDATA%/rclone/rclone.conf</code> on Windows</li>
 <li><code>~/.config/rclone/rclone.conf</code> on other</li>
 </ul>
-<p>The complete logic is as follows: Rclone will look for an existing configuration file in any of the following locations, in priority order:</p>
+<p>The complete logic is as follows: Rclone will look for an existing
+configuration file in any of the following locations, in priority
+order:</p>
 <ol type="1">
-<li><code>rclone.conf</code> (in program directory, where rclone executable is)</li>
+<li><code>rclone.conf</code> (in program directory, where rclone
+executable is)</li>
 <li><code>%APPDATA%/rclone/rclone.conf</code> (only on Windows)</li>
-<li><code>$XDG_CONFIG_HOME/rclone/rclone.conf</code> (on all systems, including Windows)</li>
-<li><code>~/.config/rclone/rclone.conf</code> (see below for explanation of ~ symbol)</li>
+<li><code>$XDG_CONFIG_HOME/rclone/rclone.conf</code> (on all systems,
+including Windows)</li>
+<li><code>~/.config/rclone/rclone.conf</code> (see below for explanation
+of ~ symbol)</li>
 <li><code>~/.rclone.conf</code></li>
 </ol>
-<p>If no existing configuration file is found, then a new one will be created in the following location:</p>
+<p>If no existing configuration file is found, then a new one will be
+created in the following location:</p>
 <ul>
-<li>On Windows: Location 2 listed above, except in the unlikely event that <code>APPDATA</code> is not defined, then location 4 is used instead.</li>
-<li>On Unix: Location 3 if <code>XDG_CONFIG_HOME</code> is defined, else location 4.</li>
-<li>Fallback to location 5 (on all OS), when the rclone directory cannot be created, but if also a home directory was not found then path <code>.rclone.conf</code> relative to current working directory will be used as a final resort.</li>
+<li>On Windows: Location 2 listed above, except in the unlikely event
+that <code>APPDATA</code> is not defined, then location 4 is used
+instead.</li>
+<li>On Unix: Location 3 if <code>XDG_CONFIG_HOME</code> is defined, else
+location 4.</li>
+<li>Fallback to location 5 (on all OS), when the rclone directory cannot
+be created, but if also a home directory was not found then path
+<code>.rclone.conf</code> relative to current working directory will be
+used as a final resort.</li>
 </ul>
-<p>The <code>~</code> symbol in paths above represent the home directory of the current user on any OS, and the value is defined as following:</p>
+<p>The <code>~</code> symbol in paths above represent the home directory
+of the current user on any OS, and the value is defined as
+following:</p>
 <ul>
-<li>On Windows: <code>%HOME%</code> if defined, else <code>%USERPROFILE%</code>, or else <code>%HOMEDRIVE%\%HOMEPATH%</code>.</li>
-<li>On Unix: <code>$HOME</code> if defined, else by looking up current user in OS-specific user database (e.g. passwd file), or else use the result from shell command <code>cd &amp;&amp; pwd</code>.</li>
+<li>On Windows: <code>%HOME%</code> if defined, else
+<code>%USERPROFILE%</code>, or else
+<code>%HOMEDRIVE%\%HOMEPATH%</code>.</li>
+<li>On Unix: <code>$HOME</code> if defined, else by looking up current
+user in OS-specific user database (e.g. passwd file), or else use the
+result from shell command <code>cd &amp;&amp; pwd</code>.</li>
 </ul>
-<p>If you run <code>rclone config file</code> you will see where the default location is for you.</p>
-<p>The fact that an existing file <code>rclone.conf</code> in the same directory as the rclone executable is always preferred, means that it is easy to run in "portable" mode by downloading rclone executable to a writable directory and then create an empty file <code>rclone.conf</code> in the same directory.</p>
-<p>If the location is set to empty string <code>""</code> or path to a file with name <code>notfound</code>, or the os null device represented by value <code>NUL</code> on Windows and <code>/dev/null</code> on Unix systems, then rclone will keep the config file in memory only.</p>
-<p>The file format is basic <a href="https://en.wikipedia.org/wiki/INI_file#Format">INI</a>: Sections of text, led by a <code>[section]</code> header and followed by <code>key=value</code> entries on separate lines. In rclone each remote is represented by its own section, where the section name defines the name of the remote. Options are specified as the <code>key=value</code> entries, where the key is the option name without the <code>--backend-</code> prefix, in lowercase and with <code>_</code> instead of <code>-</code>. E.g. option <code>--mega-hard-delete</code> corresponds to key <code>hard_delete</code>. Only backend options can be specified. A special, and required, key <code>type</code> identifies the <a href="https://rclone.org/overview/">storage system</a>, where the value is the internal lowercase name as returned by command <code>rclone help backends</code>. Comments are indicated by <code>;</code> or <code>#</code> at the beginning of a line.</p>
+<p>If you run <code>rclone config file</code> you will see where the
+default location is for you.</p>
+<p>The fact that an existing file <code>rclone.conf</code> in the same
+directory as the rclone executable is always preferred, means that it is
+easy to run in "portable" mode by downloading rclone executable to a
+writable directory and then create an empty file
+<code>rclone.conf</code> in the same directory.</p>
+<p>If the location is set to empty string <code>""</code> or path to a
+file with name <code>notfound</code>, or the os null device represented
+by value <code>NUL</code> on Windows and <code>/dev/null</code> on Unix
+systems, then rclone will keep the config file in memory only.</p>
+<p>The file format is basic <a
+href="https://en.wikipedia.org/wiki/INI_file#Format">INI</a>: Sections
+of text, led by a <code>[section]</code> header and followed by
+<code>key=value</code> entries on separate lines. In rclone each remote
+is represented by its own section, where the section name defines the
+name of the remote. Options are specified as the <code>key=value</code>
+entries, where the key is the option name without the
+<code>--backend-</code> prefix, in lowercase and with <code>_</code>
+instead of <code>-</code>. E.g. option <code>--mega-hard-delete</code>
+corresponds to key <code>hard_delete</code>. Only backend options can be
+specified. A special, and required, key <code>type</code> identifies the
+<a href="https://rclone.org/overview/">storage system</a>, where the
+value is the internal lowercase name as returned by command
+<code>rclone help backends</code>. Comments are indicated by
+<code>;</code> or <code>#</code> at the beginning of a line.</p>
 <p>Example:</p>
 <pre><code>[megaremote]
 type = mega
 user = you@example.com
 pass = PDPcQVVjVtzFY-GTdDFozqBhTdsPg3qH</code></pre>
-<p>Note that passwords are in <a href="https://rclone.org/commands/rclone_obscure/">obscured</a> form. Also, many storage systems uses token-based authentication instead of passwords, and this requires additional steps. It is easier, and safer, to use the interactive command <code>rclone config</code> instead of manually editing the configuration file.</p>
-<p>The configuration file will typically contain login information, and should therefore have restricted permissions so that only the current user can read it. Rclone tries to ensure this when it writes the file. You may also choose to <a href="#configuration-encryption">encrypt</a> the file.</p>
-<p>When token-based authentication are used, the configuration file must be writable, because rclone needs to update the tokens inside it.</p>
-<p>To reduce risk of corrupting an existing configuration file, rclone will not write directly to it when saving changes. Instead it will first write to a new, temporary, file. If a configuration file already existed, it will (on Unix systems) try to mirror its permissions to the new file. Then it will rename the existing file to a temporary name as backup. Next, rclone will rename the new file to the correct name, before finally cleaning up by deleting the backup file.</p>
-<p>If the configuration file path used by rclone is a symbolic link, then this will be evaluated and rclone will write to the resolved path, instead of overwriting the symbolic link. Temporary files used in the process (described above) will be written to the same parent directory as that of the resolved configuration file, but if this directory is also a symbolic link it will not be resolved and the temporary files will be written to the location of the directory symbolic link.</p>
+<p>Note that passwords are in <a
+href="https://rclone.org/commands/rclone_obscure/">obscured</a> form.
+Also, many storage systems uses token-based authentication instead of
+passwords, and this requires additional steps. It is easier, and safer,
+to use the interactive command <code>rclone config</code> instead of
+manually editing the configuration file.</p>
+<p>The configuration file will typically contain login information, and
+should therefore have restricted permissions so that only the current
+user can read it. Rclone tries to ensure this when it writes the file.
+You may also choose to <a href="#configuration-encryption">encrypt</a>
+the file.</p>
+<p>When token-based authentication are used, the configuration file must
+be writable, because rclone needs to update the tokens inside it.</p>
+<p>To reduce risk of corrupting an existing configuration file, rclone
+will not write directly to it when saving changes. Instead it will first
+write to a new, temporary, file. If a configuration file already
+existed, it will (on Unix systems) try to mirror its permissions to the
+new file. Then it will rename the existing file to a temporary name as
+backup. Next, rclone will rename the new file to the correct name,
+before finally cleaning up by deleting the backup file.</p>
+<p>If the configuration file path used by rclone is a symbolic link,
+then this will be evaluated and rclone will write to the resolved path,
+instead of overwriting the symbolic link. Temporary files used in the
+process (described above) will be written to the same parent directory
+as that of the resolved configuration file, but if this directory is
+also a symbolic link it will not be resolved and the temporary files
+will be written to the location of the directory symbolic link.</p>
 <h3 id="contimeouttime">--contimeout=TIME</h3>
-<p>Set the connection timeout. This should be in go time format which looks like <code>5s</code> for 5 seconds, <code>10m</code> for 10 minutes, or <code>3h30m</code>.</p>
-<p>The connection timeout is the amount of time rclone will wait for a connection to go through to a remote object storage system. It is <code>1m</code> by default.</p>
+<p>Set the connection timeout. This should be in go time format which
+looks like <code>5s</code> for 5 seconds, <code>10m</code> for 10
+minutes, or <code>3h30m</code>.</p>
+<p>The connection timeout is the amount of time rclone will wait for a
+connection to go through to a remote object storage system. It is
+<code>1m</code> by default.</p>
 <h3 id="copy-destdir">--copy-dest=DIR</h3>
-<p>When using <code>sync</code>, <code>copy</code> or <code>move</code> DIR is checked in addition to the destination for files. If a file identical to the source is found that file is server-side copied from DIR to the destination. This is useful for incremental backup.</p>
-<p>The remote in use must support server-side copy and you must use the same remote as the destination of the sync. The compare directory must not overlap the destination directory.</p>
+<p>When using <code>sync</code>, <code>copy</code> or <code>move</code>
+DIR is checked in addition to the destination for files. If a file
+identical to the source is found that file is server-side copied from
+DIR to the destination. This is useful for incremental backup.</p>
+<p>The remote in use must support server-side copy and you must use the
+same remote as the destination of the sync. The compare directory must
+not overlap the destination directory.</p>
 <p>See <code>--compare-dest</code> and <code>--backup-dir</code>.</p>
 <h3 id="dedupe-mode-mode">--dedupe-mode MODE</h3>
-<p>Mode to run dedupe command in. One of <code>interactive</code>, <code>skip</code>, <code>first</code>, <code>newest</code>, <code>oldest</code>, <code>rename</code>. The default is <code>interactive</code>.<br />
-See the dedupe command for more information as to what these options mean.</p>
+<p>Mode to run dedupe command in. One of <code>interactive</code>,
+<code>skip</code>, <code>first</code>, <code>newest</code>,
+<code>oldest</code>, <code>rename</code>. The default is
+<code>interactive</code>.<br />
+See the dedupe command for more information as to what these options
+mean.</p>
 <h3 id="default-time-time">--default-time TIME</h3>
-<p>If a file or directory does have a modification time rclone can read then rclone will display this fixed time instead.</p>
-<p>The default is <code>2000-01-01 00:00:00 UTC</code>. This can be configured in any of the ways shown in <a href="#time-option">the time or duration options</a>.</p>
-<p>For example <code>--default-time 2020-06-01</code> to set the default time to the 1st of June 2020 or <code>--default-time 0s</code> to set the default time to the time rclone started up.</p>
+<p>If a file or directory does have a modification time rclone can read
+then rclone will display this fixed time instead.</p>
+<p>The default is <code>2000-01-01 00:00:00 UTC</code>. This can be
+configured in any of the ways shown in <a href="#time-option">the time
+or duration options</a>.</p>
+<p>For example <code>--default-time 2020-06-01</code> to set the default
+time to the 1st of June 2020 or <code>--default-time 0s</code> to set
+the default time to the time rclone started up.</p>
 <h3 id="disable-featurefeature...">--disable FEATURE,FEATURE,...</h3>
-<p>This disables a comma separated list of optional features. For example to disable server-side move and server-side copy use:</p>
+<p>This disables a comma separated list of optional features. For
+example to disable server-side move and server-side copy use:</p>
 <pre><code>--disable move,copy</code></pre>
 <p>The features can be put in any case.</p>
 <p>To see a list of which features can be disabled use:</p>
 <pre><code>--disable help</code></pre>
 <p>The features a remote has can be seen in JSON format with:</p>
 <pre><code>rclone backend features remote:</code></pre>
-<p>See the overview <a href="https://rclone.org/overview/#features">features</a> and <a href="https://rclone.org/overview/#optional-features">optional features</a> to get an idea of which feature does what.</p>
-<p>Note that some features can be set to <code>true</code> if they are <code>true</code>/<code>false</code> feature flag features by prefixing them with <code>!</code>. For example the <code>CaseInsensitive</code> feature can be forced to <code>false</code> with <code>--disable CaseInsensitive</code> and forced to <code>true</code> with <code>--disable '!CaseInsensitive'</code>. In general it isn't a good idea doing this but it may be useful in extremis.</p>
-<p>(Note that <code>!</code> is a shell command which you will need to escape with single quotes or a backslash on unix like platforms.)</p>
-<p>This flag can be useful for debugging and in exceptional circumstances (e.g. Google Drive limiting the total volume of Server Side Copies to 100 GiB/day).</p>
+<p>See the overview <a
+href="https://rclone.org/overview/#features">features</a> and <a
+href="https://rclone.org/overview/#optional-features">optional
+features</a> to get an idea of which feature does what.</p>
+<p>Note that some features can be set to <code>true</code> if they are
+<code>true</code>/<code>false</code> feature flag features by prefixing
+them with <code>!</code>. For example the <code>CaseInsensitive</code>
+feature can be forced to <code>false</code> with
+<code>--disable CaseInsensitive</code> and forced to <code>true</code>
+with <code>--disable '!CaseInsensitive'</code>. In general it isn't a
+good idea doing this but it may be useful in extremis.</p>
+<p>(Note that <code>!</code> is a shell command which you will need to
+escape with single quotes or a backslash on unix like platforms.)</p>
+<p>This flag can be useful for debugging and in exceptional
+circumstances (e.g. Google Drive limiting the total volume of Server
+Side Copies to 100 GiB/day).</p>
 <h3 id="disable-http2">--disable-http2</h3>
-<p>This stops rclone from trying to use HTTP/2 if available. This can sometimes speed up transfers due to a <a href="https://github.com/golang/go/issues/37373">problem in the Go standard library</a>.</p>
+<p>This stops rclone from trying to use HTTP/2 if available. This can
+sometimes speed up transfers due to a <a
+href="https://github.com/golang/go/issues/37373">problem in the Go
+standard library</a>.</p>
 <h3 id="dscp-value">--dscp VALUE</h3>
-<p>Specify a DSCP value or name to use in connections. This could help QoS system to identify traffic class. BE, EF, DF, LE, CSx and AFxx are allowed.</p>
-<p>See the description of <a href="https://en.wikipedia.org/wiki/Differentiated_services">differentiated services</a> to get an idea of this field. Setting this to 1 (LE) to identify the flow to SCAVENGER class can avoid occupying too much bandwidth in a network with DiffServ support (<a href="https://tools.ietf.org/html/rfc8622">RFC 8622</a>).</p>
-<p>For example, if you configured QoS on router to handle LE properly. Running:</p>
+<p>Specify a DSCP value or name to use in connections. This could help
+QoS system to identify traffic class. BE, EF, DF, LE, CSx and AFxx are
+allowed.</p>
+<p>See the description of <a
+href="https://en.wikipedia.org/wiki/Differentiated_services">differentiated
+services</a> to get an idea of this field. Setting this to 1 (LE) to
+identify the flow to SCAVENGER class can avoid occupying too much
+bandwidth in a network with DiffServ support (<a
+href="https://tools.ietf.org/html/rfc8622">RFC 8622</a>).</p>
+<p>For example, if you configured QoS on router to handle LE properly.
+Running:</p>
 <pre><code>rclone copy --dscp LE from:/from to:/to</code></pre>
 <p>would make the priority lower than usual internet flows.</p>
-<p>This option has no effect on Windows (see <a href="https://github.com/golang/go/issues/42728">golang/go#42728</a>).</p>
+<p>This option has no effect on Windows (see <a
+href="https://github.com/golang/go/issues/42728">golang/go#42728</a>).</p>
 <h3 id="n---dry-run">-n, --dry-run</h3>
-<p>Do a trial run with no permanent changes. Use this to see what rclone would do without actually doing it. Useful when setting up the <code>sync</code> command which deletes files in the destination.</p>
+<p>Do a trial run with no permanent changes. Use this to see what rclone
+would do without actually doing it. Useful when setting up the
+<code>sync</code> command which deletes files in the destination.</p>
 <h3 id="expect-continue-timeouttime">--expect-continue-timeout=TIME</h3>
-<p>This specifies the amount of time to wait for a server's first response headers after fully writing the request headers if the request has an "Expect: 100-continue" header. Not all backends support using this.</p>
-<p>Zero means no timeout and causes the body to be sent immediately, without waiting for the server to approve. This time does not include the time to send the request header.</p>
+<p>This specifies the amount of time to wait for a server's first
+response headers after fully writing the request headers if the request
+has an "Expect: 100-continue" header. Not all backends support using
+this.</p>
+<p>Zero means no timeout and causes the body to be sent immediately,
+without waiting for the server to approve. This time does not include
+the time to send the request header.</p>
 <p>The default is <code>1s</code>. Set to <code>0</code> to disable.</p>
 <h3 id="error-on-no-transfer">--error-on-no-transfer</h3>
-<p>By default, rclone will exit with return code 0 if there were no errors.</p>
-<p>This option allows rclone to return exit code 9 if no files were transferred between the source and destination. This allows using rclone in scripts, and triggering follow-on actions if data was copied, or skipping if not.</p>
-<p>NB: Enabling this option turns a usually non-fatal error into a potentially fatal one - please check and adjust your scripts accordingly!</p>
+<p>By default, rclone will exit with return code 0 if there were no
+errors.</p>
+<p>This option allows rclone to return exit code 9 if no files were
+transferred between the source and destination. This allows using rclone
+in scripts, and triggering follow-on actions if data was copied, or
+skipping if not.</p>
+<p>NB: Enabling this option turns a usually non-fatal error into a
+potentially fatal one - please check and adjust your scripts
+accordingly!</p>
 <h3 id="fix-case">--fix-case</h3>
-<p>Normally, a sync to a case insensitive dest (such as macOS / Windows) will not result in a matching filename if the source and dest filenames have casing differences but are otherwise identical. For example, syncing <code>hello.txt</code> to <code>HELLO.txt</code> will normally result in the dest filename remaining <code>HELLO.txt</code>. If <code>--fix-case</code> is set, then <code>HELLO.txt</code> will be renamed to <code>hello.txt</code> to match the source.</p>
-<p>NB: - directory names with incorrect casing will also be fixed - <code>--fix-case</code> will be ignored if <code>--immutable</code> is set - using <code>--local-case-sensitive</code> instead is not advisable; it will cause <code>HELLO.txt</code> to get deleted! - the old dest filename must not be excluded by filters. Be especially careful with <a href="https://rclone.org/filtering/#files-from-read-list-of-source-file-names"><code>--files-from</code></a>, which does not respect <a href="https://rclone.org/filtering/#ignore-case-make-searches-case-insensitive"><code>--ignore-case</code></a>! - on remotes that do not support server-side move, <code>--fix-case</code> will require downloading the file and re-uploading it. To avoid this, do not use <code>--fix-case</code>.</p>
-<h3 id="fs-cache-expire-durationtime">--fs-cache-expire-duration=TIME</h3>
-<p>When using rclone via the API rclone caches created remotes for 5 minutes by default in the "fs cache". This means that if you do repeated actions on the same remote then rclone won't have to build it again from scratch, which makes it more efficient.</p>
-<p>This flag sets the time that the remotes are cached for. If you set it to <code>0</code> (or negative) then rclone won't cache the remotes at all.</p>
-<p>Note that if you use some flags, eg <code>--backup-dir</code> and if this is set to <code>0</code> rclone may build two remotes (one for the source or destination and one for the <code>--backup-dir</code> where it may have only built one before.</p>
-<h3 id="fs-cache-expire-intervaltime">--fs-cache-expire-interval=TIME</h3>
-<p>This controls how often rclone checks for cached remotes to expire. See the <code>--fs-cache-expire-duration</code> documentation above for more info. The default is 60s, set to 0 to disable expiry.</p>
+<p>Normally, a sync to a case insensitive dest (such as macOS / Windows)
+will not result in a matching filename if the source and dest filenames
+have casing differences but are otherwise identical. For example,
+syncing <code>hello.txt</code> to <code>HELLO.txt</code> will normally
+result in the dest filename remaining <code>HELLO.txt</code>. If
+<code>--fix-case</code> is set, then <code>HELLO.txt</code> will be
+renamed to <code>hello.txt</code> to match the source.</p>
+<p>NB: - directory names with incorrect casing will also be fixed -
+<code>--fix-case</code> will be ignored if <code>--immutable</code> is
+set - using <code>--local-case-sensitive</code> instead is not
+advisable; it will cause <code>HELLO.txt</code> to get deleted! - the
+old dest filename must not be excluded by filters. Be especially careful
+with <a
+href="https://rclone.org/filtering/#files-from-read-list-of-source-file-names"><code>--files-from</code></a>,
+which does not respect <a
+href="https://rclone.org/filtering/#ignore-case-make-searches-case-insensitive"><code>--ignore-case</code></a>!
+- on remotes that do not support server-side move,
+<code>--fix-case</code> will require downloading the file and
+re-uploading it. To avoid this, do not use <code>--fix-case</code>.</p>
+<h3
+id="fs-cache-expire-durationtime">--fs-cache-expire-duration=TIME</h3>
+<p>When using rclone via the API rclone caches created remotes for 5
+minutes by default in the "fs cache". This means that if you do repeated
+actions on the same remote then rclone won't have to build it again from
+scratch, which makes it more efficient.</p>
+<p>This flag sets the time that the remotes are cached for. If you set
+it to <code>0</code> (or negative) then rclone won't cache the remotes
+at all.</p>
+<p>Note that if you use some flags, eg <code>--backup-dir</code> and if
+this is set to <code>0</code> rclone may build two remotes (one for the
+source or destination and one for the <code>--backup-dir</code> where it
+may have only built one before.</p>
+<h3
+id="fs-cache-expire-intervaltime">--fs-cache-expire-interval=TIME</h3>
+<p>This controls how often rclone checks for cached remotes to expire.
+See the <code>--fs-cache-expire-duration</code> documentation above for
+more info. The default is 60s, set to 0 to disable expiry.</p>
 <h3 id="header">--header</h3>
-<p>Add an HTTP header for all transactions. The flag can be repeated to add multiple headers.</p>
-<p>If you want to add headers only for uploads use <code>--header-upload</code> and if you want to add headers only for downloads use <code>--header-download</code>.</p>
-<p>This flag is supported for all HTTP based backends even those not supported by <code>--header-upload</code> and <code>--header-download</code> so may be used as a workaround for those with care.</p>
+<p>Add an HTTP header for all transactions. The flag can be repeated to
+add multiple headers.</p>
+<p>If you want to add headers only for uploads use
+<code>--header-upload</code> and if you want to add headers only for
+downloads use <code>--header-download</code>.</p>
+<p>This flag is supported for all HTTP based backends even those not
+supported by <code>--header-upload</code> and
+<code>--header-download</code> so may be used as a workaround for those
+with care.</p>
 <pre><code>rclone ls remote:test --header &quot;X-Rclone: Foo&quot; --header &quot;X-LetMeIn: Yes&quot;</code></pre>
 <h3 id="header-download">--header-download</h3>
-<p>Add an HTTP header for all download transactions. The flag can be repeated to add multiple headers.</p>
+<p>Add an HTTP header for all download transactions. The flag can be
+repeated to add multiple headers.</p>
 <pre><code>rclone sync --interactive s3:test/src ~/dst --header-download &quot;X-Amz-Meta-Test: Foo&quot; --header-download &quot;X-Amz-Meta-Test2: Bar&quot;</code></pre>
-<p>See the GitHub issue <a href="https://github.com/rclone/rclone/issues/59">here</a> for currently supported backends.</p>
+<p>See the GitHub issue <a
+href="https://github.com/rclone/rclone/issues/59">here</a> for currently
+supported backends.</p>
 <h3 id="header-upload">--header-upload</h3>
-<p>Add an HTTP header for all upload transactions. The flag can be repeated to add multiple headers.</p>
+<p>Add an HTTP header for all upload transactions. The flag can be
+repeated to add multiple headers.</p>
 <pre><code>rclone sync --interactive ~/src s3:test/dst --header-upload &quot;Content-Disposition: attachment; filename=&#39;cool.html&#39;&quot; --header-upload &quot;X-Amz-Meta-Test: FooBar&quot;</code></pre>
-<p>See the GitHub issue <a href="https://github.com/rclone/rclone/issues/59">here</a> for currently supported backends.</p>
+<p>See the GitHub issue <a
+href="https://github.com/rclone/rclone/issues/59">here</a> for currently
+supported backends.</p>
 <h3 id="human-readable">--human-readable</h3>
-<p>Rclone commands output values for sizes (e.g. number of bytes) and counts (e.g. number of files) either as <em>raw</em> numbers, or in <em>human-readable</em> format.</p>
-<p>In human-readable format the values are scaled to larger units, indicated with a suffix shown after the value, and rounded to three decimals. Rclone consistently uses binary units (powers of 2) for sizes and decimal units (powers of 10) for counts. The unit prefix for size is according to IEC standard notation, e.g. <code>Ki</code> for kibi. Used with byte unit, <code>1 KiB</code> means 1024 Byte. In list type of output, only the unit prefix appended to the value (e.g. <code>9.762Ki</code>), while in more textual output the full unit is shown (e.g. <code>9.762 KiB</code>). For counts the SI standard notation is used, e.g. prefix <code>k</code> for kilo. Used with file counts, <code>1k</code> means 1000 files.</p>
-<p>The various <a href="https://rclone.org/commands/rclone_ls/">list</a> commands output raw numbers by default. Option <code>--human-readable</code> will make them output values in human-readable format instead (with the short unit prefix).</p>
-<p>The <a href="https://rclone.org/commands/rclone_about/">about</a> command outputs human-readable by default, with a command-specific option <code>--full</code> to output the raw numbers instead.</p>
-<p>Command <a href="https://rclone.org/commands/rclone_size/">size</a> outputs both human-readable and raw numbers in the same output.</p>
-<p>The <a href="https://rclone.org/commands/rclone_tree/">tree</a> command also considers <code>--human-readable</code>, but it will not use the exact same notation as the other commands: It rounds to one decimal, and uses single letter suffix, e.g. <code>K</code> instead of <code>Ki</code>. The reason for this is that it relies on an external library.</p>
-<p>The interactive command <a href="https://rclone.org/commands/rclone_ncdu/">ncdu</a> shows human-readable by default, and responds to key <code>u</code> for toggling human-readable format.</p>
+<p>Rclone commands output values for sizes (e.g. number of bytes) and
+counts (e.g. number of files) either as <em>raw</em> numbers, or in
+<em>human-readable</em> format.</p>
+<p>In human-readable format the values are scaled to larger units,
+indicated with a suffix shown after the value, and rounded to three
+decimals. Rclone consistently uses binary units (powers of 2) for sizes
+and decimal units (powers of 10) for counts. The unit prefix for size is
+according to IEC standard notation, e.g. <code>Ki</code> for kibi. Used
+with byte unit, <code>1 KiB</code> means 1024 Byte. In list type of
+output, only the unit prefix appended to the value (e.g.
+<code>9.762Ki</code>), while in more textual output the full unit is
+shown (e.g. <code>9.762 KiB</code>). For counts the SI standard notation
+is used, e.g. prefix <code>k</code> for kilo. Used with file counts,
+<code>1k</code> means 1000 files.</p>
+<p>The various <a href="https://rclone.org/commands/rclone_ls/">list</a>
+commands output raw numbers by default. Option
+<code>--human-readable</code> will make them output values in
+human-readable format instead (with the short unit prefix).</p>
+<p>The <a href="https://rclone.org/commands/rclone_about/">about</a>
+command outputs human-readable by default, with a command-specific
+option <code>--full</code> to output the raw numbers instead.</p>
+<p>Command <a href="https://rclone.org/commands/rclone_size/">size</a>
+outputs both human-readable and raw numbers in the same output.</p>
+<p>The <a href="https://rclone.org/commands/rclone_tree/">tree</a>
+command also considers <code>--human-readable</code>, but it will not
+use the exact same notation as the other commands: It rounds to one
+decimal, and uses single letter suffix, e.g. <code>K</code> instead of
+<code>Ki</code>. The reason for this is that it relies on an external
+library.</p>
+<p>The interactive command <a
+href="https://rclone.org/commands/rclone_ncdu/">ncdu</a> shows
+human-readable by default, and responds to key <code>u</code> for
+toggling human-readable format.</p>
 <h3 id="ignore-case-sync">--ignore-case-sync</h3>
-<p>Using this option will cause rclone to ignore the case of the files when synchronizing so files will not be copied/synced when the existing filenames are the same, even if the casing is different.</p>
+<p>Using this option will cause rclone to ignore the case of the files
+when synchronizing so files will not be copied/synced when the existing
+filenames are the same, even if the casing is different.</p>
 <h3 id="ignore-checksum">--ignore-checksum</h3>
-<p>Normally rclone will check that the checksums of transferred files match, and give an error "corrupted on transfer" if they don't.</p>
-<p>You can use this option to skip that check. You should only use it if you have had the "corrupted on transfer" error message and you are sure you might want to transfer potentially corrupted data.</p>
+<p>Normally rclone will check that the checksums of transferred files
+match, and give an error "corrupted on transfer" if they don't.</p>
+<p>You can use this option to skip that check. You should only use it if
+you have had the "corrupted on transfer" error message and you are sure
+you might want to transfer potentially corrupted data.</p>
 <h3 id="ignore-existing">--ignore-existing</h3>
-<p>Using this option will make rclone unconditionally skip all files that exist on the destination, no matter the content of these files.</p>
-<p>While this isn't a generally recommended option, it can be useful in cases where your files change due to encryption. However, it cannot correct partial transfers in case a transfer was interrupted.</p>
-<p>When performing a <code>move</code>/<code>moveto</code> command, this flag will leave skipped files in the source location unchanged when a file with the same name exists on the destination.</p>
+<p>Using this option will make rclone unconditionally skip all files
+that exist on the destination, no matter the content of these files.</p>
+<p>While this isn't a generally recommended option, it can be useful in
+cases where your files change due to encryption. However, it cannot
+correct partial transfers in case a transfer was interrupted.</p>
+<p>When performing a <code>move</code>/<code>moveto</code> command, this
+flag will leave skipped files in the source location unchanged when a
+file with the same name exists on the destination.</p>
 <h3 id="ignore-size">--ignore-size</h3>
-<p>Normally rclone will look at modification time and size of files to see if they are equal. If you set this flag then rclone will check only the modification time. If <code>--checksum</code> is set then it only checks the checksum.</p>
-<p>It will also cause rclone to skip verifying the sizes are the same after transfer.</p>
-<p>This can be useful for transferring files to and from OneDrive which occasionally misreports the size of image files (see <a href="https://github.com/rclone/rclone/issues/399">#399</a> for more info).</p>
+<p>Normally rclone will look at modification time and size of files to
+see if they are equal. If you set this flag then rclone will check only
+the modification time. If <code>--checksum</code> is set then it only
+checks the checksum.</p>
+<p>It will also cause rclone to skip verifying the sizes are the same
+after transfer.</p>
+<p>This can be useful for transferring files to and from OneDrive which
+occasionally misreports the size of image files (see <a
+href="https://github.com/rclone/rclone/issues/399">#399</a> for more
+info).</p>
 <h3 id="i---ignore-times">-I, --ignore-times</h3>
-<p>Using this option will cause rclone to unconditionally upload all files regardless of the state of files on the destination.</p>
-<p>Normally rclone would skip any files that have the same modification time and are the same size (or have the same checksum if using <code>--checksum</code>).</p>
+<p>Using this option will cause rclone to unconditionally upload all
+files regardless of the state of files on the destination.</p>
+<p>Normally rclone would skip any files that have the same modification
+time and are the same size (or have the same checksum if using
+<code>--checksum</code>).</p>
 <h3 id="immutable">--immutable</h3>
-<p>Treat source and destination files as immutable and disallow modification.</p>
-<p>With this option set, files will be created and deleted as requested, but existing files will never be updated. If an existing file does not match between the source and destination, rclone will give the error <code>Source and destination exist but do not match: immutable file modified</code>.</p>
-<p>Note that only commands which transfer files (e.g. <code>sync</code>, <code>copy</code>, <code>move</code>) are affected by this behavior, and only modification is disallowed. Files may still be deleted explicitly (e.g. <code>delete</code>, <code>purge</code>) or implicitly (e.g. <code>sync</code>, <code>move</code>). Use <code>copy --immutable</code> if it is desired to avoid deletion as well as modification.</p>
-<p>This can be useful as an additional layer of protection for immutable or append-only data sets (notably backup archives), where modification implies corruption and should not be propagated.</p>
+<p>Treat source and destination files as immutable and disallow
+modification.</p>
+<p>With this option set, files will be created and deleted as requested,
+but existing files will never be updated. If an existing file does not
+match between the source and destination, rclone will give the error
+<code>Source and destination exist but do not match: immutable file modified</code>.</p>
+<p>Note that only commands which transfer files (e.g. <code>sync</code>,
+<code>copy</code>, <code>move</code>) are affected by this behavior, and
+only modification is disallowed. Files may still be deleted explicitly
+(e.g. <code>delete</code>, <code>purge</code>) or implicitly (e.g.
+<code>sync</code>, <code>move</code>). Use <code>copy --immutable</code>
+if it is desired to avoid deletion as well as modification.</p>
+<p>This can be useful as an additional layer of protection for immutable
+or append-only data sets (notably backup archives), where modification
+implies corruption and should not be propagated.</p>
 <h3 id="inplace">--inplace</h3>
-<p>The <code>--inplace</code> flag changes the behaviour of rclone when uploading files to some backends (backends with the <code>PartialUploads</code> feature flag set) such as:</p>
+<p>The <code>--inplace</code> flag changes the behaviour of rclone when
+uploading files to some backends (backends with the
+<code>PartialUploads</code> feature flag set) such as:</p>
 <ul>
 <li>local</li>
 <li>ftp</li>
 <li>sftp</li>
 <li>pcloud</li>
 </ul>
-<p>Without <code>--inplace</code> (the default) rclone will first upload to a temporary file with an extension like this, where <code>XXXXXX</code> represents a hash of the source file's fingerprint and <code>.partial</code> is <a href="#partial-suffix">--partial-suffix</a> value (<code>.partial</code> by default).</p>
+<p>Without <code>--inplace</code> (the default) rclone will first upload
+to a temporary file with an extension like this, where
+<code>XXXXXX</code> represents a hash of the source file's fingerprint
+and <code>.partial</code> is <a
+href="#partial-suffix">--partial-suffix</a> value (<code>.partial</code>
+by default).</p>
 <pre><code>original-file-name.XXXXXX.partial</code></pre>
-<p>(rclone will make sure the final name is no longer than 100 characters by truncating the <code>original-file-name</code> part if necessary).</p>
-<p>When the upload is complete, rclone will rename the <code>.partial</code> file to the correct name, overwriting any existing file at that point. If the upload fails then the <code>.partial</code> file will be deleted.</p>
-<p>This prevents other users of the backend from seeing partially uploaded files in their new names and prevents overwriting the old file until the new one is completely uploaded.</p>
-<p>If the <code>--inplace</code> flag is supplied, rclone will upload directly to the final name without creating a <code>.partial</code> file.</p>
-<p>This means that an incomplete file will be visible in the directory listings while the upload is in progress and any existing files will be overwritten as soon as the upload starts. If the transfer fails then the file will be deleted. This can cause data loss of the existing file if the transfer fails.</p>
-<p>Note that on the local file system if you don't use <code>--inplace</code> hard links (Unix only) will be broken. And if you do use <code>--inplace</code> you won't be able to update in use executables.</p>
-<p>Note also that versions of rclone prior to v1.63.0 behave as if the <code>--inplace</code> flag is always supplied.</p>
+<p>(rclone will make sure the final name is no longer than 100
+characters by truncating the <code>original-file-name</code> part if
+necessary).</p>
+<p>When the upload is complete, rclone will rename the
+<code>.partial</code> file to the correct name, overwriting any existing
+file at that point. If the upload fails then the <code>.partial</code>
+file will be deleted.</p>
+<p>This prevents other users of the backend from seeing partially
+uploaded files in their new names and prevents overwriting the old file
+until the new one is completely uploaded.</p>
+<p>If the <code>--inplace</code> flag is supplied, rclone will upload
+directly to the final name without creating a <code>.partial</code>
+file.</p>
+<p>This means that an incomplete file will be visible in the directory
+listings while the upload is in progress and any existing files will be
+overwritten as soon as the upload starts. If the transfer fails then the
+file will be deleted. This can cause data loss of the existing file if
+the transfer fails.</p>
+<p>Note that on the local file system if you don't use
+<code>--inplace</code> hard links (Unix only) will be broken. And if you
+do use <code>--inplace</code> you won't be able to update in use
+executables.</p>
+<p>Note also that versions of rclone prior to v1.63.0 behave as if the
+<code>--inplace</code> flag is always supplied.</p>
 <h3 id="interactive">-i, --interactive</h3>
-<p>This flag can be used to tell rclone that you wish a manual confirmation before destructive operations.</p>
-<p>It is <strong>recommended</strong> that you use this flag while learning rclone especially with <code>rclone sync</code>.</p>
+<p>This flag can be used to tell rclone that you wish a manual
+confirmation before destructive operations.</p>
+<p>It is <strong>recommended</strong> that you use this flag while
+learning rclone especially with <code>rclone sync</code>.</p>
 <p>For example</p>
 <pre><code>$ rclone delete --interactive /tmp/dir
 rclone: delete &quot;important-file.txt&quot;?
@@ -7253,411 +12663,945 @@ q) Exit rclone now.
 y/n/s/!/q&gt; n</code></pre>
 <p>The options mean</p>
 <ul>
-<li><code>y</code>: <strong>Yes</strong>, this operation should go ahead. You can also press Return for this to happen. You'll be asked every time unless you choose <code>s</code> or <code>!</code>.</li>
-<li><code>n</code>: <strong>No</strong>, do not do this operation. You'll be asked every time unless you choose <code>s</code> or <code>!</code>.</li>
-<li><code>s</code>: <strong>Skip</strong> all the following operations of this type with no more questions. This takes effect until rclone exits. If there are any different kind of operations you'll be prompted for them.</li>
-<li><code>!</code>: <strong>Do all</strong> the following operations with no more questions. Useful if you've decided that you don't mind rclone doing that kind of operation. This takes effect until rclone exits . If there are any different kind of operations you'll be prompted for them.</li>
+<li><code>y</code>: <strong>Yes</strong>, this operation should go
+ahead. You can also press Return for this to happen. You'll be asked
+every time unless you choose <code>s</code> or <code>!</code>.</li>
+<li><code>n</code>: <strong>No</strong>, do not do this operation.
+You'll be asked every time unless you choose <code>s</code> or
+<code>!</code>.</li>
+<li><code>s</code>: <strong>Skip</strong> all the following operations
+of this type with no more questions. This takes effect until rclone
+exits. If there are any different kind of operations you'll be prompted
+for them.</li>
+<li><code>!</code>: <strong>Do all</strong> the following operations
+with no more questions. Useful if you've decided that you don't mind
+rclone doing that kind of operation. This takes effect until rclone
+exits . If there are any different kind of operations you'll be prompted
+for them.</li>
 <li><code>q</code>: <strong>Quit</strong> rclone now, just in case!</li>
 </ul>
 <h3 id="leave-root">--leave-root</h3>
-<p>During rmdirs it will not remove root directory, even if it's empty.</p>
+<p>During rmdirs it will not remove root directory, even if it's
+empty.</p>
 <h3 id="log-filefile">--log-file=FILE</h3>
-<p>Log all of rclone's output to FILE. This is not active by default. This can be useful for tracking down problems with syncs in combination with the <code>-v</code> flag. See the <a href="#logging">Logging section</a> for more info.</p>
+<p>Log all of rclone's output to FILE. This is not active by default.
+This can be useful for tracking down problems with syncs in combination
+with the <code>-v</code> flag. See the <a href="#logging">Logging
+section</a> for more info.</p>
 <p>If FILE exists then rclone will append to it.</p>
-<p>Note that if you are using the <code>logrotate</code> program to manage rclone's logs, then you should use the <code>copytruncate</code> option as rclone doesn't have a signal to rotate logs.</p>
+<p>Note that if you are using the <code>logrotate</code> program to
+manage rclone's logs, then you should use the <code>copytruncate</code>
+option as rclone doesn't have a signal to rotate logs.</p>
 <h3 id="log-format-list">--log-format LIST</h3>
-<p>Comma separated list of log format options. Accepted options are <code>date</code>, <code>time</code>, <code>microseconds</code>, <code>pid</code>, <code>longfile</code>, <code>shortfile</code>, <code>UTC</code>. Any other keywords will be silently ignored. <code>pid</code> will tag log messages with process identifier which useful with <code>rclone mount --daemon</code>. Other accepted options are explained in the <a href="https://pkg.go.dev/log#pkg-constants">go documentation</a>. The default log format is "<code>date</code>,<code>time</code>".</p>
+<p>Comma separated list of log format options. Accepted options are
+<code>date</code>, <code>time</code>, <code>microseconds</code>,
+<code>pid</code>, <code>longfile</code>, <code>shortfile</code>,
+<code>UTC</code>. Any other keywords will be silently ignored.
+<code>pid</code> will tag log messages with process identifier which
+useful with <code>rclone mount --daemon</code>. Other accepted options
+are explained in the <a href="https://pkg.go.dev/log#pkg-constants">go
+documentation</a>. The default log format is
+"<code>date</code>,<code>time</code>".</p>
 <h3 id="log-level-level">--log-level LEVEL</h3>
-<p>This sets the log level for rclone. The default log level is <code>NOTICE</code>.</p>
-<p><code>DEBUG</code> is equivalent to <code>-vv</code>. It outputs lots of debug info - useful for bug reports and really finding out what rclone is doing.</p>
-<p><code>INFO</code> is equivalent to <code>-v</code>. It outputs information about each transfer and prints stats once a minute by default.</p>
-<p><code>NOTICE</code> is the default log level if no logging flags are supplied. It outputs very little when things are working normally. It outputs warnings and significant events.</p>
-<p><code>ERROR</code> is equivalent to <code>-q</code>. It only outputs error messages.</p>
+<p>This sets the log level for rclone. The default log level is
+<code>NOTICE</code>.</p>
+<p><code>DEBUG</code> is equivalent to <code>-vv</code>. It outputs lots
+of debug info - useful for bug reports and really finding out what
+rclone is doing.</p>
+<p><code>INFO</code> is equivalent to <code>-v</code>. It outputs
+information about each transfer and prints stats once a minute by
+default.</p>
+<p><code>NOTICE</code> is the default log level if no logging flags are
+supplied. It outputs very little when things are working normally. It
+outputs warnings and significant events.</p>
+<p><code>ERROR</code> is equivalent to <code>-q</code>. It only outputs
+error messages.</p>
 <h3 id="use-json-log">--use-json-log</h3>
-<p>This switches the log format to JSON for rclone. The fields of json log are level, msg, source, time.</p>
+<p>This switches the log format to JSON for rclone. The fields of json
+log are level, msg, source, time.</p>
 <h3 id="low-level-retries-number">--low-level-retries NUMBER</h3>
 <p>This controls the number of low level retries rclone does.</p>
-<p>A low level retry is used to retry a failing operation - typically one HTTP request. This might be uploading a chunk of a big file for example. You will see low level retries in the log with the <code>-v</code> flag.</p>
-<p>This shouldn't need to be changed from the default in normal operations. However, if you get a lot of low level retries you may wish to reduce the value so rclone moves on to a high level retry (see the <code>--retries</code> flag) quicker.</p>
-<p>Disable low level retries with <code>--low-level-retries 1</code>.</p>
+<p>A low level retry is used to retry a failing operation - typically
+one HTTP request. This might be uploading a chunk of a big file for
+example. You will see low level retries in the log with the
+<code>-v</code> flag.</p>
+<p>This shouldn't need to be changed from the default in normal
+operations. However, if you get a lot of low level retries you may wish
+to reduce the value so rclone moves on to a high level retry (see the
+<code>--retries</code> flag) quicker.</p>
+<p>Disable low level retries with
+<code>--low-level-retries 1</code>.</p>
 <h3 id="max-backlogn">--max-backlog=N</h3>
-<p>This is the maximum allowable backlog of files in a sync/copy/move queued for being checked or transferred.</p>
-<p>This can be set arbitrarily large. It will only use memory when the queue is in use. Note that it will use in the order of N KiB of memory when the backlog is in use.</p>
-<p>Setting this large allows rclone to calculate how many files are pending more accurately, give a more accurate estimated finish time and make <code>--order-by</code> work more accurately.</p>
-<p>Setting this small will make rclone more synchronous to the listings of the remote which may be desirable.</p>
-<p>Setting this to a negative number will make the backlog as large as possible.</p>
+<p>This is the maximum allowable backlog of files in a sync/copy/move
+queued for being checked or transferred.</p>
+<p>This can be set arbitrarily large. It will only use memory when the
+queue is in use. Note that it will use in the order of N KiB of memory
+when the backlog is in use.</p>
+<p>Setting this large allows rclone to calculate how many files are
+pending more accurately, give a more accurate estimated finish time and
+make <code>--order-by</code> work more accurately.</p>
+<p>Setting this small will make rclone more synchronous to the listings
+of the remote which may be desirable.</p>
+<p>Setting this to a negative number will make the backlog as large as
+possible.</p>
 <h3 id="max-deleten">--max-delete=N</h3>
-<p>This tells rclone not to delete more than N files. If that limit is exceeded then a fatal error will be generated and rclone will stop the operation in progress.</p>
+<p>This tells rclone not to delete more than N files. If that limit is
+exceeded then a fatal error will be generated and rclone will stop the
+operation in progress.</p>
 <h3 id="max-delete-sizesize">--max-delete-size=SIZE</h3>
-<p>Rclone will stop deleting files when the total size of deletions has reached the size specified. It defaults to off.</p>
-<p>If that limit is exceeded then a fatal error will be generated and rclone will stop the operation in progress.</p>
+<p>Rclone will stop deleting files when the total size of deletions has
+reached the size specified. It defaults to off.</p>
+<p>If that limit is exceeded then a fatal error will be generated and
+rclone will stop the operation in progress.</p>
 <h3 id="max-depthn">--max-depth=N</h3>
-<p>This modifies the recursion depth for all the commands except purge.</p>
-<p>So if you do <code>rclone --max-depth 1 ls remote:path</code> you will see only the files in the top level directory. Using <code>--max-depth 2</code> means you will see all the files in first two directory levels and so on.</p>
-<p>For historical reasons the <code>lsd</code> command defaults to using a <code>--max-depth</code> of 1 - you can override this with the command line flag.</p>
-<p>You can use this command to disable recursion (with <code>--max-depth 1</code>).</p>
-<p>Note that if you use this with <code>sync</code> and <code>--delete-excluded</code> the files not recursed through are considered excluded and will be deleted on the destination. Test first with <code>--dry-run</code> if you are not sure what will happen.</p>
+<p>This modifies the recursion depth for all the commands except
+purge.</p>
+<p>So if you do <code>rclone --max-depth 1 ls remote:path</code> you
+will see only the files in the top level directory. Using
+<code>--max-depth 2</code> means you will see all the files in first two
+directory levels and so on.</p>
+<p>For historical reasons the <code>lsd</code> command defaults to using
+a <code>--max-depth</code> of 1 - you can override this with the command
+line flag.</p>
+<p>You can use this command to disable recursion (with
+<code>--max-depth 1</code>).</p>
+<p>Note that if you use this with <code>sync</code> and
+<code>--delete-excluded</code> the files not recursed through are
+considered excluded and will be deleted on the destination. Test first
+with <code>--dry-run</code> if you are not sure what will happen.</p>
 <h3 id="max-durationtime">--max-duration=TIME</h3>
-<p>Rclone will stop transferring when it has run for the duration specified. Defaults to off.</p>
-<p>When the limit is reached all transfers will stop immediately. Use <code>--cutoff-mode</code> to modify this behaviour.</p>
-<p>Rclone will exit with exit code 10 if the duration limit is reached.</p>
+<p>Rclone will stop transferring when it has run for the duration
+specified. Defaults to off.</p>
+<p>When the limit is reached all transfers will stop immediately. Use
+<code>--cutoff-mode</code> to modify this behaviour.</p>
+<p>Rclone will exit with exit code 10 if the duration limit is
+reached.</p>
 <h3 id="max-transfersize">--max-transfer=SIZE</h3>
-<p>Rclone will stop transferring when it has reached the size specified. Defaults to off.</p>
-<p>When the limit is reached all transfers will stop immediately. Use <code>--cutoff-mode</code> to modify this behaviour.</p>
-<p>Rclone will exit with exit code 8 if the transfer limit is reached.</p>
-<h3 id="cutoff-modehardsoftcautious">--cutoff-mode=hard|soft|cautious</h3>
-<p>This modifies the behavior of <code>--max-transfer</code> and <code>--max-duration</code> Defaults to <code>--cutoff-mode=hard</code>.</p>
-<p>Specifying <code>--cutoff-mode=hard</code> will stop transferring immediately when Rclone reaches the limit.</p>
-<p>Specifying <code>--cutoff-mode=soft</code> will stop starting new transfers when Rclone reaches the limit.</p>
-<p>Specifying <code>--cutoff-mode=cautious</code> will try to prevent Rclone from reaching the limit. Only applicable for <code>--max-transfer</code></p>
+<p>Rclone will stop transferring when it has reached the size specified.
+Defaults to off.</p>
+<p>When the limit is reached all transfers will stop immediately. Use
+<code>--cutoff-mode</code> to modify this behaviour.</p>
+<p>Rclone will exit with exit code 8 if the transfer limit is
+reached.</p>
+<h3
+id="cutoff-modehardsoftcautious">--cutoff-mode=hard|soft|cautious</h3>
+<p>This modifies the behavior of <code>--max-transfer</code> and
+<code>--max-duration</code> Defaults to
+<code>--cutoff-mode=hard</code>.</p>
+<p>Specifying <code>--cutoff-mode=hard</code> will stop transferring
+immediately when Rclone reaches the limit.</p>
+<p>Specifying <code>--cutoff-mode=soft</code> will stop starting new
+transfers when Rclone reaches the limit.</p>
+<p>Specifying <code>--cutoff-mode=cautious</code> will try to prevent
+Rclone from reaching the limit. Only applicable for
+<code>--max-transfer</code></p>
 <h2 id="m---metadata">-M, --metadata</h2>
-<p>Setting this flag enables rclone to copy the metadata from the source to the destination. For local backends this is ownership, permissions, xattr etc. See the <a href="#metadata">metadata section</a> for more info.</p>
+<p>Setting this flag enables rclone to copy the metadata from the source
+to the destination. For local backends this is ownership, permissions,
+xattr etc. See the <a href="#metadata">metadata section</a> for more
+info.</p>
 <h3 id="metadata-mapper">--metadata-mapper SpaceSepList</h3>
-<p>If you supply the parameter <code>--metadata-mapper /path/to/program</code> then rclone will use that program to map metadata from source object to destination object.</p>
-<p>The argument to this flag should be a command with an optional space separated list of arguments. If one of the arguments has a space in then enclose it in <code>"</code>, if you want a literal <code>"</code> in an argument then enclose the argument in <code>"</code> and double the <code>"</code>. See <a href="https://godoc.org/encoding/csv">CSV encoding</a> for more info.</p>
+<p>If you supply the parameter
+<code>--metadata-mapper /path/to/program</code> then rclone will use
+that program to map metadata from source object to destination
+object.</p>
+<p>The argument to this flag should be a command with an optional space
+separated list of arguments. If one of the arguments has a space in then
+enclose it in <code>"</code>, if you want a literal <code>"</code> in an
+argument then enclose the argument in <code>"</code> and double the
+<code>"</code>. See <a href="https://godoc.org/encoding/csv">CSV
+encoding</a> for more info.</p>
 <pre><code>--metadata-mapper &quot;python bin/test_metadata_mapper.py&quot;
 --metadata-mapper &#39;python bin/test_metadata_mapper.py &quot;argument with a space&quot;&#39;
 --metadata-mapper &#39;python bin/test_metadata_mapper.py &quot;argument with &quot;&quot;two&quot;&quot; quotes&quot;&#39;</code></pre>
-<p>This uses a simple JSON based protocol with input on STDIN and output on STDOUT. This will be called for every file and directory copied and may be called concurrently.</p>
-<p>The program's job is to take a metadata blob on the input and turn it into a metadata blob on the output suitable for the destination backend.</p>
-<p>Input to the program (via STDIN) might look like this. This provides some context for the <code>Metadata</code> which may be important.</p>
+<p>This uses a simple JSON based protocol with input on STDIN and output
+on STDOUT. This will be called for every file and directory copied and
+may be called concurrently.</p>
+<p>The program's job is to take a metadata blob on the input and turn it
+into a metadata blob on the output suitable for the destination
+backend.</p>
+<p>Input to the program (via STDIN) might look like this. This provides
+some context for the <code>Metadata</code> which may be important.</p>
 <ul>
-<li><code>SrcFs</code> is the config string for the remote that the object is currently on.</li>
+<li><code>SrcFs</code> is the config string for the remote that the
+object is currently on.</li>
 <li><code>SrcFsType</code> is the name of the source backend.</li>
-<li><code>DstFs</code> is the config string for the remote that the object is being copied to</li>
+<li><code>DstFs</code> is the config string for the remote that the
+object is being copied to</li>
 <li><code>DstFsType</code> is the name of the destination backend.</li>
-<li><code>Remote</code> is the path of the object relative to the root.</li>
-<li><code>Size</code>, <code>MimeType</code>, <code>ModTime</code> are attributes of the object.</li>
-<li><code>IsDir</code> is <code>true</code> if this is a directory (not yet implemented).</li>
-<li><code>ID</code> is the source <code>ID</code> of the object if known.</li>
-<li><code>Metadata</code> is the backend specific metadata as described in the backend docs.</li>
+<li><code>Remote</code> is the path of the object relative to the
+root.</li>
+<li><code>Size</code>, <code>MimeType</code>, <code>ModTime</code> are
+attributes of the object.</li>
+<li><code>IsDir</code> is <code>true</code> if this is a directory (not
+yet implemented).</li>
+<li><code>ID</code> is the source <code>ID</code> of the object if
+known.</li>
+<li><code>Metadata</code> is the backend specific metadata as described
+in the backend docs.</li>
 </ul>
-<div class="sourceCode" id="cb598"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb598-1"><a href="#cb598-1" aria-hidden="true"></a><span class="fu">{</span></span>
-<span id="cb598-2"><a href="#cb598-2" aria-hidden="true"></a>    <span class="dt">&quot;SrcFs&quot;</span><span class="fu">:</span> <span class="st">&quot;gdrive:&quot;</span><span class="fu">,</span></span>
-<span id="cb598-3"><a href="#cb598-3" aria-hidden="true"></a>    <span class="dt">&quot;SrcFsType&quot;</span><span class="fu">:</span> <span class="st">&quot;drive&quot;</span><span class="fu">,</span></span>
-<span id="cb598-4"><a href="#cb598-4" aria-hidden="true"></a>    <span class="dt">&quot;DstFs&quot;</span><span class="fu">:</span> <span class="st">&quot;newdrive:user&quot;</span><span class="fu">,</span></span>
-<span id="cb598-5"><a href="#cb598-5" aria-hidden="true"></a>    <span class="dt">&quot;DstFsType&quot;</span><span class="fu">:</span> <span class="st">&quot;onedrive&quot;</span><span class="fu">,</span></span>
-<span id="cb598-6"><a href="#cb598-6" aria-hidden="true"></a>    <span class="dt">&quot;Remote&quot;</span><span class="fu">:</span> <span class="st">&quot;test.txt&quot;</span><span class="fu">,</span></span>
-<span id="cb598-7"><a href="#cb598-7" aria-hidden="true"></a>    <span class="dt">&quot;Size&quot;</span><span class="fu">:</span> <span class="dv">6</span><span class="fu">,</span></span>
-<span id="cb598-8"><a href="#cb598-8" aria-hidden="true"></a>    <span class="dt">&quot;MimeType&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
-<span id="cb598-9"><a href="#cb598-9" aria-hidden="true"></a>    <span class="dt">&quot;ModTime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
-<span id="cb598-10"><a href="#cb598-10" aria-hidden="true"></a>    <span class="dt">&quot;IsDir&quot;</span><span class="fu">:</span> <span class="kw">false</span><span class="fu">,</span></span>
-<span id="cb598-11"><a href="#cb598-11" aria-hidden="true"></a>    <span class="dt">&quot;ID&quot;</span><span class="fu">:</span> <span class="st">&quot;xyz&quot;</span><span class="fu">,</span></span>
-<span id="cb598-12"><a href="#cb598-12" aria-hidden="true"></a>    <span class="dt">&quot;Metadata&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb598-13"><a href="#cb598-13" aria-hidden="true"></a>        <span class="dt">&quot;btime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T16:53:11Z&quot;</span><span class="fu">,</span></span>
-<span id="cb598-14"><a href="#cb598-14" aria-hidden="true"></a>        <span class="dt">&quot;content-type&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
-<span id="cb598-15"><a href="#cb598-15" aria-hidden="true"></a>        <span class="dt">&quot;mtime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
-<span id="cb598-16"><a href="#cb598-16" aria-hidden="true"></a>        <span class="dt">&quot;owner&quot;</span><span class="fu">:</span> <span class="st">&quot;user1@domain1.com&quot;</span><span class="fu">,</span></span>
-<span id="cb598-17"><a href="#cb598-17" aria-hidden="true"></a>        <span class="dt">&quot;permissions&quot;</span><span class="fu">:</span> <span class="st">&quot;...&quot;</span><span class="fu">,</span></span>
-<span id="cb598-18"><a href="#cb598-18" aria-hidden="true"></a>        <span class="dt">&quot;description&quot;</span><span class="fu">:</span> <span class="st">&quot;my nice file&quot;</span><span class="fu">,</span></span>
-<span id="cb598-19"><a href="#cb598-19" aria-hidden="true"></a>        <span class="dt">&quot;starred&quot;</span><span class="fu">:</span> <span class="st">&quot;false&quot;</span></span>
-<span id="cb598-20"><a href="#cb598-20" aria-hidden="true"></a>    <span class="fu">}</span></span>
-<span id="cb598-21"><a href="#cb598-21" aria-hidden="true"></a><span class="fu">}</span></span></code></pre></div>
-<p>The program should then modify the input as desired and send it to STDOUT. The returned <code>Metadata</code> field will be used in its entirety for the destination object. Any other fields will be ignored. Note in this example we translate user names and permissions and add something to the description:</p>
-<div class="sourceCode" id="cb599"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb599-1"><a href="#cb599-1" aria-hidden="true"></a><span class="fu">{</span></span>
-<span id="cb599-2"><a href="#cb599-2" aria-hidden="true"></a>    <span class="dt">&quot;Metadata&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb599-3"><a href="#cb599-3" aria-hidden="true"></a>        <span class="dt">&quot;btime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T16:53:11Z&quot;</span><span class="fu">,</span></span>
-<span id="cb599-4"><a href="#cb599-4" aria-hidden="true"></a>        <span class="dt">&quot;content-type&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
-<span id="cb599-5"><a href="#cb599-5" aria-hidden="true"></a>        <span class="dt">&quot;mtime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
-<span id="cb599-6"><a href="#cb599-6" aria-hidden="true"></a>        <span class="dt">&quot;owner&quot;</span><span class="fu">:</span> <span class="st">&quot;user1@domain2.com&quot;</span><span class="fu">,</span></span>
-<span id="cb599-7"><a href="#cb599-7" aria-hidden="true"></a>        <span class="dt">&quot;permissions&quot;</span><span class="fu">:</span> <span class="st">&quot;...&quot;</span><span class="fu">,</span></span>
-<span id="cb599-8"><a href="#cb599-8" aria-hidden="true"></a>        <span class="dt">&quot;description&quot;</span><span class="fu">:</span> <span class="st">&quot;my nice file [migrated from domain1]&quot;</span><span class="fu">,</span></span>
-<span id="cb599-9"><a href="#cb599-9" aria-hidden="true"></a>        <span class="dt">&quot;starred&quot;</span><span class="fu">:</span> <span class="st">&quot;false&quot;</span></span>
-<span id="cb599-10"><a href="#cb599-10" aria-hidden="true"></a>    <span class="fu">}</span></span>
-<span id="cb599-11"><a href="#cb599-11" aria-hidden="true"></a><span class="fu">}</span></span></code></pre></div>
+<div class="sourceCode" id="cb598"><pre
+class="sourceCode json"><code class="sourceCode json"><span id="cb598-1"><a href="#cb598-1" aria-hidden="true" tabindex="-1"></a><span class="fu">{</span></span>
+<span id="cb598-2"><a href="#cb598-2" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;SrcFs&quot;</span><span class="fu">:</span> <span class="st">&quot;gdrive:&quot;</span><span class="fu">,</span></span>
+<span id="cb598-3"><a href="#cb598-3" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;SrcFsType&quot;</span><span class="fu">:</span> <span class="st">&quot;drive&quot;</span><span class="fu">,</span></span>
+<span id="cb598-4"><a href="#cb598-4" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;DstFs&quot;</span><span class="fu">:</span> <span class="st">&quot;newdrive:user&quot;</span><span class="fu">,</span></span>
+<span id="cb598-5"><a href="#cb598-5" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;DstFsType&quot;</span><span class="fu">:</span> <span class="st">&quot;onedrive&quot;</span><span class="fu">,</span></span>
+<span id="cb598-6"><a href="#cb598-6" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;Remote&quot;</span><span class="fu">:</span> <span class="st">&quot;test.txt&quot;</span><span class="fu">,</span></span>
+<span id="cb598-7"><a href="#cb598-7" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;Size&quot;</span><span class="fu">:</span> <span class="dv">6</span><span class="fu">,</span></span>
+<span id="cb598-8"><a href="#cb598-8" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;MimeType&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
+<span id="cb598-9"><a href="#cb598-9" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;ModTime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
+<span id="cb598-10"><a href="#cb598-10" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;IsDir&quot;</span><span class="fu">:</span> <span class="kw">false</span><span class="fu">,</span></span>
+<span id="cb598-11"><a href="#cb598-11" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;ID&quot;</span><span class="fu">:</span> <span class="st">&quot;xyz&quot;</span><span class="fu">,</span></span>
+<span id="cb598-12"><a href="#cb598-12" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;Metadata&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb598-13"><a href="#cb598-13" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;btime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T16:53:11Z&quot;</span><span class="fu">,</span></span>
+<span id="cb598-14"><a href="#cb598-14" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;content-type&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
+<span id="cb598-15"><a href="#cb598-15" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;mtime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
+<span id="cb598-16"><a href="#cb598-16" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;owner&quot;</span><span class="fu">:</span> <span class="st">&quot;user1@domain1.com&quot;</span><span class="fu">,</span></span>
+<span id="cb598-17"><a href="#cb598-17" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;permissions&quot;</span><span class="fu">:</span> <span class="st">&quot;...&quot;</span><span class="fu">,</span></span>
+<span id="cb598-18"><a href="#cb598-18" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;description&quot;</span><span class="fu">:</span> <span class="st">&quot;my nice file&quot;</span><span class="fu">,</span></span>
+<span id="cb598-19"><a href="#cb598-19" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;starred&quot;</span><span class="fu">:</span> <span class="st">&quot;false&quot;</span></span>
+<span id="cb598-20"><a href="#cb598-20" aria-hidden="true" tabindex="-1"></a>    <span class="fu">}</span></span>
+<span id="cb598-21"><a href="#cb598-21" aria-hidden="true" tabindex="-1"></a><span class="fu">}</span></span></code></pre></div>
+<p>The program should then modify the input as desired and send it to
+STDOUT. The returned <code>Metadata</code> field will be used in its
+entirety for the destination object. Any other fields will be ignored.
+Note in this example we translate user names and permissions and add
+something to the description:</p>
+<div class="sourceCode" id="cb599"><pre
+class="sourceCode json"><code class="sourceCode json"><span id="cb599-1"><a href="#cb599-1" aria-hidden="true" tabindex="-1"></a><span class="fu">{</span></span>
+<span id="cb599-2"><a href="#cb599-2" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;Metadata&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb599-3"><a href="#cb599-3" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;btime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T16:53:11Z&quot;</span><span class="fu">,</span></span>
+<span id="cb599-4"><a href="#cb599-4" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;content-type&quot;</span><span class="fu">:</span> <span class="st">&quot;text/plain; charset=utf-8&quot;</span><span class="fu">,</span></span>
+<span id="cb599-5"><a href="#cb599-5" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;mtime&quot;</span><span class="fu">:</span> <span class="st">&quot;2022-10-11T17:53:10.286745272+01:00&quot;</span><span class="fu">,</span></span>
+<span id="cb599-6"><a href="#cb599-6" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;owner&quot;</span><span class="fu">:</span> <span class="st">&quot;user1@domain2.com&quot;</span><span class="fu">,</span></span>
+<span id="cb599-7"><a href="#cb599-7" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;permissions&quot;</span><span class="fu">:</span> <span class="st">&quot;...&quot;</span><span class="fu">,</span></span>
+<span id="cb599-8"><a href="#cb599-8" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;description&quot;</span><span class="fu">:</span> <span class="st">&quot;my nice file [migrated from domain1]&quot;</span><span class="fu">,</span></span>
+<span id="cb599-9"><a href="#cb599-9" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;starred&quot;</span><span class="fu">:</span> <span class="st">&quot;false&quot;</span></span>
+<span id="cb599-10"><a href="#cb599-10" aria-hidden="true" tabindex="-1"></a>    <span class="fu">}</span></span>
+<span id="cb599-11"><a href="#cb599-11" aria-hidden="true" tabindex="-1"></a><span class="fu">}</span></span></code></pre></div>
 <p>Metadata can be removed here too.</p>
-<p>An example python program might look something like this to implement the above transformations.</p>
-<div class="sourceCode" id="cb600"><pre class="sourceCode python"><code class="sourceCode python"><span id="cb600-1"><a href="#cb600-1" aria-hidden="true"></a><span class="im">import</span> sys, json</span>
-<span id="cb600-2"><a href="#cb600-2" aria-hidden="true"></a></span>
-<span id="cb600-3"><a href="#cb600-3" aria-hidden="true"></a>i <span class="op">=</span> json.load(sys.stdin)</span>
-<span id="cb600-4"><a href="#cb600-4" aria-hidden="true"></a>metadata <span class="op">=</span> i[<span class="st">&quot;Metadata&quot;</span>]</span>
-<span id="cb600-5"><a href="#cb600-5" aria-hidden="true"></a><span class="co"># Add tag to description</span></span>
-<span id="cb600-6"><a href="#cb600-6" aria-hidden="true"></a><span class="cf">if</span> <span class="st">&quot;description&quot;</span> <span class="kw">in</span> metadata:</span>
-<span id="cb600-7"><a href="#cb600-7" aria-hidden="true"></a>    metadata[<span class="st">&quot;description&quot;</span>] <span class="op">+=</span> <span class="st">&quot; [migrated from domain1]&quot;</span></span>
-<span id="cb600-8"><a href="#cb600-8" aria-hidden="true"></a><span class="cf">else</span>:</span>
-<span id="cb600-9"><a href="#cb600-9" aria-hidden="true"></a>    metadata[<span class="st">&quot;description&quot;</span>] <span class="op">=</span> <span class="st">&quot;[migrated from domain1]&quot;</span></span>
-<span id="cb600-10"><a href="#cb600-10" aria-hidden="true"></a><span class="co"># Modify owner</span></span>
-<span id="cb600-11"><a href="#cb600-11" aria-hidden="true"></a><span class="cf">if</span> <span class="st">&quot;owner&quot;</span> <span class="kw">in</span> metadata:</span>
-<span id="cb600-12"><a href="#cb600-12" aria-hidden="true"></a>    metadata[<span class="st">&quot;owner&quot;</span>] <span class="op">=</span> metadata[<span class="st">&quot;owner&quot;</span>].replace(<span class="st">&quot;domain1.com&quot;</span>, <span class="st">&quot;domain2.com&quot;</span>)</span>
-<span id="cb600-13"><a href="#cb600-13" aria-hidden="true"></a>o <span class="op">=</span> { <span class="st">&quot;Metadata&quot;</span>: metadata }</span>
-<span id="cb600-14"><a href="#cb600-14" aria-hidden="true"></a>json.dump(o, sys.stdout, indent<span class="op">=</span><span class="st">&quot;</span><span class="ch">\t</span><span class="st">&quot;</span>)</span></code></pre></div>
-<p>You can find this example (slightly expanded) in the rclone source code at <a href="https://github.com/rclone/rclone/blob/master/bin/test_metadata_mapper.py">bin/test_metadata_mapper.py</a>.</p>
-<p>If you want to see the input to the metadata mapper and the output returned from it in the log you can use <code>-vv --dump mapper</code>.</p>
+<p>An example python program might look something like this to implement
+the above transformations.</p>
+<div class="sourceCode" id="cb600"><pre
+class="sourceCode python"><code class="sourceCode python"><span id="cb600-1"><a href="#cb600-1" aria-hidden="true" tabindex="-1"></a><span class="im">import</span> sys, json</span>
+<span id="cb600-2"><a href="#cb600-2" aria-hidden="true" tabindex="-1"></a></span>
+<span id="cb600-3"><a href="#cb600-3" aria-hidden="true" tabindex="-1"></a>i <span class="op">=</span> json.load(sys.stdin)</span>
+<span id="cb600-4"><a href="#cb600-4" aria-hidden="true" tabindex="-1"></a>metadata <span class="op">=</span> i[<span class="st">&quot;Metadata&quot;</span>]</span>
+<span id="cb600-5"><a href="#cb600-5" aria-hidden="true" tabindex="-1"></a><span class="co"># Add tag to description</span></span>
+<span id="cb600-6"><a href="#cb600-6" aria-hidden="true" tabindex="-1"></a><span class="cf">if</span> <span class="st">&quot;description&quot;</span> <span class="kw">in</span> metadata:</span>
+<span id="cb600-7"><a href="#cb600-7" aria-hidden="true" tabindex="-1"></a>    metadata[<span class="st">&quot;description&quot;</span>] <span class="op">+=</span> <span class="st">&quot; [migrated from domain1]&quot;</span></span>
+<span id="cb600-8"><a href="#cb600-8" aria-hidden="true" tabindex="-1"></a><span class="cf">else</span>:</span>
+<span id="cb600-9"><a href="#cb600-9" aria-hidden="true" tabindex="-1"></a>    metadata[<span class="st">&quot;description&quot;</span>] <span class="op">=</span> <span class="st">&quot;[migrated from domain1]&quot;</span></span>
+<span id="cb600-10"><a href="#cb600-10" aria-hidden="true" tabindex="-1"></a><span class="co"># Modify owner</span></span>
+<span id="cb600-11"><a href="#cb600-11" aria-hidden="true" tabindex="-1"></a><span class="cf">if</span> <span class="st">&quot;owner&quot;</span> <span class="kw">in</span> metadata:</span>
+<span id="cb600-12"><a href="#cb600-12" aria-hidden="true" tabindex="-1"></a>    metadata[<span class="st">&quot;owner&quot;</span>] <span class="op">=</span> metadata[<span class="st">&quot;owner&quot;</span>].replace(<span class="st">&quot;domain1.com&quot;</span>, <span class="st">&quot;domain2.com&quot;</span>)</span>
+<span id="cb600-13"><a href="#cb600-13" aria-hidden="true" tabindex="-1"></a>o <span class="op">=</span> { <span class="st">&quot;Metadata&quot;</span>: metadata }</span>
+<span id="cb600-14"><a href="#cb600-14" aria-hidden="true" tabindex="-1"></a>json.dump(o, sys.stdout, indent<span class="op">=</span><span class="st">&quot;</span><span class="ch">\t</span><span class="st">&quot;</span>)</span></code></pre></div>
+<p>You can find this example (slightly expanded) in the rclone source
+code at <a
+href="https://github.com/rclone/rclone/blob/master/bin/test_metadata_mapper.py">bin/test_metadata_mapper.py</a>.</p>
+<p>If you want to see the input to the metadata mapper and the output
+returned from it in the log you can use
+<code>-vv --dump mapper</code>.</p>
 <p>See the <a href="#metadata">metadata section</a> for more info.</p>
 <h3 id="metadata-set-keyvalue">--metadata-set key=value</h3>
-<p>Add metadata <code>key</code> = <code>value</code> when uploading. This can be repeated as many times as required. See the <a href="#metadata">metadata section</a> for more info.</p>
+<p>Add metadata <code>key</code> = <code>value</code> when uploading.
+This can be repeated as many times as required. See the <a
+href="#metadata">metadata section</a> for more info.</p>
 <h3 id="modify-windowtime">--modify-window=TIME</h3>
-<p>When checking whether a file has been modified, this is the maximum allowed time difference that a file can have and still be considered equivalent.</p>
-<p>The default is <code>1ns</code> unless this is overridden by a remote. For example OS X only stores modification times to the nearest second so if you are reading and writing to an OS X filing system this will be <code>1s</code> by default.</p>
-<p>This command line flag allows you to override that computed default.</p>
-<h3 id="multi-thread-write-buffer-sizesize">--multi-thread-write-buffer-size=SIZE</h3>
-<p>When transferring with multiple threads, rclone will buffer SIZE bytes in memory before writing to disk for each thread.</p>
-<p>This can improve performance if the underlying filesystem does not deal well with a lot of small writes in different positions of the file, so if you see transfers being limited by disk write speed, you might want to experiment with different values. Specially for magnetic drives and remote file systems a higher value can be useful.</p>
-<p>Nevertheless, the default of <code>128k</code> should be fine for almost all use cases, so before changing it ensure that network is not really your bottleneck.</p>
-<p>As a final hint, size is not the only factor: block size (or similar concept) can have an impact. In one case, we observed that exact multiples of 16k performed much better than other values.</p>
-<h3 id="multi-thread-chunk-sizesizesuffix">--multi-thread-chunk-size=SizeSuffix</h3>
-<p>Normally the chunk size for multi thread transfers is set by the backend. However some backends such as <code>local</code> and <code>smb</code> (which implement <code>OpenWriterAt</code> but not <code>OpenChunkWriter</code>) don't have a natural chunk size.</p>
+<p>When checking whether a file has been modified, this is the maximum
+allowed time difference that a file can have and still be considered
+equivalent.</p>
+<p>The default is <code>1ns</code> unless this is overridden by a
+remote. For example OS X only stores modification times to the nearest
+second so if you are reading and writing to an OS X filing system this
+will be <code>1s</code> by default.</p>
+<p>This command line flag allows you to override that computed
+default.</p>
+<h3
+id="multi-thread-write-buffer-sizesize">--multi-thread-write-buffer-size=SIZE</h3>
+<p>When transferring with multiple threads, rclone will buffer SIZE
+bytes in memory before writing to disk for each thread.</p>
+<p>This can improve performance if the underlying filesystem does not
+deal well with a lot of small writes in different positions of the file,
+so if you see transfers being limited by disk write speed, you might
+want to experiment with different values. Specially for magnetic drives
+and remote file systems a higher value can be useful.</p>
+<p>Nevertheless, the default of <code>128k</code> should be fine for
+almost all use cases, so before changing it ensure that network is not
+really your bottleneck.</p>
+<p>As a final hint, size is not the only factor: block size (or similar
+concept) can have an impact. In one case, we observed that exact
+multiples of 16k performed much better than other values.</p>
+<h3
+id="multi-thread-chunk-sizesizesuffix">--multi-thread-chunk-size=SizeSuffix</h3>
+<p>Normally the chunk size for multi thread transfers is set by the
+backend. However some backends such as <code>local</code> and
+<code>smb</code> (which implement <code>OpenWriterAt</code> but not
+<code>OpenChunkWriter</code>) don't have a natural chunk size.</p>
 <p>In this case the value of this option is used (default 64Mi).</p>
 <h3 id="multi-thread-cutoff">--multi-thread-cutoff=SIZE</h3>
-<p>When transferring files above SIZE to capable backends, rclone will use multiple threads to transfer the file (default 256M).</p>
-<p>Capable backends are marked in the <a href="https://rclone.org/overview/#optional-features">overview</a> as <code>MultithreadUpload</code>. (They need to implement either the <code>OpenWriterAt</code> or <code>OpenChunkWriter</code> internal interfaces). These include include, <code>local</code>, <code>s3</code>, <code>azureblob</code>, <code>b2</code>, <code>oracleobjectstorage</code> and <code>smb</code> at the time of writing.</p>
-<p>On the local disk, rclone preallocates the file (using <code>fallocate(FALLOC_FL_KEEP_SIZE)</code> on unix or <code>NTSetInformationFile</code> on Windows both of which takes no time) then each thread writes directly into the file at the correct place. This means that rclone won't create fragmented or sparse files and there won't be any assembly time at the end of the transfer.</p>
-<p>The number of threads used to transfer is controlled by <code>--multi-thread-streams</code>.</p>
+<p>When transferring files above SIZE to capable backends, rclone will
+use multiple threads to transfer the file (default 256M).</p>
+<p>Capable backends are marked in the <a
+href="https://rclone.org/overview/#optional-features">overview</a> as
+<code>MultithreadUpload</code>. (They need to implement either the
+<code>OpenWriterAt</code> or <code>OpenChunkWriter</code> internal
+interfaces). These include include, <code>local</code>, <code>s3</code>,
+<code>azureblob</code>, <code>b2</code>,
+<code>oracleobjectstorage</code> and <code>smb</code> at the time of
+writing.</p>
+<p>On the local disk, rclone preallocates the file (using
+<code>fallocate(FALLOC_FL_KEEP_SIZE)</code> on unix or
+<code>NTSetInformationFile</code> on Windows both of which takes no
+time) then each thread writes directly into the file at the correct
+place. This means that rclone won't create fragmented or sparse files
+and there won't be any assembly time at the end of the transfer.</p>
+<p>The number of threads used to transfer is controlled by
+<code>--multi-thread-streams</code>.</p>
 <p>Use <code>-vv</code> if you wish to see info about the threads.</p>
-<p>This will work with the <code>sync</code>/<code>copy</code>/<code>move</code> commands and friends <code>copyto</code>/<code>moveto</code>. Multi thread transfers will be used with <code>rclone mount</code> and <code>rclone serve</code> if <code>--vfs-cache-mode</code> is set to <code>writes</code> or above.</p>
-<p><strong>NB</strong> that this <strong>only</strong> works with supported backends as the destination but will work with any backend as the source.</p>
-<p><strong>NB</strong> that multi-thread copies are disabled for local to local copies as they are faster without unless <code>--multi-thread-streams</code> is set explicitly.</p>
-<p><strong>NB</strong> on Windows using multi-thread transfers to the local disk will cause the resulting files to be <a href="https://en.wikipedia.org/wiki/Sparse_file">sparse</a>. Use <code>--local-no-sparse</code> to disable sparse files (which may cause long delays at the start of transfers) or disable multi-thread transfers with <code>--multi-thread-streams 0</code></p>
+<p>This will work with the
+<code>sync</code>/<code>copy</code>/<code>move</code> commands and
+friends <code>copyto</code>/<code>moveto</code>. Multi thread transfers
+will be used with <code>rclone mount</code> and
+<code>rclone serve</code> if <code>--vfs-cache-mode</code> is set to
+<code>writes</code> or above.</p>
+<p><strong>NB</strong> that this <strong>only</strong> works with
+supported backends as the destination but will work with any backend as
+the source.</p>
+<p><strong>NB</strong> that multi-thread copies are disabled for local
+to local copies as they are faster without unless
+<code>--multi-thread-streams</code> is set explicitly.</p>
+<p><strong>NB</strong> on Windows using multi-thread transfers to the
+local disk will cause the resulting files to be <a
+href="https://en.wikipedia.org/wiki/Sparse_file">sparse</a>. Use
+<code>--local-no-sparse</code> to disable sparse files (which may cause
+long delays at the start of transfers) or disable multi-thread transfers
+with <code>--multi-thread-streams 0</code></p>
 <h3 id="multi-thread-streamsn">--multi-thread-streams=N</h3>
-<p>When using multi thread transfers (see above <code>--multi-thread-cutoff</code>) this sets the number of streams to use. Set to <code>0</code> to disable multi thread transfers (Default 4).</p>
-<p>If the backend has a <code>--backend-upload-concurrency</code> setting (eg <code>--s3-upload-concurrency</code>) then this setting will be used as the number of transfers instead if it is larger than the value of <code>--multi-thread-streams</code> or <code>--multi-thread-streams</code> isn't set.</p>
+<p>When using multi thread transfers (see above
+<code>--multi-thread-cutoff</code>) this sets the number of streams to
+use. Set to <code>0</code> to disable multi thread transfers (Default
+4).</p>
+<p>If the backend has a <code>--backend-upload-concurrency</code>
+setting (eg <code>--s3-upload-concurrency</code>) then this setting will
+be used as the number of transfers instead if it is larger than the
+value of <code>--multi-thread-streams</code> or
+<code>--multi-thread-streams</code> isn't set.</p>
 <h3 id="no-check-dest">--no-check-dest</h3>
-<p>The <code>--no-check-dest</code> can be used with <code>move</code> or <code>copy</code> and it causes rclone not to check the destination at all when copying files.</p>
+<p>The <code>--no-check-dest</code> can be used with <code>move</code>
+or <code>copy</code> and it causes rclone not to check the destination
+at all when copying files.</p>
 <p>This means that:</p>
 <ul>
 <li>the destination is not listed minimising the API calls</li>
 <li>files are always transferred</li>
-<li>this can cause duplicates on remotes which allow it (e.g. Google Drive)</li>
-<li><code>--retries 1</code> is recommended otherwise you'll transfer everything again on a retry</li>
+<li>this can cause duplicates on remotes which allow it (e.g. Google
+Drive)</li>
+<li><code>--retries 1</code> is recommended otherwise you'll transfer
+everything again on a retry</li>
 </ul>
-<p>This flag is useful to minimise the transactions if you know that none of the files are on the destination.</p>
+<p>This flag is useful to minimise the transactions if you know that
+none of the files are on the destination.</p>
 <p>This is a specialized flag which should be ignored by most users!</p>
 <h3 id="no-gzip-encoding">--no-gzip-encoding</h3>
-<p>Don't set <code>Accept-Encoding: gzip</code>. This means that rclone won't ask the server for compressed files automatically. Useful if you've set the server to return files with <code>Content-Encoding: gzip</code> but you uploaded compressed files.</p>
-<p>There is no need to set this in normal operation, and doing so will decrease the network transfer efficiency of rclone.</p>
+<p>Don't set <code>Accept-Encoding: gzip</code>. This means that rclone
+won't ask the server for compressed files automatically. Useful if
+you've set the server to return files with
+<code>Content-Encoding: gzip</code> but you uploaded compressed
+files.</p>
+<p>There is no need to set this in normal operation, and doing so will
+decrease the network transfer efficiency of rclone.</p>
 <h3 id="no-traverse">--no-traverse</h3>
-<p>The <code>--no-traverse</code> flag controls whether the destination file system is traversed when using the <code>copy</code> or <code>move</code> commands. <code>--no-traverse</code> is not compatible with <code>sync</code> and will be ignored if you supply it with <code>sync</code>.</p>
-<p>If you are only copying a small number of files (or are filtering most of the files) and/or have a large number of files on the destination then <code>--no-traverse</code> will stop rclone listing the destination and save time.</p>
-<p>However, if you are copying a large number of files, especially if you are doing a copy where lots of the files under consideration haven't changed and won't need copying then you shouldn't use <code>--no-traverse</code>.</p>
-<p>See <a href="https://rclone.org/commands/rclone_copy/">rclone copy</a> for an example of how to use it.</p>
+<p>The <code>--no-traverse</code> flag controls whether the destination
+file system is traversed when using the <code>copy</code> or
+<code>move</code> commands. <code>--no-traverse</code> is not compatible
+with <code>sync</code> and will be ignored if you supply it with
+<code>sync</code>.</p>
+<p>If you are only copying a small number of files (or are filtering
+most of the files) and/or have a large number of files on the
+destination then <code>--no-traverse</code> will stop rclone listing the
+destination and save time.</p>
+<p>However, if you are copying a large number of files, especially if
+you are doing a copy where lots of the files under consideration haven't
+changed and won't need copying then you shouldn't use
+<code>--no-traverse</code>.</p>
+<p>See <a href="https://rclone.org/commands/rclone_copy/">rclone
+copy</a> for an example of how to use it.</p>
 <h3 id="no-unicode-normalization">--no-unicode-normalization</h3>
-<p>Don't normalize unicode characters in filenames during the sync routine.</p>
-<p>Sometimes, an operating system will store filenames containing unicode parts in their decomposed form (particularly macOS). Some cloud storage systems will then recompose the unicode, resulting in duplicate files if the data is ever copied back to a local filesystem.</p>
-<p>Using this flag will disable that functionality, treating each unicode character as unique. For example, by default é and é will be normalized into the same character. With <code>--no-unicode-normalization</code> they will be treated as unique characters.</p>
+<p>Don't normalize unicode characters in filenames during the sync
+routine.</p>
+<p>Sometimes, an operating system will store filenames containing
+unicode parts in their decomposed form (particularly macOS). Some cloud
+storage systems will then recompose the unicode, resulting in duplicate
+files if the data is ever copied back to a local filesystem.</p>
+<p>Using this flag will disable that functionality, treating each
+unicode character as unique. For example, by default é and é will be
+normalized into the same character. With
+<code>--no-unicode-normalization</code> they will be treated as unique
+characters.</p>
 <h3 id="no-update-modtime">--no-update-modtime</h3>
-<p>When using this flag, rclone won't update modification times of remote files if they are incorrect as it would normally.</p>
-<p>This can be used if the remote is being synced with another tool also (e.g. the Google Drive client).</p>
+<p>When using this flag, rclone won't update modification times of
+remote files if they are incorrect as it would normally.</p>
+<p>This can be used if the remote is being synced with another tool also
+(e.g. the Google Drive client).</p>
 <h3 id="no-update-dir-modtime">--no-update-dir-modtime</h3>
-<p>When using this flag, rclone won't update modification times of remote directories if they are incorrect as it would normally.</p>
+<p>When using this flag, rclone won't update modification times of
+remote directories if they are incorrect as it would normally.</p>
 <h3 id="order-by-string">--order-by string</h3>
-<p>The <code>--order-by</code> flag controls the order in which files in the backlog are processed in <code>rclone sync</code>, <code>rclone copy</code> and <code>rclone move</code>.</p>
-<p>The order by string is constructed like this. The first part describes what aspect is being measured:</p>
+<p>The <code>--order-by</code> flag controls the order in which files in
+the backlog are processed in <code>rclone sync</code>,
+<code>rclone copy</code> and <code>rclone move</code>.</p>
+<p>The order by string is constructed like this. The first part
+describes what aspect is being measured:</p>
 <ul>
 <li><code>size</code> - order by the size of the files</li>
 <li><code>name</code> - order by the full path of the files</li>
-<li><code>modtime</code> - order by the modification date of the files</li>
+<li><code>modtime</code> - order by the modification date of the
+files</li>
 </ul>
 <p>This can have a modifier appended with a comma:</p>
 <ul>
-<li><code>ascending</code> or <code>asc</code> - order so that the smallest (or oldest) is processed first</li>
-<li><code>descending</code> or <code>desc</code> - order so that the largest (or newest) is processed first</li>
-<li><code>mixed</code> - order so that the smallest is processed first for some threads and the largest for others</li>
+<li><code>ascending</code> or <code>asc</code> - order so that the
+smallest (or oldest) is processed first</li>
+<li><code>descending</code> or <code>desc</code> - order so that the
+largest (or newest) is processed first</li>
+<li><code>mixed</code> - order so that the smallest is processed first
+for some threads and the largest for others</li>
 </ul>
-<p>If the modifier is <code>mixed</code> then it can have an optional percentage (which defaults to <code>50</code>), e.g. <code>size,mixed,25</code> which means that 25% of the threads should be taking the smallest items and 75% the largest. The threads which take the smallest first will always take the smallest first and likewise the largest first threads. The <code>mixed</code> mode can be useful to minimise the transfer time when you are transferring a mixture of large and small files - the large files are guaranteed upload threads and bandwidth and the small files will be processed continuously.</p>
-<p>If no modifier is supplied then the order is <code>ascending</code>.</p>
+<p>If the modifier is <code>mixed</code> then it can have an optional
+percentage (which defaults to <code>50</code>), e.g.
+<code>size,mixed,25</code> which means that 25% of the threads should be
+taking the smallest items and 75% the largest. The threads which take
+the smallest first will always take the smallest first and likewise the
+largest first threads. The <code>mixed</code> mode can be useful to
+minimise the transfer time when you are transferring a mixture of large
+and small files - the large files are guaranteed upload threads and
+bandwidth and the small files will be processed continuously.</p>
+<p>If no modifier is supplied then the order is
+<code>ascending</code>.</p>
 <p>For example</p>
 <ul>
-<li><code>--order-by size,desc</code> - send the largest files first</li>
-<li><code>--order-by modtime,ascending</code> - send the oldest files first</li>
-<li><code>--order-by name</code> - send the files with alphabetically by path first</li>
+<li><code>--order-by size,desc</code> - send the largest files
+first</li>
+<li><code>--order-by modtime,ascending</code> - send the oldest files
+first</li>
+<li><code>--order-by name</code> - send the files with alphabetically by
+path first</li>
 </ul>
-<p>If the <code>--order-by</code> flag is not supplied or it is supplied with an empty string then the default ordering will be used which is as scanned. With <code>--checkers 1</code> this is mostly alphabetical, however with the default <code>--checkers 8</code> it is somewhat random.</p>
+<p>If the <code>--order-by</code> flag is not supplied or it is supplied
+with an empty string then the default ordering will be used which is as
+scanned. With <code>--checkers 1</code> this is mostly alphabetical,
+however with the default <code>--checkers 8</code> it is somewhat
+random.</p>
 <h4 id="limitations-3">Limitations</h4>
-<p>The <code>--order-by</code> flag does not do a separate pass over the data. This means that it may transfer some files out of the order specified if</p>
+<p>The <code>--order-by</code> flag does not do a separate pass over the
+data. This means that it may transfer some files out of the order
+specified if</p>
 <ul>
-<li>there are no files in the backlog or the source has not been fully scanned yet</li>
-<li>there are more than <a href="#max-backlog-n">--max-backlog</a> files in the backlog</li>
+<li>there are no files in the backlog or the source has not been fully
+scanned yet</li>
+<li>there are more than <a href="#max-backlog-n">--max-backlog</a> files
+in the backlog</li>
 </ul>
-<p>Rclone will do its best to transfer the best file it has so in practice this should not cause a problem. Think of <code>--order-by</code> as being more of a best efforts flag rather than a perfect ordering.</p>
-<p>If you want perfect ordering then you will need to specify <a href="#check-first">--check-first</a> which will find all the files which need transferring first before transferring any.</p>
+<p>Rclone will do its best to transfer the best file it has so in
+practice this should not cause a problem. Think of
+<code>--order-by</code> as being more of a best efforts flag rather than
+a perfect ordering.</p>
+<p>If you want perfect ordering then you will need to specify <a
+href="#check-first">--check-first</a> which will find all the files
+which need transferring first before transferring any.</p>
 <h3 id="partial-suffix">--partial-suffix</h3>
-<p>When <a href="#inplace">--inplace</a> is not used, it causes rclone to use the <code>--partial-suffix</code> as suffix for temporary files.</p>
+<p>When <a href="#inplace">--inplace</a> is not used, it causes rclone
+to use the <code>--partial-suffix</code> as suffix for temporary
+files.</p>
 <p>Suffix length limit is 16 characters.</p>
 <p>The default is <code>.partial</code>.</p>
 <h3 id="password-command">--password-command SpaceSepList</h3>
-<p>This flag supplies a program which should supply the config password when run. This is an alternative to rclone prompting for the password or setting the <code>RCLONE_CONFIG_PASS</code> variable. It is also used when setting the config password for the first time.</p>
-<p>The argument to this should be a command with a space separated list of arguments. If one of the arguments has a space in then enclose it in <code>"</code>, if you want a literal <code>"</code> in an argument then enclose the argument in <code>"</code> and double the <code>"</code>. See <a href="https://godoc.org/encoding/csv">CSV encoding</a> for more info.</p>
+<p>This flag supplies a program which should supply the config password
+when run. This is an alternative to rclone prompting for the password or
+setting the <code>RCLONE_CONFIG_PASS</code> variable. It is also used
+when setting the config password for the first time.</p>
+<p>The argument to this should be a command with a space separated list
+of arguments. If one of the arguments has a space in then enclose it in
+<code>"</code>, if you want a literal <code>"</code> in an argument then
+enclose the argument in <code>"</code> and double the <code>"</code>.
+See <a href="https://godoc.org/encoding/csv">CSV encoding</a> for more
+info.</p>
 <p>Eg</p>
 <pre><code>--password-command &quot;echo hello&quot;
 --password-command &#39;echo &quot;hello with space&quot;&#39;
 --password-command &#39;echo &quot;hello with &quot;&quot;quotes&quot;&quot; and space&quot;&#39;</code></pre>
-<p>Note that when changing the configuration password the environment variable <code>RCLONE_PASSWORD_CHANGE=1</code> will be set. This can be used to distinguish initial decryption of the config file from the new password.</p>
-<p>See the <a href="#configuration-encryption">Configuration Encryption</a> for more info.</p>
-<p>See a <a href="https://github.com/rclone/rclone/wiki/Windows-Powershell-use-rclone-password-command-for-Config-file-password">Windows PowerShell example on the Wiki</a>.</p>
+<p>Note that when changing the configuration password the environment
+variable <code>RCLONE_PASSWORD_CHANGE=1</code> will be set. This can be
+used to distinguish initial decryption of the config file from the new
+password.</p>
+<p>See the <a href="#configuration-encryption">Configuration
+Encryption</a> for more info.</p>
+<p>See a <a
+href="https://github.com/rclone/rclone/wiki/Windows-Powershell-use-rclone-password-command-for-Config-file-password">Windows
+PowerShell example on the Wiki</a>.</p>
 <h3 id="p---progress">-P, --progress</h3>
-<p>This flag makes rclone update the stats in a static block in the terminal providing a realtime overview of the transfer.</p>
-<p>Any log messages will scroll above the static block. Log messages will push the static block down to the bottom of the terminal where it will stay.</p>
-<p>Normally this is updated every 500mS but this period can be overridden with the <code>--stats</code> flag.</p>
-<p>This can be used with the <code>--stats-one-line</code> flag for a simpler display.</p>
-<p>To change the display length of filenames (for different terminal widths), see the <code>--stats-file-name-length</code> option. The default output is formatted for 80 character wide terminals.</p>
-<p>Note: On Windows until <a href="https://github.com/Azure/go-ansiterm/issues/26">this bug</a> is fixed all non-ASCII characters will be replaced with <code>.</code> when <code>--progress</code> is in use.</p>
+<p>This flag makes rclone update the stats in a static block in the
+terminal providing a realtime overview of the transfer.</p>
+<p>Any log messages will scroll above the static block. Log messages
+will push the static block down to the bottom of the terminal where it
+will stay.</p>
+<p>Normally this is updated every 500mS but this period can be
+overridden with the <code>--stats</code> flag.</p>
+<p>This can be used with the <code>--stats-one-line</code> flag for a
+simpler display.</p>
+<p>To change the display length of filenames (for different terminal
+widths), see the <code>--stats-file-name-length</code> option. The
+default output is formatted for 80 character wide terminals.</p>
+<p>Note: On Windows until <a
+href="https://github.com/Azure/go-ansiterm/issues/26">this bug</a> is
+fixed all non-ASCII characters will be replaced with <code>.</code> when
+<code>--progress</code> is in use.</p>
 <h3 id="progress-terminal-title">--progress-terminal-title</h3>
-<p>This flag, when used with <code>-P/--progress</code>, will print the string <code>ETA: %s</code> to the terminal title.</p>
+<p>This flag, when used with <code>-P/--progress</code>, will print the
+string <code>ETA: %s</code> to the terminal title.</p>
 <h3 id="q---quiet">-q, --quiet</h3>
 <p>This flag will limit rclone's output to error messages only.</p>
 <h3 id="refresh-times">--refresh-times</h3>
-<p>The <code>--refresh-times</code> flag can be used to update modification times of existing files when they are out of sync on backends which don't support hashes.</p>
-<p>This is useful if you uploaded files with the incorrect timestamps and you now wish to correct them.</p>
-<p>This flag is <strong>only</strong> useful for destinations which don't support hashes (e.g. <code>crypt</code>).</p>
-<p>This can be used any of the sync commands <code>sync</code>, <code>copy</code> or <code>move</code>.</p>
-<p>To use this flag you will need to be doing a modification time sync (so not using <code>--size-only</code> or <code>--checksum</code>). The flag will have no effect when using <code>--size-only</code> or <code>--checksum</code>.</p>
-<p>If this flag is used when rclone comes to upload a file it will check to see if there is an existing file on the destination. If this file matches the source with size (and checksum if available) but has a differing timestamp then instead of re-uploading it, rclone will update the timestamp on the destination file. If the checksum does not match rclone will upload the new file. If the checksum is absent (e.g. on a <code>crypt</code> backend) then rclone will update the timestamp.</p>
-<p>Note that some remotes can't set the modification time without re-uploading the file so this flag is less useful on them.</p>
-<p>Normally if you are doing a modification time sync rclone will update modification times without <code>--refresh-times</code> provided that the remote supports checksums <strong>and</strong> the checksums match on the file. However if the checksums are absent then rclone will upload the file rather than setting the timestamp as this is the safe behaviour.</p>
+<p>The <code>--refresh-times</code> flag can be used to update
+modification times of existing files when they are out of sync on
+backends which don't support hashes.</p>
+<p>This is useful if you uploaded files with the incorrect timestamps
+and you now wish to correct them.</p>
+<p>This flag is <strong>only</strong> useful for destinations which
+don't support hashes (e.g. <code>crypt</code>).</p>
+<p>This can be used any of the sync commands <code>sync</code>,
+<code>copy</code> or <code>move</code>.</p>
+<p>To use this flag you will need to be doing a modification time sync
+(so not using <code>--size-only</code> or <code>--checksum</code>). The
+flag will have no effect when using <code>--size-only</code> or
+<code>--checksum</code>.</p>
+<p>If this flag is used when rclone comes to upload a file it will check
+to see if there is an existing file on the destination. If this file
+matches the source with size (and checksum if available) but has a
+differing timestamp then instead of re-uploading it, rclone will update
+the timestamp on the destination file. If the checksum does not match
+rclone will upload the new file. If the checksum is absent (e.g. on a
+<code>crypt</code> backend) then rclone will update the timestamp.</p>
+<p>Note that some remotes can't set the modification time without
+re-uploading the file so this flag is less useful on them.</p>
+<p>Normally if you are doing a modification time sync rclone will update
+modification times without <code>--refresh-times</code> provided that
+the remote supports checksums <strong>and</strong> the checksums match
+on the file. However if the checksums are absent then rclone will upload
+the file rather than setting the timestamp as this is the safe
+behaviour.</p>
 <h3 id="retries-int">--retries int</h3>
-<p>Retry the entire sync if it fails this many times it fails (default 3).</p>
-<p>Some remotes can be unreliable and a few retries help pick up the files which didn't get transferred because of errors.</p>
+<p>Retry the entire sync if it fails this many times it fails (default
+3).</p>
+<p>Some remotes can be unreliable and a few retries help pick up the
+files which didn't get transferred because of errors.</p>
 <p>Disable retries with <code>--retries 1</code>.</p>
 <h3 id="retries-sleeptime">--retries-sleep=TIME</h3>
-<p>This sets the interval between each retry specified by <code>--retries</code></p>
+<p>This sets the interval between each retry specified by
+<code>--retries</code></p>
 <p>The default is <code>0</code>. Use <code>0</code> to disable.</p>
 <h3 id="server-side-across-configs">--server-side-across-configs</h3>
-<p>Allow server-side operations (e.g. copy or move) to work across different configurations.</p>
-<p>This can be useful if you wish to do a server-side copy or move between two remotes which use the same backend but are configured differently.</p>
-<p>Note that this isn't enabled by default because it isn't easy for rclone to tell if it will work between any two configurations.</p>
+<p>Allow server-side operations (e.g. copy or move) to work across
+different configurations.</p>
+<p>This can be useful if you wish to do a server-side copy or move
+between two remotes which use the same backend but are configured
+differently.</p>
+<p>Note that this isn't enabled by default because it isn't easy for
+rclone to tell if it will work between any two configurations.</p>
 <h3 id="size-only">--size-only</h3>
-<p>Normally rclone will look at modification time and size of files to see if they are equal. If you set this flag then rclone will check only the size.</p>
-<p>This can be useful transferring files from Dropbox which have been modified by the desktop sync client which doesn't set checksums of modification times in the same way as rclone.</p>
+<p>Normally rclone will look at modification time and size of files to
+see if they are equal. If you set this flag then rclone will check only
+the size.</p>
+<p>This can be useful transferring files from Dropbox which have been
+modified by the desktop sync client which doesn't set checksums of
+modification times in the same way as rclone.</p>
 <h3 id="statstime">--stats=TIME</h3>
-<p>Commands which transfer data (<code>sync</code>, <code>copy</code>, <code>copyto</code>, <code>move</code>, <code>moveto</code>) will print data transfer stats at regular intervals to show their progress.</p>
+<p>Commands which transfer data (<code>sync</code>, <code>copy</code>,
+<code>copyto</code>, <code>move</code>, <code>moveto</code>) will print
+data transfer stats at regular intervals to show their progress.</p>
 <p>This sets the interval.</p>
 <p>The default is <code>1m</code>. Use <code>0</code> to disable.</p>
-<p>If you set the stats interval then all commands can show stats. This can be useful when running other commands, <code>check</code> or <code>mount</code> for example.</p>
-<p>Stats are logged at <code>INFO</code> level by default which means they won't show at default log level <code>NOTICE</code>. Use <code>--stats-log-level NOTICE</code> or <code>-v</code> to make them show. See the <a href="#logging">Logging section</a> for more info on log levels.</p>
-<p>Note that on macOS you can send a SIGINFO (which is normally ctrl-T in the terminal) to make the stats print immediately.</p>
-<h3 id="stats-file-name-length-integer">--stats-file-name-length integer</h3>
-<p>By default, the <code>--stats</code> output will truncate file names and paths longer than 40 characters. This is equivalent to providing <code>--stats-file-name-length 40</code>. Use <code>--stats-file-name-length 0</code> to disable any truncation of file names printed by stats.</p>
+<p>If you set the stats interval then all commands can show stats. This
+can be useful when running other commands, <code>check</code> or
+<code>mount</code> for example.</p>
+<p>Stats are logged at <code>INFO</code> level by default which means
+they won't show at default log level <code>NOTICE</code>. Use
+<code>--stats-log-level NOTICE</code> or <code>-v</code> to make them
+show. See the <a href="#logging">Logging section</a> for more info on
+log levels.</p>
+<p>Note that on macOS you can send a SIGINFO (which is normally ctrl-T
+in the terminal) to make the stats print immediately.</p>
+<h3 id="stats-file-name-length-integer">--stats-file-name-length
+integer</h3>
+<p>By default, the <code>--stats</code> output will truncate file names
+and paths longer than 40 characters. This is equivalent to providing
+<code>--stats-file-name-length 40</code>. Use
+<code>--stats-file-name-length 0</code> to disable any truncation of
+file names printed by stats.</p>
 <h3 id="stats-log-level-string">--stats-log-level string</h3>
-<p>Log level to show <code>--stats</code> output at. This can be <code>DEBUG</code>, <code>INFO</code>, <code>NOTICE</code>, or <code>ERROR</code>. The default is <code>INFO</code>. This means at the default level of logging which is <code>NOTICE</code> the stats won't show - if you want them to then use <code>--stats-log-level NOTICE</code>. See the <a href="#logging">Logging section</a> for more info on log levels.</p>
+<p>Log level to show <code>--stats</code> output at. This can be
+<code>DEBUG</code>, <code>INFO</code>, <code>NOTICE</code>, or
+<code>ERROR</code>. The default is <code>INFO</code>. This means at the
+default level of logging which is <code>NOTICE</code> the stats won't
+show - if you want them to then use
+<code>--stats-log-level NOTICE</code>. See the <a
+href="#logging">Logging section</a> for more info on log levels.</p>
 <h3 id="stats-one-line">--stats-one-line</h3>
-<p>When this is specified, rclone condenses the stats into a single line showing the most important stats only.</p>
+<p>When this is specified, rclone condenses the stats into a single line
+showing the most important stats only.</p>
 <h3 id="stats-one-line-date">--stats-one-line-date</h3>
-<p>When this is specified, rclone enables the single-line stats and prepends the display with a date string. The default is <code>2006/01/02 15:04:05 -</code></p>
+<p>When this is specified, rclone enables the single-line stats and
+prepends the display with a date string. The default is
+<code>2006/01/02 15:04:05 -</code></p>
 <h3 id="stats-one-line-date-format">--stats-one-line-date-format</h3>
-<p>When this is specified, rclone enables the single-line stats and prepends the display with a user-supplied date string. The date string MUST be enclosed in quotes. Follow <a href="https://golang.org/pkg/time/#Time.Format">golang specs</a> for date formatting syntax.</p>
+<p>When this is specified, rclone enables the single-line stats and
+prepends the display with a user-supplied date string. The date string
+MUST be enclosed in quotes. Follow <a
+href="https://golang.org/pkg/time/#Time.Format">golang specs</a> for
+date formatting syntax.</p>
 <h3 id="stats-unitbitsbytes">--stats-unit=bits|bytes</h3>
-<p>By default, data transfer rates will be printed in bytes per second.</p>
-<p>This option allows the data rate to be printed in bits per second.</p>
+<p>By default, data transfer rates will be printed in bytes per
+second.</p>
+<p>This option allows the data rate to be printed in bits per
+second.</p>
 <p>Data transfer volume will still be reported in bytes.</p>
-<p>The rate is reported as a binary unit, not SI unit. So 1 Mbit/s equals 1,048,576 bit/s and not 1,000,000 bit/s.</p>
+<p>The rate is reported as a binary unit, not SI unit. So 1 Mbit/s
+equals 1,048,576 bit/s and not 1,000,000 bit/s.</p>
 <p>The default is <code>bytes</code>.</p>
 <h3 id="suffixsuffix">--suffix=SUFFIX</h3>
-<p>When using <code>sync</code>, <code>copy</code> or <code>move</code> any files which would have been overwritten or deleted will have the suffix added to them. If there is a file with the same path (after the suffix has been added), then it will be overwritten.</p>
-<p>The remote in use must support server-side move or copy and you must use the same remote as the destination of the sync.</p>
-<p>This is for use with files to add the suffix in the current directory or with <code>--backup-dir</code>. See <code>--backup-dir</code> for more info.</p>
+<p>When using <code>sync</code>, <code>copy</code> or <code>move</code>
+any files which would have been overwritten or deleted will have the
+suffix added to them. If there is a file with the same path (after the
+suffix has been added), then it will be overwritten.</p>
+<p>The remote in use must support server-side move or copy and you must
+use the same remote as the destination of the sync.</p>
+<p>This is for use with files to add the suffix in the current directory
+or with <code>--backup-dir</code>. See <code>--backup-dir</code> for
+more info.</p>
 <p>For example</p>
 <pre><code>rclone copy --interactive /path/to/local/file remote:current --suffix .bak</code></pre>
-<p>will copy <code>/path/to/local</code> to <code>remote:current</code>, but for any files which would have been updated or deleted have .bak added.</p>
-<p>If using <code>rclone sync</code> with <code>--suffix</code> and without <code>--backup-dir</code> then it is recommended to put a filter rule in excluding the suffix otherwise the <code>sync</code> will delete the backup files.</p>
+<p>will copy <code>/path/to/local</code> to <code>remote:current</code>,
+but for any files which would have been updated or deleted have .bak
+added.</p>
+<p>If using <code>rclone sync</code> with <code>--suffix</code> and
+without <code>--backup-dir</code> then it is recommended to put a filter
+rule in excluding the suffix otherwise the <code>sync</code> will delete
+the backup files.</p>
 <pre><code>rclone sync --interactive /path/to/local/file remote:current --suffix .bak --exclude &quot;*.bak&quot;</code></pre>
 <h3 id="suffix-keep-extension">--suffix-keep-extension</h3>
-<p>When using <code>--suffix</code>, setting this causes rclone put the SUFFIX before the extension of the files that it backs up rather than after.</p>
-<p>So let's say we had <code>--suffix -2019-01-01</code>, without the flag <code>file.txt</code> would be backed up to <code>file.txt-2019-01-01</code> and with the flag it would be backed up to <code>file-2019-01-01.txt</code>. This can be helpful to make sure the suffixed files can still be opened.</p>
-<p>If a file has two (or more) extensions and the second (or subsequent) extension is recognised as a valid mime type, then the suffix will go before that extension. So <code>file.tar.gz</code> would be backed up to <code>file-2019-01-01.tar.gz</code> whereas <code>file.badextension.gz</code> would be backed up to <code>file.badextension-2019-01-01.gz</code>.</p>
+<p>When using <code>--suffix</code>, setting this causes rclone put the
+SUFFIX before the extension of the files that it backs up rather than
+after.</p>
+<p>So let's say we had <code>--suffix -2019-01-01</code>, without the
+flag <code>file.txt</code> would be backed up to
+<code>file.txt-2019-01-01</code> and with the flag it would be backed up
+to <code>file-2019-01-01.txt</code>. This can be helpful to make sure
+the suffixed files can still be opened.</p>
+<p>If a file has two (or more) extensions and the second (or subsequent)
+extension is recognised as a valid mime type, then the suffix will go
+before that extension. So <code>file.tar.gz</code> would be backed up to
+<code>file-2019-01-01.tar.gz</code> whereas
+<code>file.badextension.gz</code> would be backed up to
+<code>file.badextension-2019-01-01.gz</code>.</p>
 <h3 id="syslog">--syslog</h3>
-<p>On capable OSes (not Windows or Plan9) send all log output to syslog.</p>
-<p>This can be useful for running rclone in a script or <code>rclone mount</code>.</p>
+<p>On capable OSes (not Windows or Plan9) send all log output to
+syslog.</p>
+<p>This can be useful for running rclone in a script or
+<code>rclone mount</code>.</p>
 <h3 id="syslog-facility-string">--syslog-facility string</h3>
-<p>If using <code>--syslog</code> this sets the syslog facility (e.g. <code>KERN</code>, <code>USER</code>). See <code>man syslog</code> for a list of possible facilities. The default facility is <code>DAEMON</code>.</p>
+<p>If using <code>--syslog</code> this sets the syslog facility (e.g.
+<code>KERN</code>, <code>USER</code>). See <code>man syslog</code> for a
+list of possible facilities. The default facility is
+<code>DAEMON</code>.</p>
 <h3 id="temp-dirdir">--temp-dir=DIR</h3>
-<p>Specify the directory rclone will use for temporary files, to override the default. Make sure the directory exists and have accessible permissions.</p>
-<p>By default the operating system's temp directory will be used: - On Unix systems, <code>$TMPDIR</code> if non-empty, else <code>/tmp</code>. - On Windows, the first non-empty value from <code>%TMP%</code>, <code>%TEMP%</code>, <code>%USERPROFILE%</code>, or the Windows directory.</p>
-<p>When overriding the default with this option, the specified path will be set as value of environment variable <code>TMPDIR</code> on Unix systems and <code>TMP</code> and <code>TEMP</code> on Windows.</p>
-<p>You can use the <a href="https://rclone.org/commands/rclone_config_paths/">config paths</a> command to see the current value.</p>
+<p>Specify the directory rclone will use for temporary files, to
+override the default. Make sure the directory exists and have accessible
+permissions.</p>
+<p>By default the operating system's temp directory will be used: - On
+Unix systems, <code>$TMPDIR</code> if non-empty, else <code>/tmp</code>.
+- On Windows, the first non-empty value from <code>%TMP%</code>,
+<code>%TEMP%</code>, <code>%USERPROFILE%</code>, or the Windows
+directory.</p>
+<p>When overriding the default with this option, the specified path will
+be set as value of environment variable <code>TMPDIR</code> on Unix
+systems and <code>TMP</code> and <code>TEMP</code> on Windows.</p>
+<p>You can use the <a
+href="https://rclone.org/commands/rclone_config_paths/">config paths</a>
+command to see the current value.</p>
 <h3 id="tpslimit-float">--tpslimit float</h3>
-<p>Limit transactions per second to this number. Default is 0 which is used to mean unlimited transactions per second.</p>
-<p>A transaction is roughly defined as an API call; its exact meaning will depend on the backend. For HTTP based backends it is an HTTP PUT/GET/POST/etc and its response. For FTP/SFTP it is a round trip transaction over TCP.</p>
-<p>For example, to limit rclone to 10 transactions per second use <code>--tpslimit 10</code>, or to 1 transaction every 2 seconds use <code>--tpslimit 0.5</code>.</p>
-<p>Use this when the number of transactions per second from rclone is causing a problem with the cloud storage provider (e.g. getting you banned or rate limited).</p>
-<p>This can be very useful for <code>rclone mount</code> to control the behaviour of applications using it.</p>
-<p>This limit applies to all HTTP based backends and to the FTP and SFTP backends. It does not apply to the local backend or the Storj backend.</p>
+<p>Limit transactions per second to this number. Default is 0 which is
+used to mean unlimited transactions per second.</p>
+<p>A transaction is roughly defined as an API call; its exact meaning
+will depend on the backend. For HTTP based backends it is an HTTP
+PUT/GET/POST/etc and its response. For FTP/SFTP it is a round trip
+transaction over TCP.</p>
+<p>For example, to limit rclone to 10 transactions per second use
+<code>--tpslimit 10</code>, or to 1 transaction every 2 seconds use
+<code>--tpslimit 0.5</code>.</p>
+<p>Use this when the number of transactions per second from rclone is
+causing a problem with the cloud storage provider (e.g. getting you
+banned or rate limited).</p>
+<p>This can be very useful for <code>rclone mount</code> to control the
+behaviour of applications using it.</p>
+<p>This limit applies to all HTTP based backends and to the FTP and SFTP
+backends. It does not apply to the local backend or the Storj
+backend.</p>
 <p>See also <code>--tpslimit-burst</code>.</p>
 <h3 id="tpslimit-burst-int">--tpslimit-burst int</h3>
-<p>Max burst of transactions for <code>--tpslimit</code> (default <code>1</code>).</p>
-<p>Normally <code>--tpslimit</code> will do exactly the number of transaction per second specified. However if you supply <code>--tps-burst</code> then rclone can save up some transactions from when it was idle giving a burst of up to the parameter supplied.</p>
-<p>For example if you provide <code>--tpslimit-burst 10</code> then if rclone has been idle for more than 10*<code>--tpslimit</code> then it can do 10 transactions very quickly before they are limited again.</p>
-<p>This may be used to increase performance of <code>--tpslimit</code> without changing the long term average number of transactions per second.</p>
+<p>Max burst of transactions for <code>--tpslimit</code> (default
+<code>1</code>).</p>
+<p>Normally <code>--tpslimit</code> will do exactly the number of
+transaction per second specified. However if you supply
+<code>--tps-burst</code> then rclone can save up some transactions from
+when it was idle giving a burst of up to the parameter supplied.</p>
+<p>For example if you provide <code>--tpslimit-burst 10</code> then if
+rclone has been idle for more than 10*<code>--tpslimit</code> then it
+can do 10 transactions very quickly before they are limited again.</p>
+<p>This may be used to increase performance of <code>--tpslimit</code>
+without changing the long term average number of transactions per
+second.</p>
 <h3 id="track-renames">--track-renames</h3>
-<p>By default, rclone doesn't keep track of renamed files, so if you rename a file locally then sync it to a remote, rclone will delete the old file on the remote and upload a new copy.</p>
-<p>An rclone sync with <code>--track-renames</code> runs like a normal sync, but keeps track of objects which exist in the destination but not in the source (which would normally be deleted), and which objects exist in the source but not the destination (which would normally be transferred). These objects are then candidates for renaming.</p>
-<p>After the sync, rclone matches up the source only and destination only objects using the <code>--track-renames-strategy</code> specified and either renames the destination object or transfers the source and deletes the destination object. <code>--track-renames</code> is stateless like all of rclone's syncs.</p>
-<p>To use this flag the destination must support server-side copy or server-side move, and to use a hash based <code>--track-renames-strategy</code> (the default) the source and the destination must have a compatible hash.</p>
-<p>If the destination does not support server-side copy or move, rclone will fall back to the default behaviour and log an error level message to the console.</p>
-<p>Encrypted destinations are not currently supported by <code>--track-renames</code> if <code>--track-renames-strategy</code> includes <code>hash</code>.</p>
-<p>Note that <code>--track-renames</code> is incompatible with <code>--no-traverse</code> and that it uses extra memory to keep track of all the rename candidates.</p>
-<p>Note also that <code>--track-renames</code> is incompatible with <code>--delete-before</code> and will select <code>--delete-after</code> instead of <code>--delete-during</code>.</p>
-<h3 id="track-renames-strategy-hashmodtimeleafsize">--track-renames-strategy (hash,modtime,leaf,size)</h3>
-<p>This option changes the file matching criteria for <code>--track-renames</code>.</p>
-<p>The matching is controlled by a comma separated selection of these tokens:</p>
+<p>By default, rclone doesn't keep track of renamed files, so if you
+rename a file locally then sync it to a remote, rclone will delete the
+old file on the remote and upload a new copy.</p>
+<p>An rclone sync with <code>--track-renames</code> runs like a normal
+sync, but keeps track of objects which exist in the destination but not
+in the source (which would normally be deleted), and which objects exist
+in the source but not the destination (which would normally be
+transferred). These objects are then candidates for renaming.</p>
+<p>After the sync, rclone matches up the source only and destination
+only objects using the <code>--track-renames-strategy</code> specified
+and either renames the destination object or transfers the source and
+deletes the destination object. <code>--track-renames</code> is
+stateless like all of rclone's syncs.</p>
+<p>To use this flag the destination must support server-side copy or
+server-side move, and to use a hash based
+<code>--track-renames-strategy</code> (the default) the source and the
+destination must have a compatible hash.</p>
+<p>If the destination does not support server-side copy or move, rclone
+will fall back to the default behaviour and log an error level message
+to the console.</p>
+<p>Encrypted destinations are not currently supported by
+<code>--track-renames</code> if <code>--track-renames-strategy</code>
+includes <code>hash</code>.</p>
+<p>Note that <code>--track-renames</code> is incompatible with
+<code>--no-traverse</code> and that it uses extra memory to keep track
+of all the rename candidates.</p>
+<p>Note also that <code>--track-renames</code> is incompatible with
+<code>--delete-before</code> and will select <code>--delete-after</code>
+instead of <code>--delete-during</code>.</p>
+<h3
+id="track-renames-strategy-hashmodtimeleafsize">--track-renames-strategy
+(hash,modtime,leaf,size)</h3>
+<p>This option changes the file matching criteria for
+<code>--track-renames</code>.</p>
+<p>The matching is controlled by a comma separated selection of these
+tokens:</p>
 <ul>
-<li><code>modtime</code> - the modification time of the file - not supported on all backends</li>
-<li><code>hash</code> - the hash of the file contents - not supported on all backends</li>
-<li><code>leaf</code> - the name of the file not including its directory name</li>
-<li><code>size</code> - the size of the file (this is always enabled)</li>
+<li><code>modtime</code> - the modification time of the file - not
+supported on all backends</li>
+<li><code>hash</code> - the hash of the file contents - not supported on
+all backends</li>
+<li><code>leaf</code> - the name of the file not including its directory
+name</li>
+<li><code>size</code> - the size of the file (this is always
+enabled)</li>
 </ul>
 <p>The default option is <code>hash</code>.</p>
-<p>Using <code>--track-renames-strategy modtime,leaf</code> would match files based on modification time, the leaf of the file name and the size only.</p>
-<p>Using <code>--track-renames-strategy modtime</code> or <code>leaf</code> can enable <code>--track-renames</code> support for encrypted destinations.</p>
-<p>Note that the <code>hash</code> strategy is not supported with encrypted destinations.</p>
+<p>Using <code>--track-renames-strategy modtime,leaf</code> would match
+files based on modification time, the leaf of the file name and the size
+only.</p>
+<p>Using <code>--track-renames-strategy modtime</code> or
+<code>leaf</code> can enable <code>--track-renames</code> support for
+encrypted destinations.</p>
+<p>Note that the <code>hash</code> strategy is not supported with
+encrypted destinations.</p>
 <h3 id="delete-beforeduringafter">--delete-(before,during,after)</h3>
-<p>This option allows you to specify when files on your destination are deleted when you sync folders.</p>
-<p>Specifying the value <code>--delete-before</code> will delete all files present on the destination, but not on the source <em>before</em> starting the transfer of any new or updated files. This uses two passes through the file systems, one for the deletions and one for the copies.</p>
-<p>Specifying <code>--delete-during</code> will delete files while checking and uploading files. This is the fastest option and uses the least memory.</p>
-<p>Specifying <code>--delete-after</code> (the default value) will delay deletion of files until all new/updated files have been successfully transferred. The files to be deleted are collected in the copy pass then deleted after the copy pass has completed successfully. The files to be deleted are held in memory so this mode may use more memory. This is the safest mode as it will only delete files if there have been no errors subsequent to that. If there have been errors before the deletions start then you will get the message <code>not deleting files as there were IO errors</code>.</p>
+<p>This option allows you to specify when files on your destination are
+deleted when you sync folders.</p>
+<p>Specifying the value <code>--delete-before</code> will delete all
+files present on the destination, but not on the source <em>before</em>
+starting the transfer of any new or updated files. This uses two passes
+through the file systems, one for the deletions and one for the
+copies.</p>
+<p>Specifying <code>--delete-during</code> will delete files while
+checking and uploading files. This is the fastest option and uses the
+least memory.</p>
+<p>Specifying <code>--delete-after</code> (the default value) will delay
+deletion of files until all new/updated files have been successfully
+transferred. The files to be deleted are collected in the copy pass then
+deleted after the copy pass has completed successfully. The files to be
+deleted are held in memory so this mode may use more memory. This is the
+safest mode as it will only delete files if there have been no errors
+subsequent to that. If there have been errors before the deletions start
+then you will get the message
+<code>not deleting files as there were IO errors</code>.</p>
 <h3 id="fast-list">--fast-list</h3>
-<p>When doing anything which involves a directory listing (e.g. <code>sync</code>, <code>copy</code>, <code>ls</code> - in fact nearly every command), rclone has different strategies to choose from.</p>
-<p>The basic strategy is to list one directory and processes it before using more directory lists to process any subdirectories. This is a mandatory backend feature, called <code>List</code>, which means it is supported by all backends. This strategy uses small amount of memory, and because it can be parallelised it is fast for operations involving processing of the list results.</p>
-<p>Some backends provide the support for an alternative strategy, where all files beneath a directory can be listed in one (or a small number) of transactions. Rclone supports this alternative strategy through an optional backend feature called <a href="https://rclone.org/overview/#listr"><code>ListR</code></a>. You can see in the storage system overview documentation's <a href="https://rclone.org/overview/#optional-features">optional features</a> section which backends it is enabled for (these tend to be the bucket-based ones, e.g. S3, B2, GCS, Swift). This strategy requires fewer transactions for highly recursive operations, which is important on backends where this is charged or heavily rate limited. It may be faster (due to fewer transactions) or slower (because it can't be parallelized) depending on different parameters, and may require more memory if rclone has to keep the whole listing in memory.</p>
-<p>Which listing strategy rclone picks for a given operation is complicated, but in general it tries to choose the best possible. It will prefer <code>ListR</code> in situations where it doesn't need to store the listed files in memory, e.g. for unlimited recursive <code>ls</code> command variants. In other situations it will prefer <code>List</code>, e.g. for <code>sync</code> and <code>copy</code>, where it needs to keep the listed files in memory, and is performing operations on them where parallelization may be a huge advantage.</p>
-<p>Rclone is not able to take all relevant parameters into account for deciding the best strategy, and therefore allows you to influence the choice in two ways: You can stop rclone from using <code>ListR</code> by disabling the feature, using the <a href="#disable-feature-feature">--disable</a> option (<code>--disable ListR</code>), or you can allow rclone to use <code>ListR</code> where it would normally choose not to do so due to higher memory usage, using the <code>--fast-list</code> option. Rclone should always produce identical results either way. Using <code>--disable ListR</code> or <code>--fast-list</code> on a remote which doesn't support <code>ListR</code> does nothing, rclone will just ignore it.</p>
-<p>A rule of thumb is that if you pay for transactions and can fit your entire sync listing into memory, then <code>--fast-list</code> is recommended. If you have a very big sync to do, then don't use <code>--fast-list</code>, otherwise you will run out of memory. Run some tests and compare before you decide, and if in doubt then just leave the default, let rclone decide, i.e. not use <code>--fast-list</code>.</p>
+<p>When doing anything which involves a directory listing (e.g.
+<code>sync</code>, <code>copy</code>, <code>ls</code> - in fact nearly
+every command), rclone has different strategies to choose from.</p>
+<p>The basic strategy is to list one directory and processes it before
+using more directory lists to process any subdirectories. This is a
+mandatory backend feature, called <code>List</code>, which means it is
+supported by all backends. This strategy uses small amount of memory,
+and because it can be parallelised it is fast for operations involving
+processing of the list results.</p>
+<p>Some backends provide the support for an alternative strategy, where
+all files beneath a directory can be listed in one (or a small number)
+of transactions. Rclone supports this alternative strategy through an
+optional backend feature called <a
+href="https://rclone.org/overview/#listr"><code>ListR</code></a>. You
+can see in the storage system overview documentation's <a
+href="https://rclone.org/overview/#optional-features">optional
+features</a> section which backends it is enabled for (these tend to be
+the bucket-based ones, e.g. S3, B2, GCS, Swift). This strategy requires
+fewer transactions for highly recursive operations, which is important
+on backends where this is charged or heavily rate limited. It may be
+faster (due to fewer transactions) or slower (because it can't be
+parallelized) depending on different parameters, and may require more
+memory if rclone has to keep the whole listing in memory.</p>
+<p>Which listing strategy rclone picks for a given operation is
+complicated, but in general it tries to choose the best possible. It
+will prefer <code>ListR</code> in situations where it doesn't need to
+store the listed files in memory, e.g. for unlimited recursive
+<code>ls</code> command variants. In other situations it will prefer
+<code>List</code>, e.g. for <code>sync</code> and <code>copy</code>,
+where it needs to keep the listed files in memory, and is performing
+operations on them where parallelization may be a huge advantage.</p>
+<p>Rclone is not able to take all relevant parameters into account for
+deciding the best strategy, and therefore allows you to influence the
+choice in two ways: You can stop rclone from using <code>ListR</code> by
+disabling the feature, using the <a
+href="#disable-feature-feature">--disable</a> option
+(<code>--disable ListR</code>), or you can allow rclone to use
+<code>ListR</code> where it would normally choose not to do so due to
+higher memory usage, using the <code>--fast-list</code> option. Rclone
+should always produce identical results either way. Using
+<code>--disable ListR</code> or <code>--fast-list</code> on a remote
+which doesn't support <code>ListR</code> does nothing, rclone will just
+ignore it.</p>
+<p>A rule of thumb is that if you pay for transactions and can fit your
+entire sync listing into memory, then <code>--fast-list</code> is
+recommended. If you have a very big sync to do, then don't use
+<code>--fast-list</code>, otherwise you will run out of memory. Run some
+tests and compare before you decide, and if in doubt then just leave the
+default, let rclone decide, i.e. not use <code>--fast-list</code>.</p>
 <h3 id="timeouttime">--timeout=TIME</h3>
-<p>This sets the IO idle timeout. If a transfer has started but then becomes idle for this long it is considered broken and disconnected.</p>
+<p>This sets the IO idle timeout. If a transfer has started but then
+becomes idle for this long it is considered broken and disconnected.</p>
 <p>The default is <code>5m</code>. Set to <code>0</code> to disable.</p>
 <h3 id="transfersn">--transfers=N</h3>
-<p>The number of file transfers to run in parallel. It can sometimes be useful to set this to a smaller number if the remote is giving a lot of timeouts or bigger if you have lots of bandwidth and a fast remote.</p>
+<p>The number of file transfers to run in parallel. It can sometimes be
+useful to set this to a smaller number if the remote is giving a lot of
+timeouts or bigger if you have lots of bandwidth and a fast remote.</p>
 <p>The default is to run 4 file transfers in parallel.</p>
-<p>Look at --multi-thread-streams if you would like to control single file transfers.</p>
+<p>Look at --multi-thread-streams if you would like to control single
+file transfers.</p>
 <h3 id="u---update">-u, --update</h3>
-<p>This forces rclone to skip any files which exist on the destination and have a modified time that is newer than the source file.</p>
-<p>This can be useful in avoiding needless transfers when transferring to a remote which doesn't support modification times directly (or when using <code>--use-server-modtime</code> to avoid extra API calls) as it is more accurate than a <code>--size-only</code> check and faster than using <code>--checksum</code>. On such remotes (or when using <code>--use-server-modtime</code>) the time checked will be the uploaded time.</p>
-<p>If an existing destination file has a modification time older than the source file's, it will be updated if the sizes are different. If the sizes are the same, it will be updated if the checksum is different or not available.</p>
-<p>If an existing destination file has a modification time equal (within the computed modify window) to the source file's, it will be updated if the sizes are different. The checksum will not be checked in this case unless the <code>--checksum</code> flag is provided.</p>
+<p>This forces rclone to skip any files which exist on the destination
+and have a modified time that is newer than the source file.</p>
+<p>This can be useful in avoiding needless transfers when transferring
+to a remote which doesn't support modification times directly (or when
+using <code>--use-server-modtime</code> to avoid extra API calls) as it
+is more accurate than a <code>--size-only</code> check and faster than
+using <code>--checksum</code>. On such remotes (or when using
+<code>--use-server-modtime</code>) the time checked will be the uploaded
+time.</p>
+<p>If an existing destination file has a modification time older than
+the source file's, it will be updated if the sizes are different. If the
+sizes are the same, it will be updated if the checksum is different or
+not available.</p>
+<p>If an existing destination file has a modification time equal (within
+the computed modify window) to the source file's, it will be updated if
+the sizes are different. The checksum will not be checked in this case
+unless the <code>--checksum</code> flag is provided.</p>
 <p>In all other cases the file will not be updated.</p>
-<p>Consider using the <code>--modify-window</code> flag to compensate for time skews between the source and the backend, for backends that do not support mod times, and instead use uploaded times. However, if the backend does not support checksums, note that syncing or copying within the time skew window may still result in additional transfers for safety.</p>
+<p>Consider using the <code>--modify-window</code> flag to compensate
+for time skews between the source and the backend, for backends that do
+not support mod times, and instead use uploaded times. However, if the
+backend does not support checksums, note that syncing or copying within
+the time skew window may still result in additional transfers for
+safety.</p>
 <h3 id="use-mmap">--use-mmap</h3>
-<p>If this flag is set then rclone will use anonymous memory allocated by mmap on Unix based platforms and VirtualAlloc on Windows for its transfer buffers (size controlled by <code>--buffer-size</code>). Memory allocated like this does not go on the Go heap and can be returned to the OS immediately when it is finished with.</p>
-<p>If this flag is not set then rclone will allocate and free the buffers using the Go memory allocator which may use more memory as memory pages are returned less aggressively to the OS.</p>
-<p>It is possible this does not work well on all platforms so it is disabled by default; in the future it may be enabled by default.</p>
+<p>If this flag is set then rclone will use anonymous memory allocated
+by mmap on Unix based platforms and VirtualAlloc on Windows for its
+transfer buffers (size controlled by <code>--buffer-size</code>). Memory
+allocated like this does not go on the Go heap and can be returned to
+the OS immediately when it is finished with.</p>
+<p>If this flag is not set then rclone will allocate and free the
+buffers using the Go memory allocator which may use more memory as
+memory pages are returned less aggressively to the OS.</p>
+<p>It is possible this does not work well on all platforms so it is
+disabled by default; in the future it may be enabled by default.</p>
 <h3 id="use-server-modtime">--use-server-modtime</h3>
-<p>Some object-store backends (e.g, Swift, S3) do not preserve file modification times (modtime). On these backends, rclone stores the original modtime as additional metadata on the object. By default it will make an API call to retrieve the metadata when the modtime is needed by an operation.</p>
-<p>Use this flag to disable the extra API call and rely instead on the server's modified time. In cases such as a local to remote sync using <code>--update</code>, knowing the local file is newer than the time it was last uploaded to the remote is sufficient. In those cases, this flag can speed up the process and reduce the number of API calls necessary.</p>
-<p>Using this flag on a sync operation without also using <code>--update</code> would cause all files modified at any time other than the last upload time to be uploaded again, which is probably not what you want.</p>
+<p>Some object-store backends (e.g, Swift, S3) do not preserve file
+modification times (modtime). On these backends, rclone stores the
+original modtime as additional metadata on the object. By default it
+will make an API call to retrieve the metadata when the modtime is
+needed by an operation.</p>
+<p>Use this flag to disable the extra API call and rely instead on the
+server's modified time. In cases such as a local to remote sync using
+<code>--update</code>, knowing the local file is newer than the time it
+was last uploaded to the remote is sufficient. In those cases, this flag
+can speed up the process and reduce the number of API calls
+necessary.</p>
+<p>Using this flag on a sync operation without also using
+<code>--update</code> would cause all files modified at any time other
+than the last upload time to be uploaded again, which is probably not
+what you want.</p>
 <h3 id="v--vv---verbose">-v, -vv, --verbose</h3>
-<p>With <code>-v</code> rclone will tell you about each file that is transferred and a small number of significant events.</p>
-<p>With <code>-vv</code> rclone will become very verbose telling you about every file it considers and transfers. Please send bug reports with a log with this setting.</p>
-<p>When setting verbosity as an environment variable, use <code>RCLONE_VERBOSE=1</code> or <code>RCLONE_VERBOSE=2</code> for <code>-v</code> and <code>-vv</code> respectively.</p>
+<p>With <code>-v</code> rclone will tell you about each file that is
+transferred and a small number of significant events.</p>
+<p>With <code>-vv</code> rclone will become very verbose telling you
+about every file it considers and transfers. Please send bug reports
+with a log with this setting.</p>
+<p>When setting verbosity as an environment variable, use
+<code>RCLONE_VERBOSE=1</code> or <code>RCLONE_VERBOSE=2</code> for
+<code>-v</code> and <code>-vv</code> respectively.</p>
 <h3 id="v---version">-V, --version</h3>
 <p>Prints the version number</p>
 <h2 id="ssltls-options">SSL/TLS options</h2>
-<p>The outgoing SSL/TLS connections rclone makes can be controlled with these options. For example this can be very useful with the HTTP or WebDAV backends. Rclone HTTP servers have their own set of configuration for SSL/TLS which you can find in their documentation.</p>
+<p>The outgoing SSL/TLS connections rclone makes can be controlled with
+these options. For example this can be very useful with the HTTP or
+WebDAV backends. Rclone HTTP servers have their own set of configuration
+for SSL/TLS which you can find in their documentation.</p>
 <h3 id="ca-cert-stringarray">--ca-cert stringArray</h3>
-<p>This loads the PEM encoded certificate authority certificates and uses it to verify the certificates of the servers rclone connects to.</p>
-<p>If you have generated certificates signed with a local CA then you will need this flag to connect to servers using those certificates.</p>
+<p>This loads the PEM encoded certificate authority certificates and
+uses it to verify the certificates of the servers rclone connects
+to.</p>
+<p>If you have generated certificates signed with a local CA then you
+will need this flag to connect to servers using those certificates.</p>
 <h3 id="client-cert-string">--client-cert string</h3>
 <p>This loads the PEM encoded client side certificate.</p>
-<p>This is used for <a href="https://en.wikipedia.org/wiki/Mutual_authentication">mutual TLS authentication</a>.</p>
-<p>The <code>--client-key</code> flag is required too when using this.</p>
+<p>This is used for <a
+href="https://en.wikipedia.org/wiki/Mutual_authentication">mutual TLS
+authentication</a>.</p>
+<p>The <code>--client-key</code> flag is required too when using
+this.</p>
 <h3 id="client-key-string">--client-key string</h3>
-<p>This loads the PEM encoded client side private key used for mutual TLS authentication. Used in conjunction with <code>--client-cert</code>.</p>
-<h3 id="no-check-certificatetruefalse">--no-check-certificate=true/false</h3>
-<p><code>--no-check-certificate</code> controls whether a client verifies the server's certificate chain and host name. If <code>--no-check-certificate</code> is true, TLS accepts any certificate presented by the server and any host name in that certificate. In this mode, TLS is susceptible to man-in-the-middle attacks.</p>
+<p>This loads the PEM encoded client side private key used for mutual
+TLS authentication. Used in conjunction with
+<code>--client-cert</code>.</p>
+<h3
+id="no-check-certificatetruefalse">--no-check-certificate=true/false</h3>
+<p><code>--no-check-certificate</code> controls whether a client
+verifies the server's certificate chain and host name. If
+<code>--no-check-certificate</code> is true, TLS accepts any certificate
+presented by the server and any host name in that certificate. In this
+mode, TLS is susceptible to man-in-the-middle attacks.</p>
 <p>This option defaults to <code>false</code>.</p>
 <p><strong>This should be used only for testing.</strong></p>
 <h2 id="configuration-encryption">Configuration Encryption</h2>
-<p>Your configuration file contains information for logging in to your cloud services. This means that you should keep your <code>rclone.conf</code> file in a secure location.</p>
-<p>If you are in an environment where that isn't possible, you can add a password to your configuration. This means that you will have to supply the password every time you start rclone.</p>
-<p>To add a password to your rclone configuration, execute <code>rclone config</code>.</p>
+<p>Your configuration file contains information for logging in to your
+cloud services. This means that you should keep your
+<code>rclone.conf</code> file in a secure location.</p>
+<p>If you are in an environment where that isn't possible, you can add a
+password to your configuration. This means that you will have to supply
+the password every time you start rclone.</p>
+<p>To add a password to your rclone configuration, execute
+<code>rclone config</code>.</p>
 <pre><code>&gt;rclone config
 Current remotes:
 
@@ -7684,31 +13628,91 @@ c) Change Password
 u) Unencrypt configuration
 q) Quit to main menu
 c/u/q&gt;</code></pre>
-<p>Your configuration is now encrypted, and every time you start rclone you will have to supply the password. See below for details. In the same menu, you can change the password or completely remove encryption from your configuration.</p>
-<p>There is no way to recover the configuration if you lose your password.</p>
+<p>Your configuration is now encrypted, and every time you start rclone
+you will have to supply the password. See below for details. In the same
+menu, you can change the password or completely remove encryption from
+your configuration.</p>
+<p>There is no way to recover the configuration if you lose your
+password.</p>
 <p>You can also use</p>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config_encryption_set/">rclone config encryption set</a> to set the config encryption directly</li>
-<li><a href="https://rclone.org/commands/rclone_config_encryption_remove/">rclone config encryption remove</a> to remove it</li>
-<li><a href="https://rclone.org/commands/rclone_config_encryption_check/">rclone config encryption check</a> to check that it is encrypted properly.</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption_set/">rclone
+config encryption set</a> to set the config encryption directly</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption_remove/">rclone
+config encryption remove</a> to remove it</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption_check/">rclone
+config encryption check</a> to check that it is encrypted properly.</li>
 </ul>
-<p>rclone uses <a href="https://godoc.org/golang.org/x/crypto/nacl/secretbox">nacl secretbox</a> which in turn uses XSalsa20 and Poly1305 to encrypt and authenticate your configuration with secret-key cryptography. The password is SHA-256 hashed, which produces the key for secretbox. The hashed password is not stored.</p>
-<p>While this provides very good security, we do not recommend storing your encrypted rclone configuration in public if it contains sensitive information, maybe except if you use a very strong password.</p>
-<p>If it is safe in your environment, you can set the <code>RCLONE_CONFIG_PASS</code> environment variable to contain your password, in which case it will be used for decrypting the configuration.</p>
-<p>You can set this for a session from a script. For unix like systems save this to a file called <code>set-rclone-password</code>:</p>
+<p>rclone uses <a
+href="https://godoc.org/golang.org/x/crypto/nacl/secretbox">nacl
+secretbox</a> which in turn uses XSalsa20 and Poly1305 to encrypt and
+authenticate your configuration with secret-key cryptography. The
+password is SHA-256 hashed, which produces the key for secretbox. The
+hashed password is not stored.</p>
+<p>While this provides very good security, we do not recommend storing
+your encrypted rclone configuration in public if it contains sensitive
+information, maybe except if you use a very strong password.</p>
+<p>If it is safe in your environment, you can set the
+<code>RCLONE_CONFIG_PASS</code> environment variable to contain your
+password, in which case it will be used for decrypting the
+configuration.</p>
+<p>You can set this for a session from a script. For unix like systems
+save this to a file called <code>set-rclone-password</code>:</p>
 <pre><code>#!/bin/echo Source this file don&#39;t run it
 
 read -s RCLONE_CONFIG_PASS
 export RCLONE_CONFIG_PASS</code></pre>
-<p>Then source the file when you want to use it. From the shell you would do <code>source set-rclone-password</code>. It will then ask you for the password and set it in the environment variable.</p>
-<p>An alternate means of supplying the password is to provide a script which will retrieve the password and print on standard output. This script should have a fully specified path name and not rely on any environment variables. The script is supplied either via <a href="#password-command"><code>--password-command="..."</code></a> command line argument or via the <code>RCLONE_PASSWORD_COMMAND</code> environment variable.</p>
-<p>One useful example of this is using the <code>passwordstore</code> application to retrieve the password:</p>
+<p>Then source the file when you want to use it. From the shell you
+would do <code>source set-rclone-password</code>. It will then ask you
+for the password and set it in the environment variable.</p>
+<p>An alternate means of supplying the password is to provide a script
+which will retrieve the password and print on standard output. This
+script should have a fully specified path name and not rely on any
+environment variables. The script is supplied either via <a
+href="#password-command"><code>--password-command="..."</code></a>
+command line argument or via the <code>RCLONE_PASSWORD_COMMAND</code>
+environment variable.</p>
+<p>One useful example of this is using the <code>passwordstore</code>
+application to retrieve the password:</p>
 <pre><code>export RCLONE_PASSWORD_COMMAND=&quot;pass rclone/config&quot;</code></pre>
-<p>If the <code>passwordstore</code> password manager holds the password for the rclone configuration, using the script method means the password is primarily protected by the <code>passwordstore</code> system, and is never embedded in the clear in scripts, nor available for examination using the standard commands available. It is quite possible with long running rclone sessions for copies of passwords to be innocently captured in log files or terminal scroll buffers, etc. Using the script method of supplying the password enhances the security of the config password considerably.</p>
-<p>If you are running rclone inside a script, unless you are using the <code>--password-command</code> method, you might want to disable password prompts. To do that, pass the parameter <code>--ask-password=false</code> to rclone. This will make rclone fail instead of asking for a password if <code>RCLONE_CONFIG_PASS</code> doesn't contain a valid password, and <code>--password-command</code> has not been supplied.</p>
-<p>Whenever running commands that may be affected by options in a configuration file, rclone will look for an existing file according to the rules described <a href="#config-config-file">above</a>, and load any it finds. If an encrypted file is found, this includes decrypting it, with the possible consequence of a password prompt. When executing a command line that you know are not actually using anything from such a configuration file, you can avoid it being loaded by overriding the location, e.g. with one of the documented special values for memory-only configuration. Since only backend options can be stored in configuration files, this is normally unnecessary for commands that do not operate on backends, e.g. <code>completion</code>. However, it will be relevant for commands that do operate on backends in general, but are used without referencing a stored remote, e.g. listing local filesystem paths, or <a href="#connection-strings">connection strings</a>: <code>rclone --config="" ls .</code></p>
-<h2 id="configuration-encryption-cheatsheet">Configuration Encryption Cheatsheet</h2>
-<p>You can quickly apply a configuration encryption without plain-text at rest or transfer. Detailed instructions for popular OSes:</p>
+<p>If the <code>passwordstore</code> password manager holds the password
+for the rclone configuration, using the script method means the password
+is primarily protected by the <code>passwordstore</code> system, and is
+never embedded in the clear in scripts, nor available for examination
+using the standard commands available. It is quite possible with long
+running rclone sessions for copies of passwords to be innocently
+captured in log files or terminal scroll buffers, etc. Using the script
+method of supplying the password enhances the security of the config
+password considerably.</p>
+<p>If you are running rclone inside a script, unless you are using the
+<code>--password-command</code> method, you might want to disable
+password prompts. To do that, pass the parameter
+<code>--ask-password=false</code> to rclone. This will make rclone fail
+instead of asking for a password if <code>RCLONE_CONFIG_PASS</code>
+doesn't contain a valid password, and <code>--password-command</code>
+has not been supplied.</p>
+<p>Whenever running commands that may be affected by options in a
+configuration file, rclone will look for an existing file according to
+the rules described <a href="#config-config-file">above</a>, and load
+any it finds. If an encrypted file is found, this includes decrypting
+it, with the possible consequence of a password prompt. When executing a
+command line that you know are not actually using anything from such a
+configuration file, you can avoid it being loaded by overriding the
+location, e.g. with one of the documented special values for memory-only
+configuration. Since only backend options can be stored in configuration
+files, this is normally unnecessary for commands that do not operate on
+backends, e.g. <code>completion</code>. However, it will be relevant for
+commands that do operate on backends in general, but are used without
+referencing a stored remote, e.g. listing local filesystem paths, or <a
+href="#connection-strings">connection strings</a>:
+<code>rclone --config="" ls .</code></p>
+<h2 id="configuration-encryption-cheatsheet">Configuration Encryption
+Cheatsheet</h2>
+<p>You can quickly apply a configuration encryption without plain-text
+at rest or transfer. Detailed instructions for popular OSes:</p>
 <h3 id="mac">Mac</h3>
 <ul>
 <li>Generate and store a password</li>
@@ -7722,7 +13726,11 @@ export RCLONE_CONFIG_PASS</code></pre>
 <ul>
 <li>Prerequisite</li>
 </ul>
-<p>Linux doesn't come with a default password manager. Let's install the "pass" utility using a package manager, e.g. <code>apt install pass</code>, <code>yum install pass</code>, <a href="https://www.passwordstore.org/#download">etc.</a>; then initialize a password store:</p>
+<p>Linux doesn't come with a default password manager. Let's install the
+"pass" utility using a package manager, e.g.
+<code>apt install pass</code>, <code>yum install pass</code>, <a
+href="https://www.passwordstore.org/#download">etc.</a>; then initialize
+a password store:</p>
 <p><code>pass init rclone</code></p>
 <ul>
 <li>Generate and store a password</li>
@@ -7741,41 +13749,69 @@ export RCLONE_CONFIG_PASS</code></pre>
 <li>Add the password retrieval instruction</li>
 </ul>
 <p><code>[Environment]::SetEnvironmentVariable("RCLONE_PASSWORD_COMMAND", "[System.Runtime.InteropServices.Marshal]::PtrToStringAuto([System.Runtime.InteropServices.Marshal]::SecureStringToBSTR((Import-Clixml -Path "rclone-credential.xml").Password))")</code></p>
-<h3 id="encrypt-the-config-file-all-systems">Encrypt the config file (all systems)</h3>
+<h3 id="encrypt-the-config-file-all-systems">Encrypt the config file
+(all systems)</h3>
 <ul>
 <li><p>Execute <code>rclone config</code> -&gt; <code>s</code></p></li>
 <li><p>Add/update the password from previous steps</p></li>
 </ul>
 <h2 id="developer-options">Developer options</h2>
-<p>These options are useful when developing or debugging rclone. There are also some more remote specific options which aren't documented here which are used for testing. These start with remote name e.g. <code>--drive-test-option</code> - see the docs for the remote in question.</p>
+<p>These options are useful when developing or debugging rclone. There
+are also some more remote specific options which aren't documented here
+which are used for testing. These start with remote name e.g.
+<code>--drive-test-option</code> - see the docs for the remote in
+question.</p>
 <h3 id="cpuprofilefile">--cpuprofile=FILE</h3>
-<p>Write CPU profile to file. This can be analysed with <code>go tool pprof</code>.</p>
+<p>Write CPU profile to file. This can be analysed with
+<code>go tool pprof</code>.</p>
 <h4 id="dump-flagflagflag">--dump flag,flag,flag</h4>
-<p>The <code>--dump</code> flag takes a comma separated list of flags to dump info about.</p>
-<p>Note that some headers including <code>Accept-Encoding</code> as shown may not be correct in the request and the response may not show <code>Content-Encoding</code> if the go standard libraries auto gzip encoding was in effect. In this case the body of the request will be gunzipped before showing it.</p>
+<p>The <code>--dump</code> flag takes a comma separated list of flags to
+dump info about.</p>
+<p>Note that some headers including <code>Accept-Encoding</code> as
+shown may not be correct in the request and the response may not show
+<code>Content-Encoding</code> if the go standard libraries auto gzip
+encoding was in effect. In this case the body of the request will be
+gunzipped before showing it.</p>
 <p>The available flags are:</p>
 <h4 id="dump-headers">--dump headers</h4>
-<p>Dump HTTP headers with <code>Authorization:</code> lines removed. May still contain sensitive info. Can be very verbose. Useful for debugging only.</p>
-<p>Use <code>--dump auth</code> if you do want the <code>Authorization:</code> headers.</p>
+<p>Dump HTTP headers with <code>Authorization:</code> lines removed. May
+still contain sensitive info. Can be very verbose. Useful for debugging
+only.</p>
+<p>Use <code>--dump auth</code> if you do want the
+<code>Authorization:</code> headers.</p>
 <h4 id="dump-bodies">--dump bodies</h4>
-<p>Dump HTTP headers and bodies - may contain sensitive info. Can be very verbose. Useful for debugging only.</p>
-<p>Note that the bodies are buffered in memory so don't use this for enormous files.</p>
+<p>Dump HTTP headers and bodies - may contain sensitive info. Can be
+very verbose. Useful for debugging only.</p>
+<p>Note that the bodies are buffered in memory so don't use this for
+enormous files.</p>
 <h4 id="dump-requests">--dump requests</h4>
-<p>Like <code>--dump bodies</code> but dumps the request bodies and the response headers. Useful for debugging download problems.</p>
+<p>Like <code>--dump bodies</code> but dumps the request bodies and the
+response headers. Useful for debugging download problems.</p>
 <h4 id="dump-responses">--dump responses</h4>
-<p>Like <code>--dump bodies</code> but dumps the response bodies and the request headers. Useful for debugging upload problems.</p>
+<p>Like <code>--dump bodies</code> but dumps the response bodies and the
+request headers. Useful for debugging upload problems.</p>
 <h4 id="dump-auth">--dump auth</h4>
-<p>Dump HTTP headers - will contain sensitive info such as <code>Authorization:</code> headers - use <code>--dump headers</code> to dump without <code>Authorization:</code> headers. Can be very verbose. Useful for debugging only.</p>
+<p>Dump HTTP headers - will contain sensitive info such as
+<code>Authorization:</code> headers - use <code>--dump headers</code> to
+dump without <code>Authorization:</code> headers. Can be very verbose.
+Useful for debugging only.</p>
 <h4 id="dump-filters">--dump filters</h4>
-<p>Dump the filters to the output. Useful to see exactly what include and exclude options are filtering on.</p>
+<p>Dump the filters to the output. Useful to see exactly what include
+and exclude options are filtering on.</p>
 <h4 id="dump-goroutines">--dump goroutines</h4>
-<p>This dumps a list of the running go-routines at the end of the command to standard output.</p>
+<p>This dumps a list of the running go-routines at the end of the
+command to standard output.</p>
 <h4 id="dump-openfiles">--dump openfiles</h4>
-<p>This dumps a list of the open files at the end of the command. It uses the <code>lsof</code> command to do that so you'll need that installed to use it.</p>
+<p>This dumps a list of the open files at the end of the command. It
+uses the <code>lsof</code> command to do that so you'll need that
+installed to use it.</p>
 <h4 id="dump-mapper">--dump mapper</h4>
-<p>This shows the JSON blobs being sent to the program supplied with <code>--metadata-mapper</code> and received from it. It can be useful for debugging the metadata mapper interface.</p>
+<p>This shows the JSON blobs being sent to the program supplied with
+<code>--metadata-mapper</code> and received from it. It can be useful
+for debugging the metadata mapper interface.</p>
 <h3 id="memprofilefile">--memprofile=FILE</h3>
-<p>Write memory profile to file. This can be analysed with <code>go tool pprof</code>.</p>
+<p>Write memory profile to file. This can be analysed with
+<code>go tool pprof</code>.</p>
 <h2 id="filtering">Filtering</h2>
 <p>For the filtering options</p>
 <ul>
@@ -7801,34 +13837,72 @@ export RCLONE_CONFIG_PASS</code></pre>
 <li><code>--metadata-filter</code></li>
 <li><code>--metadata-filter-from</code></li>
 </ul>
-<p>See the <a href="https://rclone.org/filtering/">filtering section</a>.</p>
+<p>See the <a href="https://rclone.org/filtering/">filtering
+section</a>.</p>
 <h2 id="remote-control">Remote control</h2>
-<p>For the remote control options and for instructions on how to remote control rclone</p>
+<p>For the remote control options and for instructions on how to remote
+control rclone</p>
 <ul>
 <li><code>--rc</code></li>
 <li>and anything starting with <code>--rc-</code></li>
 </ul>
-<p>See <a href="https://rclone.org/rc/">the remote control section</a>.</p>
+<p>See <a href="https://rclone.org/rc/">the remote control
+section</a>.</p>
 <h2 id="logging">Logging</h2>
-<p>rclone has 4 levels of logging, <code>ERROR</code>, <code>NOTICE</code>, <code>INFO</code> and <code>DEBUG</code>.</p>
-<p>By default, rclone logs to standard error. This means you can redirect standard error and still see the normal output of rclone commands (e.g. <code>rclone ls</code>).</p>
-<p>By default, rclone will produce <code>Error</code> and <code>Notice</code> level messages.</p>
-<p>If you use the <code>-q</code> flag, rclone will only produce <code>Error</code> messages.</p>
-<p>If you use the <code>-v</code> flag, rclone will produce <code>Error</code>, <code>Notice</code> and <code>Info</code> messages.</p>
-<p>If you use the <code>-vv</code> flag, rclone will produce <code>Error</code>, <code>Notice</code>, <code>Info</code> and <code>Debug</code> messages.</p>
-<p>You can also control the log levels with the <code>--log-level</code> flag.</p>
-<p>If you use the <code>--log-file=FILE</code> option, rclone will redirect <code>Error</code>, <code>Info</code> and <code>Debug</code> messages along with standard error to FILE.</p>
-<p>If you use the <code>--syslog</code> flag then rclone will log to syslog and the <code>--syslog-facility</code> control which facility it uses.</p>
-<p>Rclone prefixes all log messages with their level in capitals, e.g. INFO which makes it easy to grep the log file for different kinds of information.</p>
+<p>rclone has 4 levels of logging, <code>ERROR</code>,
+<code>NOTICE</code>, <code>INFO</code> and <code>DEBUG</code>.</p>
+<p>By default, rclone logs to standard error. This means you can
+redirect standard error and still see the normal output of rclone
+commands (e.g. <code>rclone ls</code>).</p>
+<p>By default, rclone will produce <code>Error</code> and
+<code>Notice</code> level messages.</p>
+<p>If you use the <code>-q</code> flag, rclone will only produce
+<code>Error</code> messages.</p>
+<p>If you use the <code>-v</code> flag, rclone will produce
+<code>Error</code>, <code>Notice</code> and <code>Info</code>
+messages.</p>
+<p>If you use the <code>-vv</code> flag, rclone will produce
+<code>Error</code>, <code>Notice</code>, <code>Info</code> and
+<code>Debug</code> messages.</p>
+<p>You can also control the log levels with the <code>--log-level</code>
+flag.</p>
+<p>If you use the <code>--log-file=FILE</code> option, rclone will
+redirect <code>Error</code>, <code>Info</code> and <code>Debug</code>
+messages along with standard error to FILE.</p>
+<p>If you use the <code>--syslog</code> flag then rclone will log to
+syslog and the <code>--syslog-facility</code> control which facility it
+uses.</p>
+<p>Rclone prefixes all log messages with their level in capitals, e.g.
+INFO which makes it easy to grep the log file for different kinds of
+information.</p>
 <h2 id="metrics">Metrics</h2>
 <p>Rclone can publish metrics in the OpenMetrics/Prometheus format.</p>
-<p>To enable the metrics endpoint, use the <code>--metrics-addr</code> flag. Metrics can also be published on the <code>--rc-addr</code> port if the <code>--rc</code> flag and <code>--rc-enable-metrics</code> flags are supplied or if using rclone rcd <code>--rc-enable-metrics</code></p>
-<p>Rclone provides extensive configuration options for the metrics HTTP endpoint. These settings are grouped under the Metrics section and have a prefix <code>--metrics-*</code>.</p>
-<p>When metrics are enabled with <code>--rc-enable-metrics</code>, they will be published on the same port as the rc API. In this case, the <code>--metrics-*</code> flags will be ignored, and the HTTP endpoint configuration will be managed by the <code>--rc-*</code> parameters.</p>
+<p>To enable the metrics endpoint, use the <code>--metrics-addr</code>
+flag. Metrics can also be published on the <code>--rc-addr</code> port
+if the <code>--rc</code> flag and <code>--rc-enable-metrics</code> flags
+are supplied or if using rclone rcd <code>--rc-enable-metrics</code></p>
+<p>Rclone provides extensive configuration options for the metrics HTTP
+endpoint. These settings are grouped under the Metrics section and have
+a prefix <code>--metrics-*</code>.</p>
+<p>When metrics are enabled with <code>--rc-enable-metrics</code>, they
+will be published on the same port as the rc API. In this case, the
+<code>--metrics-*</code> flags will be ignored, and the HTTP endpoint
+configuration will be managed by the <code>--rc-*</code> parameters.</p>
 <h2 id="exit-code">Exit Code</h2>
-<p>If any errors occur during the command execution, rclone will exit with a non-zero exit code. This allows scripts to detect when rclone operations have failed.</p>
-<p>During the startup phase, rclone will exit immediately if an error is detected in the configuration. There will always be a log message immediately before exiting.</p>
-<p>When rclone is running it will accumulate errors as it goes along, and only exit with a non-zero exit code if (after retries) there were still failed transfers. For every error counted there will be a high priority log message (visible with <code>-q</code>) showing the message and which file caused the problem. A high priority message is also shown when starting a retry so the user can see that any previous error messages may not be valid after the retry. If rclone has done a retry it will log a high priority message if the retry was successful.</p>
+<p>If any errors occur during the command execution, rclone will exit
+with a non-zero exit code. This allows scripts to detect when rclone
+operations have failed.</p>
+<p>During the startup phase, rclone will exit immediately if an error is
+detected in the configuration. There will always be a log message
+immediately before exiting.</p>
+<p>When rclone is running it will accumulate errors as it goes along,
+and only exit with a non-zero exit code if (after retries) there were
+still failed transfers. For every error counted there will be a high
+priority log message (visible with <code>-q</code>) showing the message
+and which file caused the problem. A high priority message is also shown
+when starting a retry so the user can see that any previous error
+messages may not be valid after the retry. If rclone has done a retry it
+will log a high priority message if the retry was successful.</p>
 <h3 id="list-of-exit-codes">List of exit codes</h3>
 <ul>
 <li><code>0</code> - success</li>
@@ -7836,24 +13910,49 @@ export RCLONE_CONFIG_PASS</code></pre>
 <li><code>2</code> - Error not otherwise categorised</li>
 <li><code>3</code> - Directory not found</li>
 <li><code>4</code> - File not found</li>
-<li><code>5</code> - Temporary error (one that more retries might fix) (Retry errors)</li>
-<li><code>6</code> - Less serious errors (like 461 errors from dropbox) (NoRetry errors)</li>
-<li><code>7</code> - Fatal error (one that more retries won't fix, like account suspended) (Fatal errors)</li>
-<li><code>8</code> - Transfer exceeded - limit set by --max-transfer reached</li>
-<li><code>9</code> - Operation successful, but no files transferred (Requires <a href="#error-on-no-transfer"><code>--error-on-no-transfer</code></a>)</li>
-<li><code>10</code> - Duration exceeded - limit set by --max-duration reached</li>
+<li><code>5</code> - Temporary error (one that more retries might fix)
+(Retry errors)</li>
+<li><code>6</code> - Less serious errors (like 461 errors from dropbox)
+(NoRetry errors)</li>
+<li><code>7</code> - Fatal error (one that more retries won't fix, like
+account suspended) (Fatal errors)</li>
+<li><code>8</code> - Transfer exceeded - limit set by --max-transfer
+reached</li>
+<li><code>9</code> - Operation successful, but no files transferred
+(Requires <a
+href="#error-on-no-transfer"><code>--error-on-no-transfer</code></a>)</li>
+<li><code>10</code> - Duration exceeded - limit set by --max-duration
+reached</li>
 </ul>
 <h2 id="environment-variables">Environment Variables</h2>
-<p>Rclone can be configured entirely using environment variables. These can be used to set defaults for options or config file entries.</p>
+<p>Rclone can be configured entirely using environment variables. These
+can be used to set defaults for options or config file entries.</p>
 <h3 id="options-91">Options</h3>
-<p>Every option in rclone can have its default set by environment variable.</p>
-<p>To find the name of the environment variable, first, take the long option name, strip the leading <code>--</code>, change <code>-</code> to <code>_</code>, make upper case and prepend <code>RCLONE_</code>.</p>
-<p>For example, to always set <code>--stats 5s</code>, set the environment variable <code>RCLONE_STATS=5s</code>. If you set stats on the command line this will override the environment variable setting.</p>
-<p>Or to always use the trash in drive <code>--drive-use-trash</code>, set <code>RCLONE_DRIVE_USE_TRASH=true</code>.</p>
-<p>Verbosity is slightly different, the environment variable equivalent of <code>--verbose</code> or <code>-v</code> is <code>RCLONE_VERBOSE=1</code>, or for <code>-vv</code>, <code>RCLONE_VERBOSE=2</code>.</p>
-<p>The same parser is used for the options and the environment variables so they take exactly the same form.</p>
-<p>The options set by environment variables can be seen with the <code>-vv</code> flag, e.g. <code>rclone version -vv</code>.</p>
-<p>Options that can appear multiple times (type <code>stringArray</code>) are treated slighly differently as environment variables can only be defined once. In order to allow a simple mechanism for adding one or many items, the input is treated as a <a href="https://godoc.org/encoding/csv">CSV encoded</a> string. For example</p>
+<p>Every option in rclone can have its default set by environment
+variable.</p>
+<p>To find the name of the environment variable, first, take the long
+option name, strip the leading <code>--</code>, change <code>-</code> to
+<code>_</code>, make upper case and prepend <code>RCLONE_</code>.</p>
+<p>For example, to always set <code>--stats 5s</code>, set the
+environment variable <code>RCLONE_STATS=5s</code>. If you set stats on
+the command line this will override the environment variable
+setting.</p>
+<p>Or to always use the trash in drive <code>--drive-use-trash</code>,
+set <code>RCLONE_DRIVE_USE_TRASH=true</code>.</p>
+<p>Verbosity is slightly different, the environment variable equivalent
+of <code>--verbose</code> or <code>-v</code> is
+<code>RCLONE_VERBOSE=1</code>, or for <code>-vv</code>,
+<code>RCLONE_VERBOSE=2</code>.</p>
+<p>The same parser is used for the options and the environment variables
+so they take exactly the same form.</p>
+<p>The options set by environment variables can be seen with the
+<code>-vv</code> flag, e.g. <code>rclone version -vv</code>.</p>
+<p>Options that can appear multiple times (type
+<code>stringArray</code>) are treated slighly differently as environment
+variables can only be defined once. In order to allow a simple mechanism
+for adding one or many items, the input is treated as a <a
+href="https://godoc.org/encoding/csv">CSV encoded</a> string. For
+example</p>
 <table>
 <colgroup>
 <col style="width: 52%" />
@@ -7884,11 +13983,22 @@ export RCLONE_CONFIG_PASS</code></pre>
 </tr>
 </tbody>
 </table>
-<p>If <code>stringArray</code> options are defined as environment variables <strong>and</strong> options on the command line then all the values will be used.</p>
+<p>If <code>stringArray</code> options are defined as environment
+variables <strong>and</strong> options on the command line then all the
+values will be used.</p>
 <h3 id="config-file">Config file</h3>
-<p>You can set defaults for values in the config file on an individual remote basis. The names of the config items are documented in the page for each backend.</p>
-<p>To find the name of the environment variable, you need to set, take <code>RCLONE_CONFIG_</code> + name of remote + <code>_</code> + name of config file option and make it all uppercase. Note one implication here is the remote's name must be convertible into a valid environment variable name, so it can only contain letters, digits, or the <code>_</code> (underscore) character.</p>
-<p>For example, to configure an S3 remote named <code>mys3:</code> without a config file (using unix ways of setting environment variables):</p>
+<p>You can set defaults for values in the config file on an individual
+remote basis. The names of the config items are documented in the page
+for each backend.</p>
+<p>To find the name of the environment variable, you need to set, take
+<code>RCLONE_CONFIG_</code> + name of remote + <code>_</code> + name of
+config file option and make it all uppercase. Note one implication here
+is the remote's name must be convertible into a valid environment
+variable name, so it can only contain letters, digits, or the
+<code>_</code> (underscore) character.</p>
+<p>For example, to configure an S3 remote named <code>mys3:</code>
+without a config file (using unix ways of setting environment
+variables):</p>
 <pre><code>$ export RCLONE_CONFIG_MYS3_TYPE=s3
 $ export RCLONE_CONFIG_MYS3_ACCESS_KEY_ID=XXX
 $ export RCLONE_CONFIG_MYS3_SECRET_ACCESS_KEY=XXX
@@ -7896,51 +14006,94 @@ $ rclone lsd mys3:
           -1 2016-09-21 12:54:21        -1 my-bucket
 $ rclone listremotes | grep mys3
 mys3:</code></pre>
-<p>Note that if you want to create a remote using environment variables you must create the <code>..._TYPE</code> variable as above.</p>
-<p>Note that the name of a remote created using environment variable is case insensitive, in contrast to regular remotes stored in config file as documented <a href="#valid-remote-names">above</a>. You must write the name in uppercase in the environment variable, but as seen from example above it will be listed and can be accessed in lowercase, while you can also refer to the same remote in uppercase:</p>
+<p>Note that if you want to create a remote using environment variables
+you must create the <code>..._TYPE</code> variable as above.</p>
+<p>Note that the name of a remote created using environment variable is
+case insensitive, in contrast to regular remotes stored in config file
+as documented <a href="#valid-remote-names">above</a>. You must write
+the name in uppercase in the environment variable, but as seen from
+example above it will be listed and can be accessed in lowercase, while
+you can also refer to the same remote in uppercase:</p>
 <pre><code>$ rclone lsd mys3:
           -1 2016-09-21 12:54:21        -1 my-bucket
 $ rclone lsd MYS3:
           -1 2016-09-21 12:54:21        -1 my-bucket</code></pre>
-<p>Note that you can only set the options of the immediate backend, so RCLONE_CONFIG_MYS3CRYPT_ACCESS_KEY_ID has no effect, if myS3Crypt is a crypt remote based on an S3 remote. However RCLONE_S3_ACCESS_KEY_ID will set the access key of all remotes using S3, including myS3Crypt.</p>
-<p>Note also that now rclone has <a href="#connection-strings">connection strings</a>, it is probably easier to use those instead which makes the above example</p>
+<p>Note that you can only set the options of the immediate backend, so
+RCLONE_CONFIG_MYS3CRYPT_ACCESS_KEY_ID has no effect, if myS3Crypt is a
+crypt remote based on an S3 remote. However RCLONE_S3_ACCESS_KEY_ID will
+set the access key of all remotes using S3, including myS3Crypt.</p>
+<p>Note also that now rclone has <a
+href="#connection-strings">connection strings</a>, it is probably easier
+to use those instead which makes the above example</p>
 <pre><code>rclone lsd :s3,access_key_id=XXX,secret_access_key=XXX:</code></pre>
 <h3 id="precedence">Precedence</h3>
-<p>The various different methods of backend configuration are read in this order and the first one with a value is used.</p>
+<p>The various different methods of backend configuration are read in
+this order and the first one with a value is used.</p>
 <ul>
-<li>Parameters in connection strings, e.g. <code>myRemote,skip_links:</code></li>
-<li>Flag values as supplied on the command line, e.g. <code>--skip-links</code></li>
-<li>Remote specific environment vars, e.g. <code>RCLONE_CONFIG_MYREMOTE_SKIP_LINKS</code> (see above).</li>
-<li>Backend-specific environment vars, e.g. <code>RCLONE_LOCAL_SKIP_LINKS</code>.</li>
-<li>Backend generic environment vars, e.g. <code>RCLONE_SKIP_LINKS</code>.</li>
+<li>Parameters in connection strings, e.g.
+<code>myRemote,skip_links:</code></li>
+<li>Flag values as supplied on the command line, e.g.
+<code>--skip-links</code></li>
+<li>Remote specific environment vars, e.g.
+<code>RCLONE_CONFIG_MYREMOTE_SKIP_LINKS</code> (see above).</li>
+<li>Backend-specific environment vars, e.g.
+<code>RCLONE_LOCAL_SKIP_LINKS</code>.</li>
+<li>Backend generic environment vars, e.g.
+<code>RCLONE_SKIP_LINKS</code>.</li>
 <li>Config file, e.g. <code>skip_links = true</code>.</li>
-<li>Default values, e.g. <code>false</code> - these can't be changed.</li>
+<li>Default values, e.g. <code>false</code> - these can't be
+changed.</li>
 </ul>
-<p>So if both <code>--skip-links</code> is supplied on the command line and an environment variable <code>RCLONE_LOCAL_SKIP_LINKS</code> is set, the command line flag will take preference.</p>
-<p>The backend configurations set by environment variables can be seen with the <code>-vv</code> flag, e.g. <code>rclone about myRemote: -vv</code>.</p>
+<p>So if both <code>--skip-links</code> is supplied on the command line
+and an environment variable <code>RCLONE_LOCAL_SKIP_LINKS</code> is set,
+the command line flag will take preference.</p>
+<p>The backend configurations set by environment variables can be seen
+with the <code>-vv</code> flag, e.g.
+<code>rclone about myRemote: -vv</code>.</p>
 <p>For non backend configuration the order is as follows:</p>
 <ul>
-<li>Flag values as supplied on the command line, e.g. <code>--stats 5s</code>.</li>
+<li>Flag values as supplied on the command line, e.g.
+<code>--stats 5s</code>.</li>
 <li>Environment vars, e.g. <code>RCLONE_STATS=5s</code>.</li>
 <li>Default values, e.g. <code>1m</code> - these can't be changed.</li>
 </ul>
 <h3 id="other-environment-variables">Other environment variables</h3>
 <ul>
-<li><code>RCLONE_CONFIG_PASS</code> set to contain your config file password (see <a href="#configuration-encryption">Configuration Encryption</a> section)</li>
-<li><code>HTTP_PROXY</code>, <code>HTTPS_PROXY</code> and <code>NO_PROXY</code> (or the lowercase versions thereof).
+<li><code>RCLONE_CONFIG_PASS</code> set to contain your config file
+password (see <a href="#configuration-encryption">Configuration
+Encryption</a> section)</li>
+<li><code>HTTP_PROXY</code>, <code>HTTPS_PROXY</code> and
+<code>NO_PROXY</code> (or the lowercase versions thereof).
 <ul>
-<li><code>HTTPS_PROXY</code> takes precedence over <code>HTTP_PROXY</code> for https requests.</li>
-<li>The environment values may be either a complete URL or a "host[:port]" for, in which case the "http" scheme is assumed.</li>
+<li><code>HTTPS_PROXY</code> takes precedence over
+<code>HTTP_PROXY</code> for https requests.</li>
+<li>The environment values may be either a complete URL or a
+"host[:port]" for, in which case the "http" scheme is assumed.</li>
 </ul></li>
-<li><code>USER</code> and <code>LOGNAME</code> values are used as fallbacks for current username. The primary method for looking up username is OS-specific: Windows API on Windows, real user ID in /etc/passwd on Unix systems. In the documentation the current username is simply referred to as <code>$USER</code>.</li>
-<li><code>RCLONE_CONFIG_DIR</code> - rclone <strong>sets</strong> this variable for use in config files and sub processes to point to the directory holding the config file.</li>
+<li><code>USER</code> and <code>LOGNAME</code> values are used as
+fallbacks for current username. The primary method for looking up
+username is OS-specific: Windows API on Windows, real user ID in
+/etc/passwd on Unix systems. In the documentation the current username
+is simply referred to as <code>$USER</code>.</li>
+<li><code>RCLONE_CONFIG_DIR</code> - rclone <strong>sets</strong> this
+variable for use in config files and sub processes to point to the
+directory holding the config file.</li>
 </ul>
-<p>The options set by environment variables can be seen with the <code>-vv</code> and <code>--log-level=DEBUG</code> flags, e.g. <code>rclone version -vv</code>.</p>
-<h1 id="configuring-rclone-on-a-remote-headless-machine">Configuring rclone on a remote / headless machine</h1>
-<p>Some of the configurations (those involving oauth2) require an Internet connected web browser.</p>
-<p>If you are trying to set rclone up on a remote or headless box with no browser available on it (e.g. a NAS or a server in a datacenter) then you will need to use an alternative means of configuration. There are two ways of doing it, described below.</p>
-<h2 id="configuring-using-rclone-authorize">Configuring using rclone authorize</h2>
-<p>On the headless box run <code>rclone</code> config but answer <code>N</code> to the <code>Use auto config?</code> question.</p>
+<p>The options set by environment variables can be seen with the
+<code>-vv</code> and <code>--log-level=DEBUG</code> flags, e.g.
+<code>rclone version -vv</code>.</p>
+<h1 id="configuring-rclone-on-a-remote-headless-machine">Configuring
+rclone on a remote / headless machine</h1>
+<p>Some of the configurations (those involving oauth2) require an
+Internet connected web browser.</p>
+<p>If you are trying to set rclone up on a remote or headless box with
+no browser available on it (e.g. a NAS or a server in a datacenter) then
+you will need to use an alternative means of configuration. There are
+two ways of doing it, described below.</p>
+<h2 id="configuring-using-rclone-authorize">Configuring using rclone
+authorize</h2>
+<p>On the headless box run <code>rclone</code> config but answer
+<code>N</code> to the <code>Use auto config?</code> question.</p>
 <pre><code>Use auto config?
  * Say Y if not sure
  * Say N if you are working on a remote or headless machine
@@ -7980,20 +14133,27 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt;</code></pre>
-<h2 id="configuring-by-copying-the-config-file">Configuring by copying the config file</h2>
-<p>Rclone stores all of its config in a single configuration file. This can easily be copied to configure a remote rclone.</p>
+<h2 id="configuring-by-copying-the-config-file">Configuring by copying
+the config file</h2>
+<p>Rclone stores all of its config in a single configuration file. This
+can easily be copied to configure a remote rclone.</p>
 <p>So first configure rclone on your desktop machine with</p>
 <pre><code>rclone config</code></pre>
 <p>to set up the config file.</p>
-<p>Find the config file by running <code>rclone config file</code>, for example</p>
+<p>Find the config file by running <code>rclone config file</code>, for
+example</p>
 <pre><code>$ rclone config file
 Configuration file is stored at:
 /home/user/.rclone.conf</code></pre>
-<p>Now transfer it to the remote box (scp, cut paste, ftp, sftp, etc.) and place it in the correct place (use <code>rclone config file</code> on the remote box to find out where).</p>
+<p>Now transfer it to the remote box (scp, cut paste, ftp, sftp, etc.)
+and place it in the correct place (use <code>rclone config file</code>
+on the remote box to find out where).</p>
 <h2 id="configuring-using-ssh-tunnel">Configuring using SSH Tunnel</h2>
-<p>Linux and MacOS users can utilize SSH Tunnel to redirect the headless box port 53682 to local machine by using the following command:</p>
+<p>Linux and MacOS users can utilize SSH Tunnel to redirect the headless
+box port 53682 to local machine by using the following command:</p>
 <pre><code>ssh -L localhost:53682:localhost:53682 username@remote_server</code></pre>
-<p>Then on the headless box run <code>rclone config</code> and answer <code>Y</code> to the <code>Use auto config?</code> question.</p>
+<p>Then on the headless box run <code>rclone config</code> and answer
+<code>Y</code> to the <code>Use auto config?</code> question.</p>
 <pre><code>Use auto config?
  * Say Y if not sure
  * Say N if you are working on a remote or headless machine
@@ -8001,18 +14161,39 @@ Configuration file is stored at:
 y) Yes (default)
 n) No
 y/n&gt; y</code></pre>
-<p>Then copy and paste the auth url <code>http://127.0.0.1:53682/auth?state=xxxxxxxxxxxx</code> to the browser on your local machine, complete the auth and it is done.</p>
-<h1 id="filtering-includes-and-excludes">Filtering, includes and excludes</h1>
-<p>Filter flags determine which files rclone <code>sync</code>, <code>move</code>, <code>ls</code>, <code>lsl</code>, <code>md5sum</code>, <code>sha1sum</code>, <code>size</code>, <code>delete</code>, <code>check</code> and similar commands apply to.</p>
-<p>They are specified in terms of path/file name patterns; path/file lists; file age and size, or presence of a file in a directory. Bucket based remotes without the concept of directory apply filters to object key, age and size in an analogous way.</p>
+<p>Then copy and paste the auth url
+<code>http://127.0.0.1:53682/auth?state=xxxxxxxxxxxx</code> to the
+browser on your local machine, complete the auth and it is done.</p>
+<h1 id="filtering-includes-and-excludes">Filtering, includes and
+excludes</h1>
+<p>Filter flags determine which files rclone <code>sync</code>,
+<code>move</code>, <code>ls</code>, <code>lsl</code>,
+<code>md5sum</code>, <code>sha1sum</code>, <code>size</code>,
+<code>delete</code>, <code>check</code> and similar commands apply
+to.</p>
+<p>They are specified in terms of path/file name patterns; path/file
+lists; file age and size, or presence of a file in a directory. Bucket
+based remotes without the concept of directory apply filters to object
+key, age and size in an analogous way.</p>
 <p>Rclone <code>purge</code> does not obey filters.</p>
-<p>To test filters without risk of damage to data, apply them to <code>rclone ls</code>, or with the <code>--dry-run</code> and <code>-vv</code> flags.</p>
-<p>Rclone filter patterns can only be used in filter command line options, not in the specification of a remote.</p>
-<p>E.g. <code>rclone copy "remote:dir*.jpg" /path/to/dir</code> does not have a filter effect. <code>rclone copy remote:dir /path/to/dir --include "*.jpg"</code> does.</p>
-<p><strong>Important</strong> Avoid mixing any two of <code>--include...</code>, <code>--exclude...</code> or <code>--filter...</code> flags in an rclone command. The results might not be what you expect. Instead use a <code>--filter...</code> flag.</p>
-<h2 id="patterns-for-matching-pathfile-names">Patterns for matching path/file names</h2>
+<p>To test filters without risk of damage to data, apply them to
+<code>rclone ls</code>, or with the <code>--dry-run</code> and
+<code>-vv</code> flags.</p>
+<p>Rclone filter patterns can only be used in filter command line
+options, not in the specification of a remote.</p>
+<p>E.g. <code>rclone copy "remote:dir*.jpg" /path/to/dir</code> does not
+have a filter effect.
+<code>rclone copy remote:dir /path/to/dir --include "*.jpg"</code>
+does.</p>
+<p><strong>Important</strong> Avoid mixing any two of
+<code>--include...</code>, <code>--exclude...</code> or
+<code>--filter...</code> flags in an rclone command. The results might
+not be what you expect. Instead use a <code>--filter...</code> flag.</p>
+<h2 id="patterns-for-matching-pathfile-names">Patterns for matching
+path/file names</h2>
 <h3 id="patterns">Pattern syntax</h3>
-<p>Here is a formal definition of the pattern syntax, <a href="#examples">examples</a> are below.</p>
+<p>Here is a formal definition of the pattern syntax, <a
+href="#examples">examples</a> are below.</p>
 <p>Rclone matching rules follow a glob style:</p>
 <pre><code>*         matches any sequence of non-separator (/) characters
 **        matches any sequence of characters including / separators
@@ -8032,13 +14213,22 @@ lo - hi   matches character c for lo &lt;= c &lt;= hi</code></pre>
 <p>pattern-list:</p>
 <pre><code>pattern { , pattern }
           comma-separated (without spaces) patterns</code></pre>
-<p>character classes (see <a href="https://golang.org/pkg/regexp/syntax/">Go regular expression reference</a>) include:</p>
+<p>character classes (see <a
+href="https://golang.org/pkg/regexp/syntax/">Go regular expression
+reference</a>) include:</p>
 <pre><code>Named character classes (e.g. [\d], [^\d], [\D], [^\D])
 Perl character classes (e.g. \s, \S, \w, \W)
 ASCII character classes (e.g. [[:alnum:]], [[:alpha:]], [[:punct:]], [[:xdigit:]])</code></pre>
-<p>regexp for advanced users to insert a regular expression - see <a href="#regexp">below</a> for more info:</p>
+<p>regexp for advanced users to insert a regular expression - see <a
+href="#regexp">below</a> for more info:</p>
 <pre><code>Any re2 regular expression not containing `}}`</code></pre>
-<p>If the filter pattern starts with a <code>/</code> then it only matches at the top level of the directory tree, <strong>relative to the root of the remote</strong> (not necessarily the root of the drive). If it does not start with <code>/</code> then it is matched starting at the <strong>end of the path/file name</strong> but it only matches a complete path element - it must match from a <code>/</code> separator or the beginning of the path/file.</p>
+<p>If the filter pattern starts with a <code>/</code> then it only
+matches at the top level of the directory tree, <strong>relative to the
+root of the remote</strong> (not necessarily the root of the drive). If
+it does not start with <code>/</code> then it is matched starting at the
+<strong>end of the path/file name</strong> but it only matches a
+complete path element - it must match from a <code>/</code> separator or
+the beginning of the path/file.</p>
 <pre><code>file.jpg   - matches &quot;file.jpg&quot;
            - matches &quot;directory/file.jpg&quot;
            - doesn&#39;t match &quot;afile.jpg&quot;
@@ -8046,7 +14236,8 @@ ASCII character classes (e.g. [[:alnum:]], [[:alpha:]], [[:punct:]], [[:xdigit:]
 /file.jpg  - matches &quot;file.jpg&quot; in the root directory of the remote
            - doesn&#39;t match &quot;afile.jpg&quot;
            - doesn&#39;t match &quot;directory/file.jpg&quot;</code></pre>
-<p>The top level of the remote might not be the top level of the drive.</p>
+<p>The top level of the remote might not be the top level of the
+drive.</p>
 <p>E.g. for a Microsoft Windows local directory structure</p>
 <pre><code>F:
 ├── bkp
@@ -8056,10 +14247,16 @@ ASCII character classes (e.g. [[:alnum:]], [[:alpha:]], [[:punct:]], [[:xdigit:]
 │   │   └── 456.jpg
 │   ├── incl
 │   │   └── document.pdf</code></pre>
-<p>To copy the contents of folder <code>data</code> into folder <code>bkp</code> excluding the contents of subfolder <code>excl</code>the following command treats <code>F:\data</code> and <code>F:\bkp</code> as top level for filtering.</p>
+<p>To copy the contents of folder <code>data</code> into folder
+<code>bkp</code> excluding the contents of subfolder
+<code>excl</code>the following command treats <code>F:\data</code> and
+<code>F:\bkp</code> as top level for filtering.</p>
 <p><code>rclone copy F:\data\ F:\bkp\ --exclude=/excl/**</code></p>
-<p><strong>Important</strong> Use <code>/</code> in path/file name patterns and not <code>\</code> even if running on Microsoft Windows.</p>
-<p>Simple patterns are case sensitive unless the <code>--ignore-case</code> flag is used.</p>
+<p><strong>Important</strong> Use <code>/</code> in path/file name
+patterns and not <code>\</code> even if running on Microsoft
+Windows.</p>
+<p>Simple patterns are case sensitive unless the
+<code>--ignore-case</code> flag is used.</p>
 <p>Without <code>--ignore-case</code> (default)</p>
 <pre><code>potato - matches &quot;potato&quot;
        - doesn&#39;t match &quot;POTATO&quot;</code></pre>
@@ -8067,23 +14264,49 @@ ASCII character classes (e.g. [[:alnum:]], [[:alpha:]], [[:punct:]], [[:xdigit:]
 <pre><code>potato - matches &quot;potato&quot;
        - matches &quot;POTATO&quot;</code></pre>
 <h2 id="regexp">Using regular expressions in filter patterns</h2>
-<p>The syntax of filter patterns is glob style matching (like <code>bash</code> uses) to make things easy for users. However this does not provide absolute control over the matching, so for advanced users rclone also provides a regular expression syntax.</p>
-<p>The regular expressions used are as defined in the <a href="https://golang.org/pkg/regexp/syntax/">Go regular expression reference</a>. Regular expressions should be enclosed in <code>{{</code> <code>}}</code>. They will match only the last path segment if the glob doesn't start with <code>/</code> or the whole path name if it does. Note that rclone does not attempt to parse the supplied regular expression, meaning that using any regular expression filter will prevent rclone from using <a href="#directory_filter">directory filter rules</a>, as it will instead check every path against the supplied regular expression(s).</p>
-<p>Here is how the <code>{{regexp}}</code> is transformed into an full regular expression to match the entire path:</p>
+<p>The syntax of filter patterns is glob style matching (like
+<code>bash</code> uses) to make things easy for users. However this does
+not provide absolute control over the matching, so for advanced users
+rclone also provides a regular expression syntax.</p>
+<p>The regular expressions used are as defined in the <a
+href="https://golang.org/pkg/regexp/syntax/">Go regular expression
+reference</a>. Regular expressions should be enclosed in <code>{{</code>
+<code>}}</code>. They will match only the last path segment if the glob
+doesn't start with <code>/</code> or the whole path name if it does.
+Note that rclone does not attempt to parse the supplied regular
+expression, meaning that using any regular expression filter will
+prevent rclone from using <a href="#directory_filter">directory filter
+rules</a>, as it will instead check every path against the supplied
+regular expression(s).</p>
+<p>Here is how the <code>{{regexp}}</code> is transformed into an full
+regular expression to match the entire path:</p>
 <pre><code>{{regexp}}  becomes (^|/)(regexp)$
 /{{regexp}} becomes ^(regexp)$</code></pre>
 <p>Regexp syntax can be mixed with glob syntax, for example</p>
 <pre><code>*.{{jpe?g}} to match file.jpg, file.jpeg but not file.png</code></pre>
-<p>You can also use regexp flags - to set case insensitive, for example</p>
+<p>You can also use regexp flags - to set case insensitive, for
+example</p>
 <pre><code>*.{{(?i)jpg}} to match file.jpg, file.JPG but not file.png</code></pre>
-<p>Be careful with wildcards in regular expressions - you don't want them to match path separators normally. To match any file name starting with <code>start</code> and ending with <code>end</code> write</p>
+<p>Be careful with wildcards in regular expressions - you don't want
+them to match path separators normally. To match any file name starting
+with <code>start</code> and ending with <code>end</code> write</p>
 <pre><code>{{start[^/]*end\.jpg}}</code></pre>
 <p>Not</p>
 <pre><code>{{start.*end\.jpg}}</code></pre>
-<p>Which will match a directory called <code>start</code> with a file called <code>end.jpg</code> in it as the <code>.*</code> will match <code>/</code> characters.</p>
-<p>Note that you can use <code>-vv --dump filters</code> to show the filter patterns in regexp format - rclone implements the glob patterns by transforming them into regular expressions.</p>
+<p>Which will match a directory called <code>start</code> with a file
+called <code>end.jpg</code> in it as the <code>.*</code> will match
+<code>/</code> characters.</p>
+<p>Note that you can use <code>-vv --dump filters</code> to show the
+filter patterns in regexp format - rclone implements the glob patterns
+by transforming them into regular expressions.</p>
 <h2 id="examples">Filter pattern examples</h2>
 <table>
+<colgroup>
+<col style="width: 27%" />
+<col style="width: 20%" />
+<col style="width: 17%" />
+<col style="width: 35%" />
+</colgroup>
 <thead>
 <tr class="header">
 <th>Description</th>
@@ -8215,8 +14438,10 @@ ASCII character classes (e.g. [[:alnum:]], [[:alpha:]], [[:punct:]], [[:xdigit:]
 </tr>
 </tbody>
 </table>
-<h2 id="how-filter-rules-work">How filter rules are applied to files</h2>
-<p>Rclone path/file name filters are made up of one or more of the following flags:</p>
+<h2 id="how-filter-rules-work">How filter rules are applied to
+files</h2>
+<p>Rclone path/file name filters are made up of one or more of the
+following flags:</p>
 <ul>
 <li><code>--include</code></li>
 <li><code>--include-from</code></li>
@@ -8226,104 +14451,266 @@ ASCII character classes (e.g. [[:alnum:]], [[:alpha:]], [[:punct:]], [[:xdigit:]
 <li><code>--filter-from</code></li>
 </ul>
 <p>There can be more than one instance of individual flags.</p>
-<p>Rclone internally uses a combined list of all the include and exclude rules. The order in which rules are processed can influence the result of the filter.</p>
-<p>All flags of the same type are processed together in the order above, regardless of what order the different types of flags are included on the command line.</p>
-<p>Multiple instances of the same flag are processed from left to right according to their position in the command line.</p>
-<p>To mix up the order of processing includes and excludes use <code>--filter...</code> flags.</p>
-<p>Within <code>--include-from</code>, <code>--exclude-from</code> and <code>--filter-from</code> flags rules are processed from top to bottom of the referenced file.</p>
-<p>If there is an <code>--include</code> or <code>--include-from</code> flag specified, rclone implies a <code>- **</code> rule which it adds to the bottom of the internal rule list. Specifying a <code>+</code> rule with a <code>--filter...</code> flag does not imply that rule.</p>
-<p>Each path/file name passed through rclone is matched against the combined filter list. At first match to a rule the path/file name is included or excluded and no further filter rules are processed for that path/file.</p>
-<p>If rclone does not find a match, after testing against all rules (including the implied rule if appropriate), the path/file name is included.</p>
-<p>Any path/file included at that stage is processed by the rclone command.</p>
-<p><code>--files-from</code> and <code>--files-from-raw</code> flags over-ride and cannot be combined with other filter options.</p>
-<p>To see the internal combined rule list, in regular expression form, for a command add the <code>--dump filters</code> flag. Running an rclone command with <code>--dump filters</code> and <code>-vv</code> flags lists the internal filter elements and shows how they are applied to each source path/file. There is not currently a means provided to pass regular expression filter options into rclone directly though character class filter rules contain character classes. <a href="https://golang.org/pkg/regexp/syntax/">Go regular expression reference</a></p>
-<h3 id="directory_filter">How filter rules are applied to directories</h3>
-<p>Rclone commands are applied to path/file names not directories. The entire contents of a directory can be matched to a filter by the pattern <code>directory/*</code> or recursively by <code>directory/**</code>.</p>
-<p>Directory filter rules are defined with a closing <code>/</code> separator.</p>
-<p>E.g. <code>/directory/subdirectory/</code> is an rclone directory filter rule.</p>
-<p>Rclone commands can use directory filter rules to determine whether they recurse into subdirectories. This potentially optimises access to a remote by avoiding listing unnecessary directories. Whether optimisation is desirable depends on the specific filter rules and source remote content.</p>
-<p>If any <a href="#regexp">regular expression filters</a> are in use, then no directory recursion optimisation is possible, as rclone must check every path against the supplied regular expression(s).</p>
+<p>Rclone internally uses a combined list of all the include and exclude
+rules. The order in which rules are processed can influence the result
+of the filter.</p>
+<p>All flags of the same type are processed together in the order above,
+regardless of what order the different types of flags are included on
+the command line.</p>
+<p>Multiple instances of the same flag are processed from left to right
+according to their position in the command line.</p>
+<p>To mix up the order of processing includes and excludes use
+<code>--filter...</code> flags.</p>
+<p>Within <code>--include-from</code>, <code>--exclude-from</code> and
+<code>--filter-from</code> flags rules are processed from top to bottom
+of the referenced file.</p>
+<p>If there is an <code>--include</code> or <code>--include-from</code>
+flag specified, rclone implies a <code>- **</code> rule which it adds to
+the bottom of the internal rule list. Specifying a <code>+</code> rule
+with a <code>--filter...</code> flag does not imply that rule.</p>
+<p>Each path/file name passed through rclone is matched against the
+combined filter list. At first match to a rule the path/file name is
+included or excluded and no further filter rules are processed for that
+path/file.</p>
+<p>If rclone does not find a match, after testing against all rules
+(including the implied rule if appropriate), the path/file name is
+included.</p>
+<p>Any path/file included at that stage is processed by the rclone
+command.</p>
+<p><code>--files-from</code> and <code>--files-from-raw</code> flags
+over-ride and cannot be combined with other filter options.</p>
+<p>To see the internal combined rule list, in regular expression form,
+for a command add the <code>--dump filters</code> flag. Running an
+rclone command with <code>--dump filters</code> and <code>-vv</code>
+flags lists the internal filter elements and shows how they are applied
+to each source path/file. There is not currently a means provided to
+pass regular expression filter options into rclone directly though
+character class filter rules contain character classes. <a
+href="https://golang.org/pkg/regexp/syntax/">Go regular expression
+reference</a></p>
+<h3 id="directory_filter">How filter rules are applied to
+directories</h3>
+<p>Rclone commands are applied to path/file names not directories. The
+entire contents of a directory can be matched to a filter by the pattern
+<code>directory/*</code> or recursively by
+<code>directory/**</code>.</p>
+<p>Directory filter rules are defined with a closing <code>/</code>
+separator.</p>
+<p>E.g. <code>/directory/subdirectory/</code> is an rclone directory
+filter rule.</p>
+<p>Rclone commands can use directory filter rules to determine whether
+they recurse into subdirectories. This potentially optimises access to a
+remote by avoiding listing unnecessary directories. Whether optimisation
+is desirable depends on the specific filter rules and source remote
+content.</p>
+<p>If any <a href="#regexp">regular expression filters</a> are in use,
+then no directory recursion optimisation is possible, as rclone must
+check every path against the supplied regular expression(s).</p>
 <p>Directory recursion optimisation occurs if either:</p>
 <ul>
-<li><p>A source remote does not support the rclone <code>ListR</code> primitive. local, sftp, Microsoft OneDrive and WebDAV do not support <code>ListR</code>. Google Drive and most bucket type storage do. <a href="https://rclone.org/overview/#optional-features">Full list</a></p></li>
-<li><p>On other remotes (those that support <code>ListR</code>), if the rclone command is not naturally recursive, and provided it is not run with the <code>--fast-list</code> flag. <code>ls</code>, <code>lsf -R</code> and <code>size</code> are naturally recursive but <code>sync</code>, <code>copy</code> and <code>move</code> are not.</p></li>
-<li><p>Whenever the <code>--disable ListR</code> flag is applied to an rclone command.</p></li>
+<li><p>A source remote does not support the rclone <code>ListR</code>
+primitive. local, sftp, Microsoft OneDrive and WebDAV do not support
+<code>ListR</code>. Google Drive and most bucket type storage do. <a
+href="https://rclone.org/overview/#optional-features">Full
+list</a></p></li>
+<li><p>On other remotes (those that support <code>ListR</code>), if the
+rclone command is not naturally recursive, and provided it is not run
+with the <code>--fast-list</code> flag. <code>ls</code>,
+<code>lsf -R</code> and <code>size</code> are naturally recursive but
+<code>sync</code>, <code>copy</code> and <code>move</code> are
+not.</p></li>
+<li><p>Whenever the <code>--disable ListR</code> flag is applied to an
+rclone command.</p></li>
 </ul>
-<p>Rclone commands imply directory filter rules from path/file filter rules. To view the directory filter rules rclone has implied for a command specify the <code>--dump filters</code> flag.</p>
+<p>Rclone commands imply directory filter rules from path/file filter
+rules. To view the directory filter rules rclone has implied for a
+command specify the <code>--dump filters</code> flag.</p>
 <p>E.g. for an include rule</p>
 <pre><code>/a/*.jpg</code></pre>
 <p>Rclone implies the directory include rule</p>
 <pre><code>/a/</code></pre>
-<p>Directory filter rules specified in an rclone command can limit the scope of an rclone command but path/file filters still have to be specified.</p>
-<p>E.g. <code>rclone ls remote: --include /directory/</code> will not match any files. Because it is an <code>--include</code> option the <code>--exclude **</code> rule is implied, and the <code>/directory/</code> pattern serves only to optimise access to the remote by ignoring everything outside of that directory.</p>
-<p>E.g. <code>rclone ls remote: --filter-from filter-list.txt</code> with a file <code>filter-list.txt</code>:</p>
+<p>Directory filter rules specified in an rclone command can limit the
+scope of an rclone command but path/file filters still have to be
+specified.</p>
+<p>E.g. <code>rclone ls remote: --include /directory/</code> will not
+match any files. Because it is an <code>--include</code> option the
+<code>--exclude **</code> rule is implied, and the
+<code>/directory/</code> pattern serves only to optimise access to the
+remote by ignoring everything outside of that directory.</p>
+<p>E.g. <code>rclone ls remote: --filter-from filter-list.txt</code>
+with a file <code>filter-list.txt</code>:</p>
 <pre><code>- /dir1/
 - /dir2/
 + *.pdf
 - **</code></pre>
-<p>All files in directories <code>dir1</code> or <code>dir2</code> or their subdirectories are completely excluded from the listing. Only files of suffix <code>pdf</code> in the root of <code>remote:</code> or its subdirectories are listed. The <code>- **</code> rule prevents listing of any path/files not previously matched by the rules above.</p>
-<p>Option <code>exclude-if-present</code> creates a directory exclude rule based on the presence of a file in a directory and takes precedence over other rclone directory filter rules.</p>
-<p>When using pattern list syntax, if a pattern item contains either <code>/</code> or <code>**</code>, then rclone will not able to imply a directory filter rule from this pattern list.</p>
+<p>All files in directories <code>dir1</code> or <code>dir2</code> or
+their subdirectories are completely excluded from the listing. Only
+files of suffix <code>pdf</code> in the root of <code>remote:</code> or
+its subdirectories are listed. The <code>- **</code> rule prevents
+listing of any path/files not previously matched by the rules above.</p>
+<p>Option <code>exclude-if-present</code> creates a directory exclude
+rule based on the presence of a file in a directory and takes precedence
+over other rclone directory filter rules.</p>
+<p>When using pattern list syntax, if a pattern item contains either
+<code>/</code> or <code>**</code>, then rclone will not able to imply a
+directory filter rule from this pattern list.</p>
 <p>E.g. for an include rule</p>
 <pre><code>{dir1/**,dir2/**}</code></pre>
-<p>Rclone will match files below directories <code>dir1</code> or <code>dir2</code> only, but will not be able to use this filter to exclude a directory <code>dir3</code> from being traversed.</p>
-<p>Directory recursion optimisation may affect performance, but normally not the result. One exception to this is sync operations with option <code>--create-empty-src-dirs</code>, where any traversed empty directories will be created. With the pattern list example <code>{dir1/**,dir2/**}</code> above, this would create an empty directory <code>dir3</code> on destination (when it exists on source). Changing the filter to <code>{dir1,dir2}/**</code>, or splitting it into two include rules <code>--include dir1/** --include dir2/**</code>, will match the same files while also filtering directories, with the result that an empty directory <code>dir3</code> will no longer be created.</p>
-<h3 id="exclude---exclude-files-matching-pattern"><code>--exclude</code> - Exclude files matching pattern</h3>
-<p>Excludes path/file names from an rclone command based on a single exclude rule.</p>
-<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
-<p><code>--exclude</code> should not be used with <code>--include</code>, <code>--include-from</code>, <code>--filter</code> or <code>--filter-from</code> flags.</p>
-<p><code>--exclude</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
-<p>E.g. <code>rclone ls remote: --exclude *.bak</code> excludes all .bak files from listing.</p>
-<p>E.g. <code>rclone size remote: --exclude "/dir/**"</code> returns the total size of all files on <code>remote:</code> excluding those in root directory <code>dir</code> and sub directories.</p>
-<p>E.g. on Microsoft Windows <code>rclone ls remote: --exclude "*\[{JP,KR,HK}\]*"</code> lists the files in <code>remote:</code> without <code>[JP]</code> or <code>[KR]</code> or <code>[HK]</code> in their name. Quotes prevent the shell from interpreting the <code>\</code> characters.<code>\</code> characters escape the <code>[</code> and <code>]</code> so an rclone filter treats them literally rather than as a character-range. The <code>{</code> and <code>}</code> define an rclone pattern list. For other operating systems single quotes are required ie <code>rclone ls remote: --exclude '*\[{JP,KR,HK}\]*'</code></p>
-<h3 id="exclude-from---read-exclude-patterns-from-file"><code>--exclude-from</code> - Read exclude patterns from file</h3>
-<p>Excludes path/file names from an rclone command based on rules in a named file. The file contains a list of remarks and pattern rules.</p>
+<p>Rclone will match files below directories <code>dir1</code> or
+<code>dir2</code> only, but will not be able to use this filter to
+exclude a directory <code>dir3</code> from being traversed.</p>
+<p>Directory recursion optimisation may affect performance, but normally
+not the result. One exception to this is sync operations with option
+<code>--create-empty-src-dirs</code>, where any traversed empty
+directories will be created. With the pattern list example
+<code>{dir1/**,dir2/**}</code> above, this would create an empty
+directory <code>dir3</code> on destination (when it exists on source).
+Changing the filter to <code>{dir1,dir2}/**</code>, or splitting it into
+two include rules <code>--include dir1/** --include dir2/**</code>, will
+match the same files while also filtering directories, with the result
+that an empty directory <code>dir3</code> will no longer be created.</p>
+<h3 id="exclude---exclude-files-matching-pattern"><code>--exclude</code>
+- Exclude files matching pattern</h3>
+<p>Excludes path/file names from an rclone command based on a single
+exclude rule.</p>
+<p>This flag can be repeated. See above for the order filter flags are
+processed in.</p>
+<p><code>--exclude</code> should not be used with
+<code>--include</code>, <code>--include-from</code>,
+<code>--filter</code> or <code>--filter-from</code> flags.</p>
+<p><code>--exclude</code> has no effect when combined with
+<code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
+<p>E.g. <code>rclone ls remote: --exclude *.bak</code> excludes all .bak
+files from listing.</p>
+<p>E.g. <code>rclone size remote: --exclude "/dir/**"</code> returns the
+total size of all files on <code>remote:</code> excluding those in root
+directory <code>dir</code> and sub directories.</p>
+<p>E.g. on Microsoft Windows
+<code>rclone ls remote: --exclude "*\[{JP,KR,HK}\]*"</code> lists the
+files in <code>remote:</code> without <code>[JP]</code> or
+<code>[KR]</code> or <code>[HK]</code> in their name. Quotes prevent the
+shell from interpreting the <code>\</code> characters.<code>\</code>
+characters escape the <code>[</code> and <code>]</code> so an rclone
+filter treats them literally rather than as a character-range. The
+<code>{</code> and <code>}</code> define an rclone pattern list. For
+other operating systems single quotes are required ie
+<code>rclone ls remote: --exclude '*\[{JP,KR,HK}\]*'</code></p>
+<h3
+id="exclude-from---read-exclude-patterns-from-file"><code>--exclude-from</code>
+- Read exclude patterns from file</h3>
+<p>Excludes path/file names from an rclone command based on rules in a
+named file. The file contains a list of remarks and pattern rules.</p>
 <p>For an example <code>exclude-file.txt</code>:</p>
 <pre><code># a sample exclude rule file
 *.bak
 file2.jpg</code></pre>
-<p><code>rclone ls remote: --exclude-from exclude-file.txt</code> lists the files on <code>remote:</code> except those named <code>file2.jpg</code> or with a suffix <code>.bak</code>. That is equivalent to <code>rclone ls remote: --exclude file2.jpg --exclude "*.bak"</code>.</p>
-<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
-<p>The <code>--exclude-from</code> flag is useful where multiple exclude filter rules are applied to an rclone command.</p>
-<p><code>--exclude-from</code> should not be used with <code>--include</code>, <code>--include-from</code>, <code>--filter</code> or <code>--filter-from</code> flags.</p>
-<p><code>--exclude-from</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
-<p><code>--exclude-from</code> followed by <code>-</code> reads filter rules from standard input.</p>
-<h3 id="include---include-files-matching-pattern"><code>--include</code> - Include files matching pattern</h3>
-<p>Adds a single include rule based on path/file names to an rclone command.</p>
-<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
-<p><code>--include</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
-<p><code>--include</code> implies <code>--exclude **</code> at the end of an rclone internal filter list. Therefore if you mix <code>--include</code> and <code>--include-from</code> flags with <code>--exclude</code>, <code>--exclude-from</code>, <code>--filter</code> or <code>--filter-from</code>, you must use include rules for all the files you want in the include statement. For more flexibility use the <code>--filter-from</code> flag.</p>
-<p>E.g. <code>rclone ls remote: --include "*.{png,jpg}"</code> lists the files on <code>remote:</code> with suffix <code>.png</code> and <code>.jpg</code>. All other files are excluded.</p>
-<p>E.g. multiple rclone copy commands can be combined with <code>--include</code> and a pattern-list.</p>
+<p><code>rclone ls remote: --exclude-from exclude-file.txt</code> lists
+the files on <code>remote:</code> except those named
+<code>file2.jpg</code> or with a suffix <code>.bak</code>. That is
+equivalent to
+<code>rclone ls remote: --exclude file2.jpg --exclude "*.bak"</code>.</p>
+<p>This flag can be repeated. See above for the order filter flags are
+processed in.</p>
+<p>The <code>--exclude-from</code> flag is useful where multiple exclude
+filter rules are applied to an rclone command.</p>
+<p><code>--exclude-from</code> should not be used with
+<code>--include</code>, <code>--include-from</code>,
+<code>--filter</code> or <code>--filter-from</code> flags.</p>
+<p><code>--exclude-from</code> has no effect when combined with
+<code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
+<p><code>--exclude-from</code> followed by <code>-</code> reads filter
+rules from standard input.</p>
+<h3 id="include---include-files-matching-pattern"><code>--include</code>
+- Include files matching pattern</h3>
+<p>Adds a single include rule based on path/file names to an rclone
+command.</p>
+<p>This flag can be repeated. See above for the order filter flags are
+processed in.</p>
+<p><code>--include</code> has no effect when combined with
+<code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
+<p><code>--include</code> implies <code>--exclude **</code> at the end
+of an rclone internal filter list. Therefore if you mix
+<code>--include</code> and <code>--include-from</code> flags with
+<code>--exclude</code>, <code>--exclude-from</code>,
+<code>--filter</code> or <code>--filter-from</code>, you must use
+include rules for all the files you want in the include statement. For
+more flexibility use the <code>--filter-from</code> flag.</p>
+<p>E.g. <code>rclone ls remote: --include "*.{png,jpg}"</code> lists the
+files on <code>remote:</code> with suffix <code>.png</code> and
+<code>.jpg</code>. All other files are excluded.</p>
+<p>E.g. multiple rclone copy commands can be combined with
+<code>--include</code> and a pattern-list.</p>
 <pre><code>rclone copy /vol1/A remote:A
 rclone copy /vol1/B remote:B</code></pre>
 <p>is equivalent to:</p>
 <pre><code>rclone copy /vol1 remote: --include &quot;{A,B}/**&quot;</code></pre>
-<p>E.g. <code>rclone ls remote:/wheat --include "??[^[:punct:]]*"</code> lists the files <code>remote:</code> directory <code>wheat</code> (and subdirectories) whose third character is not punctuation. This example uses an <a href="https://golang.org/pkg/regexp/syntax/">ASCII character class</a>.</p>
-<h3 id="include-from---read-include-patterns-from-file"><code>--include-from</code> - Read include patterns from file</h3>
-<p>Adds path/file names to an rclone command based on rules in a named file. The file contains a list of remarks and pattern rules.</p>
+<p>E.g. <code>rclone ls remote:/wheat --include "??[^[:punct:]]*"</code>
+lists the files <code>remote:</code> directory <code>wheat</code> (and
+subdirectories) whose third character is not punctuation. This example
+uses an <a href="https://golang.org/pkg/regexp/syntax/">ASCII character
+class</a>.</p>
+<h3
+id="include-from---read-include-patterns-from-file"><code>--include-from</code>
+- Read include patterns from file</h3>
+<p>Adds path/file names to an rclone command based on rules in a named
+file. The file contains a list of remarks and pattern rules.</p>
 <p>For an example <code>include-file.txt</code>:</p>
 <pre><code># a sample include rule file
 *.jpg
 file2.avi</code></pre>
-<p><code>rclone ls remote: --include-from include-file.txt</code> lists the files on <code>remote:</code> with name <code>file2.avi</code> or suffix <code>.jpg</code>. That is equivalent to <code>rclone ls remote: --include file2.avi --include "*.jpg"</code>.</p>
-<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
-<p>The <code>--include-from</code> flag is useful where multiple include filter rules are applied to an rclone command.</p>
-<p><code>--include-from</code> implies <code>--exclude **</code> at the end of an rclone internal filter list. Therefore if you mix <code>--include</code> and <code>--include-from</code> flags with <code>--exclude</code>, <code>--exclude-from</code>, <code>--filter</code> or <code>--filter-from</code>, you must use include rules for all the files you want in the include statement. For more flexibility use the <code>--filter-from</code> flag.</p>
-<p><code>--exclude-from</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
-<p><code>--exclude-from</code> followed by <code>-</code> reads filter rules from standard input.</p>
-<h3 id="filter---add-a-file-filtering-rule"><code>--filter</code> - Add a file-filtering rule</h3>
-<p>Specifies path/file names to an rclone command, based on a single include or exclude rule, in <code>+</code> or <code>-</code> format.</p>
-<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
-<p><code>--filter +</code> differs from <code>--include</code>. In the case of <code>--include</code> rclone implies an <code>--exclude *</code> rule which it adds to the bottom of the internal rule list. <code>--filter...+</code> does not imply that rule.</p>
-<p><code>--filter</code> has no effect when combined with <code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
-<p><code>--filter</code> should not be used with <code>--include</code>, <code>--include-from</code>, <code>--exclude</code> or <code>--exclude-from</code> flags.</p>
-<p>E.g. <code>rclone ls remote: --filter "- *.bak"</code> excludes all <code>.bak</code> files from a list of <code>remote:</code>.</p>
-<h3 id="filter-from---read-filtering-patterns-from-a-file"><code>--filter-from</code> - Read filtering patterns from a file</h3>
-<p>Adds path/file names to an rclone command based on rules in a named file. The file contains a list of remarks and pattern rules. Include rules start with <code>+</code> and exclude rules with <code>-</code>. <code>!</code> clears existing rules. Rules are processed in the order they are defined.</p>
-<p>This flag can be repeated. See above for the order filter flags are processed in.</p>
-<p>Arrange the order of filter rules with the most restrictive first and work down.</p>
-<p>Lines starting with # or ; are ignored, and can be used to write comments. Inline comments are not supported. <em>Use <code>-vv --dump filters</code> to see how they appear in the final regexp.</em></p>
+<p><code>rclone ls remote: --include-from include-file.txt</code> lists
+the files on <code>remote:</code> with name <code>file2.avi</code> or
+suffix <code>.jpg</code>. That is equivalent to
+<code>rclone ls remote: --include file2.avi --include "*.jpg"</code>.</p>
+<p>This flag can be repeated. See above for the order filter flags are
+processed in.</p>
+<p>The <code>--include-from</code> flag is useful where multiple include
+filter rules are applied to an rclone command.</p>
+<p><code>--include-from</code> implies <code>--exclude **</code> at the
+end of an rclone internal filter list. Therefore if you mix
+<code>--include</code> and <code>--include-from</code> flags with
+<code>--exclude</code>, <code>--exclude-from</code>,
+<code>--filter</code> or <code>--filter-from</code>, you must use
+include rules for all the files you want in the include statement. For
+more flexibility use the <code>--filter-from</code> flag.</p>
+<p><code>--exclude-from</code> has no effect when combined with
+<code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
+<p><code>--exclude-from</code> followed by <code>-</code> reads filter
+rules from standard input.</p>
+<h3 id="filter---add-a-file-filtering-rule"><code>--filter</code> - Add
+a file-filtering rule</h3>
+<p>Specifies path/file names to an rclone command, based on a single
+include or exclude rule, in <code>+</code> or <code>-</code> format.</p>
+<p>This flag can be repeated. See above for the order filter flags are
+processed in.</p>
+<p><code>--filter +</code> differs from <code>--include</code>. In the
+case of <code>--include</code> rclone implies an
+<code>--exclude *</code> rule which it adds to the bottom of the
+internal rule list. <code>--filter...+</code> does not imply that
+rule.</p>
+<p><code>--filter</code> has no effect when combined with
+<code>--files-from</code> or <code>--files-from-raw</code> flags.</p>
+<p><code>--filter</code> should not be used with <code>--include</code>,
+<code>--include-from</code>, <code>--exclude</code> or
+<code>--exclude-from</code> flags.</p>
+<p>E.g. <code>rclone ls remote: --filter "- *.bak"</code> excludes all
+<code>.bak</code> files from a list of <code>remote:</code>.</p>
+<h3
+id="filter-from---read-filtering-patterns-from-a-file"><code>--filter-from</code>
+- Read filtering patterns from a file</h3>
+<p>Adds path/file names to an rclone command based on rules in a named
+file. The file contains a list of remarks and pattern rules. Include
+rules start with <code>+</code> and exclude rules with <code>-</code>.
+<code>!</code> clears existing rules. Rules are processed in the order
+they are defined.</p>
+<p>This flag can be repeated. See above for the order filter flags are
+processed in.</p>
+<p>Arrange the order of filter rules with the most restrictive first and
+work down.</p>
+<p>Lines starting with # or ; are ignored, and can be used to write
+comments. Inline comments are not supported. <em>Use
+<code>-vv --dump filters</code> to see how they appear in the final
+regexp.</em></p>
 <p>E.g. for <code>filter-file.txt</code>:</p>
 <pre><code># a sample filter rule file
 - secret*.jpg
@@ -8335,42 +14722,80 @@ file2.avi</code></pre>
 + /dir/**
 # exclude everything else
 - *</code></pre>
-<p><code>rclone ls remote: --filter-from filter-file.txt</code> lists the path/files on <code>remote:</code> including all <code>jpg</code> and <code>png</code> files, excluding any matching <code>secret*.jpg</code> and including <code>file2.avi</code>. It also includes everything in the directory <code>dir</code> at the root of <code>remote</code>, except <code>remote:dir/Trash</code> which it excludes. Everything else is excluded.</p>
+<p><code>rclone ls remote: --filter-from filter-file.txt</code> lists
+the path/files on <code>remote:</code> including all <code>jpg</code>
+and <code>png</code> files, excluding any matching
+<code>secret*.jpg</code> and including <code>file2.avi</code>. It also
+includes everything in the directory <code>dir</code> at the root of
+<code>remote</code>, except <code>remote:dir/Trash</code> which it
+excludes. Everything else is excluded.</p>
 <p>E.g. for an alternative <code>filter-file.txt</code>:</p>
 <pre><code>- secret*.jpg
 + *.jpg
 + *.png
 + file2.avi
 - *</code></pre>
-<p>Files <code>file1.jpg</code>, <code>file3.png</code> and <code>file2.avi</code> are listed whilst <code>secret17.jpg</code> and files without the suffix <code>.jpg</code> or <code>.png</code> are excluded.</p>
+<p>Files <code>file1.jpg</code>, <code>file3.png</code> and
+<code>file2.avi</code> are listed whilst <code>secret17.jpg</code> and
+files without the suffix <code>.jpg</code> or <code>.png</code> are
+excluded.</p>
 <p>E.g. for an alternative <code>filter-file.txt</code>:</p>
 <pre><code>+ *.jpg
 + *.gif
 !
 + 42.doc
 - *</code></pre>
-<p>Only file 42.doc is listed. Prior rules are cleared by the <code>!</code>.</p>
-<h3 id="files-from---read-list-of-source-file-names"><code>--files-from</code> - Read list of source-file names</h3>
-<p>Adds path/files to an rclone command from a list in a named file. Rclone processes the path/file names in the order of the list, and no others.</p>
-<p>Other filter flags (<code>--include</code>, <code>--include-from</code>, <code>--exclude</code>, <code>--exclude-from</code>, <code>--filter</code> and <code>--filter-from</code>) are ignored when <code>--files-from</code> is used.</p>
-<p><code>--files-from</code> expects a list of files as its input. Leading or trailing whitespace is stripped from the input lines. Lines starting with <code>#</code> or <code>;</code> are ignored.</p>
-<p>Rclone commands with a <code>--files-from</code> flag traverse the remote, treating the names in <code>--files-from</code> as a set of filters.</p>
-<p>If the <code>--no-traverse</code> and <code>--files-from</code> flags are used together an rclone command does not traverse the remote. Instead it addresses each path/file named in the file individually. For each path/file name, that requires typically 1 API call. This can be efficient for a short <code>--files-from</code> list and a remote containing many files.</p>
-<p>Rclone commands do not error if any names in the <code>--files-from</code> file are missing from the source remote.</p>
-<p>The <code>--files-from</code> flag can be repeated in a single rclone command to read path/file names from more than one file. The files are read from left to right along the command line.</p>
-<p>Paths within the <code>--files-from</code> file are interpreted as starting with the root specified in the rclone command. Leading <code>/</code> separators are ignored. See <a href="#files-from-raw-read-list-of-source-file-names-without-any-processing">--files-from-raw</a> if you need the input to be processed in a raw manner.</p>
+<p>Only file 42.doc is listed. Prior rules are cleared by the
+<code>!</code>.</p>
+<h3
+id="files-from---read-list-of-source-file-names"><code>--files-from</code>
+- Read list of source-file names</h3>
+<p>Adds path/files to an rclone command from a list in a named file.
+Rclone processes the path/file names in the order of the list, and no
+others.</p>
+<p>Other filter flags (<code>--include</code>,
+<code>--include-from</code>, <code>--exclude</code>,
+<code>--exclude-from</code>, <code>--filter</code> and
+<code>--filter-from</code>) are ignored when <code>--files-from</code>
+is used.</p>
+<p><code>--files-from</code> expects a list of files as its input.
+Leading or trailing whitespace is stripped from the input lines. Lines
+starting with <code>#</code> or <code>;</code> are ignored.</p>
+<p>Rclone commands with a <code>--files-from</code> flag traverse the
+remote, treating the names in <code>--files-from</code> as a set of
+filters.</p>
+<p>If the <code>--no-traverse</code> and <code>--files-from</code> flags
+are used together an rclone command does not traverse the remote.
+Instead it addresses each path/file named in the file individually. For
+each path/file name, that requires typically 1 API call. This can be
+efficient for a short <code>--files-from</code> list and a remote
+containing many files.</p>
+<p>Rclone commands do not error if any names in the
+<code>--files-from</code> file are missing from the source remote.</p>
+<p>The <code>--files-from</code> flag can be repeated in a single rclone
+command to read path/file names from more than one file. The files are
+read from left to right along the command line.</p>
+<p>Paths within the <code>--files-from</code> file are interpreted as
+starting with the root specified in the rclone command. Leading
+<code>/</code> separators are ignored. See <a
+href="#files-from-raw-read-list-of-source-file-names-without-any-processing">--files-from-raw</a>
+if you need the input to be processed in a raw manner.</p>
 <p>E.g. for a file <code>files-from.txt</code>:</p>
 <pre><code># comment
 file1.jpg
 subdir/file2.jpg</code></pre>
-<p><code>rclone copy --files-from files-from.txt /home/me/pics remote:pics</code> copies the following, if they exist, and only those files.</p>
+<p><code>rclone copy --files-from files-from.txt /home/me/pics remote:pics</code>
+copies the following, if they exist, and only those files.</p>
 <pre><code>/home/me/pics/file1.jpg        → remote:pics/file1.jpg
 /home/me/pics/subdir/file2.jpg → remote:pics/subdir/file2.jpg</code></pre>
-<p>E.g. to copy the following files referenced by their absolute paths:</p>
+<p>E.g. to copy the following files referenced by their absolute
+paths:</p>
 <pre><code>/home/user1/42
 /home/user1/dir/ford
 /home/user2/prefect</code></pre>
-<p>First find a common subdirectory - in this case <code>/home</code> and put the remaining files in <code>files-from.txt</code> with or without leading <code>/</code>, e.g.</p>
+<p>First find a common subdirectory - in this case <code>/home</code>
+and put the remaining files in <code>files-from.txt</code> with or
+without leading <code>/</code>, e.g.</p>
 <pre><code>user1/42
 user1/dir/ford
 user2/prefect</code></pre>
@@ -8380,129 +14805,226 @@ user2/prefect</code></pre>
 <pre><code>/home/user1/42       → remote:backup/user1/important
 /home/user1/dir/ford → remote:backup/user1/dir/file
 /home/user2/prefect  → remote:backup/user2/stuff</code></pre>
-<p>Alternatively if <code>/</code> is chosen as root <code>files-from.txt</code> will be:</p>
+<p>Alternatively if <code>/</code> is chosen as root
+<code>files-from.txt</code> will be:</p>
 <pre><code>/home/user1/42
 /home/user1/dir/ford
 /home/user2/prefect</code></pre>
 <p>The copy command will be:</p>
 <pre><code>rclone copy --files-from files-from.txt / remote:backup</code></pre>
-<p>Then there will be an extra <code>home</code> directory on the remote:</p>
+<p>Then there will be an extra <code>home</code> directory on the
+remote:</p>
 <pre><code>/home/user1/42       → remote:backup/home/user1/42
 /home/user1/dir/ford → remote:backup/home/user1/dir/ford
 /home/user2/prefect  → remote:backup/home/user2/prefect</code></pre>
-<h3 id="files-from-raw---read-list-of-source-file-names-without-any-processing"><code>--files-from-raw</code> - Read list of source-file names without any processing</h3>
-<p>This flag is the same as <code>--files-from</code> except that input is read in a raw manner. Lines with leading / trailing whitespace, and lines starting with <code>;</code> or <code>#</code> are read without any processing. <a href="https://rclone.org/commands/rclone_lsf/">rclone lsf</a> has a compatible format that can be used to export file lists from remotes for input to <code>--files-from-raw</code>.</p>
-<h3 id="ignore-case---make-searches-case-insensitive"><code>--ignore-case</code> - make searches case insensitive</h3>
-<p>By default, rclone filter patterns are case sensitive. The <code>--ignore-case</code> flag makes all of the filters patterns on the command line case insensitive.</p>
-<p>E.g. <code>--include "zaphod.txt"</code> does not match a file <code>Zaphod.txt</code>. With <code>--ignore-case</code> a match is made.</p>
+<h3
+id="files-from-raw---read-list-of-source-file-names-without-any-processing"><code>--files-from-raw</code>
+- Read list of source-file names without any processing</h3>
+<p>This flag is the same as <code>--files-from</code> except that input
+is read in a raw manner. Lines with leading / trailing whitespace, and
+lines starting with <code>;</code> or <code>#</code> are read without
+any processing. <a href="https://rclone.org/commands/rclone_lsf/">rclone
+lsf</a> has a compatible format that can be used to export file lists
+from remotes for input to <code>--files-from-raw</code>.</p>
+<h3
+id="ignore-case---make-searches-case-insensitive"><code>--ignore-case</code>
+- make searches case insensitive</h3>
+<p>By default, rclone filter patterns are case sensitive. The
+<code>--ignore-case</code> flag makes all of the filters patterns on the
+command line case insensitive.</p>
+<p>E.g. <code>--include "zaphod.txt"</code> does not match a file
+<code>Zaphod.txt</code>. With <code>--ignore-case</code> a match is
+made.</p>
 <h2 id="quoting-shell-metacharacters">Quoting shell metacharacters</h2>
-<p>Rclone commands with filter patterns containing shell metacharacters may not as work as expected in your shell and may require quoting.</p>
+<p>Rclone commands with filter patterns containing shell metacharacters
+may not as work as expected in your shell and may require quoting.</p>
 <p>E.g. linux, OSX (<code>*</code> metacharacter)</p>
 <ul>
 <li><code>--include \*.jpg</code></li>
 <li><code>--include '*.jpg'</code></li>
 <li><code>--include='*.jpg'</code></li>
 </ul>
-<p>Microsoft Windows expansion is done by the command, not shell, so <code>--include *.jpg</code> does not require quoting.</p>
-<p>If the rclone error <code>Command .... needs .... arguments maximum: you provided .... non flag arguments:</code> is encountered, the cause is commonly spaces within the name of a remote or flag value. The fix then is to quote values containing spaces.</p>
+<p>Microsoft Windows expansion is done by the command, not shell, so
+<code>--include *.jpg</code> does not require quoting.</p>
+<p>If the rclone error
+<code>Command .... needs .... arguments maximum: you provided .... non flag arguments:</code>
+is encountered, the cause is commonly spaces within the name of a remote
+or flag value. The fix then is to quote values containing spaces.</p>
 <h2 id="other-filters">Other filters</h2>
-<h3 id="min-size---dont-transfer-any-file-smaller-than-this"><code>--min-size</code> - Don't transfer any file smaller than this</h3>
-<p>Controls the minimum size file within the scope of an rclone command. Default units are <code>KiB</code> but abbreviations <code>B</code>, <code>K</code>, <code>M</code>, <code>G</code>, <code>T</code> or <code>P</code> are valid.</p>
-<p>E.g. <code>rclone ls remote: --min-size 50k</code> lists files on <code>remote:</code> of 50 KiB size or larger.</p>
-<p>See <a href="https://rclone.org/docs/#size-option">the size option docs</a> for more info.</p>
-<h3 id="max-size---dont-transfer-any-file-larger-than-this"><code>--max-size</code> - Don't transfer any file larger than this</h3>
-<p>Controls the maximum size file within the scope of an rclone command. Default units are <code>KiB</code> but abbreviations <code>B</code>, <code>K</code>, <code>M</code>, <code>G</code>, <code>T</code> or <code>P</code> are valid.</p>
-<p>E.g. <code>rclone ls remote: --max-size 1G</code> lists files on <code>remote:</code> of 1 GiB size or smaller.</p>
-<p>See <a href="https://rclone.org/docs/#size-option">the size option docs</a> for more info.</p>
-<h3 id="max-age---dont-transfer-any-file-older-than-this"><code>--max-age</code> - Don't transfer any file older than this</h3>
-<p>Controls the maximum age of files within the scope of an rclone command.</p>
-<p><code>--max-age</code> applies only to files and not to directories.</p>
-<p>E.g. <code>rclone ls remote: --max-age 2d</code> lists files on <code>remote:</code> of 2 days old or less.</p>
-<p>See <a href="https://rclone.org/docs/#time-option">the time option docs</a> for valid formats.</p>
-<h3 id="min-age---dont-transfer-any-file-younger-than-this"><code>--min-age</code> - Don't transfer any file younger than this</h3>
-<p>Controls the minimum age of files within the scope of an rclone command. (see <code>--max-age</code> for valid formats)</p>
-<p><code>--min-age</code> applies only to files and not to directories.</p>
-<p>E.g. <code>rclone ls remote: --min-age 2d</code> lists files on <code>remote:</code> of 2 days old or more.</p>
-<p>See <a href="https://rclone.org/docs/#time-option">the time option docs</a> for valid formats.</p>
+<h3
+id="min-size---dont-transfer-any-file-smaller-than-this"><code>--min-size</code>
+- Don't transfer any file smaller than this</h3>
+<p>Controls the minimum size file within the scope of an rclone command.
+Default units are <code>KiB</code> but abbreviations <code>B</code>,
+<code>K</code>, <code>M</code>, <code>G</code>, <code>T</code> or
+<code>P</code> are valid.</p>
+<p>E.g. <code>rclone ls remote: --min-size 50k</code> lists files on
+<code>remote:</code> of 50 KiB size or larger.</p>
+<p>See <a href="https://rclone.org/docs/#size-option">the size option
+docs</a> for more info.</p>
+<h3
+id="max-size---dont-transfer-any-file-larger-than-this"><code>--max-size</code>
+- Don't transfer any file larger than this</h3>
+<p>Controls the maximum size file within the scope of an rclone command.
+Default units are <code>KiB</code> but abbreviations <code>B</code>,
+<code>K</code>, <code>M</code>, <code>G</code>, <code>T</code> or
+<code>P</code> are valid.</p>
+<p>E.g. <code>rclone ls remote: --max-size 1G</code> lists files on
+<code>remote:</code> of 1 GiB size or smaller.</p>
+<p>See <a href="https://rclone.org/docs/#size-option">the size option
+docs</a> for more info.</p>
+<h3
+id="max-age---dont-transfer-any-file-older-than-this"><code>--max-age</code>
+- Don't transfer any file older than this</h3>
+<p>Controls the maximum age of files within the scope of an rclone
+command.</p>
+<p><code>--max-age</code> applies only to files and not to
+directories.</p>
+<p>E.g. <code>rclone ls remote: --max-age 2d</code> lists files on
+<code>remote:</code> of 2 days old or less.</p>
+<p>See <a href="https://rclone.org/docs/#time-option">the time option
+docs</a> for valid formats.</p>
+<h3
+id="min-age---dont-transfer-any-file-younger-than-this"><code>--min-age</code>
+- Don't transfer any file younger than this</h3>
+<p>Controls the minimum age of files within the scope of an rclone
+command. (see <code>--max-age</code> for valid formats)</p>
+<p><code>--min-age</code> applies only to files and not to
+directories.</p>
+<p>E.g. <code>rclone ls remote: --min-age 2d</code> lists files on
+<code>remote:</code> of 2 days old or more.</p>
+<p>See <a href="https://rclone.org/docs/#time-option">the time option
+docs</a> for valid formats.</p>
 <h2 id="other-flags">Other flags</h2>
-<h3 id="delete-excluded---delete-files-on-dest-excluded-from-sync"><code>--delete-excluded</code> - Delete files on dest excluded from sync</h3>
-<p><strong>Important</strong> this flag is dangerous to your data - use with <code>--dry-run</code> and <code>-v</code> first.</p>
-<p>In conjunction with <code>rclone sync</code>, <code>--delete-excluded</code> deletes any files on the destination which are excluded from the command.</p>
-<p>E.g. the scope of <code>rclone sync --interactive A: B:</code> can be restricted:</p>
+<h3
+id="delete-excluded---delete-files-on-dest-excluded-from-sync"><code>--delete-excluded</code>
+- Delete files on dest excluded from sync</h3>
+<p><strong>Important</strong> this flag is dangerous to your data - use
+with <code>--dry-run</code> and <code>-v</code> first.</p>
+<p>In conjunction with <code>rclone sync</code>,
+<code>--delete-excluded</code> deletes any files on the destination
+which are excluded from the command.</p>
+<p>E.g. the scope of <code>rclone sync --interactive A: B:</code> can be
+restricted:</p>
 <pre><code>rclone --min-size 50k --delete-excluded sync A: B:</code></pre>
-<p>All files on <code>B:</code> which are less than 50 KiB are deleted because they are excluded from the rclone sync command.</p>
-<h3 id="dump-filters---dump-the-filters-to-the-output"><code>--dump filters</code> - dump the filters to the output</h3>
-<p>Dumps the defined filters to standard output in regular expression format.</p>
+<p>All files on <code>B:</code> which are less than 50 KiB are deleted
+because they are excluded from the rclone sync command.</p>
+<h3
+id="dump-filters---dump-the-filters-to-the-output"><code>--dump filters</code>
+- dump the filters to the output</h3>
+<p>Dumps the defined filters to standard output in regular expression
+format.</p>
 <p>Useful for debugging.</p>
-<h2 id="exclude-directory-based-on-a-file">Exclude directory based on a file</h2>
-<p>The <code>--exclude-if-present</code> flag controls whether a directory is within the scope of an rclone command based on the presence of a named file within it. The flag can be repeated to check for multiple file names, presence of any of them will exclude the directory.</p>
+<h2 id="exclude-directory-based-on-a-file">Exclude directory based on a
+file</h2>
+<p>The <code>--exclude-if-present</code> flag controls whether a
+directory is within the scope of an rclone command based on the presence
+of a named file within it. The flag can be repeated to check for
+multiple file names, presence of any of them will exclude the
+directory.</p>
 <p>This flag has a priority over other filter flags.</p>
 <p>E.g. for the following directory structure:</p>
 <pre><code>dir1/file1
 dir1/dir2/file2
 dir1/dir2/dir3/file3
 dir1/dir2/dir3/.ignore</code></pre>
-<p>The command <code>rclone ls --exclude-if-present .ignore dir1</code> does not list <code>dir3</code>, <code>file3</code> or <code>.ignore</code>.</p>
+<p>The command <code>rclone ls --exclude-if-present .ignore dir1</code>
+does not list <code>dir3</code>, <code>file3</code> or
+<code>.ignore</code>.</p>
 <h2 id="metadata">Metadata filters</h2>
-<p>The metadata filters work in a very similar way to the normal file name filters, except they match <a href="https://rclone.org/docs/#metadata">metadata</a> on the object.</p>
-<p>The metadata should be specified as <code>key=value</code> patterns. This may be wildcarded using the normal <a href="#patterns">filter patterns</a> or <a href="#regexp">regular expressions</a>.</p>
-<p>For example if you wished to list only local files with a mode of <code>100664</code> you could do that with:</p>
+<p>The metadata filters work in a very similar way to the normal file
+name filters, except they match <a
+href="https://rclone.org/docs/#metadata">metadata</a> on the object.</p>
+<p>The metadata should be specified as <code>key=value</code> patterns.
+This may be wildcarded using the normal <a href="#patterns">filter
+patterns</a> or <a href="#regexp">regular expressions</a>.</p>
+<p>For example if you wished to list only local files with a mode of
+<code>100664</code> you could do that with:</p>
 <pre><code>rclone lsf -M --files-only --metadata-include &quot;mode=100664&quot; .</code></pre>
-<p>Or if you wished to show files with an <code>atime</code>, <code>mtime</code> or <code>btime</code> at a given date:</p>
+<p>Or if you wished to show files with an <code>atime</code>,
+<code>mtime</code> or <code>btime</code> at a given date:</p>
 <pre><code>rclone lsf -M --files-only --metadata-include &quot;[abm]time=2022-12-16*&quot; .</code></pre>
-<p>Like file filtering, metadata filtering only applies to files not to directories.</p>
+<p>Like file filtering, metadata filtering only applies to files not to
+directories.</p>
 <p>The filters can be applied using these flags.</p>
 <ul>
-<li><code>--metadata-include</code> - Include metadatas matching pattern</li>
-<li><code>--metadata-include-from</code> - Read metadata include patterns from file (use - to read from stdin)</li>
-<li><code>--metadata-exclude</code> - Exclude metadatas matching pattern</li>
-<li><code>--metadata-exclude-from</code> - Read metadata exclude patterns from file (use - to read from stdin)</li>
+<li><code>--metadata-include</code> - Include metadatas matching
+pattern</li>
+<li><code>--metadata-include-from</code> - Read metadata include
+patterns from file (use - to read from stdin)</li>
+<li><code>--metadata-exclude</code> - Exclude metadatas matching
+pattern</li>
+<li><code>--metadata-exclude-from</code> - Read metadata exclude
+patterns from file (use - to read from stdin)</li>
 <li><code>--metadata-filter</code> - Add a metadata filtering rule</li>
-<li><code>--metadata-filter-from</code> - Read metadata filtering patterns from a file (use - to read from stdin)</li>
+<li><code>--metadata-filter-from</code> - Read metadata filtering
+patterns from a file (use - to read from stdin)</li>
 </ul>
-<p>Each flag can be repeated. See the section on <a href="#how-filter-rules-work">how filter rules are applied</a> for more details - these flags work in an identical way to the file name filtering flags, but instead of file name patterns have metadata patterns.</p>
+<p>Each flag can be repeated. See the section on <a
+href="#how-filter-rules-work">how filter rules are applied</a> for more
+details - these flags work in an identical way to the file name
+filtering flags, but instead of file name patterns have metadata
+patterns.</p>
 <h2 id="common-pitfalls">Common pitfalls</h2>
-<p>The most frequent filter support issues on the <a href="https://forum.rclone.org/">rclone forum</a> are:</p>
+<p>The most frequent filter support issues on the <a
+href="https://forum.rclone.org/">rclone forum</a> are:</p>
 <ul>
 <li>Not using paths relative to the root of the remote</li>
 <li>Not using <code>/</code> to match from the root of a remote</li>
 <li>Not using <code>**</code> to match the contents of a directory</li>
 </ul>
 <h1 id="gui-experimental">GUI (Experimental)</h1>
-<p>Rclone can serve a web based GUI (graphical user interface). This is somewhat experimental at the moment so things may be subject to change.</p>
-<p>Run this command in a terminal and rclone will download and then display the GUI in a web browser.</p>
+<p>Rclone can serve a web based GUI (graphical user interface). This is
+somewhat experimental at the moment so things may be subject to
+change.</p>
+<p>Run this command in a terminal and rclone will download and then
+display the GUI in a web browser.</p>
 <pre><code>rclone rcd --rc-web-gui</code></pre>
-<p>This will produce logs like this and rclone needs to continue to run to serve the GUI:</p>
+<p>This will produce logs like this and rclone needs to continue to run
+to serve the GUI:</p>
 <pre><code>2019/08/25 11:40:14 NOTICE: A new release for gui is present at https://github.com/rclone/rclone-webui-react/releases/download/v0.0.6/currentbuild.zip
 2019/08/25 11:40:14 NOTICE: Downloading webgui binary. Please wait. [Size: 3813937, Path :  /home/USER/.cache/rclone/webgui/v0.0.6.zip]
 2019/08/25 11:40:16 NOTICE: Unzipping
 2019/08/25 11:40:16 NOTICE: Serving remote control on http://127.0.0.1:5572/</code></pre>
-<p>This assumes you are running rclone locally on your machine. It is possible to separate the rclone and the GUI - see below for details.</p>
-<p>If you wish to check for updates then you can add <code>--rc-web-gui-update</code> to the command line.</p>
-<p>If you find your GUI broken, you may force it to update by add <code>--rc-web-gui-force-update</code>.</p>
-<p>By default, rclone will open your browser. Add <code>--rc-web-gui-no-open-browser</code> to disable this feature.</p>
+<p>This assumes you are running rclone locally on your machine. It is
+possible to separate the rclone and the GUI - see below for details.</p>
+<p>If you wish to check for updates then you can add
+<code>--rc-web-gui-update</code> to the command line.</p>
+<p>If you find your GUI broken, you may force it to update by add
+<code>--rc-web-gui-force-update</code>.</p>
+<p>By default, rclone will open your browser. Add
+<code>--rc-web-gui-no-open-browser</code> to disable this feature.</p>
 <h2 id="using-the-gui">Using the GUI</h2>
-<p>Once the GUI opens, you will be looking at the dashboard which has an overall overview.</p>
-<p>On the left hand side you will see a series of view buttons you can click on:</p>
+<p>Once the GUI opens, you will be looking at the dashboard which has an
+overall overview.</p>
+<p>On the left hand side you will see a series of view buttons you can
+click on:</p>
 <ul>
 <li>Dashboard - main overview</li>
 <li>Configs - examine and create new configurations</li>
-<li>Explorer - view, download and upload files to the cloud storage systems</li>
+<li>Explorer - view, download and upload files to the cloud storage
+systems</li>
 <li>Backend - view or alter the backend config</li>
 <li>Log out</li>
 </ul>
 <p>(More docs and walkthrough video to come!)</p>
 <h2 id="how-it-works">How it works</h2>
-<p>When you run the <code>rclone rcd --rc-web-gui</code> this is what happens</p>
+<p>When you run the <code>rclone rcd --rc-web-gui</code> this is what
+happens</p>
 <ul>
 <li>Rclone starts but only runs the remote control API ("rc").</li>
-<li>The API is bound to localhost with an auto-generated username and password.</li>
+<li>The API is bound to localhost with an auto-generated username and
+password.</li>
 <li>If the API bundle is missing then rclone will download it.</li>
-<li>rclone will start serving the files from the API bundle over the same port as the API</li>
-<li>rclone will open the browser with a <code>login_token</code> so it can log straight in.</li>
+<li>rclone will start serving the files from the API bundle over the
+same port as the API</li>
+<li>rclone will open the browser with a <code>login_token</code> so it
+can log straight in.</li>
 </ul>
 <h2 id="advanced-use">Advanced use</h2>
-<p>The <code>rclone rcd</code> may use any of the <a href="https://rclone.org/rc/#supported-parameters">flags documented on the rc page</a>.</p>
+<p>The <code>rclone rcd</code> may use any of the <a
+href="https://rclone.org/rc/#supported-parameters">flags documented on
+the rc page</a>.</p>
 <p>The flag <code>--rc-web-gui</code> is shorthand for</p>
 <ul>
 <li>Download the web GUI if necessary</li>
@@ -8512,9 +15034,11 @@ dir1/dir2/dir3/.ignore</code></pre>
 <li><code>--rc-serve</code></li>
 </ul>
 <p>These flags can be overridden as desired.</p>
-<p>See also the <a href="https://rclone.org/commands/rclone_rcd/">rclone rcd documentation</a>.</p>
+<p>See also the <a href="https://rclone.org/commands/rclone_rcd/">rclone
+rcd documentation</a>.</p>
 <h3 id="example-running-a-public-gui">Example: Running a public GUI</h3>
-<p>For example the GUI could be served on a public port over SSL using an htpasswd file using the following flags:</p>
+<p>For example the GUI could be served on a public port over SSL using
+an htpasswd file using the following flags:</p>
 <ul>
 <li><code>--rc-web-gui</code></li>
 <li><code>--rc-addr :443</code></li>
@@ -8522,31 +15046,43 @@ dir1/dir2/dir3/.ignore</code></pre>
 <li><code>--rc-cert /path/to/ssl.crt</code></li>
 <li><code>--rc-key /path/to/ssl.key</code></li>
 </ul>
-<h3 id="example-running-a-gui-behind-a-proxy">Example: Running a GUI behind a proxy</h3>
-<p>If you want to run the GUI behind a proxy at <code>/rclone</code> you could use these flags:</p>
+<h3 id="example-running-a-gui-behind-a-proxy">Example: Running a GUI
+behind a proxy</h3>
+<p>If you want to run the GUI behind a proxy at <code>/rclone</code> you
+could use these flags:</p>
 <ul>
 <li><code>--rc-web-gui</code></li>
 <li><code>--rc-baseurl rclone</code></li>
 <li><code>--rc-htpasswd /path/to/htpasswd</code></li>
 </ul>
-<p>Or instead of htpasswd if you just want a single user and password:</p>
+<p>Or instead of htpasswd if you just want a single user and
+password:</p>
 <ul>
 <li><code>--rc-user me</code></li>
 <li><code>--rc-pass mypassword</code></li>
 </ul>
 <h2 id="project">Project</h2>
-<p>The GUI is being developed in the: <a href="https://github.com/rclone/rclone-webui-react">rclone/rclone-webui-react repository</a>.</p>
+<p>The GUI is being developed in the: <a
+href="https://github.com/rclone/rclone-webui-react">rclone/rclone-webui-react
+repository</a>.</p>
 <p>Bug reports and contributions are very welcome :-)</p>
-<p>If you have questions then please ask them on the <a href="https://forum.rclone.org/">rclone forum</a>.</p>
-<h1 id="remote-controlling-rclone-with-its-api">Remote controlling rclone with its API</h1>
-<p>If rclone is run with the <code>--rc</code> flag then it starts an HTTP server which can be used to remote control rclone using its API.</p>
-<p>You can either use the <a href="#api-rc">rc</a> command to access the API or <a href="#api-http">use HTTP directly</a>.</p>
-<p>If you just want to run a remote control then see the <a href="https://rclone.org/commands/rclone_rcd/">rcd</a> command.</p>
+<p>If you have questions then please ask them on the <a
+href="https://forum.rclone.org/">rclone forum</a>.</p>
+<h1 id="remote-controlling-rclone-with-its-api">Remote controlling
+rclone with its API</h1>
+<p>If rclone is run with the <code>--rc</code> flag then it starts an
+HTTP server which can be used to remote control rclone using its
+API.</p>
+<p>You can either use the <a href="#api-rc">rc</a> command to access the
+API or <a href="#api-http">use HTTP directly</a>.</p>
+<p>If you just want to run a remote control then see the <a
+href="https://rclone.org/commands/rclone_rcd/">rcd</a> command.</p>
 <h2 id="supported-parameters">Supported parameters</h2>
 <h3 id="rc">--rc</h3>
 <p>Flag to start the http server listen on remote requests</p>
 <h3 id="rc-addrip">--rc-addr=IP</h3>
-<p>IPaddress:Port or :Port to bind server to. (default "localhost:5572")</p>
+<p>IPaddress:Port or :Port to bind server to. (default
+"localhost:5572")</p>
 <h3 id="rc-certkey">--rc-cert=KEY</h3>
 <p>SSL PEM key (concatenation of certificate and CA certificate)</p>
 <h3 id="rc-client-capath">--rc-client-ca=PATH</h3>
@@ -8558,74 +15094,107 @@ dir1/dir2/dir3/.ignore</code></pre>
 <h3 id="rc-max-header-bytesvalue">--rc-max-header-bytes=VALUE</h3>
 <p>Maximum size of request header (default 4096)</p>
 <h3 id="rc-min-tls-versionvalue">--rc-min-tls-version=VALUE</h3>
-<p>The minimum TLS version that is acceptable. Valid values are "tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
+<p>The minimum TLS version that is acceptable. Valid values are
+"tls1.0", "tls1.1", "tls1.2" and "tls1.3" (default "tls1.0").</p>
 <h3 id="rc-uservalue">--rc-user=VALUE</h3>
 <p>User name for authentication.</p>
 <h3 id="rc-passvalue">--rc-pass=VALUE</h3>
 <p>Password for authentication.</p>
 <h3 id="rc-realmvalue">--rc-realm=VALUE</h3>
 <p>Realm for authentication (default "rclone")</p>
-<h3 id="rc-server-read-timeoutduration">--rc-server-read-timeout=DURATION</h3>
+<h3
+id="rc-server-read-timeoutduration">--rc-server-read-timeout=DURATION</h3>
 <p>Timeout for server reading data (default 1h0m0s)</p>
-<h3 id="rc-server-write-timeoutduration">--rc-server-write-timeout=DURATION</h3>
+<h3
+id="rc-server-write-timeoutduration">--rc-server-write-timeout=DURATION</h3>
 <p>Timeout for server writing data (default 1h0m0s)</p>
 <h3 id="rc-serve">--rc-serve</h3>
-<p>Enable the serving of remote objects via the HTTP interface. This means objects will be accessible at http://127.0.0.1:5572/ by default, so you can browse to http://127.0.0.1:5572/ or http://127.0.0.1:5572/* to see a listing of the remotes. Objects may be requested from remotes using this syntax http://127.0.0.1:5572/[remote:path]/path/to/object</p>
+<p>Enable the serving of remote objects via the HTTP interface. This
+means objects will be accessible at http://127.0.0.1:5572/ by default,
+so you can browse to http://127.0.0.1:5572/ or http://127.0.0.1:5572/*
+to see a listing of the remotes. Objects may be requested from remotes
+using this syntax http://127.0.0.1:5572/[remote:path]/path/to/object</p>
 <p>Default Off.</p>
 <h3 id="rc-serve-no-modtime">--rc-serve-no-modtime</h3>
-<p>Set this flag to skip reading the modification time (can speed things up).</p>
+<p>Set this flag to skip reading the modification time (can speed things
+up).</p>
 <p>Default Off.</p>
 <h3 id="rc-files-pathtodirectory">--rc-files /path/to/directory</h3>
 <p>Path to local files to serve on the HTTP server.</p>
-<p>If this is set then rclone will serve the files in that directory. It will also open the root in the web browser if specified. This is for implementing browser based GUIs for rclone functions.</p>
-<p>If <code>--rc-user</code> or <code>--rc-pass</code> is set then the URL that is opened will have the authorization in the URL in the <code>http://user:pass@localhost/</code> style.</p>
+<p>If this is set then rclone will serve the files in that directory. It
+will also open the root in the web browser if specified. This is for
+implementing browser based GUIs for rclone functions.</p>
+<p>If <code>--rc-user</code> or <code>--rc-pass</code> is set then the
+URL that is opened will have the authorization in the URL in the
+<code>http://user:pass@localhost/</code> style.</p>
 <p>Default Off.</p>
 <h3 id="rc-enable-metrics">--rc-enable-metrics</h3>
-<p>Enable OpenMetrics/Prometheus compatible endpoint at <code>/metrics</code>. If more control over the metrics is desired (for example running it on a different port or with different auth) then endpoint can be enabled with the <code>--metrics-*</code> flags instead.</p>
+<p>Enable OpenMetrics/Prometheus compatible endpoint at
+<code>/metrics</code>. If more control over the metrics is desired (for
+example running it on a different port or with different auth) then
+endpoint can be enabled with the <code>--metrics-*</code> flags
+instead.</p>
 <p>Default Off.</p>
 <h3 id="rc-web-gui">--rc-web-gui</h3>
-<p>Set this flag to serve the default web gui on the same port as rclone.</p>
+<p>Set this flag to serve the default web gui on the same port as
+rclone.</p>
 <p>Default Off.</p>
 <h3 id="rc-allow-origin">--rc-allow-origin</h3>
 <p>Set the allowed Access-Control-Allow-Origin for rc requests.</p>
-<p>Can be used with --rc-web-gui if the rclone is running on different IP than the web-gui.</p>
+<p>Can be used with --rc-web-gui if the rclone is running on different
+IP than the web-gui.</p>
 <p>Default is IP address on which rc is running.</p>
 <h3 id="rc-web-fetch-url">--rc-web-fetch-url</h3>
 <p>Set the URL to fetch the rclone-web-gui files from.</p>
-<p>Default https://api.github.com/repos/rclone/rclone-webui-react/releases/latest.</p>
+<p>Default
+https://api.github.com/repos/rclone/rclone-webui-react/releases/latest.</p>
 <h3 id="rc-web-gui-update">--rc-web-gui-update</h3>
-<p>Set this flag to check and update rclone-webui-react from the rc-web-fetch-url.</p>
+<p>Set this flag to check and update rclone-webui-react from the
+rc-web-fetch-url.</p>
 <p>Default Off.</p>
 <h3 id="rc-web-gui-force-update">--rc-web-gui-force-update</h3>
-<p>Set this flag to force update rclone-webui-react from the rc-web-fetch-url.</p>
+<p>Set this flag to force update rclone-webui-react from the
+rc-web-fetch-url.</p>
 <p>Default Off.</p>
 <h3 id="rc-web-gui-no-open-browser">--rc-web-gui-no-open-browser</h3>
-<p>Set this flag to disable opening browser automatically when using web-gui.</p>
+<p>Set this flag to disable opening browser automatically when using
+web-gui.</p>
 <p>Default Off.</p>
-<h3 id="rc-job-expire-durationduration">--rc-job-expire-duration=DURATION</h3>
+<h3
+id="rc-job-expire-durationduration">--rc-job-expire-duration=DURATION</h3>
 <p>Expire finished async jobs older than DURATION (default 60s).</p>
-<h3 id="rc-job-expire-intervalduration">--rc-job-expire-interval=DURATION</h3>
+<h3
+id="rc-job-expire-intervalduration">--rc-job-expire-interval=DURATION</h3>
 <p>Interval duration to check for expired async jobs (default 10s).</p>
 <h3 id="rc-no-auth">--rc-no-auth</h3>
-<p>By default rclone will require authorisation to have been set up on the rc interface in order to use any methods which access any rclone remotes. Eg <code>operations/list</code> is denied as it involved creating a remote as is <code>sync/copy</code>.</p>
-<p>If this is set then no authorisation will be required on the server to use these methods. The alternative is to use <code>--rc-user</code> and <code>--rc-pass</code> and use these credentials in the request.</p>
+<p>By default rclone will require authorisation to have been set up on
+the rc interface in order to use any methods which access any rclone
+remotes. Eg <code>operations/list</code> is denied as it involved
+creating a remote as is <code>sync/copy</code>.</p>
+<p>If this is set then no authorisation will be required on the server
+to use these methods. The alternative is to use <code>--rc-user</code>
+and <code>--rc-pass</code> and use these credentials in the request.</p>
 <p>Default Off.</p>
 <h3 id="rc-baseurl">--rc-baseurl</h3>
 <p>Prefix for URLs.</p>
 <p>Default is root</p>
 <h3 id="rc-template">--rc-template</h3>
 <p>User-specified template.</p>
-<h2 id="api-rc">Accessing the remote control via the rclone rc command</h2>
-<p>Rclone itself implements the remote control protocol in its <code>rclone rc</code> command.</p>
+<h2 id="api-rc">Accessing the remote control via the rclone rc
+command</h2>
+<p>Rclone itself implements the remote control protocol in its
+<code>rclone rc</code> command.</p>
 <p>You can use it like this</p>
 <pre><code>$ rclone rc rc/noop param1=one param2=two
 {
     &quot;param1&quot;: &quot;one&quot;,
     &quot;param2&quot;: &quot;two&quot;
 }</code></pre>
-<p>Run <code>rclone rc</code> on its own to see the help for the installed remote control commands.</p>
+<p>Run <code>rclone rc</code> on its own to see the help for the
+installed remote control commands.</p>
 <h2 id="json-input">JSON input</h2>
-<p><code>rclone rc</code> also supports a <code>--json</code> flag which can be used to send more complicated input parameters.</p>
+<p><code>rclone rc</code> also supports a <code>--json</code> flag which
+can be used to send more complicated input parameters.</p>
 <pre><code>$ rclone rc --json &#39;{ &quot;p1&quot;: [1,&quot;2&quot;,null,4], &quot;p2&quot;: { &quot;a&quot;:1, &quot;b&quot;:2 } }&#39; rc/noop
 {
     &quot;p1&quot;: [
@@ -8639,22 +15208,39 @@ dir1/dir2/dir3/.ignore</code></pre>
         &quot;b&quot;: 2
     }
 }</code></pre>
-<p>If the parameter being passed is an object then it can be passed as a JSON string rather than using the <code>--json</code> flag which simplifies the command line.</p>
+<p>If the parameter being passed is an object then it can be passed as a
+JSON string rather than using the <code>--json</code> flag which
+simplifies the command line.</p>
 <pre><code>rclone rc operations/list fs=/tmp remote=test opt=&#39;{&quot;showHash&quot;: true}&#39;</code></pre>
 <p>Rather than</p>
 <pre><code>rclone rc operations/list --json &#39;{&quot;fs&quot;: &quot;/tmp&quot;, &quot;remote&quot;: &quot;test&quot;, &quot;opt&quot;: {&quot;showHash&quot;: true}}&#39;</code></pre>
 <h2 id="special-parameters">Special parameters</h2>
-<p>The rc interface supports some special parameters which apply to <strong>all</strong> commands. These start with <code>_</code> to show they are different.</p>
-<h3 id="running-asynchronous-jobs-with-_async-true">Running asynchronous jobs with _async = true</h3>
-<p>Each rc call is classified as a job and it is assigned its own id. By default jobs are executed immediately as they are created or synchronously.</p>
-<p>If <code>_async</code> has a true value when supplied to an rc call then it will return immediately with a job id and the task will be run in the background. The <code>job/status</code> call can be used to get information of the background job. The job can be queried for up to 1 minute after it has finished.</p>
-<p>It is recommended that potentially long running jobs, e.g. <code>sync/sync</code>, <code>sync/copy</code>, <code>sync/move</code>, <code>operations/purge</code> are run with the <code>_async</code> flag to avoid any potential problems with the HTTP request and response timing out.</p>
+<p>The rc interface supports some special parameters which apply to
+<strong>all</strong> commands. These start with <code>_</code> to show
+they are different.</p>
+<h3 id="running-asynchronous-jobs-with-_async-true">Running asynchronous
+jobs with _async = true</h3>
+<p>Each rc call is classified as a job and it is assigned its own id. By
+default jobs are executed immediately as they are created or
+synchronously.</p>
+<p>If <code>_async</code> has a true value when supplied to an rc call
+then it will return immediately with a job id and the task will be run
+in the background. The <code>job/status</code> call can be used to get
+information of the background job. The job can be queried for up to 1
+minute after it has finished.</p>
+<p>It is recommended that potentially long running jobs, e.g.
+<code>sync/sync</code>, <code>sync/copy</code>, <code>sync/move</code>,
+<code>operations/purge</code> are run with the <code>_async</code> flag
+to avoid any potential problems with the HTTP request and response
+timing out.</p>
 <p>Starting a job with the <code>_async</code> flag:</p>
 <pre><code>$ rclone rc --json &#39;{ &quot;p1&quot;: [1,&quot;2&quot;,null,4], &quot;p2&quot;: { &quot;a&quot;:1, &quot;b&quot;:2 }, &quot;_async&quot;: true }&#39; rc/noop
 {
     &quot;jobid&quot;: 2
 }</code></pre>
-<p>Query the status to see if the job has finished. For more information on the meaning of these return parameters see the <code>job/status</code> call.</p>
+<p>Query the status to see if the job has finished. For more information
+on the meaning of these return parameters see the
+<code>job/status</code> call.</p>
 <pre><code>$ rclone rc --json &#39;{ &quot;jobid&quot;:2 }&#39; job/status
 {
     &quot;duration&quot;: 0.000124163,
@@ -8678,60 +15264,112 @@ dir1/dir2/dir3/.ignore</code></pre>
     &quot;startTime&quot;: &quot;2018-10-27T11:38:07.911121728+01:00&quot;,
     &quot;success&quot;: true
 }</code></pre>
-<p><code>job/list</code> can be used to show the running or recently completed jobs</p>
+<p><code>job/list</code> can be used to show the running or recently
+completed jobs</p>
 <pre><code>$ rclone rc job/list
 {
     &quot;jobids&quot;: [
         2
     ]
 }</code></pre>
-<h3 id="setting-config-flags-with-_config">Setting config flags with _config</h3>
-<p>If you wish to set config (the equivalent of the global flags) for the duration of an rc call only then pass in the <code>_config</code> parameter.</p>
-<p>This should be in the same format as the <code>config</code> key returned by <a href="#options-get">options/get</a>.</p>
-<p>For example, if you wished to run a sync with the <code>--checksum</code> parameter, you would pass this parameter in your JSON blob.</p>
+<h3 id="setting-config-flags-with-_config">Setting config flags with
+_config</h3>
+<p>If you wish to set config (the equivalent of the global flags) for
+the duration of an rc call only then pass in the <code>_config</code>
+parameter.</p>
+<p>This should be in the same format as the <code>config</code> key
+returned by <a href="#options-get">options/get</a>.</p>
+<p>For example, if you wished to run a sync with the
+<code>--checksum</code> parameter, you would pass this parameter in your
+JSON blob.</p>
 <pre><code>&quot;_config&quot;:{&quot;CheckSum&quot;: true}</code></pre>
 <p>If using <code>rclone rc</code> this could be passed as</p>
 <pre><code>rclone rc sync/sync ... _config=&#39;{&quot;CheckSum&quot;: true}&#39;</code></pre>
-<p>Any config parameters you don't set will inherit the global defaults which were set with command line flags or environment variables.</p>
-<p>Note that it is possible to set some values as strings or integers - see <a href="#data-types">data types</a> for more info. Here is an example setting the equivalent of <code>--buffer-size</code> in string or integer format.</p>
+<p>Any config parameters you don't set will inherit the global defaults
+which were set with command line flags or environment variables.</p>
+<p>Note that it is possible to set some values as strings or integers -
+see <a href="#data-types">data types</a> for more info. Here is an
+example setting the equivalent of <code>--buffer-size</code> in string
+or integer format.</p>
 <pre><code>&quot;_config&quot;:{&quot;BufferSize&quot;: &quot;42M&quot;}
 &quot;_config&quot;:{&quot;BufferSize&quot;: 44040192}</code></pre>
-<p>If you wish to check the <code>_config</code> assignment has worked properly then calling <code>options/local</code> will show what the value got set to.</p>
-<h3 id="setting-filter-flags-with-_filter">Setting filter flags with _filter</h3>
-<p>If you wish to set filters for the duration of an rc call only then pass in the <code>_filter</code> parameter.</p>
-<p>This should be in the same format as the <code>filter</code> key returned by <a href="#options-get">options/get</a>.</p>
+<p>If you wish to check the <code>_config</code> assignment has worked
+properly then calling <code>options/local</code> will show what the
+value got set to.</p>
+<h3 id="setting-filter-flags-with-_filter">Setting filter flags with
+_filter</h3>
+<p>If you wish to set filters for the duration of an rc call only then
+pass in the <code>_filter</code> parameter.</p>
+<p>This should be in the same format as the <code>filter</code> key
+returned by <a href="#options-get">options/get</a>.</p>
 <p>For example, if you wished to run a sync with these flags</p>
 <pre><code>--max-size 1M --max-age 42s --include &quot;a&quot; --include &quot;b&quot;</code></pre>
 <p>you would pass this parameter in your JSON blob.</p>
 <pre><code>&quot;_filter&quot;:{&quot;MaxSize&quot;:&quot;1M&quot;, &quot;IncludeRule&quot;:[&quot;a&quot;,&quot;b&quot;], &quot;MaxAge&quot;:&quot;42s&quot;}</code></pre>
 <p>If using <code>rclone rc</code> this could be passed as</p>
 <pre><code>rclone rc ... _filter=&#39;{&quot;MaxSize&quot;:&quot;1M&quot;, &quot;IncludeRule&quot;:[&quot;a&quot;,&quot;b&quot;], &quot;MaxAge&quot;:&quot;42s&quot;}&#39;</code></pre>
-<p>Any filter parameters you don't set will inherit the global defaults which were set with command line flags or environment variables.</p>
-<p>Note that it is possible to set some values as strings or integers - see <a href="#data-types">data types</a> for more info. Here is an example setting the equivalent of <code>--buffer-size</code> in string or integer format.</p>
+<p>Any filter parameters you don't set will inherit the global defaults
+which were set with command line flags or environment variables.</p>
+<p>Note that it is possible to set some values as strings or integers -
+see <a href="#data-types">data types</a> for more info. Here is an
+example setting the equivalent of <code>--buffer-size</code> in string
+or integer format.</p>
 <pre><code>&quot;_filter&quot;:{&quot;MinSize&quot;: &quot;42M&quot;}
 &quot;_filter&quot;:{&quot;MinSize&quot;: 44040192}</code></pre>
-<p>If you wish to check the <code>_filter</code> assignment has worked properly then calling <code>options/local</code> will show what the value got set to.</p>
-<h3 id="assigning-operations-to-groups-with-_group-value">Assigning operations to groups with _group = value</h3>
-<p>Each rc call has its own stats group for tracking its metrics. By default grouping is done by the composite group name from prefix <code>job/</code> and id of the job like so <code>job/1</code>.</p>
-<p>If <code>_group</code> has a value then stats for that request will be grouped under that value. This allows caller to group stats under their own name.</p>
-<p>Stats for specific group can be accessed by passing <code>group</code> to <code>core/stats</code>:</p>
+<p>If you wish to check the <code>_filter</code> assignment has worked
+properly then calling <code>options/local</code> will show what the
+value got set to.</p>
+<h3 id="assigning-operations-to-groups-with-_group-value">Assigning
+operations to groups with _group = value</h3>
+<p>Each rc call has its own stats group for tracking its metrics. By
+default grouping is done by the composite group name from prefix
+<code>job/</code> and id of the job like so <code>job/1</code>.</p>
+<p>If <code>_group</code> has a value then stats for that request will
+be grouped under that value. This allows caller to group stats under
+their own name.</p>
+<p>Stats for specific group can be accessed by passing
+<code>group</code> to <code>core/stats</code>:</p>
 <pre><code>$ rclone rc --json &#39;{ &quot;group&quot;: &quot;job/1&quot; }&#39; core/stats
 {
     &quot;speed&quot;: 12345
     ...
 }</code></pre>
 <h2 id="data-types">Data types</h2>
-<p>When the API returns types, these will mostly be straight forward integer, string or boolean types.</p>
-<p>However some of the types returned by the <a href="#options-get">options/get</a> call and taken by the <a href="#options-set">options/set</a> calls as well as the <code>vfsOpt</code>, <code>mountOpt</code> and the <code>_config</code> parameters.</p>
+<p>When the API returns types, these will mostly be straight forward
+integer, string or boolean types.</p>
+<p>However some of the types returned by the <a
+href="#options-get">options/get</a> call and taken by the <a
+href="#options-set">options/set</a> calls as well as the
+<code>vfsOpt</code>, <code>mountOpt</code> and the <code>_config</code>
+parameters.</p>
 <ul>
-<li><code>Duration</code> - these are returned as an integer duration in nanoseconds. They may be set as an integer, or they may be set with time string, eg "5s". See the <a href="https://rclone.org/docs/#options">options section</a> for more info.</li>
-<li><code>Size</code> - these are returned as an integer number of bytes. They may be set as an integer or they may be set with a size suffix string, eg "10M". See the <a href="https://rclone.org/docs/#options">options section</a> for more info.</li>
-<li>Enumerated type (such as <code>CutoffMode</code>, <code>DumpFlags</code>, <code>LogLevel</code>, <code>VfsCacheMode</code> - these will be returned as an integer and may be set as an integer but more conveniently they can be set as a string, eg "HARD" for <code>CutoffMode</code> or <code>DEBUG</code> for <code>LogLevel</code>.</li>
-<li><code>BandwidthSpec</code> - this will be set and returned as a string, eg "1M".</li>
+<li><code>Duration</code> - these are returned as an integer duration in
+nanoseconds. They may be set as an integer, or they may be set with time
+string, eg "5s". See the <a
+href="https://rclone.org/docs/#options">options section</a> for more
+info.</li>
+<li><code>Size</code> - these are returned as an integer number of
+bytes. They may be set as an integer or they may be set with a size
+suffix string, eg "10M". See the <a
+href="https://rclone.org/docs/#options">options section</a> for more
+info.</li>
+<li>Enumerated type (such as <code>CutoffMode</code>,
+<code>DumpFlags</code>, <code>LogLevel</code>, <code>VfsCacheMode</code>
+- these will be returned as an integer and may be set as an integer but
+more conveniently they can be set as a string, eg "HARD" for
+<code>CutoffMode</code> or <code>DEBUG</code> for
+<code>LogLevel</code>.</li>
+<li><code>BandwidthSpec</code> - this will be set and returned as a
+string, eg "1M".</li>
 </ul>
 <h3 id="option-blocks">Option blocks</h3>
-<p>The calls <a href="#options-info">options/info</a> (for the main config) and <a href="#config-providers">config/providers</a> (for the backend config) may be used to get information on the rclone configuration options. This can be used to build user interfaces for displaying and setting any rclone option.</p>
-<p>These consist of arrays of <code>Option</code> blocks. These have the following format. Each block describes a single option.</p>
+<p>The calls <a href="#options-info">options/info</a> (for the main
+config) and <a href="#config-providers">config/providers</a> (for the
+backend config) may be used to get information on the rclone
+configuration options. This can be used to build user interfaces for
+displaying and setting any rclone option.</p>
+<p>These consist of arrays of <code>Option</code> blocks. These have the
+following format. Each block describes a single option.</p>
 <table>
 <colgroup>
 <col style="width: 19%" />
@@ -8770,7 +15408,8 @@ dir1/dir2/dir3/.ignore</code></pre>
 <td>Groups</td>
 <td>string</td>
 <td>Y</td>
-<td>groups this option belongs to - comma separated string for options classification</td>
+<td>groups this option belongs to - comma separated string for options
+classification</td>
 </tr>
 <tr class="odd">
 <td>Provider</td>
@@ -8782,7 +15421,8 @@ dir1/dir2/dir3/.ignore</code></pre>
 <td>Default</td>
 <td>any</td>
 <td>N</td>
-<td>default value, if set (and not to nil or "") then Required does nothing</td>
+<td>default value, if set (and not to nil or "") then Required does
+nothing</td>
 </tr>
 <tr class="odd">
 <td>Value</td>
@@ -8794,7 +15434,8 @@ dir1/dir2/dir3/.ignore</code></pre>
 <td>Examples</td>
 <td>Examples</td>
 <td>Y</td>
-<td>predefined values that can be selected from list (multiple-choice option)</td>
+<td>predefined values that can be selected from list (multiple-choice
+option)</td>
 </tr>
 <tr class="odd">
 <td>ShortOpt</td>
@@ -8806,13 +15447,15 @@ dir1/dir2/dir3/.ignore</code></pre>
 <td>Hide</td>
 <td>Visibility</td>
 <td>N</td>
-<td>if non zero, this option is hidden from the configurator or the command line</td>
+<td>if non zero, this option is hidden from the configurator or the
+command line</td>
 </tr>
 <tr class="odd">
 <td>Required</td>
 <td>bool</td>
 <td>N</td>
-<td>this option is required, meaning value cannot be empty unless there is a default</td>
+<td>this option is required, meaning value cannot be empty unless there
+is a default</td>
 </tr>
 <tr class="even">
 <td>IsPassword</td>
@@ -8836,17 +15479,21 @@ dir1/dir2/dir3/.ignore</code></pre>
 <td>Exclusive</td>
 <td>bool</td>
 <td>N</td>
-<td>set if the answer can only be one of the examples (empty string allowed unless Required or Default is set)</td>
+<td>set if the answer can only be one of the examples (empty string
+allowed unless Required or Default is set)</td>
 </tr>
 <tr class="even">
 <td>Sensitive</td>
 <td>bool</td>
 <td>N</td>
-<td>set if this option should be redacted when using <code>rclone config redacted</code></td>
+<td>set if this option should be redacted when using
+<code>rclone config redacted</code></td>
 </tr>
 </tbody>
 </table>
-<p>An example of this might be the <code>--log-level</code> flag. Note that the <code>Name</code> of the option becomes the command line flag with <code>_</code> replaced with <code>-</code>.</p>
+<p>An example of this might be the <code>--log-level</code> flag. Note
+that the <code>Name</code> of the option becomes the command line flag
+with <code>_</code> replaced with <code>-</code>.</p>
 <pre><code>{
     &quot;Advanced&quot;: false,
     &quot;Default&quot;: 5,
@@ -8876,23 +15523,37 @@ dir1/dir2/dir3/.ignore</code></pre>
     &quot;Value&quot;: null,
     &quot;ValueStr&quot;: &quot;NOTICE&quot;
 },</code></pre>
-<p>Note that the <code>Help</code> may be multiple lines separated by <code>\n</code>. The first line will always be a short sentence and this is the sentence shown when running <code>rclone help flags</code>.</p>
-<h2 id="specifying-remotes-to-work-on">Specifying remotes to work on</h2>
-<p>Remotes are specified with the <code>fs=</code>, <code>srcFs=</code>, <code>dstFs=</code> parameters depending on the command being used.</p>
-<p>The parameters can be a string as per the rest of rclone, eg <code>s3:bucket/path</code> or <code>:sftp:/my/dir</code>. They can also be specified as JSON blobs.</p>
-<p>If specifying a JSON blob it should be a object mapping strings to strings. These values will be used to configure the remote. There are 3 special values which may be set:</p>
+<p>Note that the <code>Help</code> may be multiple lines separated by
+<code>\n</code>. The first line will always be a short sentence and this
+is the sentence shown when running <code>rclone help flags</code>.</p>
+<h2 id="specifying-remotes-to-work-on">Specifying remotes to work
+on</h2>
+<p>Remotes are specified with the <code>fs=</code>, <code>srcFs=</code>,
+<code>dstFs=</code> parameters depending on the command being used.</p>
+<p>The parameters can be a string as per the rest of rclone, eg
+<code>s3:bucket/path</code> or <code>:sftp:/my/dir</code>. They can also
+be specified as JSON blobs.</p>
+<p>If specifying a JSON blob it should be a object mapping strings to
+strings. These values will be used to configure the remote. There are 3
+special values which may be set:</p>
 <ul>
-<li><code>type</code> - set to <code>type</code> to specify a remote called <code>:type:</code></li>
-<li><code>_name</code> - set to <code>name</code> to specify a remote called <code>name:</code></li>
+<li><code>type</code> - set to <code>type</code> to specify a remote
+called <code>:type:</code></li>
+<li><code>_name</code> - set to <code>name</code> to specify a remote
+called <code>name:</code></li>
 <li><code>_root</code> - sets the root of the remote - may be empty</li>
 </ul>
-<p>One of <code>_name</code> or <code>type</code> should normally be set. If the <code>local</code> backend is desired then <code>type</code> should be set to <code>local</code>. If <code>_root</code> isn't specified then it defaults to the root of the remote.</p>
+<p>One of <code>_name</code> or <code>type</code> should normally be
+set. If the <code>local</code> backend is desired then <code>type</code>
+should be set to <code>local</code>. If <code>_root</code> isn't
+specified then it defaults to the root of the remote.</p>
 <p>For example this JSON is equivalent to <code>remote:/tmp</code></p>
 <pre><code>{
     &quot;_name&quot;: &quot;remote&quot;,
     &quot;_root&quot;: &quot;/tmp&quot;
 }</code></pre>
-<p>And this is equivalent to <code>:sftp,host='example.com':/tmp</code></p>
+<p>And this is equivalent to
+<code>:sftp,host='example.com':/tmp</code></p>
 <pre><code>{
     &quot;type&quot;: &quot;sftp&quot;,
     &quot;host&quot;: &quot;example.com&quot;,
@@ -8932,27 +15593,43 @@ dir1/dir2/dir3/.ignore</code></pre>
         }
     }
 }</code></pre>
-<p>Note that this is the direct equivalent of using this "backend" command:</p>
+<p>Note that this is the direct equivalent of using this "backend"
+command:</p>
 <pre><code>rclone backend noop . -o echo=yes -o blue path1 path2</code></pre>
 <p>Note that arguments must be preceded by the "-a" flag</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more information.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more information.</p>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="cache-expire">cache/expire: Purge a remote from cache</h3>
-<p>Purge a remote from the cache backend. Supports either a directory or a file. Params: - remote = path to remote (required) - withData = true/false to delete cached data (chunks) as well (optional)</p>
+<p>Purge a remote from the cache backend. Supports either a directory or
+a file. Params: - remote = path to remote (required) - withData =
+true/false to delete cached data (chunks) as well (optional)</p>
 <p>Eg</p>
 <pre><code>rclone rc cache/expire remote=path/to/sub/folder/
 rclone rc cache/expire remote=/ withData=true</code></pre>
 <h3 id="cache-fetch">cache/fetch: Fetch file chunks</h3>
 <p>Ensure the specified file chunks are cached on disk.</p>
-<p>The chunks= parameter specifies the file chunks to check. It takes a comma separated list of array slice indices. The slice indices are similar to Python slices: start[:end]</p>
-<p>start is the 0 based chunk number from the beginning of the file to fetch inclusive. end is 0 based chunk number from the beginning of the file to fetch exclusive. Both values can be negative, in which case they count from the back of the file. The value "-5:" represents the last 5 chunks of a file.</p>
-<p>Some valid examples are: ":5,-5:" -&gt; the first and last five chunks "0,-2" -&gt; the first and the second last chunk "0:10" -&gt; the first ten chunks</p>
-<p>Any parameter with a key that starts with "file" can be used to specify files to fetch, e.g.</p>
+<p>The chunks= parameter specifies the file chunks to check. It takes a
+comma separated list of array slice indices. The slice indices are
+similar to Python slices: start[:end]</p>
+<p>start is the 0 based chunk number from the beginning of the file to
+fetch inclusive. end is 0 based chunk number from the beginning of the
+file to fetch exclusive. Both values can be negative, in which case they
+count from the back of the file. The value "-5:" represents the last 5
+chunks of a file.</p>
+<p>Some valid examples are: ":5,-5:" -&gt; the first and last five
+chunks "0,-2" -&gt; the first and the second last chunk "0:10" -&gt; the
+first ten chunks</p>
+<p>Any parameter with a key that starts with "file" can be used to
+specify files to fetch, e.g.</p>
 <pre><code>rclone rc cache/fetch chunks=0 file=hello file2=home/goodbye</code></pre>
-<p>File names will automatically be encrypted when the a crypt remote is used on top of the cache.</p>
+<p>File names will automatically be encrypted when the a crypt remote is
+used on top of the cache.</p>
 <h3 id="cache-stats">cache/stats: Get cache stats</h3>
 <p>Show statistics for the cache remote.</p>
-<h3 id="config-create">config/create: create the config for a remote.</h3>
+<h3 id="config-create">config/create: create the config for a
+remote.</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>name - name of remote</li>
@@ -8961,48 +15638,66 @@ rclone rc cache/expire remote=/ withData=true</code></pre>
 <li>opt - a dictionary of options to control the configuration
 <ul>
 <li>obscure - declare passwords are plain and need obscuring</li>
-<li>noObscure - declare passwords are already obscured and don't need obscuring</li>
+<li>noObscure - declare passwords are already obscured and don't need
+obscuring</li>
 <li>nonInteractive - don't interact with a user, return questions</li>
 <li>continue - continue the config process with an answer</li>
-<li>all - ask all the config questions not just the post config ones</li>
+<li>all - ask all the config questions not just the post config
+ones</li>
 <li>state - state to restart with - used with continue</li>
 <li>result - result to restart with - used with continue</li>
 </ul></li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_config_create/">config create</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_config_create/">config
+create</a> command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="config-delete">config/delete: Delete a remote in the config file.</h3>
+<h3 id="config-delete">config/delete: Delete a remote in the config
+file.</h3>
 <p>Parameters:</p>
 <ul>
 <li>name - name of remote to delete</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_config_delete/">config delete</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_config_delete/">config
+delete</a> command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="config-dump">config/dump: Dumps the config file.</h3>
 <p>Returns a JSON object: - key: value</p>
 <p>Where keys are remote names and values are the config parameters.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_config_dump/">config dump</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_config_dump/">config dump</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="config-get">config/get: Get a remote in the config file.</h3>
 <p>Parameters:</p>
 <ul>
 <li>name - name of remote to get</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_config_dump/">config dump</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_config_dump/">config dump</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="config-listremotes">config/listremotes: Lists the remotes in the config file and defined in environment variables.</h3>
+<h3 id="config-listremotes">config/listremotes: Lists the remotes in the
+config file and defined in environment variables.</h3>
 <p>Returns - remotes - array of remote names</p>
-<p>See the <a href="https://rclone.org/commands/rclone_listremotes/">listremotes</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_listremotes/">listremotes</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="config-password">config/password: password the config for a remote.</h3>
+<h3 id="config-password">config/password: password the config for a
+remote.</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>name - name of remote</li>
 <li>parameters - a map of { "key": "value" } pairs</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_config_password/">config password</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_config_password/">config
+password</a> command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="config-paths">config/paths: Reads the config file path and other important paths.</h3>
+<h3 id="config-paths">config/paths: Reads the config file path and other
+important paths.</h3>
 <p>Returns a JSON object with the following keys:</p>
 <ul>
 <li>config: path to config file</li>
@@ -9015,20 +15710,29 @@ rclone rc cache/expire remote=/ withData=true</code></pre>
     &quot;config&quot;: &quot;/home/USER/.rclone.conf&quot;,
     &quot;temp&quot;: &quot;/tmp&quot;
 }</code></pre>
-<p>See the <a href="https://rclone.org/commands/rclone_config_paths/">config paths</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_config_paths/">config paths</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="config-providers">config/providers: Shows how providers are configured in the config file.</h3>
+<h3 id="config-providers">config/providers: Shows how providers are
+configured in the config file.</h3>
 <p>Returns a JSON object: - providers - array of objects</p>
-<p>See the <a href="https://rclone.org/commands/rclone_config_providers/">config providers</a> command for more information on the above.</p>
-<p>Note that the Options blocks are in the same format as returned by "options/info". They are described in the <a href="#option-blocks">option blocks</a> section.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_config_providers/">config
+providers</a> command for more information on the above.</p>
+<p>Note that the Options blocks are in the same format as returned by
+"options/info". They are described in the <a
+href="#option-blocks">option blocks</a> section.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="config-setpath">config/setpath: Set the path of the config file</h3>
+<h3 id="config-setpath">config/setpath: Set the path of the config
+file</h3>
 <p>Parameters:</p>
 <ul>
 <li>path - path to the config file to use</li>
 </ul>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="config-update">config/update: update the config for a remote.</h3>
+<h3 id="config-update">config/update: update the config for a
+remote.</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>name - name of remote</li>
@@ -9036,18 +15740,24 @@ rclone rc cache/expire remote=/ withData=true</code></pre>
 <li>opt - a dictionary of options to control the configuration
 <ul>
 <li>obscure - declare passwords are plain and need obscuring</li>
-<li>noObscure - declare passwords are already obscured and don't need obscuring</li>
+<li>noObscure - declare passwords are already obscured and don't need
+obscuring</li>
 <li>nonInteractive - don't interact with a user, return questions</li>
 <li>continue - continue the config process with an answer</li>
-<li>all - ask all the config questions not just the post config ones</li>
+<li>all - ask all the config questions not just the post config
+ones</li>
 <li>state - state to restart with - used with continue</li>
 <li>result - result to restart with - used with continue</li>
 </ul></li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_config_update/">config update</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_config_update/">config
+update</a> command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="core-bwlimit">core/bwlimit: Set the bandwidth limit.</h3>
-<p>This sets the bandwidth limit to the string passed in. This should be a single bandwidth limit entry or a pair of upload:download bandwidth.</p>
+<p>This sets the bandwidth limit to the string passed in. This should be
+a single bandwidth limit entry or a pair of upload:download
+bandwidth.</p>
 <p>Eg</p>
 <pre><code>rclone rc core/bwlimit rate=off
 {
@@ -9070,7 +15780,8 @@ rclone rc core/bwlimit rate=1M:100k
     &quot;bytesPerSecondRx&quot;: 131072,
     &quot;rate&quot;: &quot;1M&quot;
 }</code></pre>
-<p>If the rate parameter is not supplied then the bandwidth is queried</p>
+<p>If the rate parameter is not supplied then the bandwidth is
+queried</p>
 <pre><code>rclone rc core/bwlimit
 {
     &quot;bytesPerSecond&quot;: 1048576,
@@ -9078,19 +15789,25 @@ rclone rc core/bwlimit rate=1M:100k
     &quot;bytesPerSecondRx&quot;: 1048576,
     &quot;rate&quot;: &quot;1M&quot;
 }</code></pre>
-<p>The format of the parameter is exactly the same as passed to --bwlimit except only one bandwidth may be specified.</p>
-<p>In either case "rate" is returned as a human-readable string, and "bytesPerSecond" is returned as a number.</p>
-<h3 id="core-command">core/command: Run a rclone terminal command over rc.</h3>
+<p>The format of the parameter is exactly the same as passed to
+--bwlimit except only one bandwidth may be specified.</p>
+<p>In either case "rate" is returned as a human-readable string, and
+"bytesPerSecond" is returned as a number.</p>
+<h3 id="core-command">core/command: Run a rclone terminal command over
+rc.</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>command - a string with the command name.</li>
 <li>arg - a list of arguments for the backend command.</li>
 <li>opt - a map of string to string of options.</li>
-<li>returnType - one of ("COMBINED_OUTPUT", "STREAM", "STREAM_ONLY_STDOUT", "STREAM_ONLY_STDERR").
+<li>returnType - one of ("COMBINED_OUTPUT", "STREAM",
+"STREAM_ONLY_STDOUT", "STREAM_ONLY_STDERR").
 <ul>
 <li>Defaults to "COMBINED_OUTPUT" if not set.</li>
-<li>The STREAM returnTypes will write the output to the body of the HTTP message.</li>
-<li>The COMBINED_OUTPUT will write the output to the "result" parameter.</li>
+<li>The STREAM returnTypes will write the output to the body of the HTTP
+message.</li>
+<li>The COMBINED_OUTPUT will write the output to the "result"
+parameter.</li>
 </ul></li>
 </ul>
 <p>Returns:</p>
@@ -9100,7 +15817,8 @@ rclone rc core/bwlimit rate=1M:100k
 <li>Only set when using returnType "COMBINED_OUTPUT".</li>
 </ul></li>
 <li>error - set if rclone exits with an error code.</li>
-<li>returnType - one of ("COMBINED_OUTPUT", "STREAM", "STREAM_ONLY_STDOUT", "STREAM_ONLY_STDERR").</li>
+<li>returnType - one of ("COMBINED_OUTPUT", "STREAM",
+"STREAM_ONLY_STDOUT", "STREAM_ONLY_STDERR").</li>
 </ul>
 <p>Example:</p>
 <pre><code>rclone rc core/command command=ls -a mydrive:/ -o max-depth=1
@@ -9118,9 +15836,12 @@ OR
 }
 </code></pre>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="core-du">core/du: Returns disk usage of a locally attached disk.</h3>
-<p>This returns the disk usage for the local directory passed in as dir.</p>
-<p>If the directory is not passed in, it defaults to the directory pointed to by --cache-dir.</p>
+<h3 id="core-du">core/du: Returns disk usage of a locally attached
+disk.</h3>
+<p>This returns the disk usage for the local directory passed in as
+dir.</p>
+<p>If the directory is not passed in, it defaults to the directory
+pointed to by --cache-dir.</p>
 <ul>
 <li>dir - string (optional)</li>
 </ul>
@@ -9134,7 +15855,9 @@ OR
     }
 }</code></pre>
 <h3 id="core-gc">core/gc: Runs a garbage collection.</h3>
-<p>This tells the go runtime to do a garbage collection run. It isn't necessary to call this normally, but it can be useful for debugging memory problems.</p>
+<p>This tells the go runtime to do a garbage collection run. It isn't
+necessary to call this normally, but it can be useful for debugging
+memory problems.</p>
 <h3 id="core-group-list">core/group-list: Returns list of stats.</h3>
 <p>This returns list of stats groups currently in memory.</p>
 <p>Returns the following values:</p>
@@ -9147,27 +15870,36 @@ OR
         ]
 }</code></pre>
 <h3 id="core-memstats">core/memstats: Returns the memory statistics</h3>
-<p>This returns the memory statistics of the running program. What the values mean are explained in the go docs: https://golang.org/pkg/runtime/#MemStats</p>
+<p>This returns the memory statistics of the running program. What the
+values mean are explained in the go docs:
+https://golang.org/pkg/runtime/#MemStats</p>
 <p>The most interesting values for most people are:</p>
 <ul>
-<li>HeapAlloc - this is the amount of memory rclone is actually using</li>
-<li>HeapSys - this is the amount of memory rclone has obtained from the OS</li>
+<li>HeapAlloc - this is the amount of memory rclone is actually
+using</li>
+<li>HeapSys - this is the amount of memory rclone has obtained from the
+OS</li>
 <li>Sys - this is the total amount of memory requested from the OS
 <ul>
 <li>It is virtual memory so may include unused memory</li>
 </ul></li>
 </ul>
 <h3 id="core-obscure">core/obscure: Obscures a string passed in.</h3>
-<p>Pass a clear string and rclone will obscure it for the config file: - clear - string</p>
+<p>Pass a clear string and rclone will obscure it for the config file: -
+clear - string</p>
 <p>Returns: - obscured - string</p>
 <h3 id="core-pid">core/pid: Return PID of current process</h3>
-<p>This returns PID of current process. Useful for stopping rclone process.</p>
+<p>This returns PID of current process. Useful for stopping rclone
+process.</p>
 <h3 id="core-quit">core/quit: Terminates the app.</h3>
-<p>(Optional) Pass an exit code to be used for terminating the app: - exitCode - int</p>
-<h3 id="core-stats">core/stats: Returns stats about current transfers.</h3>
+<p>(Optional) Pass an exit code to be used for terminating the app: -
+exitCode - int</p>
+<h3 id="core-stats">core/stats: Returns stats about current
+transfers.</h3>
 <p>This returns all available stats:</p>
 <pre><code>rclone rc core/stats</code></pre>
-<p>If group is not provided then summed up stats for all groups will be returned.</p>
+<p>If group is not provided then summed up stats for all groups will be
+returned.</p>
 <p>Parameters</p>
 <ul>
 <li>group - name of the stats group (string)</li>
@@ -9209,7 +15941,9 @@ OR
     &quot;checking&quot;: an array of names of currently active file checks
         []
 }</code></pre>
-<p>Values for "transferring", "checking" and "lastError" are only assigned if data is available. The value for "eta" is null if an eta cannot be determined.</p>
+<p>Values for "transferring", "checking" and "lastError" are only
+assigned if data is available. The value for "eta" is null if an eta
+cannot be determined.</p>
 <h3 id="core-stats-delete">core/stats-delete: Delete stats group.</h3>
 <p>This deletes entire stats group.</p>
 <p>Parameters</p>
@@ -9217,15 +15951,18 @@ OR
 <li>group - name of the stats group (string)</li>
 </ul>
 <h3 id="core-stats-reset">core/stats-reset: Reset stats.</h3>
-<p>This clears counters, errors and finished transfers for all stats or specific stats group if group is provided.</p>
+<p>This clears counters, errors and finished transfers for all stats or
+specific stats group if group is provided.</p>
 <p>Parameters</p>
 <ul>
 <li>group - name of the stats group (string)</li>
 </ul>
-<h3 id="core-transferred">core/transferred: Returns stats about completed transfers.</h3>
+<h3 id="core-transferred">core/transferred: Returns stats about
+completed transfers.</h3>
 <p>This returns stats about completed transfers:</p>
 <pre><code>rclone rc core/transferred</code></pre>
-<p>If group is not provided then completed transfers for all groups will be returned.</p>
+<p>If group is not provided then completed transfers for all groups will
+be returned.</p>
 <p>Note only the last 100 completed transfers are returned.</p>
 <p>Parameters</p>
 <ul>
@@ -9246,12 +15983,14 @@ OR
             }
         ]
 }</code></pre>
-<h3 id="core-version">core/version: Shows the current version of rclone and the go runtime.</h3>
+<h3 id="core-version">core/version: Shows the current version of rclone
+and the go runtime.</h3>
 <p>This shows the current version of go and the go runtime:</p>
 <ul>
 <li>version - rclone version, e.g. "v1.53.0"</li>
 <li>decomposed - version number as [major, minor, patch]</li>
-<li>isGit - boolean - true if this was compiled from the git version</li>
+<li>isGit - boolean - true if this was compiled from the git
+version</li>
 <li>isBeta - boolean - true if this is a beta version</li>
 <li>os - OS in use as according to Go</li>
 <li>arch - cpu architecture in use according to Go</li>
@@ -9259,27 +15998,49 @@ OR
 <li>linking - type of rclone executable (static or dynamic)</li>
 <li>goTags - space separated build tags or "none"</li>
 </ul>
-<h3 id="debug-set-block-profile-rate">debug/set-block-profile-rate: Set runtime.SetBlockProfileRate for blocking profiling.</h3>
-<p>SetBlockProfileRate controls the fraction of goroutine blocking events that are reported in the blocking profile. The profiler aims to sample an average of one blocking event per rate nanoseconds spent blocked.</p>
-<p>To include every blocking event in the profile, pass rate = 1. To turn off profiling entirely, pass rate &lt;= 0.</p>
+<h3 id="debug-set-block-profile-rate">debug/set-block-profile-rate: Set
+runtime.SetBlockProfileRate for blocking profiling.</h3>
+<p>SetBlockProfileRate controls the fraction of goroutine blocking
+events that are reported in the blocking profile. The profiler aims to
+sample an average of one blocking event per rate nanoseconds spent
+blocked.</p>
+<p>To include every blocking event in the profile, pass rate = 1. To
+turn off profiling entirely, pass rate &lt;= 0.</p>
 <p>After calling this you can use this to see the blocking profile:</p>
 <pre><code>go tool pprof http://localhost:5572/debug/pprof/block</code></pre>
 <p>Parameters:</p>
 <ul>
 <li>rate - int</li>
 </ul>
-<h3 id="debug-set-gc-percent">debug/set-gc-percent: Call runtime/debug.SetGCPercent for setting the garbage collection target percentage.</h3>
-<p>SetGCPercent sets the garbage collection target percentage: a collection is triggered when the ratio of freshly allocated data to live data remaining after the previous collection reaches this percentage. SetGCPercent returns the previous setting. The initial setting is the value of the GOGC environment variable at startup, or 100 if the variable is not set.</p>
-<p>This setting may be effectively reduced in order to maintain a memory limit. A negative percentage effectively disables garbage collection, unless the memory limit is reached.</p>
-<p>See https://pkg.go.dev/runtime/debug#SetMemoryLimit for more details.</p>
+<h3 id="debug-set-gc-percent">debug/set-gc-percent: Call
+runtime/debug.SetGCPercent for setting the garbage collection target
+percentage.</h3>
+<p>SetGCPercent sets the garbage collection target percentage: a
+collection is triggered when the ratio of freshly allocated data to live
+data remaining after the previous collection reaches this percentage.
+SetGCPercent returns the previous setting. The initial setting is the
+value of the GOGC environment variable at startup, or 100 if the
+variable is not set.</p>
+<p>This setting may be effectively reduced in order to maintain a memory
+limit. A negative percentage effectively disables garbage collection,
+unless the memory limit is reached.</p>
+<p>See https://pkg.go.dev/runtime/debug#SetMemoryLimit for more
+details.</p>
 <p>Parameters:</p>
 <ul>
 <li>gc-percent - int</li>
 </ul>
-<h3 id="debug-set-mutex-profile-fraction">debug/set-mutex-profile-fraction: Set runtime.SetMutexProfileFraction for mutex profiling.</h3>
-<p>SetMutexProfileFraction controls the fraction of mutex contention events that are reported in the mutex profile. On average 1/rate events are reported. The previous rate is returned.</p>
-<p>To turn off profiling entirely, pass rate 0. To just read the current rate, pass rate &lt; 0. (For n&gt;1 the details of sampling may change.)</p>
-<p>Once this is set you can look use this to profile the mutex contention:</p>
+<h3
+id="debug-set-mutex-profile-fraction">debug/set-mutex-profile-fraction:
+Set runtime.SetMutexProfileFraction for mutex profiling.</h3>
+<p>SetMutexProfileFraction controls the fraction of mutex contention
+events that are reported in the mutex profile. On average 1/rate events
+are reported. The previous rate is returned.</p>
+<p>To turn off profiling entirely, pass rate 0. To just read the current
+rate, pass rate &lt; 0. (For n&gt;1 the details of sampling may
+change.)</p>
+<p>Once this is set you can look use this to profile the mutex
+contention:</p>
 <pre><code>go tool pprof http://localhost:5572/debug/pprof/mutex</code></pre>
 <p>Parameters:</p>
 <ul>
@@ -9289,23 +16050,51 @@ OR
 <ul>
 <li>previousRate - int</li>
 </ul>
-<h3 id="debug-set-soft-memory-limit">debug/set-soft-memory-limit: Call runtime/debug.SetMemoryLimit for setting a soft memory limit for the runtime.</h3>
+<h3 id="debug-set-soft-memory-limit">debug/set-soft-memory-limit: Call
+runtime/debug.SetMemoryLimit for setting a soft memory limit for the
+runtime.</h3>
 <p>SetMemoryLimit provides the runtime with a soft memory limit.</p>
-<p>The runtime undertakes several processes to try to respect this memory limit, including adjustments to the frequency of garbage collections and returning memory to the underlying system more aggressively. This limit will be respected even if GOGC=off (or, if SetGCPercent(-1) is executed).</p>
-<p>The input limit is provided as bytes, and includes all memory mapped, managed, and not released by the Go runtime. Notably, it does not account for space used by the Go binary and memory external to Go, such as memory managed by the underlying system on behalf of the process, or memory managed by non-Go code inside the same process. Examples of excluded memory sources include: OS kernel memory held on behalf of the process, memory allocated by C code, and memory mapped by syscall.Mmap (because it is not managed by the Go runtime).</p>
-<p>A zero limit or a limit that's lower than the amount of memory used by the Go runtime may cause the garbage collector to run nearly continuously. However, the application may still make progress.</p>
-<p>The memory limit is always respected by the Go runtime, so to effectively disable this behavior, set the limit very high. math.MaxInt64 is the canonical value for disabling the limit, but values much greater than the available memory on the underlying system work just as well.</p>
-<p>See https://go.dev/doc/gc-guide for a detailed guide explaining the soft memory limit in more detail, as well as a variety of common use-cases and scenarios.</p>
-<p>SetMemoryLimit returns the previously set memory limit. A negative input does not adjust the limit, and allows for retrieval of the currently set memory limit.</p>
+<p>The runtime undertakes several processes to try to respect this
+memory limit, including adjustments to the frequency of garbage
+collections and returning memory to the underlying system more
+aggressively. This limit will be respected even if GOGC=off (or, if
+SetGCPercent(-1) is executed).</p>
+<p>The input limit is provided as bytes, and includes all memory mapped,
+managed, and not released by the Go runtime. Notably, it does not
+account for space used by the Go binary and memory external to Go, such
+as memory managed by the underlying system on behalf of the process, or
+memory managed by non-Go code inside the same process. Examples of
+excluded memory sources include: OS kernel memory held on behalf of the
+process, memory allocated by C code, and memory mapped by syscall.Mmap
+(because it is not managed by the Go runtime).</p>
+<p>A zero limit or a limit that's lower than the amount of memory used
+by the Go runtime may cause the garbage collector to run nearly
+continuously. However, the application may still make progress.</p>
+<p>The memory limit is always respected by the Go runtime, so to
+effectively disable this behavior, set the limit very high.
+math.MaxInt64 is the canonical value for disabling the limit, but values
+much greater than the available memory on the underlying system work
+just as well.</p>
+<p>See https://go.dev/doc/gc-guide for a detailed guide explaining the
+soft memory limit in more detail, as well as a variety of common
+use-cases and scenarios.</p>
+<p>SetMemoryLimit returns the previously set memory limit. A negative
+input does not adjust the limit, and allows for retrieval of the
+currently set memory limit.</p>
 <p>Parameters:</p>
 <ul>
 <li>mem-limit - int</li>
 </ul>
 <h3 id="fscache-clear">fscache/clear: Clear the Fs cache.</h3>
-<p>This clears the fs cache. This is where remotes created from backends are cached for a short while to make repeated rc calls more efficient.</p>
-<p>If you change the parameters of a backend then you may want to call this to clear an existing remote out of the cache before re-creating it.</p>
+<p>This clears the fs cache. This is where remotes created from backends
+are cached for a short while to make repeated rc calls more
+efficient.</p>
+<p>If you change the parameters of a backend then you may want to call
+this to clear an existing remote out of the cache before re-creating
+it.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="fscache-entries">fscache/entries: Returns the number of entries in the fs cache.</h3>
+<h3 id="fscache-entries">fscache/entries: Returns the number of entries
+in the fs cache.</h3>
 <p>This returns the number of entries in the fs cache.</p>
 <p>Returns - entries - number of items in the cache</p>
 <p><strong>Authentication is required for this call.</strong></p>
@@ -9313,8 +16102,10 @@ OR
 <p>Parameters: None.</p>
 <p>Results:</p>
 <ul>
-<li>executeId - string id of rclone executing (change after restart)</li>
-<li>jobids - array of integer job ids (starting at 1 on each restart)</li>
+<li>executeId - string id of rclone executing (change after
+restart)</li>
+<li>jobids - array of integer job ids (starting at 1 on each
+restart)</li>
 </ul>
 <h3 id="job-status">job/status: Reads the status of the job ID</h3>
 <p>Parameters:</p>
@@ -9325,13 +16116,16 @@ OR
 <ul>
 <li>finished - boolean</li>
 <li>duration - time in seconds that the job ran for</li>
-<li>endTime - time the job finished (e.g. "2018-10-26T18:50:20.528746884+01:00")</li>
+<li>endTime - time the job finished (e.g.
+"2018-10-26T18:50:20.528746884+01:00")</li>
 <li>error - error from the job or empty string for no error</li>
 <li>finished - boolean whether the job has finished or not</li>
 <li>id - as passed in above</li>
-<li>startTime - time the job started (e.g. "2018-10-26T18:50:20.528336039+01:00")</li>
+<li>startTime - time the job started (e.g.
+"2018-10-26T18:50:20.528336039+01:00")</li>
 <li>success - boolean - true for success false otherwise</li>
-<li>output - output of the job as would have been returned if called synchronously</li>
+<li>output - output of the job as would have been returned if called
+synchronously</li>
 <li>progress - output of the progress related to the underlying job</li>
 </ul>
 <h3 id="job-stop">job/stop: Stop the running job</h3>
@@ -9339,13 +16133,16 @@ OR
 <ul>
 <li>jobid - id of the job (integer).</li>
 </ul>
-<h3 id="job-stopgroup">job/stopgroup: Stop all running jobs in a group</h3>
+<h3 id="job-stopgroup">job/stopgroup: Stop all running jobs in a
+group</h3>
 <p>Parameters:</p>
 <ul>
 <li>group - name of the group (string).</li>
 </ul>
-<h3 id="mount-listmounts">mount/listmounts: Show current mount points</h3>
-<p>This shows currently mounted points, which can be used for performing an unmount.</p>
+<h3 id="mount-listmounts">mount/listmounts: Show current mount
+points</h3>
+<p>This shows currently mounted points, which can be used for performing
+an unmount.</p>
 <p>This takes no parameters and returns</p>
 <ul>
 <li>mountPoints: list of current mount points</li>
@@ -9354,13 +16151,16 @@ OR
 <pre><code>rclone rc mount/listmounts</code></pre>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="mount-mount">mount/mount: Create a new mount point</h3>
-<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
-<p>If no mountType is provided, the priority is given as follows: 1. mount 2.cmount 3.mount2</p>
+<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of
+Rclone's cloud storage systems as a file system with FUSE.</p>
+<p>If no mountType is provided, the priority is given as follows: 1.
+mount 2.cmount 3.mount2</p>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote path to be mounted (required)</li>
 <li>mountPoint: valid path on the local machine (required)</li>
-<li>mountType: one of the values (mount, cmount, mount2) specifies the mount implementation to use</li>
+<li>mountType: one of the values (mount, cmount, mount2) specifies the
+mount implementation to use</li>
 <li>mountOpt: a JSON object with Mount options in.</li>
 <li>vfsOpt: a JSON object with VFS options in.</li>
 </ul>
@@ -9368,7 +16168,9 @@ OR
 <pre><code>rclone rc mount/mount fs=mydrive: mountPoint=/home/&lt;user&gt;/mountPoint
 rclone rc mount/mount fs=mydrive: mountPoint=/home/&lt;user&gt;/mountPoint mountType=mount
 rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;CacheMode&quot;: 2}&#39; mountOpt=&#39;{&quot;AllowOther&quot;: true}&#39;</code></pre>
-<p>The vfsOpt are as described in options/get and can be seen in the the "vfs" section when running and the mountOpt can be seen in the "mount" section:</p>
+<p>The vfsOpt are as described in options/get and can be seen in the the
+"vfs" section when running and the mountOpt can be seen in the "mount"
+section:</p>
 <pre><code>rclone rc options/get</code></pre>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="mount-types">mount/types: Show all possible mount types</h3>
@@ -9377,109 +16179,158 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
 <ul>
 <li>mountTypes: list of mount types</li>
 </ul>
-<p>The mount types are strings like "mount", "mount2", "cmount" and can be passed to mount/mount as the mountType parameter.</p>
+<p>The mount types are strings like "mount", "mount2", "cmount" and can
+be passed to mount/mount as the mountType parameter.</p>
 <p>Eg</p>
 <pre><code>rclone rc mount/types</code></pre>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="mount-unmount">mount/unmount: Unmount selected active mount</h3>
-<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
+<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of
+Rclone's cloud storage systems as a file system with FUSE.</p>
 <p>This takes the following parameters:</p>
 <ul>
-<li>mountPoint: valid path on the local machine where the mount was created (required)</li>
+<li>mountPoint: valid path on the local machine where the mount was
+created (required)</li>
 </ul>
 <p>Example:</p>
 <pre><code>rclone rc mount/unmount mountPoint=/home/&lt;user&gt;/mountPoint</code></pre>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="mount-unmountall">mount/unmountall: Unmount all active mounts</h3>
-<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of Rclone's cloud storage systems as a file system with FUSE.</p>
-<p>This takes no parameters and returns error if unmount does not succeed.</p>
+<h3 id="mount-unmountall">mount/unmountall: Unmount all active
+mounts</h3>
+<p>rclone allows Linux, FreeBSD, macOS and Windows to mount any of
+Rclone's cloud storage systems as a file system with FUSE.</p>
+<p>This takes no parameters and returns error if unmount does not
+succeed.</p>
 <p>Eg</p>
 <pre><code>rclone rc mount/unmountall</code></pre>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-about">operations/about: Return the space used on the remote</h3>
+<h3 id="operations-about">operations/about: Return the space used on the
+remote</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 </ul>
 <p>The result is as returned from rclone about --json</p>
-<p>See the <a href="https://rclone.org/commands/rclone_about/">about</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_about/">about</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-check">operations/check: check the source and destination are the same</h3>
-<p>Checks the files in the source and destination match. It compares sizes and hashes and logs a report of files that don't match. It doesn't alter the source or destination.</p>
+<h3 id="operations-check">operations/check: check the source and
+destination are the same</h3>
+<p>Checks the files in the source and destination match. It compares
+sizes and hashes and logs a report of files that don't match. It doesn't
+alter the source or destination.</p>
 <p>This takes the following parameters:</p>
 <ul>
-<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for local filesystem</li>
-<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/" for local filesystem</li>
+<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for
+local filesystem</li>
+<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/"
+for local filesystem</li>
 <li>download - check by downloading rather than with hash</li>
-<li>checkFileHash - treat checkFileFs:checkFileRemote as a SUM file with hashes of given type</li>
-<li>checkFileFs - treat checkFileFs:checkFileRemote as a SUM file with hashes of given type</li>
-<li>checkFileRemote - treat checkFileFs:checkFileRemote as a SUM file with hashes of given type</li>
+<li>checkFileHash - treat checkFileFs:checkFileRemote as a SUM file with
+hashes of given type</li>
+<li>checkFileFs - treat checkFileFs:checkFileRemote as a SUM file with
+hashes of given type</li>
+<li>checkFileRemote - treat checkFileFs:checkFileRemote as a SUM file
+with hashes of given type</li>
 <li>oneWay - check one way only, source files must exist on remote</li>
 <li>combined - make a combined report of changes (default false)</li>
-<li>missingOnSrc - report all files missing from the source (default true)</li>
-<li>missingOnDst - report all files missing from the destination (default true)</li>
+<li>missingOnSrc - report all files missing from the source (default
+true)</li>
+<li>missingOnDst - report all files missing from the destination
+(default true)</li>
 <li>match - report all matching files (default false)</li>
 <li>differ - report all non-matching files (default true)</li>
-<li>error - report all files with errors (hashing or reading) (default true)</li>
+<li>error - report all files with errors (hashing or reading) (default
+true)</li>
 </ul>
-<p>If you supply the download flag, it will download the data from both remotes and check them against each other on the fly. This can be useful for remotes that don't support hashes or if you really want to check all the data.</p>
-<p>If you supply the size-only global flag, it will only compare the sizes not the hashes as well. Use this for a quick check.</p>
-<p>If you supply the checkFileHash option with a valid hash name, the checkFileFs:checkFileRemote must point to a text file in the SUM format. This treats the checksum file as the source and dstFs as the destination. Note that srcFs is not used and should not be supplied in this case.</p>
+<p>If you supply the download flag, it will download the data from both
+remotes and check them against each other on the fly. This can be useful
+for remotes that don't support hashes or if you really want to check all
+the data.</p>
+<p>If you supply the size-only global flag, it will only compare the
+sizes not the hashes as well. Use this for a quick check.</p>
+<p>If you supply the checkFileHash option with a valid hash name, the
+checkFileFs:checkFileRemote must point to a text file in the SUM format.
+This treats the checksum file as the source and dstFs as the
+destination. Note that srcFs is not used and should not be supplied in
+this case.</p>
 <p>Returns:</p>
 <ul>
 <li>success - true if no error, false otherwise</li>
 <li>status - textual summary of check, OK or text string</li>
 <li>hashType - hash used in check, may be missing</li>
 <li>combined - array of strings of combined report of changes</li>
-<li>missingOnSrc - array of strings of all files missing from the source</li>
-<li>missingOnDst - array of strings of all files missing from the destination</li>
+<li>missingOnSrc - array of strings of all files missing from the
+source</li>
+<li>missingOnDst - array of strings of all files missing from the
+destination</li>
 <li>match - array of strings of all matching files</li>
 <li>differ - array of strings of all non-matching files</li>
-<li>error - array of strings of all files with errors (hashing or reading)</li>
+<li>error - array of strings of all files with errors (hashing or
+reading)</li>
 </ul>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-cleanup">operations/cleanup: Remove trashed files in the remote or path</h3>
+<h3 id="operations-cleanup">operations/cleanup: Remove trashed files in
+the remote or path</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_cleanup/">cleanup</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_cleanup/">cleanup</a> command
+for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-copyfile">operations/copyfile: Copy a file from source remote to destination remote</h3>
+<h3 id="operations-copyfile">operations/copyfile: Copy a file from
+source remote to destination remote</h3>
 <p>This takes the following parameters:</p>
 <ul>
-<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for local filesystem</li>
-<li>srcRemote - a path within that remote e.g. "file.txt" for the source</li>
-<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/" for local filesystem</li>
-<li>dstRemote - a path within that remote e.g. "file2.txt" for the destination</li>
+<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for
+local filesystem</li>
+<li>srcRemote - a path within that remote e.g. "file.txt" for the
+source</li>
+<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/"
+for local filesystem</li>
+<li>dstRemote - a path within that remote e.g. "file2.txt" for the
+destination</li>
 </ul>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-copyurl">operations/copyurl: Copy the URL to the object</h3>
+<h3 id="operations-copyurl">operations/copyurl: Copy the URL to the
+object</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
 <li>url - string, URL to read from</li>
-<li>autoFilename - boolean, set to true to retrieve destination file name from url</li>
+<li>autoFilename - boolean, set to true to retrieve destination file
+name from url</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_copyurl/">copyurl</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_copyurl/">copyurl</a> command
+for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-delete">operations/delete: Remove files in the path</h3>
+<h3 id="operations-delete">operations/delete: Remove files in the
+path</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_delete/">delete</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_delete/">delete</a> command for
+more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-deletefile">operations/deletefile: Remove the single file pointed to</h3>
+<h3 id="operations-deletefile">operations/deletefile: Remove the single
+file pointed to</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_deletefile/">deletefile</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_deletefile/">deletefile</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-fsinfo">operations/fsinfo: Return information about the remote</h3>
+<h3 id="operations-fsinfo">operations/fsinfo: Return information about
+the remote</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
@@ -9584,22 +16435,33 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
                 &quot;Help&quot;: &quot;Textual help string\n&quot;
         }
 }</code></pre>
-<p>This command does not have a command line equivalent so use this instead:</p>
+<p>This command does not have a command line equivalent so use this
+instead:</p>
 <pre><code>rclone rc --loopback operations/fsinfo fs=remote:</code></pre>
-<h3 id="operations-hashsum">operations/hashsum: Produces a hashsum file for all the objects in the path.</h3>
-<p>Produces a hash file for all the objects in the path using the hash named. The output is in the same format as the standard md5sum/sha1sum tool.</p>
+<h3 id="operations-hashsum">operations/hashsum: Produces a hashsum file
+for all the objects in the path.</h3>
+<p>Produces a hash file for all the objects in the path using the hash
+named. The output is in the same format as the standard md5sum/sha1sum
+tool.</p>
 <p>This takes the following parameters:</p>
 <ul>
-<li>fs - a remote name string e.g. "drive:" for the source, "/" for local filesystem
+<li>fs - a remote name string e.g. "drive:" for the source, "/" for
+local filesystem
 <ul>
-<li>this can point to a file and just that file will be returned in the listing.</li>
+<li>this can point to a file and just that file will be returned in the
+listing.</li>
 </ul></li>
 <li>hashType - type of hash to be used</li>
 <li>download - check by downloading rather than with hash (boolean)</li>
 <li>base64 - output the hashes in base64 rather than hex (boolean)</li>
 </ul>
-<p>If you supply the download flag, it will download the data from the remote and create the hash on the fly. This can be useful for remotes that don't support the given hash or if you really want to check all the data.</p>
-<p>Note that if you wish to supply a checkfile to check hashes against the current files then you should use operations/check instead of operations/hashsum.</p>
+<p>If you supply the download flag, it will download the data from the
+remote and create the hash on the fly. This can be useful for remotes
+that don't support the given hash or if you really want to check all the
+data.</p>
+<p>Note that if you wish to supply a checkfile to check hashes against
+the current files then you should use operations/check instead of
+operations/hashsum.</p>
 <p>Returns:</p>
 <ul>
 <li>hashsum - array of strings of the hashes</li>
@@ -9615,9 +16477,12 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
         &quot;VHbmHzHh4taXzgag8BAIKQ==  bisect-rclone.sh&quot;,
     ]
 }</code></pre>
-<p>See the <a href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_hashsum/">hashsum</a> command
+for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-list">operations/list: List the given remote and path in JSON format</h3>
+<h3 id="operations-list">operations/list: List the given remote and path
+in JSON format</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
@@ -9633,7 +16498,8 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
 <li>dirsOnly - If set only show directories</li>
 <li>filesOnly - If set only show files</li>
 <li>metadata - If set return metadata of objects also</li>
-<li>hashTypes - array of strings of hash types to show if showHash set</li>
+<li>hashTypes - array of strings of hash types to show if showHash
+set</li>
 </ul></li>
 </ul>
 <p>Returns:</p>
@@ -9643,80 +16509,107 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
 <li>This is an array of objects as described in the lsjson command</li>
 </ul></li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_lsjson/">lsjson</a> command for more information on the above and examples.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_lsjson/">lsjson</a> command for
+more information on the above and examples.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-mkdir">operations/mkdir: Make a destination directory or container</h3>
+<h3 id="operations-mkdir">operations/mkdir: Make a destination directory
+or container</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_mkdir/">mkdir</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_mkdir/">mkdir</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-movefile">operations/movefile: Move a file from source remote to destination remote</h3>
+<h3 id="operations-movefile">operations/movefile: Move a file from
+source remote to destination remote</h3>
 <p>This takes the following parameters:</p>
 <ul>
-<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for local filesystem</li>
-<li>srcRemote - a path within that remote e.g. "file.txt" for the source</li>
-<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/" for local filesystem</li>
-<li>dstRemote - a path within that remote e.g. "file2.txt" for the destination</li>
+<li>srcFs - a remote name string e.g. "drive:" for the source, "/" for
+local filesystem</li>
+<li>srcRemote - a path within that remote e.g. "file.txt" for the
+source</li>
+<li>dstFs - a remote name string e.g. "drive2:" for the destination, "/"
+for local filesystem</li>
+<li>dstRemote - a path within that remote e.g. "file2.txt" for the
+destination</li>
 </ul>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-publiclink">operations/publiclink: Create or retrieve a public link to the given file or folder.</h3>
+<h3 id="operations-publiclink">operations/publiclink: Create or retrieve
+a public link to the given file or folder.</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
-<li>unlink - boolean - if set removes the link rather than adding it (optional)</li>
-<li>expire - string - the expiry time of the link e.g. "1d" (optional)</li>
+<li>unlink - boolean - if set removes the link rather than adding it
+(optional)</li>
+<li>expire - string - the expiry time of the link e.g. "1d"
+(optional)</li>
 </ul>
 <p>Returns:</p>
 <ul>
 <li>url - URL of the resource</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_link/">link</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_link/">link</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-purge">operations/purge: Remove a directory or container and all of its contents</h3>
+<h3 id="operations-purge">operations/purge: Remove a directory or
+container and all of its contents</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_purge/">purge</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_purge/">purge</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-rmdir">operations/rmdir: Remove an empty directory or container</h3>
+<h3 id="operations-rmdir">operations/rmdir: Remove an empty directory or
+container</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_rmdir/">rmdir</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-rmdirs">operations/rmdirs: Remove all the empty directories in the path</h3>
+<h3 id="operations-rmdirs">operations/rmdirs: Remove all the empty
+directories in the path</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
 <li>leaveRoot - boolean, set to true not to delete the root</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_rmdirs/">rmdirs</a> command for
+more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-settier">operations/settier: Changes storage tier or class on all files in the path</h3>
+<h3 id="operations-settier">operations/settier: Changes storage tier or
+class on all files in the path</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_settier/">settier</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_settier/">settier</a> command
+for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-settierfile">operations/settierfile: Changes storage tier or class on the single file pointed to</h3>
+<h3 id="operations-settierfile">operations/settierfile: Changes storage
+tier or class on the single file pointed to</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_settierfile/">settierfile</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_settierfile/">settierfile</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-size">operations/size: Count the number of bytes and files in remote</h3>
+<h3 id="operations-size">operations/size: Count the number of bytes and
+files in remote</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:path/to/dir"</li>
@@ -9726,9 +16619,11 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
 <li>count - number of files</li>
 <li>bytes - number of bytes in those files</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_size/">size</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_size/">size</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-stat">operations/stat: Give information about the supplied file or directory</h3>
+<h3 id="operations-stat">operations/stat: Give information about the
+supplied file or directory</h3>
 <p>This takes the following parameters</p>
 <ul>
 <li>fs - a remote name string eg "drive:"</li>
@@ -9740,24 +16635,32 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
 </ul>
 <p>The result is</p>
 <ul>
-<li>item - an object as described in the lsjson command. Will be null if not found.</li>
+<li>item - an object as described in the lsjson command. Will be null if
+not found.</li>
 </ul>
-<p>Note that if you are only interested in files then it is much more efficient to set the filesOnly flag in the options.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_lsjson/">lsjson</a> command for more information on the above and examples.</p>
+<p>Note that if you are only interested in files then it is much more
+efficient to set the filesOnly flag in the options.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_lsjson/">lsjson</a> command for
+more information on the above and examples.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="operations-uploadfile">operations/uploadfile: Upload file using multiform/form-data</h3>
+<h3 id="operations-uploadfile">operations/uploadfile: Upload file using
+multiform/form-data</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>fs - a remote name string e.g. "drive:"</li>
 <li>remote - a path within that remote e.g. "dir"</li>
 <li>each part in body represents a file to be uploaded</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_uploadfile/">uploadfile</a> command for more information on the above.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_uploadfile/">uploadfile</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="options-blocks">options/blocks: List all the option blocks</h3>
 <p>Returns: - options - a list of the options block names</p>
 <h3 id="options-get">options/get: Get all the global options</h3>
-<p>Returns an object where keys are option block names and values are an object with the current option values in.</p>
+<p>Returns an object where keys are option block names and values are an
+object with the current option values in.</p>
 <p>Parameters:</p>
 <ul>
 <li>blocks: optional string of comma separated blocks to include
@@ -9765,10 +16668,17 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
 <li>all are included if this is missing or ""</li>
 </ul></li>
 </ul>
-<p>Note that these are the global options which are unaffected by use of the _config and _filter parameters. If you wish to read the parameters set in _config then use options/config and for _filter use options/filter.</p>
-<p>This shows the internal names of the option within rclone which should map to the external options very easily with a few exceptions.</p>
-<h3 id="options-info">options/info: Get info about all the global options</h3>
-<p>Returns an object where keys are option block names and values are an array of objects with info about each options.</p>
+<p>Note that these are the global options which are unaffected by use of
+the _config and _filter parameters. If you wish to read the parameters
+set in _config then use options/config and for _filter use
+options/filter.</p>
+<p>This shows the internal names of the option within rclone which
+should map to the external options very easily with a few
+exceptions.</p>
+<h3 id="options-info">options/info: Get info about all the global
+options</h3>
+<p>Returns an object where keys are option block names and values are an
+array of objects with info about each options.</p>
 <p>Parameters:</p>
 <ul>
 <li>blocks: optional string of comma separated blocks to include
@@ -9776,12 +16686,22 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
 <li>all are included if this is missing or ""</li>
 </ul></li>
 </ul>
-<p>These objects are in the same format as returned by "config/providers". They are described in the <a href="#option-blocks">option blocks</a> section.</p>
-<h3 id="options-local">options/local: Get the currently active config for this call</h3>
-<p>Returns an object with the keys "config" and "filter". The "config" key contains the local config and the "filter" key contains the local filters.</p>
-<p>Note that these are the local options specific to this rc call. If _config was not supplied then they will be the global options. Likewise with "_filter".</p>
-<p>This call is mostly useful for seeing if _config and _filter passing is working.</p>
-<p>This shows the internal names of the option within rclone which should map to the external options very easily with a few exceptions.</p>
+<p>These objects are in the same format as returned by
+"config/providers". They are described in the <a
+href="#option-blocks">option blocks</a> section.</p>
+<h3 id="options-local">options/local: Get the currently active config
+for this call</h3>
+<p>Returns an object with the keys "config" and "filter". The "config"
+key contains the local config and the "filter" key contains the local
+filters.</p>
+<p>Note that these are the local options specific to this rc call. If
+_config was not supplied then they will be the global options. Likewise
+with "_filter".</p>
+<p>This call is mostly useful for seeing if _config and _filter passing
+is working.</p>
+<p>This shows the internal names of the option within rclone which
+should map to the external options very easily with a few
+exceptions.</p>
 <h3 id="options-set">options/set: Set an option</h3>
 <p>Parameters:</p>
 <ul>
@@ -9791,51 +16711,65 @@ rclone rc mount/mount fs=TestDrive: mountPoint=/mnt/tmp vfsOpt=&#39;{&quot;Cache
 </ul></li>
 </ul>
 <p>Repeated as often as required.</p>
-<p>Only supply the options you wish to change. If an option is unknown it will be silently ignored. Not all options will have an effect when changed like this.</p>
+<p>Only supply the options you wish to change. If an option is unknown
+it will be silently ignored. Not all options will have an effect when
+changed like this.</p>
 <p>For example:</p>
-<p>This sets DEBUG level logs (-vv) (these can be set by number or string)</p>
+<p>This sets DEBUG level logs (-vv) (these can be set by number or
+string)</p>
 <pre><code>rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: &quot;DEBUG&quot;}}&#39;
 rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 8}}&#39;</code></pre>
 <p>And this sets INFO level logs (-v)</p>
 <pre><code>rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: &quot;INFO&quot;}}&#39;</code></pre>
 <p>And this sets NOTICE level logs (normal without -v)</p>
 <pre><code>rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: &quot;NOTICE&quot;}}&#39;</code></pre>
-<h3 id="pluginsctl-addPlugin">pluginsctl/addPlugin: Add a plugin using url</h3>
+<h3 id="pluginsctl-addPlugin">pluginsctl/addPlugin: Add a plugin using
+url</h3>
 <p>Used for adding a plugin to the webgui.</p>
 <p>This takes the following parameters:</p>
 <ul>
-<li>url - http url of the github repo where the plugin is hosted (http://github.com/rclone/rclone-webui-react).</li>
+<li>url - http url of the github repo where the plugin is hosted
+(http://github.com/rclone/rclone-webui-react).</li>
 </ul>
 <p>Example:</p>
 <p>rclone rc pluginsctl/addPlugin</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="pluginsctl-getPluginsForType">pluginsctl/getPluginsForType: Get plugins with type criteria</h3>
+<h3 id="pluginsctl-getPluginsForType">pluginsctl/getPluginsForType: Get
+plugins with type criteria</h3>
 <p>This shows all possible plugins by a mime type.</p>
 <p>This takes the following parameters:</p>
 <ul>
-<li>type - supported mime type by a loaded plugin e.g. (video/mp4, audio/mp3).</li>
-<li>pluginType - filter plugins based on their type e.g. (DASHBOARD, FILE_HANDLER, TERMINAL).</li>
+<li>type - supported mime type by a loaded plugin e.g. (video/mp4,
+audio/mp3).</li>
+<li>pluginType - filter plugins based on their type e.g. (DASHBOARD,
+FILE_HANDLER, TERMINAL).</li>
 </ul>
 <p>Returns:</p>
 <ul>
 <li>loadedPlugins - list of current production plugins.</li>
-<li>testPlugins - list of temporarily loaded development plugins, usually running on a different server.</li>
+<li>testPlugins - list of temporarily loaded development plugins,
+usually running on a different server.</li>
 </ul>
 <p>Example:</p>
 <p>rclone rc pluginsctl/getPluginsForType type=video/mp4</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="pluginsctl-listPlugins">pluginsctl/listPlugins: Get the list of currently loaded plugins</h3>
-<p>This allows you to get the currently enabled plugins and their details.</p>
+<h3 id="pluginsctl-listPlugins">pluginsctl/listPlugins: Get the list of
+currently loaded plugins</h3>
+<p>This allows you to get the currently enabled plugins and their
+details.</p>
 <p>This takes no parameters and returns:</p>
 <ul>
 <li>loadedPlugins - list of current production plugins.</li>
-<li>testPlugins - list of temporarily loaded development plugins, usually running on a different server.</li>
+<li>testPlugins - list of temporarily loaded development plugins,
+usually running on a different server.</li>
 </ul>
 <p>E.g.</p>
 <p>rclone rc pluginsctl/listPlugins</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="pluginsctl-listTestPlugins">pluginsctl/listTestPlugins: Show currently loaded test plugins</h3>
-<p>Allows listing of test plugins with the rclone.test set to true in package.json of the plugin.</p>
+<h3 id="pluginsctl-listTestPlugins">pluginsctl/listTestPlugins: Show
+currently loaded test plugins</h3>
+<p>Allows listing of test plugins with the rclone.test set to true in
+package.json of the plugin.</p>
 <p>This takes no parameters and returns:</p>
 <ul>
 <li>loadedTestPlugins - list of currently available test plugins.</li>
@@ -9843,106 +16777,168 @@ rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 8}}&
 <p>E.g.</p>
 <pre><code>rclone rc pluginsctl/listTestPlugins</code></pre>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="pluginsctl-removePlugin">pluginsctl/removePlugin: Remove a loaded plugin</h3>
+<h3 id="pluginsctl-removePlugin">pluginsctl/removePlugin: Remove a
+loaded plugin</h3>
 <p>This allows you to remove a plugin using it's name.</p>
 <p>This takes parameters:</p>
 <ul>
-<li>name - name of the plugin in the format <code>author</code>/<code>plugin_name</code>.</li>
+<li>name - name of the plugin in the format
+<code>author</code>/<code>plugin_name</code>.</li>
 </ul>
 <p>E.g.</p>
 <p>rclone rc pluginsctl/removePlugin name=rclone/video-plugin</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="pluginsctl-removeTestPlugin">pluginsctl/removeTestPlugin: Remove a test plugin</h3>
+<h3 id="pluginsctl-removeTestPlugin">pluginsctl/removeTestPlugin: Remove
+a test plugin</h3>
 <p>This allows you to remove a plugin using it's name.</p>
 <p>This takes the following parameters:</p>
 <ul>
-<li>name - name of the plugin in the format <code>author</code>/<code>plugin_name</code>.</li>
+<li>name - name of the plugin in the format
+<code>author</code>/<code>plugin_name</code>.</li>
 </ul>
 <p>Example:</p>
 <pre><code>rclone rc pluginsctl/removeTestPlugin name=rclone/rclone-webui-react</code></pre>
 <p><strong>Authentication is required for this call.</strong></p>
 <h3 id="rc-error">rc/error: This returns an error</h3>
-<p>This returns an error with the input as part of its error string. Useful for testing error handling.</p>
-<h3 id="rc-list">rc/list: List all the registered remote control commands</h3>
-<p>This lists all the registered remote control commands as a JSON map in the commands response.</p>
+<p>This returns an error with the input as part of its error string.
+Useful for testing error handling.</p>
+<h3 id="rc-list">rc/list: List all the registered remote control
+commands</h3>
+<p>This lists all the registered remote control commands as a JSON map
+in the commands response.</p>
 <h3 id="rc-noop">rc/noop: Echo the input to the output parameters</h3>
-<p>This echoes the input parameters to the output parameters for testing purposes. It can be used to check that rclone is still alive and to check that parameter passing is working properly.</p>
-<h3 id="rc-noopauth">rc/noopauth: Echo the input to the output parameters requiring auth</h3>
-<p>This echoes the input parameters to the output parameters for testing purposes. It can be used to check that rclone is still alive and to check that parameter passing is working properly.</p>
+<p>This echoes the input parameters to the output parameters for testing
+purposes. It can be used to check that rclone is still alive and to
+check that parameter passing is working properly.</p>
+<h3 id="rc-noopauth">rc/noopauth: Echo the input to the output
+parameters requiring auth</h3>
+<p>This echoes the input parameters to the output parameters for testing
+purposes. It can be used to check that rclone is still alive and to
+check that parameter passing is working properly.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="sync-bisync">sync/bisync: Perform bidirectional synchronization between two paths.</h3>
+<h3 id="sync-bisync">sync/bisync: Perform bidirectional synchronization
+between two paths.</h3>
 <p>This takes the following parameters</p>
 <ul>
 <li>path1 - a remote directory string e.g. <code>drive:path1</code></li>
 <li>path2 - a remote directory string e.g. <code>drive:path2</code></li>
 <li>dryRun - dry-run mode</li>
 <li>resync - performs the resync run</li>
-<li>checkAccess - abort if RCLONE_TEST files are not found on both filesystems</li>
-<li>checkFilename - file name for checkAccess (default: RCLONE_TEST)</li>
-<li>maxDelete - abort sync if percentage of deleted files is above this threshold (default: 50)</li>
+<li>checkAccess - abort if RCLONE_TEST files are not found on both
+filesystems</li>
+<li>checkFilename - file name for checkAccess (default:
+RCLONE_TEST)</li>
+<li>maxDelete - abort sync if percentage of deleted files is above this
+threshold (default: 50)</li>
 <li>force - Bypass maxDelete safety check and run the sync</li>
-<li>checkSync - <code>true</code> by default, <code>false</code> disables comparison of final listings, <code>only</code> will skip sync, only compare listings from the last run</li>
-<li>createEmptySrcDirs - Sync creation and deletion of empty directories. (Not compatible with --remove-empty-dirs)</li>
-<li>removeEmptyDirs - remove empty directories at the final cleanup step</li>
+<li>checkSync - <code>true</code> by default, <code>false</code>
+disables comparison of final listings, <code>only</code> will skip sync,
+only compare listings from the last run</li>
+<li>createEmptySrcDirs - Sync creation and deletion of empty
+directories. (Not compatible with --remove-empty-dirs)</li>
+<li>removeEmptyDirs - remove empty directories at the final cleanup
+step</li>
 <li>filtersFile - read filtering patterns from a file</li>
 <li>ignoreListingChecksum - Do not use checksums for listings</li>
-<li>resilient - Allow future runs to retry after certain less-serious errors, instead of requiring resync. Use at your own risk!</li>
-<li>workdir - server directory for history files (default: <code>~/.cache/rclone/bisync</code>)</li>
-<li>backupdir1 - --backup-dir for Path1. Must be a non-overlapping path on the same remote.</li>
-<li>backupdir2 - --backup-dir for Path2. Must be a non-overlapping path on the same remote.</li>
+<li>resilient - Allow future runs to retry after certain less-serious
+errors, instead of requiring resync. Use at your own risk!</li>
+<li>workdir - server directory for history files (default:
+<code>~/.cache/rclone/bisync</code>)</li>
+<li>backupdir1 - --backup-dir for Path1. Must be a non-overlapping path
+on the same remote.</li>
+<li>backupdir2 - --backup-dir for Path2. Must be a non-overlapping path
+on the same remote.</li>
 <li>noCleanup - retain working files</li>
 </ul>
-<p>See <a href="https://rclone.org/commands/rclone_bisync/">bisync command help</a> and <a href="https://rclone.org/bisync/">full bisync description</a> for more information.</p>
+<p>See <a href="https://rclone.org/commands/rclone_bisync/">bisync
+command help</a> and <a href="https://rclone.org/bisync/">full bisync
+description</a> for more information.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="sync-copy">sync/copy: copy a directory from source remote to destination remote</h3>
+<h3 id="sync-copy">sync/copy: copy a directory from source remote to
+destination remote</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>srcFs - a remote name string e.g. "drive:src" for the source</li>
-<li>dstFs - a remote name string e.g. "drive:dst" for the destination</li>
-<li>createEmptySrcDirs - create empty src directories on destination if set</li>
+<li>dstFs - a remote name string e.g. "drive:dst" for the
+destination</li>
+<li>createEmptySrcDirs - create empty src directories on destination if
+set</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_copy/">copy</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_copy/">copy</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="sync-move">sync/move: move a directory from source remote to destination remote</h3>
+<h3 id="sync-move">sync/move: move a directory from source remote to
+destination remote</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>srcFs - a remote name string e.g. "drive:src" for the source</li>
-<li>dstFs - a remote name string e.g. "drive:dst" for the destination</li>
-<li>createEmptySrcDirs - create empty src directories on destination if set</li>
+<li>dstFs - a remote name string e.g. "drive:dst" for the
+destination</li>
+<li>createEmptySrcDirs - create empty src directories on destination if
+set</li>
 <li>deleteEmptySrcDirs - delete empty src directories if set</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_move/">move</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_move/">move</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="sync-sync">sync/sync: sync a directory from source remote to destination remote</h3>
+<h3 id="sync-sync">sync/sync: sync a directory from source remote to
+destination remote</h3>
 <p>This takes the following parameters:</p>
 <ul>
 <li>srcFs - a remote name string e.g. "drive:src" for the source</li>
-<li>dstFs - a remote name string e.g. "drive:dst" for the destination</li>
-<li>createEmptySrcDirs - create empty src directories on destination if set</li>
+<li>dstFs - a remote name string e.g. "drive:dst" for the
+destination</li>
+<li>createEmptySrcDirs - create empty src directories on destination if
+set</li>
 </ul>
-<p>See the <a href="https://rclone.org/commands/rclone_sync/">sync</a> command for more information on the above.</p>
+<p>See the <a href="https://rclone.org/commands/rclone_sync/">sync</a>
+command for more information on the above.</p>
 <p><strong>Authentication is required for this call.</strong></p>
-<h3 id="vfs-forget">vfs/forget: Forget files or directories in the directory cache.</h3>
-<p>This forgets the paths in the directory cache causing them to be re-read from the remote when needed.</p>
-<p>If no paths are passed in then it will forget all the paths in the directory cache.</p>
+<h3 id="vfs-forget">vfs/forget: Forget files or directories in the
+directory cache.</h3>
+<p>This forgets the paths in the directory cache causing them to be
+re-read from the remote when needed.</p>
+<p>If no paths are passed in then it will forget all the paths in the
+directory cache.</p>
 <pre><code>rclone rc vfs/forget</code></pre>
-<p>Otherwise pass files or dirs in as file=path or dir=path. Any parameter key starting with file will forget that file and any starting with dir will forget that dir, e.g.</p>
+<p>Otherwise pass files or dirs in as file=path or dir=path. Any
+parameter key starting with file will forget that file and any starting
+with dir will forget that dir, e.g.</p>
 <pre><code>rclone rc vfs/forget file=hello file2=goodbye dir=home/junk</code></pre>
-<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
+<p>This command takes an "fs" parameter. If this parameter is not
+supplied and if there is only one VFS in use then that VFS will be used.
+If there is more than one VFS in use then the "fs" parameter must be
+supplied.</p>
 <h3 id="vfs-list">vfs/list: List active VFSes.</h3>
 <p>This lists the active VFSes.</p>
-<p>It returns a list under the key "vfses" where the values are the VFS names that could be passed to the other VFS commands in the "fs" parameter.</p>
-<h3 id="vfs-poll-interval">vfs/poll-interval: Get the status or update the value of the poll-interval option.</h3>
-<p>Without any parameter given this returns the current status of the poll-interval setting.</p>
-<p>When the interval=duration parameter is set, the poll-interval value is updated and the polling function is notified. Setting interval=0 disables poll-interval.</p>
+<p>It returns a list under the key "vfses" where the values are the VFS
+names that could be passed to the other VFS commands in the "fs"
+parameter.</p>
+<h3 id="vfs-poll-interval">vfs/poll-interval: Get the status or update
+the value of the poll-interval option.</h3>
+<p>Without any parameter given this returns the current status of the
+poll-interval setting.</p>
+<p>When the interval=duration parameter is set, the poll-interval value
+is updated and the polling function is notified. Setting interval=0
+disables poll-interval.</p>
 <pre><code>rclone rc vfs/poll-interval interval=5m</code></pre>
-<p>The timeout=duration parameter can be used to specify a time to wait for the current poll function to apply the new value. If timeout is less or equal 0, which is the default, wait indefinitely.</p>
-<p>The new poll-interval value will only be active when the timeout is not reached.</p>
-<p>If poll-interval is updated or disabled temporarily, some changes might not get picked up by the polling function, depending on the used remote.</p>
-<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
+<p>The timeout=duration parameter can be used to specify a time to wait
+for the current poll function to apply the new value. If timeout is less
+or equal 0, which is the default, wait indefinitely.</p>
+<p>The new poll-interval value will only be active when the timeout is
+not reached.</p>
+<p>If poll-interval is updated or disabled temporarily, some changes
+might not get picked up by the polling function, depending on the used
+remote.</p>
+<p>This command takes an "fs" parameter. If this parameter is not
+supplied and if there is only one VFS in use then that VFS will be used.
+If there is more than one VFS in use then the "fs" parameter must be
+supplied.</p>
 <h3 id="vfs-queue">vfs/queue: Queue info for a VFS.</h3>
 <p>This returns info about the upload queue for the selected VFS.</p>
-<p>This is only useful if <code>--vfs-cache-mode</code> &gt; off. If you call it when the <code>--vfs-cache-mode</code> is off, it will return an empty result.</p>
+<p>This is only useful if <code>--vfs-cache-mode</code> &gt; off. If you
+call it when the <code>--vfs-cache-mode</code> is off, it will return an
+empty result.</p>
 <pre><code>{
     &quot;queued&quot;: // an array of files queued for upload
     [
@@ -9957,29 +16953,61 @@ rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 8}}&
         },
    ],
 }</code></pre>
-<p>The <code>expiry</code> time is the time until the file is elegible for being uploaded in floating point seconds. This may go negative. As rclone only transfers <code>--transfers</code> files at once, only the lowest <code>--transfers</code> expiry times will have <code>uploading</code> as <code>true</code>. So there may be files with negative expiry times for which <code>uploading</code> is <code>false</code>.</p>
-<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
-<h3 id="vfs-queue-set-expiry">vfs/queue-set-expiry: Set the expiry time for an item queued for upload.</h3>
-<p>Use this to adjust the <code>expiry</code> time for an item in the upload queue. You will need to read the <code>id</code> of the item using <code>vfs/queue</code> before using this call.</p>
-<p>You can then set <code>expiry</code> to a floating point number of seconds from now when the item is eligible for upload. If you want the item to be uploaded as soon as possible then set it to a large negative number (eg -1000000000). If you want the upload of the item to be delayed for a long time then set it to a large positive number.</p>
-<p>Setting the <code>expiry</code> of an item which has already has started uploading will have no effect - the item will carry on being uploaded.</p>
-<p>This will return an error if called with <code>--vfs-cache-mode</code> off or if the <code>id</code> passed is not found.</p>
+<p>The <code>expiry</code> time is the time until the file is elegible
+for being uploaded in floating point seconds. This may go negative. As
+rclone only transfers <code>--transfers</code> files at once, only the
+lowest <code>--transfers</code> expiry times will have
+<code>uploading</code> as <code>true</code>. So there may be files with
+negative expiry times for which <code>uploading</code> is
+<code>false</code>.</p>
+<p>This command takes an "fs" parameter. If this parameter is not
+supplied and if there is only one VFS in use then that VFS will be used.
+If there is more than one VFS in use then the "fs" parameter must be
+supplied.</p>
+<h3 id="vfs-queue-set-expiry">vfs/queue-set-expiry: Set the expiry time
+for an item queued for upload.</h3>
+<p>Use this to adjust the <code>expiry</code> time for an item in the
+upload queue. You will need to read the <code>id</code> of the item
+using <code>vfs/queue</code> before using this call.</p>
+<p>You can then set <code>expiry</code> to a floating point number of
+seconds from now when the item is eligible for upload. If you want the
+item to be uploaded as soon as possible then set it to a large negative
+number (eg -1000000000). If you want the upload of the item to be
+delayed for a long time then set it to a large positive number.</p>
+<p>Setting the <code>expiry</code> of an item which has already has
+started uploading will have no effect - the item will carry on being
+uploaded.</p>
+<p>This will return an error if called with
+<code>--vfs-cache-mode</code> off or if the <code>id</code> passed is
+not found.</p>
 <p>This takes the following parameters</p>
 <ul>
 <li><code>fs</code> - select the VFS in use (optional)</li>
-<li><code>id</code> - a numeric ID as returned from <code>vfs/queue</code></li>
-<li><code>expiry</code> - a new expiry time as floating point seconds</li>
+<li><code>id</code> - a numeric ID as returned from
+<code>vfs/queue</code></li>
+<li><code>expiry</code> - a new expiry time as floating point
+seconds</li>
 </ul>
 <p>This returns an empty result on success, or an error.</p>
-<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
+<p>This command takes an "fs" parameter. If this parameter is not
+supplied and if there is only one VFS in use then that VFS will be used.
+If there is more than one VFS in use then the "fs" parameter must be
+supplied.</p>
 <h3 id="vfs-refresh">vfs/refresh: Refresh the directory cache.</h3>
-<p>This reads the directories for the specified paths and freshens the directory cache.</p>
-<p>If no paths are passed in then it will refresh the root directory.</p>
+<p>This reads the directories for the specified paths and freshens the
+directory cache.</p>
+<p>If no paths are passed in then it will refresh the root
+directory.</p>
 <pre><code>rclone rc vfs/refresh</code></pre>
-<p>Otherwise pass directories in as dir=path. Any parameter key starting with dir will refresh that directory, e.g.</p>
+<p>Otherwise pass directories in as dir=path. Any parameter key starting
+with dir will refresh that directory, e.g.</p>
 <pre><code>rclone rc vfs/refresh dir=home/junk dir2=data/misc</code></pre>
-<p>If the parameter recursive=true is given the whole directory tree will get refreshed. This refresh will use --fast-list if enabled.</p>
-<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
+<p>If the parameter recursive=true is given the whole directory tree
+will get refreshed. This refresh will use --fast-list if enabled.</p>
+<p>This command takes an "fs" parameter. If this parameter is not
+supplied and if there is only one VFS in use then that VFS will be used.
+If there is more than one VFS in use then the "fs" parameter must be
+supplied.</p>
 <h3 id="vfs-stats">vfs/stats: Stats for a VFS.</h3>
 <p>This returns stats for the selected VFS.</p>
 <pre><code>{
@@ -10009,15 +17037,26 @@ rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 8}}&
         &quot;WriteWait&quot;: 1000000000
     }
 }</code></pre>
-<p>This command takes an "fs" parameter. If this parameter is not supplied and if there is only one VFS in use then that VFS will be used. If there is more than one VFS in use then the "fs" parameter must be supplied.</p>
+<p>This command takes an "fs" parameter. If this parameter is not
+supplied and if there is only one VFS in use then that VFS will be used.
+If there is more than one VFS in use then the "fs" parameter must be
+supplied.</p>
 <h2 id="api-http">Accessing the remote control via HTTP</h2>
 <p>Rclone implements a simple HTTP based protocol.</p>
-<p>Each endpoint takes an JSON object and returns a JSON object or an error. The JSON objects are essentially a map of string names to values.</p>
+<p>Each endpoint takes an JSON object and returns a JSON object or an
+error. The JSON objects are essentially a map of string names to
+values.</p>
 <p>All calls must made using POST.</p>
-<p>The input objects can be supplied using URL parameters, POST parameters or by supplying "Content-Type: application/json" and a JSON blob in the body. There are examples of these below using <code>curl</code>.</p>
-<p>The response will be a JSON blob in the body of the response. This is formatted to be reasonably human-readable.</p>
+<p>The input objects can be supplied using URL parameters, POST
+parameters or by supplying "Content-Type: application/json" and a JSON
+blob in the body. There are examples of these below using
+<code>curl</code>.</p>
+<p>The response will be a JSON blob in the body of the response. This is
+formatted to be reasonably human-readable.</p>
 <h3 id="error-returns">Error returns</h3>
-<p>If an error occurs then there will be an HTTP error status (e.g. 500) and the body of the response will contain a JSON encoded error object, e.g.</p>
+<p>If an error occurs then there will be an HTTP error status (e.g. 500)
+and the body of the response will contain a JSON encoded error object,
+e.g.</p>
 <pre><code>{
     &quot;error&quot;: &quot;Expecting string value for key \&quot;remote\&quot; (was float64)&quot;,
     &quot;input&quot;: {
@@ -10027,10 +17066,15 @@ rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 8}}&
     &quot;status&quot;: 400
     &quot;path&quot;: &quot;operations/rmdir&quot;,
 }</code></pre>
-<p>The keys in the error response are - error - error string - input - the input parameters to the call - status - the HTTP status code - path - the path of the call</p>
+<p>The keys in the error response are - error - error string - input -
+the input parameters to the call - status - the HTTP status code - path
+- the path of the call</p>
 <h3 id="cors">CORS</h3>
-<p>The sever implements basic CORS support and allows all origins for that. The response to a preflight OPTIONS request will echo the requested "Access-Control-Request-Headers" back.</p>
-<h3 id="using-post-with-url-parameters-only">Using POST with URL parameters only</h3>
+<p>The sever implements basic CORS support and allows all origins for
+that. The response to a preflight OPTIONS request will echo the
+requested "Access-Control-Request-Headers" back.</p>
+<h3 id="using-post-with-url-parameters-only">Using POST with URL
+parameters only</h3>
 <pre><code>curl -X POST &#39;http://localhost:5572/rc/noop?potato=1&amp;sausage=2&#39;</code></pre>
 <p>Response</p>
 <pre><code>{
@@ -10046,7 +17090,8 @@ rclone rc options/set --json &#39;{&quot;main&quot;: {&quot;LogLevel&quot;: 8}}&
         &quot;sausage&quot;: &quot;2&quot;
     }
 }</code></pre>
-<p>Note that curl doesn't return errors to the shell unless you use the <code>-f</code> option</p>
+<p>Note that curl doesn't return errors to the shell unless you use the
+<code>-f</code> option</p>
 <pre><code>$ curl -f -X POST &#39;http://localhost:5572/rc/error?potato=1&amp;sausage=2&#39;
 curl: (22) The requested URL returned error: 400 Bad Request
 $ echo $?
@@ -10058,7 +17103,8 @@ $ echo $?
     &quot;potato&quot;: &quot;1&quot;,
     &quot;sausage&quot;: &quot;2&quot;
 }</code></pre>
-<p>Note that you can combine these with URL parameters too with the POST parameters taking precedence.</p>
+<p>Note that you can combine these with URL parameters too with the POST
+parameters taking precedence.</p>
 <pre><code>curl --data &quot;potato=1&quot; --data &quot;sausage=2&quot; &quot;http://localhost:5572/rc/noop?rutabaga=3&amp;sausage=4&quot;</code></pre>
 <p>Response</p>
 <pre><code>{
@@ -10074,7 +17120,8 @@ $ echo $?
     &quot;password&quot;: &quot;xyz&quot;,
     &quot;username&quot;: &quot;xyz&quot;
 }</code></pre>
-<p>This can be combined with URL parameters too if required. The JSON blob takes precedence.</p>
+<p>This can be combined with URL parameters too if required. The JSON
+blob takes precedence.</p>
 <pre><code>curl -H &quot;Content-Type: application/json&quot; -X POST -d &#39;{&quot;potato&quot;:2,&quot;sausage&quot;:1}&#39; &#39;http://localhost:5572/rc/noop?rutabaga=3&amp;potato=4&#39;</code></pre>
 <pre><code>{
     &quot;potato&quot;: 2,
@@ -10082,13 +17129,17 @@ $ echo $?
     &quot;sausage&quot;: 1
 }</code></pre>
 <h2 id="debugging-rclone-with-pprof">Debugging rclone with pprof</h2>
-<p>If you use the <code>--rc</code> flag this will also enable the use of the go profiling tools on the same port.</p>
-<p>To use these, first <a href="https://golang.org/doc/install">install go</a>.</p>
+<p>If you use the <code>--rc</code> flag this will also enable the use
+of the go profiling tools on the same port.</p>
+<p>To use these, first <a href="https://golang.org/doc/install">install
+go</a>.</p>
 <h3 id="debugging-memory-use">Debugging memory use</h3>
 <p>To profile rclone's memory use you can run:</p>
 <pre><code>go tool pprof -web http://localhost:5572/debug/pprof/heap</code></pre>
-<p>This should open a page in your browser showing what is using what memory.</p>
-<p>You can also use the <code>-text</code> flag to produce a textual summary</p>
+<p>This should open a page in your browser showing what is using what
+memory.</p>
+<p>You can also use the <code>-text</code> flag to produce a textual
+summary</p>
 <pre><code>$ go tool pprof -text http://localhost:5572/debug/pprof/heap
 Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
       flat  flat%   sum%        cum   cum%
@@ -10105,36 +17156,66 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
          0     0%   100%      513kB 33.38%  net/http.(*conn).serve
          0     0%   100%  1024.03kB 66.62%  runtime.main</code></pre>
 <h3 id="debugging-go-routine-leaks">Debugging go routine leaks</h3>
-<p>Memory leaks are most often caused by go routine leaks keeping memory alive which should have been garbage collected.</p>
+<p>Memory leaks are most often caused by go routine leaks keeping memory
+alive which should have been garbage collected.</p>
 <p>See all active go routines using</p>
 <pre><code>curl http://localhost:5572/debug/pprof/goroutine?debug=1</code></pre>
-<p>Or go to http://localhost:5572/debug/pprof/goroutine?debug=1 in your browser.</p>
+<p>Or go to http://localhost:5572/debug/pprof/goroutine?debug=1 in your
+browser.</p>
 <h3 id="other-profiles-to-look-at">Other profiles to look at</h3>
-<p>You can see a summary of profiles available at http://localhost:5572/debug/pprof/</p>
+<p>You can see a summary of profiles available at
+http://localhost:5572/debug/pprof/</p>
 <p>Here is how to use some of them:</p>
 <ul>
-<li>Memory: <code>go tool pprof http://localhost:5572/debug/pprof/heap</code></li>
-<li>Go routines: <code>curl http://localhost:5572/debug/pprof/goroutine?debug=1</code></li>
-<li>30-second CPU profile: <code>go tool pprof http://localhost:5572/debug/pprof/profile</code></li>
-<li>5-second execution trace: <code>wget http://localhost:5572/debug/pprof/trace?seconds=5</code></li>
+<li>Memory:
+<code>go tool pprof http://localhost:5572/debug/pprof/heap</code></li>
+<li>Go routines:
+<code>curl http://localhost:5572/debug/pprof/goroutine?debug=1</code></li>
+<li>30-second CPU profile:
+<code>go tool pprof http://localhost:5572/debug/pprof/profile</code></li>
+<li>5-second execution trace:
+<code>wget http://localhost:5572/debug/pprof/trace?seconds=5</code></li>
 <li>Goroutine blocking profile
 <ul>
-<li>Enable first with: <code>rclone rc debug/set-block-profile-rate rate=1</code> (<a href="#debug-set-block-profile-rate">docs</a>)</li>
+<li>Enable first with:
+<code>rclone rc debug/set-block-profile-rate rate=1</code> (<a
+href="#debug-set-block-profile-rate">docs</a>)</li>
 <li><code>go tool pprof http://localhost:5572/debug/pprof/block</code></li>
 </ul></li>
 <li>Contended mutexes:
 <ul>
-<li>Enable first with: <code>rclone rc debug/set-mutex-profile-fraction rate=1</code> (<a href="#debug-set-mutex-profile-fraction">docs</a>)</li>
+<li>Enable first with:
+<code>rclone rc debug/set-mutex-profile-fraction rate=1</code> (<a
+href="#debug-set-mutex-profile-fraction">docs</a>)</li>
 <li><code>go tool pprof http://localhost:5572/debug/pprof/mutex</code></li>
 </ul></li>
 </ul>
-<p>See the <a href="https://golang.org/pkg/net/http/pprof/">net/http/pprof docs</a> for more info on how to use the profiling and for a general overview see <a href="https://blog.golang.org/profiling-go-programs">the Go team's blog post on profiling go programs</a>.</p>
-<p>The profiling hook is <a href="https://stackoverflow.com/q/26545159/164234">zero overhead unless it is used</a>.</p>
-<h1 id="overview-of-cloud-storage-systems">Overview of cloud storage systems</h1>
-<p>Each cloud storage system is slightly different. Rclone attempts to provide a unified interface to them, but some underlying differences show through.</p>
+<p>See the <a
+href="https://golang.org/pkg/net/http/pprof/">net/http/pprof docs</a>
+for more info on how to use the profiling and for a general overview see
+<a href="https://blog.golang.org/profiling-go-programs">the Go team's
+blog post on profiling go programs</a>.</p>
+<p>The profiling hook is <a
+href="https://stackoverflow.com/q/26545159/164234">zero overhead unless
+it is used</a>.</p>
+<h1 id="overview-of-cloud-storage-systems">Overview of cloud storage
+systems</h1>
+<p>Each cloud storage system is slightly different. Rclone attempts to
+provide a unified interface to them, but some underlying differences
+show through.</p>
 <h2 id="features-1">Features</h2>
-<p>Here is an overview of the major features of each cloud storage system.</p>
+<p>Here is an overview of the major features of each cloud storage
+system.</p>
 <table>
+<colgroup>
+<col style="width: 25%" />
+<col style="width: 16%" />
+<col style="width: 8%" />
+<col style="width: 16%" />
+<col style="width: 15%" />
+<col style="width: 9%" />
+<col style="width: 8%" />
+</colgroup>
 <thead>
 <tr class="header">
 <th>Name</th>
@@ -10599,24 +17680,59 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tr>
 </tbody>
 </table>
-<p>¹ Dropbox supports <a href="https://www.dropbox.com/developers/reference/content-hash">its own custom hash</a>. This is an SHA256 sum of all the 4 MiB block SHA256s.</p>
-<p>² SFTP supports checksums if the same login has shell access and <code>md5sum</code> or <code>sha1sum</code> as well as <code>echo</code> are in the remote's PATH.</p>
-<p>³ WebDAV supports hashes when used with Fastmail Files, Owncloud and Nextcloud only.</p>
-<p>⁴ WebDAV supports modtimes when used with Fastmail Files, Owncloud and Nextcloud only.</p>
-<p>⁵ <a href="https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash">QuickXorHash</a> is Microsoft's own hash.</p>
+<p>¹ Dropbox supports <a
+href="https://www.dropbox.com/developers/reference/content-hash">its own
+custom hash</a>. This is an SHA256 sum of all the 4 MiB block
+SHA256s.</p>
+<p>² SFTP supports checksums if the same login has shell access and
+<code>md5sum</code> or <code>sha1sum</code> as well as <code>echo</code>
+are in the remote's PATH.</p>
+<p>³ WebDAV supports hashes when used with Fastmail Files, Owncloud and
+Nextcloud only.</p>
+<p>⁴ WebDAV supports modtimes when used with Fastmail Files, Owncloud
+and Nextcloud only.</p>
+<p>⁵ <a
+href="https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash">QuickXorHash</a>
+is Microsoft's own hash.</p>
 <p>⁶ Mail.ru uses its own modified SHA1 hash</p>
 <p>⁷ pCloud only supports SHA1 (not MD5) in its EU region</p>
-<p>⁸ Opendrive does not support creation of duplicate files using their web client interface or other stock clients, but the underlying storage platform has been determined to allow duplicate files, and it is possible to create them with <code>rclone</code>. It may be that this is a mistake or an unsupported feature.</p>
-<p>⁹ QingStor does not support SetModTime for objects bigger than 5 GiB.</p>
-<p>¹⁰ FTP supports modtimes for the major FTP servers, and also others if they advertised required protocol extensions. See <a href="https://rclone.org/ftp/#modification-times">this</a> for more details.</p>
-<p>¹¹ Internet Archive requires option <code>wait_archive</code> to be set to a non-zero value for full modtime support.</p>
-<p>¹² HiDrive supports <a href="https://static.hidrive.com/dev/0001">its own custom hash</a>. It combines SHA1 sums for each 4 KiB block hierarchically to a single top-level sum.</p>
-<p>¹³ Uloz.to provides server-calculated MD5 hash upon file upload. MD5 and SHA256 hashes are client-calculated and stored as metadata fields.</p>
+<p>⁸ Opendrive does not support creation of duplicate files using their
+web client interface or other stock clients, but the underlying storage
+platform has been determined to allow duplicate files, and it is
+possible to create them with <code>rclone</code>. It may be that this is
+a mistake or an unsupported feature.</p>
+<p>⁹ QingStor does not support SetModTime for objects bigger than 5
+GiB.</p>
+<p>¹⁰ FTP supports modtimes for the major FTP servers, and also others
+if they advertised required protocol extensions. See <a
+href="https://rclone.org/ftp/#modification-times">this</a> for more
+details.</p>
+<p>¹¹ Internet Archive requires option <code>wait_archive</code> to be
+set to a non-zero value for full modtime support.</p>
+<p>¹² HiDrive supports <a href="https://static.hidrive.com/dev/0001">its
+own custom hash</a>. It combines SHA1 sums for each 4 KiB block
+hierarchically to a single top-level sum.</p>
+<p>¹³ Uloz.to provides server-calculated MD5 hash upon file upload. MD5
+and SHA256 hashes are client-calculated and stored as metadata
+fields.</p>
 <h3 id="hash">Hash</h3>
-<p>The cloud storage system supports various hash types of the objects. The hashes are used when transferring data as an integrity check and can be specifically used with the <code>--checksum</code> flag in syncs and in the <code>check</code> command.</p>
-<p>To use the verify checksums when transferring between cloud storage systems they must support a common hash type.</p>
+<p>The cloud storage system supports various hash types of the objects.
+The hashes are used when transferring data as an integrity check and can
+be specifically used with the <code>--checksum</code> flag in syncs and
+in the <code>check</code> command.</p>
+<p>To use the verify checksums when transferring between cloud storage
+systems they must support a common hash type.</p>
 <h3 id="modtime">ModTime</h3>
-<p>Almost all cloud storage systems store some sort of timestamp on objects, but several of them not something that is appropriate to use for syncing. E.g. some backends will only write a timestamp that represents the time of the upload. To be relevant for syncing it should be able to store the modification time of the source object. If this is not the case, rclone will only check the file size by default, though can be configured to check the file hash (with the <code>--checksum</code> flag). Ideally it should also be possible to change the timestamp of an existing file without having to re-upload it.</p>
+<p>Almost all cloud storage systems store some sort of timestamp on
+objects, but several of them not something that is appropriate to use
+for syncing. E.g. some backends will only write a timestamp that
+represents the time of the upload. To be relevant for syncing it should
+be able to store the modification time of the source object. If this is
+not the case, rclone will only check the file size by default, though
+can be configured to check the file hash (with the
+<code>--checksum</code> flag). Ideally it should also be possible to
+change the timestamp of an existing file without having to re-upload
+it.</p>
 <table>
 <colgroup>
 <col style="width: 27%" />
@@ -10635,7 +17751,8 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tr>
 <tr class="even">
 <td><code>R</code></td>
-<td>ModTimes supported on files but can't be changed without re-upload</td>
+<td>ModTimes supported on files but can't be changed without
+re-upload</td>
 </tr>
 <tr class="odd">
 <td><code>R/W</code></td>
@@ -10643,47 +17760,145 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tr>
 <tr class="even">
 <td><code>DR</code></td>
-<td>ModTimes supported on files and directories but can't be changed without re-upload</td>
+<td>ModTimes supported on files and directories but can't be changed
+without re-upload</td>
 </tr>
 <tr class="odd">
 <td><code>DR/W</code></td>
-<td>Read and Write ModTimes fully supported on files and directories</td>
+<td>Read and Write ModTimes fully supported on files and
+directories</td>
 </tr>
 </tbody>
 </table>
-<p>Storage systems with a <code>-</code> in the ModTime column, means the modification read on objects is not the modification time of the file when uploaded. It is most likely the time the file was uploaded, or possibly something else (like the time the picture was taken in Google Photos).</p>
-<p>Storage systems with a <code>R</code> (for read-only) in the ModTime column, means the it keeps modification times on objects, and updates them when uploading objects, but it does not support changing only the modification time (<code>SetModTime</code> operation) without re-uploading, possibly not even without deleting existing first. Some operations in rclone, such as <code>copy</code> and <code>sync</code> commands, will automatically check for <code>SetModTime</code> support and re-upload if necessary to keep the modification times in sync. Other commands will not work without <code>SetModTime</code> support, e.g. <code>touch</code> command on an existing file will fail, and changes to modification time only on a files in a <code>mount</code> will be silently ignored.</p>
-<p>Storage systems with <code>R/W</code> (for read/write) in the ModTime column, means they do also support modtime-only operations.</p>
-<p>Storage systems with <code>D</code> in the ModTime column means that the following symbols apply to directories as well as files.</p>
+<p>Storage systems with a <code>-</code> in the ModTime column, means
+the modification read on objects is not the modification time of the
+file when uploaded. It is most likely the time the file was uploaded, or
+possibly something else (like the time the picture was taken in Google
+Photos).</p>
+<p>Storage systems with a <code>R</code> (for read-only) in the ModTime
+column, means the it keeps modification times on objects, and updates
+them when uploading objects, but it does not support changing only the
+modification time (<code>SetModTime</code> operation) without
+re-uploading, possibly not even without deleting existing first. Some
+operations in rclone, such as <code>copy</code> and <code>sync</code>
+commands, will automatically check for <code>SetModTime</code> support
+and re-upload if necessary to keep the modification times in sync. Other
+commands will not work without <code>SetModTime</code> support, e.g.
+<code>touch</code> command on an existing file will fail, and changes to
+modification time only on a files in a <code>mount</code> will be
+silently ignored.</p>
+<p>Storage systems with <code>R/W</code> (for read/write) in the ModTime
+column, means they do also support modtime-only operations.</p>
+<p>Storage systems with <code>D</code> in the ModTime column means that
+the following symbols apply to directories as well as files.</p>
 <h3 id="case-insensitive">Case Insensitive</h3>
-<p>If a cloud storage systems is case sensitive then it is possible to have two files which differ only in case, e.g. <code>file.txt</code> and <code>FILE.txt</code>. If a cloud storage system is case insensitive then that isn't possible.</p>
-<p>This can cause problems when syncing between a case insensitive system and a case sensitive system. The symptom of this is that no matter how many times you run the sync it never completes fully.</p>
-<p>The local filesystem and SFTP may or may not be case sensitive depending on OS.</p>
+<p>If a cloud storage systems is case sensitive then it is possible to
+have two files which differ only in case, e.g. <code>file.txt</code> and
+<code>FILE.txt</code>. If a cloud storage system is case insensitive
+then that isn't possible.</p>
+<p>This can cause problems when syncing between a case insensitive
+system and a case sensitive system. The symptom of this is that no
+matter how many times you run the sync it never completes fully.</p>
+<p>The local filesystem and SFTP may or may not be case sensitive
+depending on OS.</p>
 <ul>
 <li>Windows - usually case insensitive, though case is preserved</li>
-<li>OSX - usually case insensitive, though it is possible to format case sensitive</li>
-<li>Linux - usually case sensitive, but there are case insensitive file systems (e.g. FAT formatted USB keys)</li>
+<li>OSX - usually case insensitive, though it is possible to format case
+sensitive</li>
+<li>Linux - usually case sensitive, but there are case insensitive file
+systems (e.g. FAT formatted USB keys)</li>
 </ul>
-<p>Most of the time this doesn't cause any problems as people tend to avoid files whose name differs only by case even on case sensitive systems.</p>
+<p>Most of the time this doesn't cause any problems as people tend to
+avoid files whose name differs only by case even on case sensitive
+systems.</p>
 <h3 id="duplicate-files">Duplicate files</h3>
-<p>If a cloud storage system allows duplicate files then it can have two objects with the same name.</p>
-<p>This confuses rclone greatly when syncing - use the <code>rclone dedupe</code> command to rename or remove duplicates.</p>
+<p>If a cloud storage system allows duplicate files then it can have two
+objects with the same name.</p>
+<p>This confuses rclone greatly when syncing - use the
+<code>rclone dedupe</code> command to rename or remove duplicates.</p>
 <h3 id="restricted-filenames">Restricted filenames</h3>
-<p>Some cloud storage systems might have restrictions on the characters that are usable in file or directory names. When <code>rclone</code> detects such a name during a file upload, it will transparently replace the restricted characters with similar looking Unicode characters. To handle the different sets of restricted characters for different backends, rclone uses something it calls <a href="#encoding">encoding</a>.</p>
-<p>This process is designed to avoid ambiguous file names as much as possible and allow to move files between many cloud storage systems transparently.</p>
-<p>The name shown by <code>rclone</code> to the user or during log output will only contain a minimal set of <a href="#restricted-characters">replaced characters</a> to ensure correct formatting and not necessarily the actual name used on the cloud storage.</p>
-<p>This transformation is reversed when downloading a file or parsing <code>rclone</code> arguments. For example, when uploading a file named <code>my file?.txt</code> to Onedrive, it will be displayed as <code>my file?.txt</code> on the console, but stored as <code>my file？.txt</code> to Onedrive (the <code>?</code> gets replaced by the similar looking <code>？</code> character, the so-called "fullwidth question mark"). The reverse transformation allows to read a file <code>unusual/name.txt</code> from Google Drive, by passing the name <code>unusual／name.txt</code> on the command line (the <code>/</code> needs to be replaced by the similar looking <code>／</code> character).</p>
+<p>Some cloud storage systems might have restrictions on the characters
+that are usable in file or directory names. When <code>rclone</code>
+detects such a name during a file upload, it will transparently replace
+the restricted characters with similar looking Unicode characters. To
+handle the different sets of restricted characters for different
+backends, rclone uses something it calls <a
+href="#encoding">encoding</a>.</p>
+<p>This process is designed to avoid ambiguous file names as much as
+possible and allow to move files between many cloud storage systems
+transparently.</p>
+<p>The name shown by <code>rclone</code> to the user or during log
+output will only contain a minimal set of <a
+href="#restricted-characters">replaced characters</a> to ensure correct
+formatting and not necessarily the actual name used on the cloud
+storage.</p>
+<p>This transformation is reversed when downloading a file or parsing
+<code>rclone</code> arguments. For example, when uploading a file named
+<code>my file?.txt</code> to Onedrive, it will be displayed as
+<code>my file?.txt</code> on the console, but stored as
+<code>my file？.txt</code> to Onedrive (the <code>?</code> gets replaced
+by the similar looking <code>？</code> character, the so-called
+"fullwidth question mark"). The reverse transformation allows to read a
+file <code>unusual/name.txt</code> from Google Drive, by passing the
+name <code>unusual／name.txt</code> on the command line (the
+<code>/</code> needs to be replaced by the similar looking
+<code>／</code> character).</p>
 <h4 id="restricted-filenames-caveats">Caveats</h4>
-<p>The filename encoding system works well in most cases, at least where file names are written in English or similar languages. You might not even notice it: It just works. In some cases it may lead to issues, though. E.g. when file names are written in Chinese, or Japanese, where it is always the Unicode fullwidth variants of the punctuation marks that are used.</p>
-<p>On Windows, the characters <code>:</code>, <code>*</code> and <code>?</code> are examples of restricted characters. If these are used in filenames on a remote that supports it, Rclone will transparently convert them to their fullwidth Unicode variants <code>＊</code>, <code>？</code> and <code>：</code> when downloading to Windows, and back again when uploading. This way files with names that are not allowed on Windows can still be stored.</p>
-<p>However, if you have files on your Windows system originally with these same Unicode characters in their names, they will be included in the same conversion process. E.g. if you create a file in your Windows filesystem with name <code>Test：1.jpg</code>, where <code>：</code> is the Unicode fullwidth colon symbol, and use rclone to upload it to Google Drive, which supports regular <code>:</code> (halfwidth question mark), rclone will replace the fullwidth <code>:</code> with the halfwidth <code>:</code> and store the file as <code>Test:1.jpg</code> in Google Drive. Since both Windows and Google Drive allows the name <code>Test：1.jpg</code>, it would probably be better if rclone just kept the name as is in this case.</p>
-<p>With the opposite situation; if you have a file named <code>Test:1.jpg</code>, in your Google Drive, e.g. uploaded from a Linux system where <code>:</code> is valid in file names. Then later use rclone to copy this file to your Windows computer you will notice that on your local disk it gets renamed to <code>Test：1.jpg</code>. The original filename is not legal on Windows, due to the <code>:</code>, and rclone therefore renames it to make the copy possible. That is all good. However, this can also lead to an issue: If you already had a <em>different</em> file named <code>Test：1.jpg</code> on Windows, and then use rclone to copy either way. Rclone will then treat the file originally named <code>Test:1.jpg</code> on Google Drive and the file originally named <code>Test：1.jpg</code> on Windows as the same file, and replace the contents from one with the other.</p>
-<p>Its virtually impossible to handle all cases like these correctly in all situations, but by customizing the <a href="#encoding">encoding option</a>, changing the set of characters that rclone should convert, you should be able to create a configuration that works well for your specific situation. See also the <a href="https://rclone.org/overview/#encoding-example-windows">example</a> below.</p>
-<p>(Windows was used as an example of a file system with many restricted characters, and Google drive a storage system with few.)</p>
+<p>The filename encoding system works well in most cases, at least where
+file names are written in English or similar languages. You might not
+even notice it: It just works. In some cases it may lead to issues,
+though. E.g. when file names are written in Chinese, or Japanese, where
+it is always the Unicode fullwidth variants of the punctuation marks
+that are used.</p>
+<p>On Windows, the characters <code>:</code>, <code>*</code> and
+<code>?</code> are examples of restricted characters. If these are used
+in filenames on a remote that supports it, Rclone will transparently
+convert them to their fullwidth Unicode variants <code>＊</code>,
+<code>？</code> and <code>：</code> when downloading to Windows, and
+back again when uploading. This way files with names that are not
+allowed on Windows can still be stored.</p>
+<p>However, if you have files on your Windows system originally with
+these same Unicode characters in their names, they will be included in
+the same conversion process. E.g. if you create a file in your Windows
+filesystem with name <code>Test：1.jpg</code>, where <code>：</code> is
+the Unicode fullwidth colon symbol, and use rclone to upload it to
+Google Drive, which supports regular <code>:</code> (halfwidth question
+mark), rclone will replace the fullwidth <code>:</code> with the
+halfwidth <code>:</code> and store the file as <code>Test:1.jpg</code>
+in Google Drive. Since both Windows and Google Drive allows the name
+<code>Test：1.jpg</code>, it would probably be better if rclone just
+kept the name as is in this case.</p>
+<p>With the opposite situation; if you have a file named
+<code>Test:1.jpg</code>, in your Google Drive, e.g. uploaded from a
+Linux system where <code>:</code> is valid in file names. Then later use
+rclone to copy this file to your Windows computer you will notice that
+on your local disk it gets renamed to <code>Test：1.jpg</code>. The
+original filename is not legal on Windows, due to the <code>:</code>,
+and rclone therefore renames it to make the copy possible. That is all
+good. However, this can also lead to an issue: If you already had a
+<em>different</em> file named <code>Test：1.jpg</code> on Windows, and
+then use rclone to copy either way. Rclone will then treat the file
+originally named <code>Test:1.jpg</code> on Google Drive and the file
+originally named <code>Test：1.jpg</code> on Windows as the same file,
+and replace the contents from one with the other.</p>
+<p>Its virtually impossible to handle all cases like these correctly in
+all situations, but by customizing the <a href="#encoding">encoding
+option</a>, changing the set of characters that rclone should convert,
+you should be able to create a configuration that works well for your
+specific situation. See also the <a
+href="https://rclone.org/overview/#encoding-example-windows">example</a>
+below.</p>
+<p>(Windows was used as an example of a file system with many restricted
+characters, and Google drive a storage system with few.)</p>
 <h4 id="restricted-characters">Default restricted characters</h4>
-<p>The table below shows the characters that are replaced by default.</p>
-<p>When a replacement character is found in a filename, this character will be escaped with the <code>‛</code> character to avoid ambiguous file names. (e.g. a file named <code>␀.txt</code> would shown as <code>‛␀.txt</code>)</p>
-<p>Each cloud storage backend can use a different set of characters, which will be specified in the documentation for each backend.</p>
+<p>The table below shows the characters that are replaced by
+default.</p>
+<p>When a replacement character is found in a filename, this character
+will be escaped with the <code>‛</code> character to avoid ambiguous
+file names. (e.g. a file named <code>␀.txt</code> would shown as
+<code>‛␀.txt</code>)</p>
+<p>Each cloud storage backend can use a different set of characters,
+which will be specified in the documentation for each backend.</p>
 <table>
 <thead>
 <tr class="header">
@@ -10865,7 +18080,8 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tr>
 </tbody>
 </table>
-<p>The default encoding will also encode these file names as they are problematic with many cloud storage systems.</p>
+<p>The default encoding will also encode these file names as they are
+problematic with many cloud storage systems.</p>
 <table>
 <thead>
 <tr class="header">
@@ -10885,15 +18101,40 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tbody>
 </table>
 <h4 id="invalid-utf8">Invalid UTF-8 bytes</h4>
-<p>Some backends only support a sequence of well formed UTF-8 bytes as file or directory names.</p>
-<p>In this case all invalid UTF-8 bytes will be replaced with a quoted representation of the byte value to allow uploading a file to such a backend. For example, the invalid byte <code>0xFE</code> will be encoded as <code>‛FE</code>.</p>
-<p>A common source of invalid UTF-8 bytes are local filesystems, that store names in a different encoding than UTF-8 or UTF-16, like latin1. See the <a href="https://rclone.org/local/#filenames">local filenames</a> section for details.</p>
+<p>Some backends only support a sequence of well formed UTF-8 bytes as
+file or directory names.</p>
+<p>In this case all invalid UTF-8 bytes will be replaced with a quoted
+representation of the byte value to allow uploading a file to such a
+backend. For example, the invalid byte <code>0xFE</code> will be encoded
+as <code>‛FE</code>.</p>
+<p>A common source of invalid UTF-8 bytes are local filesystems, that
+store names in a different encoding than UTF-8 or UTF-16, like latin1.
+See the <a href="https://rclone.org/local/#filenames">local
+filenames</a> section for details.</p>
 <h4 id="encoding">Encoding option</h4>
-<p>Most backends have an encoding option, specified as a flag <code>--backend-encoding</code> where <code>backend</code> is the name of the backend, or as a config parameter <code>encoding</code> (you'll need to select the Advanced config in <code>rclone config</code> to see it).</p>
-<p>This will have default value which encodes and decodes characters in such a way as to preserve the maximum number of characters (see above).</p>
-<p>However this can be incorrect in some scenarios, for example if you have a Windows file system with Unicode fullwidth characters <code>＊</code>, <code>？</code> or <code>：</code>, that you want to remain as those characters on the remote rather than being translated to regular (halfwidth) <code>*</code>, <code>?</code> and <code>:</code>.</p>
-<p>The <code>--backend-encoding</code> flags allow you to change that. You can disable the encoding completely with <code>--backend-encoding Raw</code> or set <code>encoding = Raw</code> in the config file.</p>
-<p>Encoding takes a comma separated list of encodings. You can see the list of all possible values by passing an invalid value to this flag, e.g. <code>--local-encoding "help"</code>. The command <code>rclone help flags encoding</code> will show you the defaults for the backends.</p>
+<p>Most backends have an encoding option, specified as a flag
+<code>--backend-encoding</code> where <code>backend</code> is the name
+of the backend, or as a config parameter <code>encoding</code> (you'll
+need to select the Advanced config in <code>rclone config</code> to see
+it).</p>
+<p>This will have default value which encodes and decodes characters in
+such a way as to preserve the maximum number of characters (see
+above).</p>
+<p>However this can be incorrect in some scenarios, for example if you
+have a Windows file system with Unicode fullwidth characters
+<code>＊</code>, <code>？</code> or <code>：</code>, that you want to
+remain as those characters on the remote rather than being translated to
+regular (halfwidth) <code>*</code>, <code>?</code> and
+<code>:</code>.</p>
+<p>The <code>--backend-encoding</code> flags allow you to change that.
+You can disable the encoding completely with
+<code>--backend-encoding Raw</code> or set <code>encoding = Raw</code>
+in the config file.</p>
+<p>Encoding takes a comma separated list of encodings. You can see the
+list of all possible values by passing an invalid value to this flag,
+e.g. <code>--local-encoding "help"</code>. The command
+<code>rclone help flags encoding</code> will show you the defaults for
+the backends.</p>
 <table>
 <colgroup>
 <col style="width: 31%" />
@@ -11055,31 +18296,71 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tr>
 </tbody>
 </table>
-<p>¹ Encoding from NUL 0x00 to ␀ is always implicit except when using Raw. It was previously incorrectly documented as disabling encoding, and to maintain backward compatibility, its behavior has not been changed.</p>
+<p>¹ Encoding from NUL 0x00 to ␀ is always implicit except when using
+Raw. It was previously incorrectly documented as disabling encoding, and
+to maintain backward compatibility, its behavior has not been
+changed.</p>
 <h5 id="encoding-example-ftp">Encoding example: FTP</h5>
 <p>To take a specific example, the FTP backend's default encoding is</p>
 <pre><code>--ftp-encoding &quot;Slash,Del,Ctl,RightSpace,Dot&quot;</code></pre>
-<p>However, let's say the FTP server is running on Windows and can't have any of the invalid Windows characters in file names. You are backing up Linux servers to this FTP server which do have those characters in file names. So you would add the Windows set which are</p>
+<p>However, let's say the FTP server is running on Windows and can't
+have any of the invalid Windows characters in file names. You are
+backing up Linux servers to this FTP server which do have those
+characters in file names. So you would add the Windows set which are</p>
 <pre><code>Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot</code></pre>
 <p>to the existing ones, giving:</p>
 <pre><code>Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot,Del,RightSpace</code></pre>
-<p>This can be specified using the <code>--ftp-encoding</code> flag or using an <code>encoding</code> parameter in the config file.</p>
+<p>This can be specified using the <code>--ftp-encoding</code> flag or
+using an <code>encoding</code> parameter in the config file.</p>
 <h5 id="encoding-example-windows">Encoding example: Windows</h5>
-<p>As a nother example, take a Windows system where there is a file with name <code>Test：1.jpg</code>, where <code>：</code> is the Unicode fullwidth colon symbol. When using rclone to copy this to a remote which supports <code>:</code>, the regular (halfwidth) colon (such as Google Drive), you will notice that the file gets renamed to <code>Test:1.jpg</code>.</p>
-<p>To avoid this you can change the set of characters rclone should convert for the local filesystem, using command-line argument <code>--local-encoding</code>. Rclone's default behavior on Windows corresponds to</p>
+<p>As a nother example, take a Windows system where there is a file with
+name <code>Test：1.jpg</code>, where <code>：</code> is the Unicode
+fullwidth colon symbol. When using rclone to copy this to a remote which
+supports <code>:</code>, the regular (halfwidth) colon (such as Google
+Drive), you will notice that the file gets renamed to
+<code>Test:1.jpg</code>.</p>
+<p>To avoid this you can change the set of characters rclone should
+convert for the local filesystem, using command-line argument
+<code>--local-encoding</code>. Rclone's default behavior on Windows
+corresponds to</p>
 <pre><code>--local-encoding &quot;Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot&quot;</code></pre>
-<p>If you want to use fullwidth characters <code>：</code>, <code>＊</code> and <code>？</code> in your filenames without rclone changing them when uploading to a remote, then set the same as the default value but without <code>Colon,Question,Asterisk</code>:</p>
+<p>If you want to use fullwidth characters <code>：</code>,
+<code>＊</code> and <code>？</code> in your filenames without rclone
+changing them when uploading to a remote, then set the same as the
+default value but without <code>Colon,Question,Asterisk</code>:</p>
 <pre><code>--local-encoding &quot;Slash,LtGt,DoubleQuote,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot&quot;</code></pre>
-<p>Alternatively, you can disable the conversion of any characters with <code>--local-encoding Raw</code>.</p>
-<p>Instead of using command-line argument <code>--local-encoding</code>, you may also set it as <a href="https://rclone.org/docs/#environment-variables">environment variable</a> <code>RCLONE_LOCAL_ENCODING</code>, or <a href="https://rclone.org/docs/#configure">configure</a> a remote of type <code>local</code> in your config, and set the <code>encoding</code> option there.</p>
-<p>The risk by doing this is that if you have a filename with the regular (halfwidth) <code>:</code>, <code>*</code> and <code>?</code> in your cloud storage, and you try to download it to your Windows filesystem, this will fail. These characters are not valid in filenames on Windows, and you have told rclone not to work around this by converting them to valid fullwidth variants.</p>
+<p>Alternatively, you can disable the conversion of any characters with
+<code>--local-encoding Raw</code>.</p>
+<p>Instead of using command-line argument <code>--local-encoding</code>,
+you may also set it as <a
+href="https://rclone.org/docs/#environment-variables">environment
+variable</a> <code>RCLONE_LOCAL_ENCODING</code>, or <a
+href="https://rclone.org/docs/#configure">configure</a> a remote of type
+<code>local</code> in your config, and set the <code>encoding</code>
+option there.</p>
+<p>The risk by doing this is that if you have a filename with the
+regular (halfwidth) <code>:</code>, <code>*</code> and <code>?</code> in
+your cloud storage, and you try to download it to your Windows
+filesystem, this will fail. These characters are not valid in filenames
+on Windows, and you have told rclone not to work around this by
+converting them to valid fullwidth variants.</p>
 <h3 id="mime-type">MIME Type</h3>
-<p>MIME types (also known as media types) classify types of documents using a simple text classification, e.g. <code>text/html</code> or <code>application/pdf</code>.</p>
-<p>Some cloud storage systems support reading (<code>R</code>) the MIME type of objects and some support writing (<code>W</code>) the MIME type of objects.</p>
-<p>The MIME type can be important if you are serving files directly to HTTP from the storage system.</p>
-<p>If you are copying from a remote which supports reading (<code>R</code>) to a remote which supports writing (<code>W</code>) then rclone will preserve the MIME types. Otherwise they will be guessed from the extension, or the remote itself may assign the MIME type.</p>
+<p>MIME types (also known as media types) classify types of documents
+using a simple text classification, e.g. <code>text/html</code> or
+<code>application/pdf</code>.</p>
+<p>Some cloud storage systems support reading (<code>R</code>) the MIME
+type of objects and some support writing (<code>W</code>) the MIME type
+of objects.</p>
+<p>The MIME type can be important if you are serving files directly to
+HTTP from the storage system.</p>
+<p>If you are copying from a remote which supports reading
+(<code>R</code>) to a remote which supports writing (<code>W</code>)
+then rclone will preserve the MIME types. Otherwise they will be guessed
+from the extension, or the remote itself may assign the MIME type.</p>
 <h3 id="metadata-1">Metadata</h3>
-<p>Backends may or may support reading or writing metadata. They may support reading and writing system metadata (metadata intrinsic to that backend) and/or user metadata (general purpose metadata).</p>
+<p>Backends may or may support reading or writing metadata. They may
+support reading and writing system metadata (metadata intrinsic to that
+backend) and/or user metadata (general purpose metadata).</p>
 <p>The levels of metadata support are</p>
 <table>
 <colgroup>
@@ -11103,7 +18384,8 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tr>
 <tr class="odd">
 <td><code>RWU</code></td>
-<td>Read and write System Metadata and read and write User Metadata on files only</td>
+<td>Read and write System Metadata and read and write User Metadata on
+files only</td>
 </tr>
 <tr class="even">
 <td><code>DR</code></td>
@@ -11115,13 +18397,16 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tr>
 <tr class="even">
 <td><code>DRWU</code></td>
-<td>Read and write System Metadata and read and write User Metadata on files and directories</td>
+<td>Read and write System Metadata and read and write User Metadata on
+files and directories</td>
 </tr>
 </tbody>
 </table>
-<p>See <a href="https://rclone.org/docs/#metadata">the metadata docs</a> for more info.</p>
+<p>See <a href="https://rclone.org/docs/#metadata">the metadata docs</a>
+for more info.</p>
 <h2 id="optional-features">Optional Features</h2>
-<p>All rclone remotes support a base command set. Other features depend upon backend-specific capabilities.</p>
+<p>All rclone remotes support a base command set. Other features depend
+upon backend-specific capabilities.</p>
 <table style="width:100%;">
 <colgroup>
 <col style="width: 20%" />
@@ -11856,42 +19141,81 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
 </tr>
 </tbody>
 </table>
-<p>¹ Note Swift implements this in order to delete directory markers but it doesn't actually have a quicker way of deleting files other than deleting them individually.</p>
-<p>² Storj implements this efficiently only for entire buckets. If purging a directory inside a bucket, files are deleted individually.</p>
+<p>¹ Note Swift implements this in order to delete directory markers but
+it doesn't actually have a quicker way of deleting files other than
+deleting them individually.</p>
+<p>² Storj implements this efficiently only for entire buckets. If
+purging a directory inside a bucket, files are deleted individually.</p>
 <p>³ StreamUpload is not supported with Nextcloud</p>
 <p>⁴ Use the <code>--sftp-copy-is-hardlink</code> flag to enable.</p>
 <p>⁵ Use the <code>--onedrive-delta</code> flag to enable.</p>
 <h3 id="purge">Purge</h3>
-<p>This deletes a directory quicker than just deleting all the files in the directory.</p>
+<p>This deletes a directory quicker than just deleting all the files in
+the directory.</p>
 <h3 id="copy">Copy</h3>
-<p>Used when copying an object to and from the same remote. This known as a server-side copy so you can copy a file without downloading it and uploading it again. It is used if you use <code>rclone copy</code> or <code>rclone move</code> if the remote doesn't support <code>Move</code> directly.</p>
-<p>If the server doesn't support <code>Copy</code> directly then for copy operations the file is downloaded then re-uploaded.</p>
+<p>Used when copying an object to and from the same remote. This known
+as a server-side copy so you can copy a file without downloading it and
+uploading it again. It is used if you use <code>rclone copy</code> or
+<code>rclone move</code> if the remote doesn't support <code>Move</code>
+directly.</p>
+<p>If the server doesn't support <code>Copy</code> directly then for
+copy operations the file is downloaded then re-uploaded.</p>
 <h3 id="move">Move</h3>
-<p>Used when moving/renaming an object on the same remote. This is known as a server-side move of a file. This is used in <code>rclone move</code> if the server doesn't support <code>DirMove</code>.</p>
-<p>If the server isn't capable of <code>Move</code> then rclone simulates it with <code>Copy</code> then delete. If the server doesn't support <code>Copy</code> then rclone will download the file and re-upload it.</p>
+<p>Used when moving/renaming an object on the same remote. This is known
+as a server-side move of a file. This is used in
+<code>rclone move</code> if the server doesn't support
+<code>DirMove</code>.</p>
+<p>If the server isn't capable of <code>Move</code> then rclone
+simulates it with <code>Copy</code> then delete. If the server doesn't
+support <code>Copy</code> then rclone will download the file and
+re-upload it.</p>
 <h3 id="dirmove">DirMove</h3>
-<p>This is used to implement <code>rclone move</code> to move a directory if possible. If it isn't then it will use <code>Move</code> on each file (which falls back to <code>Copy</code> then download and upload - see <code>Move</code> section).</p>
+<p>This is used to implement <code>rclone move</code> to move a
+directory if possible. If it isn't then it will use <code>Move</code> on
+each file (which falls back to <code>Copy</code> then download and
+upload - see <code>Move</code> section).</p>
 <h3 id="cleanup">CleanUp</h3>
-<p>This is used for emptying the trash for a remote by <code>rclone cleanup</code>.</p>
-<p>If the server can't do <code>CleanUp</code> then <code>rclone cleanup</code> will return an error.</p>
-<p>‡‡ Note that while Box implements this it has to delete every file individually so it will be slower than emptying the trash via the WebUI</p>
+<p>This is used for emptying the trash for a remote by
+<code>rclone cleanup</code>.</p>
+<p>If the server can't do <code>CleanUp</code> then
+<code>rclone cleanup</code> will return an error.</p>
+<p>‡‡ Note that while Box implements this it has to delete every file
+individually so it will be slower than emptying the trash via the
+WebUI</p>
 <h3 id="listr">ListR</h3>
-<p>The remote supports a recursive list to list all the contents beneath a directory quickly. This enables the <code>--fast-list</code> flag to work. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
+<p>The remote supports a recursive list to list all the contents beneath
+a directory quickly. This enables the <code>--fast-list</code> flag to
+work. See the <a href="https://rclone.org/docs/#fast-list">rclone
+docs</a> for more details.</p>
 <h3 id="streamupload">StreamUpload</h3>
-<p>Some remotes allow files to be uploaded without knowing the file size in advance. This allows certain operations to work without spooling the file to local disk first, e.g. <code>rclone rcat</code>.</p>
+<p>Some remotes allow files to be uploaded without knowing the file size
+in advance. This allows certain operations to work without spooling the
+file to local disk first, e.g. <code>rclone rcat</code>.</p>
 <h3 id="multithreadupload">MultithreadUpload</h3>
-<p>Some remotes allow transfers to the remote to be sent as chunks in parallel. If this is supported then rclone will use multi-thread copying to transfer files much faster.</p>
+<p>Some remotes allow transfers to the remote to be sent as chunks in
+parallel. If this is supported then rclone will use multi-thread copying
+to transfer files much faster.</p>
 <h3 id="linksharing">LinkSharing</h3>
-<p>Sets the necessary permissions on a file or folder and prints a link that allows others to access them, even if they don't have an account on the particular cloud provider.</p>
+<p>Sets the necessary permissions on a file or folder and prints a link
+that allows others to access them, even if they don't have an account on
+the particular cloud provider.</p>
 <h3 id="about-1">About</h3>
-<p>Rclone <code>about</code> prints quota information for a remote. Typical output includes bytes used, free, quota and in trash.</p>
-<p>If a remote lacks about capability <code>rclone about remote:</code>returns an error.</p>
-<p>Backends without about capability cannot determine free space for an rclone mount, or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/commands/rclone_about/">rclone about command</a></p>
+<p>Rclone <code>about</code> prints quota information for a remote.
+Typical output includes bytes used, free, quota and in trash.</p>
+<p>If a remote lacks about capability
+<code>rclone about remote:</code>returns an error.</p>
+<p>Backends without about capability cannot determine free space for an
+rclone mount, or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/commands/rclone_about/">rclone about
+command</a></p>
 <h3 id="emptydir">EmptyDir</h3>
-<p>The remote supports empty directories. See <a href="https://rclone.org/bugs/#limitations">Limitations</a> for details. Most Object/Bucket-based remotes do not support this.</p>
+<p>The remote supports empty directories. See <a
+href="https://rclone.org/bugs/#limitations">Limitations</a> for details.
+Most Object/Bucket-based remotes do not support this.</p>
 <h1 id="global-flags">Global Flags</h1>
-<p>This describes the global flags available to every rclone command split into groups.</p>
+<p>This describes the global flags available to every rclone command
+split into groups.</p>
 <h2 id="copy-1">Copy</h2>
 <p>Flags for anything which can copy a file.</p>
 <pre><code>      --check-first                                 Do all the checks before starting transfers
@@ -11970,7 +19294,7 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
       --tpslimit float                     Limit HTTP transactions per second to this
       --tpslimit-burst int                 Max burst of transactions for --tpslimit (default 1)
       --use-cookies                        Enable session cookiejar
-      --user-agent string                  Set the user-agent to a specified string (default &quot;rclone/v1.68.2&quot;)</code></pre>
+      --user-agent string                  Set the user-agent to a specified string (default &quot;rclone/v1.68.2-beta.8331.25cf42493.feature/add-frostfs-support&quot;)</code></pre>
 <h2 id="performance">Performance</h2>
 <p>Flags helpful for increasing performance.</p>
 <pre><code>      --buffer-size SizeSuffix   In memory buffer size when reading files for each --transfer (default 16Mi)
@@ -12347,6 +19671,21 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
       --filescom-password string                            The password used to authenticate with Files.com (obscured)
       --filescom-site string                                Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com)
       --filescom-username string                            The username used to authenticate with Files.com
+      --frostfs-address string                              Address of account
+      --frostfs-ape-cache-invalidation-duration Duration    APE cache invalidation duration (default 8s)
+      --frostfs-ape-cache-invalidation-timeout Duration     APE cache invalidation timeout (default 24s)
+      --frostfs-ape-chain-check-interval Duration           The interval for verifying that the APE chain is saved in FrostFS (default 500ms)
+      --frostfs-connection-timeout Duration                 FrostFS connection timeout (default 4s)
+      --frostfs-container-creation-policy string            Container creation policy for new containers (default &quot;private&quot;)
+      --frostfs-description string                          Description of the remote
+      --frostfs-endpoint string                             Endpoints to connect to FrostFS node
+      --frostfs-password string                             Password to decrypt wallet
+      --frostfs-placement-policy string                     Placement policy for new containers (default &quot;REP 3&quot;)
+      --frostfs-rebalance-interval Duration                 FrostFS rebalance connections interval (default 15s)
+      --frostfs-request-timeout Duration                    FrostFS request timeout (default 12s)
+      --frostfs-rpc-endpoint string                         Endpoint to connect to Neo rpc node
+      --frostfs-session-expiration int                      FrostFS session expiration epoch (default 4294967295)
+      --frostfs-wallet string                               Path to wallet
       --ftp-ask-password                                    Allow asking for FTP password when needed
       --ftp-close-timeout Duration                          Maximum time to wait for a response to close (default 1m0s)
       --ftp-concurrency int                                 Maximum number of FTP simultaneous connections, 0 for unlimited
@@ -12874,38 +20213,103 @@ Showing nodes accounting for 1537.03kB, 100% of 1537.03kB total
       --zoho-token-url string                               Token server url</code></pre>
 <h1 id="docker-volume-plugin">Docker Volume Plugin</h1>
 <h2 id="introduction">Introduction</h2>
-<p>Docker 1.9 has added support for creating <a href="https://docs.docker.com/storage/volumes/">named volumes</a> via <a href="https://docs.docker.com/engine/reference/commandline/volume_create/">command-line interface</a> and mounting them in containers as a way to share data between them. Since Docker 1.10 you can create named volumes with <a href="https://docs.docker.com/compose/">Docker Compose</a> by descriptions in <a href="https://docs.docker.com/compose/compose-file/compose-file-v2/#volume-configuration-reference">docker-compose.yml</a> files for use by container groups on a single host. As of Docker 1.12 volumes are supported by <a href="https://docs.docker.com/engine/swarm/key-concepts/">Docker Swarm</a> included with Docker Engine and created from descriptions in <a href="https://docs.docker.com/compose/compose-file/compose-file-v3/#volume-configuration-reference">swarm compose v3</a> files for use with <em>swarm stacks</em> across multiple cluster nodes.</p>
-<p><a href="https://docs.docker.com/engine/extend/plugins_volume/">Docker Volume Plugins</a> augment the default <code>local</code> volume driver included in Docker with stateful volumes shared across containers and hosts. Unlike local volumes, your data will <em>not</em> be deleted when such volume is removed. Plugins can run managed by the docker daemon, as a native system service (under systemd, <em>sysv</em> or <em>upstart</em>) or as a standalone executable. Rclone can run as docker volume plugin in all these modes. It interacts with the local docker daemon via <a href="https://docs.docker.com/engine/extend/plugin_api/">plugin API</a> and handles mounting of remote file systems into docker containers so it must run on the same host as the docker daemon or on every Swarm node.</p>
+<p>Docker 1.9 has added support for creating <a
+href="https://docs.docker.com/storage/volumes/">named volumes</a> via <a
+href="https://docs.docker.com/engine/reference/commandline/volume_create/">command-line
+interface</a> and mounting them in containers as a way to share data
+between them. Since Docker 1.10 you can create named volumes with <a
+href="https://docs.docker.com/compose/">Docker Compose</a> by
+descriptions in <a
+href="https://docs.docker.com/compose/compose-file/compose-file-v2/#volume-configuration-reference">docker-compose.yml</a>
+files for use by container groups on a single host. As of Docker 1.12
+volumes are supported by <a
+href="https://docs.docker.com/engine/swarm/key-concepts/">Docker
+Swarm</a> included with Docker Engine and created from descriptions in
+<a
+href="https://docs.docker.com/compose/compose-file/compose-file-v3/#volume-configuration-reference">swarm
+compose v3</a> files for use with <em>swarm stacks</em> across multiple
+cluster nodes.</p>
+<p><a
+href="https://docs.docker.com/engine/extend/plugins_volume/">Docker
+Volume Plugins</a> augment the default <code>local</code> volume driver
+included in Docker with stateful volumes shared across containers and
+hosts. Unlike local volumes, your data will <em>not</em> be deleted when
+such volume is removed. Plugins can run managed by the docker daemon, as
+a native system service (under systemd, <em>sysv</em> or
+<em>upstart</em>) or as a standalone executable. Rclone can run as
+docker volume plugin in all these modes. It interacts with the local
+docker daemon via <a
+href="https://docs.docker.com/engine/extend/plugin_api/">plugin API</a>
+and handles mounting of remote file systems into docker containers so it
+must run on the same host as the docker daemon or on every Swarm
+node.</p>
 <h2 id="getting-started">Getting started</h2>
-<p>In the first example we will use the <a href="https://rclone.org/sftp/">SFTP</a> rclone volume with Docker engine on a standalone Ubuntu machine.</p>
-<p>Start from <a href="https://docs.docker.com/engine/install/">installing Docker</a> on the host.</p>
-<p>The <em>FUSE</em> driver is a prerequisite for rclone mounting and should be installed on host:</p>
+<p>In the first example we will use the <a
+href="https://rclone.org/sftp/">SFTP</a> rclone volume with Docker
+engine on a standalone Ubuntu machine.</p>
+<p>Start from <a
+href="https://docs.docker.com/engine/install/">installing Docker</a> on
+the host.</p>
+<p>The <em>FUSE</em> driver is a prerequisite for rclone mounting and
+should be installed on host:</p>
 <pre><code>sudo apt-get -y install fuse</code></pre>
 <p>Create two directories required by rclone docker plugin:</p>
 <pre><code>sudo mkdir -p /var/lib/docker-plugins/rclone/config
 sudo mkdir -p /var/lib/docker-plugins/rclone/cache</code></pre>
-<p>Install the managed rclone docker plugin for your architecture (here <code>amd64</code>):</p>
+<p>Install the managed rclone docker plugin for your architecture (here
+<code>amd64</code>):</p>
 <pre><code>docker plugin install rclone/docker-volume-rclone:amd64 args=&quot;-v&quot; --alias rclone --grant-all-permissions
 docker plugin list</code></pre>
-<p>Create your <a href="https://rclone.org/sftp/#standard-options">SFTP volume</a>:</p>
+<p>Create your <a href="https://rclone.org/sftp/#standard-options">SFTP
+volume</a>:</p>
 <pre><code>docker volume create firstvolume -d rclone -o type=sftp -o sftp-host=_hostname_ -o sftp-user=_username_ -o sftp-pass=_password_ -o allow-other=true</code></pre>
-<p>Note that since all options are static, you don't even have to run <code>rclone config</code> or create the <code>rclone.conf</code> file (but the <code>config</code> directory should still be present). In the simplest case you can use <code>localhost</code> as <em>hostname</em> and your SSH credentials as <em>username</em> and <em>password</em>. You can also change the remote path to your home directory on the host, for example <code>-o path=/home/username</code>.</p>
+<p>Note that since all options are static, you don't even have to run
+<code>rclone config</code> or create the <code>rclone.conf</code> file
+(but the <code>config</code> directory should still be present). In the
+simplest case you can use <code>localhost</code> as <em>hostname</em>
+and your SSH credentials as <em>username</em> and <em>password</em>. You
+can also change the remote path to your home directory on the host, for
+example <code>-o path=/home/username</code>.</p>
 <p>Time to create a test container and mount the volume into it:</p>
 <pre><code>docker run --rm -it -v firstvolume:/mnt --workdir /mnt ubuntu:latest bash</code></pre>
-<p>If all goes well, you will enter the new container and change right to the mounted SFTP remote. You can type <code>ls</code> to list the mounted directory or otherwise play with it. Type <code>exit</code> when you are done. The container will stop but the volume will stay, ready to be reused. When it's not needed anymore, remove it:</p>
+<p>If all goes well, you will enter the new container and change right
+to the mounted SFTP remote. You can type <code>ls</code> to list the
+mounted directory or otherwise play with it. Type <code>exit</code> when
+you are done. The container will stop but the volume will stay, ready to
+be reused. When it's not needed anymore, remove it:</p>
 <pre><code>docker volume list
 docker volume remove firstvolume</code></pre>
-<p>Now let us try <strong>something more elaborate</strong>: <a href="https://rclone.org/drive/">Google Drive</a> volume on multi-node Docker Swarm.</p>
-<p>You should start from installing Docker and FUSE, creating plugin directories and installing rclone plugin on <em>every</em> swarm node. Then <a href="https://docs.docker.com/engine/swarm/swarm-mode/">setup the Swarm</a>.</p>
-<p>Google Drive volumes need an access token which can be setup via web browser and will be periodically renewed by rclone. The managed plugin cannot run a browser so we will use a technique similar to the <a href="https://rclone.org/remote_setup/">rclone setup on a headless box</a>.</p>
-<p>Run <a href="https://rclone.org/commands/rclone_config_create/">rclone config</a> on <em>another</em> machine equipped with <em>web browser</em> and graphical user interface. Create the <a href="https://rclone.org/drive/#standard-options">Google Drive remote</a>. When done, transfer the resulting <code>rclone.conf</code> to the Swarm cluster and save as <code>/var/lib/docker-plugins/rclone/config/rclone.conf</code> on <em>every</em> node. By default this location is accessible only to the root user so you will need appropriate privileges. The resulting config will look like this:</p>
+<p>Now let us try <strong>something more elaborate</strong>: <a
+href="https://rclone.org/drive/">Google Drive</a> volume on multi-node
+Docker Swarm.</p>
+<p>You should start from installing Docker and FUSE, creating plugin
+directories and installing rclone plugin on <em>every</em> swarm node.
+Then <a href="https://docs.docker.com/engine/swarm/swarm-mode/">setup
+the Swarm</a>.</p>
+<p>Google Drive volumes need an access token which can be setup via web
+browser and will be periodically renewed by rclone. The managed plugin
+cannot run a browser so we will use a technique similar to the <a
+href="https://rclone.org/remote_setup/">rclone setup on a headless
+box</a>.</p>
+<p>Run <a
+href="https://rclone.org/commands/rclone_config_create/">rclone
+config</a> on <em>another</em> machine equipped with <em>web
+browser</em> and graphical user interface. Create the <a
+href="https://rclone.org/drive/#standard-options">Google Drive
+remote</a>. When done, transfer the resulting <code>rclone.conf</code>
+to the Swarm cluster and save as
+<code>/var/lib/docker-plugins/rclone/config/rclone.conf</code> on
+<em>every</em> node. By default this location is accessible only to the
+root user so you will need appropriate privileges. The resulting config
+will look like this:</p>
 <pre><code>[gdrive]
 type = drive
 scope = drive
 drive_id = 1234567...
 root_folder_id = 0Abcd...
 token = {&quot;access_token&quot;:...}</code></pre>
-<p>Now create the file named <code>example.yml</code> with a swarm stack description like this:</p>
+<p>Now create the file named <code>example.yml</code> with a swarm stack
+description like this:</p>
 <pre><code>version: &#39;3&#39;
 services:
   heimdall:
@@ -12922,42 +20326,127 @@ volumes:
       poll_interval: 0</code></pre>
 <p>and run the stack:</p>
 <pre><code>docker stack deploy example -c ./example.yml</code></pre>
-<p>After a few seconds docker will spread the parsed stack description over cluster, create the <code>example_heimdall</code> service on port <em>8080</em>, run service containers on one or more cluster nodes and request the <code>example_configdata</code> volume from rclone plugins on the node hosts. You can use the following commands to confirm results:</p>
+<p>After a few seconds docker will spread the parsed stack description
+over cluster, create the <code>example_heimdall</code> service on port
+<em>8080</em>, run service containers on one or more cluster nodes and
+request the <code>example_configdata</code> volume from rclone plugins
+on the node hosts. You can use the following commands to confirm
+results:</p>
 <pre><code>docker service ls
 docker service ps example_heimdall
 docker volume ls</code></pre>
-<p>Point your browser to <code>http://cluster.host.address:8080</code> and play with the service. Stop it with <code>docker stack remove example</code> when you are done. Note that the <code>example_configdata</code> volume(s) created on demand at the cluster nodes will not be automatically removed together with the stack but stay for future reuse. You can remove them manually by invoking the <code>docker volume remove example_configdata</code> command on every node.</p>
+<p>Point your browser to <code>http://cluster.host.address:8080</code>
+and play with the service. Stop it with
+<code>docker stack remove example</code> when you are done. Note that
+the <code>example_configdata</code> volume(s) created on demand at the
+cluster nodes will not be automatically removed together with the stack
+but stay for future reuse. You can remove them manually by invoking the
+<code>docker volume remove example_configdata</code> command on every
+node.</p>
 <h2 id="creating-volumes-via-cli">Creating Volumes via CLI</h2>
-<p>Volumes can be created with <a href="https://docs.docker.com/engine/reference/commandline/volume_create/">docker volume create</a>. Here are a few examples:</p>
+<p>Volumes can be created with <a
+href="https://docs.docker.com/engine/reference/commandline/volume_create/">docker
+volume create</a>. Here are a few examples:</p>
 <pre><code>docker volume create vol1 -d rclone -o remote=storj: -o vfs-cache-mode=full
 docker volume create vol2 -d rclone -o remote=:storj,access_grant=xxx:heimdall
 docker volume create vol3 -d rclone -o type=storj -o path=heimdall -o storj-access-grant=xxx -o poll-interval=0</code></pre>
-<p>Note the <code>-d rclone</code> flag that tells docker to request volume from the rclone driver. This works even if you installed managed driver by its full name <code>rclone/docker-volume-rclone</code> because you provided the <code>--alias rclone</code> option.</p>
+<p>Note the <code>-d rclone</code> flag that tells docker to request
+volume from the rclone driver. This works even if you installed managed
+driver by its full name <code>rclone/docker-volume-rclone</code> because
+you provided the <code>--alias rclone</code> option.</p>
 <p>Volumes can be inspected as follows:</p>
 <pre><code>docker volume list
 docker volume inspect vol1</code></pre>
 <h2 id="volume-configuration">Volume Configuration</h2>
-<p>Rclone flags and volume options are set via the <code>-o</code> flag to the <code>docker volume create</code> command. They include backend-specific parameters as well as mount and <em>VFS</em> options. Also there are a few special <code>-o</code> options: <code>remote</code>, <code>fs</code>, <code>type</code>, <code>path</code>, <code>mount-type</code> and <code>persist</code>.</p>
-<p><code>remote</code> determines an existing remote name from the config file, with trailing colon and optionally with a remote path. See the full syntax in the <a href="https://rclone.org/docs/#syntax-of-remote-paths">rclone documentation</a>. This option can be aliased as <code>fs</code> to prevent confusion with the <em>remote</em> parameter of such backends as <em>crypt</em> or <em>alias</em>.</p>
-<p>The <code>remote=:backend:dir/subdir</code> syntax can be used to create <a href="https://rclone.org/docs/#backend-path-to-dir">on-the-fly (config-less) remotes</a>, while the <code>type</code> and <code>path</code> options provide a simpler alternative for this. Using two split options</p>
+<p>Rclone flags and volume options are set via the <code>-o</code> flag
+to the <code>docker volume create</code> command. They include
+backend-specific parameters as well as mount and <em>VFS</em> options.
+Also there are a few special <code>-o</code> options:
+<code>remote</code>, <code>fs</code>, <code>type</code>,
+<code>path</code>, <code>mount-type</code> and <code>persist</code>.</p>
+<p><code>remote</code> determines an existing remote name from the
+config file, with trailing colon and optionally with a remote path. See
+the full syntax in the <a
+href="https://rclone.org/docs/#syntax-of-remote-paths">rclone
+documentation</a>. This option can be aliased as <code>fs</code> to
+prevent confusion with the <em>remote</em> parameter of such backends as
+<em>crypt</em> or <em>alias</em>.</p>
+<p>The <code>remote=:backend:dir/subdir</code> syntax can be used to
+create <a href="https://rclone.org/docs/#backend-path-to-dir">on-the-fly
+(config-less) remotes</a>, while the <code>type</code> and
+<code>path</code> options provide a simpler alternative for this. Using
+two split options</p>
 <pre><code>-o type=backend -o path=dir/subdir</code></pre>
 <p>is equivalent to the combined syntax</p>
 <pre><code>-o remote=:backend:dir/subdir</code></pre>
-<p>but is arguably easier to parameterize in scripts. The <code>path</code> part is optional.</p>
-<p><a href="https://rclone.org/commands/rclone_serve_docker/#options">Mount and VFS options</a> as well as <a href="https://rclone.org/flags/#backend-flags">backend parameters</a> are named like their twin command-line flags without the <code>--</code> CLI prefix. Optionally you can use underscores instead of dashes in option names. For example, <code>--vfs-cache-mode full</code> becomes <code>-o vfs-cache-mode=full</code> or <code>-o vfs_cache_mode=full</code>. Boolean CLI flags without value will gain the <code>true</code> value, e.g. <code>--allow-other</code> becomes <code>-o allow-other=true</code> or <code>-o allow_other=true</code>.</p>
-<p>Please note that you can provide parameters only for the backend immediately referenced by the backend type of mounted <code>remote</code>. If this is a wrapping backend like <em>alias, chunker or crypt</em>, you cannot provide options for the referred to remote or backend. This limitation is imposed by the rclone connection string parser. The only workaround is to feed plugin with <code>rclone.conf</code> or configure plugin arguments (see below).</p>
+<p>but is arguably easier to parameterize in scripts. The
+<code>path</code> part is optional.</p>
+<p><a
+href="https://rclone.org/commands/rclone_serve_docker/#options">Mount
+and VFS options</a> as well as <a
+href="https://rclone.org/flags/#backend-flags">backend parameters</a>
+are named like their twin command-line flags without the <code>--</code>
+CLI prefix. Optionally you can use underscores instead of dashes in
+option names. For example, <code>--vfs-cache-mode full</code> becomes
+<code>-o vfs-cache-mode=full</code> or
+<code>-o vfs_cache_mode=full</code>. Boolean CLI flags without value
+will gain the <code>true</code> value, e.g. <code>--allow-other</code>
+becomes <code>-o allow-other=true</code> or
+<code>-o allow_other=true</code>.</p>
+<p>Please note that you can provide parameters only for the backend
+immediately referenced by the backend type of mounted
+<code>remote</code>. If this is a wrapping backend like <em>alias,
+chunker or crypt</em>, you cannot provide options for the referred to
+remote or backend. This limitation is imposed by the rclone connection
+string parser. The only workaround is to feed plugin with
+<code>rclone.conf</code> or configure plugin arguments (see below).</p>
 <h2 id="special-volume-options">Special Volume Options</h2>
-<p><code>mount-type</code> determines the mount method and in general can be one of: <code>mount</code>, <code>cmount</code>, or <code>mount2</code>. This can be aliased as <code>mount_type</code>. It should be noted that the managed rclone docker plugin currently does not support the <code>cmount</code> method and <code>mount2</code> is rarely needed. This option defaults to the first found method, which is usually <code>mount</code> so you generally won't need it.</p>
-<p><code>persist</code> is a reserved boolean (true/false) option. In future it will allow to persist on-the-fly remotes in the plugin <code>rclone.conf</code> file.</p>
+<p><code>mount-type</code> determines the mount method and in general
+can be one of: <code>mount</code>, <code>cmount</code>, or
+<code>mount2</code>. This can be aliased as <code>mount_type</code>. It
+should be noted that the managed rclone docker plugin currently does not
+support the <code>cmount</code> method and <code>mount2</code> is rarely
+needed. This option defaults to the first found method, which is usually
+<code>mount</code> so you generally won't need it.</p>
+<p><code>persist</code> is a reserved boolean (true/false) option. In
+future it will allow to persist on-the-fly remotes in the plugin
+<code>rclone.conf</code> file.</p>
 <h2 id="connection-strings-1">Connection Strings</h2>
-<p>The <code>remote</code> value can be extended with <a href="https://rclone.org/docs/#connection-strings">connection strings</a> as an alternative way to supply backend parameters. This is equivalent to the <code>-o</code> backend options with one <em>syntactic difference</em>. Inside connection string the backend prefix must be dropped from parameter names but in the <code>-o param=value</code> array it must be present. For instance, compare the following option array</p>
+<p>The <code>remote</code> value can be extended with <a
+href="https://rclone.org/docs/#connection-strings">connection
+strings</a> as an alternative way to supply backend parameters. This is
+equivalent to the <code>-o</code> backend options with one <em>syntactic
+difference</em>. Inside connection string the backend prefix must be
+dropped from parameter names but in the <code>-o param=value</code>
+array it must be present. For instance, compare the following option
+array</p>
 <pre><code>-o remote=:sftp:/home -o sftp-host=localhost</code></pre>
 <p>with equivalent connection string:</p>
 <pre><code>-o remote=:sftp,host=localhost:/home</code></pre>
-<p>This difference exists because flag options <code>-o key=val</code> include not only backend parameters but also mount/VFS flags and possibly other settings. Also it allows to discriminate the <code>remote</code> option from the <code>crypt-remote</code> (or similarly named backend parameters) and arguably simplifies scripting due to clearer value substitution.</p>
+<p>This difference exists because flag options <code>-o key=val</code>
+include not only backend parameters but also mount/VFS flags and
+possibly other settings. Also it allows to discriminate the
+<code>remote</code> option from the <code>crypt-remote</code> (or
+similarly named backend parameters) and arguably simplifies scripting
+due to clearer value substitution.</p>
 <h2 id="using-with-swarm-or-compose">Using with Swarm or Compose</h2>
-<p>Both <em>Docker Swarm</em> and <em>Docker Compose</em> use <a href="http://yaml.org/spec/1.2/spec.html">YAML</a>-formatted text files to describe groups (stacks) of containers, their properties, networks and volumes. <em>Compose</em> uses the <a href="https://docs.docker.com/compose/compose-file/compose-file-v2/#volume-configuration-reference">compose v2</a> format, <em>Swarm</em> uses the <a href="https://docs.docker.com/compose/compose-file/compose-file-v3/#volume-configuration-reference">compose v3</a> format. They are mostly similar, differences are explained in the <a href="https://docs.docker.com/compose/compose-file/compose-versioning/#upgrading">docker documentation</a>.</p>
-<p>Volumes are described by the children of the top-level <code>volumes:</code> node. Each of them should be named after its volume and have at least two elements, the self-explanatory <code>driver: rclone</code> value and the <code>driver_opts:</code> structure playing the same role as <code>-o key=val</code> CLI flags:</p>
+<p>Both <em>Docker Swarm</em> and <em>Docker Compose</em> use <a
+href="http://yaml.org/spec/1.2/spec.html">YAML</a>-formatted text files
+to describe groups (stacks) of containers, their properties, networks
+and volumes. <em>Compose</em> uses the <a
+href="https://docs.docker.com/compose/compose-file/compose-file-v2/#volume-configuration-reference">compose
+v2</a> format, <em>Swarm</em> uses the <a
+href="https://docs.docker.com/compose/compose-file/compose-file-v3/#volume-configuration-reference">compose
+v3</a> format. They are mostly similar, differences are explained in the
+<a
+href="https://docs.docker.com/compose/compose-file/compose-versioning/#upgrading">docker
+documentation</a>.</p>
+<p>Volumes are described by the children of the top-level
+<code>volumes:</code> node. Each of them should be named after its
+volume and have at least two elements, the self-explanatory
+<code>driver: rclone</code> value and the <code>driver_opts:</code>
+structure playing the same role as <code>-o key=val</code> CLI
+flags:</p>
 <pre><code>volumes:
   volume_name_1:
     driver: rclone
@@ -12967,38 +20456,147 @@ docker volume inspect vol1</code></pre>
       vfs_cache_mode: full
       token: &#39;{&quot;type&quot;: &quot;borrower&quot;, &quot;expires&quot;: &quot;2021-12-31&quot;}&#39;
       poll_interval: 0</code></pre>
-<p>Notice a few important details: - YAML prefers <code>_</code> in option names instead of <code>-</code>. - YAML treats single and double quotes interchangeably. Simple strings and integers can be left unquoted. - Boolean values must be quoted like <code>'true'</code> or <code>"false"</code> because these two words are reserved by YAML. - The filesystem string is keyed with <code>remote</code> (or with <code>fs</code>). Normally you can omit quotes here, but if the string ends with colon, you <strong>must</strong> quote it like <code>remote: "storage_box:"</code>. - YAML is picky about surrounding braces in values as this is in fact another <a href="http://yaml.org/spec/1.2/spec.html#id2790832">syntax for key/value mappings</a>. For example, JSON access tokens usually contain double quotes and surrounding braces, so you must put them in single quotes.</p>
+<p>Notice a few important details: - YAML prefers <code>_</code> in
+option names instead of <code>-</code>. - YAML treats single and double
+quotes interchangeably. Simple strings and integers can be left
+unquoted. - Boolean values must be quoted like <code>'true'</code> or
+<code>"false"</code> because these two words are reserved by YAML. - The
+filesystem string is keyed with <code>remote</code> (or with
+<code>fs</code>). Normally you can omit quotes here, but if the string
+ends with colon, you <strong>must</strong> quote it like
+<code>remote: "storage_box:"</code>. - YAML is picky about surrounding
+braces in values as this is in fact another <a
+href="http://yaml.org/spec/1.2/spec.html#id2790832">syntax for key/value
+mappings</a>. For example, JSON access tokens usually contain double
+quotes and surrounding braces, so you must put them in single
+quotes.</p>
 <h2 id="installing-as-managed-plugin">Installing as Managed Plugin</h2>
-<p>Docker daemon can install plugins from an image registry and run them managed. We maintain the <a href="https://hub.docker.com/p/rclone/docker-volume-rclone/">docker-volume-rclone</a> plugin image on <a href="https://hub.docker.com">Docker Hub</a>.</p>
-<p>Rclone volume plugin requires <strong>Docker Engine &gt;= 19.03.15</strong></p>
-<p>The plugin requires presence of two directories on the host before it can be installed. Note that plugin will <strong>not</strong> create them automatically. By default they must exist on host at the following locations (though you can tweak the paths): - <code>/var/lib/docker-plugins/rclone/config</code> is reserved for the <code>rclone.conf</code> config file and <strong>must</strong> exist even if it's empty and the config file is not present. - <code>/var/lib/docker-plugins/rclone/cache</code> holds the plugin state file as well as optional VFS caches.</p>
-<p>You can <a href="https://docs.docker.com/engine/reference/commandline/plugin_install/">install managed plugin</a> with default settings as follows:</p>
+<p>Docker daemon can install plugins from an image registry and run them
+managed. We maintain the <a
+href="https://hub.docker.com/p/rclone/docker-volume-rclone/">docker-volume-rclone</a>
+plugin image on <a href="https://hub.docker.com">Docker Hub</a>.</p>
+<p>Rclone volume plugin requires <strong>Docker Engine &gt;=
+19.03.15</strong></p>
+<p>The plugin requires presence of two directories on the host before it
+can be installed. Note that plugin will <strong>not</strong> create them
+automatically. By default they must exist on host at the following
+locations (though you can tweak the paths): -
+<code>/var/lib/docker-plugins/rclone/config</code> is reserved for the
+<code>rclone.conf</code> config file and <strong>must</strong> exist
+even if it's empty and the config file is not present. -
+<code>/var/lib/docker-plugins/rclone/cache</code> holds the plugin state
+file as well as optional VFS caches.</p>
+<p>You can <a
+href="https://docs.docker.com/engine/reference/commandline/plugin_install/">install
+managed plugin</a> with default settings as follows:</p>
 <pre><code>docker plugin install rclone/docker-volume-rclone:amd64 --grant-all-permissions --alias rclone</code></pre>
-<p>The <code>:amd64</code> part of the image specification after colon is called a <em>tag</em>. Usually you will want to install the latest plugin for your architecture. In this case the tag will just name it, like <code>amd64</code> above. The following plugin architectures are currently available: - <code>amd64</code> - <code>arm64</code> - <code>arm-v7</code></p>
-<p>Sometimes you might want a concrete plugin version, not the latest one. Then you should use image tag in the form <code>:ARCHITECTURE-VERSION</code>. For example, to install plugin version <code>v1.56.2</code> on architecture <code>arm64</code> you will use tag <code>arm64-1.56.2</code> (note the removed <code>v</code>) so the full image specification becomes <code>rclone/docker-volume-rclone:arm64-1.56.2</code>.</p>
-<p>We also provide the <code>latest</code> plugin tag, but since docker does not support multi-architecture plugins as of the time of this writing, this tag is currently an <strong>alias for <code>amd64</code></strong>. By convention the <code>latest</code> tag is the default one and can be omitted, thus both <code>rclone/docker-volume-rclone:latest</code> and just <code>rclone/docker-volume-rclone</code> will refer to the latest plugin release for the <code>amd64</code> platform.</p>
-<p>Also the <code>amd64</code> part can be omitted from the versioned rclone plugin tags. For example, rclone image reference <code>rclone/docker-volume-rclone:amd64-1.56.2</code> can be abbreviated as <code>rclone/docker-volume-rclone:1.56.2</code> for convenience. However, for non-intel architectures you still have to use the full tag as <code>amd64</code> or <code>latest</code> will fail to start.</p>
-<p>Managed plugin is in fact a special container running in a namespace separate from normal docker containers. Inside it runs the <code>rclone serve docker</code> command. The config and cache directories are bind-mounted into the container at start. The docker daemon connects to a unix socket created by the command inside the container. The command creates on-demand remote mounts right inside, then docker machinery propagates them through kernel mount namespaces and bind-mounts into requesting user containers.</p>
-<p>You can tweak a few plugin settings after installation when it's disabled (not in use), for instance:</p>
+<p>The <code>:amd64</code> part of the image specification after colon
+is called a <em>tag</em>. Usually you will want to install the latest
+plugin for your architecture. In this case the tag will just name it,
+like <code>amd64</code> above. The following plugin architectures are
+currently available: - <code>amd64</code> - <code>arm64</code> -
+<code>arm-v7</code></p>
+<p>Sometimes you might want a concrete plugin version, not the latest
+one. Then you should use image tag in the form
+<code>:ARCHITECTURE-VERSION</code>. For example, to install plugin
+version <code>v1.56.2</code> on architecture <code>arm64</code> you will
+use tag <code>arm64-1.56.2</code> (note the removed <code>v</code>) so
+the full image specification becomes
+<code>rclone/docker-volume-rclone:arm64-1.56.2</code>.</p>
+<p>We also provide the <code>latest</code> plugin tag, but since docker
+does not support multi-architecture plugins as of the time of this
+writing, this tag is currently an <strong>alias for
+<code>amd64</code></strong>. By convention the <code>latest</code> tag
+is the default one and can be omitted, thus both
+<code>rclone/docker-volume-rclone:latest</code> and just
+<code>rclone/docker-volume-rclone</code> will refer to the latest plugin
+release for the <code>amd64</code> platform.</p>
+<p>Also the <code>amd64</code> part can be omitted from the versioned
+rclone plugin tags. For example, rclone image reference
+<code>rclone/docker-volume-rclone:amd64-1.56.2</code> can be abbreviated
+as <code>rclone/docker-volume-rclone:1.56.2</code> for convenience.
+However, for non-intel architectures you still have to use the full tag
+as <code>amd64</code> or <code>latest</code> will fail to start.</p>
+<p>Managed plugin is in fact a special container running in a namespace
+separate from normal docker containers. Inside it runs the
+<code>rclone serve docker</code> command. The config and cache
+directories are bind-mounted into the container at start. The docker
+daemon connects to a unix socket created by the command inside the
+container. The command creates on-demand remote mounts right inside,
+then docker machinery propagates them through kernel mount namespaces
+and bind-mounts into requesting user containers.</p>
+<p>You can tweak a few plugin settings after installation when it's
+disabled (not in use), for instance:</p>
 <pre><code>docker plugin disable rclone
 docker plugin set rclone RCLONE_VERBOSE=2 config=/etc/rclone args=&quot;--vfs-cache-mode=writes --allow-other&quot;
 docker plugin enable rclone
 docker plugin inspect rclone</code></pre>
-<p>Note that if docker refuses to disable the plugin, you should find and remove all active volumes connected with it as well as containers and swarm services that use them. This is rather tedious so please carefully plan in advance.</p>
-<p>You can tweak the following settings: <code>args</code>, <code>config</code>, <code>cache</code>, <code>HTTP_PROXY</code>, <code>HTTPS_PROXY</code>, <code>NO_PROXY</code> and <code>RCLONE_VERBOSE</code>. It's <em>your</em> task to keep plugin settings in sync across swarm cluster nodes.</p>
-<p><code>args</code> sets command-line arguments for the <code>rclone serve docker</code> command (<em>none</em> by default). Arguments should be separated by space so you will normally want to put them in quotes on the <a href="https://docs.docker.com/engine/reference/commandline/plugin_set/">docker plugin set</a> command line. Both <a href="https://rclone.org/commands/rclone_serve_docker/#options">serve docker flags</a> and <a href="https://rclone.org/flags/">generic rclone flags</a> are supported, including backend parameters that will be used as defaults for volume creation. Note that plugin will fail (due to <a href="https://github.com/moby/moby/blob/v20.10.7/plugin/v2/plugin.go#L195">this docker bug</a>) if the <code>args</code> value is empty. Use e.g. <code>args="-v"</code> as a workaround.</p>
-<p><code>config=/host/dir</code> sets alternative host location for the config directory. Plugin will look for <code>rclone.conf</code> here. It's not an error if the config file is not present but the directory must exist. Please note that plugin can periodically rewrite the config file, for example when it renews storage access tokens. Keep this in mind and try to avoid races between the plugin and other instances of rclone on the host that might try to change the config simultaneously resulting in corrupted <code>rclone.conf</code>. You can also put stuff like private key files for SFTP remotes in this directory. Just note that it's bind-mounted inside the plugin container at the predefined path <code>/data/config</code>. For example, if your key file is named <code>sftp-box1.key</code> on the host, the corresponding volume config option should read <code>-o sftp-key-file=/data/config/sftp-box1.key</code>.</p>
-<p><code>cache=/host/dir</code> sets alternative host location for the <em>cache</em> directory. The plugin will keep VFS caches here. Also it will create and maintain the <code>docker-plugin.state</code> file in this directory. When the plugin is restarted or reinstalled, it will look in this file to recreate any volumes that existed previously. However, they will not be re-mounted into consuming containers after restart. Usually this is not a problem as the docker daemon normally will restart affected user containers after failures, daemon restarts or host reboots.</p>
-<p><code>RCLONE_VERBOSE</code> sets plugin verbosity from <code>0</code> (errors only, by default) to <code>2</code> (debugging). Verbosity can be also tweaked via <code>args="-v [-v] ..."</code>. Since arguments are more generic, you will rarely need this setting. The plugin output by default feeds the docker daemon log on local host. Log entries are reflected as <em>errors</em> in the docker log but retain their actual level assigned by rclone in the encapsulated message string.</p>
-<p><code>HTTP_PROXY</code>, <code>HTTPS_PROXY</code>, <code>NO_PROXY</code> customize the plugin proxy settings.</p>
-<p>You can set custom plugin options right when you install it, <em>in one go</em>:</p>
+<p>Note that if docker refuses to disable the plugin, you should find
+and remove all active volumes connected with it as well as containers
+and swarm services that use them. This is rather tedious so please
+carefully plan in advance.</p>
+<p>You can tweak the following settings: <code>args</code>,
+<code>config</code>, <code>cache</code>, <code>HTTP_PROXY</code>,
+<code>HTTPS_PROXY</code>, <code>NO_PROXY</code> and
+<code>RCLONE_VERBOSE</code>. It's <em>your</em> task to keep plugin
+settings in sync across swarm cluster nodes.</p>
+<p><code>args</code> sets command-line arguments for the
+<code>rclone serve docker</code> command (<em>none</em> by default).
+Arguments should be separated by space so you will normally want to put
+them in quotes on the <a
+href="https://docs.docker.com/engine/reference/commandline/plugin_set/">docker
+plugin set</a> command line. Both <a
+href="https://rclone.org/commands/rclone_serve_docker/#options">serve
+docker flags</a> and <a href="https://rclone.org/flags/">generic rclone
+flags</a> are supported, including backend parameters that will be used
+as defaults for volume creation. Note that plugin will fail (due to <a
+href="https://github.com/moby/moby/blob/v20.10.7/plugin/v2/plugin.go#L195">this
+docker bug</a>) if the <code>args</code> value is empty. Use e.g.
+<code>args="-v"</code> as a workaround.</p>
+<p><code>config=/host/dir</code> sets alternative host location for the
+config directory. Plugin will look for <code>rclone.conf</code> here.
+It's not an error if the config file is not present but the directory
+must exist. Please note that plugin can periodically rewrite the config
+file, for example when it renews storage access tokens. Keep this in
+mind and try to avoid races between the plugin and other instances of
+rclone on the host that might try to change the config simultaneously
+resulting in corrupted <code>rclone.conf</code>. You can also put stuff
+like private key files for SFTP remotes in this directory. Just note
+that it's bind-mounted inside the plugin container at the predefined
+path <code>/data/config</code>. For example, if your key file is named
+<code>sftp-box1.key</code> on the host, the corresponding volume config
+option should read
+<code>-o sftp-key-file=/data/config/sftp-box1.key</code>.</p>
+<p><code>cache=/host/dir</code> sets alternative host location for the
+<em>cache</em> directory. The plugin will keep VFS caches here. Also it
+will create and maintain the <code>docker-plugin.state</code> file in
+this directory. When the plugin is restarted or reinstalled, it will
+look in this file to recreate any volumes that existed previously.
+However, they will not be re-mounted into consuming containers after
+restart. Usually this is not a problem as the docker daemon normally
+will restart affected user containers after failures, daemon restarts or
+host reboots.</p>
+<p><code>RCLONE_VERBOSE</code> sets plugin verbosity from <code>0</code>
+(errors only, by default) to <code>2</code> (debugging). Verbosity can
+be also tweaked via <code>args="-v [-v] ..."</code>. Since arguments are
+more generic, you will rarely need this setting. The plugin output by
+default feeds the docker daemon log on local host. Log entries are
+reflected as <em>errors</em> in the docker log but retain their actual
+level assigned by rclone in the encapsulated message string.</p>
+<p><code>HTTP_PROXY</code>, <code>HTTPS_PROXY</code>,
+<code>NO_PROXY</code> customize the plugin proxy settings.</p>
+<p>You can set custom plugin options right when you install it, <em>in
+one go</em>:</p>
 <pre><code>docker plugin remove rclone
 docker plugin install rclone/docker-volume-rclone:amd64 \
        --alias rclone --grant-all-permissions \
        args=&quot;-v --allow-other&quot; config=/etc/rclone
 docker plugin inspect rclone</code></pre>
 <h2 id="healthchecks">Healthchecks</h2>
-<p>The docker plugin volume protocol doesn't provide a way for plugins to inform the docker daemon that a volume is (un-)available. As a workaround you can setup a healthcheck to verify that the mount is responding, for example:</p>
+<p>The docker plugin volume protocol doesn't provide a way for plugins
+to inform the docker daemon that a volume is (un-)available. As a
+workaround you can setup a healthcheck to verify that the mount is
+responding, for example:</p>
 <pre><code>services:
   my_service:
     image: my_image
@@ -13009,15 +20607,24 @@ docker plugin inspect rclone</code></pre>
       retries: 3
       start_period: 15s</code></pre>
 <h2 id="running-plugin-under-systemd">Running Plugin under Systemd</h2>
-<p>In most cases you should prefer managed mode. Moreover, MacOS and Windows do not support native Docker plugins. Please use managed mode on these systems. Proceed further only if you are on Linux.</p>
-<p>First, <a href="https://rclone.org/install/">install rclone</a>. You can just run it (type <code>rclone serve docker</code> and hit enter) for the test.</p>
+<p>In most cases you should prefer managed mode. Moreover, MacOS and
+Windows do not support native Docker plugins. Please use managed mode on
+these systems. Proceed further only if you are on Linux.</p>
+<p>First, <a href="https://rclone.org/install/">install rclone</a>. You
+can just run it (type <code>rclone serve docker</code> and hit enter)
+for the test.</p>
 <p>Install <em>FUSE</em>:</p>
 <pre><code>sudo apt-get -y install fuse</code></pre>
-<p>Download two systemd configuration files: <a href="https://raw.githubusercontent.com/rclone/rclone/master/contrib/docker-plugin/systemd/docker-volume-rclone.service">docker-volume-rclone.service</a> and <a href="https://raw.githubusercontent.com/rclone/rclone/master/contrib/docker-plugin/systemd/docker-volume-rclone.socket">docker-volume-rclone.socket</a>.</p>
+<p>Download two systemd configuration files: <a
+href="https://raw.githubusercontent.com/rclone/rclone/master/contrib/docker-plugin/systemd/docker-volume-rclone.service">docker-volume-rclone.service</a>
+and <a
+href="https://raw.githubusercontent.com/rclone/rclone/master/contrib/docker-plugin/systemd/docker-volume-rclone.socket">docker-volume-rclone.socket</a>.</p>
 <p>Put them to the <code>/etc/systemd/system/</code> directory:</p>
 <pre><code>cp docker-volume-plugin.service /etc/systemd/system/
 cp docker-volume-plugin.socket  /etc/systemd/system/</code></pre>
-<p>Please note that all commands in this section must be run as <em>root</em> but we omit <code>sudo</code> prefix for brevity. Now create directories required by the service:</p>
+<p>Please note that all commands in this section must be run as
+<em>root</em> but we omit <code>sudo</code> prefix for brevity. Now
+create directories required by the service:</p>
 <pre><code>mkdir -p /var/lib/docker-volumes/rclone
 mkdir -p /var/lib/docker-plugins/rclone/config
 mkdir -p /var/lib/docker-plugins/rclone/cache</code></pre>
@@ -13027,18 +20634,36 @@ systemctl start docker-volume-rclone.service
 systemctl enable docker-volume-rclone.socket
 systemctl start docker-volume-rclone.socket
 systemctl restart docker</code></pre>
-<p>Or run the service directly: - run <code>systemctl daemon-reload</code> to let systemd pick up new config - run <code>systemctl enable docker-volume-rclone.service</code> to make the new service start automatically when you power on your machine. - run <code>systemctl start docker-volume-rclone.service</code> to start the service now. - run <code>systemctl restart docker</code> to restart docker daemon and let it detect the new plugin socket. Note that this step is not needed in managed mode where docker knows about plugin state changes.</p>
-<p>The two methods are equivalent from the user perspective, but I personally prefer socket activation.</p>
+<p>Or run the service directly: - run
+<code>systemctl daemon-reload</code> to let systemd pick up new config -
+run <code>systemctl enable docker-volume-rclone.service</code> to make
+the new service start automatically when you power on your machine. -
+run <code>systemctl start docker-volume-rclone.service</code> to start
+the service now. - run <code>systemctl restart docker</code> to restart
+docker daemon and let it detect the new plugin socket. Note that this
+step is not needed in managed mode where docker knows about plugin state
+changes.</p>
+<p>The two methods are equivalent from the user perspective, but I
+personally prefer socket activation.</p>
 <h2 id="troubleshooting">Troubleshooting</h2>
-<p>You can <a href="https://docs.docker.com/engine/extend/#debugging-plugins">see managed plugin settings</a> with</p>
+<p>You can <a
+href="https://docs.docker.com/engine/extend/#debugging-plugins">see
+managed plugin settings</a> with</p>
 <pre><code>docker plugin list
 docker plugin inspect rclone</code></pre>
-<p>Note that docker (including latest 20.10.7) will not show actual values of <code>args</code>, just the defaults.</p>
-<p>Use <code>journalctl --unit docker</code> to see managed plugin output as part of the docker daemon log. Note that docker reflects plugin lines as <em>errors</em> but their actual level can be seen from encapsulated message string.</p>
-<p>You will usually install the latest version of managed plugin for your platform. Use the following commands to print the actual installed version:</p>
+<p>Note that docker (including latest 20.10.7) will not show actual
+values of <code>args</code>, just the defaults.</p>
+<p>Use <code>journalctl --unit docker</code> to see managed plugin
+output as part of the docker daemon log. Note that docker reflects
+plugin lines as <em>errors</em> but their actual level can be seen from
+encapsulated message string.</p>
+<p>You will usually install the latest version of managed plugin for
+your platform. Use the following commands to print the actual installed
+version:</p>
 <pre><code>PLUGID=$(docker plugin list --no-trunc | awk &#39;/rclone/{print$1}&#39;)
 sudo runc --root /run/docker/runtime-runc/plugins.moby exec $PLUGID rclone version</code></pre>
-<p>You can even use <code>runc</code> to run shell inside the plugin container:</p>
+<p>You can even use <code>runc</code> to run shell inside the plugin
+container:</p>
 <pre><code>sudo runc --root /run/docker/runtime-runc/plugins.moby exec --tty $PLUGID bash</code></pre>
 <p>Also you can use curl to check the plugin socket connectivity:</p>
 <pre><code>docker plugin list --no-trunc
@@ -13046,28 +20671,54 @@ PLUGID=123abc...
 sudo curl -H Content-Type:application/json -XPOST -d {} --unix-socket /run/docker/plugins/$PLUGID/rclone.sock http://localhost/Plugin.Activate</code></pre>
 <p>though this is rarely needed.</p>
 <h2 id="caveats">Caveats</h2>
-<p>Finally I'd like to mention a <em>caveat with updating volume settings</em>. Docker CLI does not have a dedicated command like <code>docker volume update</code>. It may be tempting to invoke <code>docker volume create</code> with updated options on existing volume, but there is a gotcha. The command will do nothing, it won't even return an error. I hope that docker maintainers will fix this some day. In the meantime be aware that you must remove your volume before recreating it with new settings:</p>
+<p>Finally I'd like to mention a <em>caveat with updating volume
+settings</em>. Docker CLI does not have a dedicated command like
+<code>docker volume update</code>. It may be tempting to invoke
+<code>docker volume create</code> with updated options on existing
+volume, but there is a gotcha. The command will do nothing, it won't
+even return an error. I hope that docker maintainers will fix this some
+day. In the meantime be aware that you must remove your volume before
+recreating it with new settings:</p>
 <pre><code>docker volume remove my_vol
 docker volume create my_vol -d rclone -o opt1=new_val1 ...</code></pre>
 <p>and verify that settings did update:</p>
 <pre><code>docker volume list
 docker volume inspect my_vol</code></pre>
-<p>If docker refuses to remove the volume, you should find containers or swarm services that use it and stop them first.</p>
+<p>If docker refuses to remove the volume, you should find containers or
+swarm services that use it and stop them first.</p>
 <h2 id="bisync">Bisync</h2>
-<p><code>bisync</code> is <strong>in beta</strong> and is considered an <strong>advanced command</strong>, so use with care. Make sure you have read and understood the entire <a href="https://rclone.org/bisync">manual</a> (especially the <a href="#limitations">Limitations</a> section) before using, or data loss can result. Questions can be asked in the <a href="https://forum.rclone.org/">Rclone Forum</a>.</p>
+<p><code>bisync</code> is <strong>in beta</strong> and is considered an
+<strong>advanced command</strong>, so use with care. Make sure you have
+read and understood the entire <a
+href="https://rclone.org/bisync">manual</a> (especially the <a
+href="#limitations">Limitations</a> section) before using, or data loss
+can result. Questions can be asked in the <a
+href="https://forum.rclone.org/">Rclone Forum</a>.</p>
 <h2 id="getting-started">Getting started</h2>
 <ul>
-<li><a href="https://rclone.org/install/">Install rclone</a> and setup your remotes.</li>
-<li>Bisync will create its working directory at <code>~/.cache/rclone/bisync</code> on Linux, <code>/Users/yourusername/Library/Caches/rclone/bisync</code> on Mac, or <code>C:\Users\MyLogin\AppData\Local\rclone\bisync</code> on Windows. Make sure that this location is writable.</li>
-<li>Run bisync with the <code>--resync</code> flag, specifying the paths to the local and remote sync directory roots.</li>
-<li>For successive sync runs, leave off the <code>--resync</code> flag. (<strong>Important!</strong>)</li>
-<li>Consider using a <a href="#filtering">filters file</a> for excluding unnecessary files and directories from the sync.</li>
-<li>Consider setting up the <a href="#check-access">--check-access</a> feature for safety.</li>
-<li>On Linux or Mac, consider setting up a <a href="#cron">crontab entry</a>. bisync can safely run in concurrent cron jobs thanks to lock files it maintains.</li>
+<li><a href="https://rclone.org/install/">Install rclone</a> and setup
+your remotes.</li>
+<li>Bisync will create its working directory at
+<code>~/.cache/rclone/bisync</code> on Linux,
+<code>/Users/yourusername/Library/Caches/rclone/bisync</code> on Mac, or
+<code>C:\Users\MyLogin\AppData\Local\rclone\bisync</code> on Windows.
+Make sure that this location is writable.</li>
+<li>Run bisync with the <code>--resync</code> flag, specifying the paths
+to the local and remote sync directory roots.</li>
+<li>For successive sync runs, leave off the <code>--resync</code> flag.
+(<strong>Important!</strong>)</li>
+<li>Consider using a <a href="#filtering">filters file</a> for excluding
+unnecessary files and directories from the sync.</li>
+<li>Consider setting up the <a href="#check-access">--check-access</a>
+feature for safety.</li>
+<li>On Linux or Mac, consider setting up a <a href="#cron">crontab
+entry</a>. bisync can safely run in concurrent cron jobs thanks to lock
+files it maintains.</li>
 </ul>
 <p>For example, your first command might look like this:</p>
 <pre><code>rclone bisync remote1:path1 remote2:path2 --create-empty-src-dirs --compare size,modtime,checksum --slow-hash-sync-only --resilient -MvP --drive-skip-gdocs --fix-case --resync --dry-run</code></pre>
-<p>If all looks good, run it again without <code>--dry-run</code>. After that, remove <code>--resync</code> as well.</p>
+<p>If all looks good, run it again without <code>--dry-run</code>. After
+that, remove <code>--resync</code> as well.</p>
 <p>Here is a typical run log (with timestamps removed for clarity):</p>
 <pre><code>rclone bisync /testdir/path1/ /testdir/path2/ --verbose
 INFO  : Synching Path1 &quot;/testdir/path1/&quot; with Path2 &quot;/testdir/path2/&quot;
@@ -13150,174 +20801,783 @@ Optional Flags:
       --max-delete PERCENT                   Safety check on maximum percentage of deleted files allowed. If exceeded, the bisync run will abort. (default: 50%)
   -n, --dry-run                              Go through the motions - No files are copied/deleted.
   -v, --verbose                              Increases logging verbosity. May be specified more than once for more details.</code></pre>
-<p>Arbitrary rclone flags may be specified on the <a href="https://rclone.org/commands/rclone_bisync/">bisync command line</a>, for example <code>rclone bisync ./testdir/path1/ gdrive:testdir/path2/ --drive-skip-gdocs -v -v --timeout 10s</code> Note that interactions of various rclone flags with bisync process flow has not been fully tested yet.</p>
+<p>Arbitrary rclone flags may be specified on the <a
+href="https://rclone.org/commands/rclone_bisync/">bisync command
+line</a>, for example
+<code>rclone bisync ./testdir/path1/ gdrive:testdir/path2/ --drive-skip-gdocs -v -v --timeout 10s</code>
+Note that interactions of various rclone flags with bisync process flow
+has not been fully tested yet.</p>
 <h3 id="paths">Paths</h3>
-<p>Path1 and Path2 arguments may be references to any mix of local directory paths (absolute or relative), UNC paths (<code>//server/share/path</code>), Windows drive paths (with a drive letter and <code>:</code>) or configured <a href="https://rclone.org/docs/#syntax-of-remote-paths">remotes</a> with optional subdirectory paths. Cloud references are distinguished by having a <code>:</code> in the argument (see <a href="#windows">Windows support</a> below).</p>
-<p>Path1 and Path2 are treated equally, in that neither has priority for file changes (except during <a href="#resync"><code>--resync</code></a>), and access efficiency does not change whether a remote is on Path1 or Path2.</p>
-<p>The listings in bisync working directory (default: <code>~/.cache/rclone/bisync</code>) are named based on the Path1 and Path2 arguments so that separate syncs to individual directories within the tree may be set up, e.g.: <code>path_to_local_tree..dropbox_subdir.lst</code>.</p>
-<p>Any empty directories after the sync on both the Path1 and Path2 filesystems are not deleted by default, unless <code>--create-empty-src-dirs</code> is specified. If the <code>--remove-empty-dirs</code> flag is specified, then both paths will have ALL empty directories purged as the last step in the process.</p>
+<p>Path1 and Path2 arguments may be references to any mix of local
+directory paths (absolute or relative), UNC paths
+(<code>//server/share/path</code>), Windows drive paths (with a drive
+letter and <code>:</code>) or configured <a
+href="https://rclone.org/docs/#syntax-of-remote-paths">remotes</a> with
+optional subdirectory paths. Cloud references are distinguished by
+having a <code>:</code> in the argument (see <a href="#windows">Windows
+support</a> below).</p>
+<p>Path1 and Path2 are treated equally, in that neither has priority for
+file changes (except during <a
+href="#resync"><code>--resync</code></a>), and access efficiency does
+not change whether a remote is on Path1 or Path2.</p>
+<p>The listings in bisync working directory (default:
+<code>~/.cache/rclone/bisync</code>) are named based on the Path1 and
+Path2 arguments so that separate syncs to individual directories within
+the tree may be set up, e.g.:
+<code>path_to_local_tree..dropbox_subdir.lst</code>.</p>
+<p>Any empty directories after the sync on both the Path1 and Path2
+filesystems are not deleted by default, unless
+<code>--create-empty-src-dirs</code> is specified. If the
+<code>--remove-empty-dirs</code> flag is specified, then both paths will
+have ALL empty directories purged as the last step in the process.</p>
 <h2 id="command-line-flags">Command-line flags</h2>
 <h3 id="resync">--resync</h3>
-<p>This will effectively make both Path1 and Path2 filesystems contain a matching superset of all files. By default, Path2 files that do not exist in Path1 will be copied to Path1, and the process will then copy the Path1 tree to Path2.</p>
-<p>The <code>--resync</code> sequence is roughly equivalent to the following (but see <a href="#resync-mode"><code>--resync-mode</code></a> for other options):</p>
+<p>This will effectively make both Path1 and Path2 filesystems contain a
+matching superset of all files. By default, Path2 files that do not
+exist in Path1 will be copied to Path1, and the process will then copy
+the Path1 tree to Path2.</p>
+<p>The <code>--resync</code> sequence is roughly equivalent to the
+following (but see <a href="#resync-mode"><code>--resync-mode</code></a>
+for other options):</p>
 <pre><code>rclone copy Path2 Path1 --ignore-existing [--create-empty-src-dirs]
 rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
-<p>The base directories on both Path1 and Path2 filesystems must exist or bisync will fail. This is required for safety - that bisync can verify that both paths are valid.</p>
-<p>When using <code>--resync</code>, a newer version of a file on the Path2 filesystem will (by default) be overwritten by the Path1 filesystem version. (Note that this is <a href="https://github.com/rclone/rclone/issues/5681#issuecomment-938761815">NOT entirely symmetrical</a>, and more symmetrical options can be specified with the <a href="#resync-mode"><code>--resync-mode</code></a> flag.) Carefully evaluate deltas using <a href="https://rclone.org/flags/#non-backend-flags">--dry-run</a>.</p>
-<p>For a resync run, one of the paths may be empty (no files in the path tree). The resync run should result in files on both paths, else a normal non-resync run will fail.</p>
-<p>For a non-resync run, either path being empty (no files in the tree) fails with <code>Empty current PathN listing. Cannot sync to an empty directory: X.pathN.lst</code> This is a safety check that an unexpected empty path does not result in deleting <strong>everything</strong> in the other path.</p>
-<p>Note that <code>--resync</code> implies <code>--resync-mode path1</code> unless a different <a href="#resync-mode"><code>--resync-mode</code></a> is explicitly specified. It is not necessary to use both the <code>--resync</code> and <code>--resync-mode</code> flags -- either one is sufficient without the other.</p>
-<p><strong>Note:</strong> <code>--resync</code> (including <code>--resync-mode</code>) should only be used under three specific (rare) circumstances: 1. It is your <em>first</em> bisync run (between these two paths) 2. You've just made changes to your bisync settings (such as editing the contents of your <code>--filters-file</code>) 3. There was an error on the prior run, and as a result, bisync now requires <code>--resync</code> to recover</p>
-<p>The rest of the time, you should <em>omit</em> <code>--resync</code>. The reason is because <code>--resync</code> will only <em>copy</em> (not <em>sync</em>) each side to the other. Therefore, if you included <code>--resync</code> for every bisync run, it would never be possible to delete a file -- the deleted file would always keep reappearing at the end of every run (because it's being copied from the other side where it still exists). Similarly, renaming a file would always result in a duplicate copy (both old and new name) on both sides.</p>
-<p>If you find that frequent interruptions from #3 are an issue, rather than automatically running <code>--resync</code>, the recommended alternative is to use the <a href="#resilient"><code>--resilient</code></a>, <a href="#recover"><code>--recover</code></a>, and <a href="#conflict-resolve"><code>--conflict-resolve</code></a> flags, (along with <a href="#graceful-shutdown">Graceful Shutdown</a> mode, when needed) for a very robust "set-it-and-forget-it" bisync setup that can automatically bounce back from almost any interruption it might encounter. Consider adding something like the following:</p>
+<p>The base directories on both Path1 and Path2 filesystems must exist
+or bisync will fail. This is required for safety - that bisync can
+verify that both paths are valid.</p>
+<p>When using <code>--resync</code>, a newer version of a file on the
+Path2 filesystem will (by default) be overwritten by the Path1
+filesystem version. (Note that this is <a
+href="https://github.com/rclone/rclone/issues/5681#issuecomment-938761815">NOT
+entirely symmetrical</a>, and more symmetrical options can be specified
+with the <a href="#resync-mode"><code>--resync-mode</code></a> flag.)
+Carefully evaluate deltas using <a
+href="https://rclone.org/flags/#non-backend-flags">--dry-run</a>.</p>
+<p>For a resync run, one of the paths may be empty (no files in the path
+tree). The resync run should result in files on both paths, else a
+normal non-resync run will fail.</p>
+<p>For a non-resync run, either path being empty (no files in the tree)
+fails with
+<code>Empty current PathN listing. Cannot sync to an empty directory: X.pathN.lst</code>
+This is a safety check that an unexpected empty path does not result in
+deleting <strong>everything</strong> in the other path.</p>
+<p>Note that <code>--resync</code> implies
+<code>--resync-mode path1</code> unless a different <a
+href="#resync-mode"><code>--resync-mode</code></a> is explicitly
+specified. It is not necessary to use both the <code>--resync</code> and
+<code>--resync-mode</code> flags -- either one is sufficient without the
+other.</p>
+<p><strong>Note:</strong> <code>--resync</code> (including
+<code>--resync-mode</code>) should only be used under three specific
+(rare) circumstances: 1. It is your <em>first</em> bisync run (between
+these two paths) 2. You've just made changes to your bisync settings
+(such as editing the contents of your <code>--filters-file</code>) 3.
+There was an error on the prior run, and as a result, bisync now
+requires <code>--resync</code> to recover</p>
+<p>The rest of the time, you should <em>omit</em> <code>--resync</code>.
+The reason is because <code>--resync</code> will only <em>copy</em> (not
+<em>sync</em>) each side to the other. Therefore, if you included
+<code>--resync</code> for every bisync run, it would never be possible
+to delete a file -- the deleted file would always keep reappearing at
+the end of every run (because it's being copied from the other side
+where it still exists). Similarly, renaming a file would always result
+in a duplicate copy (both old and new name) on both sides.</p>
+<p>If you find that frequent interruptions from #3 are an issue, rather
+than automatically running <code>--resync</code>, the recommended
+alternative is to use the <a
+href="#resilient"><code>--resilient</code></a>, <a
+href="#recover"><code>--recover</code></a>, and <a
+href="#conflict-resolve"><code>--conflict-resolve</code></a> flags,
+(along with <a href="#graceful-shutdown">Graceful Shutdown</a> mode,
+when needed) for a very robust "set-it-and-forget-it" bisync setup that
+can automatically bounce back from almost any interruption it might
+encounter. Consider adding something like the following:</p>
 <pre><code>--resilient --recover --max-lock 2m --conflict-resolve newer</code></pre>
 <h3 id="resync-mode">--resync-mode CHOICE</h3>
-<p>In the event that a file differs on both sides during a <code>--resync</code>, <code>--resync-mode</code> controls which version will overwrite the other. The supported options are similar to <a href="#conflict-resolve"><code>--conflict-resolve</code></a>. For all of the following options, the version that is kept is referred to as the "winner", and the version that is overwritten (deleted) is referred to as the "loser". The options are named after the "winner":</p>
+<p>In the event that a file differs on both sides during a
+<code>--resync</code>, <code>--resync-mode</code> controls which version
+will overwrite the other. The supported options are similar to <a
+href="#conflict-resolve"><code>--conflict-resolve</code></a>. For all of
+the following options, the version that is kept is referred to as the
+"winner", and the version that is overwritten (deleted) is referred to
+as the "loser". The options are named after the "winner":</p>
 <ul>
-<li><code>path1</code> - (the default) - the version from Path1 is unconditionally considered the winner (regardless of <code>modtime</code> and <code>size</code>, if any). This can be useful if one side is more trusted or up-to-date than the other, at the time of the <code>--resync</code>.</li>
-<li><code>path2</code> - same as <code>path1</code>, except the path2 version is considered the winner.</li>
-<li><code>newer</code> - the newer file (by <code>modtime</code>) is considered the winner, regardless of which side it came from. This may result in having a mix of some winners from Path1, and some winners from Path2. (The implementation is analogous to running <code>rclone copy --update</code> in both directions.)</li>
-<li><code>older</code> - same as <code>newer</code>, except the older file is considered the winner, and the newer file is considered the loser.</li>
-<li><code>larger</code> - the larger file (by <code>size</code>) is considered the winner (regardless of <code>modtime</code>, if any). This can be a useful option for remotes without <code>modtime</code> support, or with the kinds of files (such as logs) that tend to grow but not shrink, over time.</li>
-<li><code>smaller</code> - the smaller file (by <code>size</code>) is considered the winner (regardless of <code>modtime</code>, if any).</li>
+<li><code>path1</code> - (the default) - the version from Path1 is
+unconditionally considered the winner (regardless of
+<code>modtime</code> and <code>size</code>, if any). This can be useful
+if one side is more trusted or up-to-date than the other, at the time of
+the <code>--resync</code>.</li>
+<li><code>path2</code> - same as <code>path1</code>, except the path2
+version is considered the winner.</li>
+<li><code>newer</code> - the newer file (by <code>modtime</code>) is
+considered the winner, regardless of which side it came from. This may
+result in having a mix of some winners from Path1, and some winners from
+Path2. (The implementation is analogous to running
+<code>rclone copy --update</code> in both directions.)</li>
+<li><code>older</code> - same as <code>newer</code>, except the older
+file is considered the winner, and the newer file is considered the
+loser.</li>
+<li><code>larger</code> - the larger file (by <code>size</code>) is
+considered the winner (regardless of <code>modtime</code>, if any). This
+can be a useful option for remotes without <code>modtime</code> support,
+or with the kinds of files (such as logs) that tend to grow but not
+shrink, over time.</li>
+<li><code>smaller</code> - the smaller file (by <code>size</code>) is
+considered the winner (regardless of <code>modtime</code>, if any).</li>
 </ul>
-<p>For all of the above options, note the following: - If either of the underlying remotes lacks support for the chosen method, it will be ignored and will fall back to the default of <code>path1</code>. (For example, if <code>--resync-mode newer</code> is set, but one of the paths uses a remote that doesn't support <code>modtime</code>.) - If a winner can't be determined because the chosen method's attribute is missing or equal, it will be ignored, and bisync will instead try to determine whether the files differ by looking at the other <code>--compare</code> methods in effect. (For example, if <code>--resync-mode newer</code> is set, but the Path1 and Path2 modtimes are identical, bisync will compare the sizes.) If bisync concludes that they differ, preference is given to whichever is the "source" at that moment. (In practice, this gives a slight advantage to Path2, as the 2to1 copy comes before the 1to2 copy.) If the files <em>do not</em> differ, nothing is copied (as both sides are already correct). - These options apply only to files that exist on both sides (with the same name and relative path). Files that exist <em>only</em> on one side and not the other are <em>always</em> copied to the other, during <code>--resync</code> (this is one of the main differences between resync and non-resync runs.). - <code>--conflict-resolve</code>, <code>--conflict-loser</code>, and <code>--conflict-suffix</code> do not apply during <code>--resync</code>, and unlike these flags, nothing is renamed during <code>--resync</code>. When a file differs on both sides during <code>--resync</code>, one version always overwrites the other (much like in <code>rclone copy</code>.) (Consider using <a href="#backup-dir1-and-backup-dir2"><code>--backup-dir</code></a> to retain a backup of the losing version.) - Unlike for <code>--conflict-resolve</code>, <code>--resync-mode none</code> is not a valid option (or rather, it will be interpreted as "no resync", unless <code>--resync</code> has also been specified, in which case it will be ignored.) - Winners and losers are decided at the individual file-level only (there is not currently an option to pick an entire winning directory atomically, although the <code>path1</code> and <code>path2</code> options typically produce a similar result.) - To maintain backward-compatibility, the <code>--resync</code> flag implies <code>--resync-mode path1</code> unless a different <code>--resync-mode</code> is explicitly specified. Similarly, all <code>--resync-mode</code> options (except <code>none</code>) imply <code>--resync</code>, so it is not necessary to use both the <code>--resync</code> and <code>--resync-mode</code> flags simultaneously -- either one is sufficient without the other.</p>
+<p>For all of the above options, note the following: - If either of the
+underlying remotes lacks support for the chosen method, it will be
+ignored and will fall back to the default of <code>path1</code>. (For
+example, if <code>--resync-mode newer</code> is set, but one of the
+paths uses a remote that doesn't support <code>modtime</code>.) - If a
+winner can't be determined because the chosen method's attribute is
+missing or equal, it will be ignored, and bisync will instead try to
+determine whether the files differ by looking at the other
+<code>--compare</code> methods in effect. (For example, if
+<code>--resync-mode newer</code> is set, but the Path1 and Path2
+modtimes are identical, bisync will compare the sizes.) If bisync
+concludes that they differ, preference is given to whichever is the
+"source" at that moment. (In practice, this gives a slight advantage to
+Path2, as the 2to1 copy comes before the 1to2 copy.) If the files <em>do
+not</em> differ, nothing is copied (as both sides are already correct).
+- These options apply only to files that exist on both sides (with the
+same name and relative path). Files that exist <em>only</em> on one side
+and not the other are <em>always</em> copied to the other, during
+<code>--resync</code> (this is one of the main differences between
+resync and non-resync runs.). - <code>--conflict-resolve</code>,
+<code>--conflict-loser</code>, and <code>--conflict-suffix</code> do not
+apply during <code>--resync</code>, and unlike these flags, nothing is
+renamed during <code>--resync</code>. When a file differs on both sides
+during <code>--resync</code>, one version always overwrites the other
+(much like in <code>rclone copy</code>.) (Consider using <a
+href="#backup-dir1-and-backup-dir2"><code>--backup-dir</code></a> to
+retain a backup of the losing version.) - Unlike for
+<code>--conflict-resolve</code>, <code>--resync-mode none</code> is not
+a valid option (or rather, it will be interpreted as "no resync", unless
+<code>--resync</code> has also been specified, in which case it will be
+ignored.) - Winners and losers are decided at the individual file-level
+only (there is not currently an option to pick an entire winning
+directory atomically, although the <code>path1</code> and
+<code>path2</code> options typically produce a similar result.) - To
+maintain backward-compatibility, the <code>--resync</code> flag implies
+<code>--resync-mode path1</code> unless a different
+<code>--resync-mode</code> is explicitly specified. Similarly, all
+<code>--resync-mode</code> options (except <code>none</code>) imply
+<code>--resync</code>, so it is not necessary to use both the
+<code>--resync</code> and <code>--resync-mode</code> flags
+simultaneously -- either one is sufficient without the other.</p>
 <h3 id="check-access">--check-access</h3>
-<p>Access check files are an additional safety measure against data loss. bisync will ensure it can find matching <code>RCLONE_TEST</code> files in the same places in the Path1 and Path2 filesystems. <code>RCLONE_TEST</code> files are not generated automatically. For <code>--check-access</code> to succeed, you must first either: <strong>A)</strong> Place one or more <code>RCLONE_TEST</code> files in both systems, or <strong>B)</strong> Set <code>--check-filename</code> to a filename already in use in various locations throughout your sync'd fileset. Recommended methods for <strong>A)</strong> include: * <code>rclone touch Path1/RCLONE_TEST</code> (create a new file) * <code>rclone copyto Path1/RCLONE_TEST Path2/RCLONE_TEST</code> (copy an existing file) * <code>rclone copy Path1/RCLONE_TEST Path2/RCLONE_TEST  --include "RCLONE_TEST"</code> (copy multiple files at once, recursively) * create the files manually (outside of rclone) * run <code>bisync</code> once <em>without</em> <code>--check-access</code> to set matching files on both filesystems will also work, but is not preferred, due to potential for user error (you are temporarily disabling the safety feature).</p>
-<p>Note that <code>--check-access</code> is still enforced on <code>--resync</code>, so <code>bisync --resync --check-access</code> will not work as a method of initially setting the files (this is to ensure that bisync can't <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20%2D%2Dcheck%2Daccess%20doesn%27t%20always%20fail%20when%20it%20should">inadvertently circumvent its own safety switch</a>.)</p>
-<p>Time stamps and file contents for <code>RCLONE_TEST</code> files are not important, just the names and locations. If you have symbolic links in your sync tree it is recommended to place <code>RCLONE_TEST</code> files in the linked-to directory tree to protect against bisync assuming a bunch of deleted files if the linked-to tree should not be accessible. See also the <a href="--check-filename">--check-filename</a> flag.</p>
+<p>Access check files are an additional safety measure against data
+loss. bisync will ensure it can find matching <code>RCLONE_TEST</code>
+files in the same places in the Path1 and Path2 filesystems.
+<code>RCLONE_TEST</code> files are not generated automatically. For
+<code>--check-access</code> to succeed, you must first either:
+<strong>A)</strong> Place one or more <code>RCLONE_TEST</code> files in
+both systems, or <strong>B)</strong> Set <code>--check-filename</code>
+to a filename already in use in various locations throughout your sync'd
+fileset. Recommended methods for <strong>A)</strong> include: *
+<code>rclone touch Path1/RCLONE_TEST</code> (create a new file) *
+<code>rclone copyto Path1/RCLONE_TEST Path2/RCLONE_TEST</code> (copy an
+existing file) *
+<code>rclone copy Path1/RCLONE_TEST Path2/RCLONE_TEST  --include "RCLONE_TEST"</code>
+(copy multiple files at once, recursively) * create the files manually
+(outside of rclone) * run <code>bisync</code> once <em>without</em>
+<code>--check-access</code> to set matching files on both filesystems
+will also work, but is not preferred, due to potential for user error
+(you are temporarily disabling the safety feature).</p>
+<p>Note that <code>--check-access</code> is still enforced on
+<code>--resync</code>, so <code>bisync --resync --check-access</code>
+will not work as a method of initially setting the files (this is to
+ensure that bisync can't <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20%2D%2Dcheck%2Daccess%20doesn%27t%20always%20fail%20when%20it%20should">inadvertently
+circumvent its own safety switch</a>.)</p>
+<p>Time stamps and file contents for <code>RCLONE_TEST</code> files are
+not important, just the names and locations. If you have symbolic links
+in your sync tree it is recommended to place <code>RCLONE_TEST</code>
+files in the linked-to directory tree to protect against bisync assuming
+a bunch of deleted files if the linked-to tree should not be accessible.
+See also the <a href="--check-filename">--check-filename</a> flag.</p>
 <h3 id="check-filename">--check-filename</h3>
-<p>Name of the file(s) used in access health validation. The default <code>--check-filename</code> is <code>RCLONE_TEST</code>. One or more files having this filename must exist, synchronized between your source and destination filesets, in order for <code>--check-access</code> to succeed. See <a href="#check-access">--check-access</a> for additional details.</p>
+<p>Name of the file(s) used in access health validation. The default
+<code>--check-filename</code> is <code>RCLONE_TEST</code>. One or more
+files having this filename must exist, synchronized between your source
+and destination filesets, in order for <code>--check-access</code> to
+succeed. See <a href="#check-access">--check-access</a> for additional
+details.</p>
 <h3 id="compare">--compare</h3>
-<p>As of <code>v1.66</code>, bisync fully supports comparing based on any combination of size, modtime, and checksum (lifting the prior restriction on backends without modtime support.)</p>
-<p>By default (without the <code>--compare</code> flag), bisync inherits the same comparison options as <code>sync</code> (that is: <code>size</code> and <code>modtime</code> by default, unless modified with flags such as <a href="https://rclone.org/docs/#c-checksum"><code>--checksum</code></a> or <a href="/docs/#size-only"><code>--size-only</code></a>.)</p>
-<p>If the <code>--compare</code> flag is set, it will override these defaults. This can be useful if you wish to compare based on combinations not currently supported in <code>sync</code>, such as comparing all three of <code>size</code> AND <code>modtime</code> AND <code>checksum</code> simultaneously (or just <code>modtime</code> AND <code>checksum</code>).</p>
-<p><code>--compare</code> takes a comma-separated list, with the currently supported values being <code>size</code>, <code>modtime</code>, and <code>checksum</code>. For example, if you want to compare size and checksum, but not modtime, you would do:</p>
+<p>As of <code>v1.66</code>, bisync fully supports comparing based on
+any combination of size, modtime, and checksum (lifting the prior
+restriction on backends without modtime support.)</p>
+<p>By default (without the <code>--compare</code> flag), bisync inherits
+the same comparison options as <code>sync</code> (that is:
+<code>size</code> and <code>modtime</code> by default, unless modified
+with flags such as <a
+href="https://rclone.org/docs/#c-checksum"><code>--checksum</code></a>
+or <a href="/docs/#size-only"><code>--size-only</code></a>.)</p>
+<p>If the <code>--compare</code> flag is set, it will override these
+defaults. This can be useful if you wish to compare based on
+combinations not currently supported in <code>sync</code>, such as
+comparing all three of <code>size</code> AND <code>modtime</code> AND
+<code>checksum</code> simultaneously (or just <code>modtime</code> AND
+<code>checksum</code>).</p>
+<p><code>--compare</code> takes a comma-separated list, with the
+currently supported values being <code>size</code>,
+<code>modtime</code>, and <code>checksum</code>. For example, if you
+want to compare size and checksum, but not modtime, you would do:</p>
 <pre><code>--compare size,checksum</code></pre>
 <p>Or if you want to compare all three:</p>
 <pre><code>--compare size,modtime,checksum</code></pre>
-<p><code>--compare</code> overrides any conflicting flags. For example, if you set the conflicting flags <code>--compare checksum --size-only</code>, <code>--size-only</code> will be ignored, and bisync will compare checksum and not size. To avoid confusion, it is recommended to use <em>either</em> <code>--compare</code> or the normal <code>sync</code> flags, but not both.</p>
-<p>If <code>--compare</code> includes <code>checksum</code> and both remotes support checksums but have no hash types in common with each other, checksums will be considered <em>only</em> for comparisons within the same side (to determine what has changed since the prior sync), but not for comparisons against the opposite side. If one side supports checksums and the other does not, checksums will only be considered on the side that supports them.</p>
-<p>When comparing with <code>checksum</code> and/or <code>size</code> without <code>modtime</code>, bisync cannot determine whether a file is <code>newer</code> or <code>older</code> -- only whether it is <code>changed</code> or <code>unchanged</code>. (If it is <code>changed</code> on both sides, bisync still does the standard equality-check to avoid declaring a sync conflict unless it absolutely has to.)</p>
-<p>It is recommended to do a <code>--resync</code> when changing <code>--compare</code> settings, as otherwise your prior listing files may not contain the attributes you wish to compare (for example, they will not have stored checksums if you were not previously comparing checksums.)</p>
+<p><code>--compare</code> overrides any conflicting flags. For example,
+if you set the conflicting flags
+<code>--compare checksum --size-only</code>, <code>--size-only</code>
+will be ignored, and bisync will compare checksum and not size. To avoid
+confusion, it is recommended to use <em>either</em>
+<code>--compare</code> or the normal <code>sync</code> flags, but not
+both.</p>
+<p>If <code>--compare</code> includes <code>checksum</code> and both
+remotes support checksums but have no hash types in common with each
+other, checksums will be considered <em>only</em> for comparisons within
+the same side (to determine what has changed since the prior sync), but
+not for comparisons against the opposite side. If one side supports
+checksums and the other does not, checksums will only be considered on
+the side that supports them.</p>
+<p>When comparing with <code>checksum</code> and/or <code>size</code>
+without <code>modtime</code>, bisync cannot determine whether a file is
+<code>newer</code> or <code>older</code> -- only whether it is
+<code>changed</code> or <code>unchanged</code>. (If it is
+<code>changed</code> on both sides, bisync still does the standard
+equality-check to avoid declaring a sync conflict unless it absolutely
+has to.)</p>
+<p>It is recommended to do a <code>--resync</code> when changing
+<code>--compare</code> settings, as otherwise your prior listing files
+may not contain the attributes you wish to compare (for example, they
+will not have stored checksums if you were not previously comparing
+checksums.)</p>
 <h3 id="ignore-listing-checksum">--ignore-listing-checksum</h3>
-<p>When <code>--checksum</code> or <code>--compare checksum</code> is set, bisync will retrieve (or generate) checksums (for backends that support them) when creating the listings for both paths, and store the checksums in the listing files. <code>--ignore-listing-checksum</code> will disable this behavior, which may speed things up considerably, especially on backends (such as <a href="https://rclone.org/local/">local</a>) where hashes must be computed on the fly instead of retrieved. Please note the following:</p>
+<p>When <code>--checksum</code> or <code>--compare checksum</code> is
+set, bisync will retrieve (or generate) checksums (for backends that
+support them) when creating the listings for both paths, and store the
+checksums in the listing files. <code>--ignore-listing-checksum</code>
+will disable this behavior, which may speed things up considerably,
+especially on backends (such as <a
+href="https://rclone.org/local/">local</a>) where hashes must be
+computed on the fly instead of retrieved. Please note the following:</p>
 <ul>
-<li>As of <code>v1.66</code>, <code>--ignore-listing-checksum</code> is now automatically set when neither <code>--checksum</code> nor <code>--compare checksum</code> are in use (as the checksums would not be used for anything.)</li>
-<li><code>--ignore-listing-checksum</code> is NOT the same as <a href="https://rclone.org/docs/#ignore-checksum"><code>--ignore-checksum</code></a>, and you may wish to use one or the other, or both. In a nutshell: <code>--ignore-listing-checksum</code> controls whether checksums are considered when scanning for diffs, while <code>--ignore-checksum</code> controls whether checksums are considered during the copy/sync operations that follow, if there ARE diffs.</li>
-<li>Unless <code>--ignore-listing-checksum</code> is passed, bisync currently computes hashes for one path <em>even when there's no common hash with the other path</em> (for example, a <a href="https://rclone.org/crypt/#modification-times-and-hashes">crypt</a> remote.) This can still be beneficial, as the hashes will still be used to detect changes within the same side (if <code>--checksum</code> or <code>--compare checksum</code> is set), even if they can't be used to compare against the opposite side.</li>
-<li>If you wish to ignore listing checksums <em>only</em> on remotes where they are slow to compute, consider using <a href="#no-slow-hash"><code>--no-slow-hash</code></a> (or <a href="#slow-hash-sync-only"><code>--slow-hash-sync-only</code></a>) instead of <code>--ignore-listing-checksum</code>.</li>
-<li>If <code>--ignore-listing-checksum</code> is used simultaneously with <code>--compare checksum</code> (or <code>--checksum</code>), checksums will be ignored for bisync deltas, but still considered during the sync operations that follow (if deltas are detected based on modtime and/or size.)</li>
+<li>As of <code>v1.66</code>, <code>--ignore-listing-checksum</code> is
+now automatically set when neither <code>--checksum</code> nor
+<code>--compare checksum</code> are in use (as the checksums would not
+be used for anything.)</li>
+<li><code>--ignore-listing-checksum</code> is NOT the same as <a
+href="https://rclone.org/docs/#ignore-checksum"><code>--ignore-checksum</code></a>,
+and you may wish to use one or the other, or both. In a nutshell:
+<code>--ignore-listing-checksum</code> controls whether checksums are
+considered when scanning for diffs, while <code>--ignore-checksum</code>
+controls whether checksums are considered during the copy/sync
+operations that follow, if there ARE diffs.</li>
+<li>Unless <code>--ignore-listing-checksum</code> is passed, bisync
+currently computes hashes for one path <em>even when there's no common
+hash with the other path</em> (for example, a <a
+href="https://rclone.org/crypt/#modification-times-and-hashes">crypt</a>
+remote.) This can still be beneficial, as the hashes will still be used
+to detect changes within the same side (if <code>--checksum</code> or
+<code>--compare checksum</code> is set), even if they can't be used to
+compare against the opposite side.</li>
+<li>If you wish to ignore listing checksums <em>only</em> on remotes
+where they are slow to compute, consider using <a
+href="#no-slow-hash"><code>--no-slow-hash</code></a> (or <a
+href="#slow-hash-sync-only"><code>--slow-hash-sync-only</code></a>)
+instead of <code>--ignore-listing-checksum</code>.</li>
+<li>If <code>--ignore-listing-checksum</code> is used simultaneously
+with <code>--compare checksum</code> (or <code>--checksum</code>),
+checksums will be ignored for bisync deltas, but still considered during
+the sync operations that follow (if deltas are detected based on modtime
+and/or size.)</li>
 </ul>
 <h3 id="no-slow-hash">--no-slow-hash</h3>
-<p>On some remotes (notably <code>local</code>), checksums can dramatically slow down a bisync run, because hashes cannot be stored and need to be computed in real-time when they are requested. On other remotes (such as <code>drive</code>), they add practically no time at all. The <code>--no-slow-hash</code> flag will automatically skip checksums on remotes where they are slow, while still comparing them on others (assuming <a href="#compare"><code>--compare</code></a> includes <code>checksum</code>.) This can be useful when one of your bisync paths is slow but you still want to check checksums on the other, for a more robust sync.</p>
+<p>On some remotes (notably <code>local</code>), checksums can
+dramatically slow down a bisync run, because hashes cannot be stored and
+need to be computed in real-time when they are requested. On other
+remotes (such as <code>drive</code>), they add practically no time at
+all. The <code>--no-slow-hash</code> flag will automatically skip
+checksums on remotes where they are slow, while still comparing them on
+others (assuming <a href="#compare"><code>--compare</code></a> includes
+<code>checksum</code>.) This can be useful when one of your bisync paths
+is slow but you still want to check checksums on the other, for a more
+robust sync.</p>
 <h3 id="slow-hash-sync-only">--slow-hash-sync-only</h3>
-<p>Same as <a href="#no-slow-hash"><code>--no-slow-hash</code></a>, except slow hashes are still considered during sync calls. They are still NOT considered for determining deltas, nor or they included in listings. They are also skipped during <code>--resync</code>. The main use case for this flag is when you have a large number of files, but relatively few of them change from run to run -- so you don't want to check your entire tree every time (it would take too long), but you still want to consider checksums for the smaller group of files for which a <code>modtime</code> or <code>size</code> change was detected. Keep in mind that this speed savings comes with a safety trade-off: if a file's content were to change without a change to its <code>modtime</code> or <code>size</code>, bisync would not detect it, and it would not be synced.</p>
-<p><code>--slow-hash-sync-only</code> is only useful if both remotes share a common hash type (if they don't, bisync will automatically fall back to <code>--no-slow-hash</code>.) Both <code>--no-slow-hash</code> and <code>--slow-hash-sync-only</code> have no effect without <code>--compare checksum</code> (or <code>--checksum</code>).</p>
+<p>Same as <a href="#no-slow-hash"><code>--no-slow-hash</code></a>,
+except slow hashes are still considered during sync calls. They are
+still NOT considered for determining deltas, nor or they included in
+listings. They are also skipped during <code>--resync</code>. The main
+use case for this flag is when you have a large number of files, but
+relatively few of them change from run to run -- so you don't want to
+check your entire tree every time (it would take too long), but you
+still want to consider checksums for the smaller group of files for
+which a <code>modtime</code> or <code>size</code> change was detected.
+Keep in mind that this speed savings comes with a safety trade-off: if a
+file's content were to change without a change to its
+<code>modtime</code> or <code>size</code>, bisync would not detect it,
+and it would not be synced.</p>
+<p><code>--slow-hash-sync-only</code> is only useful if both remotes
+share a common hash type (if they don't, bisync will automatically fall
+back to <code>--no-slow-hash</code>.) Both <code>--no-slow-hash</code>
+and <code>--slow-hash-sync-only</code> have no effect without
+<code>--compare checksum</code> (or <code>--checksum</code>).</p>
 <h3 id="download-hash">--download-hash</h3>
-<p>If <code>--download-hash</code> is set, bisync will use best efforts to obtain an MD5 checksum by downloading and computing on-the-fly, when checksums are not otherwise available (for example, a remote that doesn't support them.) Note that since rclone has to download the entire file, this may dramatically slow down your bisync runs, and is also likely to use a lot of data, so it is probably not practical for bisync paths with a large total file size. However, it can be a good option for syncing small-but-important files with maximum accuracy (for example, a source code repo on a <code>crypt</code> remote.) An additional advantage over methods like <a href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a> is that the original file is not required for comparison (for example, <code>--download-hash</code> can be used to bisync two different crypt remotes with different passwords.)</p>
-<p>When <code>--download-hash</code> is set, bisync still looks for more efficient checksums first, and falls back to downloading only when none are found. It takes priority over conflicting flags such as <code>--no-slow-hash</code>. <code>--download-hash</code> is not suitable for <a href="#gdocs">Google Docs</a> and other files of unknown size, as their checksums would change from run to run (due to small variances in the internals of the generated export file.) Therefore, bisync automatically skips <code>--download-hash</code> for files with a size less than 0.</p>
-<p>See also: <a href="https://rclone.org/hasher/"><code>Hasher</code></a> backend, <a href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a> command, <a href="https://rclone.org/commands/rclone_check/"><code>rclone check --download</code></a> option, <a href="https://rclone.org/commands/rclone_md5sum/"><code>md5sum</code></a> command</p>
+<p>If <code>--download-hash</code> is set, bisync will use best efforts
+to obtain an MD5 checksum by downloading and computing on-the-fly, when
+checksums are not otherwise available (for example, a remote that
+doesn't support them.) Note that since rclone has to download the entire
+file, this may dramatically slow down your bisync runs, and is also
+likely to use a lot of data, so it is probably not practical for bisync
+paths with a large total file size. However, it can be a good option for
+syncing small-but-important files with maximum accuracy (for example, a
+source code repo on a <code>crypt</code> remote.) An additional
+advantage over methods like <a
+href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a>
+is that the original file is not required for comparison (for example,
+<code>--download-hash</code> can be used to bisync two different crypt
+remotes with different passwords.)</p>
+<p>When <code>--download-hash</code> is set, bisync still looks for more
+efficient checksums first, and falls back to downloading only when none
+are found. It takes priority over conflicting flags such as
+<code>--no-slow-hash</code>. <code>--download-hash</code> is not
+suitable for <a href="#gdocs">Google Docs</a> and other files of unknown
+size, as their checksums would change from run to run (due to small
+variances in the internals of the generated export file.) Therefore,
+bisync automatically skips <code>--download-hash</code> for files with a
+size less than 0.</p>
+<p>See also: <a
+href="https://rclone.org/hasher/"><code>Hasher</code></a> backend, <a
+href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a>
+command, <a
+href="https://rclone.org/commands/rclone_check/"><code>rclone check --download</code></a>
+option, <a
+href="https://rclone.org/commands/rclone_md5sum/"><code>md5sum</code></a>
+command</p>
 <h3 id="max-delete">--max-delete</h3>
-<p>As a safety check, if greater than the <code>--max-delete</code> percent of files were deleted on either the Path1 or Path2 filesystem, then bisync will abort with a warning message, without making any changes. The default <code>--max-delete</code> is <code>50%</code>. One way to trigger this limit is to rename a directory that contains more than half of your files. This will appear to bisync as a bunch of deleted files and a bunch of new files. This safety check is intended to block bisync from deleting all of the files on both filesystems due to a temporary network access issue, or if the user had inadvertently deleted the files on one side or the other. To force the sync, either set a different delete percentage limit, e.g. <code>--max-delete 75</code> (allows up to 75% deletion), or use <code>--force</code> to bypass the check.</p>
-<p>Also see the <a href="#all-files-changed">all files changed</a> check.</p>
+<p>As a safety check, if greater than the <code>--max-delete</code>
+percent of files were deleted on either the Path1 or Path2 filesystem,
+then bisync will abort with a warning message, without making any
+changes. The default <code>--max-delete</code> is <code>50%</code>. One
+way to trigger this limit is to rename a directory that contains more
+than half of your files. This will appear to bisync as a bunch of
+deleted files and a bunch of new files. This safety check is intended to
+block bisync from deleting all of the files on both filesystems due to a
+temporary network access issue, or if the user had inadvertently deleted
+the files on one side or the other. To force the sync, either set a
+different delete percentage limit, e.g. <code>--max-delete 75</code>
+(allows up to 75% deletion), or use <code>--force</code> to bypass the
+check.</p>
+<p>Also see the <a href="#all-files-changed">all files changed</a>
+check.</p>
 <h3 id="filters-file">--filters-file</h3>
-<p>By using rclone filter features you can exclude file types or directory sub-trees from the sync. See the <a href="#filtering">bisync filters</a> section and generic <a href="https://rclone.org/filtering/#filter-from-read-filtering-patterns-from-a-file">--filter-from</a> documentation. An <a href="#example-filters-file">example filters file</a> contains filters for non-allowed files for synching with Dropbox.</p>
-<p>If you make changes to your filters file then bisync requires a run with <code>--resync</code>. This is a safety feature, which prevents existing files on the Path1 and/or Path2 side from seeming to disappear from view (since they are excluded in the new listings), which would fool bisync into seeing them as deleted (as compared to the prior run listings), and then bisync would proceed to delete them for real.</p>
-<p>To block this from happening, bisync calculates an MD5 hash of the filters file and stores the hash in a <code>.md5</code> file in the same place as your filters file. On the next run with <code>--filters-file</code> set, bisync re-calculates the MD5 hash of the current filters file and compares it to the hash stored in the <code>.md5</code> file. If they don't match, the run aborts with a critical error and thus forces you to do a <code>--resync</code>, likely avoiding a disaster.</p>
+<p>By using rclone filter features you can exclude file types or
+directory sub-trees from the sync. See the <a href="#filtering">bisync
+filters</a> section and generic <a
+href="https://rclone.org/filtering/#filter-from-read-filtering-patterns-from-a-file">--filter-from</a>
+documentation. An <a href="#example-filters-file">example filters
+file</a> contains filters for non-allowed files for synching with
+Dropbox.</p>
+<p>If you make changes to your filters file then bisync requires a run
+with <code>--resync</code>. This is a safety feature, which prevents
+existing files on the Path1 and/or Path2 side from seeming to disappear
+from view (since they are excluded in the new listings), which would
+fool bisync into seeing them as deleted (as compared to the prior run
+listings), and then bisync would proceed to delete them for real.</p>
+<p>To block this from happening, bisync calculates an MD5 hash of the
+filters file and stores the hash in a <code>.md5</code> file in the same
+place as your filters file. On the next run with
+<code>--filters-file</code> set, bisync re-calculates the MD5 hash of
+the current filters file and compares it to the hash stored in the
+<code>.md5</code> file. If they don't match, the run aborts with a
+critical error and thus forces you to do a <code>--resync</code>, likely
+avoiding a disaster.</p>
 <h3 id="conflict-resolve">--conflict-resolve CHOICE</h3>
-<p>In bisync, a "conflict" is a file that is <em>new</em> or <em>changed</em> on <em>both sides</em> (relative to the prior run) AND is <em>not currently identical</em> on both sides. <code>--conflict-resolve</code> controls how bisync handles such a scenario. The currently supported options are:</p>
+<p>In bisync, a "conflict" is a file that is <em>new</em> or
+<em>changed</em> on <em>both sides</em> (relative to the prior run) AND
+is <em>not currently identical</em> on both sides.
+<code>--conflict-resolve</code> controls how bisync handles such a
+scenario. The currently supported options are:</p>
 <ul>
-<li><code>none</code> - (the default) - do not attempt to pick a winner, keep and rename both files according to <a href="#conflict-loser"><code>--conflict-loser</code></a> and <a href="#conflict-suffix"><code>--conflict-suffix</code></a> settings. For example, with the default settings, <code>file.txt</code> on Path1 is renamed <code>file.txt.conflict1</code> and <code>file.txt</code> on Path2 is renamed <code>file.txt.conflict2</code>. Both are copied to the opposite path during the run, so both sides end up with a copy of both files. (As <code>none</code> is the default, it is not necessary to specify <code>--conflict-resolve none</code> -- you can just omit the flag.)</li>
-<li><code>newer</code> - the newer file (by <code>modtime</code>) is considered the winner and is copied without renaming. The older file (the "loser") is handled according to <code>--conflict-loser</code> and <code>--conflict-suffix</code> settings (either renamed or deleted.) For example, if <code>file.txt</code> on Path1 is newer than <code>file.txt</code> on Path2, the result on both sides (with other default settings) will be <code>file.txt</code> (winner from Path1) and <code>file.txt.conflict1</code> (loser from Path2).</li>
-<li><code>older</code> - same as <code>newer</code>, except the older file is considered the winner, and the newer file is considered the loser.</li>
-<li><code>larger</code> - the larger file (by <code>size</code>) is considered the winner (regardless of <code>modtime</code>, if any).</li>
-<li><code>smaller</code> - the smaller file (by <code>size</code>) is considered the winner (regardless of <code>modtime</code>, if any).</li>
-<li><code>path1</code> - the version from Path1 is unconditionally considered the winner (regardless of <code>modtime</code> and <code>size</code>, if any). This can be useful if one side is usually more trusted or up-to-date than the other.</li>
-<li><code>path2</code> - same as <code>path1</code>, except the path2 version is considered the winner.</li>
+<li><code>none</code> - (the default) - do not attempt to pick a winner,
+keep and rename both files according to <a
+href="#conflict-loser"><code>--conflict-loser</code></a> and <a
+href="#conflict-suffix"><code>--conflict-suffix</code></a> settings. For
+example, with the default settings, <code>file.txt</code> on Path1 is
+renamed <code>file.txt.conflict1</code> and <code>file.txt</code> on
+Path2 is renamed <code>file.txt.conflict2</code>. Both are copied to the
+opposite path during the run, so both sides end up with a copy of both
+files. (As <code>none</code> is the default, it is not necessary to
+specify <code>--conflict-resolve none</code> -- you can just omit the
+flag.)</li>
+<li><code>newer</code> - the newer file (by <code>modtime</code>) is
+considered the winner and is copied without renaming. The older file
+(the "loser") is handled according to <code>--conflict-loser</code> and
+<code>--conflict-suffix</code> settings (either renamed or deleted.) For
+example, if <code>file.txt</code> on Path1 is newer than
+<code>file.txt</code> on Path2, the result on both sides (with other
+default settings) will be <code>file.txt</code> (winner from Path1) and
+<code>file.txt.conflict1</code> (loser from Path2).</li>
+<li><code>older</code> - same as <code>newer</code>, except the older
+file is considered the winner, and the newer file is considered the
+loser.</li>
+<li><code>larger</code> - the larger file (by <code>size</code>) is
+considered the winner (regardless of <code>modtime</code>, if any).</li>
+<li><code>smaller</code> - the smaller file (by <code>size</code>) is
+considered the winner (regardless of <code>modtime</code>, if any).</li>
+<li><code>path1</code> - the version from Path1 is unconditionally
+considered the winner (regardless of <code>modtime</code> and
+<code>size</code>, if any). This can be useful if one side is usually
+more trusted or up-to-date than the other.</li>
+<li><code>path2</code> - same as <code>path1</code>, except the path2
+version is considered the winner.</li>
 </ul>
-<p>For all of the above options, note the following: - If either of the underlying remotes lacks support for the chosen method, it will be ignored and fall back to <code>none</code>. (For example, if <code>--conflict-resolve newer</code> is set, but one of the paths uses a remote that doesn't support <code>modtime</code>.) - If a winner can't be determined because the chosen method's attribute is missing or equal, it will be ignored and fall back to <code>none</code>. (For example, if <code>--conflict-resolve newer</code> is set, but the Path1 and Path2 modtimes are identical, even if the sizes may differ.) - If the file's content is currently identical on both sides, it is not considered a "conflict", even if new or changed on both sides since the prior sync. (For example, if you made a change on one side and then synced it to the other side by other means.) Therefore, none of the conflict resolution flags apply in this scenario. - The conflict resolution flags do not apply during a <code>--resync</code>, as there is no "prior run" to speak of (but see <a href="#resync-mode"><code>--resync-mode</code></a> for similar options.)</p>
+<p>For all of the above options, note the following: - If either of the
+underlying remotes lacks support for the chosen method, it will be
+ignored and fall back to <code>none</code>. (For example, if
+<code>--conflict-resolve newer</code> is set, but one of the paths uses
+a remote that doesn't support <code>modtime</code>.) - If a winner can't
+be determined because the chosen method's attribute is missing or equal,
+it will be ignored and fall back to <code>none</code>. (For example, if
+<code>--conflict-resolve newer</code> is set, but the Path1 and Path2
+modtimes are identical, even if the sizes may differ.) - If the file's
+content is currently identical on both sides, it is not considered a
+"conflict", even if new or changed on both sides since the prior sync.
+(For example, if you made a change on one side and then synced it to the
+other side by other means.) Therefore, none of the conflict resolution
+flags apply in this scenario. - The conflict resolution flags do not
+apply during a <code>--resync</code>, as there is no "prior run" to
+speak of (but see <a href="#resync-mode"><code>--resync-mode</code></a>
+for similar options.)</p>
 <h3 id="conflict-loser">--conflict-loser CHOICE</h3>
-<p><code>--conflict-loser</code> determines what happens to the "loser" of a sync conflict (when <a href="#conflict-resolve"><code>--conflict-resolve</code></a> determines a winner) or to both files (when there is no winner.) The currently supported options are:</p>
+<p><code>--conflict-loser</code> determines what happens to the "loser"
+of a sync conflict (when <a
+href="#conflict-resolve"><code>--conflict-resolve</code></a> determines
+a winner) or to both files (when there is no winner.) The currently
+supported options are:</p>
 <ul>
-<li><code>num</code> - (the default) - auto-number the conflicts by automatically appending the next available number to the <code>--conflict-suffix</code>, in chronological order. For example, with the default settings, the first conflict for <code>file.txt</code> will be renamed <code>file.txt.conflict1</code>. If <code>file.txt.conflict1</code> already exists, <code>file.txt.conflict2</code> will be used instead (etc., up to a maximum of 9223372036854775807 conflicts.)</li>
-<li><code>pathname</code> - rename the conflicts according to which side they came from, which was the default behavior prior to <code>v1.66</code>. For example, with <code>--conflict-suffix path</code>, <code>file.txt</code> from Path1 will be renamed <code>file.txt.path1</code>, and <code>file.txt</code> from Path2 will be renamed <code>file.txt.path2</code>. If two non-identical suffixes are provided (ex. <code>--conflict-suffix cloud,local</code>), the trailing digit is omitted. Importantly, note that with <code>pathname</code>, there is no auto-numbering beyond <code>2</code>, so if <code>file.txt.path2</code> somehow already exists, it will be overwritten. Using a dynamic date variable in your <code>--conflict-suffix</code> (see below) is one possible way to avoid this. Note also that conflicts-of-conflicts are possible, if the original conflict is not manually resolved -- for example, if for some reason you edited <code>file.txt.path1</code> on both sides, and those edits were different, the result would be <code>file.txt.path1.path1</code> and <code>file.txt.path1.path2</code> (in addition to <code>file.txt.path2</code>.)</li>
-<li><code>delete</code> - keep the winner only and delete the loser, instead of renaming it. If a winner cannot be determined (see <code>--conflict-resolve</code> for details on how this could happen), <code>delete</code> is ignored and the default <code>num</code> is used instead (i.e. both versions are kept and renamed, and neither is deleted.) <code>delete</code> is inherently the most destructive option, so use it only with care.</li>
+<li><code>num</code> - (the default) - auto-number the conflicts by
+automatically appending the next available number to the
+<code>--conflict-suffix</code>, in chronological order. For example,
+with the default settings, the first conflict for <code>file.txt</code>
+will be renamed <code>file.txt.conflict1</code>. If
+<code>file.txt.conflict1</code> already exists,
+<code>file.txt.conflict2</code> will be used instead (etc., up to a
+maximum of 9223372036854775807 conflicts.)</li>
+<li><code>pathname</code> - rename the conflicts according to which side
+they came from, which was the default behavior prior to
+<code>v1.66</code>. For example, with
+<code>--conflict-suffix path</code>, <code>file.txt</code> from Path1
+will be renamed <code>file.txt.path1</code>, and <code>file.txt</code>
+from Path2 will be renamed <code>file.txt.path2</code>. If two
+non-identical suffixes are provided (ex.
+<code>--conflict-suffix cloud,local</code>), the trailing digit is
+omitted. Importantly, note that with <code>pathname</code>, there is no
+auto-numbering beyond <code>2</code>, so if <code>file.txt.path2</code>
+somehow already exists, it will be overwritten. Using a dynamic date
+variable in your <code>--conflict-suffix</code> (see below) is one
+possible way to avoid this. Note also that conflicts-of-conflicts are
+possible, if the original conflict is not manually resolved -- for
+example, if for some reason you edited <code>file.txt.path1</code> on
+both sides, and those edits were different, the result would be
+<code>file.txt.path1.path1</code> and <code>file.txt.path1.path2</code>
+(in addition to <code>file.txt.path2</code>.)</li>
+<li><code>delete</code> - keep the winner only and delete the loser,
+instead of renaming it. If a winner cannot be determined (see
+<code>--conflict-resolve</code> for details on how this could happen),
+<code>delete</code> is ignored and the default <code>num</code> is used
+instead (i.e. both versions are kept and renamed, and neither is
+deleted.) <code>delete</code> is inherently the most destructive option,
+so use it only with care.</li>
 </ul>
-<p>For all of the above options, note that if a winner cannot be determined (see <code>--conflict-resolve</code> for details on how this could happen), or if <code>--conflict-resolve</code> is not in use, <em>both</em> files will be renamed.</p>
+<p>For all of the above options, note that if a winner cannot be
+determined (see <code>--conflict-resolve</code> for details on how this
+could happen), or if <code>--conflict-resolve</code> is not in use,
+<em>both</em> files will be renamed.</p>
 <h3 id="conflict-suffix">--conflict-suffix STRING[,STRING]</h3>
-<p><code>--conflict-suffix</code> controls the suffix that is appended when bisync renames a <a href="#conflict-loser"><code>--conflict-loser</code></a> (default: <code>conflict</code>). <code>--conflict-suffix</code> will accept either one string or two comma-separated strings to assign different suffixes to Path1 vs. Path2. This may be helpful later in identifying the source of the conflict. (For example, <code>--conflict-suffix dropboxconflict,laptopconflict</code>)</p>
-<p>With <code>--conflict-loser num</code>, a number is always appended to the suffix. With <code>--conflict-loser pathname</code>, a number is appended only when one suffix is specified (or when two identical suffixes are specified.) i.e. with <code>--conflict-loser pathname</code>, all of the following would produce exactly the same result:</p>
+<p><code>--conflict-suffix</code> controls the suffix that is appended
+when bisync renames a <a
+href="#conflict-loser"><code>--conflict-loser</code></a> (default:
+<code>conflict</code>). <code>--conflict-suffix</code> will accept
+either one string or two comma-separated strings to assign different
+suffixes to Path1 vs. Path2. This may be helpful later in identifying
+the source of the conflict. (For example,
+<code>--conflict-suffix dropboxconflict,laptopconflict</code>)</p>
+<p>With <code>--conflict-loser num</code>, a number is always appended
+to the suffix. With <code>--conflict-loser pathname</code>, a number is
+appended only when one suffix is specified (or when two identical
+suffixes are specified.) i.e. with
+<code>--conflict-loser pathname</code>, all of the following would
+produce exactly the same result:</p>
 <pre><code>--conflict-suffix path
 --conflict-suffix path,path
 --conflict-suffix path1,path2</code></pre>
-<p>Suffixes may be as short as 1 character. By default, the suffix is appended after any other extensions (ex. <code>file.jpg.conflict1</code>), however, this can be changed with the <a href="https://rclone.org/docs/#suffix-keep-extension"><code>--suffix-keep-extension</code></a> flag (i.e. to instead result in <code>file.conflict1.jpg</code>).</p>
-<p><code>--conflict-suffix</code> supports several <em>dynamic date variables</em> when enclosed in curly braces as globs. This can be helpful to track the date and/or time that each conflict was handled by bisync. For example:</p>
+<p>Suffixes may be as short as 1 character. By default, the suffix is
+appended after any other extensions (ex.
+<code>file.jpg.conflict1</code>), however, this can be changed with the
+<a
+href="https://rclone.org/docs/#suffix-keep-extension"><code>--suffix-keep-extension</code></a>
+flag (i.e. to instead result in <code>file.conflict1.jpg</code>).</p>
+<p><code>--conflict-suffix</code> supports several <em>dynamic date
+variables</em> when enclosed in curly braces as globs. This can be
+helpful to track the date and/or time that each conflict was handled by
+bisync. For example:</p>
 <pre><code>--conflict-suffix {DateOnly}-conflict
 // result: myfile.txt.2006-01-02-conflict1</code></pre>
-<p>All of the formats described <a href="https://pkg.go.dev/time#pkg-constants">here</a> and <a href="https://pkg.go.dev/time#example-Time.Format">here</a> are supported, but take care to ensure that your chosen format does not use any characters that are illegal on your remotes (for example, macOS does not allow colons in filenames, and slashes are also best avoided as they are often interpreted as directory separators.) To address this particular issue, an additional <code>{MacFriendlyTime}</code> (or just <code>{mac}</code>) option is supported, which results in <code>2006-01-02 0304PM</code>.</p>
-<p>Note that <code>--conflict-suffix</code> is entirely separate from rclone's main <a href="https://rclone.org/docs/#suffix-suffix"><code>--sufix</code></a> flag. This is intentional, as users may wish to use both flags simultaneously, if also using <a href="#backup-dir1-and-backup-dir2"><code>--backup-dir</code></a>.</p>
-<p>Finally, note that the default in bisync prior to <code>v1.66</code> was to rename conflicts with <code>..path1</code> and <code>..path2</code> (with two periods, and <code>path</code> instead of <code>conflict</code>.) Bisync now defaults to a single dot instead of a double dot, but additional dots can be added by including them in the specified suffix string. For example, for behavior equivalent to the previous default, use:</p>
+<p>All of the formats described <a
+href="https://pkg.go.dev/time#pkg-constants">here</a> and <a
+href="https://pkg.go.dev/time#example-Time.Format">here</a> are
+supported, but take care to ensure that your chosen format does not use
+any characters that are illegal on your remotes (for example, macOS does
+not allow colons in filenames, and slashes are also best avoided as they
+are often interpreted as directory separators.) To address this
+particular issue, an additional <code>{MacFriendlyTime}</code> (or just
+<code>{mac}</code>) option is supported, which results in
+<code>2006-01-02 0304PM</code>.</p>
+<p>Note that <code>--conflict-suffix</code> is entirely separate from
+rclone's main <a
+href="https://rclone.org/docs/#suffix-suffix"><code>--sufix</code></a>
+flag. This is intentional, as users may wish to use both flags
+simultaneously, if also using <a
+href="#backup-dir1-and-backup-dir2"><code>--backup-dir</code></a>.</p>
+<p>Finally, note that the default in bisync prior to <code>v1.66</code>
+was to rename conflicts with <code>..path1</code> and
+<code>..path2</code> (with two periods, and <code>path</code> instead of
+<code>conflict</code>.) Bisync now defaults to a single dot instead of a
+double dot, but additional dots can be added by including them in the
+specified suffix string. For example, for behavior equivalent to the
+previous default, use:</p>
 <pre><code>[--conflict-resolve none] --conflict-loser pathname --conflict-suffix .path</code></pre>
 <h3 id="check-sync">--check-sync</h3>
-<p>Enabled by default, the check-sync function checks that all of the same files exist in both the Path1 and Path2 history listings. This <em>check-sync</em> integrity check is performed at the end of the sync run by default. Any untrapped failing copy/deletes between the two paths might result in differences between the two listings and in the untracked file content differences between the two paths. A resync run would correct the error.</p>
-<p>Note that the default-enabled integrity check locally executes a load of both the final Path1 and Path2 listings, and thus adds to the run time of a sync. Using <code>--check-sync=false</code> will disable it and may significantly reduce the sync run times for very large numbers of files.</p>
-<p>The check may be run manually with <code>--check-sync=only</code>. It runs only the integrity check and terminates without actually synching.</p>
-<p>Note that currently, <code>--check-sync</code> <strong>only checks listing snapshots and NOT the actual files on the remotes.</strong> Note also that the listing snapshots will not know about any changes that happened during or after the latest bisync run, as those will be discovered on the next run. Therefore, while listings should always match <em>each other</em> at the end of a bisync run, it is <em>expected</em> that they will not match the underlying remotes, nor will the remotes match each other, if there were changes during or after the run. This is normal, and any differences will be detected and synced on the next run.</p>
-<p>For a robust integrity check of the current state of the remotes (as opposed to just their listing snapshots), consider using <a href="commands/rclone_check/"><code>check</code></a> (or <a href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a>, if at least one path is a <code>crypt</code> remote) instead of <code>--check-sync</code>, keeping in mind that differences are expected if files changed during or after your last bisync run.</p>
+<p>Enabled by default, the check-sync function checks that all of the
+same files exist in both the Path1 and Path2 history listings. This
+<em>check-sync</em> integrity check is performed at the end of the sync
+run by default. Any untrapped failing copy/deletes between the two paths
+might result in differences between the two listings and in the
+untracked file content differences between the two paths. A resync run
+would correct the error.</p>
+<p>Note that the default-enabled integrity check locally executes a load
+of both the final Path1 and Path2 listings, and thus adds to the run
+time of a sync. Using <code>--check-sync=false</code> will disable it
+and may significantly reduce the sync run times for very large numbers
+of files.</p>
+<p>The check may be run manually with <code>--check-sync=only</code>. It
+runs only the integrity check and terminates without actually
+synching.</p>
+<p>Note that currently, <code>--check-sync</code> <strong>only checks
+listing snapshots and NOT the actual files on the remotes.</strong> Note
+also that the listing snapshots will not know about any changes that
+happened during or after the latest bisync run, as those will be
+discovered on the next run. Therefore, while listings should always
+match <em>each other</em> at the end of a bisync run, it is
+<em>expected</em> that they will not match the underlying remotes, nor
+will the remotes match each other, if there were changes during or after
+the run. This is normal, and any differences will be detected and synced
+on the next run.</p>
+<p>For a robust integrity check of the current state of the remotes (as
+opposed to just their listing snapshots), consider using <a
+href="commands/rclone_check/"><code>check</code></a> (or <a
+href="https://rclone.org/commands/rclone_cryptcheck/"><code>cryptcheck</code></a>,
+if at least one path is a <code>crypt</code> remote) instead of
+<code>--check-sync</code>, keeping in mind that differences are expected
+if files changed during or after your last bisync run.</p>
 <p>For example, a possible sequence could look like this:</p>
 <ol type="1">
 <li>Normally scheduled bisync run:</li>
 </ol>
 <pre><code>rclone bisync Path1 Path2 -MPc --check-access --max-delete 10 --filters-file /path/to/filters.txt -v --no-cleanup --ignore-listing-checksum --disable ListR --checkers=16 --drive-pacer-min-sleep=10ms --create-empty-src-dirs --resilient</code></pre>
 <ol start="2" type="1">
-<li>Periodic independent integrity check (perhaps scheduled nightly or weekly):</li>
+<li>Periodic independent integrity check (perhaps scheduled nightly or
+weekly):</li>
 </ol>
 <pre><code>rclone check -MvPc Path1 Path2 --filter-from /path/to/filters.txt</code></pre>
 <ol start="3" type="1">
-<li>If diffs are found, you have some choices to correct them. If one side is more up-to-date and you want to make the other side match it, you could run:</li>
+<li>If diffs are found, you have some choices to correct them. If one
+side is more up-to-date and you want to make the other side match it,
+you could run:</li>
 </ol>
 <pre><code>rclone sync Path1 Path2 --filter-from /path/to/filters.txt --create-empty-src-dirs -MPc -v</code></pre>
 <p>(or switch Path1 and Path2 to make Path2 the source-of-truth)</p>
-<p>Or, if neither side is totally up-to-date, you could run a <code>--resync</code> to bring them back into agreement (but remember that this could cause deleted files to re-appear.)</p>
-<p>*Note also that <code>rclone check</code> does not currently include empty directories, so if you want to know if any empty directories are out of sync, consider alternatively running the above <code>rclone sync</code> command with <code>--dry-run</code> added.</p>
-<p>See also: <a href="#concurrent-modifications">Concurrent modifications</a>, <a href="#resilient"><code>--resilient</code></a></p>
+<p>Or, if neither side is totally up-to-date, you could run a
+<code>--resync</code> to bring them back into agreement (but remember
+that this could cause deleted files to re-appear.)</p>
+<p>*Note also that <code>rclone check</code> does not currently include
+empty directories, so if you want to know if any empty directories are
+out of sync, consider alternatively running the above
+<code>rclone sync</code> command with <code>--dry-run</code> added.</p>
+<p>See also: <a href="#concurrent-modifications">Concurrent
+modifications</a>, <a href="#resilient"><code>--resilient</code></a></p>
 <h3 id="resilient">--resilient</h3>
-<p><strong><em>Caution: this is an experimental feature. Use at your own risk!</em></strong></p>
-<p>By default, most errors or interruptions will cause bisync to abort and require <a href="#resync"><code>--resync</code></a> to recover. This is a safety feature, to prevent bisync from running again until a user checks things out. However, in some cases, bisync can go too far and enforce a lockout when one isn't actually necessary, like for certain less-serious errors that might resolve themselves on the next run. When <code>--resilient</code> is specified, bisync tries its best to recover and self-correct, and only requires <code>--resync</code> as a last resort when a human's involvement is absolutely necessary. The intended use case is for running bisync as a background process (such as via scheduled <a href="#cron">cron</a>).</p>
-<p>When using <code>--resilient</code> mode, bisync will still report the error and abort, however it will not lock out future runs -- allowing the possibility of retrying at the next normally scheduled time, without requiring a <code>--resync</code> first. Examples of such retryable errors include access test failures, missing listing files, and filter change detections. These safety features will still prevent the <em>current</em> run from proceeding -- the difference is that if conditions have improved by the time of the <em>next</em> run, that next run will be allowed to proceed. Certain more serious errors will still enforce a <code>--resync</code> lockout, even in <code>--resilient</code> mode, to prevent data loss.</p>
-<p>Behavior of <code>--resilient</code> may change in a future version. (See also: <a href="#recover"><code>--recover</code></a>, <a href="#max-lock"><code>--max-lock</code></a>, <a href="#graceful-shutdown">Graceful Shutdown</a>)</p>
+<p><strong><em>Caution: this is an experimental feature. Use at your own
+risk!</em></strong></p>
+<p>By default, most errors or interruptions will cause bisync to abort
+and require <a href="#resync"><code>--resync</code></a> to recover. This
+is a safety feature, to prevent bisync from running again until a user
+checks things out. However, in some cases, bisync can go too far and
+enforce a lockout when one isn't actually necessary, like for certain
+less-serious errors that might resolve themselves on the next run. When
+<code>--resilient</code> is specified, bisync tries its best to recover
+and self-correct, and only requires <code>--resync</code> as a last
+resort when a human's involvement is absolutely necessary. The intended
+use case is for running bisync as a background process (such as via
+scheduled <a href="#cron">cron</a>).</p>
+<p>When using <code>--resilient</code> mode, bisync will still report
+the error and abort, however it will not lock out future runs --
+allowing the possibility of retrying at the next normally scheduled
+time, without requiring a <code>--resync</code> first. Examples of such
+retryable errors include access test failures, missing listing files,
+and filter change detections. These safety features will still prevent
+the <em>current</em> run from proceeding -- the difference is that if
+conditions have improved by the time of the <em>next</em> run, that next
+run will be allowed to proceed. Certain more serious errors will still
+enforce a <code>--resync</code> lockout, even in
+<code>--resilient</code> mode, to prevent data loss.</p>
+<p>Behavior of <code>--resilient</code> may change in a future version.
+(See also: <a href="#recover"><code>--recover</code></a>, <a
+href="#max-lock"><code>--max-lock</code></a>, <a
+href="#graceful-shutdown">Graceful Shutdown</a>)</p>
 <h3 id="recover">--recover</h3>
-<p>If <code>--recover</code> is set, in the event of a sudden interruption or other un-graceful shutdown, bisync will attempt to automatically recover on the next run, instead of requiring <code>--resync</code>. Bisync is able to recover robustly by keeping one "backup" listing at all times, representing the state of both paths after the last known successful sync. Bisync can then compare the current state with this snapshot to determine which changes it needs to retry. Changes that were synced after this snapshot (during the run that was later interrupted) will appear to bisync as if they are "new or changed on both sides", but in most cases this is not a problem, as bisync will simply do its usual "equality check" and learn that no action needs to be taken on these files, since they are already identical on both sides.</p>
-<p>In the rare event that a file is synced successfully during a run that later aborts, and then that same file changes AGAIN before the next run, bisync will think it is a sync conflict, and handle it accordingly. (From bisync's perspective, the file has changed on both sides since the last trusted sync, and the files on either side are not currently identical.) Therefore, <code>--recover</code> carries with it a slightly increased chance of having conflicts -- though in practice this is pretty rare, as the conditions required to cause it are quite specific. This risk can be reduced by using bisync's <a href="#graceful-shutdown">"Graceful Shutdown"</a> mode (triggered by sending <code>SIGINT</code> or <code>Ctrl+C</code>), when you have the choice, instead of forcing a sudden termination.</p>
-<p><code>--recover</code> and <code>--resilient</code> are similar, but distinct -- the main difference is that <code>--resilient</code> is about <em>retrying</em>, while <code>--recover</code> is about <em>recovering</em>. Most users will probably want both. <code>--resilient</code> allows retrying when bisync has chosen to abort itself due to safety features such as failing <code>--check-access</code> or detecting a filter change. <code>--resilient</code> does not cover external interruptions such as a user shutting down their computer in the middle of a sync -- that is what <code>--recover</code> is for.</p>
+<p>If <code>--recover</code> is set, in the event of a sudden
+interruption or other un-graceful shutdown, bisync will attempt to
+automatically recover on the next run, instead of requiring
+<code>--resync</code>. Bisync is able to recover robustly by keeping one
+"backup" listing at all times, representing the state of both paths
+after the last known successful sync. Bisync can then compare the
+current state with this snapshot to determine which changes it needs to
+retry. Changes that were synced after this snapshot (during the run that
+was later interrupted) will appear to bisync as if they are "new or
+changed on both sides", but in most cases this is not a problem, as
+bisync will simply do its usual "equality check" and learn that no
+action needs to be taken on these files, since they are already
+identical on both sides.</p>
+<p>In the rare event that a file is synced successfully during a run
+that later aborts, and then that same file changes AGAIN before the next
+run, bisync will think it is a sync conflict, and handle it accordingly.
+(From bisync's perspective, the file has changed on both sides since the
+last trusted sync, and the files on either side are not currently
+identical.) Therefore, <code>--recover</code> carries with it a slightly
+increased chance of having conflicts -- though in practice this is
+pretty rare, as the conditions required to cause it are quite specific.
+This risk can be reduced by using bisync's <a
+href="#graceful-shutdown">"Graceful Shutdown"</a> mode (triggered by
+sending <code>SIGINT</code> or <code>Ctrl+C</code>), when you have the
+choice, instead of forcing a sudden termination.</p>
+<p><code>--recover</code> and <code>--resilient</code> are similar, but
+distinct -- the main difference is that <code>--resilient</code> is
+about <em>retrying</em>, while <code>--recover</code> is about
+<em>recovering</em>. Most users will probably want both.
+<code>--resilient</code> allows retrying when bisync has chosen to abort
+itself due to safety features such as failing
+<code>--check-access</code> or detecting a filter change.
+<code>--resilient</code> does not cover external interruptions such as a
+user shutting down their computer in the middle of a sync -- that is
+what <code>--recover</code> is for.</p>
 <h3 id="max-lock">--max-lock</h3>
-<p>Bisync uses <a href="#lock-file">lock files</a> as a safety feature to prevent interference from other bisync runs while it is running. Bisync normally removes these lock files at the end of a run, but if bisync is abruptly interrupted, these files will be left behind. By default, they will lock out all future runs, until the user has a chance to manually check things out and remove the lock. As an alternative, <code>--max-lock</code> can be used to make them automatically expire after a certain period of time, so that future runs are not locked out forever, and auto-recovery is possible. <code>--max-lock</code> can be any duration <code>2m</code> or greater (or <code>0</code> to disable). If set, lock files older than this will be considered "expired", and future runs will be allowed to disregard them and proceed. (Note that the <code>--max-lock</code> duration must be set by the process that left the lock file -- not the later one interpreting it.)</p>
-<p>If set, bisync will also "renew" these lock files every <code>--max-lock minus one minute</code> throughout a run, for extra safety. (For example, with <code>--max-lock 5m</code>, bisync would renew the lock file (for another 5 minutes) every 4 minutes until the run has completed.) In other words, it should not be possible for a lock file to pass its expiration time while the process that created it is still running -- and you can therefore be reasonably sure that any <em>expired</em> lock file you may find was left there by an interrupted run, not one that is still running and just taking awhile.</p>
-<p>If <code>--max-lock</code> is <code>0</code> or not set, the default is that lock files will never expire, and will block future runs (of these same two bisync paths) indefinitely.</p>
-<p>For maximum resilience from disruptions, consider setting a relatively short duration like <code>--max-lock 2m</code> along with <a href="#resilient"><code>--resilient</code></a> and <a href="#recover"><code>--recover</code></a>, and a relatively frequent <a href="#cron">cron schedule</a>. The result will be a very robust "set-it-and-forget-it" bisync run that can automatically bounce back from almost any interruption it might encounter, without requiring the user to get involved and run a <code>--resync</code>. (See also: <a href="#graceful-shutdown">Graceful Shutdown</a> mode)</p>
-<h3 id="backup-dir1-and---backup-dir2">--backup-dir1 and --backup-dir2</h3>
-<p>As of <code>v1.66</code>, <a href="https://rclone.org/docs/#backup-dir-dir"><code>--backup-dir</code></a> is supported in bisync. Because <code>--backup-dir</code> must be a non-overlapping path on the same remote, Bisync has introduced new <code>--backup-dir1</code> and <code>--backup-dir2</code> flags to support separate backup-dirs for <code>Path1</code> and <code>Path2</code> (bisyncing between different remotes with <code>--backup-dir</code> would not otherwise be possible.) <code>--backup-dir1</code> and <code>--backup-dir2</code> can use different remotes from each other, but <code>--backup-dir1</code> must use the same remote as <code>Path1</code>, and <code>--backup-dir2</code> must use the same remote as <code>Path2</code>. Each backup directory must not overlap its respective bisync Path without being excluded by a filter rule.</p>
-<p>The standard <code>--backup-dir</code> will also work, if both paths use the same remote (but note that deleted files from both paths would be mixed together in the same dir). If either <code>--backup-dir1</code> and <code>--backup-dir2</code> are set, they will override <code>--backup-dir</code>.</p>
+<p>Bisync uses <a href="#lock-file">lock files</a> as a safety feature
+to prevent interference from other bisync runs while it is running.
+Bisync normally removes these lock files at the end of a run, but if
+bisync is abruptly interrupted, these files will be left behind. By
+default, they will lock out all future runs, until the user has a chance
+to manually check things out and remove the lock. As an alternative,
+<code>--max-lock</code> can be used to make them automatically expire
+after a certain period of time, so that future runs are not locked out
+forever, and auto-recovery is possible. <code>--max-lock</code> can be
+any duration <code>2m</code> or greater (or <code>0</code> to disable).
+If set, lock files older than this will be considered "expired", and
+future runs will be allowed to disregard them and proceed. (Note that
+the <code>--max-lock</code> duration must be set by the process that
+left the lock file -- not the later one interpreting it.)</p>
+<p>If set, bisync will also "renew" these lock files every
+<code>--max-lock minus one minute</code> throughout a run, for extra
+safety. (For example, with <code>--max-lock 5m</code>, bisync would
+renew the lock file (for another 5 minutes) every 4 minutes until the
+run has completed.) In other words, it should not be possible for a lock
+file to pass its expiration time while the process that created it is
+still running -- and you can therefore be reasonably sure that any
+<em>expired</em> lock file you may find was left there by an interrupted
+run, not one that is still running and just taking awhile.</p>
+<p>If <code>--max-lock</code> is <code>0</code> or not set, the default
+is that lock files will never expire, and will block future runs (of
+these same two bisync paths) indefinitely.</p>
+<p>For maximum resilience from disruptions, consider setting a
+relatively short duration like <code>--max-lock 2m</code> along with <a
+href="#resilient"><code>--resilient</code></a> and <a
+href="#recover"><code>--recover</code></a>, and a relatively frequent <a
+href="#cron">cron schedule</a>. The result will be a very robust
+"set-it-and-forget-it" bisync run that can automatically bounce back
+from almost any interruption it might encounter, without requiring the
+user to get involved and run a <code>--resync</code>. (See also: <a
+href="#graceful-shutdown">Graceful Shutdown</a> mode)</p>
+<h3 id="backup-dir1-and---backup-dir2">--backup-dir1 and
+--backup-dir2</h3>
+<p>As of <code>v1.66</code>, <a
+href="https://rclone.org/docs/#backup-dir-dir"><code>--backup-dir</code></a>
+is supported in bisync. Because <code>--backup-dir</code> must be a
+non-overlapping path on the same remote, Bisync has introduced new
+<code>--backup-dir1</code> and <code>--backup-dir2</code> flags to
+support separate backup-dirs for <code>Path1</code> and
+<code>Path2</code> (bisyncing between different remotes with
+<code>--backup-dir</code> would not otherwise be possible.)
+<code>--backup-dir1</code> and <code>--backup-dir2</code> can use
+different remotes from each other, but <code>--backup-dir1</code> must
+use the same remote as <code>Path1</code>, and
+<code>--backup-dir2</code> must use the same remote as
+<code>Path2</code>. Each backup directory must not overlap its
+respective bisync Path without being excluded by a filter rule.</p>
+<p>The standard <code>--backup-dir</code> will also work, if both paths
+use the same remote (but note that deleted files from both paths would
+be mixed together in the same dir). If either <code>--backup-dir1</code>
+and <code>--backup-dir2</code> are set, they will override
+<code>--backup-dir</code>.</p>
 <p>Example:</p>
 <pre><code>rclone bisync /Users/someuser/some/local/path/Bisync gdrive:Bisync --backup-dir1 /Users/someuser/some/local/path/BackupDir --backup-dir2 gdrive:BackupDir --suffix -2023-08-26 --suffix-keep-extension --check-access --max-delete 10 --filters-file /Users/someuser/some/local/path/bisync_filters.txt --no-cleanup --ignore-listing-checksum --checkers=16 --drive-pacer-min-sleep=10ms --create-empty-src-dirs --resilient -MvP --drive-skip-gdocs --fix-case</code></pre>
-<p>In this example, if the user deletes a file in <code>/Users/someuser/some/local/path/Bisync</code>, bisync will propagate the delete to the other side by moving the corresponding file from <code>gdrive:Bisync</code> to <code>gdrive:BackupDir</code>. If the user deletes a file from <code>gdrive:Bisync</code>, bisync moves it from <code>/Users/someuser/some/local/path/Bisync</code> to <code>/Users/someuser/some/local/path/BackupDir</code>.</p>
-<p>In the event of a <a href="#conflict-loser">rename due to a sync conflict</a>, the rename is not considered a delete, unless a previous conflict with the same name already exists and would get overwritten.</p>
-<p>See also: <a href="https://rclone.org/docs/#suffix-suffix"><code>--suffix</code></a>, <a href="https://rclone.org/docs/#suffix-keep-extension"><code>--suffix-keep-extension</code></a></p>
+<p>In this example, if the user deletes a file in
+<code>/Users/someuser/some/local/path/Bisync</code>, bisync will
+propagate the delete to the other side by moving the corresponding file
+from <code>gdrive:Bisync</code> to <code>gdrive:BackupDir</code>. If the
+user deletes a file from <code>gdrive:Bisync</code>, bisync moves it
+from <code>/Users/someuser/some/local/path/Bisync</code> to
+<code>/Users/someuser/some/local/path/BackupDir</code>.</p>
+<p>In the event of a <a href="#conflict-loser">rename due to a sync
+conflict</a>, the rename is not considered a delete, unless a previous
+conflict with the same name already exists and would get
+overwritten.</p>
+<p>See also: <a
+href="https://rclone.org/docs/#suffix-suffix"><code>--suffix</code></a>,
+<a
+href="https://rclone.org/docs/#suffix-keep-extension"><code>--suffix-keep-extension</code></a></p>
 <h2 id="operation">Operation</h2>
 <h3 id="runtime-flow-details">Runtime flow details</h3>
-<p>bisync retains the listings of the <code>Path1</code> and <code>Path2</code> filesystems from the prior run. On each successive run it will:</p>
+<p>bisync retains the listings of the <code>Path1</code> and
+<code>Path2</code> filesystems from the prior run. On each successive
+run it will:</p>
 <ul>
-<li>list files on <code>path1</code> and <code>path2</code>, and check for changes on each side. Changes include <code>New</code>, <code>Newer</code>, <code>Older</code>, and <code>Deleted</code> files.</li>
-<li>Propagate changes on <code>path1</code> to <code>path2</code>, and vice-versa.</li>
+<li>list files on <code>path1</code> and <code>path2</code>, and check
+for changes on each side. Changes include <code>New</code>,
+<code>Newer</code>, <code>Older</code>, and <code>Deleted</code>
+files.</li>
+<li>Propagate changes on <code>path1</code> to <code>path2</code>, and
+vice-versa.</li>
 </ul>
 <h3 id="safety-measures">Safety measures</h3>
 <ul>
-<li>Lock file prevents multiple simultaneous runs when taking a while. This can be particularly useful if bisync is run by cron scheduler.</li>
-<li>Handle change conflicts non-destructively by creating <code>.conflict1</code>, <code>.conflict2</code>, etc. file versions, according to <a href="#conflict-resolve"><code>--conflict-resolve</code></a>, <a href="#conflict-loser"><code>--conflict-loser</code></a>, and <a href="#conflict-suffix"><code>--conflict-suffix</code></a> settings.</li>
-<li>File system access health check using <code>RCLONE_TEST</code> files (see the <code>--check-access</code> flag).</li>
-<li>Abort on excessive deletes - protects against a failed listing being interpreted as all the files were deleted. See the <code>--max-delete</code> and <code>--force</code> flags.</li>
-<li>If something evil happens, bisync goes into a safe state to block damage by later runs. (See <a href="#error-handling">Error Handling</a>)</li>
+<li>Lock file prevents multiple simultaneous runs when taking a while.
+This can be particularly useful if bisync is run by cron scheduler.</li>
+<li>Handle change conflicts non-destructively by creating
+<code>.conflict1</code>, <code>.conflict2</code>, etc. file versions,
+according to <a
+href="#conflict-resolve"><code>--conflict-resolve</code></a>, <a
+href="#conflict-loser"><code>--conflict-loser</code></a>, and <a
+href="#conflict-suffix"><code>--conflict-suffix</code></a>
+settings.</li>
+<li>File system access health check using <code>RCLONE_TEST</code> files
+(see the <code>--check-access</code> flag).</li>
+<li>Abort on excessive deletes - protects against a failed listing being
+interpreted as all the files were deleted. See the
+<code>--max-delete</code> and <code>--force</code> flags.</li>
+<li>If something evil happens, bisync goes into a safe state to block
+damage by later runs. (See <a href="#error-handling">Error
+Handling</a>)</li>
 </ul>
 <h3 id="normal-sync-checks">Normal sync checks</h3>
 <table>
@@ -13405,21 +21665,32 @@ rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
 <tbody>
 <tr class="odd">
 <td>Path1 new/changed AND Path2 new/changed AND Path1 == Path2</td>
-<td>File is new/changed on Path1 AND new/changed on Path2 AND Path1 version is currently identical to Path2</td>
+<td>File is new/changed on Path1 AND new/changed on Path2 AND Path1
+version is currently identical to Path2</td>
 <td>No change</td>
 <td>None</td>
 </tr>
 <tr class="even">
 <td>Path1 new AND Path2 new</td>
-<td>File is new on Path1 AND new on Path2 (and Path1 version is NOT identical to Path2)</td>
-<td>Conflicts handled according to <a href="#conflict-resolve"><code>--conflict-resolve</code></a> &amp; <a href="#conflict-loser"><code>--conflict-loser</code></a> settings</td>
-<td>default: <code>rclone copy</code> renamed <code>Path2.conflict2</code> file to Path1, <code>rclone copy</code> renamed <code>Path1.conflict1</code> file to Path2</td>
+<td>File is new on Path1 AND new on Path2 (and Path1 version is NOT
+identical to Path2)</td>
+<td>Conflicts handled according to <a
+href="#conflict-resolve"><code>--conflict-resolve</code></a> &amp; <a
+href="#conflict-loser"><code>--conflict-loser</code></a> settings</td>
+<td>default: <code>rclone copy</code> renamed
+<code>Path2.conflict2</code> file to Path1, <code>rclone copy</code>
+renamed <code>Path1.conflict1</code> file to Path2</td>
 </tr>
 <tr class="odd">
 <td>Path2 newer AND Path1 changed</td>
-<td>File is newer on Path2 AND also changed (newer/older/size) on Path1 (and Path1 version is NOT identical to Path2)</td>
-<td>Conflicts handled according to <a href="#conflict-resolve"><code>--conflict-resolve</code></a> &amp; <a href="#conflict-loser"><code>--conflict-loser</code></a> settings</td>
-<td>default: <code>rclone copy</code> renamed <code>Path2.conflict2</code> file to Path1, <code>rclone copy</code> renamed <code>Path1.conflict1</code> file to Path2</td>
+<td>File is newer on Path2 AND also changed (newer/older/size) on Path1
+(and Path1 version is NOT identical to Path2)</td>
+<td>Conflicts handled according to <a
+href="#conflict-resolve"><code>--conflict-resolve</code></a> &amp; <a
+href="#conflict-loser"><code>--conflict-loser</code></a> settings</td>
+<td>default: <code>rclone copy</code> renamed
+<code>Path2.conflict2</code> file to Path1, <code>rclone copy</code>
+renamed <code>Path1.conflict1</code> file to Path2</td>
 </tr>
 <tr class="even">
 <td>Path2 newer AND Path1 deleted</td>
@@ -13429,120 +21700,365 @@ rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
 </tr>
 <tr class="odd">
 <td>Path2 deleted AND Path1 changed</td>
-<td>File is deleted on Path2 AND changed (newer/older/size) on Path1</td>
+<td>File is deleted on Path2 AND changed (newer/older/size) on
+Path1</td>
 <td>Path1 version survives</td>
 <td><code>rclone copy</code> Path1 to Path2</td>
 </tr>
 <tr class="even">
 <td>Path1 deleted AND Path2 changed</td>
-<td>File is deleted on Path1 AND changed (newer/older/size) on Path2</td>
+<td>File is deleted on Path1 AND changed (newer/older/size) on
+Path2</td>
 <td>Path2 version survives</td>
 <td><code>rclone copy</code> Path2 to Path1</td>
 </tr>
 </tbody>
 </table>
-<p>As of <code>rclone v1.64</code>, bisync is now better at detecting <em>false positive</em> sync conflicts, which would previously have resulted in unnecessary renames and duplicates. Now, when bisync comes to a file that it wants to rename (because it is new/changed on both sides), it first checks whether the Path1 and Path2 versions are currently <em>identical</em> (using the same underlying function as <a href="commands/rclone_check/"><code>check</code></a>.) If bisync concludes that the files are identical, it will skip them and move on. Otherwise, it will create renamed duplicates, as before. This behavior also <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=Renamed%20directories">improves the experience of renaming directories</a>, as a <code>--resync</code> is no longer required, so long as the same change has been made on both sides.</p>
+<p>As of <code>rclone v1.64</code>, bisync is now better at detecting
+<em>false positive</em> sync conflicts, which would previously have
+resulted in unnecessary renames and duplicates. Now, when bisync comes
+to a file that it wants to rename (because it is new/changed on both
+sides), it first checks whether the Path1 and Path2 versions are
+currently <em>identical</em> (using the same underlying function as <a
+href="commands/rclone_check/"><code>check</code></a>.) If bisync
+concludes that the files are identical, it will skip them and move on.
+Otherwise, it will create renamed duplicates, as before. This behavior
+also <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=Renamed%20directories">improves
+the experience of renaming directories</a>, as a <code>--resync</code>
+is no longer required, so long as the same change has been made on both
+sides.</p>
 <h3 id="all-files-changed">All files changed check</h3>
-<p>If <em>all</em> prior existing files on either of the filesystems have changed (e.g. timestamps have changed due to changing the system's timezone) then bisync will abort without making any changes. Any new files are not considered for this check. You could use <code>--force</code> to force the sync (whichever side has the changed timestamp files wins). Alternately, a <code>--resync</code> may be used (Path1 versions will be pushed to Path2). Consider the situation carefully and perhaps use <code>--dry-run</code> before you commit to the changes.</p>
+<p>If <em>all</em> prior existing files on either of the filesystems
+have changed (e.g. timestamps have changed due to changing the system's
+timezone) then bisync will abort without making any changes. Any new
+files are not considered for this check. You could use
+<code>--force</code> to force the sync (whichever side has the changed
+timestamp files wins). Alternately, a <code>--resync</code> may be used
+(Path1 versions will be pushed to Path2). Consider the situation
+carefully and perhaps use <code>--dry-run</code> before you commit to
+the changes.</p>
 <h3 id="modification-times">Modification times</h3>
-<p>By default, bisync compares files by modification time and size. If you or your application should change the content of a file without changing the modification time and size, then bisync will <em>not</em> notice the change, and thus will not copy it to the other side. As an alternative, consider comparing by checksum (if your remotes support it). See <a href="#compare"><code>--compare</code></a> for details.</p>
+<p>By default, bisync compares files by modification time and size. If
+you or your application should change the content of a file without
+changing the modification time and size, then bisync will <em>not</em>
+notice the change, and thus will not copy it to the other side. As an
+alternative, consider comparing by checksum (if your remotes support
+it). See <a href="#compare"><code>--compare</code></a> for details.</p>
 <h3 id="error-handling">Error handling</h3>
-<p>Certain bisync critical errors, such as file copy/move failing, will result in a bisync lockout of following runs. The lockout is asserted because the sync status and history of the Path1 and Path2 filesystems cannot be trusted, so it is safer to block any further changes until someone checks things out. The recovery is to do a <code>--resync</code> again.</p>
-<p>It is recommended to use <code>--resync --dry-run --verbose</code> initially and <em>carefully</em> review what changes will be made before running the <code>--resync</code> without <code>--dry-run</code>.</p>
-<p>Most of these events come up due to an error status from an internal call. On such a critical error the <code>{...}.path1.lst</code> and <code>{...}.path2.lst</code> listing files are renamed to extension <code>.lst-err</code>, which blocks any future bisync runs (since the normal <code>.lst</code> files are not found). Bisync keeps them under <code>bisync</code> subdirectory of the rclone cache directory, typically at <code>${HOME}/.cache/rclone/bisync/</code> on Linux.</p>
-<p>Some errors are considered temporary and re-running the bisync is not blocked. The <em>critical return</em> blocks further bisync runs.</p>
-<p>See also: <a href="#resilient"><code>--resilient</code></a>, <a href="#recover"><code>--recover</code></a>, <a href="#max-lock"><code>--max-lock</code></a>, <a href="#graceful-shutdown">Graceful Shutdown</a></p>
+<p>Certain bisync critical errors, such as file copy/move failing, will
+result in a bisync lockout of following runs. The lockout is asserted
+because the sync status and history of the Path1 and Path2 filesystems
+cannot be trusted, so it is safer to block any further changes until
+someone checks things out. The recovery is to do a <code>--resync</code>
+again.</p>
+<p>It is recommended to use <code>--resync --dry-run --verbose</code>
+initially and <em>carefully</em> review what changes will be made before
+running the <code>--resync</code> without <code>--dry-run</code>.</p>
+<p>Most of these events come up due to an error status from an internal
+call. On such a critical error the <code>{...}.path1.lst</code> and
+<code>{...}.path2.lst</code> listing files are renamed to extension
+<code>.lst-err</code>, which blocks any future bisync runs (since the
+normal <code>.lst</code> files are not found). Bisync keeps them under
+<code>bisync</code> subdirectory of the rclone cache directory,
+typically at <code>${HOME}/.cache/rclone/bisync/</code> on Linux.</p>
+<p>Some errors are considered temporary and re-running the bisync is not
+blocked. The <em>critical return</em> blocks further bisync runs.</p>
+<p>See also: <a href="#resilient"><code>--resilient</code></a>, <a
+href="#recover"><code>--recover</code></a>, <a
+href="#max-lock"><code>--max-lock</code></a>, <a
+href="#graceful-shutdown">Graceful Shutdown</a></p>
 <h3 id="lock-file">Lock file</h3>
-<p>When bisync is running, a lock file is created in the bisync working directory, typically at <code>~/.cache/rclone/bisync/PATH1..PATH2.lck</code> on Linux. If bisync should crash or hang, the lock file will remain in place and block any further runs of bisync <em>for the same paths</em>. Delete the lock file as part of debugging the situation. The lock file effectively blocks follow-on (e.g., scheduled by <em>cron</em>) runs when the prior invocation is taking a long time. The lock file contains <em>PID</em> of the blocking process, which may help in debug. Lock files can be set to automatically expire after a certain amount of time, using the <a href="#max-lock"><code>--max-lock</code></a> flag.</p>
-<p><strong>Note</strong> that while concurrent bisync runs are allowed, <em>be very cautious</em> that there is no overlap in the trees being synched between concurrent runs, lest there be replicated files, deleted files and general mayhem.</p>
+<p>When bisync is running, a lock file is created in the bisync working
+directory, typically at
+<code>~/.cache/rclone/bisync/PATH1..PATH2.lck</code> on Linux. If bisync
+should crash or hang, the lock file will remain in place and block any
+further runs of bisync <em>for the same paths</em>. Delete the lock file
+as part of debugging the situation. The lock file effectively blocks
+follow-on (e.g., scheduled by <em>cron</em>) runs when the prior
+invocation is taking a long time. The lock file contains <em>PID</em> of
+the blocking process, which may help in debug. Lock files can be set to
+automatically expire after a certain amount of time, using the <a
+href="#max-lock"><code>--max-lock</code></a> flag.</p>
+<p><strong>Note</strong> that while concurrent bisync runs are allowed,
+<em>be very cautious</em> that there is no overlap in the trees being
+synched between concurrent runs, lest there be replicated files, deleted
+files and general mayhem.</p>
 <h3 id="return-codes">Return codes</h3>
-<p><code>rclone bisync</code> returns the following codes to calling program: - <code>0</code> on a successful run, - <code>1</code> for a non-critical failing run (a rerun may be successful), - <code>2</code> for a critically aborted run (requires a <code>--resync</code> to recover).</p>
+<p><code>rclone bisync</code> returns the following codes to calling
+program: - <code>0</code> on a successful run, - <code>1</code> for a
+non-critical failing run (a rerun may be successful), - <code>2</code>
+for a critically aborted run (requires a <code>--resync</code> to
+recover).</p>
 <h3 id="graceful-shutdown">Graceful Shutdown</h3>
-<p>Bisync has a "Graceful Shutdown" mode which is activated by sending <code>SIGINT</code> or pressing <code>Ctrl+C</code> during a run. Once triggered, bisync will use best efforts to exit cleanly before the timer runs out. If bisync is in the middle of transferring files, it will attempt to cleanly empty its queue by finishing what it has started but not taking more. If it cannot do so within 30 seconds, it will cancel the in-progress transfers at that point and then give itself a maximum of 60 seconds to wrap up, save its state for next time, and exit. With the <code>-vP</code> flags you will see constant status updates and a final confirmation of whether or not the graceful shutdown was successful.</p>
-<p>At any point during the "Graceful Shutdown" sequence, a second <code>SIGINT</code> or <code>Ctrl+C</code> will trigger an immediate, un-graceful exit, which will leave things in a messier state. Usually a robust recovery will still be possible if using <a href="#recover"><code>--recover</code></a> mode, otherwise you will need to do a <code>--resync</code>.</p>
-<p>If you plan to use Graceful Shutdown mode, it is recommended to use <a href="#resilient"><code>--resilient</code></a> and <a href="#recover"><code>--recover</code></a>, and it is important to NOT use <a href="https://rclone.org/docs/#inplace"><code>--inplace</code></a>, otherwise you risk leaving partially-written files on one side, which may be confused for real files on the next run. Note also that in the event of an abrupt interruption, a <a href="#lock-file">lock file</a> will be left behind to block concurrent runs. You will need to delete it before you can proceed with the next run (or wait for it to expire on its own, if using <code>--max-lock</code>.)</p>
+<p>Bisync has a "Graceful Shutdown" mode which is activated by sending
+<code>SIGINT</code> or pressing <code>Ctrl+C</code> during a run. Once
+triggered, bisync will use best efforts to exit cleanly before the timer
+runs out. If bisync is in the middle of transferring files, it will
+attempt to cleanly empty its queue by finishing what it has started but
+not taking more. If it cannot do so within 30 seconds, it will cancel
+the in-progress transfers at that point and then give itself a maximum
+of 60 seconds to wrap up, save its state for next time, and exit. With
+the <code>-vP</code> flags you will see constant status updates and a
+final confirmation of whether or not the graceful shutdown was
+successful.</p>
+<p>At any point during the "Graceful Shutdown" sequence, a second
+<code>SIGINT</code> or <code>Ctrl+C</code> will trigger an immediate,
+un-graceful exit, which will leave things in a messier state. Usually a
+robust recovery will still be possible if using <a
+href="#recover"><code>--recover</code></a> mode, otherwise you will need
+to do a <code>--resync</code>.</p>
+<p>If you plan to use Graceful Shutdown mode, it is recommended to use
+<a href="#resilient"><code>--resilient</code></a> and <a
+href="#recover"><code>--recover</code></a>, and it is important to NOT
+use <a
+href="https://rclone.org/docs/#inplace"><code>--inplace</code></a>,
+otherwise you risk leaving partially-written files on one side, which
+may be confused for real files on the next run. Note also that in the
+event of an abrupt interruption, a <a href="#lock-file">lock file</a>
+will be left behind to block concurrent runs. You will need to delete it
+before you can proceed with the next run (or wait for it to expire on
+its own, if using <code>--max-lock</code>.)</p>
 <h2 id="limitations-4">Limitations</h2>
 <h3 id="supported-backends">Supported backends</h3>
-<p>Bisync is considered <em>BETA</em> and has been tested with the following backends: - Local filesystem - Google Drive - Dropbox - OneDrive - S3 - SFTP - Yandex Disk - Crypt</p>
-<p>It has not been fully tested with other services yet. If it works, or sorta works, please let us know and we'll update the list. Run the test suite to check for proper operation as described below.</p>
-<p>The first release of <code>rclone bisync</code> required both underlying backends to support modification times, and refused to run otherwise. This limitation has been lifted as of <code>v1.66</code>, as bisync now supports comparing checksum and/or size instead of (or in addition to) modtime. See <a href="#compare"><code>--compare</code></a> for details.</p>
+<p>Bisync is considered <em>BETA</em> and has been tested with the
+following backends: - Local filesystem - Google Drive - Dropbox -
+OneDrive - S3 - SFTP - Yandex Disk - Crypt</p>
+<p>It has not been fully tested with other services yet. If it works, or
+sorta works, please let us know and we'll update the list. Run the test
+suite to check for proper operation as described below.</p>
+<p>The first release of <code>rclone bisync</code> required both
+underlying backends to support modification times, and refused to run
+otherwise. This limitation has been lifted as of <code>v1.66</code>, as
+bisync now supports comparing checksum and/or size instead of (or in
+addition to) modtime. See <a href="#compare"><code>--compare</code></a>
+for details.</p>
 <h3 id="concurrent-modifications">Concurrent modifications</h3>
-<p>When using <strong>Local, FTP or SFTP</strong> remotes with <a href="https://rclone.org/docs/#inplace"><code>--inplace</code></a>, rclone does not create <em>temporary</em> files at the destination when copying, and thus if the connection is lost the created file may be corrupt, which will likely propagate back to the original path on the next sync, resulting in data loss. It is therefore recommended to <em>omit</em> <code>--inplace</code>.</p>
-<p>Files that <strong>change during</strong> a bisync run may result in data loss. Prior to <code>rclone v1.66</code>, this was commonly seen in highly dynamic environments, where the filesystem was getting hammered by running processes during the sync. As of <code>rclone v1.66</code>, bisync was redesigned to use a "snapshot" model, greatly reducing the risks from changes during a sync. Changes that are not detected during the current sync will now be detected during the following sync, and will no longer cause the entire run to throw a critical error. There is additionally a mechanism to mark files as needing to be internally rechecked next time, for added safety. It should therefore no longer be necessary to sync only at quiet times -- however, note that an error can still occur if a file happens to change at the exact moment it's being read/written by bisync (same as would happen in <code>rclone sync</code>.) (See also: <a href="https://rclone.org/docs/#ignore-checksum"><code>--ignore-checksum</code></a>, <a href="https://rclone.org/local/#local-no-check-updated"><code>--local-no-check-updated</code></a>)</p>
+<p>When using <strong>Local, FTP or SFTP</strong> remotes with <a
+href="https://rclone.org/docs/#inplace"><code>--inplace</code></a>,
+rclone does not create <em>temporary</em> files at the destination when
+copying, and thus if the connection is lost the created file may be
+corrupt, which will likely propagate back to the original path on the
+next sync, resulting in data loss. It is therefore recommended to
+<em>omit</em> <code>--inplace</code>.</p>
+<p>Files that <strong>change during</strong> a bisync run may result in
+data loss. Prior to <code>rclone v1.66</code>, this was commonly seen in
+highly dynamic environments, where the filesystem was getting hammered
+by running processes during the sync. As of <code>rclone v1.66</code>,
+bisync was redesigned to use a "snapshot" model, greatly reducing the
+risks from changes during a sync. Changes that are not detected during
+the current sync will now be detected during the following sync, and
+will no longer cause the entire run to throw a critical error. There is
+additionally a mechanism to mark files as needing to be internally
+rechecked next time, for added safety. It should therefore no longer be
+necessary to sync only at quiet times -- however, note that an error can
+still occur if a file happens to change at the exact moment it's being
+read/written by bisync (same as would happen in
+<code>rclone sync</code>.) (See also: <a
+href="https://rclone.org/docs/#ignore-checksum"><code>--ignore-checksum</code></a>,
+<a
+href="https://rclone.org/local/#local-no-check-updated"><code>--local-no-check-updated</code></a>)</p>
 <h3 id="empty-directories">Empty directories</h3>
-<p>By default, new/deleted empty directories on one path are <em>not</em> propagated to the other side. This is because bisync (and rclone) natively works on files, not directories. However, this can be changed with the <code>--create-empty-src-dirs</code> flag, which works in much the same way as in <a href="https://rclone.org/commands/rclone_sync/"><code>sync</code></a> and <a href="https://rclone.org/commands/rclone_copy/"><code>copy</code></a>. When used, empty directories created or deleted on one side will also be created or deleted on the other side. The following should be noted: * <code>--create-empty-src-dirs</code> is not compatible with <code>--remove-empty-dirs</code>. Use only one or the other (or neither). * It is not recommended to switch back and forth between <code>--create-empty-src-dirs</code> and the default (no <code>--create-empty-src-dirs</code>) without running <code>--resync</code>. This is because it may appear as though all directories (not just the empty ones) were created/deleted, when actually you've just toggled between making them visible/invisible to bisync. It looks scarier than it is, but it's still probably best to stick to one or the other, and use <code>--resync</code> when you need to switch.</p>
+<p>By default, new/deleted empty directories on one path are
+<em>not</em> propagated to the other side. This is because bisync (and
+rclone) natively works on files, not directories. However, this can be
+changed with the <code>--create-empty-src-dirs</code> flag, which works
+in much the same way as in <a
+href="https://rclone.org/commands/rclone_sync/"><code>sync</code></a>
+and <a
+href="https://rclone.org/commands/rclone_copy/"><code>copy</code></a>.
+When used, empty directories created or deleted on one side will also be
+created or deleted on the other side. The following should be noted: *
+<code>--create-empty-src-dirs</code> is not compatible with
+<code>--remove-empty-dirs</code>. Use only one or the other (or
+neither). * It is not recommended to switch back and forth between
+<code>--create-empty-src-dirs</code> and the default (no
+<code>--create-empty-src-dirs</code>) without running
+<code>--resync</code>. This is because it may appear as though all
+directories (not just the empty ones) were created/deleted, when
+actually you've just toggled between making them visible/invisible to
+bisync. It looks scarier than it is, but it's still probably best to
+stick to one or the other, and use <code>--resync</code> when you need
+to switch.</p>
 <h3 id="renamed-directories">Renamed directories</h3>
-<p>By default, renaming a folder on the Path1 side results in deleting all files on the Path2 side and then copying all files again from Path1 to Path2. Bisync sees this as all files in the old directory name as deleted and all files in the new directory name as new.</p>
-<p>A recommended solution is to use <a href="https://rclone.org/docs/#track-renames"><code>--track-renames</code></a>, which is now supported in bisync as of <code>rclone v1.66</code>. Note that <code>--track-renames</code> is not available during <code>--resync</code>, as <code>--resync</code> does not delete anything (<code>--track-renames</code> only supports <code>sync</code>, not <code>copy</code>.)</p>
-<p>Otherwise, the most effective and efficient method of renaming a directory is to rename it to the same name on both sides. (As of <code>rclone v1.64</code>, a <code>--resync</code> is no longer required after doing so, as bisync will automatically detect that Path1 and Path2 are in agreement.)</p>
-<h3 id="fast-list-used-by-default"><code>--fast-list</code> used by default</h3>
-<p>Unlike most other rclone commands, bisync uses <a href="https://rclone.org/docs/#fast-list"><code>--fast-list</code></a> by default, for backends that support it. In many cases this is desirable, however, there are some scenarios in which bisync could be faster <em>without</em> <code>--fast-list</code>, and there is also a <a href="https://github.com/rclone/rclone/commit/cbf3d4356135814921382dd3285d859d15d0aa77">known issue concerning Google Drive users with many empty directories</a>. For now, the recommended way to avoid using <code>--fast-list</code> is to add <code>--disable ListR</code> to all bisync commands. The default behavior may change in a future version.</p>
+<p>By default, renaming a folder on the Path1 side results in deleting
+all files on the Path2 side and then copying all files again from Path1
+to Path2. Bisync sees this as all files in the old directory name as
+deleted and all files in the new directory name as new.</p>
+<p>A recommended solution is to use <a
+href="https://rclone.org/docs/#track-renames"><code>--track-renames</code></a>,
+which is now supported in bisync as of <code>rclone v1.66</code>. Note
+that <code>--track-renames</code> is not available during
+<code>--resync</code>, as <code>--resync</code> does not delete anything
+(<code>--track-renames</code> only supports <code>sync</code>, not
+<code>copy</code>.)</p>
+<p>Otherwise, the most effective and efficient method of renaming a
+directory is to rename it to the same name on both sides. (As of
+<code>rclone v1.64</code>, a <code>--resync</code> is no longer required
+after doing so, as bisync will automatically detect that Path1 and Path2
+are in agreement.)</p>
+<h3 id="fast-list-used-by-default"><code>--fast-list</code> used by
+default</h3>
+<p>Unlike most other rclone commands, bisync uses <a
+href="https://rclone.org/docs/#fast-list"><code>--fast-list</code></a>
+by default, for backends that support it. In many cases this is
+desirable, however, there are some scenarios in which bisync could be
+faster <em>without</em> <code>--fast-list</code>, and there is also a <a
+href="https://github.com/rclone/rclone/commit/cbf3d4356135814921382dd3285d859d15d0aa77">known
+issue concerning Google Drive users with many empty directories</a>. For
+now, the recommended way to avoid using <code>--fast-list</code> is to
+add <code>--disable ListR</code> to all bisync commands. The default
+behavior may change in a future version.</p>
 <h3 id="case-sensitivity">Case (and unicode) sensitivity</h3>
-<p>As of <code>v1.66</code>, case and unicode form differences no longer cause critical errors, and normalization (when comparing between filesystems) is handled according to the same flags and defaults as <code>rclone sync</code>. See the following options (all of which are supported by bisync) to control this behavior more granularly: - <a href="https://rclone.org/docs/#fix-case"><code>--fix-case</code></a> - <a href="https://rclone.org/docs/#ignore-case-sync"><code>--ignore-case-sync</code></a> - <a href="https://rclone.org/docs/#no-unicode-normalization"><code>--no-unicode-normalization</code></a> - <a href="https://rclone.org/local/#local-unicode-normalization"><code>--local-unicode-normalization</code></a> and <a href="https://rclone.org/local/#local-case-sensitive"><code>--local-case-sensitive</code></a> (caution: these are normally not what you want.)</p>
-<p>Note that in the (probably rare) event that <code>--fix-case</code> is used AND a file is new/changed on both sides AND the checksums match AND the filename case does not match, the Path1 filename is considered the winner, for the purposes of <code>--fix-case</code> (Path2 will be renamed to match it).</p>
+<p>As of <code>v1.66</code>, case and unicode form differences no longer
+cause critical errors, and normalization (when comparing between
+filesystems) is handled according to the same flags and defaults as
+<code>rclone sync</code>. See the following options (all of which are
+supported by bisync) to control this behavior more granularly: - <a
+href="https://rclone.org/docs/#fix-case"><code>--fix-case</code></a> -
+<a
+href="https://rclone.org/docs/#ignore-case-sync"><code>--ignore-case-sync</code></a>
+- <a
+href="https://rclone.org/docs/#no-unicode-normalization"><code>--no-unicode-normalization</code></a>
+- <a
+href="https://rclone.org/local/#local-unicode-normalization"><code>--local-unicode-normalization</code></a>
+and <a
+href="https://rclone.org/local/#local-case-sensitive"><code>--local-case-sensitive</code></a>
+(caution: these are normally not what you want.)</p>
+<p>Note that in the (probably rare) event that <code>--fix-case</code>
+is used AND a file is new/changed on both sides AND the checksums match
+AND the filename case does not match, the Path1 filename is considered
+the winner, for the purposes of <code>--fix-case</code> (Path2 will be
+renamed to match it).</p>
 <h2 id="windows">Windows support</h2>
-<p>Bisync has been tested on Windows 8.1, Windows 10 Pro 64-bit and on Windows GitHub runners.</p>
-<p>Drive letters are allowed, including drive letters mapped to network drives (<code>rclone bisync J:\localsync GDrive:</code>). If a drive letter is omitted, the shell current drive is the default. Drive letters are a single character follows by <code>:</code>, so cloud names must be more than one character long.</p>
-<p>Absolute paths (with or without a drive letter), and relative paths (with or without a drive letter) are supported.</p>
-<p>Working directory is created at <code>C:\Users\MyLogin\AppData\Local\rclone\bisync</code>.</p>
-<p>Note that bisync output may show a mix of forward <code>/</code> and back <code>\</code> slashes.</p>
-<p>Be careful of case independent directory and file naming on Windows vs. case dependent Linux</p>
+<p>Bisync has been tested on Windows 8.1, Windows 10 Pro 64-bit and on
+Windows GitHub runners.</p>
+<p>Drive letters are allowed, including drive letters mapped to network
+drives (<code>rclone bisync J:\localsync GDrive:</code>). If a drive
+letter is omitted, the shell current drive is the default. Drive letters
+are a single character follows by <code>:</code>, so cloud names must be
+more than one character long.</p>
+<p>Absolute paths (with or without a drive letter), and relative paths
+(with or without a drive letter) are supported.</p>
+<p>Working directory is created at
+<code>C:\Users\MyLogin\AppData\Local\rclone\bisync</code>.</p>
+<p>Note that bisync output may show a mix of forward <code>/</code> and
+back <code>\</code> slashes.</p>
+<p>Be careful of case independent directory and file naming on Windows
+vs. case dependent Linux</p>
 <h2 id="filtering">Filtering</h2>
-<p>See <a href="https://rclone.org/filtering/">filtering documentation</a> for how filter rules are written and interpreted.</p>
-<p>Bisync's <a href="#filters-file"><code>--filters-file</code></a> flag slightly extends the rclone's <a href="https://rclone.org/filtering/#filter-from-read-filtering-patterns-from-a-file">--filter-from</a> filtering mechanism. For a given bisync run you may provide <em>only one</em> <code>--filters-file</code>. The <code>--include*</code>, <code>--exclude*</code>, and <code>--filter</code> flags are also supported.</p>
+<p>See <a href="https://rclone.org/filtering/">filtering
+documentation</a> for how filter rules are written and interpreted.</p>
+<p>Bisync's <a href="#filters-file"><code>--filters-file</code></a> flag
+slightly extends the rclone's <a
+href="https://rclone.org/filtering/#filter-from-read-filtering-patterns-from-a-file">--filter-from</a>
+filtering mechanism. For a given bisync run you may provide <em>only
+one</em> <code>--filters-file</code>. The <code>--include*</code>,
+<code>--exclude*</code>, and <code>--filter</code> flags are also
+supported.</p>
 <h3 id="how-to-filter-directories">How to filter directories</h3>
-<p>Filtering portions of the directory tree is a critical feature for synching.</p>
-<p>Examples of directory trees (always beneath the Path1/Path2 root level) you may want to exclude from your sync: - Directory trees containing only software build intermediate files. - Directory trees containing application temporary files and data such as the Windows <code>C:\Users\MyLogin\AppData\</code> tree. - Directory trees containing files that are large, less important, or are getting thrashed continuously by ongoing processes.</p>
-<p>On the other hand, there may be only select directories that you actually want to sync, and exclude all others. See the <a href="#include-filters">Example include-style filters for Windows user directories</a> below.</p>
-<h3 id="filters-file-writing-guidelines">Filters file writing guidelines</h3>
+<p>Filtering portions of the directory tree is a critical feature for
+synching.</p>
+<p>Examples of directory trees (always beneath the Path1/Path2 root
+level) you may want to exclude from your sync: - Directory trees
+containing only software build intermediate files. - Directory trees
+containing application temporary files and data such as the Windows
+<code>C:\Users\MyLogin\AppData\</code> tree. - Directory trees
+containing files that are large, less important, or are getting thrashed
+continuously by ongoing processes.</p>
+<p>On the other hand, there may be only select directories that you
+actually want to sync, and exclude all others. See the <a
+href="#include-filters">Example include-style filters for Windows user
+directories</a> below.</p>
+<h3 id="filters-file-writing-guidelines">Filters file writing
+guidelines</h3>
 <ol type="1">
 <li>Begin with excluding directory trees:
 <ul>
-<li>e.g. `- /AppData/`</li>
-<li><code>**</code> on the end is not necessary. Once a given directory level is excluded then everything beneath it won't be looked at by rclone.</li>
-<li>Exclude such directories that are unneeded, are big, dynamically thrashed, or where there may be access permission issues.</li>
-<li>Excluding such dirs first will make rclone operations (much) faster.</li>
-<li>Specific files may also be excluded, as with the Dropbox exclusions example below.</li>
+<li>e.g. <code>- /AppData/</code></li>
+<li><code>**</code> on the end is not necessary. Once a given directory
+level is excluded then everything beneath it won't be looked at by
+rclone.</li>
+<li>Exclude such directories that are unneeded, are big, dynamically
+thrashed, or where there may be access permission issues.</li>
+<li>Excluding such dirs first will make rclone operations (much)
+faster.</li>
+<li>Specific files may also be excluded, as with the Dropbox exclusions
+example below.</li>
 </ul></li>
 <li>Decide if it's easier (or cleaner) to:
 <ul>
-<li>Include select directories and therefore <em>exclude everything else</em> -- or --</li>
-<li>Exclude select directories and therefore <em>include everything else</em></li>
+<li>Include select directories and therefore <em>exclude everything
+else</em> -- or --</li>
+<li>Exclude select directories and therefore <em>include everything
+else</em></li>
 </ul></li>
 <li>Include select directories:
 <ul>
-<li>Add lines like: `+ /Documents/PersonalFiles/**` to select which directories to include in the sync.</li>
-<li><code>**</code> on the end specifies to include the full depth of the specified tree.</li>
-<li>With Include-style filters, files at the Path1/Path2 root are not included. They may be included with `+ /*`.</li>
-<li>Place RCLONE_TEST files within these included directory trees. They will only be looked for in these directory trees.</li>
-<li>Finish by excluding everything else by adding `- **` at the end of the filters file.</li>
+<li>Add lines like: <code>+ /Documents/PersonalFiles/**</code> to select
+which directories to include in the sync.</li>
+<li><code>**</code> on the end specifies to include the full depth of
+the specified tree.</li>
+<li>With Include-style filters, files at the Path1/Path2 root are not
+included. They may be included with <code>+ /*</code>.</li>
+<li>Place RCLONE_TEST files within these included directory trees. They
+will only be looked for in these directory trees.</li>
+<li>Finish by excluding everything else by adding <code>- **</code> at
+the end of the filters file.</li>
 <li>Disregard step 4.</li>
 </ul></li>
 <li>Exclude select directories:
 <ul>
-<li>Add more lines like in step 1. For example: <code>-/Desktop/tempfiles/</code>, or `- /testdir/<code>.    Again, a</code>**` on the end is not necessary.</li>
-<li>Do <em>not</em> add a `- **` in the file. Without this line, everything will be included that has not been explicitly excluded.</li>
+<li>Add more lines like in step 1. For example:
+<code>-/Desktop/tempfiles/</code>, or <code>- /testdir/</code>. Again, a
+<code>**</code> on the end is not necessary.</li>
+<li>Do <em>not</em> add a <code>- **</code> in the file. Without this
+line, everything will be included that has not been explicitly
+excluded.</li>
 <li>Disregard step 3.</li>
 </ul></li>
 </ol>
-<p>A few rules for the syntax of a filter file expanding on <a href="https://rclone.org/filtering/">filtering documentation</a>:</p>
+<p>A few rules for the syntax of a filter file expanding on <a
+href="https://rclone.org/filtering/">filtering documentation</a>:</p>
 <ul>
-<li>Lines may start with spaces and tabs - rclone strips leading whitespace.</li>
-<li>If the first non-whitespace character is a <code>#</code> then the line is a comment and will be ignored.</li>
+<li>Lines may start with spaces and tabs - rclone strips leading
+whitespace.</li>
+<li>If the first non-whitespace character is a <code>#</code> then the
+line is a comment and will be ignored.</li>
 <li>Blank lines are ignored.</li>
-<li>The first non-whitespace character on a filter line must be a <code>+</code> or <code>-</code>.</li>
-<li>Exactly 1 space is allowed between the <code>+/-</code> and the path term.</li>
-<li>Only forward slashes (<code>/</code>) are used in path terms, even on Windows.</li>
-<li>The rest of the line is taken as the path term. Trailing whitespace is taken literally, and probably is an error.</li>
+<li>The first non-whitespace character on a filter line must be a
+<code>+</code> or <code>-</code>.</li>
+<li>Exactly 1 space is allowed between the <code>+/-</code> and the path
+term.</li>
+<li>Only forward slashes (<code>/</code>) are used in path terms, even
+on Windows.</li>
+<li>The rest of the line is taken as the path term. Trailing whitespace
+is taken literally, and probably is an error.</li>
 </ul>
-<h3 id="include-filters">Example include-style filters for Windows user directories</h3>
-<p>This Windows <em>include-style</em> example is based on the sync root (Path1) set to <code>C:\Users\MyLogin</code>. The strategy is to select specific directories to be synched with a network drive (Path2).</p>
+<h3 id="include-filters">Example include-style filters for Windows user
+directories</h3>
+<p>This Windows <em>include-style</em> example is based on the sync root
+(Path1) set to <code>C:\Users\MyLogin</code>. The strategy is to select
+specific directories to be synched with a network drive (Path2).</p>
 <ul>
-<li>`- /AppData/` excludes an entire tree of Windows stored stuff that need not be synched. In my case, AppData has &gt;11 GB of stuff I don't care about, and there are some subdirectories beneath AppData that are not accessible to my user login, resulting in bisync critical aborts.</li>
-<li>Windows creates cache files starting with both upper and lowercase <code>NTUSER</code> at <code>C:\Users\MyLogin</code>. These files may be dynamic, locked, and are generally <em>don't care</em>.</li>
-<li>There are just a few directories with <em>my</em> data that I do want synched, in the form of `+ /<path><code>. By selecting only the directory trees I   want to avoid the dozen plus directories that various apps make   at</code>C:`.</li>
-<li>Include files in the root of the sync point, <code>C:\Users\MyLogin</code>, by adding the `+ /*` line.</li>
-<li>This is an Include-style filters file, therefore it ends with `- **` which excludes everything not explicitly included.</li>
+<li><code>- /AppData/</code> excludes an entire tree of Windows stored
+stuff that need not be synched. In my case, AppData has &gt;11 GB of
+stuff I don't care about, and there are some subdirectories beneath
+AppData that are not accessible to my user login, resulting in bisync
+critical aborts.</li>
+<li>Windows creates cache files starting with both upper and lowercase
+<code>NTUSER</code> at <code>C:\Users\MyLogin</code>. These files may be
+dynamic, locked, and are generally <em>don't care</em>.</li>
+<li>There are just a few directories with <em>my</em> data that I do
+want synched, in the form of <code>+ /&lt;path&gt;</code>. By selecting
+only the directory trees I want to avoid the dozen plus directories that
+various apps make at <code>C:\Users\MyLogin\Documents</code>.</li>
+<li>Include files in the root of the sync point,
+<code>C:\Users\MyLogin</code>, by adding the <code>+ /*</code>
+line.</li>
+<li>This is an Include-style filters file, therefore it ends with
+<code>- **</code> which excludes everything not explicitly
+included.</li>
 </ul>
 <pre><code>- /AppData/
 - NTUSER*
@@ -13555,13 +22071,33 @@ rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
 + /Pictures/**
 + /*
 - **</code></pre>
-<p>Note also that Windows implements several "library" links such as <code>C:\Users\MyLogin\My Documents\My Music</code> pointing to <code>C:\Users\MyLogin\Music</code>. rclone sees these as links, so you must add <code>--links</code> to the bisync command line if you which to follow these links. I find that I get permission errors in trying to follow the links, so I don't include the rclone <code>--links</code> flag, but then you get lots of <code>Can't follow symlink…</code> noise from rclone about not following the links. This noise can be quashed by adding <code>--quiet</code> to the bisync command line.</p>
-<h2 id="exclude-filters">Example exclude-style filters files for use with Dropbox</h2>
+<p>Note also that Windows implements several "library" links such as
+<code>C:\Users\MyLogin\My Documents\My Music</code> pointing to
+<code>C:\Users\MyLogin\Music</code>. rclone sees these as links, so you
+must add <code>--links</code> to the bisync command line if you which to
+follow these links. I find that I get permission errors in trying to
+follow the links, so I don't include the rclone <code>--links</code>
+flag, but then you get lots of <code>Can't follow symlink…</code> noise
+from rclone about not following the links. This noise can be quashed by
+adding <code>--quiet</code> to the bisync command line.</p>
+<h2 id="exclude-filters">Example exclude-style filters files for use
+with Dropbox</h2>
 <ul>
-<li>Dropbox disallows synching the listed temporary and configuration/data files. The `- <filename>` filters exclude these files where ever they may occur in the sync tree. Consider adding similar exclusions for file types you don't need to sync, such as core dump and software build files.</li>
-<li>bisync testing creates <code>/testdir/</code> at the top level of the sync tree, and usually deletes the tree after the test. If a normal sync should run while the <code>/testdir/</code> tree exists the <code>--check-access</code> phase may fail due to unbalanced RCLONE_TEST files. The `- /testdir/` filter blocks this tree from being synched. You don't need this exclusion if you are not doing bisync development testing.</li>
+<li>Dropbox disallows synching the listed temporary and
+configuration/data files. The <code>- &lt;filename&gt;</code> filters
+exclude these files where ever they may occur in the sync tree. Consider
+adding similar exclusions for file types you don't need to sync, such as
+core dump and software build files.</li>
+<li>bisync testing creates <code>/testdir/</code> at the top level of
+the sync tree, and usually deletes the tree after the test. If a normal
+sync should run while the <code>/testdir/</code> tree exists the
+<code>--check-access</code> phase may fail due to unbalanced RCLONE_TEST
+files. The <code>- /testdir/</code> filter blocks this tree from being
+synched. You don't need this exclusion if you are not doing bisync
+development testing.</li>
 <li>Everything else beneath the Path1/Path2 root will be synched.</li>
-<li>RCLONE_TEST files may be placed anywhere within the tree, including the root.</li>
+<li>RCLONE_TEST files may be placed anywhere within the tree, including
+the root.</li>
 </ul>
 <h3 id="example-filters-file">Example filters file for Dropbox</h3>
 <pre><code># Filter file for use with bisync
@@ -13584,11 +22120,18 @@ rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
 # Other example filters
 #- /TiBU/
 #- /Photos/</code></pre>
-<h3 id="how---check-access-handles-filters">How --check-access handles filters</h3>
-<p>At the start of a bisync run, listings are gathered for Path1 and Path2 while using the user's <code>--filters-file</code>. During the check access phase, bisync scans these listings for <code>RCLONE_TEST</code> files. Any <code>RCLONE_TEST</code> files hidden by the <code>--filters-file</code> are <em>not</em> in the listings and thus not checked during the check access phase.</p>
+<h3 id="how---check-access-handles-filters">How --check-access handles
+filters</h3>
+<p>At the start of a bisync run, listings are gathered for Path1 and
+Path2 while using the user's <code>--filters-file</code>. During the
+check access phase, bisync scans these listings for
+<code>RCLONE_TEST</code> files. Any <code>RCLONE_TEST</code> files
+hidden by the <code>--filters-file</code> are <em>not</em> in the
+listings and thus not checked during the check access phase.</p>
 <h2 id="troubleshooting">Troubleshooting</h2>
 <h3 id="reading-bisync-logs">Reading bisync logs</h3>
-<p>Here are two normal runs. The first one has a newer file on the remote. The second has no deltas between local and remote.</p>
+<p>Here are two normal runs. The first one has a newer file on the
+remote. The second has no deltas between local and remote.</p>
 <pre><code>2021/05/16 00:24:38 INFO  : Synching Path1 &quot;/path/to/local/tree/&quot; with Path2 &quot;dropbox:/&quot;
 2021/05/16 00:24:38 INFO  : Path1 checking for diffs
 2021/05/16 00:24:38 INFO  : - Path1    File is new                         - file.txt
@@ -13609,12 +22152,30 @@ rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
 2021/05/16 00:36:52 INFO  : Validating listings for Path1 &quot;/path/to/local/tree/&quot; vs Path2 &quot;dropbox:/&quot;
 2021/05/16 00:36:52 INFO  : Bisync successful</code></pre>
 <h3 id="dry-run-oddity">Dry run oddity</h3>
-<p>The <code>--dry-run</code> messages may indicate that it would try to delete some files. For example, if a file is new on Path2 and does not exist on Path1 then it would normally be copied to Path1, but with <code>--dry-run</code> enabled those copies don't happen, which leads to the attempted delete on Path2, blocked again by --dry-run: <code>... Not deleting as --dry-run</code>.</p>
-<p>This whole confusing situation is an artifact of the <code>--dry-run</code> flag. Scrutinize the proposed deletes carefully, and if the files would have been copied to Path1 then the threatened deletes on Path2 may be disregarded.</p>
+<p>The <code>--dry-run</code> messages may indicate that it would try to
+delete some files. For example, if a file is new on Path2 and does not
+exist on Path1 then it would normally be copied to Path1, but with
+<code>--dry-run</code> enabled those copies don't happen, which leads to
+the attempted delete on Path2, blocked again by --dry-run:
+<code>... Not deleting as --dry-run</code>.</p>
+<p>This whole confusing situation is an artifact of the
+<code>--dry-run</code> flag. Scrutinize the proposed deletes carefully,
+and if the files would have been copied to Path1 then the threatened
+deletes on Path2 may be disregarded.</p>
 <h3 id="retries">Retries</h3>
-<p>Rclone has built-in retries. If you run with <code>--verbose</code> you'll see error and retry messages such as shown below. This is usually not a bug. If at the end of the run, you see <code>Bisync successful</code> and not <code>Bisync critical error</code> or <code>Bisync aborted</code> then the run was successful, and you can ignore the error messages.</p>
-<p>The following run shows an intermittent fail. Lines <em>5</em> and _6- are low-level messages. Line <em>6</em> is a bubbled-up <em>warning</em> message, conveying the error. Rclone normally retries failing commands, so there may be numerous such messages in the log.</p>
-<p>Since there are no final error/warning messages on line <em>7</em>, rclone has recovered from failure after a retry, and the overall sync was successful.</p>
+<p>Rclone has built-in retries. If you run with <code>--verbose</code>
+you'll see error and retry messages such as shown below. This is usually
+not a bug. If at the end of the run, you see
+<code>Bisync successful</code> and not
+<code>Bisync critical error</code> or <code>Bisync aborted</code> then
+the run was successful, and you can ignore the error messages.</p>
+<p>The following run shows an intermittent fail. Lines <em>5</em> and
+_6- are low-level messages. Line <em>6</em> is a bubbled-up
+<em>warning</em> message, conveying the error. Rclone normally retries
+failing commands, so there may be numerous such messages in the log.</p>
+<p>Since there are no final error/warning messages on line <em>7</em>,
+rclone has recovered from failure after a retry, and the overall sync
+was successful.</p>
 <pre><code>1: 2021/05/14 00:44:12 INFO  : Synching Path1 &quot;/path/to/local/tree&quot; with Path2 &quot;dropbox:&quot;
 2: 2021/05/14 00:44:12 INFO  : Path1 checking for diffs
 3: 2021/05/14 00:44:12 INFO  : Path2 checking for diffs
@@ -13622,7 +22183,9 @@ rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
 5: 2021/05/14 00:44:12 ERROR : /path/to/local/tree/objects/af: error listing: unexpected end of JSON input
 6: 2021/05/14 00:44:12 NOTICE: WARNING  listing try 1 failed.                 - dropbox:
 7: 2021/05/14 00:44:12 INFO  : Bisync successful</code></pre>
-<p>This log shows a <em>Critical failure</em> which requires a <code>--resync</code> to recover from. See the <a href="#error-handling">Runtime Error Handling</a> section.</p>
+<p>This log shows a <em>Critical failure</em> which requires a
+<code>--resync</code> to recover from. See the <a
+href="#error-handling">Runtime Error Handling</a> section.</p>
 <pre><code>2021/05/12 00:49:40 INFO  : Google drive root &#39;&#39;: Waiting for checks to finish
 2021/05/12 00:49:40 INFO  : Google drive root &#39;&#39;: Waiting for transfers to finish
 2021/05/12 00:49:40 INFO  : Google drive root &#39;&#39;: not deleting files as there were IO errors
@@ -13630,21 +22193,79 @@ rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
 2021/05/12 00:49:40 ERROR : Failed to sync: not deleting files as there were IO errors
 2021/05/12 00:49:40 NOTICE: WARNING  rclone sync try 3 failed.           - /path/to/local/tree/
 2021/05/12 00:49:40 ERROR : Bisync aborted. Must run --resync to recover.</code></pre>
-<h3 id="denied-downloads-of-infected-or-abusive-files">Denied downloads of "infected" or "abusive" files</h3>
-<p>Google Drive has a filter for certain file types (<code>.exe</code>, <code>.apk</code>, et cetera) that by default cannot be copied from Google Drive to the local filesystem. If you are having problems, run with <code>--verbose</code> to see specifically which files are generating complaints. If the error is <code>This file has been identified as malware or spam and cannot be downloaded</code>, consider using the flag <a href="https://rclone.org/drive/#drive-acknowledge-abuse">--drive-acknowledge-abuse</a>.</p>
+<h3 id="denied-downloads-of-infected-or-abusive-files">Denied downloads
+of "infected" or "abusive" files</h3>
+<p>Google Drive has a filter for certain file types (<code>.exe</code>,
+<code>.apk</code>, et cetera) that by default cannot be copied from
+Google Drive to the local filesystem. If you are having problems, run
+with <code>--verbose</code> to see specifically which files are
+generating complaints. If the error is
+<code>This file has been identified as malware or spam and cannot be downloaded</code>,
+consider using the flag <a
+href="https://rclone.org/drive/#drive-acknowledge-abuse">--drive-acknowledge-abuse</a>.</p>
 <h3 id="gdocs">Google Docs (and other files of unknown size)</h3>
-<p>As of <code>v1.66</code>, <a href="https://rclone.org/drive/#import-export-of-google-documents">Google Docs</a> (including Google Sheets, Slides, etc.) are now supported in bisync, subject to the same options, defaults, and limitations as in <code>rclone sync</code>. When bisyncing drive with non-drive backends, the drive -&gt; non-drive direction is controlled by <a href="https://rclone.org/drive/#drive-export-formats"><code>--drive-export-formats</code></a> (default <code>"docx,xlsx,pptx,svg"</code>) and the non-drive -&gt; drive direction is controlled by <a href="https://rclone.org/drive/#drive-import-formats"><code>--drive-import-formats</code></a> (default none.)</p>
-<p>For example, with the default export/import formats, a Google Sheet on the drive side will be synced to an <code>.xlsx</code> file on the non-drive side. In the reverse direction, <code>.xlsx</code> files with filenames that match an existing Google Sheet will be synced to that Google Sheet, while <code>.xlsx</code> files that do NOT match an existing Google Sheet will be copied to drive as normal <code>.xlsx</code> files (without conversion to Sheets, although the Google Drive web browser UI may still give you the option to open it as one.)</p>
-<p>If <code>--drive-import-formats</code> is set (it's not, by default), then all of the specified formats will be converted to Google Docs, if there is no existing Google Doc with a matching name. Caution: such conversion can be quite lossy, and in most cases it's probably not what you want!</p>
-<p>To bisync Google Docs as URL shortcut links (in a manner similar to "Drive for Desktop"), use: <code>--drive-export-formats url</code> (or <a href="https://rclone.org/drive/#exportformats:~:text=available%20Google%20Documents.-,Extension,macOS,-Standard%20options">alternatives</a>.)</p>
-<p>Note that these link files cannot be edited on the non-drive side -- you will get errors if you try to sync an edited link file back to drive. They CAN be deleted (it will result in deleting the corresponding Google Doc.) If you create a <code>.url</code> file on the non-drive side that does not match an existing Google Doc, bisyncing it will just result in copying the literal <code>.url</code> file over to drive (no Google Doc will be created.) So, as a general rule of thumb, think of them as read-only placeholders on the non-drive side, and make all your changes on the drive side.</p>
-<p>Likewise, even with other export-formats, it is best to only move/rename Google Docs on the drive side. This is because otherwise, bisync will interpret this as a file deleted and another created, and accordingly, it will delete the Google Doc and create a new file at the new path. (Whether or not that new file is a Google Doc depends on <code>--drive-import-formats</code>.)</p>
-<p>Lastly, take note that all Google Docs on the drive side have a size of <code>-1</code> and no checksum. Therefore, they cannot be reliably synced with the <code>--checksum</code> or <code>--size-only</code> flags. (To be exact: they will still get created/deleted, and bisync's delta engine will notice changes and queue them for syncing, but the underlying sync function will consider them identical and skip them.) To work around this, use the default (modtime and size) instead of <code>--checksum</code> or <code>--size-only</code>.</p>
-<p>To ignore Google Docs entirely, use <a href="https://rclone.org/drive/#drive-skip-gdocs"><code>--drive-skip-gdocs</code></a>.</p>
+<p>As of <code>v1.66</code>, <a
+href="https://rclone.org/drive/#import-export-of-google-documents">Google
+Docs</a> (including Google Sheets, Slides, etc.) are now supported in
+bisync, subject to the same options, defaults, and limitations as in
+<code>rclone sync</code>. When bisyncing drive with non-drive backends,
+the drive -&gt; non-drive direction is controlled by <a
+href="https://rclone.org/drive/#drive-export-formats"><code>--drive-export-formats</code></a>
+(default <code>"docx,xlsx,pptx,svg"</code>) and the non-drive -&gt;
+drive direction is controlled by <a
+href="https://rclone.org/drive/#drive-import-formats"><code>--drive-import-formats</code></a>
+(default none.)</p>
+<p>For example, with the default export/import formats, a Google Sheet
+on the drive side will be synced to an <code>.xlsx</code> file on the
+non-drive side. In the reverse direction, <code>.xlsx</code> files with
+filenames that match an existing Google Sheet will be synced to that
+Google Sheet, while <code>.xlsx</code> files that do NOT match an
+existing Google Sheet will be copied to drive as normal
+<code>.xlsx</code> files (without conversion to Sheets, although the
+Google Drive web browser UI may still give you the option to open it as
+one.)</p>
+<p>If <code>--drive-import-formats</code> is set (it's not, by default),
+then all of the specified formats will be converted to Google Docs, if
+there is no existing Google Doc with a matching name. Caution: such
+conversion can be quite lossy, and in most cases it's probably not what
+you want!</p>
+<p>To bisync Google Docs as URL shortcut links (in a manner similar to
+"Drive for Desktop"), use: <code>--drive-export-formats url</code> (or
+<a
+href="https://rclone.org/drive/#exportformats:~:text=available%20Google%20Documents.-,Extension,macOS,-Standard%20options">alternatives</a>.)</p>
+<p>Note that these link files cannot be edited on the non-drive side --
+you will get errors if you try to sync an edited link file back to
+drive. They CAN be deleted (it will result in deleting the corresponding
+Google Doc.) If you create a <code>.url</code> file on the non-drive
+side that does not match an existing Google Doc, bisyncing it will just
+result in copying the literal <code>.url</code> file over to drive (no
+Google Doc will be created.) So, as a general rule of thumb, think of
+them as read-only placeholders on the non-drive side, and make all your
+changes on the drive side.</p>
+<p>Likewise, even with other export-formats, it is best to only
+move/rename Google Docs on the drive side. This is because otherwise,
+bisync will interpret this as a file deleted and another created, and
+accordingly, it will delete the Google Doc and create a new file at the
+new path. (Whether or not that new file is a Google Doc depends on
+<code>--drive-import-formats</code>.)</p>
+<p>Lastly, take note that all Google Docs on the drive side have a size
+of <code>-1</code> and no checksum. Therefore, they cannot be reliably
+synced with the <code>--checksum</code> or <code>--size-only</code>
+flags. (To be exact: they will still get created/deleted, and bisync's
+delta engine will notice changes and queue them for syncing, but the
+underlying sync function will consider them identical and skip them.) To
+work around this, use the default (modtime and size) instead of
+<code>--checksum</code> or <code>--size-only</code>.</p>
+<p>To ignore Google Docs entirely, use <a
+href="https://rclone.org/drive/#drive-skip-gdocs"><code>--drive-skip-gdocs</code></a>.</p>
 <h2 id="usage-examples">Usage examples</h2>
 <h3 id="cron">Cron</h3>
-<p>Rclone does not yet have a built-in capability to monitor the local file system for changes and must be blindly run periodically. On Windows this can be done using a <em>Task Scheduler</em>, on Linux you can use <em>Cron</em> which is described below.</p>
-<p>The 1st example runs a sync every 5 minutes between a local directory and an OwnCloud server, with output logged to a runlog file:</p>
+<p>Rclone does not yet have a built-in capability to monitor the local
+file system for changes and must be blindly run periodically. On Windows
+this can be done using a <em>Task Scheduler</em>, on Linux you can use
+<em>Cron</em> which is described below.</p>
+<p>The 1st example runs a sync every 5 minutes between a local directory
+and an OwnCloud server, with output logged to a runlog file:</p>
 <pre><code># Minute (0-59)
 #      Hour (0-23)
 #           Day of Month (1-31)
@@ -13652,25 +22273,57 @@ rclone copy Path1 Path2 [--create-empty-src-dirs]</code></pre>
 #                     Day of Week (0-6 or Sun-Sat)
 #                         Command
   */5  *    *    *    *   /path/to/rclone bisync /local/files MyCloud: --check-access --filters-file /path/to/bysync-filters.txt --log-file /path/to//bisync.log</code></pre>
-<p>See <a href="https://www.man7.org/linux/man-pages/man1/crontab.1p.html#INPUT_FILES">crontab syntax</a> for the details of crontab time interval expressions.</p>
-<p>If you run <code>rclone bisync</code> as a cron job, redirect stdout/stderr to a file. The 2nd example runs a sync to Dropbox every hour and logs all stdout (via the <code>&gt;&gt;</code>) and stderr (via <code>2&gt;&amp;1</code>) to a log file.</p>
+<p>See <a
+href="https://www.man7.org/linux/man-pages/man1/crontab.1p.html#INPUT_FILES">crontab
+syntax</a> for the details of crontab time interval expressions.</p>
+<p>If you run <code>rclone bisync</code> as a cron job, redirect
+stdout/stderr to a file. The 2nd example runs a sync to Dropbox every
+hour and logs all stdout (via the <code>&gt;&gt;</code>) and stderr (via
+<code>2&gt;&amp;1</code>) to a log file.</p>
 <pre><code>0 * * * * /path/to/rclone bisync /path/to/local/dropbox Dropbox: --check-access --filters-file /home/user/filters.txt &gt;&gt; /path/to/logs/dropbox-run.log 2&gt;&amp;1</code></pre>
-<h3 id="sharing-an-encrypted-folder-tree-between-hosts">Sharing an encrypted folder tree between hosts</h3>
-<p>bisync can keep a local folder in sync with a cloud service, but what if you have some highly sensitive files to be synched?</p>
-<p>Usage of a cloud service is for exchanging both routine and sensitive personal files between one's home network, one's personal notebook when on the road, and with one's work computer. The routine data is not sensitive. For the sensitive data, configure an rclone <a href="https://rclone.org/crypt/">crypt remote</a> to point to a subdirectory within the local disk tree that is bisync'd to Dropbox, and then set up an bisync for this local crypt directory to a directory outside of the main sync tree.</p>
+<h3 id="sharing-an-encrypted-folder-tree-between-hosts">Sharing an
+encrypted folder tree between hosts</h3>
+<p>bisync can keep a local folder in sync with a cloud service, but what
+if you have some highly sensitive files to be synched?</p>
+<p>Usage of a cloud service is for exchanging both routine and sensitive
+personal files between one's home network, one's personal notebook when
+on the road, and with one's work computer. The routine data is not
+sensitive. For the sensitive data, configure an rclone <a
+href="https://rclone.org/crypt/">crypt remote</a> to point to a
+subdirectory within the local disk tree that is bisync'd to Dropbox, and
+then set up an bisync for this local crypt directory to a directory
+outside of the main sync tree.</p>
 <h3 id="linux-server-setup">Linux server setup</h3>
 <ul>
-<li><code>/path/to/DBoxroot</code> is the root of my local sync tree. There are numerous subdirectories.</li>
-<li><code>/path/to/DBoxroot/crypt</code> is the root subdirectory for files that are encrypted. This local directory target is setup as an rclone crypt remote named <code>Dropcrypt:</code>. See <a href="#rclone-conf-snippet">rclone.conf</a> snippet below.</li>
-<li><code>/path/to/my/unencrypted/files</code> is the root of my sensitive files - not encrypted, not within the tree synched to Dropbox.</li>
-<li>To sync my local unencrypted files with the encrypted Dropbox versions I manually run <code>bisync /path/to/my/unencrypted/files DropCrypt:</code>. This step could be bundled into a script to run before and after the full Dropbox tree sync in the last step, thus actively keeping the sensitive files in sync.</li>
-<li><code>bisync /path/to/DBoxroot Dropbox:</code> runs periodically via cron, keeping my full local sync tree in sync with Dropbox.</li>
+<li><code>/path/to/DBoxroot</code> is the root of my local sync tree.
+There are numerous subdirectories.</li>
+<li><code>/path/to/DBoxroot/crypt</code> is the root subdirectory for
+files that are encrypted. This local directory target is setup as an
+rclone crypt remote named <code>Dropcrypt:</code>. See <a
+href="#rclone-conf-snippet">rclone.conf</a> snippet below.</li>
+<li><code>/path/to/my/unencrypted/files</code> is the root of my
+sensitive files - not encrypted, not within the tree synched to
+Dropbox.</li>
+<li>To sync my local unencrypted files with the encrypted Dropbox
+versions I manually run
+<code>bisync /path/to/my/unencrypted/files DropCrypt:</code>. This step
+could be bundled into a script to run before and after the full Dropbox
+tree sync in the last step, thus actively keeping the sensitive files in
+sync.</li>
+<li><code>bisync /path/to/DBoxroot Dropbox:</code> runs periodically via
+cron, keeping my full local sync tree in sync with Dropbox.</li>
 </ul>
 <h3 id="windows-notebook-setup">Windows notebook setup</h3>
 <ul>
-<li>The Dropbox client runs keeping the local tree <code>C:\Users\MyLogin\Dropbox</code> always in sync with Dropbox. I could have used <code>rclone bisync</code> instead.</li>
-<li>A separate directory tree at <code>C:\Users\MyLogin\Documents\DropLocal</code> hosts the tree of unencrypted files/folders.</li>
-<li>To sync my local unencrypted files with the encrypted Dropbox versions I manually run the following command: <code>rclone bisync C:\Users\MyLogin\Documents\DropLocal Dropcrypt:</code>.</li>
+<li>The Dropbox client runs keeping the local tree
+<code>C:\Users\MyLogin\Dropbox</code> always in sync with Dropbox. I
+could have used <code>rclone bisync</code> instead.</li>
+<li>A separate directory tree at
+<code>C:\Users\MyLogin\Documents\DropLocal</code> hosts the tree of
+unencrypted files/folders.</li>
+<li>To sync my local unencrypted files with the encrypted Dropbox
+versions I manually run the following command:
+<code>rclone bisync C:\Users\MyLogin\Documents\DropLocal Dropcrypt:</code>.</li>
 <li>The Dropbox client then syncs the changes with Dropbox.</li>
 </ul>
 <h3 id="rclone-conf-snippet">rclone.conf snippet</h3>
@@ -13687,9 +22340,20 @@ directory_name_encryption = true
 password = ...
 ...</code></pre>
 <h2 id="testing">Testing</h2>
-<p>You should read this section only if you are developing for rclone. You need to have rclone source code locally to work with bisync tests.</p>
-<p>Bisync has a dedicated test framework implemented in the <code>bisync_test.go</code> file located in the rclone source tree. The test suite is based on the <code>go test</code> command. Series of tests are stored in subdirectories below the <code>cmd/bisync/testdata</code> directory. Individual tests can be invoked by their directory name, e.g. <code>go test . -case basic -remote local -remote2 gdrive: -v</code></p>
-<p>Tests will make a temporary folder on remote and purge it afterwards. If during test run there are intermittent errors and rclone retries, these errors will be captured and flagged as invalid MISCOMPAREs. Rerunning the test will let it pass. Consider such failures as noise.</p>
+<p>You should read this section only if you are developing for rclone.
+You need to have rclone source code locally to work with bisync
+tests.</p>
+<p>Bisync has a dedicated test framework implemented in the
+<code>bisync_test.go</code> file located in the rclone source tree. The
+test suite is based on the <code>go test</code> command. Series of tests
+are stored in subdirectories below the <code>cmd/bisync/testdata</code>
+directory. Individual tests can be invoked by their directory name, e.g.
+<code>go test . -case basic -remote local -remote2 gdrive: -v</code></p>
+<p>Tests will make a temporary folder on remote and purge it afterwards.
+If during test run there are intermittent errors and rclone retries,
+these errors will be captured and flagged as invalid MISCOMPAREs.
+Rerunning the test will let it pass. Consider such failures as
+noise.</p>
 <h3 id="test-command-syntax">Test command syntax</h3>
 <pre><code>usage: go test ./cmd/bisync [options...]
 
@@ -13715,79 +22379,205 @@ Options:
   -refresh-times    Force refreshing the target modtime, useful for Dropbox
                     (default: false)
   -verbose          Run tests verbosely</code></pre>
-<p>Note: unlike rclone flags which must be prefixed by double dash (<code>--</code>), the test command flags can be equally prefixed by a single <code>-</code> or double dash.</p>
+<p>Note: unlike rclone flags which must be prefixed by double dash
+(<code>--</code>), the test command flags can be equally prefixed by a
+single <code>-</code> or double dash.</p>
 <h3 id="running-tests">Running tests</h3>
 <ul>
-<li><code>go test . -case basic -remote local -remote2 local</code> runs the <code>test_basic</code> test case using only the local filesystem, synching one local directory with another local directory. Test script output is to the console, while commands within scenario.txt have their output sent to the <code>.../workdir/test.log</code> file, which is finally compared to the golden copy.</li>
-<li>The first argument after <code>go test</code> should be a relative name of the directory containing bisync source code. If you run tests right from there, the argument will be <code>.</code> (current directory) as in most examples below. If you run bisync tests from the rclone source directory, the command should be <code>go test ./cmd/bisync ...</code>.</li>
-<li>The test engine will mangle rclone output to ensure comparability with golden listings and logs.</li>
-<li>Test scenarios are located in <code>./cmd/bisync/testdata</code>. The test <code>-case</code> argument should match the full name of a subdirectory under that directory. Every test subdirectory name on disk must start with <code>test_</code>, this prefix can be omitted on command line for brevity. Also, underscores in the name can be replaced by dashes for convenience.</li>
-<li><code>go test . -remote local -remote2 local -case all</code> runs all tests.</li>
-<li>Path1 and Path2 may either be the keyword <code>local</code> or may be names of configured cloud services. <code>go test . -remote gdrive: -remote2 dropbox: -case basic</code> will run the test between these two services, without transferring any files to the local filesystem.</li>
-<li>Test run stdout and stderr console output may be directed to a file, e.g. <code>go test . -remote gdrive: -remote2 local -case all &gt; runlog.txt 2&gt;&amp;1</code></li>
+<li><code>go test . -case basic -remote local -remote2 local</code> runs
+the <code>test_basic</code> test case using only the local filesystem,
+synching one local directory with another local directory. Test script
+output is to the console, while commands within scenario.txt have their
+output sent to the <code>.../workdir/test.log</code> file, which is
+finally compared to the golden copy.</li>
+<li>The first argument after <code>go test</code> should be a relative
+name of the directory containing bisync source code. If you run tests
+right from there, the argument will be <code>.</code> (current
+directory) as in most examples below. If you run bisync tests from the
+rclone source directory, the command should be
+<code>go test ./cmd/bisync ...</code>.</li>
+<li>The test engine will mangle rclone output to ensure comparability
+with golden listings and logs.</li>
+<li>Test scenarios are located in <code>./cmd/bisync/testdata</code>.
+The test <code>-case</code> argument should match the full name of a
+subdirectory under that directory. Every test subdirectory name on disk
+must start with <code>test_</code>, this prefix can be omitted on
+command line for brevity. Also, underscores in the name can be replaced
+by dashes for convenience.</li>
+<li><code>go test . -remote local -remote2 local -case all</code> runs
+all tests.</li>
+<li>Path1 and Path2 may either be the keyword <code>local</code> or may
+be names of configured cloud services.
+<code>go test . -remote gdrive: -remote2 dropbox: -case basic</code>
+will run the test between these two services, without transferring any
+files to the local filesystem.</li>
+<li>Test run stdout and stderr console output may be directed to a file,
+e.g.
+<code>go test . -remote gdrive: -remote2 local -case all &gt; runlog.txt 2&gt;&amp;1</code></li>
 </ul>
 <h3 id="test-execution-flow">Test execution flow</h3>
 <ol type="1">
-<li>The base setup in the <code>initial</code> directory of the testcase is applied on the Path1 and Path2 filesystems (via rclone copy the initial directory to Path1, then rclone sync Path1 to Path2).</li>
-<li>The commands in the scenario.txt file are applied, with output directed to the <code>test.log</code> file in the test working directory. Typically, the first actual command in the <code>scenario.txt</code> file is to do a <code>--resync</code>, which establishes the baseline <code>{...}.path1.lst</code> and <code>{...}.path2.lst</code> files in the test working directory (<code>.../workdir/</code> relative to the temporary test directory). Various commands and listing snapshots are done within the test.</li>
-<li>Finally, the contents of the test working directory are compared to the contents of the testcase's golden directory.</li>
+<li>The base setup in the <code>initial</code> directory of the testcase
+is applied on the Path1 and Path2 filesystems (via rclone copy the
+initial directory to Path1, then rclone sync Path1 to Path2).</li>
+<li>The commands in the scenario.txt file are applied, with output
+directed to the <code>test.log</code> file in the test working
+directory. Typically, the first actual command in the
+<code>scenario.txt</code> file is to do a <code>--resync</code>, which
+establishes the baseline <code>{...}.path1.lst</code> and
+<code>{...}.path2.lst</code> files in the test working directory
+(<code>.../workdir/</code> relative to the temporary test directory).
+Various commands and listing snapshots are done within the test.</li>
+<li>Finally, the contents of the test working directory are compared to
+the contents of the testcase's golden directory.</li>
 </ol>
 <h3 id="notes-about-testing">Notes about testing</h3>
 <ul>
-<li>Test cases are in individual directories beneath <code>./cmd/bisync/testdata</code>. A command line reference to a test is understood to reference a directory beneath <code>testdata</code>. For example, <code>go test ./cmd/bisync -case dry-run -remote gdrive: -remote2 local</code> refers to the test case in <code>./cmd/bisync/testdata/test_dry_run</code>.</li>
-<li>The test working directory is located at <code>.../workdir</code> relative to a temporary test directory, usually under <code>/tmp</code> on Linux.</li>
-<li>The local test sync tree is created at a temporary directory named like <code>bisync.XXX</code> under system temporary directory.</li>
-<li>The remote test sync tree is located at a temporary directory under <code>&lt;remote:&gt;/bisync.XXX/</code>.</li>
-<li><code>path1</code> and/or <code>path2</code> subdirectories are created in a temporary directory under the respective local or cloud test remote.</li>
-<li>By default, the Path1 and Path2 test dirs and workdir will be deleted after each test run. The <code>-no-cleanup</code> flag disables purging these directories when validating and debugging a given test. These directories will be flushed before running another test, independent of the <code>-no-cleanup</code> usage.</li>
-<li>You will likely want to add `- /testdir/<code>to your normal   bisync</code>--filters-file<code>so that normal syncs do not attempt to sync   the test temporary directories, which may have</code>RCLONE_TEST<code>miscompares   in some testcases which would otherwise trip the</code>--check-access<code>system.   The</code>--check-access<code>mechanism is hard-coded to ignore</code>RCLONE_TEST<code>files beneath</code>bisync/testdata`, so the test cases may reside on the synched tree even if there are check file mismatches in the test tree.</li>
-<li>Some Dropbox tests can fail, notably printing the following message: <code>src and dst identical but can't set mod time without deleting and re-uploading</code> This is expected and happens due to the way Dropbox handles modification times. You should use the <code>-refresh-times</code> test flag to make up for this.</li>
-<li>If Dropbox tests hit request limit for you and print error message <code>too_many_requests/...: Too many requests or write operations.</code> then follow the <a href="https://rclone.org/dropbox/#get-your-own-dropbox-app-id">Dropbox App ID instructions</a>.</li>
+<li>Test cases are in individual directories beneath
+<code>./cmd/bisync/testdata</code>. A command line reference to a test
+is understood to reference a directory beneath <code>testdata</code>.
+For example,
+<code>go test ./cmd/bisync -case dry-run -remote gdrive: -remote2 local</code>
+refers to the test case in
+<code>./cmd/bisync/testdata/test_dry_run</code>.</li>
+<li>The test working directory is located at <code>.../workdir</code>
+relative to a temporary test directory, usually under <code>/tmp</code>
+on Linux.</li>
+<li>The local test sync tree is created at a temporary directory named
+like <code>bisync.XXX</code> under system temporary directory.</li>
+<li>The remote test sync tree is located at a temporary directory under
+<code>&lt;remote:&gt;/bisync.XXX/</code>.</li>
+<li><code>path1</code> and/or <code>path2</code> subdirectories are
+created in a temporary directory under the respective local or cloud
+test remote.</li>
+<li>By default, the Path1 and Path2 test dirs and workdir will be
+deleted after each test run. The <code>-no-cleanup</code> flag disables
+purging these directories when validating and debugging a given test.
+These directories will be flushed before running another test,
+independent of the <code>-no-cleanup</code> usage.</li>
+<li>You will likely want to add <code>- /testdir/</code> to your normal
+bisync <code>--filters-file</code> so that normal syncs do not attempt
+to sync the test temporary directories, which may have
+<code>RCLONE_TEST</code> miscompares in some testcases which would
+otherwise trip the <code>--check-access</code> system. The
+<code>--check-access</code> mechanism is hard-coded to ignore
+<code>RCLONE_TEST</code> files beneath <code>bisync/testdata</code>, so
+the test cases may reside on the synched tree even if there are check
+file mismatches in the test tree.</li>
+<li>Some Dropbox tests can fail, notably printing the following message:
+<code>src and dst identical but can't set mod time without deleting and re-uploading</code>
+This is expected and happens due to the way Dropbox handles modification
+times. You should use the <code>-refresh-times</code> test flag to make
+up for this.</li>
+<li>If Dropbox tests hit request limit for you and print error message
+<code>too_many_requests/...: Too many requests or write operations.</code>
+then follow the <a
+href="https://rclone.org/dropbox/#get-your-own-dropbox-app-id">Dropbox
+App ID instructions</a>.</li>
 </ul>
 <h3 id="updating-golden-results">Updating golden results</h3>
-<p>Sometimes even a slight change in the bisync source can cause little changes spread around many log files. Updating them manually would be a nightmare.</p>
-<p>The <code>-golden</code> flag will store the <code>test.log</code> and <code>*.lst</code> listings from each test case into respective golden directories. Golden results will automatically contain generic strings instead of local or cloud paths which means that they should match when run with a different cloud service.</p>
-<p>Your normal workflow might be as follows: 1. Git-clone the rclone sources locally 2. Modify bisync source and check that it builds 3. Run the whole test suite <code>go test ./cmd/bisync -remote local</code> 4. If some tests show log difference, recheck them individually, e.g.: <code>go test ./cmd/bisync -remote local -case basic</code> 5. If you are convinced with the difference, goldenize all tests at once: <code>go test ./cmd/bisync -remote local -golden</code> 6. Use word diff: <code>git diff --word-diff ./cmd/bisync/testdata/</code>. Please note that normal line-level diff is generally useless here. 7. Check the difference <em>carefully</em>! 8. Commit the change (<code>git commit</code>) <em>only</em> if you are sure. If unsure, save your code changes then wipe the log diffs from git: <code>git reset [--hard]</code>.</p>
+<p>Sometimes even a slight change in the bisync source can cause little
+changes spread around many log files. Updating them manually would be a
+nightmare.</p>
+<p>The <code>-golden</code> flag will store the <code>test.log</code>
+and <code>*.lst</code> listings from each test case into respective
+golden directories. Golden results will automatically contain generic
+strings instead of local or cloud paths which means that they should
+match when run with a different cloud service.</p>
+<p>Your normal workflow might be as follows: 1. Git-clone the rclone
+sources locally 2. Modify bisync source and check that it builds 3. Run
+the whole test suite <code>go test ./cmd/bisync -remote local</code> 4.
+If some tests show log difference, recheck them individually, e.g.:
+<code>go test ./cmd/bisync -remote local -case basic</code> 5. If you
+are convinced with the difference, goldenize all tests at once:
+<code>go test ./cmd/bisync -remote local -golden</code> 6. Use word
+diff: <code>git diff --word-diff ./cmd/bisync/testdata/</code>. Please
+note that normal line-level diff is generally useless here. 7. Check the
+difference <em>carefully</em>! 8. Commit the change
+(<code>git commit</code>) <em>only</em> if you are sure. If unsure, save
+your code changes then wipe the log diffs from git:
+<code>git reset [--hard]</code>.</p>
 <h3 id="structure-of-test-scenarios">Structure of test scenarios</h3>
 <ul>
-<li><code>&lt;testname&gt;/initial/</code> contains a tree of files that will be set as the initial condition on both Path1 and Path2 testdirs.</li>
-<li><code>&lt;testname&gt;/modfiles/</code> contains files that will be used to modify the Path1 and/or Path2 filesystems.</li>
-<li><code>&lt;testname&gt;/golden/</code> contains the expected content of the test working directory (<code>workdir</code>) at the completion of the testcase.</li>
-<li><code>&lt;testname&gt;/scenario.txt</code> contains the body of the test, in the form of various commands to modify files, run bisync, and snapshot listings. Output from these commands is captured to <code>.../workdir/test.log</code> for comparison to the golden files.</li>
+<li><code>&lt;testname&gt;/initial/</code> contains a tree of files that
+will be set as the initial condition on both Path1 and Path2
+testdirs.</li>
+<li><code>&lt;testname&gt;/modfiles/</code> contains files that will be
+used to modify the Path1 and/or Path2 filesystems.</li>
+<li><code>&lt;testname&gt;/golden/</code> contains the expected content
+of the test working directory (<code>workdir</code>) at the completion
+of the testcase.</li>
+<li><code>&lt;testname&gt;/scenario.txt</code> contains the body of the
+test, in the form of various commands to modify files, run bisync, and
+snapshot listings. Output from these commands is captured to
+<code>.../workdir/test.log</code> for comparison to the golden
+files.</li>
 </ul>
 <h3 id="supported-test-commands">Supported test commands</h3>
 <ul>
-<li><code>test &lt;some message&gt;</code> Print the line to the console and to the <code>test.log</code>: <code>test sync is working correctly with options x, y, z</code></li>
-<li><code>copy-listings &lt;prefix&gt;</code> Save a copy of all <code>.lst</code> listings in the test working directory with the specified prefix: <code>save-listings exclude-pass-run</code></li>
-<li><code>move-listings &lt;prefix&gt;</code> Similar to <code>copy-listings</code> but removes the source</li>
-<li><code>purge-children &lt;dir&gt;</code> This will delete all child files and purge all child subdirs under given directory but keep the parent intact. This behavior is important for tests with Google Drive because removing and re-creating the parent would change its ID.</li>
+<li><code>test &lt;some message&gt;</code> Print the line to the console
+and to the <code>test.log</code>:
+<code>test sync is working correctly with options x, y, z</code></li>
+<li><code>copy-listings &lt;prefix&gt;</code> Save a copy of all
+<code>.lst</code> listings in the test working directory with the
+specified prefix: <code>save-listings exclude-pass-run</code></li>
+<li><code>move-listings &lt;prefix&gt;</code> Similar to
+<code>copy-listings</code> but removes the source</li>
+<li><code>purge-children &lt;dir&gt;</code> This will delete all child
+files and purge all child subdirs under given directory but keep the
+parent intact. This behavior is important for tests with Google Drive
+because removing and re-creating the parent would change its ID.</li>
 <li><code>delete-file &lt;file&gt;</code> Delete a single file.</li>
-<li><code>delete-glob &lt;dir&gt; &lt;pattern&gt;</code> Delete a group of files located one level deep in the given directory with names matching a given glob pattern.</li>
-<li><code>touch-glob YYYY-MM-DD &lt;dir&gt; &lt;pattern&gt;</code> Change modification time on a group of files.</li>
-<li><code>touch-copy YYYY-MM-DD &lt;source-file&gt; &lt;dest-dir&gt;</code> Change file modification time then copy it to destination.</li>
-<li><code>copy-file &lt;source-file&gt; &lt;dest-dir&gt;</code> Copy a single file to given directory.</li>
-<li><code>copy-as &lt;source-file&gt; &lt;dest-file&gt;</code> Similar to above but destination must include both directory and the new file name at destination.</li>
-<li><code>copy-dir &lt;src&gt; &lt;dst&gt;</code> and <code>sync-dir &lt;src&gt; &lt;dst&gt;</code> Copy/sync a directory. Equivalent of <code>rclone copy</code> and <code>rclone sync</code>.</li>
-<li><code>list-dirs &lt;dir&gt;</code> Equivalent to <code>rclone lsf -R --dirs-only &lt;dir&gt;</code></li>
-<li><code>bisync [options]</code> Runs bisync against <code>-remote</code> and <code>-remote2</code>.</li>
+<li><code>delete-glob &lt;dir&gt; &lt;pattern&gt;</code> Delete a group
+of files located one level deep in the given directory with names
+matching a given glob pattern.</li>
+<li><code>touch-glob YYYY-MM-DD &lt;dir&gt; &lt;pattern&gt;</code>
+Change modification time on a group of files.</li>
+<li><code>touch-copy YYYY-MM-DD &lt;source-file&gt; &lt;dest-dir&gt;</code>
+Change file modification time then copy it to destination.</li>
+<li><code>copy-file &lt;source-file&gt; &lt;dest-dir&gt;</code> Copy a
+single file to given directory.</li>
+<li><code>copy-as &lt;source-file&gt; &lt;dest-file&gt;</code> Similar
+to above but destination must include both directory and the new file
+name at destination.</li>
+<li><code>copy-dir &lt;src&gt; &lt;dst&gt;</code> and
+<code>sync-dir &lt;src&gt; &lt;dst&gt;</code> Copy/sync a directory.
+Equivalent of <code>rclone copy</code> and
+<code>rclone sync</code>.</li>
+<li><code>list-dirs &lt;dir&gt;</code> Equivalent to
+<code>rclone lsf -R --dirs-only &lt;dir&gt;</code></li>
+<li><code>bisync [options]</code> Runs bisync against
+<code>-remote</code> and <code>-remote2</code>.</li>
 </ul>
 <h3 id="supported-substitution-terms">Supported substitution terms</h3>
 <ul>
 <li><code>{testdir/}</code> - the root dir of the testcase</li>
-<li><code>{datadir/}</code> - the <code>modfiles</code> dir under the testcase root</li>
+<li><code>{datadir/}</code> - the <code>modfiles</code> dir under the
+testcase root</li>
 <li><code>{workdir/}</code> - the temporary test working directory</li>
-<li><code>{path1/}</code> - the root of the Path1 test directory tree</li>
-<li><code>{path2/}</code> - the root of the Path2 test directory tree</li>
+<li><code>{path1/}</code> - the root of the Path1 test directory
+tree</li>
+<li><code>{path2/}</code> - the root of the Path2 test directory
+tree</li>
 <li><code>{session}</code> - base name of the test listings</li>
 <li><code>{/}</code> - OS-specific path separator</li>
-<li><code>{spc}</code>, <code>{tab}</code>, <code>{eol}</code> - whitespace</li>
+<li><code>{spc}</code>, <code>{tab}</code>, <code>{eol}</code> -
+whitespace</li>
 <li><code>{chr:HH}</code> - raw byte with given hexadecimal code</li>
 </ul>
-<p>Substitution results of the terms named like <code>{dir/}</code> will end with <code>/</code> (or backslash on Windows), so it is not necessary to include slash in the usage, for example <code>delete-file {path1/}file1.txt</code>.</p>
+<p>Substitution results of the terms named like <code>{dir/}</code> will
+end with <code>/</code> (or backslash on Windows), so it is not
+necessary to include slash in the usage, for example
+<code>delete-file {path1/}file1.txt</code>.</p>
 <h2 id="benchmarks">Benchmarks</h2>
 <p><em>This section is work in progress.</em></p>
-<p>Here are a few data points for scale, execution times, and memory usage.</p>
-<p>The first set of data was taken between a local disk to Dropbox. The <a href="https://speedtest.net">speedtest.net</a> download speed was ~170 Mbps, and upload speed was ~10 Mbps. 500 files (~9.5 MB each) had been already synched. 50 files were added in a new directory, each ~9.5 MB, ~475 MB total.</p>
+<p>Here are a few data points for scale, execution times, and memory
+usage.</p>
+<p>The first set of data was taken between a local disk to Dropbox. The
+<a href="https://speedtest.net">speedtest.net</a> download speed was
+~170 Mbps, and upload speed was ~10 Mbps. 500 files (~9.5 MB each) had
+been already synched. 50 files were added in a new directory, each ~9.5
+MB, ~475 MB total.</p>
 <table>
 <colgroup>
 <col style="width: 33%" />
@@ -13834,30 +22624,57 @@ Options:
 </tr>
 </tbody>
 </table>
-<p>This next data is from a user's application. They had ~400GB of data over 1.96 million files being sync'ed between a Windows local disk and some remote cloud. The file full path length was on average 35 characters (which factors into load time and RAM required).</p>
+<p>This next data is from a user's application. They had ~400GB of data
+over 1.96 million files being sync'ed between a Windows local disk and
+some remote cloud. The file full path length was on average 35
+characters (which factors into load time and RAM required).</p>
 <ul>
-<li>Loading the prior listing into memory (1.96 million files, listing file size 140 MB) took ~30 sec and occupied about 1 GB of RAM.</li>
-<li>Getting a fresh listing of the local file system (producing the 140 MB output file) took about XXX sec.</li>
-<li>Getting a fresh listing of the remote file system (producing the 140 MB output file) took about XXX sec. The network download speed was measured at XXX Mb/s.</li>
-<li>Once the prior and current Path1 and Path2 listings were loaded (a total of four to be loaded, two at a time), determining the deltas was pretty quick (a few seconds for this test case), and the transfer time for any files to be copied was dominated by the network bandwidth.</li>
+<li>Loading the prior listing into memory (1.96 million files, listing
+file size 140 MB) took ~30 sec and occupied about 1 GB of RAM.</li>
+<li>Getting a fresh listing of the local file system (producing the 140
+MB output file) took about XXX sec.</li>
+<li>Getting a fresh listing of the remote file system (producing the 140
+MB output file) took about XXX sec. The network download speed was
+measured at XXX Mb/s.</li>
+<li>Once the prior and current Path1 and Path2 listings were loaded (a
+total of four to be loaded, two at a time), determining the deltas was
+pretty quick (a few seconds for this test case), and the transfer time
+for any files to be copied was dominated by the network bandwidth.</li>
 </ul>
 <h2 id="references">References</h2>
-<p>rclone's bisync implementation was derived from the <a href="https://github.com/cjnaz/rclonesync-V2">rclonesync-V2</a> project, including documentation and test mechanisms, with <span class="citation" data-cites="cjnaz">[@cjnaz]</span>(https://github.com/cjnaz)'s full support and encouragement.</p>
-<p><code>rclone bisync</code> is similar in nature to a range of other projects:</p>
+<p>rclone's bisync implementation was derived from the <a
+href="https://github.com/cjnaz/rclonesync-V2">rclonesync-V2</a> project,
+including documentation and test mechanisms, with <a
+href="https://github.com/cjnaz"><span class="citation"
+data-cites="cjnaz">@cjnaz</span></a>'s full support and
+encouragement.</p>
+<p><code>rclone bisync</code> is similar in nature to a range of other
+projects:</p>
 <ul>
 <li><a href="https://github.com/bcpierce00/unison">unison</a></li>
 <li><a href="https://github.com/syncthing/syncthing">syncthing</a></li>
-<li><a href="https://github.com/cjnaz/rclonesync-V2">cjnaz/rclonesync</a></li>
-<li><a href="https://github.com/ConorWilliams/rsinc">ConorWilliams/rsinc</a></li>
-<li><a href="https://github.com/Jwink3101/syncrclone">jwink3101/syncrclone</a></li>
-<li><a href="https://github.com/DavideRossi/upback">DavideRossi/upback</a></li>
+<li><a
+href="https://github.com/cjnaz/rclonesync-V2">cjnaz/rclonesync</a></li>
+<li><a
+href="https://github.com/ConorWilliams/rsinc">ConorWilliams/rsinc</a></li>
+<li><a
+href="https://github.com/Jwink3101/syncrclone">jwink3101/syncrclone</a></li>
+<li><a
+href="https://github.com/DavideRossi/upback">DavideRossi/upback</a></li>
 </ul>
-<p>Bisync adopts the differential synchronization technique, which is based on keeping history of changes performed by both synchronizing sides. See the <em>Dual Shadow Method</em> section in <a href="https://neil.fraser.name/writing/sync/">Neil Fraser's article</a>.</p>
-<p>Also note a number of academic publications by <a href="http://www.cis.upenn.edu/%7Ebcpierce/papers/index.shtml#File%20Synchronization">Benjamin Pierce</a> about <em>Unison</em> and synchronization in general.</p>
+<p>Bisync adopts the differential synchronization technique, which is
+based on keeping history of changes performed by both synchronizing
+sides. See the <em>Dual Shadow Method</em> section in <a
+href="https://neil.fraser.name/writing/sync/">Neil Fraser's
+article</a>.</p>
+<p>Also note a number of academic publications by <a
+href="http://www.cis.upenn.edu/%7Ebcpierce/papers/index.shtml#File%20Synchronization">Benjamin
+Pierce</a> about <em>Unison</em> and synchronization in general.</p>
 <h2 id="changelog">Changelog</h2>
 <h3 id="v1.68"><code>v1.68</code></h3>
 <ul>
-<li>Fixed an issue affecting backends that round modtimes to a lower precision.</li>
+<li>Fixed an issue affecting backends that round modtimes to a lower
+precision.</li>
 </ul>
 <h3 id="v1.67"><code>v1.67</code></h3>
 <ul>
@@ -13865,61 +22682,143 @@ Options:
 </ul>
 <h3 id="v1.66"><code>v1.66</code></h3>
 <ul>
-<li>Copies and deletes are now handled in one operation instead of two</li>
-<li><code>--track-renames</code> and <code>--backup-dir</code> are now supported</li>
-<li>Partial uploads known issue on <code>local</code>/<code>ftp</code>/<code>sftp</code> has been resolved (unless using <code>--inplace</code>)</li>
-<li>Final listings are now generated from sync results, to avoid needing to re-list</li>
-<li>Bisync is now much more resilient to changes that happen during a bisync run, and far less prone to critical errors / undetected changes</li>
-<li>Bisync is now capable of rolling a file listing back in cases of uncertainty, essentially marking the file as needing to be rechecked next time.</li>
-<li>A few basic terminal colors are now supported, controllable with <a href="https://rclone.org/docs/#color-when"><code>--color</code></a> (<code>AUTO</code>|<code>NEVER</code>|<code>ALWAYS</code>)</li>
-<li>Initial listing snapshots of Path1 and Path2 are now generated concurrently, using the same "march" infrastructure as <code>check</code> and <code>sync</code>, for performance improvements and less <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors">risk of error</a>.</li>
-<li>Fixed handling of unicode normalization and case insensitivity, support for <a href="https://rclone.org/docs/#fix-case"><code>--fix-case</code></a>, <a href="/docs/#ignore-case-sync"><code>--ignore-case-sync</code></a>, <a href="/docs/#no-unicode-normalization"><code>--no-unicode-normalization</code></a></li>
-<li><code>--resync</code> is now much more efficient (especially for users of <code>--create-empty-src-dirs</code>)</li>
-<li>Google Docs (and other files of unknown size) are now supported (with the same options as in <code>sync</code>)</li>
-<li>Equality checks before a sync conflict rename now fall back to <code>cryptcheck</code> (when possible) or <code>--download</code>, instead of of <code>--size-only</code>, when <code>check</code> is not available.</li>
-<li>Bisync no longer fails to find the correct listing file when configs are overridden with backend-specific flags.</li>
-<li>Bisync now fully supports comparing based on any combination of size, modtime, and checksum, lifting the prior restriction on backends without modtime support.</li>
-<li>Bisync now supports a "Graceful Shutdown" mode to cleanly cancel a run early without requiring <code>--resync</code>.</li>
-<li>New <code>--recover</code> flag allows robust recovery in the event of interruptions, without requiring <code>--resync</code>.</li>
-<li>A new <code>--max-lock</code> setting allows lock files to automatically renew and expire, for better automatic recovery when a run is interrupted.</li>
-<li>Bisync now supports auto-resolving sync conflicts and customizing rename behavior with new <a href="#conflict-resolve"><code>--conflict-resolve</code></a>, <a href="#conflict-loser"><code>--conflict-loser</code></a>, and <a href="#conflict-suffix"><code>--conflict-suffix</code></a> flags.</li>
-<li>A new <a href="#resync-mode"><code>--resync-mode</code></a> flag allows more control over which version of a file gets kept during a <code>--resync</code>.</li>
-<li>Bisync now supports <a href="https://rclone.org/docs/#retries-int"><code>--retries</code></a> and <a href="/docs/#retries-sleep-time"><code>--retries-sleep</code></a> (when <a href="#resilient"><code>--resilient</code></a> is set.)</li>
+<li>Copies and deletes are now handled in one operation instead of
+two</li>
+<li><code>--track-renames</code> and <code>--backup-dir</code> are now
+supported</li>
+<li>Partial uploads known issue on
+<code>local</code>/<code>ftp</code>/<code>sftp</code> has been resolved
+(unless using <code>--inplace</code>)</li>
+<li>Final listings are now generated from sync results, to avoid needing
+to re-list</li>
+<li>Bisync is now much more resilient to changes that happen during a
+bisync run, and far less prone to critical errors / undetected
+changes</li>
+<li>Bisync is now capable of rolling a file listing back in cases of
+uncertainty, essentially marking the file as needing to be rechecked
+next time.</li>
+<li>A few basic terminal colors are now supported, controllable with <a
+href="https://rclone.org/docs/#color-when"><code>--color</code></a>
+(<code>AUTO</code>|<code>NEVER</code>|<code>ALWAYS</code>)</li>
+<li>Initial listing snapshots of Path1 and Path2 are now generated
+concurrently, using the same "march" infrastructure as
+<code>check</code> and <code>sync</code>, for performance improvements
+and less <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors">risk
+of error</a>.</li>
+<li>Fixed handling of unicode normalization and case insensitivity,
+support for <a
+href="https://rclone.org/docs/#fix-case"><code>--fix-case</code></a>, <a
+href="/docs/#ignore-case-sync"><code>--ignore-case-sync</code></a>, <a
+href="/docs/#no-unicode-normalization"><code>--no-unicode-normalization</code></a></li>
+<li><code>--resync</code> is now much more efficient (especially for
+users of <code>--create-empty-src-dirs</code>)</li>
+<li>Google Docs (and other files of unknown size) are now supported
+(with the same options as in <code>sync</code>)</li>
+<li>Equality checks before a sync conflict rename now fall back to
+<code>cryptcheck</code> (when possible) or <code>--download</code>,
+instead of of <code>--size-only</code>, when <code>check</code> is not
+available.</li>
+<li>Bisync no longer fails to find the correct listing file when configs
+are overridden with backend-specific flags.</li>
+<li>Bisync now fully supports comparing based on any combination of
+size, modtime, and checksum, lifting the prior restriction on backends
+without modtime support.</li>
+<li>Bisync now supports a "Graceful Shutdown" mode to cleanly cancel a
+run early without requiring <code>--resync</code>.</li>
+<li>New <code>--recover</code> flag allows robust recovery in the event
+of interruptions, without requiring <code>--resync</code>.</li>
+<li>A new <code>--max-lock</code> setting allows lock files to
+automatically renew and expire, for better automatic recovery when a run
+is interrupted.</li>
+<li>Bisync now supports auto-resolving sync conflicts and customizing
+rename behavior with new <a
+href="#conflict-resolve"><code>--conflict-resolve</code></a>, <a
+href="#conflict-loser"><code>--conflict-loser</code></a>, and <a
+href="#conflict-suffix"><code>--conflict-suffix</code></a> flags.</li>
+<li>A new <a href="#resync-mode"><code>--resync-mode</code></a> flag
+allows more control over which version of a file gets kept during a
+<code>--resync</code>.</li>
+<li>Bisync now supports <a
+href="https://rclone.org/docs/#retries-int"><code>--retries</code></a>
+and <a href="/docs/#retries-sleep-time"><code>--retries-sleep</code></a>
+(when <a href="#resilient"><code>--resilient</code></a> is set.)</li>
 </ul>
 <h3 id="v1.64"><code>v1.64</code></h3>
 <ul>
-<li>Fixed an <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=1.%20Dry%20runs%20are%20not%20completely%20dry">issue</a> causing dry runs to inadvertently commit filter changes</li>
-<li>Fixed an <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=2.%20%2D%2Dresync%20deletes%20data%2C%20contrary%20to%20docs">issue</a> causing <code>--resync</code> to erroneously delete empty folders and duplicate files unique to Path2</li>
-<li><code>--check-access</code> is now enforced during <code>--resync</code>, preventing data loss in <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=%2D%2Dcheck%2Daccess%20doesn%27t%20always%20fail%20when%20it%20should">certain user error scenarios</a></li>
-<li>Fixed an <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=5.%20Bisync%20reads%20files%20in%20excluded%20directories%20during%20delete%20operations">issue</a> causing bisync to consider more files than necessary due to overbroad filters during delete operations</li>
-<li><a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=1.%20Identical%20files%20should%20be%20left%20alone%2C%20even%20if%20new/newer/changed%20on%20both%20sides">Improved detection of false positive change conflicts</a> (identical files are now left alone instead of renamed)</li>
-<li>Added <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20Bisync%20should%20create/delete%20empty%20directories%20as%20sync%20does%2C%20when%20%2D%2Dcreate%2Dempty%2Dsrc%2Ddirs%20is%20passed">support for <code>--create-empty-src-dirs</code></a></li>
-<li>Added experimental <code>--resilient</code> mode to allow <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=2.%20Bisync%20should%20be%20more%20resilient%20to%20self%2Dcorrectable%20errors">recovery from self-correctable errors</a></li>
-<li>Added <a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=6.%20%2D%2Dignore%2Dchecksum%20should%20be%20split%20into%20two%20flags%20for%20separate%20purposes">new <code>--ignore-listing-checksum</code> flag</a> to distinguish from <code>--ignore-checksum</code></li>
-<li><a href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=6.%20Deletes%20take%20several%20times%20longer%20than%20copies">Performance improvements</a> for large remotes</li>
+<li>Fixed an <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=1.%20Dry%20runs%20are%20not%20completely%20dry">issue</a>
+causing dry runs to inadvertently commit filter changes</li>
+<li>Fixed an <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=2.%20%2D%2Dresync%20deletes%20data%2C%20contrary%20to%20docs">issue</a>
+causing <code>--resync</code> to erroneously delete empty folders and
+duplicate files unique to Path2</li>
+<li><code>--check-access</code> is now enforced during
+<code>--resync</code>, preventing data loss in <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=%2D%2Dcheck%2Daccess%20doesn%27t%20always%20fail%20when%20it%20should">certain
+user error scenarios</a></li>
+<li>Fixed an <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=5.%20Bisync%20reads%20files%20in%20excluded%20directories%20during%20delete%20operations">issue</a>
+causing bisync to consider more files than necessary due to overbroad
+filters during delete operations</li>
+<li><a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=1.%20Identical%20files%20should%20be%20left%20alone%2C%20even%20if%20new/newer/changed%20on%20both%20sides">Improved
+detection of false positive change conflicts</a> (identical files are
+now left alone instead of renamed)</li>
+<li>Added <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20Bisync%20should%20create/delete%20empty%20directories%20as%20sync%20does%2C%20when%20%2D%2Dcreate%2Dempty%2Dsrc%2Ddirs%20is%20passed">support
+for <code>--create-empty-src-dirs</code></a></li>
+<li>Added experimental <code>--resilient</code> mode to allow <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=2.%20Bisync%20should%20be%20more%20resilient%20to%20self%2Dcorrectable%20errors">recovery
+from self-correctable errors</a></li>
+<li>Added <a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=6.%20%2D%2Dignore%2Dchecksum%20should%20be%20split%20into%20two%20flags%20for%20separate%20purposes">new
+<code>--ignore-listing-checksum</code> flag</a> to distinguish from
+<code>--ignore-checksum</code></li>
+<li><a
+href="https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=6.%20Deletes%20take%20several%20times%20longer%20than%20copies">Performance
+improvements</a> for large remotes</li>
 <li>Documentation and testing improvements</li>
 </ul>
 <h1 id="release-signing">Release signing</h1>
-<p>The hashes of the binary artefacts of the rclone release are signed with a public PGP/GPG key. This can be verified manually as described below.</p>
-<p>The same mechanism is also used by <a href="https://rclone.org/commands/rclone_selfupdate/">rclone selfupdate</a> to verify that the release has not been tampered with before the new update is installed. This checks the SHA256 hash and the signature with a public key compiled into the rclone binary.</p>
+<p>The hashes of the binary artefacts of the rclone release are signed
+with a public PGP/GPG key. This can be verified manually as described
+below.</p>
+<p>The same mechanism is also used by <a
+href="https://rclone.org/commands/rclone_selfupdate/">rclone
+selfupdate</a> to verify that the release has not been tampered with
+before the new update is installed. This checks the SHA256 hash and the
+signature with a public key compiled into the rclone binary.</p>
 <h2 id="release-signing-key">Release signing key</h2>
 <p>You may obtain the release signing key from:</p>
 <ul>
-<li>From <a href="/KEYS">KEYS</a> on this website - this file contains all past signing keys also.</li>
-<li>The git repository hosted on GitHub - https://github.com/rclone/rclone/blob/master/docs/content/KEYS</li>
+<li>From <a href="/KEYS">KEYS</a> on this website - this file contains
+all past signing keys also.</li>
+<li>The git repository hosted on GitHub -
+https://github.com/rclone/rclone/blob/master/docs/content/KEYS</li>
 <li><code>gpg --keyserver hkps://keys.openpgp.org --search nick@craig-wood.com</code></li>
 <li><code>gpg --keyserver hkps://keyserver.ubuntu.com --search nick@craig-wood.com</code></li>
 <li>https://www.craig-wood.com/nick/pub/pgp-key.txt</li>
 </ul>
-<p>After importing the key, verify that the fingerprint of one of the keys matches: <code>FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA</code> as this key is used for signing.</p>
-<p>We recommend that you cross-check the fingerprint shown above through the domains listed below. By cross-checking the integrity of the fingerprint across multiple domains you can be confident that you obtained the correct key.</p>
+<p>After importing the key, verify that the fingerprint of one of the
+keys matches: <code>FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA</code> as
+this key is used for signing.</p>
+<p>We recommend that you cross-check the fingerprint shown above through
+the domains listed below. By cross-checking the integrity of the
+fingerprint across multiple domains you can be confident that you
+obtained the correct key.</p>
 <ul>
-<li>The <a href="https://github.com/rclone/rclone/blob/master/docs/content/release_signing.md">source for this page on GitHub</a>.</li>
+<li>The <a
+href="https://github.com/rclone/rclone/blob/master/docs/content/release_signing.md">source
+for this page on GitHub</a>.</li>
 <li>Through DNS <code>dig key.rclone.org txt</code></li>
 </ul>
-<p>If you find anything that doesn't not match, please contact the developers at once.</p>
+<p>If you find anything that doesn't not match, please contact the
+developers at once.</p>
 <h2 id="how-to-verify-the-release">How to verify the release</h2>
-<p>In the release directory you will see the release files and some files called <code>MD5SUMS</code>, <code>SHA1SUMS</code> and <code>SHA256SUMS</code>.</p>
+<p>In the release directory you will see the release files and some
+files called <code>MD5SUMS</code>, <code>SHA1SUMS</code> and
+<code>SHA256SUMS</code>.</p>
 <pre><code>$ rclone lsf --http-url https://downloads.rclone.org/v1.63.1 :http:
 MD5SUMS
 SHA1SUMS
@@ -13930,7 +22829,9 @@ rclone-v1.63.1-freebsd-amd64.zip
 rclone-v1.63.1-windows-arm64.zip
 rclone-v1.63.1.tar.gz
 version.txt</code></pre>
-<p>The <code>MD5SUMS</code>, <code>SHA1SUMS</code> and <code>SHA256SUMS</code> contain hashes of the binary files in the release directory along with a signature.</p>
+<p>The <code>MD5SUMS</code>, <code>SHA1SUMS</code> and
+<code>SHA256SUMS</code> contain hashes of the binary files in the
+release directory along with a signature.</p>
 <p>For example:</p>
 <pre><code>$ rclone cat --http-url https://downloads.rclone.org/v1.63.1 :http:SHA256SUMS
 -----BEGIN PGP SIGNED MESSAGE-----
@@ -13948,7 +22849,14 @@ iF0EARECAB0WIQT79zfs6firGGBL0qyTk14C/ztU+gUCZLVKJQAKCRCTk14C/ztU
 =8qrL
 -----END PGP SIGNATURE-----</code></pre>
 <h3 id="download-the-files">Download the files</h3>
-<p>The first step is to download the binary and SUMs file and verify that the SUMs you have downloaded match. Here we download <code>rclone-v1.63.1-windows-amd64.zip</code> - choose the binary (or binaries) appropriate to your architecture. We've also chosen the <code>SHA256SUMS</code> as these are the most secure. You could verify the other types of hash also for extra security. <code>rclone selfupdate</code> verifies just the <code>SHA256SUMS</code>.</p>
+<p>The first step is to download the binary and SUMs file and verify
+that the SUMs you have downloaded match. Here we download
+<code>rclone-v1.63.1-windows-amd64.zip</code> - choose the binary (or
+binaries) appropriate to your architecture. We've also chosen the
+<code>SHA256SUMS</code> as these are the most secure. You could verify
+the other types of hash also for extra security.
+<code>rclone selfupdate</code> verifies just the
+<code>SHA256SUMS</code>.</p>
 <pre><code>$ mkdir /tmp/check
 $ cd /tmp/check
 $ rclone copy --http-url https://downloads.rclone.org/v1.63.1 :http:SHA256SUMS .
@@ -13965,10 +22873,13 @@ gpg:               imported: 1</code></pre>
 gpg: Signature made Mon 17 Jul 2023 15:03:17 BST
 gpg:                using DSA key FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA
 gpg: Good signature from &quot;Nick Craig-Wood &lt;nick@craig-wood.com&gt;&quot; [ultimate]</code></pre>
-<p>Verify the signature was good and is using the fingerprint shown above.</p>
-<p>Repeat for <code>MD5SUMS</code> and <code>SHA1SUMS</code> if desired.</p>
+<p>Verify the signature was good and is using the fingerprint shown
+above.</p>
+<p>Repeat for <code>MD5SUMS</code> and <code>SHA1SUMS</code> if
+desired.</p>
 <h3 id="verify-the-hashes">Verify the hashes</h3>
-<p>Now that we know the signatures on the hashes are OK we can verify the binaries match the hashes, completing the verification.</p>
+<p>Now that we know the signatures on the hashes are OK we can verify
+the binaries match the hashes, completing the verification.</p>
 <pre><code>$ sha256sum -c SHA256SUMS 2&gt;&amp;1 | grep OK
 rclone-v1.63.1-windows-amd64.zip: OK</code></pre>
 <p>Or do the check with rclone</p>
@@ -13980,8 +22891,10 @@ rclone-v1.63.1-windows-amd64.zip: OK</code></pre>
 = rclone-v1.63.1-windows-amd64.zip
 2023/09/11 10:53:58 NOTICE: Local file system at /tmp/check: 0 differences found
 2023/09/11 10:53:58 NOTICE: Local file system at /tmp/check: 1 matching files</code></pre>
-<h3 id="verify-signatures-and-hashes-together">Verify signatures and hashes together</h3>
-<p>You can verify the signatures and hashes in one command line like this:</p>
+<h3 id="verify-signatures-and-hashes-together">Verify signatures and
+hashes together</h3>
+<p>You can verify the signatures and hashes in one command line like
+this:</p>
 <pre><code>$ h=$(gpg --decrypt SHA256SUMS) &amp;&amp; echo &quot;$h&quot; | sha256sum - -c --ignore-missing
 gpg: Signature made Mon 17 Jul 2023 15:03:17 BST
 gpg:                using DSA key FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA
@@ -13989,12 +22902,17 @@ gpg: Good signature from &quot;Nick Craig-Wood &lt;nick@craig-wood.com&gt;&quot;
 gpg:                 aka &quot;Nick Craig-Wood &lt;nick@memset.com&gt;&quot; [unknown]
 rclone-v1.63.1-windows-amd64.zip: OK</code></pre>
 <h1 id="fichier">1Fichier</h1>
-<p>This is a backend for the <a href="https://1fichier.com">1fichier</a> cloud storage service. Note that a Premium subscription is required to use the API.</p>
+<p>This is a backend for the <a href="https://1fichier.com">1fichier</a>
+cloud storage service. Note that a Premium subscription is required to
+use the API.</p>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
 <h2 id="configuration">Configuration</h2>
-<p>The initial setup for 1Fichier involves getting the API key from the website which you need to do in your browser.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>The initial setup for 1Fichier involves getting the API key from the
+website which you need to do in your browser.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -14038,13 +22956,21 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to a 1Fichier directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes">Modification times and hashes</h3>
-<p>1Fichier does not support modification times. It supports the Whirlpool hash algorithm.</p>
+<h3 id="modification-times-and-hashes">Modification times and
+hashes</h3>
+<p>1Fichier does not support modification times. It supports the
+Whirlpool hash algorithm.</p>
 <h3 id="duplicated-files">Duplicated files</h3>
-<p>1Fichier can have two files with exactly the same name and path (unlike a normal file system).</p>
-<p>Duplicated files cause problems with the syncing and you will see messages in the log about duplicates.</p>
-<h3 id="restricted-filename-characters">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>1Fichier can have two files with exactly the same name and path
+(unlike a normal file system).</p>
+<p>Duplicated files cause problems with the syncing and you will see
+messages in the log about duplicates.</p>
+<h3 id="restricted-filename-characters">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -14091,7 +23017,9 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not start or end with the following characters. These only get replaced if they are the first or last character in the name:</p>
+<p>File names can also not start or end with the following characters.
+These only get replaced if they are the first or last character in the
+name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -14108,7 +23036,9 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="standard-options">Standard options</h3>
 <p>Here are the Standard options specific to fichier (1Fichier).</p>
 <h4 id="fichier-api-key">--fichier-api-key</h4>
@@ -14132,8 +23062,11 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="fichier-file-password">--fichier-file-password</h4>
-<p>If you want to download a shared file that is password protected, add this parameter.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>If you want to download a shared file that is password protected, add
+this parameter.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: file_password</li>
@@ -14142,8 +23075,11 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="fichier-folder-password">--fichier-folder-password</h4>
-<p>If you want to list the files in a shared folder that is password protected, add this parameter.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>If you want to list the files in a shared folder that is password
+protected, add this parameter.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: folder_password</li>
@@ -14162,13 +23098,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="fichier-encoding">--fichier-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_FICHIER_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,SingleQuote,BackQuote,Dollar,BackSlash,Del,Ctl,LeftSpace,RightSpace,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="fichier-description">--fichier-description</h4>
 <p>Description of the remote.</p>
@@ -14180,17 +23118,41 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-5">Limitations</h2>
-<p><code>rclone about</code> is not supported by the 1Fichier backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the 1Fichier backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="alias">Alias</h1>
-<p>The <code>alias</code> remote provides a new name for another remote.</p>
-<p>Paths may be as deep as required or a local path, e.g. <code>remote:directory/subdirectory</code> or <code>/directory/subdirectory</code>.</p>
-<p>During the initial setup with <code>rclone config</code> you will specify the target remote. The target remote can either be a local path or another remote.</p>
-<p>Subfolders can be used in target remote. Assume an alias remote named <code>backup</code> with the target <code>mydrive:private/backup</code>. Invoking <code>rclone mkdir backup:desktop</code> is exactly the same as invoking <code>rclone mkdir mydrive:private/backup/desktop</code>.</p>
-<p>There will be no special handling of paths containing <code>..</code> segments. Invoking <code>rclone mkdir backup:../desktop</code> is exactly the same as invoking <code>rclone mkdir mydrive:private/backup/../desktop</code>. The empty path is not allowed as a remote. To alias the current directory use <code>.</code> instead.</p>
-<p>The target remote can also be a <a href="https://rclone.org/docs/#connection-strings">connection string</a>. This can be used to modify the config of a remote for different uses, e.g. the alias <code>myDriveTrash</code> with the target remote <code>myDrive,trashed_only:</code> can be used to only show the trashed files in <code>myDrive</code>.</p>
+<p>The <code>alias</code> remote provides a new name for another
+remote.</p>
+<p>Paths may be as deep as required or a local path, e.g.
+<code>remote:directory/subdirectory</code> or
+<code>/directory/subdirectory</code>.</p>
+<p>During the initial setup with <code>rclone config</code> you will
+specify the target remote. The target remote can either be a local path
+or another remote.</p>
+<p>Subfolders can be used in target remote. Assume an alias remote named
+<code>backup</code> with the target <code>mydrive:private/backup</code>.
+Invoking <code>rclone mkdir backup:desktop</code> is exactly the same as
+invoking <code>rclone mkdir mydrive:private/backup/desktop</code>.</p>
+<p>There will be no special handling of paths containing <code>..</code>
+segments. Invoking <code>rclone mkdir backup:../desktop</code> is
+exactly the same as invoking
+<code>rclone mkdir mydrive:private/backup/../desktop</code>. The empty
+path is not allowed as a remote. To alias the current directory use
+<code>.</code> instead.</p>
+<p>The target remote can also be a <a
+href="https://rclone.org/docs/#connection-strings">connection
+string</a>. This can be used to modify the config of a remote for
+different uses, e.g. the alias <code>myDriveTrash</code> with the target
+remote <code>myDrive,trashed_only:</code> can be used to only show the
+trashed files in <code>myDrive</code>.</p>
 <h2 id="configuration-1">Configuration</h2>
-<p>Here is an example of how to make an alias called <code>remote</code> for local folder. First run:</p>
+<p>Here is an example of how to make an alias called <code>remote</code>
+for local folder. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -14241,10 +23203,12 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <p>Copy another local directory to the alias directory called source</p>
 <pre><code>rclone copy /home/source remote:source</code></pre>
 <h3 id="standard-options-1">Standard options</h3>
-<p>Here are the Standard options specific to alias (Alias for an existing remote).</p>
+<p>Here are the Standard options specific to alias (Alias for an
+existing remote).</p>
 <h4 id="alias-remote">--alias-remote</h4>
 <p>Remote or path to alias.</p>
-<p>Can be "myremote:path/to/dir", "myremote:bucket", "myremote:" or "/local/path".</p>
+<p>Can be "myremote:path/to/dir", "myremote:bucket", "myremote:" or
+"/local/path".</p>
 <p>Properties:</p>
 <ul>
 <li>Config: remote</li>
@@ -14253,7 +23217,8 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <li>Required: true</li>
 </ul>
 <h3 id="advanced-options-1">Advanced options</h3>
-<p>Here are the Advanced options specific to alias (Alias for an existing remote).</p>
+<p>Here are the Advanced options specific to alias (Alias for an
+existing remote).</p>
 <h4 id="alias-description">--alias-description</h4>
 <p>Description of the remote.</p>
 <p>Properties:</p>
@@ -14297,18 +23262,24 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <li>Tencent Cloud Object Storage (COS)</li>
 <li>Wasabi</li>
 </ul>
-<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
-<p>Once you have made a remote (see the provider specific section above) you can use it like this:</p>
+<p>Paths are specified as <code>remote:bucket</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
+<p>Once you have made a remote (see the provider specific section above)
+you can use it like this:</p>
 <p>See all buckets</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>Make a new bucket</p>
 <pre><code>rclone mkdir remote:bucket</code></pre>
 <p>List the contents of a bucket</p>
 <pre><code>rclone ls remote:bucket</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote bucket, deleting any excess files in the bucket.</p>
+<p>Sync <code>/home/local/directory</code> to the remote bucket,
+deleting any excess files in the bucket.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:bucket</code></pre>
 <h2 id="configuration-2">Configuration</h2>
-<p>Here is an example of making an s3 configuration for the AWS S3 provider. Most applies to the other providers as well, any differences are described <a href="#providers">below</a>.</p>
+<p>Here is an example of making an s3 configuration for the AWS S3
+provider. Most applies to the other providers as well, any differences
+are described <a href="#providers">below</a>.</p>
 <p>First run</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
@@ -14506,29 +23477,63 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt;</code></pre>
-<h3 id="modification-times-and-hashes-1">Modification times and hashes</h3>
+<h3 id="modification-times-and-hashes-1">Modification times and
+hashes</h3>
 <h4 id="modification-times-1">Modification times</h4>
-<p>The modified time is stored as metadata on the object as <code>X-Amz-Meta-Mtime</code> as floating point since the epoch, accurate to 1 ns.</p>
-<p>If the modification time needs to be updated rclone will attempt to perform a server side copy to update the modification if the object can be copied in a single part. In the case the object is larger than 5Gb or is in Glacier or Glacier Deep Archive storage the object will be uploaded rather than copied.</p>
-<p>Note that reading this from the object takes an additional <code>HEAD</code> request as the metadata isn't returned in object listings.</p>
+<p>The modified time is stored as metadata on the object as
+<code>X-Amz-Meta-Mtime</code> as floating point since the epoch,
+accurate to 1 ns.</p>
+<p>If the modification time needs to be updated rclone will attempt to
+perform a server side copy to update the modification if the object can
+be copied in a single part. In the case the object is larger than 5Gb or
+is in Glacier or Glacier Deep Archive storage the object will be
+uploaded rather than copied.</p>
+<p>Note that reading this from the object takes an additional
+<code>HEAD</code> request as the metadata isn't returned in object
+listings.</p>
 <h4 id="hashes">Hashes</h4>
-<p>For small objects which weren't uploaded as multipart uploads (objects sized below <code>--s3-upload-cutoff</code> if uploaded with rclone) rclone uses the <code>ETag:</code> header as an MD5 checksum.</p>
-<p>However for objects which were uploaded as multipart uploads or with server side encryption (SSE-AWS or SSE-C) the <code>ETag</code> header is no longer the MD5 sum of the data, so rclone adds an additional piece of metadata <code>X-Amz-Meta-Md5chksum</code> which is a base64 encoded MD5 hash (in the same format as is required for <code>Content-MD5</code>). You can use base64 -d and hexdump to check this value manually:</p>
+<p>For small objects which weren't uploaded as multipart uploads
+(objects sized below <code>--s3-upload-cutoff</code> if uploaded with
+rclone) rclone uses the <code>ETag:</code> header as an MD5
+checksum.</p>
+<p>However for objects which were uploaded as multipart uploads or with
+server side encryption (SSE-AWS or SSE-C) the <code>ETag</code> header
+is no longer the MD5 sum of the data, so rclone adds an additional piece
+of metadata <code>X-Amz-Meta-Md5chksum</code> which is a base64 encoded
+MD5 hash (in the same format as is required for
+<code>Content-MD5</code>). You can use base64 -d and hexdump to check
+this value manually:</p>
 <pre><code>echo &#39;VWTGdNx3LyXQDfA0e2Edxw==&#39; | base64 -d | hexdump</code></pre>
-<p>or you can use <code>rclone check</code> to verify the hashes are OK.</p>
-<p>For large objects, calculating this hash can take some time so the addition of this hash can be disabled with <code>--s3-disable-checksum</code>. This will mean that these objects do not have an MD5 checksum.</p>
-<p>Note that reading this from the object takes an additional <code>HEAD</code> request as the metadata isn't returned in object listings.</p>
+<p>or you can use <code>rclone check</code> to verify the hashes are
+OK.</p>
+<p>For large objects, calculating this hash can take some time so the
+addition of this hash can be disabled with
+<code>--s3-disable-checksum</code>. This will mean that these objects do
+not have an MD5 checksum.</p>
+<p>Note that reading this from the object takes an additional
+<code>HEAD</code> request as the metadata isn't returned in object
+listings.</p>
 <h3 id="reducing-costs">Reducing costs</h3>
-<h4 id="avoiding-head-requests-to-read-the-modification-time">Avoiding HEAD requests to read the modification time</h4>
-<p>By default, rclone will use the modification time of objects stored in S3 for syncing. This is stored in object metadata which unfortunately takes an extra HEAD request to read which can be expensive (in time and money).</p>
-<p>The modification time is used by default for all operations that require checking the time a file was last updated. It allows rclone to treat the remote more like a true filesystem, but it is inefficient on S3 because it requires an extra API call to retrieve the metadata.</p>
-<p>The extra API calls can be avoided when syncing (using <code>rclone sync</code> or <code>rclone copy</code>) in a few different ways, each with its own tradeoffs.</p>
+<h4 id="avoiding-head-requests-to-read-the-modification-time">Avoiding
+HEAD requests to read the modification time</h4>
+<p>By default, rclone will use the modification time of objects stored
+in S3 for syncing. This is stored in object metadata which unfortunately
+takes an extra HEAD request to read which can be expensive (in time and
+money).</p>
+<p>The modification time is used by default for all operations that
+require checking the time a file was last updated. It allows rclone to
+treat the remote more like a true filesystem, but it is inefficient on
+S3 because it requires an extra API call to retrieve the metadata.</p>
+<p>The extra API calls can be avoided when syncing (using
+<code>rclone sync</code> or <code>rclone copy</code>) in a few different
+ways, each with its own tradeoffs.</p>
 <ul>
 <li><code>--size-only</code>
 <ul>
 <li>Only checks the size of files.</li>
 <li>Uses no extra transactions.</li>
-<li>If the file doesn't change size then rclone won't detect it has changed.</li>
+<li>If the file doesn't change size then rclone won't detect it has
+changed.</li>
 <li><code>rclone sync --size-only /path/to/source s3:bucket</code></li>
 </ul></li>
 <li><code>--checksum</code>
@@ -14536,55 +23541,120 @@ y/e/d&gt;</code></pre>
 <li>Checks the size and MD5 checksum of files.</li>
 <li>Uses no extra transactions.</li>
 <li>The most accurate detection of changes possible.</li>
-<li>Will cause the source to read an MD5 checksum which, if it is a local disk, will cause lots of disk activity.</li>
-<li>If the source and destination are both S3 this is the <strong>recommended</strong> flag to use for maximum efficiency.</li>
+<li>Will cause the source to read an MD5 checksum which, if it is a
+local disk, will cause lots of disk activity.</li>
+<li>If the source and destination are both S3 this is the
+<strong>recommended</strong> flag to use for maximum efficiency.</li>
 <li><code>rclone sync --checksum /path/to/source s3:bucket</code></li>
 </ul></li>
 <li><code>--update --use-server-modtime</code>
 <ul>
 <li>Uses no extra transactions.</li>
 <li>Modification time becomes the time the object was uploaded.</li>
-<li>For many operations this is sufficient to determine if it needs uploading.</li>
-<li>Using <code>--update</code> along with <code>--use-server-modtime</code>, avoids the extra API call and uploads files whose local modification time is newer than the time it was last uploaded.</li>
-<li>Files created with timestamps in the past will be missed by the sync.</li>
+<li>For many operations this is sufficient to determine if it needs
+uploading.</li>
+<li>Using <code>--update</code> along with
+<code>--use-server-modtime</code>, avoids the extra API call and uploads
+files whose local modification time is newer than the time it was last
+uploaded.</li>
+<li>Files created with timestamps in the past will be missed by the
+sync.</li>
 <li><code>rclone sync --update --use-server-modtime /path/to/source s3:bucket</code></li>
 </ul></li>
 </ul>
-<p>These flags can and should be used in combination with <code>--fast-list</code> - see below.</p>
-<p>If using <code>rclone mount</code> or any command using the VFS (eg <code>rclone serve</code>) commands then you might want to consider using the VFS flag <code>--no-modtime</code> which will stop rclone reading the modification time for every object. You could also use <code>--use-server-modtime</code> if you are happy with the modification times of the objects being the time of upload.</p>
-<h4 id="avoiding-get-requests-to-read-directory-listings">Avoiding GET requests to read directory listings</h4>
-<p>Rclone's default directory traversal is to process each directory individually. This takes one API call per directory. Using the <code>--fast-list</code> flag will read all info about the objects into memory first using a smaller number of API calls (one per 1000 objects). See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
+<p>These flags can and should be used in combination with
+<code>--fast-list</code> - see below.</p>
+<p>If using <code>rclone mount</code> or any command using the VFS (eg
+<code>rclone serve</code>) commands then you might want to consider
+using the VFS flag <code>--no-modtime</code> which will stop rclone
+reading the modification time for every object. You could also use
+<code>--use-server-modtime</code> if you are happy with the modification
+times of the objects being the time of upload.</p>
+<h4 id="avoiding-get-requests-to-read-directory-listings">Avoiding GET
+requests to read directory listings</h4>
+<p>Rclone's default directory traversal is to process each directory
+individually. This takes one API call per directory. Using the
+<code>--fast-list</code> flag will read all info about the objects into
+memory first using a smaller number of API calls (one per 1000 objects).
+See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for
+more details.</p>
 <pre><code>rclone sync --fast-list --checksum /path/to/source s3:bucket</code></pre>
-<p><code>--fast-list</code> trades off API transactions for memory use. As a rough guide rclone uses 1k of memory per object stored, so using <code>--fast-list</code> on a sync of a million objects will use roughly 1 GiB of RAM.</p>
-<p>If you are only copying a small number of files into a big repository then using <code>--no-traverse</code> is a good idea. This finds objects directly instead of through directory listings. You can do a "top-up" sync very cheaply by using <code>--max-age</code> and <code>--no-traverse</code> to copy only recent files, eg</p>
+<p><code>--fast-list</code> trades off API transactions for memory use.
+As a rough guide rclone uses 1k of memory per object stored, so using
+<code>--fast-list</code> on a sync of a million objects will use roughly
+1 GiB of RAM.</p>
+<p>If you are only copying a small number of files into a big repository
+then using <code>--no-traverse</code> is a good idea. This finds objects
+directly instead of through directory listings. You can do a "top-up"
+sync very cheaply by using <code>--max-age</code> and
+<code>--no-traverse</code> to copy only recent files, eg</p>
 <pre><code>rclone copy --max-age 24h --no-traverse /path/to/source s3:bucket</code></pre>
 <p>You'd then do a full <code>rclone sync</code> less often.</p>
-<p>Note that <code>--fast-list</code> isn't required in the top-up sync.</p>
-<h4 id="avoiding-head-requests-after-put">Avoiding HEAD requests after PUT</h4>
-<p>By default, rclone will HEAD every object it uploads. It does this to check the object got uploaded correctly.</p>
-<p>You can disable this with the <a href="#s3-no-head">--s3-no-head</a> option - see there for more details.</p>
-<p>Setting this flag increases the chance for undetected upload failures.</p>
+<p>Note that <code>--fast-list</code> isn't required in the top-up
+sync.</p>
+<h4 id="avoiding-head-requests-after-put">Avoiding HEAD requests after
+PUT</h4>
+<p>By default, rclone will HEAD every object it uploads. It does this to
+check the object got uploaded correctly.</p>
+<p>You can disable this with the <a href="#s3-no-head">--s3-no-head</a>
+option - see there for more details.</p>
+<p>Setting this flag increases the chance for undetected upload
+failures.</p>
 <h3 id="increasing-performance">Increasing performance</h3>
 <h4 id="using-server-side-copy">Using server-side copy</h4>
-<p>If you are copying objects between S3 buckets in the same region, you should use server-side copy. This is much faster than downloading and re-uploading the objects, as no data is transferred.</p>
-<p>For rclone to use server-side copy, you must use the same remote for the source and destination.</p>
+<p>If you are copying objects between S3 buckets in the same region, you
+should use server-side copy. This is much faster than downloading and
+re-uploading the objects, as no data is transferred.</p>
+<p>For rclone to use server-side copy, you must use the same remote for
+the source and destination.</p>
 <pre><code>rclone copy s3:source-bucket s3:destination-bucket</code></pre>
-<p>When using server-side copy, the performance is limited by the rate at which rclone issues API requests to S3. See below for how to increase the number of API requests rclone makes.</p>
-<h4 id="increasing-the-rate-of-api-requests">Increasing the rate of API requests</h4>
-<p>You can increase the rate of API requests to S3 by increasing the parallelism using <code>--transfers</code> and <code>--checkers</code> options.</p>
-<p>Rclone uses a very conservative defaults for these settings, as not all providers support high rates of requests. Depending on your provider, you can increase significantly the number of transfers and checkers.</p>
-<p>For example, with AWS S3, if you can increase the number of checkers to values like 200. If you are doing a server-side copy, you can also increase the number of transfers to 200.</p>
+<p>When using server-side copy, the performance is limited by the rate
+at which rclone issues API requests to S3. See below for how to increase
+the number of API requests rclone makes.</p>
+<h4 id="increasing-the-rate-of-api-requests">Increasing the rate of API
+requests</h4>
+<p>You can increase the rate of API requests to S3 by increasing the
+parallelism using <code>--transfers</code> and <code>--checkers</code>
+options.</p>
+<p>Rclone uses a very conservative defaults for these settings, as not
+all providers support high rates of requests. Depending on your
+provider, you can increase significantly the number of transfers and
+checkers.</p>
+<p>For example, with AWS S3, if you can increase the number of checkers
+to values like 200. If you are doing a server-side copy, you can also
+increase the number of transfers to 200.</p>
 <pre><code>rclone sync --transfers 200 --checkers 200 --checksum s3:source-bucket s3:destination-bucket</code></pre>
-<p>You will need to experiment with these values to find the optimal settings for your setup.</p>
+<p>You will need to experiment with these values to find the optimal
+settings for your setup.</p>
 <h3 id="versions">Versions</h3>
-<p>When bucket versioning is enabled (this can be done with rclone with the <a href="#versioning"><code>rclone backend versioning</code></a> command) when rclone uploads a new version of a file it creates a <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html">new version of it</a> Likewise when you delete a file, the old version will be marked hidden and still be available.</p>
-<p>Old versions of files, where available, are visible using the <a href="#s3-versions"><code>--s3-versions</code></a> flag.</p>
-<p>It is also possible to view a bucket as it was at a certain point in time, using the <a href="#s3-version-at"><code>--s3-version-at</code></a> flag. This will show the file versions as they were at that time, showing files that have been deleted afterwards, and hiding files that were created since.</p>
-<p>If you wish to remove all the old versions then you can use the <a href="#cleanup-hidden"><code>rclone backend cleanup-hidden remote:bucket</code></a> command which will delete all the old hidden versions of files, leaving the current ones intact. You can also supply a path and only old versions under that path will be deleted, e.g. <code>rclone backend cleanup-hidden remote:bucket/path/to/stuff</code>.</p>
-<p>When you <code>purge</code> a bucket, the current and the old versions will be deleted then the bucket will be deleted.</p>
-<p>However <code>delete</code> will cause the current versions of the files to become hidden old versions.</p>
-<p>Here is a session showing the listing and retrieval of an old version followed by a <code>cleanup</code> of the old versions.</p>
-<p>Show current version and all the versions with <code>--s3-versions</code> flag.</p>
+<p>When bucket versioning is enabled (this can be done with rclone with
+the <a href="#versioning"><code>rclone backend versioning</code></a>
+command) when rclone uploads a new version of a file it creates a <a
+href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html">new
+version of it</a> Likewise when you delete a file, the old version will
+be marked hidden and still be available.</p>
+<p>Old versions of files, where available, are visible using the <a
+href="#s3-versions"><code>--s3-versions</code></a> flag.</p>
+<p>It is also possible to view a bucket as it was at a certain point in
+time, using the <a
+href="#s3-version-at"><code>--s3-version-at</code></a> flag. This will
+show the file versions as they were at that time, showing files that
+have been deleted afterwards, and hiding files that were created
+since.</p>
+<p>If you wish to remove all the old versions then you can use the <a
+href="#cleanup-hidden"><code>rclone backend cleanup-hidden remote:bucket</code></a>
+command which will delete all the old hidden versions of files, leaving
+the current ones intact. You can also supply a path and only old
+versions under that path will be deleted, e.g.
+<code>rclone backend cleanup-hidden remote:bucket/path/to/stuff</code>.</p>
+<p>When you <code>purge</code> a bucket, the current and the old
+versions will be deleted then the bucket will be deleted.</p>
+<p>However <code>delete</code> will cause the current versions of the
+files to become hidden old versions.</p>
+<p>Here is a session showing the listing and retrieval of an old version
+followed by a <code>cleanup</code> of the old versions.</p>
+<p>Show current version and all the versions with
+<code>--s3-versions</code> flag.</p>
 <pre><code>$ rclone -q ls s3:cleanup-test
         9 one.txt
 
@@ -14607,17 +23677,33 @@ $ rclone -q ls s3:cleanup-test
 $ rclone -q --s3-versions ls s3:cleanup-test
         9 one.txt</code></pre>
 <h4 id="versions-naming-caveat">Versions naming caveat</h4>
-<p>When using <code>--s3-versions</code> flag rclone is relying on the file name to work out whether the objects are versions or not. Versions' names are created by inserting timestamp between file name and its extension.</p>
+<p>When using <code>--s3-versions</code> flag rclone is relying on the
+file name to work out whether the objects are versions or not. Versions'
+names are created by inserting timestamp between file name and its
+extension.</p>
 <pre><code>        9 file.txt
         8 file-v2023-07-17-161032-000.txt
        16 file-v2023-06-15-141003-000.txt</code></pre>
-<p>If there are real files present with the same names as versions, then behaviour of <code>--s3-versions</code> can be unpredictable.</p>
+<p>If there are real files present with the same names as versions, then
+behaviour of <code>--s3-versions</code> can be unpredictable.</p>
 <h3 id="cleanup-1">Cleanup</h3>
-<p>If you run <code>rclone cleanup s3:bucket</code> then it will remove all pending multipart uploads older than 24 hours. You can use the <code>--interactive</code>/<code>i</code> or <code>--dry-run</code> flag to see exactly what it will do. If you want more control over the expiry date then run <code>rclone backend cleanup s3:bucket -o max-age=1h</code> to expire all uploads older than one hour. You can use <code>rclone backend list-multipart-uploads s3:bucket</code> to see the pending multipart uploads.</p>
-<h3 id="restricted-filename-characters-1">Restricted filename characters</h3>
+<p>If you run <code>rclone cleanup s3:bucket</code> then it will remove
+all pending multipart uploads older than 24 hours. You can use the
+<code>--interactive</code>/<code>i</code> or <code>--dry-run</code> flag
+to see exactly what it will do. If you want more control over the expiry
+date then run
+<code>rclone backend cleanup s3:bucket -o max-age=1h</code> to expire
+all uploads older than one hour. You can use
+<code>rclone backend list-multipart-uploads s3:bucket</code> to see the
+pending multipart uploads.</p>
+<h3 id="restricted-filename-characters-1">Restricted filename
+characters</h3>
 <p>S3 allows any valid UTF-8 string as a key.</p>
-<p>Invalid UTF-8 bytes will be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in XML.</p>
-<p>The following characters are replaced since these are problematic when dealing with the REST API:</p>
+<p>Invalid UTF-8 bytes will be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in XML.</p>
+<p>The following characters are replaced since these are problematic
+when dealing with the REST API:</p>
 <table>
 <thead>
 <tr class="header">
@@ -14639,7 +23725,8 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </tr>
 </tbody>
 </table>
-<p>The encoding will also encode these file names as they don't seem to work with the SDK properly:</p>
+<p>The encoding will also encode these file names as they don't seem to
+work with the SDK properly:</p>
 <table>
 <thead>
 <tr class="header">
@@ -14659,60 +23746,111 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </tbody>
 </table>
 <h3 id="multipart-uploads">Multipart uploads</h3>
-<p>rclone supports multipart uploads with S3 which means that it can upload files bigger than 5 GiB.</p>
-<p>Note that files uploaded <em>both</em> with multipart upload <em>and</em> through crypt remotes do not have MD5 sums.</p>
-<p>rclone switches from single part uploads to multipart uploads at the point specified by <code>--s3-upload-cutoff</code>. This can be a maximum of 5 GiB and a minimum of 0 (ie always upload multipart files).</p>
-<p>The chunk sizes used in the multipart upload are specified by <code>--s3-chunk-size</code> and the number of chunks uploaded concurrently is specified by <code>--s3-upload-concurrency</code>.</p>
-<p>Multipart uploads will use <code>--transfers</code> * <code>--s3-upload-concurrency</code> * <code>--s3-chunk-size</code> extra memory. Single part uploads to not use extra memory.</p>
-<p>Single part transfers can be faster than multipart transfers or slower depending on your latency from S3 - the more latency, the more likely single part transfers will be faster.</p>
-<p>Increasing <code>--s3-upload-concurrency</code> will increase throughput (8 would be a sensible value) and increasing <code>--s3-chunk-size</code> also increases throughput (16M would be sensible). Increasing either of these will use more memory. The default values are high enough to gain most of the possible performance without using too much memory.</p>
+<p>rclone supports multipart uploads with S3 which means that it can
+upload files bigger than 5 GiB.</p>
+<p>Note that files uploaded <em>both</em> with multipart upload
+<em>and</em> through crypt remotes do not have MD5 sums.</p>
+<p>rclone switches from single part uploads to multipart uploads at the
+point specified by <code>--s3-upload-cutoff</code>. This can be a
+maximum of 5 GiB and a minimum of 0 (ie always upload multipart
+files).</p>
+<p>The chunk sizes used in the multipart upload are specified by
+<code>--s3-chunk-size</code> and the number of chunks uploaded
+concurrently is specified by <code>--s3-upload-concurrency</code>.</p>
+<p>Multipart uploads will use <code>--transfers</code> *
+<code>--s3-upload-concurrency</code> * <code>--s3-chunk-size</code>
+extra memory. Single part uploads to not use extra memory.</p>
+<p>Single part transfers can be faster than multipart transfers or
+slower depending on your latency from S3 - the more latency, the more
+likely single part transfers will be faster.</p>
+<p>Increasing <code>--s3-upload-concurrency</code> will increase
+throughput (8 would be a sensible value) and increasing
+<code>--s3-chunk-size</code> also increases throughput (16M would be
+sensible). Increasing either of these will use more memory. The default
+values are high enough to gain most of the possible performance without
+using too much memory.</p>
 <h3 id="buckets-and-regions">Buckets and Regions</h3>
-<p>With Amazon S3 you can list buckets (<code>rclone lsd</code>) using any region, but you can only access the content of a bucket from the region it was created in. If you attempt to access a bucket from the wrong region, you will get an error, <code>incorrect region, the bucket is not in 'XXX' region</code>.</p>
+<p>With Amazon S3 you can list buckets (<code>rclone lsd</code>) using
+any region, but you can only access the content of a bucket from the
+region it was created in. If you attempt to access a bucket from the
+wrong region, you will get an error,
+<code>incorrect region, the bucket is not in 'XXX' region</code>.</p>
 <h3 id="authentication-5">Authentication</h3>
-<p>There are a number of ways to supply <code>rclone</code> with a set of AWS credentials, with and without using the environment.</p>
+<p>There are a number of ways to supply <code>rclone</code> with a set
+of AWS credentials, with and without using the environment.</p>
 <p>The different authentication methods are tried in this order:</p>
 <ul>
-<li>Directly in the rclone configuration file (<code>env_auth = false</code> in the config file):
+<li>Directly in the rclone configuration file
+(<code>env_auth = false</code> in the config file):
 <ul>
-<li><code>access_key_id</code> and <code>secret_access_key</code> are required.</li>
-<li><code>session_token</code> can be optionally set when using AWS STS.</li>
+<li><code>access_key_id</code> and <code>secret_access_key</code> are
+required.</li>
+<li><code>session_token</code> can be optionally set when using AWS
+STS.</li>
 </ul></li>
-<li>Runtime configuration (<code>env_auth = true</code> in the config file):
+<li>Runtime configuration (<code>env_auth = true</code> in the config
+file):
 <ul>
-<li>Export the following environment variables before running <code>rclone</code>:
+<li>Export the following environment variables before running
+<code>rclone</code>:
 <ul>
-<li>Access Key ID: <code>AWS_ACCESS_KEY_ID</code> or <code>AWS_ACCESS_KEY</code></li>
-<li>Secret Access Key: <code>AWS_SECRET_ACCESS_KEY</code> or <code>AWS_SECRET_KEY</code></li>
+<li>Access Key ID: <code>AWS_ACCESS_KEY_ID</code> or
+<code>AWS_ACCESS_KEY</code></li>
+<li>Secret Access Key: <code>AWS_SECRET_ACCESS_KEY</code> or
+<code>AWS_SECRET_KEY</code></li>
 <li>Session Token: <code>AWS_SESSION_TOKEN</code> (optional)</li>
 </ul></li>
-<li>Or, use a <a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html">named profile</a>:
+<li>Or, use a <a
+href="https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html">named
+profile</a>:
 <ul>
 <li>Profile files are standard files used by AWS CLI tools</li>
-<li>By default it will use the profile in your home directory (e.g. <code>~/.aws/credentials</code> on unix based systems) file and the "default" profile, to change set these environment variables or config keys:
+<li>By default it will use the profile in your home directory (e.g.
+<code>~/.aws/credentials</code> on unix based systems) file and the
+"default" profile, to change set these environment variables or config
+keys:
 <ul>
-<li><code>AWS_SHARED_CREDENTIALS_FILE</code> to control which file or the <code>shared_credentials_file</code> config key.</li>
-<li><code>AWS_PROFILE</code> to control which profile to use or the <code>profile</code> config key.</li>
+<li><code>AWS_SHARED_CREDENTIALS_FILE</code> to control which file or
+the <code>shared_credentials_file</code> config key.</li>
+<li><code>AWS_PROFILE</code> to control which profile to use or the
+<code>profile</code> config key.</li>
 </ul></li>
 </ul></li>
-<li>Or, run <code>rclone</code> in an ECS task with an IAM role (AWS only).</li>
-<li>Or, run <code>rclone</code> on an EC2 instance with an IAM role (AWS only).</li>
-<li>Or, run <code>rclone</code> in an EKS pod with an IAM role that is associated with a service account (AWS only).</li>
-<li>Or, use <a href="https://docs.aws.amazon.com/sdkref/latest/guide/feature-process-credentials.html">process credentials</a> to read config from an external program.</li>
+<li>Or, run <code>rclone</code> in an ECS task with an IAM role (AWS
+only).</li>
+<li>Or, run <code>rclone</code> on an EC2 instance with an IAM role (AWS
+only).</li>
+<li>Or, run <code>rclone</code> in an EKS pod with an IAM role that is
+associated with a service account (AWS only).</li>
+<li>Or, use <a
+href="https://docs.aws.amazon.com/sdkref/latest/guide/feature-process-credentials.html">process
+credentials</a> to read config from an external program.</li>
 </ul></li>
 </ul>
-<p>With <code>env_auth = true</code> rclone (which uses the SDK for Go v2) should support <a href="https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html">all authentication methods</a> that the <code>aws</code> CLI tool does and the other AWS SDKs.</p>
-<p>If none of these option actually end up providing <code>rclone</code> with AWS credentials then S3 interaction will be non-authenticated (see the <a href="#anonymous-access">anonymous access</a> section for more info).</p>
+<p>With <code>env_auth = true</code> rclone (which uses the SDK for Go
+v2) should support <a
+href="https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html">all
+authentication methods</a> that the <code>aws</code> CLI tool does and
+the other AWS SDKs.</p>
+<p>If none of these option actually end up providing <code>rclone</code>
+with AWS credentials then S3 interaction will be non-authenticated (see
+the <a href="#anonymous-access">anonymous access</a> section for more
+info).</p>
 <h3 id="s3-permissions">S3 Permissions</h3>
-<p>When using the <code>sync</code> subcommand of <code>rclone</code> the following minimum permissions are required to be available on the bucket being written to:</p>
+<p>When using the <code>sync</code> subcommand of <code>rclone</code>
+the following minimum permissions are required to be available on the
+bucket being written to:</p>
 <ul>
 <li><code>ListBucket</code></li>
 <li><code>DeleteObject</code></li>
 <li><code>GetObject</code></li>
 <li><code>PutObject</code></li>
 <li><code>PutObjectACL</code></li>
-<li><code>CreateBucket</code> (unless using <a href="#s3-no-check-bucket">s3-no-check-bucket</a>)</li>
+<li><code>CreateBucket</code> (unless using <a
+href="#s3-no-check-bucket">s3-no-check-bucket</a>)</li>
 </ul>
-<p>When using the <code>lsd</code> subcommand, the <code>ListAllMyBuckets</code> permission is required.</p>
+<p>When using the <code>lsd</code> subcommand, the
+<code>ListAllMyBuckets</code> permission is required.</p>
 <p>Example policy:</p>
 <pre><code>{
     &quot;Version&quot;: &quot;2012-10-17&quot;,
@@ -14743,26 +23881,60 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 }</code></pre>
 <p>Notes on above:</p>
 <ol type="1">
-<li>This is a policy that can be used when creating bucket. It assumes that <code>USER_NAME</code> has been created.</li>
-<li>The Resource entry must include both resource ARNs, as one implies the bucket and the other implies the bucket's objects.</li>
-<li>When using <a href="#s3-no-check-bucket">s3-no-check-bucket</a> and the bucket already exsits, the <code>"arn:aws:s3:::BUCKET_NAME"</code> doesn't have to be included.</li>
+<li>This is a policy that can be used when creating bucket. It assumes
+that <code>USER_NAME</code> has been created.</li>
+<li>The Resource entry must include both resource ARNs, as one implies
+the bucket and the other implies the bucket's objects.</li>
+<li>When using <a href="#s3-no-check-bucket">s3-no-check-bucket</a> and
+the bucket already exsits, the <code>"arn:aws:s3:::BUCKET_NAME"</code>
+doesn't have to be included.</li>
 </ol>
-<p>For reference, <a href="https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b">here's an Ansible script</a> that will generate one or more buckets that will work with <code>rclone sync</code>.</p>
+<p>For reference, <a
+href="https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b">here's
+an Ansible script</a> that will generate one or more buckets that will
+work with <code>rclone sync</code>.</p>
 <h3 id="key-management-system-kms">Key Management System (KMS)</h3>
-<p>If you are using server-side encryption with KMS then you must make sure rclone is configured with <code>server_side_encryption = aws:kms</code> otherwise you will find you can't transfer small objects - these will create checksum errors.</p>
-<h3 id="glacier-and-glacier-deep-archive">Glacier and Glacier Deep Archive</h3>
-<p>You can upload objects using the glacier storage class or transition them to glacier using a <a href="http://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-lifecycle.html">lifecycle policy</a>. The bucket can still be synced or copied into normally, but if rclone tries to access data from the glacier storage class you will see an error like below.</p>
+<p>If you are using server-side encryption with KMS then you must make
+sure rclone is configured with
+<code>server_side_encryption = aws:kms</code> otherwise you will find
+you can't transfer small objects - these will create checksum
+errors.</p>
+<h3 id="glacier-and-glacier-deep-archive">Glacier and Glacier Deep
+Archive</h3>
+<p>You can upload objects using the glacier storage class or transition
+them to glacier using a <a
+href="http://docs.aws.amazon.com/AmazonS3/latest/user-guide/create-lifecycle.html">lifecycle
+policy</a>. The bucket can still be synced or copied into normally, but
+if rclone tries to access data from the glacier storage class you will
+see an error like below.</p>
 <pre><code>2017/09/11 19:07:43 Failed to sync: failed to open source object: Object in GLACIER, restore first: path/to/file</code></pre>
-<p>In this case you need to <a href="http://docs.aws.amazon.com/AmazonS3/latest/user-guide/restore-archived-objects.html">restore</a> the object(s) in question before using rclone.</p>
-<p>Note that rclone only speaks the S3 API it does not speak the Glacier Vault API, so rclone cannot directly access Glacier Vaults.</p>
-<h3 id="object-lock-enabled-s3-bucket">Object-lock enabled S3 bucket</h3>
-<p>According to AWS's <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-overview.html#object-lock-permission">documentation on S3 Object Lock</a>:</p>
+<p>In this case you need to <a
+href="http://docs.aws.amazon.com/AmazonS3/latest/user-guide/restore-archived-objects.html">restore</a>
+the object(s) in question before using rclone.</p>
+<p>Note that rclone only speaks the S3 API it does not speak the Glacier
+Vault API, so rclone cannot directly access Glacier Vaults.</p>
+<h3 id="object-lock-enabled-s3-bucket">Object-lock enabled S3
+bucket</h3>
+<p>According to AWS's <a
+href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock-overview.html#object-lock-permission">documentation
+on S3 Object Lock</a>:</p>
 <blockquote>
-<p>If you configure a default retention period on a bucket, requests to upload objects in such a bucket must include the Content-MD5 header.</p>
+<p>If you configure a default retention period on a bucket, requests to
+upload objects in such a bucket must include the Content-MD5 header.</p>
 </blockquote>
-<p>As mentioned in the <a href="#modification-times-and-hashes">Modification times and hashes</a> section, small files that are not uploaded as multipart, use a different tag, causing the upload to fail. A simple solution is to set the <code>--s3-upload-cutoff 0</code> and force all the files to be uploaded as multipart.</p>
+<p>As mentioned in the <a
+href="#modification-times-and-hashes">Modification times and hashes</a>
+section, small files that are not uploaded as multipart, use a different
+tag, causing the upload to fail. A simple solution is to set the
+<code>--s3-upload-cutoff 0</code> and force all the files to be uploaded
+as multipart.</p>
 <h3 id="standard-options-2">Standard options</h3>
-<p>Here are the Standard options specific to s3 (Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others).</p>
+<p>Here are the Standard options specific to s3 (Amazon S3 Compliant
+Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile,
+Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive,
+IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease,
+Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj,
+Synology, TencentCOS, Wasabi, Qiniu and others).</p>
 <h4 id="s3-provider">--s3-provider</h4>
 <p>Choose your S3 provider.</p>
 <p>Properties:</p>
@@ -14904,7 +24076,8 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul></li>
 </ul>
 <h4 id="s3-env-auth">--s3-env-auth</h4>
-<p>Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).</p>
+<p>Get AWS credentials from runtime (environment variables or EC2/ECS
+meta data if no env vars).</p>
 <p>Only applies if access_key_id and secret_access_key is blank.</p>
 <p>Properties:</p>
 <ul>
@@ -15090,7 +24263,8 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul>
 <h4 id="s3-endpoint">--s3-endpoint</h4>
 <p>Endpoint for S3 API.</p>
-<p>Leave blank if using AWS to use the default endpoint for the region.</p>
+<p>Leave blank if using AWS to use the default endpoint for the
+region.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: endpoint</li>
@@ -15218,11 +24392,16 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul></li>
 </ul>
 <h4 id="s3-acl">--s3-acl</h4>
-<p>Canned ACL used when creating buckets and storing or copying objects.</p>
-<p>This ACL is used for creating objects and if bucket_acl isn't set, for creating buckets too.</p>
-<p>For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl</p>
-<p>Note that this ACL is applied when server-side copying objects as S3 doesn't copy the ACL from the source but rather writes a fresh one.</p>
-<p>If the acl is an empty string then no X-Amz-Acl: header is added and the default (private) will be used.</p>
+<p>Canned ACL used when creating buckets and storing or copying
+objects.</p>
+<p>This ACL is used for creating objects and if bucket_acl isn't set,
+for creating buckets too.</p>
+<p>For more info visit
+https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl</p>
+<p>Note that this ACL is applied when server-side copying objects as S3
+doesn't copy the ACL from the source but rather writes a fresh one.</p>
+<p>If the acl is an empty string then no X-Amz-Acl: header is added and
+the default (private) will be used.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: acl</li>
@@ -15262,24 +24441,29 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 <ul>
 <li>Object owner gets FULL_CONTROL.</li>
 <li>Bucket owner gets READ access.</li>
-<li>If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.</li>
+<li>If you specify this canned ACL when creating a bucket, Amazon S3
+ignores it.</li>
 </ul></li>
 <li>"bucket-owner-full-control"
 <ul>
-<li>Both the object owner and the bucket owner get FULL_CONTROL over the object.</li>
-<li>If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.</li>
+<li>Both the object owner and the bucket owner get FULL_CONTROL over the
+object.</li>
+<li>If you specify this canned ACL when creating a bucket, Amazon S3
+ignores it.</li>
 </ul></li>
 <li>"private"
 <ul>
 <li>Owner gets FULL_CONTROL.</li>
 <li>No one else has access rights (default).</li>
-<li>This acl is available on IBM Cloud (Infra), IBM Cloud (Storage), On-Premise COS.</li>
+<li>This acl is available on IBM Cloud (Infra), IBM Cloud (Storage),
+On-Premise COS.</li>
 </ul></li>
 <li>"public-read"
 <ul>
 <li>Owner gets FULL_CONTROL.</li>
 <li>The AllUsers group gets READ access.</li>
-<li>This acl is available on IBM Cloud (Infra), IBM Cloud (Storage), On-Premise IBM COS.</li>
+<li>This acl is available on IBM Cloud (Infra), IBM Cloud (Storage),
+On-Premise IBM COS.</li>
 </ul></li>
 <li>"public-read-write"
 <ul>
@@ -15292,12 +24476,14 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 <li>Owner gets FULL_CONTROL.</li>
 <li>The AuthenticatedUsers group gets READ access.</li>
 <li>Not supported on Buckets.</li>
-<li>This acl is available on IBM Cloud (Infra) and On-Premise IBM COS.</li>
+<li>This acl is available on IBM Cloud (Infra) and On-Premise IBM
+COS.</li>
 </ul></li>
 </ul></li>
 </ul>
 <h4 id="s3-server-side-encryption">--s3-server-side-encryption</h4>
-<p>The server-side encryption algorithm used when storing this object in S3.</p>
+<p>The server-side encryption algorithm used when storing this object in
+S3.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: server_side_encryption</li>
@@ -15392,12 +24578,20 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul></li>
 </ul>
 <h3 id="advanced-options-2">Advanced options</h3>
-<p>Here are the Advanced options specific to s3 (Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others).</p>
+<p>Here are the Advanced options specific to s3 (Amazon S3 Compliant
+Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile,
+Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive,
+IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease,
+Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj,
+Synology, TencentCOS, Wasabi, Qiniu and others).</p>
 <h4 id="s3-bucket-acl">--s3-bucket-acl</h4>
 <p>Canned ACL used when creating buckets.</p>
-<p>For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl</p>
-<p>Note that this ACL is applied when only when creating buckets. If it isn't set then "acl" is used instead.</p>
-<p>If the "acl" and "bucket_acl" are empty strings then no X-Amz-Acl: header is added and the default (private) will be used.</p>
+<p>For more info visit
+https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl</p>
+<p>Note that this ACL is applied when only when creating buckets. If it
+isn't set then "acl" is used instead.</p>
+<p>If the "acl" and "bucket_acl" are empty strings then no X-Amz-Acl:
+header is added and the default (private) will be used.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: bucket_acl</li>
@@ -15440,7 +24634,8 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 <li>Default: false</li>
 </ul>
 <h4 id="s3-sse-customer-algorithm">--s3-sse-customer-algorithm</h4>
-<p>If using SSE-C, the server-side encryption algorithm used when storing this object in S3.</p>
+<p>If using SSE-C, the server-side encryption algorithm used when
+storing this object in S3.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sse_customer_algorithm</li>
@@ -15461,7 +24656,8 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul></li>
 </ul>
 <h4 id="s3-sse-customer-key">--s3-sse-customer-key</h4>
-<p>To use SSE-C you may provide the secret encryption key used to encrypt/decrypt your data.</p>
+<p>To use SSE-C you may provide the secret encryption key used to
+encrypt/decrypt your data.</p>
 <p>Alternatively you can provide --sse-customer-key-base64.</p>
 <p>Properties:</p>
 <ul>
@@ -15479,7 +24675,8 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul></li>
 </ul>
 <h4 id="s3-sse-customer-key-base64">--s3-sse-customer-key-base64</h4>
-<p>If using SSE-C you must provide the secret encryption key encoded in base64 format to encrypt/decrypt your data.</p>
+<p>If using SSE-C you must provide the secret encryption key encoded in
+base64 format to encrypt/decrypt your data.</p>
 <p>Alternatively you can provide --sse-customer-key.</p>
 <p>Properties:</p>
 <ul>
@@ -15497,8 +24694,10 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul></li>
 </ul>
 <h4 id="s3-sse-customer-key-md5">--s3-sse-customer-key-md5</h4>
-<p>If using SSE-C you may provide the secret encryption key MD5 checksum (optional).</p>
-<p>If you leave it blank, this is calculated automatically from the sse_customer_key provided.</p>
+<p>If using SSE-C you may provide the secret encryption key MD5 checksum
+(optional).</p>
+<p>If you leave it blank, this is calculated automatically from the
+sse_customer_key provided.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sse_customer_key_md5</li>
@@ -15516,7 +24715,8 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul>
 <h4 id="s3-upload-cutoff">--s3-upload-cutoff</h4>
 <p>Cutoff for switching to chunked upload.</p>
-<p>Any files larger than this will be uploaded in chunks of chunk_size. The minimum is 0 and the maximum is 5 GiB.</p>
+<p>Any files larger than this will be uploaded in chunks of chunk_size.
+The minimum is 0 and the maximum is 5 GiB.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_cutoff</li>
@@ -15526,12 +24726,27 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul>
 <h4 id="s3-chunk-size">--s3-chunk-size</h4>
 <p>Chunk size to use for uploading.</p>
-<p>When uploading files larger than upload_cutoff or files with unknown size (e.g. from "rclone rcat" or uploaded with "rclone mount" or google photos or google docs) they will be uploaded as multipart uploads using this chunk size.</p>
-<p>Note that "--s3-upload-concurrency" chunks of this size are buffered in memory per transfer.</p>
-<p>If you are transferring large files over high-speed links and you have enough memory, then increasing this will speed up the transfers.</p>
-<p>Rclone will automatically increase the chunk size when uploading a large file of known size to stay below the 10,000 chunks limit.</p>
-<p>Files of unknown size are uploaded with the configured chunk_size. Since the default chunk size is 5 MiB and there can be at most 10,000 chunks, this means that by default the maximum size of a file you can stream upload is 48 GiB. If you wish to stream upload larger files then you will need to increase chunk_size.</p>
-<p>Increasing the chunk size decreases the accuracy of the progress statistics displayed with "-P" flag. Rclone treats chunk as sent when it's buffered by the AWS SDK, when in fact it may still be uploading. A bigger chunk size means a bigger AWS SDK buffer and progress reporting more deviating from the truth.</p>
+<p>When uploading files larger than upload_cutoff or files with unknown
+size (e.g. from "rclone rcat" or uploaded with "rclone mount" or google
+photos or google docs) they will be uploaded as multipart uploads using
+this chunk size.</p>
+<p>Note that "--s3-upload-concurrency" chunks of this size are buffered
+in memory per transfer.</p>
+<p>If you are transferring large files over high-speed links and you
+have enough memory, then increasing this will speed up the
+transfers.</p>
+<p>Rclone will automatically increase the chunk size when uploading a
+large file of known size to stay below the 10,000 chunks limit.</p>
+<p>Files of unknown size are uploaded with the configured chunk_size.
+Since the default chunk size is 5 MiB and there can be at most 10,000
+chunks, this means that by default the maximum size of a file you can
+stream upload is 48 GiB. If you wish to stream upload larger files then
+you will need to increase chunk_size.</p>
+<p>Increasing the chunk size decreases the accuracy of the progress
+statistics displayed with "-P" flag. Rclone treats chunk as sent when
+it's buffered by the AWS SDK, when in fact it may still be uploading. A
+bigger chunk size means a bigger AWS SDK buffer and progress reporting
+more deviating from the truth.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -15541,9 +24756,13 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul>
 <h4 id="s3-max-upload-parts">--s3-max-upload-parts</h4>
 <p>Maximum number of parts in a multipart upload.</p>
-<p>This option defines the maximum number of multipart chunks to use when doing a multipart upload.</p>
-<p>This can be useful if a service does not support the AWS S3 specification of 10,000 chunks.</p>
-<p>Rclone will automatically increase the chunk size when uploading a large file of a known size to stay below this number of chunks limit.</p>
+<p>This option defines the maximum number of multipart chunks to use
+when doing a multipart upload.</p>
+<p>This can be useful if a service does not support the AWS S3
+specification of 10,000 chunks.</p>
+<p>Rclone will automatically increase the chunk size when uploading a
+large file of a known size to stay below this number of chunks
+limit.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: max_upload_parts</li>
@@ -15553,7 +24772,8 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul>
 <h4 id="s3-copy-cutoff">--s3-copy-cutoff</h4>
 <p>Cutoff for switching to multipart copy.</p>
-<p>Any files larger than this that need to be server-side copied will be copied in chunks of this size.</p>
+<p>Any files larger than this that need to be server-side copied will be
+copied in chunks of this size.</p>
 <p>The minimum is 0 and the maximum is 5 GiB.</p>
 <p>Properties:</p>
 <ul>
@@ -15564,7 +24784,10 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 </ul>
 <h4 id="s3-disable-checksum">--s3-disable-checksum</h4>
 <p>Don't store MD5 checksum with object metadata.</p>
-<p>Normally rclone will calculate the MD5 checksum of the input before uploading it so it can add it to metadata on the object. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
+<p>Normally rclone will calculate the MD5 checksum of the input before
+uploading it so it can add it to metadata on the object. This is great
+for data integrity checking but can cause long delays for large files to
+start uploading.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_checksum</li>
@@ -15575,7 +24798,9 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 <h4 id="s3-shared-credentials-file">--s3-shared-credentials-file</h4>
 <p>Path to the shared credentials file.</p>
 <p>If env_auth = true then rclone can use a shared credentials file.</p>
-<p>If this variable is empty rclone will look for the "AWS_SHARED_CREDENTIALS_FILE" env variable. If the env value is empty it will default to the current user's home directory.</p>
+<p>If this variable is empty rclone will look for the
+"AWS_SHARED_CREDENTIALS_FILE" env variable. If the env value is empty it
+will default to the current user's home directory.</p>
 <pre><code>Linux/OSX: &quot;$HOME/.aws/credentials&quot;
 Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <p>Properties:</p>
@@ -15587,8 +24812,10 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-profile">--s3-profile</h4>
 <p>Profile to use in the shared credentials file.</p>
-<p>If env_auth = true then rclone can use a shared credentials file. This variable controls which profile is used in that file.</p>
-<p>If empty it will default to the environment variable "AWS_PROFILE" or "default" if that environment variable is also not set.</p>
+<p>If env_auth = true then rclone can use a shared credentials file.
+This variable controls which profile is used in that file.</p>
+<p>If empty it will default to the environment variable "AWS_PROFILE" or
+"default" if that environment variable is also not set.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: profile</li>
@@ -15607,8 +24834,11 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-upload-concurrency">--s3-upload-concurrency</h4>
 <p>Concurrency for multipart uploads and copies.</p>
-<p>This is the number of chunks of the same file that are uploaded concurrently for multipart uploads and copies.</p>
-<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
+<p>This is the number of chunks of the same file that are uploaded
+concurrently for multipart uploads and copies.</p>
+<p>If you are uploading small numbers of large files over high-speed
+links and these uploads do not fully utilize your bandwidth, then
+increasing this may help to speed up the transfers.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_concurrency</li>
@@ -15618,9 +24848,15 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-force-path-style">--s3-force-path-style</h4>
 <p>If true use path style access if false use virtual hosted style.</p>
-<p>If this is true (the default) then rclone will use path style access, if false then rclone will use virtual path style. See <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro">the AWS S3 docs</a> for more info.</p>
-<p>Some providers (e.g. AWS, Aliyun OSS, Netease COS, or Tencent COS) require this set to false - rclone will do this automatically based on the provider setting.</p>
-<p>Note that if your bucket isn't a valid DNS name, i.e. has '.' or '_' in, you'll need to set this to true.</p>
+<p>If this is true (the default) then rclone will use path style access,
+if false then rclone will use virtual path style. See <a
+href="https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro">the
+AWS S3 docs</a> for more info.</p>
+<p>Some providers (e.g. AWS, Aliyun OSS, Netease COS, or Tencent COS)
+require this set to false - rclone will do this automatically based on
+the provider setting.</p>
+<p>Note that if your bucket isn't a valid DNS name, i.e. has '.' or '_'
+in, you'll need to set this to true.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: force_path_style</li>
@@ -15630,8 +24866,10 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-v2-auth">--s3-v2-auth</h4>
 <p>If true use v2 authentication.</p>
-<p>If this is false (the default) then rclone will use v4 authentication. If it is set then rclone will use v2 authentication.</p>
-<p>Use this only if v4 signatures don't work, e.g. pre Jewel/v10 CEPH.</p>
+<p>If this is false (the default) then rclone will use v4
+authentication. If it is set then rclone will use v2 authentication.</p>
+<p>Use this only if v4 signatures don't work, e.g. pre Jewel/v10
+CEPH.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: v2_auth</li>
@@ -15641,7 +24879,9 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-use-dual-stack">--s3-use-dual-stack</h4>
 <p>If true use AWS S3 dual-stack endpoint (IPv6 support).</p>
-<p>See <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/dual-stack-endpoints.html">AWS Docs on Dualstack Endpoints</a></p>
+<p>See <a
+href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/dual-stack-endpoints.html">AWS
+Docs on Dualstack Endpoints</a></p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_dual_stack</li>
@@ -15651,7 +24891,9 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-use-accelerate-endpoint">--s3-use-accelerate-endpoint</h4>
 <p>If true use the AWS S3 accelerated endpoint.</p>
-<p>See: <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration-examples.html">AWS S3 Transfer acceleration</a></p>
+<p>See: <a
+href="https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration-examples.html">AWS
+S3 Transfer acceleration</a></p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_accelerate_endpoint</li>
@@ -15661,9 +24903,13 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="s3-leave-parts-on-error">--s3-leave-parts-on-error</h4>
-<p>If true avoid calling abort upload on a failure, leaving all successfully uploaded parts on S3 for manual recovery.</p>
-<p>It should be set to true for resuming uploads across different sessions.</p>
-<p>WARNING: Storing parts of an incomplete multipart upload counts towards space usage on S3 and will add additional costs if not cleaned up.</p>
+<p>If true avoid calling abort upload on a failure, leaving all
+successfully uploaded parts on S3 for manual recovery.</p>
+<p>It should be set to true for resuming uploads across different
+sessions.</p>
+<p>WARNING: Storing parts of an incomplete multipart upload counts
+towards space usage on S3 and will add additional costs if not cleaned
+up.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: leave_parts_on_error</li>
@@ -15673,8 +24919,15 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="s3-list-chunk">--s3-list-chunk</h4>
-<p>Size of listing chunk (response list for each ListObject S3 request).</p>
-<p>This option is also known as "MaxKeys", "max-items", or "page-size" from the AWS S3 specification. Most services truncate the response list to 1000 objects even if requested more than that. In AWS S3 this is a global maximum and cannot be changed, see <a href="https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html">AWS S3</a>. In Ceph, this can be increased with the "rgw list buckets max chunk" option.</p>
+<p>Size of listing chunk (response list for each ListObject S3
+request).</p>
+<p>This option is also known as "MaxKeys", "max-items", or "page-size"
+from the AWS S3 specification. Most services truncate the response list
+to 1000 objects even if requested more than that. In AWS S3 this is a
+global maximum and cannot be changed, see <a
+href="https://docs.aws.amazon.com/cli/latest/reference/s3/ls.html">AWS
+S3</a>. In Ceph, this can be increased with the "rgw list buckets max
+chunk" option.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: list_chunk</li>
@@ -15684,9 +24937,13 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-list-version">--s3-list-version</h4>
 <p>Version of ListObjects to use: 1,2 or 0 for auto.</p>
-<p>When S3 originally launched it only provided the ListObjects call to enumerate objects in a bucket.</p>
-<p>However in May 2016 the ListObjectsV2 call was introduced. This is much higher performance and should be used if at all possible.</p>
-<p>If set to the default, 0, rclone will guess according to the provider set which list objects method to call. If it guesses wrong, then it may be set manually here.</p>
+<p>When S3 originally launched it only provided the ListObjects call to
+enumerate objects in a bucket.</p>
+<p>However in May 2016 the ListObjectsV2 call was introduced. This is
+much higher performance and should be used if at all possible.</p>
+<p>If set to the default, 0, rclone will guess according to the provider
+set which list objects method to call. If it guesses wrong, then it may
+be set manually here.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: list_version</li>
@@ -15696,7 +24953,11 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-list-url-encode">--s3-list-url-encode</h4>
 <p>Whether to url encode listings: true/false/unset</p>
-<p>Some providers support URL encoding listings and where this is available this is more reliable when using control characters in file names. If this is set to unset (the default) then rclone will choose according to the provider setting what to apply, but you can override rclone's choice here.</p>
+<p>Some providers support URL encoding listings and where this is
+available this is more reliable when using control characters in file
+names. If this is set to unset (the default) then rclone will choose
+according to the provider setting what to apply, but you can override
+rclone's choice here.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: list_url_encode</li>
@@ -15706,8 +24967,11 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-no-check-bucket">--s3-no-check-bucket</h4>
 <p>If set, don't attempt to check the bucket exists or create it.</p>
-<p>This can be useful when trying to minimise the number of transactions rclone does if you know the bucket exists already.</p>
-<p>It can also be needed if the user you are using does not have bucket creation permissions. Before v1.52.0 this would have passed silently due to a bug.</p>
+<p>This can be useful when trying to minimise the number of transactions
+rclone does if you know the bucket exists already.</p>
+<p>It can also be needed if the user you are using does not have bucket
+creation permissions. Before v1.52.0 this would have passed silently due
+to a bug.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_check_bucket</li>
@@ -15717,21 +24981,30 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-no-head">--s3-no-head</h4>
 <p>If set, don't HEAD uploaded objects to check integrity.</p>
-<p>This can be useful when trying to minimise the number of transactions rclone does.</p>
-<p>Setting it means that if rclone receives a 200 OK message after uploading an object with PUT then it will assume that it got uploaded properly.</p>
+<p>This can be useful when trying to minimise the number of transactions
+rclone does.</p>
+<p>Setting it means that if rclone receives a 200 OK message after
+uploading an object with PUT then it will assume that it got uploaded
+properly.</p>
 <p>In particular it will assume:</p>
 <ul>
-<li>the metadata, including modtime, storage class and content type was as uploaded</li>
+<li>the metadata, including modtime, storage class and content type was
+as uploaded</li>
 <li>the size was as uploaded</li>
 </ul>
-<p>It reads the following items from the response for a single part PUT:</p>
+<p>It reads the following items from the response for a single part
+PUT:</p>
 <ul>
 <li>the MD5SUM</li>
 <li>The uploaded date</li>
 </ul>
 <p>For multipart uploads these items aren't read.</p>
-<p>If an source object of unknown length is uploaded then rclone <strong>will</strong> do a HEAD request.</p>
-<p>Setting this flag increases the chance for undetected upload failures, in particular an incorrect size, so it isn't recommended for normal operation. In practice the chance of an undetected upload failure is very small even with this flag.</p>
+<p>If an source object of unknown length is uploaded then rclone
+<strong>will</strong> do a HEAD request.</p>
+<p>Setting this flag increases the chance for undetected upload
+failures, in particular an incorrect size, so it isn't recommended for
+normal operation. In practice the chance of an undetected upload failure
+is very small even with this flag.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_head</li>
@@ -15750,7 +25023,8 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-encoding">--s3-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -15759,7 +25033,8 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Default: Slash,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="s3-memory-pool-flush-time">--s3-memory-pool-flush-time</h4>
-<p>How often internal memory buffer pools will be flushed. (no longer used)</p>
+<p>How often internal memory buffer pools will be flushed. (no longer
+used)</p>
 <p>Properties:</p>
 <ul>
 <li>Config: memory_pool_flush_time</li>
@@ -15768,7 +25043,8 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Default: 1m0s</li>
 </ul>
 <h4 id="s3-memory-pool-use-mmap">--s3-memory-pool-use-mmap</h4>
-<p>Whether to use mmap buffers in internal memory pool. (no longer used)</p>
+<p>Whether to use mmap buffers in internal memory pool. (no longer
+used)</p>
 <p>Properties:</p>
 <ul>
 <li>Config: memory_pool_use_mmap</li>
@@ -15778,8 +25054,12 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-disable-http2">--s3-disable-http2</h4>
 <p>Disable usage of http2 for S3 backends.</p>
-<p>There is currently an unsolved issue with the s3 (specifically minio) backend and HTTP/2. HTTP/2 is enabled by default for the s3 backend but can be disabled here. When the issue is solved this flag will be removed.</p>
-<p>See: https://github.com/rclone/rclone/issues/4673, https://github.com/rclone/rclone/issues/3631</p>
+<p>There is currently an unsolved issue with the s3 (specifically minio)
+backend and HTTP/2. HTTP/2 is enabled by default for the s3 backend but
+can be disabled here. When the issue is solved this flag will be
+removed.</p>
+<p>See: https://github.com/rclone/rclone/issues/4673,
+https://github.com/rclone/rclone/issues/3631</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_http2</li>
@@ -15788,7 +25068,9 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="s3-download-url">--s3-download-url</h4>
-<p>Custom endpoint for downloads. This is usually set to a CloudFront CDN URL as AWS S3 offers cheaper egress for data downloaded through the CloudFront network.</p>
+<p>Custom endpoint for downloads. This is usually set to a CloudFront
+CDN URL as AWS S3 offers cheaper egress for data downloaded through the
+CloudFront network.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: download_url</li>
@@ -15797,8 +25079,10 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="s3-directory-markers">--s3-directory-markers</h4>
-<p>Upload an empty object with a trailing slash when a new directory is created</p>
-<p>Empty folders are unsupported for bucket based remotes, this option creates an empty object ending with "/", to persist the folder.</p>
+<p>Upload an empty object with a trailing slash when a new directory is
+created</p>
+<p>Empty folders are unsupported for bucket based remotes, this option
+creates an empty object ending with "/", to persist the folder.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: directory_markers</li>
@@ -15808,7 +25092,8 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-use-multipart-etag">--s3-use-multipart-etag</h4>
 <p>Whether to use ETag in multipart uploads for verification</p>
-<p>This should be true, false or left unset to use the default for the provider.</p>
+<p>This should be true, false or left unset to use the default for the
+provider.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_multipart_etag</li>
@@ -15818,8 +25103,11 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-use-unsigned-payload">--s3-use-unsigned-payload</h4>
 <p>Whether to use an unsigned payload in PutObject</p>
-<p>Rclone has to avoid the AWS SDK seeking the body when calling PutObject. The AWS provider can add checksums in the trailer to avoid seeking but other providers can't.</p>
-<p>This should be true, false or left unset to use the default for the provider.</p>
+<p>Rclone has to avoid the AWS SDK seeking the body when calling
+PutObject. The AWS provider can add checksums in the trailer to avoid
+seeking but other providers can't.</p>
+<p>This should be true, false or left unset to use the default for the
+provider.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_unsigned_payload</li>
@@ -15828,9 +25116,14 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Default: unset</li>
 </ul>
 <h4 id="s3-use-presigned-request">--s3-use-presigned-request</h4>
-<p>Whether to use a presigned request or PutObject for single part uploads</p>
-<p>If this is false rclone will use PutObject from the AWS SDK to upload an object.</p>
-<p>Versions of rclone &lt; 1.59 use presigned requests to upload a single part object and setting this flag to true will re-enable that functionality. This shouldn't be necessary except in exceptional circumstances or for testing.</p>
+<p>Whether to use a presigned request or PutObject for single part
+uploads</p>
+<p>If this is false rclone will use PutObject from the AWS SDK to upload
+an object.</p>
+<p>Versions of rclone &lt; 1.59 use presigned requests to upload a
+single part object and setting this flag to true will re-enable that
+functionality. This shouldn't be necessary except in exceptional
+circumstances or for testing.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_presigned_request</li>
@@ -15849,9 +25142,12 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-version-at">--s3-version-at</h4>
 <p>Show file versions as they were at the specified time.</p>
-<p>The parameter should be a date, "2006-01-02", datetime "2006-01-02 15:04:05" or a duration for that long ago, eg "100d" or "1h".</p>
-<p>Note that when using this no file write operations are permitted, so you can't upload files or delete them.</p>
-<p>See <a href="https://rclone.org/docs/#time-option">the time option docs</a> for valid formats.</p>
+<p>The parameter should be a date, "2006-01-02", datetime "2006-01-02
+15:04:05" or a duration for that long ago, eg "100d" or "1h".</p>
+<p>Note that when using this no file write operations are permitted, so
+you can't upload files or delete them.</p>
+<p>See <a href="https://rclone.org/docs/#time-option">the time option
+docs</a> for valid formats.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: version_at</li>
@@ -15861,7 +25157,9 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-version-deleted">--s3-version-deleted</h4>
 <p>Show deleted file markers when using versions.</p>
-<p>This shows deleted file markers in the listing when using versions. These will appear as 0 size files. The only operation which can be performed on them is deletion.</p>
+<p>This shows deleted file markers in the listing when using versions.
+These will appear as 0 size files. The only operation which can be
+performed on them is deletion.</p>
 <p>Deleting a delete marker will reveal the previous version.</p>
 <p>Deleted files will always show with a timestamp.</p>
 <p>Properties:</p>
@@ -15873,8 +25171,13 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-decompress">--s3-decompress</h4>
 <p>If set this will decompress gzip encoded objects.</p>
-<p>It is possible to upload objects to S3 with "Content-Encoding: gzip" set. Normally rclone will download these files as compressed objects.</p>
-<p>If this flag is set then rclone will decompress these files with "Content-Encoding: gzip" as they are received. This means that rclone can't check the size and hash but the file contents will be decompressed.</p>
+<p>It is possible to upload objects to S3 with "Content-Encoding: gzip"
+set. Normally rclone will download these files as compressed
+objects.</p>
+<p>If this flag is set then rclone will decompress these files with
+"Content-Encoding: gzip" as they are received. This means that rclone
+can't check the size and hash but the file contents will be
+decompressed.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: decompress</li>
@@ -15884,12 +25187,19 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-might-gzip">--s3-might-gzip</h4>
 <p>Set this if the backend might gzip objects.</p>
-<p>Normally providers will not alter objects when they are downloaded. If an object was not uploaded with <code>Content-Encoding: gzip</code> then it won't be set on download.</p>
-<p>However some providers may gzip objects even if they weren't uploaded with <code>Content-Encoding: gzip</code> (eg Cloudflare).</p>
+<p>Normally providers will not alter objects when they are downloaded.
+If an object was not uploaded with <code>Content-Encoding: gzip</code>
+then it won't be set on download.</p>
+<p>However some providers may gzip objects even if they weren't uploaded
+with <code>Content-Encoding: gzip</code> (eg Cloudflare).</p>
 <p>A symptom of this would be receiving errors like</p>
 <pre><code>ERROR corrupted on transfer: sizes differ NNN vs MMM</code></pre>
-<p>If you set this flag and rclone downloads an object with Content-Encoding: gzip set and chunked transfer encoding, then rclone will decompress the object on the fly.</p>
-<p>If this is set to unset (the default) then rclone will choose according to the provider setting what to apply, but you can override rclone's choice here.</p>
+<p>If you set this flag and rclone downloads an object with
+Content-Encoding: gzip set and chunked transfer encoding, then rclone
+will decompress the object on the fly.</p>
+<p>If this is set to unset (the default) then rclone will choose
+according to the provider setting what to apply, but you can override
+rclone's choice here.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: might_gzip</li>
@@ -15899,8 +25209,10 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-use-accept-encoding-gzip">--s3-use-accept-encoding-gzip</h4>
 <p>Whether to send <code>Accept-Encoding: gzip</code> header.</p>
-<p>By default, rclone will append <code>Accept-Encoding: gzip</code> to the request to download compressed objects whenever possible.</p>
-<p>However some providers such as Google Cloud Storage may alter the HTTP headers, breaking the signature of the request.</p>
+<p>By default, rclone will append <code>Accept-Encoding: gzip</code> to
+the request to download compressed objects whenever possible.</p>
+<p>However some providers such as Google Cloud Storage may alter the
+HTTP headers, breaking the signature of the request.</p>
 <p>A symptom of this would be receiving errors like</p>
 <pre><code>SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided.</code></pre>
 <p>In this case, you might want to try disabling this option.</p>
@@ -15922,7 +25234,8 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-sts-endpoint">--s3-sts-endpoint</h4>
 <p>Endpoint for STS (deprecated).</p>
-<p>Leave blank if using AWS to use the default endpoint for the region.</p>
+<p>Leave blank if using AWS to use the default endpoint for the
+region.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sts_endpoint</li>
@@ -15932,12 +25245,26 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="s3-use-already-exists">--s3-use-already-exists</h4>
-<p>Set if rclone should report BucketAlreadyExists errors on bucket creation.</p>
-<p>At some point during the evolution of the s3 protocol, AWS started returning an <code>AlreadyOwnedByYou</code> error when attempting to create a bucket that the user already owned, rather than a <code>BucketAlreadyExists</code> error.</p>
-<p>Unfortunately exactly what has been implemented by s3 clones is a little inconsistent, some return <code>AlreadyOwnedByYou</code>, some return <code>BucketAlreadyExists</code> and some return no error at all.</p>
-<p>This is important to rclone because it ensures the bucket exists by creating it on quite a lot of operations (unless <code>--s3-no-check-bucket</code> is used).</p>
-<p>If rclone knows the provider can return <code>AlreadyOwnedByYou</code> or returns no error then it can report <code>BucketAlreadyExists</code> errors when the user attempts to create a bucket not owned by them. Otherwise rclone ignores the <code>BucketAlreadyExists</code> error which can lead to confusion.</p>
-<p>This should be automatically set correctly for all providers rclone knows about - please make a bug report if not.</p>
+<p>Set if rclone should report BucketAlreadyExists errors on bucket
+creation.</p>
+<p>At some point during the evolution of the s3 protocol, AWS started
+returning an <code>AlreadyOwnedByYou</code> error when attempting to
+create a bucket that the user already owned, rather than a
+<code>BucketAlreadyExists</code> error.</p>
+<p>Unfortunately exactly what has been implemented by s3 clones is a
+little inconsistent, some return <code>AlreadyOwnedByYou</code>, some
+return <code>BucketAlreadyExists</code> and some return no error at
+all.</p>
+<p>This is important to rclone because it ensures the bucket exists by
+creating it on quite a lot of operations (unless
+<code>--s3-no-check-bucket</code> is used).</p>
+<p>If rclone knows the provider can return
+<code>AlreadyOwnedByYou</code> or returns no error then it can report
+<code>BucketAlreadyExists</code> errors when the user attempts to create
+a bucket not owned by them. Otherwise rclone ignores the
+<code>BucketAlreadyExists</code> error which can lead to confusion.</p>
+<p>This should be automatically set correctly for all providers rclone
+knows about - please make a bug report if not.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_already_exists</li>
@@ -15947,8 +25274,10 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-use-multipart-uploads">--s3-use-multipart-uploads</h4>
 <p>Set if rclone should use multipart uploads.</p>
-<p>You can change this if you want to disable the use of multipart uploads. This shouldn't be necessary in normal operation.</p>
-<p>This should be automatically set correctly for all providers rclone knows about - please make a bug report if not.</p>
+<p>You can change this if you want to disable the use of multipart
+uploads. This shouldn't be necessary in normal operation.</p>
+<p>This should be automatically set correctly for all providers rclone
+knows about - please make a bug report if not.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_multipart_uploads</li>
@@ -15958,7 +25287,8 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </ul>
 <h4 id="s3-sdk-log-mode">--s3-sdk-log-mode</h4>
 <p>Set to debug the SDK</p>
-<p>This can be set to a comma separated list of the following functions:</p>
+<p>This can be set to a comma separated list of the following
+functions:</p>
 <ul>
 <li><code>Signing</code></li>
 <li><code>Retries</code></li>
@@ -15970,7 +25300,9 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li><code>RequestEventMessage</code></li>
 <li><code>ResponseEventMessage</code></li>
 </ul>
-<p>Use <code>Off</code> to disable and <code>All</code> to set all log levels. You will need to use <code>-vv</code> to see the debug level logs.</p>
+<p>Use <code>Off</code> to disable and <code>All</code> to set all log
+levels. You will need to use <code>-vv</code> to see the debug level
+logs.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sdk_log_mode</li>
@@ -15988,7 +25320,8 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-3">Metadata</h3>
-<p>User metadata is stored as x-amz-meta- keys. S3 metadata keys are case insensitive and are always returned in lower case.</p>
+<p>User metadata is stored as x-amz-meta- keys. S3 metadata keys are
+case insensitive and are always returned in lower case.</p>
 <p>Here are the possible system metadata items for the s3 backend.</p>
 <table>
 <colgroup>
@@ -16066,28 +25399,37 @@ Windows:   &quot;%USERPROFILE%\.aws\credentials&quot;</code></pre>
 </tr>
 </tbody>
 </table>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h2 id="backend-commands">Backend commands</h2>
 <p>Here are the commands specific to the s3 backend.</p>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="restore">restore</h3>
 <p>Restore objects from GLACIER or INTELLIGENT-TIERING archive tier</p>
 <pre><code>rclone backend restore remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command can be used to restore one or more objects from GLACIER to normal storage or from INTELLIGENT-TIERING Archive Access / Deep Archive Access tier to the Frequent Access tier.</p>
+<p>This command can be used to restore one or more objects from GLACIER
+to normal storage or from INTELLIGENT-TIERING Archive Access / Deep
+Archive Access tier to the Frequent Access tier.</p>
 <p>Usage Examples:</p>
 <pre><code>rclone backend restore s3:bucket/path/to/object -o priority=PRIORITY -o lifetime=DAYS
 rclone backend restore s3:bucket/path/to/directory -o priority=PRIORITY -o lifetime=DAYS
 rclone backend restore s3:bucket -o priority=PRIORITY -o lifetime=DAYS
 rclone backend restore s3:bucket/path/to/directory -o priority=PRIORITY</code></pre>
-<p>This flag also obeys the filters. Test first with --interactive/-i or --dry-run flags</p>
+<p>This flag also obeys the filters. Test first with --interactive/-i or
+--dry-run flags</p>
 <pre><code>rclone --interactive backend restore --include &quot;*.txt&quot; s3:bucket/path -o priority=Standard -o lifetime=1</code></pre>
 <p>All the objects shown will be marked for restore, then</p>
 <pre><code>rclone backend restore --include &quot;*.txt&quot; s3:bucket/path -o priority=Standard -o lifetime=1</code></pre>
-<p>It returns a list of status dictionaries with Remote and Status keys. The Status will be OK if it was successful or an error message if not.</p>
+<p>It returns a list of status dictionaries with Remote and Status keys.
+The Status will be OK if it was successful or an error message if
+not.</p>
 <pre><code>[
     {
         &quot;Status&quot;: &quot;OK&quot;,
@@ -16101,13 +25443,18 @@ rclone backend restore s3:bucket/path/to/directory -o priority=PRIORITY</code></
 <p>Options:</p>
 <ul>
 <li>"description": The optional description for the job.</li>
-<li>"lifetime": Lifetime of the active copy in days, ignored for INTELLIGENT-TIERING storage</li>
+<li>"lifetime": Lifetime of the active copy in days, ignored for
+INTELLIGENT-TIERING storage</li>
 <li>"priority": Priority of restore: Standard|Expedited|Bulk</li>
 </ul>
 <h3 id="restore-status">restore-status</h3>
-<p>Show the restore status for objects being restored from GLACIER or INTELLIGENT-TIERING storage</p>
+<p>Show the restore status for objects being restored from GLACIER or
+INTELLIGENT-TIERING storage</p>
 <pre><code>rclone backend restore-status remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command can be used to show the status for objects being restored from GLACIER to normal storage or from INTELLIGENT-TIERING Archive Access / Deep Archive Access tier to the Frequent Access tier.</p>
+<p>This command can be used to show the status for objects being
+restored from GLACIER to normal storage or from INTELLIGENT-TIERING
+Archive Access / Deep Archive Access tier to the Frequent Access
+tier.</p>
 <p>Usage Examples:</p>
 <pre><code>rclone backend restore-status s3:bucket/path/to/object
 rclone backend restore-status s3:bucket/path/to/directory
@@ -16145,15 +25492,19 @@ rclone backend restore-status -o all s3:bucket/path/to/directory</code></pre>
 ]</code></pre>
 <p>Options:</p>
 <ul>
-<li>"all": if set then show all objects, not just ones with restore status</li>
+<li>"all": if set then show all objects, not just ones with restore
+status</li>
 </ul>
 <h3 id="list-multipart-uploads">list-multipart-uploads</h3>
 <p>List the unfinished multipart uploads</p>
 <pre><code>rclone backend list-multipart-uploads remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command lists the unfinished multipart uploads in JSON format.</p>
+<p>This command lists the unfinished multipart uploads in JSON
+format.</p>
 <pre><code>rclone backend list-multipart s3:bucket/path/to/object</code></pre>
-<p>It returns a dictionary of buckets with values as lists of unfinished multipart uploads.</p>
-<p>You can call it with no bucket in which case it lists all bucket, with a bucket or with a bucket and path.</p>
+<p>It returns a dictionary of buckets with values as lists of unfinished
+multipart uploads.</p>
+<p>You can call it with no bucket in which case it lists all bucket,
+with a bucket or with a bucket and path.</p>
 <pre><code>{
   &quot;rclone&quot;: [
     {
@@ -16177,8 +25528,10 @@ rclone backend restore-status -o all s3:bucket/path/to/directory</code></pre>
 <h3 id="cleanup-2">cleanup</h3>
 <p>Remove unfinished multipart uploads.</p>
 <pre><code>rclone backend cleanup remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command removes unfinished multipart uploads of age greater than max-age which defaults to 24 hours.</p>
-<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
+<p>This command removes unfinished multipart uploads of age greater than
+max-age which defaults to 24 hours.</p>
+<p>Note that you can use --interactive/-i or --dry-run with this command
+to see what it would do.</p>
 <pre><code>rclone backend cleanup s3:bucket/path/to/object
 rclone backend cleanup -o max-age=7w s3:bucket/path/to/object</code></pre>
 <p>Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.</p>
@@ -16189,30 +25542,40 @@ rclone backend cleanup -o max-age=7w s3:bucket/path/to/object</code></pre>
 <h3 id="cleanup-hidden">cleanup-hidden</h3>
 <p>Remove old versions of files.</p>
 <pre><code>rclone backend cleanup-hidden remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command removes any old hidden versions of files on a versions enabled bucket.</p>
-<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
+<p>This command removes any old hidden versions of files on a versions
+enabled bucket.</p>
+<p>Note that you can use --interactive/-i or --dry-run with this command
+to see what it would do.</p>
 <pre><code>rclone backend cleanup-hidden s3:bucket/path/to/dir</code></pre>
 <h3 id="versioning">versioning</h3>
 <p>Set/get versioning support for a bucket.</p>
 <pre><code>rclone backend versioning remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command sets versioning support if a parameter is passed and then returns the current versioning status for the bucket supplied.</p>
+<p>This command sets versioning support if a parameter is passed and
+then returns the current versioning status for the bucket supplied.</p>
 <pre><code>rclone backend versioning s3:bucket # read status only
 rclone backend versioning s3:bucket Enabled
 rclone backend versioning s3:bucket Suspended</code></pre>
-<p>It may return "Enabled", "Suspended" or "Unversioned". Note that once versioning has been enabled the status can't be set back to "Unversioned".</p>
+<p>It may return "Enabled", "Suspended" or "Unversioned". Note that once
+versioning has been enabled the status can't be set back to
+"Unversioned".</p>
 <h3 id="set">set</h3>
 <p>Set command for updating the config parameters.</p>
 <pre><code>rclone backend set remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This set command can be used to update the config parameters for a running s3 backend.</p>
+<p>This set command can be used to update the config parameters for a
+running s3 backend.</p>
 <p>Usage Examples:</p>
 <pre><code>rclone backend set s3: [-o opt_name=opt_value] [-o opt_name2=opt_value2]
 rclone rc backend/command command=set fs=s3: [-o opt_name=opt_value] [-o opt_name2=opt_value2]
 rclone rc backend/command command=set fs=s3: -o session_token=X -o access_key_id=X -o secret_access_key=X</code></pre>
 <p>The option keys are named as they are in the config file.</p>
-<p>This rebuilds the connection to the s3 backend when it is called with the new parameters. Only new parameters need be passed as the values will default to those currently in use.</p>
+<p>This rebuilds the connection to the s3 backend when it is called with
+the new parameters. Only new parameters need be passed as the values
+will default to those currently in use.</p>
 <p>It doesn't return anything.</p>
 <h3 id="anonymous-access">Anonymous access to public buckets</h3>
-<p>If you want to use rclone to access a public bucket, configure with a blank <code>access_key_id</code> and <code>secret_access_key</code>. Your config should end up looking like this:</p>
+<p>If you want to use rclone to access a public bucket, configure with a
+blank <code>access_key_id</code> and <code>secret_access_key</code>.
+Your config should end up looking like this:</p>
 <pre><code>[anons3]
 type = s3
 provider = AWS</code></pre>
@@ -16223,12 +25586,20 @@ provider = AWS</code></pre>
 <pre><code>rclone lsd :s3,provider=AWS:1000genomes</code></pre>
 <h2 id="providers-1">Providers</h2>
 <h3 id="aws-s3">AWS S3</h3>
-<p>This is the provider used as main example and described in the <a href="#configuration">configuration</a> section above.</p>
+<p>This is the provider used as main example and described in the <a
+href="#configuration">configuration</a> section above.</p>
 <h3 id="aws-snowball-edge">AWS Snowball Edge</h3>
-<p><a href="https://aws.amazon.com/snowball/">AWS Snowball</a> is a hardware appliance used for transferring bulk data back to AWS. Its main software interface is S3 object storage.</p>
-<p>To use rclone with AWS Snowball Edge devices, configure as standard for an 'S3 Compatible Service'.</p>
-<p>If using rclone pre v1.59 be sure to set <code>upload_cutoff = 0</code> otherwise you will run into authentication header issues as the snowball device does not support query parameter based authentication.</p>
-<p>With rclone v1.59 or later setting <code>upload_cutoff</code> should not be necessary.</p>
+<p><a href="https://aws.amazon.com/snowball/">AWS Snowball</a> is a
+hardware appliance used for transferring bulk data back to AWS. Its main
+software interface is S3 object storage.</p>
+<p>To use rclone with AWS Snowball Edge devices, configure as standard
+for an 'S3 Compatible Service'.</p>
+<p>If using rclone pre v1.59 be sure to set
+<code>upload_cutoff = 0</code> otherwise you will run into
+authentication header issues as the snowball device does not support
+query parameter based authentication.</p>
+<p>With rclone v1.59 or later setting <code>upload_cutoff</code> should
+not be necessary.</p>
 <p>eg.</p>
 <pre><code>[snowball]
 type = s3
@@ -16238,8 +25609,13 @@ secret_access_key = YOUR_SECRET_KEY
 endpoint = http://[IP of Snowball]:8080
 upload_cutoff = 0</code></pre>
 <h3 id="ceph">Ceph</h3>
-<p><a href="https://ceph.com/">Ceph</a> is an open-source, unified, distributed storage system designed for excellent performance, reliability and scalability. It has an S3 compatible object storage interface.</p>
-<p>To use rclone with Ceph, configure as above but leave the region blank and set the endpoint. You should end up with something like this in your config:</p>
+<p><a href="https://ceph.com/">Ceph</a> is an open-source, unified,
+distributed storage system designed for excellent performance,
+reliability and scalability. It has an S3 compatible object storage
+interface.</p>
+<p>To use rclone with Ceph, configure as above but leave the region
+blank and set the endpoint. You should end up with something like this
+in your config:</p>
 <pre><code>[ceph]
 type = s3
 provider = Ceph
@@ -16252,9 +25628,18 @@ location_constraint =
 acl =
 server_side_encryption =
 storage_class =</code></pre>
-<p>If you are using an older version of CEPH (e.g. 10.2.x Jewel) and a version of rclone before v1.59 then you may need to supply the parameter <code>--s3-upload-cutoff 0</code> or put this in the config file as <code>upload_cutoff 0</code> to work around a bug which causes uploading of small files to fail.</p>
-<p>Note also that Ceph sometimes puts <code>/</code> in the passwords it gives users. If you read the secret access key using the command line tools you will get a JSON blob with the <code>/</code> escaped as <code>\/</code>. Make sure you only write <code>/</code> in the secret access key.</p>
-<p>Eg the dump from Ceph looks something like this (irrelevant keys removed).</p>
+<p>If you are using an older version of CEPH (e.g. 10.2.x Jewel) and a
+version of rclone before v1.59 then you may need to supply the parameter
+<code>--s3-upload-cutoff 0</code> or put this in the config file as
+<code>upload_cutoff 0</code> to work around a bug which causes uploading
+of small files to fail.</p>
+<p>Note also that Ceph sometimes puts <code>/</code> in the passwords it
+gives users. If you read the secret access key using the command line
+tools you will get a JSON blob with the <code>/</code> escaped as
+<code>\/</code>. Make sure you only write <code>/</code> in the secret
+access key.</p>
+<p>Eg the dump from Ceph looks something like this (irrelevant keys
+removed).</p>
 <pre><code>{
     &quot;user_id&quot;: &quot;xxx&quot;,
     &quot;display_name&quot;: &quot;xxxx&quot;,
@@ -16266,13 +25651,21 @@ storage_class =</code></pre>
         }
     ],
 }</code></pre>
-<p>Because this is a json dump, it is encoding the <code>/</code> as <code>\/</code>, so if you use the secret key as <code>xxxxxx/xxxx</code> it will work fine.</p>
+<p>Because this is a json dump, it is encoding the <code>/</code> as
+<code>\/</code>, so if you use the secret key as
+<code>xxxxxx/xxxx</code> it will work fine.</p>
 <h3 id="cloudflare-r2">Cloudflare R2</h3>
-<p><a href="https://blog.cloudflare.com/r2-open-beta/">Cloudflare R2</a> Storage allows developers to store large amounts of unstructured data without the costly egress bandwidth fees associated with typical cloud storage services.</p>
-<p>Here is an example of making a Cloudflare R2 configuration. First run:</p>
+<p><a href="https://blog.cloudflare.com/r2-open-beta/">Cloudflare R2</a>
+Storage allows developers to store large amounts of unstructured data
+without the costly egress bandwidth fees associated with typical cloud
+storage services.</p>
+<p>Here is an example of making a Cloudflare R2 configuration. First
+run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
-<p>Note that all buckets are private, and all are stored in the same "auto" region. It is necessary to use Cloudflare workers to share the content of a bucket publicly.</p>
+<p>Note that all buckets are private, and all are stored in the same
+"auto" region. It is necessary to use Cloudflare workers to share the
+content of a bucket publicly.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -16346,12 +25739,22 @@ secret_access_key = SECRET_ACCESS_KEY
 region = auto
 endpoint = https://ACCOUNT_ID.r2.cloudflarestorage.com
 acl = private</code></pre>
-<p>Now run <code>rclone lsf r2:</code> to see your buckets and <code>rclone lsf r2:bucket</code> to look within a bucket.</p>
-<p>For R2 tokens with the "Object Read &amp; Write" permission, you may also need to add <code>no_check_bucket = true</code> for object uploads to work correctly.</p>
-<p>Note that Cloudflare decompresses files uploaded with <code>Content-Encoding: gzip</code> by default which is a deviation from what AWS does. If this is causing a problem then upload the files with <code>--header-upload "Cache-Control: no-transform"</code></p>
+<p>Now run <code>rclone lsf r2:</code> to see your buckets and
+<code>rclone lsf r2:bucket</code> to look within a bucket.</p>
+<p>For R2 tokens with the "Object Read &amp; Write" permission, you may
+also need to add <code>no_check_bucket = true</code> for object uploads
+to work correctly.</p>
+<p>Note that Cloudflare decompresses files uploaded with
+<code>Content-Encoding: gzip</code> by default which is a deviation from
+what AWS does. If this is causing a problem then upload the files with
+<code>--header-upload "Cache-Control: no-transform"</code></p>
 <h3 id="dreamhost">Dreamhost</h3>
-<p>Dreamhost <a href="https://www.dreamhost.com/cloud/storage/">DreamObjects</a> is an object storage system based on CEPH.</p>
-<p>To use rclone with Dreamhost, configure as above but leave the region blank and set the endpoint. You should end up with something like this in your config:</p>
+<p>Dreamhost <a
+href="https://www.dreamhost.com/cloud/storage/">DreamObjects</a> is an
+object storage system based on CEPH.</p>
+<p>To use rclone with Dreamhost, configure as above but leave the region
+blank and set the endpoint. You should end up with something like this
+in your config:</p>
 <pre><code>[dreamobjects]
 type = s3
 provider = DreamHost
@@ -16365,22 +25768,47 @@ acl = private
 server_side_encryption =
 storage_class =</code></pre>
 <h3 id="google-cloud-storage">Google Cloud Storage</h3>
-<p><a href="https://cloud.google.com/storage/docs">GoogleCloudStorage</a> is an <a href="https://cloud.google.com/storage/docs/interoperability">S3-interoperable</a> object storage service from Google Cloud Platform.</p>
-<p>To connect to Google Cloud Storage you will need an access key and secret key. These can be retrieved by creating an <a href="https://cloud.google.com/storage/docs/authentication/managing-hmackeys">HMAC key</a>.</p>
+<p><a
+href="https://cloud.google.com/storage/docs">GoogleCloudStorage</a> is
+an <a
+href="https://cloud.google.com/storage/docs/interoperability">S3-interoperable</a>
+object storage service from Google Cloud Platform.</p>
+<p>To connect to Google Cloud Storage you will need an access key and
+secret key. These can be retrieved by creating an <a
+href="https://cloud.google.com/storage/docs/authentication/managing-hmackeys">HMAC
+key</a>.</p>
 <pre><code>[gs]
 type = s3
 provider = GCS
 access_key_id = your_access_key
 secret_access_key = your_secret_key
 endpoint = https://storage.googleapis.com</code></pre>
-<p><strong>Note</strong> that <code>--s3-versions</code> does not work with GCS when it needs to do directory paging. Rclone will return the error:</p>
+<p><strong>Note</strong> that <code>--s3-versions</code> does not work
+with GCS when it needs to do directory paging. Rclone will return the
+error:</p>
 <pre><code>s3 protocol error: received versions listing with IsTruncated set with no NextKeyMarker</code></pre>
-<p>This is Google bug <a href="https://issuetracker.google.com/u/0/issues/312292516">#312292516</a>.</p>
+<p>This is Google bug <a
+href="https://issuetracker.google.com/u/0/issues/312292516">#312292516</a>.</p>
 <h3 id="digitalocean-spaces">DigitalOcean Spaces</h3>
-<p><a href="https://www.digitalocean.com/products/object-storage/">Spaces</a> is an <a href="https://developers.digitalocean.com/documentation/spaces/">S3-interoperable</a> object storage service from cloud provider DigitalOcean.</p>
-<p>To connect to DigitalOcean Spaces you will need an access key and secret key. These can be retrieved on the "<a href="https://cloud.digitalocean.com/settings/api/tokens">Applications &amp; API</a>" page of the DigitalOcean control panel. They will be needed when prompted by <code>rclone config</code> for your <code>access_key_id</code> and <code>secret_access_key</code>.</p>
-<p>When prompted for a <code>region</code> or <code>location_constraint</code>, press enter to use the default value. The region must be included in the <code>endpoint</code> setting (e.g. <code>nyc3.digitaloceanspaces.com</code>). The default values can be used for other settings.</p>
-<p>Going through the whole process of creating a new remote by running <code>rclone config</code>, each prompt should be answered as shown below:</p>
+<p><a
+href="https://www.digitalocean.com/products/object-storage/">Spaces</a>
+is an <a
+href="https://developers.digitalocean.com/documentation/spaces/">S3-interoperable</a>
+object storage service from cloud provider DigitalOcean.</p>
+<p>To connect to DigitalOcean Spaces you will need an access key and
+secret key. These can be retrieved on the "<a
+href="https://cloud.digitalocean.com/settings/api/tokens">Applications
+&amp; API</a>" page of the DigitalOcean control panel. They will be
+needed when prompted by <code>rclone config</code> for your
+<code>access_key_id</code> and <code>secret_access_key</code>.</p>
+<p>When prompted for a <code>region</code> or
+<code>location_constraint</code>, press enter to use the default value.
+The region must be included in the <code>endpoint</code> setting (e.g.
+<code>nyc3.digitaloceanspaces.com</code>). The default values can be
+used for other settings.</p>
+<p>Going through the whole process of creating a new remote by running
+<code>rclone config</code>, each prompt should be answered as shown
+below:</p>
 <pre><code>Storage&gt; s3
 env_auth&gt; 1
 access_key_id&gt; YOUR_ACCESS_KEY
@@ -16403,12 +25831,16 @@ location_constraint =
 acl =
 server_side_encryption =
 storage_class =</code></pre>
-<p>Once configured, you can create a new Space and begin copying files. For example:</p>
+<p>Once configured, you can create a new Space and begin copying files.
+For example:</p>
 <pre><code>rclone mkdir spaces:my-new-space
 rclone copy /path/to/files spaces:my-new-space</code></pre>
 <h3 id="huawei-obs">Huawei OBS</h3>
-<p>Object Storage Service (OBS) provides stable, secure, efficient, and easy-to-use cloud storage that lets you store virtually any volume of unstructured data in any format and access it from anywhere.</p>
-<p>OBS provides an S3 interface, you can copy and modify the following configuration and add it to your rclone configuration file.</p>
+<p>Object Storage Service (OBS) provides stable, secure, efficient, and
+easy-to-use cloud storage that lets you store virtually any volume of
+unstructured data in any format and access it from anywhere.</p>
+<p>OBS provides an S3 interface, you can copy and modify the following
+configuration and add it to your rclone configuration file.</p>
 <pre><code>[obs]
 type = s3
 provider = HuaweiOBS
@@ -16527,7 +25959,12 @@ s) Set configuration password
 q) Quit config
 e/n/d/r/c/s/q&gt; q</code></pre>
 <h3 id="ibm-cos-s3">IBM COS (S3)</h3>
-<p>Information stored with IBM Cloud Object Storage is encrypted and dispersed across multiple geographic locations, and accessed through an implementation of the S3 API. This service makes use of the distributed storage technologies provided by IBM’s Cloud Object Storage System (formerly Cleversafe). For more information visit: (http://www.ibm.com/cloud/object-storage)</p>
+<p>Information stored with IBM Cloud Object Storage is encrypted and
+dispersed across multiple geographic locations, and accessed through an
+implementation of the S3 API. This service makes use of the distributed
+storage technologies provided by IBM’s Cloud Object Storage System
+(formerly Cleversafe). For more information visit:
+(http://www.ibm.com/cloud/object-storage)</p>
 <p>To configure access to IBM COS S3, follow the steps below:</p>
 <ol type="1">
 <li>Run rclone config and select n for a new remote.</li>
@@ -16575,7 +26012,9 @@ Choose a number from below, or type in your own value
     AWS Secret Access Key (password) - leave blank for anonymous access or runtime credentials.
     secret_access_key&gt; &lt;&gt;</code></pre>
 <ol start="6" type="1">
-<li>Specify the endpoint for IBM COS. For Public IBM COS, choose from the option below. For On Premise IBM COS, enter an endpoint address.</li>
+<li>Specify the endpoint for IBM COS. For Public IBM COS, choose from
+the option below. For On Premise IBM COS, enter an endpoint
+address.</li>
 </ol>
 <pre><code>    Endpoint for IBM COS S3 API.
     Specify if using an IBM COS On Premise.
@@ -16606,7 +26045,9 @@ Choose a number from below, or type in your own value
        \ &quot;s3.tor01.objectstorage.service.networklayer.com&quot;
     endpoint&gt;1</code></pre>
 <ol start="7" type="1">
-<li>Specify a IBM COS Location Constraint. The location constraint must match endpoint when using IBM Cloud Public. For on-prem COS, do not make a selection from this list, hit enter</li>
+<li>Specify a IBM COS Location Constraint. The location constraint must
+match endpoint when using IBM Cloud Public. For on-prem COS, do not make
+a selection from this list, hit enter</li>
 </ol>
 <pre><code>     1 / US Cross Region Standard
        \ &quot;us-standard&quot;
@@ -16633,7 +26074,9 @@ Choose a number from below, or type in your own value
        \ &quot;tor01-flex&quot;
 location_constraint&gt;1</code></pre>
 <ol start="9" type="1">
-<li>Specify a canned ACL. IBM Cloud (Storage) supports "public-read" and "private". IBM Cloud(Infra) supports all the canned ACLs. On-Premise COS supports all the canned ACLs.</li>
+<li>Specify a canned ACL. IBM Cloud (Storage) supports "public-read" and
+"private". IBM Cloud(Infra) supports all the canned ACLs. On-Premise COS
+supports all the canned ACLs.</li>
 </ol>
 <pre><code>Canned ACL used when creating buckets and/or storing objects in S3.
 For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
@@ -16648,7 +26091,8 @@ Choose a number from below, or type in your own value
       \ &quot;authenticated-read&quot;
 acl&gt; 1</code></pre>
 <ol start="12" type="1">
-<li>Review the displayed configuration and accept to save the "remote" then quit. The config file should look like this</li>
+<li>Review the displayed configuration and accept to save the "remote"
+then quit. The config file should look like this</li>
 </ol>
 <pre><code>    [xxx]
     type = s3
@@ -16677,7 +26121,9 @@ acl&gt; 1</code></pre>
     6)  Delete a file on remote.
         rclone delete IBM-COS-XREGION:newbucket/file.txt</code></pre>
 <h3 id="idrive-e2">IDrive e2</h3>
-<p>Here is an example of making an <a href="https://www.idrive.com/e2/">IDrive e2</a> configuration. First run:</p>
+<p>Here is an example of making an <a
+href="https://www.idrive.com/e2/">IDrive e2</a> configuration. First
+run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
 <pre><code>No remotes found, make a new one?
@@ -16779,8 +26225,17 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
 <h3 id="ionos">IONOS Cloud</h3>
-<p><a href="https://cloud.ionos.com/storage/object-storage">IONOS S3 Object Storage</a> is a service offered by IONOS for storing and accessing unstructured data. To connect to the service, you will need an access key and a secret key. These can be found in the <a href="https://dcd.ionos.com/">Data Center Designer</a>, by selecting <strong>Manager resources</strong> &gt; <strong>Object Storage Key Manager</strong>.</p>
-<p>Here is an example of a configuration. First, run <code>rclone config</code>. This will walk you through an interactive setup process. Type <code>n</code> to add the new remote, and then enter a name:</p>
+<p><a href="https://cloud.ionos.com/storage/object-storage">IONOS S3
+Object Storage</a> is a service offered by IONOS for storing and
+accessing unstructured data. To connect to the service, you will need an
+access key and a secret key. These can be found in the <a
+href="https://dcd.ionos.com/">Data Center Designer</a>, by selecting
+<strong>Manager resources</strong> &gt; <strong>Object Storage Key
+Manager</strong>.</p>
+<p>Here is an example of a configuration. First, run
+<code>rclone config</code>. This will walk you through an interactive
+setup process. Type <code>n</code> to add the new remote, and then enter
+a name:</p>
 <pre><code>Enter name for new remote.
 name&gt; ionos-fra</code></pre>
 <p>Type <code>s3</code> to choose the connection type:</p>
@@ -16802,7 +26257,8 @@ XX / IONOS Cloud
    \ (IONOS)
 [snip]
 provider&gt; IONOS</code></pre>
-<p>Press Enter to choose the default option <code>Enter AWS credentials in the next step</code>:</p>
+<p>Press Enter to choose the default option
+<code>Enter AWS credentials in the next step</code>:</p>
 <pre><code>Option env_auth.
 Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
 Only applies if access_key_id and secret_access_key is blank.
@@ -16813,7 +26269,9 @@ Press Enter for the default (false).
  2 / Get AWS credentials from the environment (env vars or IAM).
    \ (true)
 env_auth&gt;</code></pre>
-<p>Enter your Access Key and Secret key. These can be retrieved in the <a href="https://dcd.ionos.com/">Data Center Designer</a>, click on the menu “Manager resources” / "Object Storage Key Manager".</p>
+<p>Enter your Access Key and Secret key. These can be retrieved in the
+<a href="https://dcd.ionos.com/">Data Center Designer</a>, click on the
+menu “Manager resources” / "Object Storage Key Manager".</p>
 <pre><code>Option access_key_id.
 AWS Access Key ID.
 Leave blank for anonymous access or runtime credentials.
@@ -16850,7 +26308,8 @@ Press Enter to leave empty.
  3 / Logrono, Spain
    \ (s3-eu-south-2.ionoscloud.com)
 endpoint&gt; 1</code></pre>
-<p>Press Enter to choose the default option or choose the desired ACL setting:</p>
+<p>Press Enter to choose the default option or choose the desired ACL
+setting:</p>
 <pre><code>Option acl.
 Canned ACL used when creating buckets and storing or copying objects.
 This ACL is used for creating objects and if bucket_acl isn&#39;t set, for creating buckets too.
@@ -16870,7 +26329,8 @@ acl&gt;</code></pre>
 y) Yes
 n) No (default)
 y/n&gt;</code></pre>
-<p>Press Enter to save the configuration, and then <code>q</code> to quit the configuration process:</p>
+<p>Press Enter to save the configuration, and then <code>q</code> to
+quit the configuration process:</p>
 <pre><code>Configuration complete.
 Options:
 - type: s3
@@ -16883,9 +26343,11 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>Done! Now you can try some commands (for macOS, use <code>./rclone</code> instead of <code>rclone</code>).</p>
+<p>Done! Now you can try some commands (for macOS, use
+<code>./rclone</code> instead of <code>rclone</code>).</p>
 <ol type="1">
-<li>Create a bucket (the name must be unique within the whole IONOS S3)</li>
+<li>Create a bucket (the name must be unique within the whole IONOS
+S3)</li>
 </ol>
 <pre><code>rclone mkdir ionos-fra:my-bucket</code></pre>
 <ol start="2" type="1">
@@ -16905,9 +26367,12 @@ y/e/d&gt; y</code></pre>
 </ol>
 <pre><code>rclone copy ionos-fra:my-bucket/file.txt</code></pre>
 <h3 id="minio">Minio</h3>
-<p><a href="https://minio.io/">Minio</a> is an object storage server built for cloud application developers and devops.</p>
-<p>It is very easy to install and provides an S3 compatible server which can be used by rclone.</p>
-<p>To use it, install Minio following the instructions <a href="https://docs.minio.io/docs/minio-quickstart-guide">here</a>.</p>
+<p><a href="https://minio.io/">Minio</a> is an object storage server
+built for cloud application developers and devops.</p>
+<p>It is very easy to install and provides an S3 compatible server which
+can be used by rclone.</p>
+<p>To use it, install Minio following the instructions <a
+href="https://docs.minio.io/docs/minio-quickstart-guide">here</a>.</p>
 <p>When it configures itself Minio will print something like this</p>
 <pre><code>Endpoint:  http://192.168.1.106:9000  http://172.23.0.1:9000
 AccessKey: USWUXHGYZQYFYFFIT3RE
@@ -16929,7 +26394,8 @@ Object API (Amazon S3 compatible):
    .NET:       https://docs.minio.io/docs/dotnet-client-quickstart-guide
 
 Drive Capacity: 26 GiB Free, 165 GiB Total</code></pre>
-<p>These details need to go into <code>rclone config</code> like this. Note that it is important to put the region in as stated above.</p>
+<p>These details need to go into <code>rclone config</code> like this.
+Note that it is important to put the region in as stated above.</p>
 <pre><code>env_auth&gt; 1
 access_key_id&gt; USWUXHGYZQYFYFFIT3RE
 secret_access_key&gt; MOJRH0mkL1IPauahWITSVvyDrQbEEIwljvmxdq03
@@ -16951,10 +26417,15 @@ server_side_encryption =</code></pre>
 <p>So once set up, for example, to copy files into a bucket</p>
 <pre><code>rclone copy /path/to/files minio:bucket</code></pre>
 <h3 id="qiniu">Qiniu Cloud Object Storage (Kodo)</h3>
-<p><a href="https://www.qiniu.com/en/products/kodo">Qiniu Cloud Object Storage (Kodo)</a>, a completely independent-researched core technology which is proven by repeated customer experience has occupied absolute leading market leader position. Kodo can be widely applied to mass data management.</p>
+<p><a href="https://www.qiniu.com/en/products/kodo">Qiniu Cloud Object
+Storage (Kodo)</a>, a completely independent-researched core technology
+which is proven by repeated customer experience has occupied absolute
+leading market leader position. Kodo can be widely applied to mass data
+management.</p>
 <p>To configure access to Qiniu Kodo, follow the steps below:</p>
 <ol type="1">
-<li>Run <code>rclone config</code> and select <code>n</code> for a new remote.</li>
+<li>Run <code>rclone config</code> and select <code>n</code> for a new
+remote.</li>
 </ol>
 <pre><code>rclone config
 No remotes found, make a new one?
@@ -16963,7 +26434,8 @@ s) Set configuration password
 q) Quit config
 n/s/q&gt; n</code></pre>
 <ol start="2" type="1">
-<li>Give the name of the configuration. For example, name it 'qiniu'.</li>
+<li>Give the name of the configuration. For example, name it
+'qiniu'.</li>
 </ol>
 <pre><code>name&gt; qiniu</code></pre>
 <ol start="3" type="1">
@@ -17007,7 +26479,8 @@ Leave blank for anonymous access or runtime credentials.
 Enter a string value. Press Enter for the default (&quot;&quot;).
 secret_access_key&gt; xxxxxxxxxxx</code></pre>
 <ol start="6" type="1">
-<li>Select endpoint for Qiniu Kodo. This is the standard endpoint for different region.</li>
+<li>Select endpoint for Qiniu Kodo. This is the standard endpoint for
+different region.</li>
 </ol>
 <pre><code>   / The default endpoint - a good choice if you are unsure.
  1 | East China Region 1.
@@ -17129,8 +26602,19 @@ Name                 Type
 ====                 ====
 qiniu                s3</code></pre>
 <h3 id="RackCorp">RackCorp</h3>
-<p><a href="https://www.rackcorp.com/storage/s3storage">RackCorp Object Storage</a> is an S3 compatible object storage platform from your friendly cloud provider RackCorp. The service is fast, reliable, well priced and located in many strategic locations unserviced by others, to ensure you can maintain data sovereignty.</p>
-<p>Before you can use RackCorp Object Storage, you'll need to "<a href="https://www.rackcorp.com/signup">sign up</a>" for an account on our "<a href="https://portal.rackcorp.com">portal</a>". Next you can create an <code>access key</code>, a <code>secret key</code> and <code>buckets</code>, in your location of choice with ease. These details are required for the next steps of configuration, when <code>rclone config</code> asks for your <code>access_key_id</code> and <code>secret_access_key</code>.</p>
+<p><a href="https://www.rackcorp.com/storage/s3storage">RackCorp Object
+Storage</a> is an S3 compatible object storage platform from your
+friendly cloud provider RackCorp. The service is fast, reliable, well
+priced and located in many strategic locations unserviced by others, to
+ensure you can maintain data sovereignty.</p>
+<p>Before you can use RackCorp Object Storage, you'll need to "<a
+href="https://www.rackcorp.com/signup">sign up</a>" for an account on
+our "<a href="https://portal.rackcorp.com">portal</a>". Next you can
+create an <code>access key</code>, a <code>secret key</code> and
+<code>buckets</code>, in your location of choice with ease. These
+details are required for the next steps of configuration, when
+<code>rclone config</code> asks for your <code>access_key_id</code> and
+<code>secret_access_key</code>.</p>
 <p>Your config should end up looking a bit like this:</p>
 <pre><code>[RCS3-demo-config]
 type = s3
@@ -17142,10 +26626,14 @@ region = au-nsw
 endpoint = s3.rackcorp.com
 location_constraint = au-nsw</code></pre>
 <h3 id="rclone">Rclone Serve S3</h3>
-<p>Rclone can serve any remote over the S3 protocol. For details see the <a href="https://rclone.org/commands/rclone_serve_http/">rclone serve s3</a> documentation.</p>
-<p>For example, to serve <code>remote:path</code> over s3, run the server like this:</p>
+<p>Rclone can serve any remote over the S3 protocol. For details see the
+<a href="https://rclone.org/commands/rclone_serve_http/">rclone serve
+s3</a> documentation.</p>
+<p>For example, to serve <code>remote:path</code> over s3, run the
+server like this:</p>
 <pre><code>rclone serve s3 --auth-key ACCESS_KEY_ID,SECRET_ACCESS_KEY remote:path</code></pre>
-<p>This will be compatible with an rclone remote which is defined like this:</p>
+<p>This will be compatible with an rclone remote which is defined like
+this:</p>
 <pre><code>[serves3]
 type = s3
 provider = Rclone
@@ -17153,10 +26641,18 @@ endpoint = http://127.0.0.1:8080/
 access_key_id = ACCESS_KEY_ID
 secret_access_key = SECRET_ACCESS_KEY
 use_multipart_uploads = false</code></pre>
-<p>Note that setting <code>disable_multipart_uploads = true</code> is to work around <a href="https://rclone.org/commands/rclone_serve_http/#bugs">a bug</a> which will be fixed in due course.</p>
+<p>Note that setting <code>disable_multipart_uploads = true</code> is to
+work around <a
+href="https://rclone.org/commands/rclone_serve_http/#bugs">a bug</a>
+which will be fixed in due course.</p>
 <h3 id="scaleway">Scaleway</h3>
-<p><a href="https://www.scaleway.com/object-storage/">Scaleway</a> The Object Storage platform allows you to store anything from backups, logs and web assets to documents and photos. Files can be dropped from the Scaleway console or transferred through our API and CLI or using any S3-compatible tool.</p>
-<p>Scaleway provides an S3 interface which can be configured for use with rclone like this:</p>
+<p><a href="https://www.scaleway.com/object-storage/">Scaleway</a> The
+Object Storage platform allows you to store anything from backups, logs
+and web assets to documents and photos. Files can be dropped from the
+Scaleway console or transferred through our API and CLI or using any
+S3-compatible tool.</p>
+<p>Scaleway provides an S3 interface which can be configured for use
+with rclone like this:</p>
 <pre><code>[scaleway]
 type = s3
 provider = Scaleway
@@ -17170,10 +26666,23 @@ acl = private
 upload_cutoff = 5M
 chunk_size = 5M
 copy_cutoff = 5M</code></pre>
-<p><a href="https://www.scaleway.com/en/glacier-cold-storage/">Scaleway Glacier</a> is the low-cost S3 Glacier alternative from Scaleway and it works the same way as on S3 by accepting the "GLACIER" <code>storage_class</code>. So you can configure your remote with the <code>storage_class = GLACIER</code> option to upload directly to Scaleway Glacier. Don't forget that in this state you can't read files back after, you will need to restore them to "STANDARD" storage_class first before being able to read them (see "restore" section above)</p>
+<p><a href="https://www.scaleway.com/en/glacier-cold-storage/">Scaleway
+Glacier</a> is the low-cost S3 Glacier alternative from Scaleway and it
+works the same way as on S3 by accepting the "GLACIER"
+<code>storage_class</code>. So you can configure your remote with the
+<code>storage_class = GLACIER</code> option to upload directly to
+Scaleway Glacier. Don't forget that in this state you can't read files
+back after, you will need to restore them to "STANDARD" storage_class
+first before being able to read them (see "restore" section above)</p>
 <h3 id="lyve">Seagate Lyve Cloud</h3>
-<p><a href="https://www.seagate.com/gb/en/services/cloud/storage/">Seagate Lyve Cloud</a> is an S3 compatible object storage platform from <a href="https://seagate.com/">Seagate</a> intended for enterprise use.</p>
-<p>Here is a config run through for a remote called <code>remote</code> - you may choose a different name of course. Note that to create an access key and secret key you will need to create a service account first.</p>
+<p><a
+href="https://www.seagate.com/gb/en/services/cloud/storage/">Seagate
+Lyve Cloud</a> is an S3 compatible object storage platform from <a
+href="https://seagate.com/">Seagate</a> intended for enterprise use.</p>
+<p>Here is a config run through for a remote called <code>remote</code>
+- you may choose a different name of course. Note that to create an
+access key and secret key you will need to create a service account
+first.</p>
 <pre><code>$ rclone config
 No remotes found, make a new one?
 n) New remote
@@ -17198,7 +26707,8 @@ XX / Seagate Lyve Cloud
    \ (LyveCloud)
 [snip]
 provider&gt; LyveCloud</code></pre>
-<p>Take the default (just press enter) to enter access key and secret in the config file.</p>
+<p>Take the default (just press enter) to enter access key and secret in
+the config file.</p>
 <pre><code>Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
 Only applies if access_key_id and secret_access_key is blank.
 Choose a number from below, or type in your own boolean value (true or false).
@@ -17266,8 +26776,16 @@ access_key_id = XXX
 secret_access_key = YYY
 endpoint = s3.us-east-1.lyvecloud.seagate.com</code></pre>
 <h3 id="seaweedfs">SeaweedFS</h3>
-<p><a href="https://github.com/chrislusf/seaweedfs/">SeaweedFS</a> is a distributed storage system for blobs, objects, files, and data lake, with O(1) disk seek and a scalable file metadata store. It has an S3 compatible object storage interface. SeaweedFS can also act as a <a href="https://github.com/chrislusf/seaweedfs/wiki/Gateway-to-Remote-Object-Storage">gateway to remote S3 compatible object store</a> to cache data and metadata with asynchronous write back, for fast local speed and minimize access cost.</p>
-<p>Assuming the SeaweedFS are configured with <code>weed shell</code> as such:</p>
+<p><a href="https://github.com/chrislusf/seaweedfs/">SeaweedFS</a> is a
+distributed storage system for blobs, objects, files, and data lake,
+with O(1) disk seek and a scalable file metadata store. It has an S3
+compatible object storage interface. SeaweedFS can also act as a <a
+href="https://github.com/chrislusf/seaweedfs/wiki/Gateway-to-Remote-Object-Storage">gateway
+to remote S3 compatible object store</a> to cache data and metadata with
+asynchronous write back, for fast local speed and minimize access
+cost.</p>
+<p>Assuming the SeaweedFS are configured with <code>weed shell</code> as
+such:</p>
 <pre><code>&gt; s3.bucket.create -name foo
 &gt; s3.configure -access_key=any -secret_key=any -buckets=foo -user=me -actions=Read,Write,List,Tagging,Admin -apply
 {
@@ -17290,7 +26808,8 @@ endpoint = s3.us-east-1.lyvecloud.seagate.com</code></pre>
     }
   ]
 }</code></pre>
-<p>To use rclone with SeaweedFS, above configuration should end up with something like this in your config:</p>
+<p>To use rclone with SeaweedFS, above configuration should end up with
+something like this in your config:</p>
 <pre><code>[seaweedfs_s3]
 type = s3
 provider = SeaweedFS
@@ -17300,8 +26819,13 @@ endpoint = localhost:8333</code></pre>
 <p>So once set up, for example to copy files into a bucket</p>
 <pre><code>rclone copy /path/to/files seaweedfs_s3:foo</code></pre>
 <h3 id="wasabi">Wasabi</h3>
-<p><a href="https://wasabi.com">Wasabi</a> is a cloud-based object storage service for a broad range of applications and use cases. Wasabi is designed for individuals and organizations that require a high-performance, reliable, and secure data storage infrastructure at minimal cost.</p>
-<p>Wasabi provides an S3 interface which can be configured for use with rclone like this.</p>
+<p><a href="https://wasabi.com">Wasabi</a> is a cloud-based object
+storage service for a broad range of applications and use cases. Wasabi
+is designed for individuals and organizations that require a
+high-performance, reliable, and secure data storage infrastructure at
+minimal cost.</p>
+<p>Wasabi provides an S3 interface which can be configured for use with
+rclone like this.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -17399,7 +26923,9 @@ acl =
 server_side_encryption =
 storage_class =</code></pre>
 <h3 id="alibaba-oss">Alibaba OSS</h3>
-<p>Here is an example of making an <a href="https://www.alibabacloud.com/product/oss/">Alibaba Cloud (Aliyun) OSS</a> configuration. First run:</p>
+<p>Here is an example of making an <a
+href="https://www.alibabacloud.com/product/oss/">Alibaba Cloud (Aliyun)
+OSS</a> configuration. First run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
 <pre><code>No remotes found, make a new one?
@@ -17500,8 +27026,12 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<h3 id="china-mobile-ecloud-eos">China Mobile Ecloud Elastic Object Storage (EOS)</h3>
-<p>Here is an example of making an <a href="https:///ecloud.10086.cn/home/product-introduction/eos/">China Mobile Ecloud Elastic Object Storage (EOS)</a> configuration. First run:</p>
+<h3 id="china-mobile-ecloud-eos">China Mobile Ecloud Elastic Object
+Storage (EOS)</h3>
+<p>Here is an example of making an <a
+href="https:///ecloud.10086.cn/home/product-introduction/eos/">China
+Mobile Ecloud Elastic Object Storage (EOS)</a> configuration. First
+run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
 <pre><code>No remotes found, make a new one?
@@ -17743,10 +27273,13 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
 <h3 id="leviia">Leviia Cloud Object Storage</h3>
-<p><a href="https://www.leviia.com/object-storage/">Leviia Object Storage</a>, backup and secure your data in a 100% French cloud, independent of GAFAM..</p>
+<p><a href="https://www.leviia.com/object-storage/">Leviia Object
+Storage</a>, backup and secure your data in a 100% French cloud,
+independent of GAFAM..</p>
 <p>To configure access to Leviia, follow the steps below:</p>
 <ol type="1">
-<li>Run <code>rclone config</code> and select <code>n</code> for a new remote.</li>
+<li>Run <code>rclone config</code> and select <code>n</code> for a new
+remote.</li>
 </ol>
 <pre><code>rclone config
 No remotes found, make a new one?
@@ -17755,7 +27288,8 @@ s) Set configuration password
 q) Quit config
 n/s/q&gt; n</code></pre>
 <ol start="2" type="1">
-<li>Give the name of the configuration. For example, name it 'leviia'.</li>
+<li>Give the name of the configuration. For example, name it
+'leviia'.</li>
 </ol>
 <pre><code>name&gt; leviia</code></pre>
 <ol start="3" type="1">
@@ -17845,7 +27379,9 @@ Name                 Type
 ====                 ====
 leviia                s3</code></pre>
 <h3 id="liara-cloud">Liara</h3>
-<p>Here is an example of making a <a href="https://liara.ir/landing/object-storage">Liara Object Storage</a> configuration. First run:</p>
+<p>Here is an example of making a <a
+href="https://liara.ir/landing/object-storage">Liara Object Storage</a>
+configuration. First run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
 <pre><code>No remotes found, make a new one?
@@ -17934,7 +27470,9 @@ acl =
 server_side_encryption =
 storage_class =</code></pre>
 <h3 id="linode">Linode</h3>
-<p>Here is an example of making a <a href="https://www.linode.com/products/object-storage/">Linode Object Storage</a> configuration. First run:</p>
+<p>Here is an example of making a <a
+href="https://www.linode.com/products/object-storage/">Linode Object
+Storage</a> configuration. First run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
 <pre><code>No remotes found, make a new one?
@@ -18055,7 +27593,9 @@ access_key_id = ACCESS_KEY
 secret_access_key = SECRET_ACCESS_KEY
 endpoint = eu-central-1.linodeobjects.com</code></pre>
 <h3 id="magalu">Magalu</h3>
-<p>Here is an example of making a <a href="https://magalu.cloud/object-storage/">Magalu Object Storage</a> configuration. First run:</p>
+<p>Here is an example of making a <a
+href="https://magalu.cloud/object-storage/">Magalu Object Storage</a>
+configuration. First run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
 <pre><code>No remotes found, make a new one?
@@ -18160,8 +27700,15 @@ access_key_id = ACCESS_KEY
 secret_access_key = SECRET_ACCESS_KEY
 endpoint = br-ne1.magaluobjects.com</code></pre>
 <h3 id="arvan-cloud">ArvanCloud</h3>
-<p><a href="https://www.arvancloud.com/en/products/cloud-storage">ArvanCloud</a> ArvanCloud Object Storage goes beyond the limited traditional file storage. It gives you access to backup and archived files and allows sharing. Files like profile image in the app, images sent by users or scanned documents can be stored securely and easily in our Object Storage service.</p>
-<p>ArvanCloud provides an S3 interface which can be configured for use with rclone like this.</p>
+<p><a
+href="https://www.arvancloud.com/en/products/cloud-storage">ArvanCloud</a>
+ArvanCloud Object Storage goes beyond the limited traditional file
+storage. It gives you access to backup and archived files and allows
+sharing. Files like profile image in the app, images sent by users or
+scanned documents can be stored securely and easily in our Object
+Storage service.</p>
+<p>ArvanCloud provides an S3 interface which can be configured for use
+with rclone like this.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -18255,10 +27802,14 @@ acl =
 server_side_encryption =
 storage_class =</code></pre>
 <h3 id="tencent-cos">Tencent COS</h3>
-<p><a href="https://intl.cloud.tencent.com/product/cos">Tencent Cloud Object Storage (COS)</a> is a distributed storage service offered by Tencent Cloud for unstructured data. It is secure, stable, massive, convenient, low-delay and low-cost.</p>
+<p><a href="https://intl.cloud.tencent.com/product/cos">Tencent Cloud
+Object Storage (COS)</a> is a distributed storage service offered by
+Tencent Cloud for unstructured data. It is secure, stable, massive,
+convenient, low-delay and low-cost.</p>
 <p>To configure access to Tencent COS, follow the steps below:</p>
 <ol type="1">
-<li>Run <code>rclone config</code> and select <code>n</code> for a new remote.</li>
+<li>Run <code>rclone config</code> and select <code>n</code> for a new
+remote.</li>
 </ol>
 <pre><code>rclone config
 No remotes found, make a new one?
@@ -18311,7 +27862,8 @@ Leave blank for anonymous access or runtime credentials.
 Enter a string value. Press Enter for the default (&quot;&quot;).
 secret_access_key&gt; xxxxxxxxxxx</code></pre>
 <ol start="6" type="1">
-<li>Select endpoint for Tencent COS. This is the standard endpoint for different region.</li>
+<li>Select endpoint for Tencent COS. This is the standard endpoint for
+different region.</li>
 </ol>
 <pre><code> 1 / Beijing Region.
    \ &quot;cos.ap-beijing.myqcloud.com&quot;
@@ -18366,10 +27918,15 @@ Name                 Type
 ====                 ====
 cos                  s3</code></pre>
 <h3 id="netease-nos">Netease NOS</h3>
-<p>For Netease NOS configure as per the configurator <code>rclone config</code> setting the provider <code>Netease</code>. This will automatically set <code>force_path_style = false</code> which is necessary for it to run properly.</p>
+<p>For Netease NOS configure as per the configurator
+<code>rclone config</code> setting the provider <code>Netease</code>.
+This will automatically set <code>force_path_style = false</code> which
+is necessary for it to run properly.</p>
 <h3 id="petabox">Petabox</h3>
-<p>Here is an example of making a <a href="https://petabox.io/">Petabox</a> configuration. First run:</p>
-<div class="sourceCode" id="cb969"><pre class="sourceCode bash"><code class="sourceCode bash"><span id="cb969-1"><a href="#cb969-1" aria-hidden="true"></a><span class="ex">rclone</span> config</span></code></pre></div>
+<p>Here is an example of making a <a
+href="https://petabox.io/">Petabox</a> configuration. First run:</p>
+<div class="sourceCode" id="cb969"><pre
+class="sourceCode bash"><code class="sourceCode bash"><span id="cb969-1"><a href="#cb969-1" aria-hidden="true" tabindex="-1"></a><span class="ex">rclone</span> config</span></code></pre></div>
 <p>This will guide you through an interactive setup process.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
@@ -18514,8 +28071,12 @@ secret_access_key = YOUR_SECRET_ACCESS_KEY
 region = us-east-1
 endpoint = s3.petabox.io</code></pre>
 <h3 id="storj">Storj</h3>
-<p>Storj is a decentralized cloud storage which can be used through its native protocol or an S3 compatible gateway.</p>
-<p>The S3 compatible gateway is configured using <code>rclone config</code> with a type of <code>s3</code> and with a provider name of <code>Storj</code>. Here is an example run of the configurator.</p>
+<p>Storj is a decentralized cloud storage which can be used through its
+native protocol or an S3 compatible gateway.</p>
+<p>The S3 compatible gateway is configured using
+<code>rclone config</code> with a type of <code>s3</code> and with a
+provider name of <code>Storj</code>. Here is an example run of the
+configurator.</p>
 <pre><code>Type of storage to configure.
 Storage&gt; s3
 Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
@@ -18552,45 +28113,101 @@ Edit advanced config?
 y) Yes
 n) No (default)
 y/n&gt; n</code></pre>
-<p>Note that s3 credentials are generated when you <a href="https://docs.storj.io/dcs/api-reference/s3-compatible-gateway#usage">create an access grant</a>.</p>
+<p>Note that s3 credentials are generated when you <a
+href="https://docs.storj.io/dcs/api-reference/s3-compatible-gateway#usage">create
+an access grant</a>.</p>
 <h4 id="backend-quirks">Backend quirks</h4>
 <ul>
-<li><code>--chunk-size</code> is forced to be 64 MiB or greater. This will use more memory than the default of 5 MiB.</li>
-<li>Server side copy is disabled as it isn't currently supported in the gateway.</li>
+<li><code>--chunk-size</code> is forced to be 64 MiB or greater. This
+will use more memory than the default of 5 MiB.</li>
+<li>Server side copy is disabled as it isn't currently supported in the
+gateway.</li>
 <li>GetTier and SetTier are not supported.</li>
 </ul>
 <h4 id="backend-bugs">Backend bugs</h4>
-<p>Due to <a href="https://github.com/storj/gateway-mt/issues/39">issue #39</a> uploading multipart files via the S3 gateway causes them to lose their metadata. For rclone's purpose this means that the modification time is not stored, nor is any MD5SUM (if one is available from the source).</p>
+<p>Due to <a href="https://github.com/storj/gateway-mt/issues/39">issue
+#39</a> uploading multipart files via the S3 gateway causes them to lose
+their metadata. For rclone's purpose this means that the modification
+time is not stored, nor is any MD5SUM (if one is available from the
+source).</p>
 <p>This has the following consequences:</p>
 <ul>
-<li>Using <code>rclone rcat</code> will fail as the medatada doesn't match after upload</li>
-<li>Uploading files with <code>rclone mount</code> will fail for the same reason
+<li>Using <code>rclone rcat</code> will fail as the medatada doesn't
+match after upload</li>
+<li>Uploading files with <code>rclone mount</code> will fail for the
+same reason
 <ul>
-<li>This can worked around by using <code>--vfs-cache-mode writes</code> or <code>--vfs-cache-mode full</code> or setting <code>--s3-upload-cutoff</code> large</li>
+<li>This can worked around by using <code>--vfs-cache-mode writes</code>
+or <code>--vfs-cache-mode full</code> or setting
+<code>--s3-upload-cutoff</code> large</li>
 </ul></li>
 <li>Files uploaded via a multipart upload won't have their modtimes
 <ul>
-<li>This will mean that <code>rclone sync</code> will likely keep trying to upload files bigger than <code>--s3-upload-cutoff</code></li>
-<li>This can be worked around with <code>--checksum</code> or <code>--size-only</code> or setting <code>--s3-upload-cutoff</code> large</li>
-<li>The maximum value for <code>--s3-upload-cutoff</code> is 5GiB though</li>
+<li>This will mean that <code>rclone sync</code> will likely keep trying
+to upload files bigger than <code>--s3-upload-cutoff</code></li>
+<li>This can be worked around with <code>--checksum</code> or
+<code>--size-only</code> or setting <code>--s3-upload-cutoff</code>
+large</li>
+<li>The maximum value for <code>--s3-upload-cutoff</code> is 5GiB
+though</li>
 </ul></li>
 </ul>
-<p>One general purpose workaround is to set <code>--s3-upload-cutoff 5G</code>. This means that rclone will upload files smaller than 5GiB as single parts. Note that this can be set in the config file with <code>upload_cutoff = 5G</code> or configured in the advanced settings. If you regularly transfer files larger than 5G then using <code>--checksum</code> or <code>--size-only</code> in <code>rclone sync</code> is the recommended workaround.</p>
-<h4 id="comparison-with-the-native-protocol">Comparison with the native protocol</h4>
-<p>Use the <a href="/storj">the native protocol</a> to take advantage of client-side encryption as well as to achieve the best possible download performance. Uploads will be erasure-coded locally, thus a 1gb upload will result in 2.68gb of data being uploaded to storage nodes across the network.</p>
-<p>Use this backend and the S3 compatible Hosted Gateway to increase upload performance and reduce the load on your systems and network. Uploads will be encrypted and erasure-coded server-side, thus a 1GB upload will result in only in 1GB of data being uploaded to storage nodes across the network.</p>
-<p>For more detailed comparison please check the documentation of the <a href="/storj">storj</a> backend.</p>
+<p>One general purpose workaround is to set
+<code>--s3-upload-cutoff 5G</code>. This means that rclone will upload
+files smaller than 5GiB as single parts. Note that this can be set in
+the config file with <code>upload_cutoff = 5G</code> or configured in
+the advanced settings. If you regularly transfer files larger than 5G
+then using <code>--checksum</code> or <code>--size-only</code> in
+<code>rclone sync</code> is the recommended workaround.</p>
+<h4 id="comparison-with-the-native-protocol">Comparison with the native
+protocol</h4>
+<p>Use the <a href="/storj">the native protocol</a> to take advantage of
+client-side encryption as well as to achieve the best possible download
+performance. Uploads will be erasure-coded locally, thus a 1gb upload
+will result in 2.68gb of data being uploaded to storage nodes across the
+network.</p>
+<p>Use this backend and the S3 compatible Hosted Gateway to increase
+upload performance and reduce the load on your systems and network.
+Uploads will be encrypted and erasure-coded server-side, thus a 1GB
+upload will result in only in 1GB of data being uploaded to storage
+nodes across the network.</p>
+<p>For more detailed comparison please check the documentation of the <a
+href="/storj">storj</a> backend.</p>
 <h2 id="memory-usage-memory">Memory usage {memory}</h2>
-<p>The most common cause of rclone using lots of memory is a single directory with millions of files in. Despite s3 not really having the concepts of directories, rclone does the sync on a directory by directory basis to be compatible with normal filing systems.</p>
-<p>Rclone loads each directory into memory as rclone objects. Each rclone object takes 0.5k-1k of memory, so approximately 1GB per 1,000,000 files, and the sync for that directory does not begin until it is entirely loaded in memory. So the sync can take a long time to start for large directories.</p>
-<p>To sync a directory with 100,000,000 files in you would need approximately 100 GB of memory. At some point the amount of memory becomes difficult to provide so there is <a href="https://github.com/rclone/rclone/wiki/Big-syncs-with-millions-of-files">a workaround for this</a> which involves a bit of scripting.</p>
-<p>At some point rclone will gain a sync mode which is effectively this workaround but built in to rclone.</p>
+<p>The most common cause of rclone using lots of memory is a single
+directory with millions of files in. Despite s3 not really having the
+concepts of directories, rclone does the sync on a directory by
+directory basis to be compatible with normal filing systems.</p>
+<p>Rclone loads each directory into memory as rclone objects. Each
+rclone object takes 0.5k-1k of memory, so approximately 1GB per
+1,000,000 files, and the sync for that directory does not begin until it
+is entirely loaded in memory. So the sync can take a long time to start
+for large directories.</p>
+<p>To sync a directory with 100,000,000 files in you would need
+approximately 100 GB of memory. At some point the amount of memory
+becomes difficult to provide so there is <a
+href="https://github.com/rclone/rclone/wiki/Big-syncs-with-millions-of-files">a
+workaround for this</a> which involves a bit of scripting.</p>
+<p>At some point rclone will gain a sync mode which is effectively this
+workaround but built in to rclone.</p>
 <h2 id="limitations-6">Limitations</h2>
-<p><code>rclone about</code> is not supported by the S3 backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the S3 backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h3 id="synology-c2">Synology C2 Object Storage</h3>
-<p><a href="https://c2.synology.com/en-global/object-storage/overview">Synology C2 Object Storage</a> provides a secure, S3-compatible, and cost-effective cloud storage solution without API request, download fees, and deletion penalty.</p>
-<p>The S3 compatible gateway is configured using <code>rclone config</code> with a type of <code>s3</code> and with a provider name of <code>Synology</code>. Here is an example run of the configurator.</p>
+<p><a
+href="https://c2.synology.com/en-global/object-storage/overview">Synology
+C2 Object Storage</a> provides a secure, S3-compatible, and
+cost-effective cloud storage solution without API request, download
+fees, and deletion penalty.</p>
+<p>The S3 compatible gateway is configured using
+<code>rclone config</code> with a type of <code>s3</code> and with a
+provider name of <code>Synology</code>. Here is an example run of the
+configurator.</p>
 <p>First run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
@@ -18709,12 +28326,19 @@ d) Delete this remote
 
 y/e/d&gt; y</code></pre>
 <h1 id="backblaze-b2">Backblaze B2</h1>
-<p>B2 is <a href="https://www.backblaze.com/cloud-storage">Backblaze's cloud storage system</a>.</p>
-<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
+<p>B2 is <a href="https://www.backblaze.com/cloud-storage">Backblaze's
+cloud storage system</a>.</p>
+<p>Paths are specified as <code>remote:bucket</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
 <h2 id="configuration-3">Configuration</h2>
 <p>Here is an example of making a b2 configuration. First run</p>
 <pre><code>rclone config</code></pre>
-<p>This will guide you through an interactive setup process. To authenticate you will either need your Account ID (a short hex number) and Master Application Key (a long hex number) OR an Application Key, which is the recommended method. See below for further details on generating and using an Application Key.</p>
+<p>This will guide you through an interactive setup process. To
+authenticate you will either need your Account ID (a short hex number)
+and Master Application Key (a long hex number) OR an Application Key,
+which is the recommended method. See below for further details on
+generating and using an Application Key.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 q) Quit config
@@ -18745,27 +28369,49 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>This remote is called <code>remote</code> and can now be used like this</p>
+<p>This remote is called <code>remote</code> and can now be used like
+this</p>
 <p>See all buckets</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>Create a new bucket</p>
 <pre><code>rclone mkdir remote:bucket</code></pre>
 <p>List the contents of a bucket</p>
 <pre><code>rclone ls remote:bucket</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote bucket, deleting any excess files in the bucket.</p>
+<p>Sync <code>/home/local/directory</code> to the remote bucket,
+deleting any excess files in the bucket.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:bucket</code></pre>
 <h3 id="application-keys">Application Keys</h3>
-<p>B2 supports multiple <a href="https://www.backblaze.com/docs/cloud-storage-application-keys">Application Keys for different access permission to B2 Buckets</a>.</p>
-<p>You can use these with rclone too; you will need to use rclone version 1.43 or later.</p>
-<p>Follow Backblaze's docs to create an Application Key with the required permission and add the <code>applicationKeyId</code> as the <code>account</code> and the <code>Application Key</code> itself as the <code>key</code>.</p>
-<p>Note that you must put the <em>applicationKeyId</em> as the <code>account</code> – you can't use the master Account ID. If you try then B2 will return 401 errors.</p>
+<p>B2 supports multiple <a
+href="https://www.backblaze.com/docs/cloud-storage-application-keys">Application
+Keys for different access permission to B2 Buckets</a>.</p>
+<p>You can use these with rclone too; you will need to use rclone
+version 1.43 or later.</p>
+<p>Follow Backblaze's docs to create an Application Key with the
+required permission and add the <code>applicationKeyId</code> as the
+<code>account</code> and the <code>Application Key</code> itself as the
+<code>key</code>.</p>
+<p>Note that you must put the <em>applicationKeyId</em> as the
+<code>account</code> – you can't use the master Account ID. If you try
+then B2 will return 401 errors.</p>
 <h3 id="fast-list-1">--fast-list</h3>
-<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
+<p>This remote supports <code>--fast-list</code> which allows you to use
+fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details.</p>
 <h3 id="modification-times-2">Modification times</h3>
-<p>The modification time is stored as metadata on the object as <code>X-Bz-Info-src_last_modified_millis</code> as milliseconds since 1970-01-01 in the Backblaze standard. Other tools should be able to use this as a modified time.</p>
-<p>Modified times are used in syncing and are fully supported. Note that if a modification time needs to be updated on an object then it will create a new version of the object.</p>
-<h3 id="restricted-filename-characters-2">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>The modification time is stored as metadata on the object as
+<code>X-Bz-Info-src_last_modified_millis</code> as milliseconds since
+1970-01-01 in the Backblaze standard. Other tools should be able to use
+this as a modified time.</p>
+<p>Modified times are used in syncing and are fully supported. Note that
+if a modification time needs to be updated on an object then it will
+create a new version of the object.</p>
+<h3 id="restricted-filename-characters-2">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -18782,30 +28428,91 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<p>Note that in 2020-05 Backblaze started allowing  characters in file names. Rclone hasn't changed its encoding as this could cause syncs to re-transfer files. If you want rclone not to replace  then see the <code>--b2-encoding</code> flag below and remove the <code>BackSlash</code> from the string. This can be set in the config.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<p>Note that in 2020-05 Backblaze started allowing  characters in file
+names. Rclone hasn't changed its encoding as this could cause syncs to
+re-transfer files. If you want rclone not to replace  then see the
+<code>--b2-encoding</code> flag below and remove the
+<code>BackSlash</code> from the string. This can be set in the
+config.</p>
 <h3 id="sha1-checksums">SHA1 checksums</h3>
-<p>The SHA1 checksums of the files are checked on upload and download and will be used in the syncing process.</p>
-<p>Large files (bigger than the limit in <code>--b2-upload-cutoff</code>) which are uploaded in chunks will store their SHA1 on the object as <code>X-Bz-Info-large_file_sha1</code> as recommended by Backblaze.</p>
-<p>For a large file to be uploaded with an SHA1 checksum, the source needs to support SHA1 checksums. The local disk supports SHA1 checksums so large file transfers from local disk will have an SHA1. See <a href="https://rclone.org/overview/#features">the overview</a> for exactly which remotes support SHA1.</p>
-<p>Sources which don't support SHA1, in particular <code>crypt</code> will upload large files without SHA1 checksums. This may be fixed in the future (see <a href="https://github.com/rclone/rclone/issues/1767">#1767</a>).</p>
-<p>Files sizes below <code>--b2-upload-cutoff</code> will always have an SHA1 regardless of the source.</p>
+<p>The SHA1 checksums of the files are checked on upload and download
+and will be used in the syncing process.</p>
+<p>Large files (bigger than the limit in
+<code>--b2-upload-cutoff</code>) which are uploaded in chunks will store
+their SHA1 on the object as <code>X-Bz-Info-large_file_sha1</code> as
+recommended by Backblaze.</p>
+<p>For a large file to be uploaded with an SHA1 checksum, the source
+needs to support SHA1 checksums. The local disk supports SHA1 checksums
+so large file transfers from local disk will have an SHA1. See <a
+href="https://rclone.org/overview/#features">the overview</a> for
+exactly which remotes support SHA1.</p>
+<p>Sources which don't support SHA1, in particular <code>crypt</code>
+will upload large files without SHA1 checksums. This may be fixed in the
+future (see <a
+href="https://github.com/rclone/rclone/issues/1767">#1767</a>).</p>
+<p>Files sizes below <code>--b2-upload-cutoff</code> will always have an
+SHA1 regardless of the source.</p>
 <h3 id="transfers">Transfers</h3>
-<p>Backblaze recommends that you do lots of transfers simultaneously for maximum speed. In tests from my SSD equipped laptop the optimum setting is about <code>--transfers 32</code> though higher numbers may be used for a slight speed improvement. The optimum number for you may vary depending on your hardware, how big the files are, how much you want to load your computer, etc. The default of <code>--transfers 4</code> is definitely too low for Backblaze B2 though.</p>
-<p>Note that uploading big files (bigger than 200 MiB by default) will use a 96 MiB RAM buffer by default. There can be at most <code>--transfers</code> of these in use at any moment, so this sets the upper limit on the memory used.</p>
+<p>Backblaze recommends that you do lots of transfers simultaneously for
+maximum speed. In tests from my SSD equipped laptop the optimum setting
+is about <code>--transfers 32</code> though higher numbers may be used
+for a slight speed improvement. The optimum number for you may vary
+depending on your hardware, how big the files are, how much you want to
+load your computer, etc. The default of <code>--transfers 4</code> is
+definitely too low for Backblaze B2 though.</p>
+<p>Note that uploading big files (bigger than 200 MiB by default) will
+use a 96 MiB RAM buffer by default. There can be at most
+<code>--transfers</code> of these in use at any moment, so this sets the
+upper limit on the memory used.</p>
 <h3 id="versions-1">Versions</h3>
-<p>The default setting of B2 is to keep old versions of files. This means when rclone uploads a new version of a file it creates a <a href="https://www.backblaze.com/docs/cloud-storage-file-versions">new version of it</a>. Likewise when you delete a file, the old version will be marked hidden and still be available.</p>
-<p>Whether B2 keeps old versions of files or not can be adjusted on a per bucket basis using the "Lifecycle settings" on the B2 control panel or when creating the bucket using the <a href="#b2-lifecycle">--b2-lifecycle</a> flag or after creation using the <a href="#lifecycle">rclone backend lifecycle</a> command.</p>
-<p>You may opt in to a "hard delete" of files with the <code>--b2-hard-delete</code> flag which permanently removes files on deletion instead of hiding them.</p>
-<p>Old versions of files, where available, are visible using the <code>--b2-versions</code> flag.</p>
-<p>It is also possible to view a bucket as it was at a certain point in time, using the <code>--b2-version-at</code> flag. This will show the file versions as they were at that time, showing files that have been deleted afterwards, and hiding files that were created since.</p>
-<p>If you wish to remove all the old versions, and unfinished large file uploads, then you can use the <code>rclone cleanup remote:bucket</code> command which will delete all the old versions of files, leaving the current ones intact. You can also supply a path and only old versions under that path will be deleted, e.g. <code>rclone cleanup remote:bucket/path/to/stuff</code>.</p>
-<p>Note that <code>cleanup</code> will remove partially uploaded files from the bucket if they are more than a day old. If you want more control over the expiry date then run <code>rclone backend cleanup b2:bucket -o max-age=1h</code> to remove all unfinished large file uploads older than one hour, leaving old versions intact.</p>
-<p>If you wish to remove all the old versions, leaving current files and unfinished large files intact, then you can use the <a href="#cleanup-hidden"><code>rclone backend cleanup-hidden remote:bucket</code></a> command. You can also supply a path and only old versions under that path will be deleted, e.g. <code>rclone backend cleanup-hidden remote:bucket/path/to/stuff</code>.</p>
-<p>When you <code>purge</code> a bucket, the current and the old versions will be deleted then the bucket will be deleted.</p>
-<p>However <code>delete</code> will cause the current versions of the files to become hidden old versions.</p>
-<p>Here is a session showing the listing and retrieval of an old version followed by a <code>cleanup</code> of the old versions.</p>
-<p>Show current version and all the versions with <code>--b2-versions</code> flag.</p>
+<p>The default setting of B2 is to keep old versions of files. This
+means when rclone uploads a new version of a file it creates a <a
+href="https://www.backblaze.com/docs/cloud-storage-file-versions">new
+version of it</a>. Likewise when you delete a file, the old version will
+be marked hidden and still be available.</p>
+<p>Whether B2 keeps old versions of files or not can be adjusted on a
+per bucket basis using the "Lifecycle settings" on the B2 control panel
+or when creating the bucket using the <a
+href="#b2-lifecycle">--b2-lifecycle</a> flag or after creation using the
+<a href="#lifecycle">rclone backend lifecycle</a> command.</p>
+<p>You may opt in to a "hard delete" of files with the
+<code>--b2-hard-delete</code> flag which permanently removes files on
+deletion instead of hiding them.</p>
+<p>Old versions of files, where available, are visible using the
+<code>--b2-versions</code> flag.</p>
+<p>It is also possible to view a bucket as it was at a certain point in
+time, using the <code>--b2-version-at</code> flag. This will show the
+file versions as they were at that time, showing files that have been
+deleted afterwards, and hiding files that were created since.</p>
+<p>If you wish to remove all the old versions, and unfinished large file
+uploads, then you can use the <code>rclone cleanup remote:bucket</code>
+command which will delete all the old versions of files, leaving the
+current ones intact. You can also supply a path and only old versions
+under that path will be deleted, e.g.
+<code>rclone cleanup remote:bucket/path/to/stuff</code>.</p>
+<p>Note that <code>cleanup</code> will remove partially uploaded files
+from the bucket if they are more than a day old. If you want more
+control over the expiry date then run
+<code>rclone backend cleanup b2:bucket -o max-age=1h</code> to remove
+all unfinished large file uploads older than one hour, leaving old
+versions intact.</p>
+<p>If you wish to remove all the old versions, leaving current files and
+unfinished large files intact, then you can use the <a
+href="#cleanup-hidden"><code>rclone backend cleanup-hidden remote:bucket</code></a>
+command. You can also supply a path and only old versions under that
+path will be deleted, e.g.
+<code>rclone backend cleanup-hidden remote:bucket/path/to/stuff</code>.</p>
+<p>When you <code>purge</code> a bucket, the current and the old
+versions will be deleted then the bucket will be deleted.</p>
+<p>However <code>delete</code> will cause the current versions of the
+files to become hidden old versions.</p>
+<p>Here is a session showing the listing and retrieval of an old version
+followed by a <code>cleanup</code> of the old versions.</p>
+<p>Show current version and all the versions with
+<code>--b2-versions</code> flag.</p>
 <pre><code>$ rclone -q ls b2:cleanup-test
         9 one.txt
 
@@ -18828,29 +28535,43 @@ $ rclone -q ls b2:cleanup-test
 $ rclone -q --b2-versions ls b2:cleanup-test
         9 one.txt</code></pre>
 <h4 id="versions-naming-caveat-1">Versions naming caveat</h4>
-<p>When using <code>--b2-versions</code> flag rclone is relying on the file name to work out whether the objects are versions or not. Versions' names are created by inserting timestamp between file name and its extension.</p>
+<p>When using <code>--b2-versions</code> flag rclone is relying on the
+file name to work out whether the objects are versions or not. Versions'
+names are created by inserting timestamp between file name and its
+extension.</p>
 <pre><code>        9 file.txt
         8 file-v2023-07-17-161032-000.txt
        16 file-v2023-06-15-141003-000.txt</code></pre>
-<p>If there are real files present with the same names as versions, then behaviour of <code>--b2-versions</code> can be unpredictable.</p>
+<p>If there are real files present with the same names as versions, then
+behaviour of <code>--b2-versions</code> can be unpredictable.</p>
 <h3 id="data-usage">Data usage</h3>
-<p>It is useful to know how many requests are sent to the server in different scenarios.</p>
+<p>It is useful to know how many requests are sent to the server in
+different scenarios.</p>
 <p>All copy commands send the following 4 requests:</p>
 <pre><code>/b2api/v1/b2_authorize_account
 /b2api/v1/b2_create_bucket
 /b2api/v1/b2_list_buckets
 /b2api/v1/b2_list_file_names</code></pre>
-<p>The <code>b2_list_file_names</code> request will be sent once for every 1k files in the remote path, providing the checksum and modification time of the listed files. As of version 1.33 issue <a href="https://github.com/rclone/rclone/issues/818">#818</a> causes extra requests to be sent when using B2 with Crypt. When a copy operation does not require any files to be uploaded, no more requests will be sent.</p>
-<p>Uploading files that do not require chunking, will send 2 requests per file upload:</p>
+<p>The <code>b2_list_file_names</code> request will be sent once for
+every 1k files in the remote path, providing the checksum and
+modification time of the listed files. As of version 1.33 issue <a
+href="https://github.com/rclone/rclone/issues/818">#818</a> causes extra
+requests to be sent when using B2 with Crypt. When a copy operation does
+not require any files to be uploaded, no more requests will be sent.</p>
+<p>Uploading files that do not require chunking, will send 2 requests
+per file upload:</p>
 <pre><code>/b2api/v1/b2_get_upload_url
 /b2api/v1/b2_upload_file/</code></pre>
-<p>Uploading files requiring chunking, will send 2 requests (one each to start and finish the upload) and another 2 requests for each chunk:</p>
+<p>Uploading files requiring chunking, will send 2 requests (one each to
+start and finish the upload) and another 2 requests for each chunk:</p>
 <pre><code>/b2api/v1/b2_start_large_file
 /b2api/v1/b2_get_upload_part_url
 /b2api/v1/b2_upload_part/
 /b2api/v1/b2_finish_large_file</code></pre>
 <h4 id="versions-2">Versions</h4>
-<p>Versions can be viewed with the <code>--b2-versions</code> flag. When it is set rclone will show and act on older versions of files. For example</p>
+<p>Versions can be viewed with the <code>--b2-versions</code> flag. When
+it is set rclone will show and act on older versions of files. For
+example</p>
 <p>Listing without <code>--b2-versions</code></p>
 <pre><code>$ rclone -q ls b2:cleanup-test
         9 one.txt</code></pre>
@@ -18860,17 +28581,23 @@ $ rclone -q --b2-versions ls b2:cleanup-test
         8 one-v2016-07-04-141032-000.txt
        16 one-v2016-07-04-141003-000.txt
        15 one-v2016-07-02-155621-000.txt</code></pre>
-<p>Showing that the current version is unchanged but older versions can be seen. These have the UTC date that they were uploaded to the server to the nearest millisecond appended to them.</p>
-<p>Note that when using <code>--b2-versions</code> no file write operations are permitted, so you can't upload files or delete them.</p>
+<p>Showing that the current version is unchanged but older versions can
+be seen. These have the UTC date that they were uploaded to the server
+to the nearest millisecond appended to them.</p>
+<p>Note that when using <code>--b2-versions</code> no file write
+operations are permitted, so you can't upload files or delete them.</p>
 <h3 id="b2-and-rclone-link">B2 and rclone link</h3>
-<p>Rclone supports generating file share links for private B2 buckets. They can either be for a file for example:</p>
+<p>Rclone supports generating file share links for private B2 buckets.
+They can either be for a file for example:</p>
 <pre><code>./rclone link B2:bucket/path/to/file.txt
 https://f002.backblazeb2.com/file/bucket/path/to/file.txt?Authorization=xxxxxxxx
 </code></pre>
 <p>or if run on a directory you will get:</p>
 <pre><code>./rclone link B2:bucket/path
 https://f002.backblazeb2.com/file/bucket/path?Authorization=xxxxxxxx</code></pre>
-<p>you can then use the authorization token (the part of the url from the <code>?Authorization=</code> on) on any file path under that directory. For example:</p>
+<p>you can then use the authorization token (the part of the url from
+the <code>?Authorization=</code> on) on any file path under that
+directory. For example:</p>
 <pre><code>https://f002.backblazeb2.com/file/bucket/path/to/file1?Authorization=xxxxxxxx
 https://f002.backblazeb2.com/file/bucket/path/file2?Authorization=xxxxxxxx
 https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxxx
@@ -18918,13 +28645,17 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-test-mode">--b2-test-mode</h4>
 <p>A flag string for X-Bz-Test-Mode header for debugging.</p>
-<p>This is for debugging purposes only. Setting it to one of the strings below will cause b2 to return specific errors:</p>
+<p>This is for debugging purposes only. Setting it to one of the strings
+below will cause b2 to return specific errors:</p>
 <ul>
 <li>"fail_some_uploads"</li>
 <li>"expire_some_account_authorization_tokens"</li>
 <li>"force_cap_exceeded"</li>
 </ul>
-<p>These will be set in the "X-Bz-Test-Mode" header which is documented in the <a href="https://www.backblaze.com/docs/cloud-storage-integration-checklist">b2 integrations checklist</a>.</p>
+<p>These will be set in the "X-Bz-Test-Mode" header which is documented
+in the <a
+href="https://www.backblaze.com/docs/cloud-storage-integration-checklist">b2
+integrations checklist</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: test_mode</li>
@@ -18934,7 +28665,8 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-versions">--b2-versions</h4>
 <p>Include old versions in directory listings.</p>
-<p>Note that when using this no file write operations are permitted, so you can't upload files or delete them.</p>
+<p>Note that when using this no file write operations are permitted, so
+you can't upload files or delete them.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: versions</li>
@@ -18944,7 +28676,8 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-version-at">--b2-version-at</h4>
 <p>Show file versions as they were at the specified time.</p>
-<p>Note that when using this no file write operations are permitted, so you can't upload files or delete them.</p>
+<p>Note that when using this no file write operations are permitted, so
+you can't upload files or delete them.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: version_at</li>
@@ -18954,7 +28687,8 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-upload-cutoff">--b2-upload-cutoff</h4>
 <p>Cutoff for switching to chunked upload.</p>
-<p>Files above this size will be uploaded in chunks of "--b2-chunk-size".</p>
+<p>Files above this size will be uploaded in chunks of
+"--b2-chunk-size".</p>
 <p>This value should be set no larger than 4.657 GiB (== 5 GB).</p>
 <p>Properties:</p>
 <ul>
@@ -18965,7 +28699,8 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-copy-cutoff">--b2-copy-cutoff</h4>
 <p>Cutoff for switching to multipart copy.</p>
-<p>Any files larger than this that need to be server-side copied will be copied in chunks of this size.</p>
+<p>Any files larger than this that need to be server-side copied will be
+copied in chunks of this size.</p>
 <p>The minimum is 0 and the maximum is 4.6 GiB.</p>
 <p>Properties:</p>
 <ul>
@@ -18977,7 +28712,8 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 <h4 id="b2-chunk-size">--b2-chunk-size</h4>
 <p>Upload chunk size.</p>
 <p>When uploading large files, chunk the file into this size.</p>
-<p>Must fit in memory. These chunks are buffered in memory and there might a maximum of "--transfers" chunks in progress at once.</p>
+<p>Must fit in memory. These chunks are buffered in memory and there
+might a maximum of "--transfers" chunks in progress at once.</p>
 <p>5,000,000 Bytes is the minimum size.</p>
 <p>Properties:</p>
 <ul>
@@ -18988,8 +28724,11 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-upload-concurrency">--b2-upload-concurrency</h4>
 <p>Concurrency for multipart uploads.</p>
-<p>This is the number of chunks of the same file that are uploaded concurrently.</p>
-<p>Note that chunks are stored in memory and there may be up to "--transfers" * "--b2-upload-concurrency" chunks stored at once in memory.</p>
+<p>This is the number of chunks of the same file that are uploaded
+concurrently.</p>
+<p>Note that chunks are stored in memory and there may be up to
+"--transfers" * "--b2-upload-concurrency" chunks stored at once in
+memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_concurrency</li>
@@ -18999,7 +28738,10 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-disable-checksum">--b2-disable-checksum</h4>
 <p>Disable checksums for large (&gt; upload cutoff) files.</p>
-<p>Normally rclone will calculate the SHA1 checksum of the input before uploading it so it can add it to metadata on the object. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
+<p>Normally rclone will calculate the SHA1 checksum of the input before
+uploading it so it can add it to metadata on the object. This is great
+for data integrity checking but can cause long delays for large files to
+start uploading.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_checksum</li>
@@ -19009,9 +28751,17 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-download-url">--b2-download-url</h4>
 <p>Custom endpoint for downloads.</p>
-<p>This is usually set to a Cloudflare CDN URL as Backblaze offers free egress for data downloaded through the Cloudflare network. Rclone works with private buckets by sending an "Authorization" header. If the custom endpoint rewrites the requests for authentication, e.g., in Cloudflare Workers, this header needs to be handled properly. Leave blank if you want to use the endpoint provided by Backblaze.</p>
-<p>The URL provided here SHOULD have the protocol and SHOULD NOT have a trailing slash or specify the /file/bucket subpath as rclone will request files with "{download_url}/file/{bucket_name}/{path}".</p>
-<p>Example: &gt; https://mysubdomain.mydomain.tld (No trailing "/", "file" or "bucket")</p>
+<p>This is usually set to a Cloudflare CDN URL as Backblaze offers free
+egress for data downloaded through the Cloudflare network. Rclone works
+with private buckets by sending an "Authorization" header. If the custom
+endpoint rewrites the requests for authentication, e.g., in Cloudflare
+Workers, this header needs to be handled properly. Leave blank if you
+want to use the endpoint provided by Backblaze.</p>
+<p>The URL provided here SHOULD have the protocol and SHOULD NOT have a
+trailing slash or specify the /file/bucket subpath as rclone will
+request files with "{download_url}/file/{bucket_name}/{path}".</p>
+<p>Example: &gt; https://mysubdomain.mydomain.tld (No trailing "/",
+"file" or "bucket")</p>
 <p>Properties:</p>
 <ul>
 <li>Config: download_url</li>
@@ -19020,8 +28770,11 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 <li>Required: false</li>
 </ul>
 <h4 id="b2-download-auth-duration">--b2-download-auth-duration</h4>
-<p>Time before the public link authorization token will expire in s or suffix ms|s|m|h|d.</p>
-<p>This is used in combination with "rclone link" for making files accessible to the public and sets the duration before the download authorization token will expire.</p>
+<p>Time before the public link authorization token will expire in s or
+suffix ms|s|m|h|d.</p>
+<p>This is used in combination with "rclone link" for making files
+accessible to the public and sets the duration before the download
+authorization token will expire.</p>
 <p>The minimum value is 1 second. The maximum value is one week.</p>
 <p>Properties:</p>
 <ul>
@@ -19031,7 +28784,8 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 <li>Default: 1w</li>
 </ul>
 <h4 id="b2-memory-pool-flush-time">--b2-memory-pool-flush-time</h4>
-<p>How often internal memory buffer pools will be flushed. (no longer used)</p>
+<p>How often internal memory buffer pools will be flushed. (no longer
+used)</p>
 <p>Properties:</p>
 <ul>
 <li>Config: memory_pool_flush_time</li>
@@ -19040,7 +28794,8 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 <li>Default: 1m0s</li>
 </ul>
 <h4 id="b2-memory-pool-use-mmap">--b2-memory-pool-use-mmap</h4>
-<p>Whether to use mmap buffers in internal memory pool. (no longer used)</p>
+<p>Whether to use mmap buffers in internal memory pool. (no longer
+used)</p>
 <p>Properties:</p>
 <ul>
 <li>Config: memory_pool_use_mmap</li>
@@ -19049,13 +28804,23 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 <li>Default: false</li>
 </ul>
 <h4 id="b2-lifecycle">--b2-lifecycle</h4>
-<p>Set the number of days deleted files should be kept when creating a bucket.</p>
-<p>On bucket creation, this parameter is used to create a lifecycle rule for the entire bucket.</p>
-<p>If lifecycle is 0 (the default) it does not create a lifecycle rule so the default B2 behaviour applies. This is to create versions of files on delete and overwrite and to keep them indefinitely.</p>
-<p>If lifecycle is &gt;0 then it creates a single rule setting the number of days before a file that is deleted or overwritten is deleted permanently. This is known as daysFromHidingToDeleting in the b2 docs.</p>
+<p>Set the number of days deleted files should be kept when creating a
+bucket.</p>
+<p>On bucket creation, this parameter is used to create a lifecycle rule
+for the entire bucket.</p>
+<p>If lifecycle is 0 (the default) it does not create a lifecycle rule
+so the default B2 behaviour applies. This is to create versions of files
+on delete and overwrite and to keep them indefinitely.</p>
+<p>If lifecycle is &gt;0 then it creates a single rule setting the
+number of days before a file that is deleted or overwritten is deleted
+permanently. This is known as daysFromHidingToDeleting in the b2
+docs.</p>
 <p>The minimum value for this parameter is 1 day.</p>
-<p>You can also enable hard_delete in the config also which will mean deletions won't cause versions but overwrites will still cause versions to be made.</p>
-<p>See: <a href="#lifecycle">rclone backend lifecycle</a> for setting lifecycles after bucket creation.</p>
+<p>You can also enable hard_delete in the config also which will mean
+deletions won't cause versions but overwrites will still cause versions
+to be made.</p>
+<p>See: <a href="#lifecycle">rclone backend lifecycle</a> for setting
+lifecycles after bucket creation.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: lifecycle</li>
@@ -19065,7 +28830,8 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 </ul>
 <h4 id="b2-encoding">--b2-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -19087,12 +28853,16 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="lifecycle">lifecycle</h3>
 <p>Read or set the lifecycle for a bucket</p>
 <pre><code>rclone backend lifecycle remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command can be used to read or set the lifecycle for a bucket.</p>
+<p>This command can be used to read or set the lifecycle for a
+bucket.</p>
 <p>Usage Examples:</p>
 <p>To show the current lifecycle rules:</p>
 <pre><code>rclone backend lifecycle b2:bucket</code></pre>
@@ -19104,25 +28874,34 @@ https://f002.backblazeb2.com/file/bucket/path/folder/file3?Authorization=xxxxxxx
         &quot;fileNamePrefix&quot;: &quot;&quot;
     }
 ]</code></pre>
-<p>If there are no lifecycle rules (the default) then it will just return [].</p>
+<p>If there are no lifecycle rules (the default) then it will just
+return [].</p>
 <p>To reset the current lifecycle rules:</p>
 <pre><code>rclone backend lifecycle b2:bucket -o daysFromHidingToDeleting=30
 rclone backend lifecycle b2:bucket -o daysFromUploadingToHiding=5 -o daysFromHidingToDeleting=1</code></pre>
 <p>This will run and then print the new lifecycle rules as above.</p>
-<p>Rclone only lets you set lifecycles for the whole bucket with the fileNamePrefix = "".</p>
-<p>You can't disable versioning with B2. The best you can do is to set the daysFromHidingToDeleting to 1 day. You can enable hard_delete in the config also which will mean deletions won't cause versions but overwrites will still cause versions to be made.</p>
+<p>Rclone only lets you set lifecycles for the whole bucket with the
+fileNamePrefix = "".</p>
+<p>You can't disable versioning with B2. The best you can do is to set
+the daysFromHidingToDeleting to 1 day. You can enable hard_delete in the
+config also which will mean deletions won't cause versions but
+overwrites will still cause versions to be made.</p>
 <pre><code>rclone backend lifecycle b2:bucket -o daysFromHidingToDeleting=1</code></pre>
 <p>See: https://www.backblaze.com/docs/cloud-storage-lifecycle-rules</p>
 <p>Options:</p>
 <ul>
-<li>"daysFromHidingToDeleting": After a file has been hidden for this many days it is deleted. 0 is off.</li>
-<li>"daysFromUploadingToHiding": This many days after uploading a file is hidden</li>
+<li>"daysFromHidingToDeleting": After a file has been hidden for this
+many days it is deleted. 0 is off.</li>
+<li>"daysFromUploadingToHiding": This many days after uploading a file
+is hidden</li>
 </ul>
 <h3 id="cleanup-3">cleanup</h3>
 <p>Remove unfinished large file uploads.</p>
 <pre><code>rclone backend cleanup remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command removes unfinished large file uploads of age greater than max-age, which defaults to 24 hours.</p>
-<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
+<p>This command removes unfinished large file uploads of age greater
+than max-age, which defaults to 24 hours.</p>
+<p>Note that you can use --interactive/-i or --dry-run with this command
+to see what it would do.</p>
 <pre><code>rclone backend cleanup b2:bucket/path/to/object
 rclone backend cleanup -o max-age=7w b2:bucket/path/to/object</code></pre>
 <p>Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.</p>
@@ -19134,17 +28913,28 @@ rclone backend cleanup -o max-age=7w b2:bucket/path/to/object</code></pre>
 <p>Remove old versions of files.</p>
 <pre><code>rclone backend cleanup-hidden remote: [options] [&lt;arguments&gt;+]</code></pre>
 <p>This command removes any old hidden versions of files.</p>
-<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
+<p>Note that you can use --interactive/-i or --dry-run with this command
+to see what it would do.</p>
 <pre><code>rclone backend cleanup-hidden b2:bucket/path/to/dir</code></pre>
 <h2 id="limitations-7">Limitations</h2>
-<p><code>rclone about</code> is not supported by the B2 backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the B2 backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="box">Box</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<p>The initial setup for Box involves getting a token from Box which you can do either in your browser, or with a config.json downloaded from Box to use JWT authentication. <code>rclone config</code> walks you through it.</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<p>The initial setup for Box involves getting a token from Box which you
+can do either in your browser, or with a config.json downloaded from Box
+to use JWT authentication. <code>rclone config</code> walks you through
+it.</p>
 <h2 id="configuration-4">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -19203,8 +28993,14 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Box. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from Box. This only runs from the moment it opens
+your browser to the moment you get back the verification code. This is
+on <code>http://127.0.0.1:53682/</code> and this it may require you to
+unblock it temporarily if you are running a host firewall.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your Box</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -19212,22 +29008,37 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an Box directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="using-rclone-with-an-enterprise-account-with-sso">Using rclone with an Enterprise account with SSO</h3>
-<p>If you have an "Enterprise" account type with Box with single sign on (SSO), you need to create a password to use Box with rclone. This can be done at your Enterprise Box account by going to Settings, "Account" Tab, and then set the password in the "Authentication" field.</p>
-<p>Once you have done this, you can setup your Enterprise Box account using the same procedure detailed above in the, using the password you have just set.</p>
+<h3 id="using-rclone-with-an-enterprise-account-with-sso">Using rclone
+with an Enterprise account with SSO</h3>
+<p>If you have an "Enterprise" account type with Box with single sign on
+(SSO), you need to create a password to use Box with rclone. This can be
+done at your Enterprise Box account by going to Settings, "Account" Tab,
+and then set the password in the "Authentication" field.</p>
+<p>Once you have done this, you can setup your Enterprise Box account
+using the same procedure detailed above in the, using the password you
+have just set.</p>
 <h3 id="invalid-refresh-token">Invalid refresh token</h3>
-<p>According to the <a href="https://developer.box.com/v2.0/docs/oauth-20#section-6-using-the-access-and-refresh-tokens">box docs</a>:</p>
+<p>According to the <a
+href="https://developer.box.com/v2.0/docs/oauth-20#section-6-using-the-access-and-refresh-tokens">box
+docs</a>:</p>
 <blockquote>
 <p>Each refresh_token is valid for one use in 60 days.</p>
 </blockquote>
 <p>This means that if you</p>
 <ul>
 <li>Don't use the box remote for 60 days</li>
-<li>Copy the config file with a box refresh token in and use it in two places</li>
+<li>Copy the config file with a box refresh token in and use it in two
+places</li>
 <li>Get an error on a token refresh</li>
 </ul>
-<p>then rclone will return an error which includes the text <code>Invalid refresh token</code>.</p>
-<p>To fix this you will need to use oauth2 again to update the refresh token. You can use the methods in <a href="https://rclone.org/remote_setup/">the remote setup docs</a>, bearing in mind that if you use the copy the config file method, you should not use that remote on the computer you did the authentication on.</p>
+<p>then rclone will return an error which includes the text
+<code>Invalid refresh token</code>.</p>
+<p>To fix this you will need to use oauth2 again to update the refresh
+token. You can use the methods in <a
+href="https://rclone.org/remote_setup/">the remote setup docs</a>,
+bearing in mind that if you use the copy the config file method, you
+should not use that remote on the computer you did the authentication
+on.</p>
 <p>Here is how to do it.</p>
 <pre><code>$ rclone config
 Current remotes:
@@ -19288,11 +29099,19 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<h3 id="modification-times-and-hashes-2">Modification times and hashes</h3>
-<p>Box allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
-<p>Box supports SHA1 type hashes, so you can use the <code>--checksum</code> flag.</p>
-<h3 id="restricted-filename-characters-3">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<h3 id="modification-times-and-hashes-2">Modification times and
+hashes</h3>
+<p>Box allows modification times to be set on objects accurate to 1
+second. These will be used to detect whether objects need syncing or
+not.</p>
+<p>Box supports SHA1 type hashes, so you can use the
+<code>--checksum</code> flag.</p>
+<h3 id="restricted-filename-characters-3">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -19309,7 +29128,8 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
+<p>File names can also not end with the following characters. These only
+get replaced if they are the last character in the name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -19326,18 +29146,39 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="transfers-1">Transfers</h3>
-<p>For files above 50 MiB rclone will use a chunked transfer. Rclone will upload up to <code>--transfers</code> chunks at the same time (shared among all the multipart uploads). Chunks are buffered in memory and are normally 8 MiB so increasing <code>--transfers</code> will increase memory use.</p>
+<p>For files above 50 MiB rclone will use a chunked transfer. Rclone
+will upload up to <code>--transfers</code> chunks at the same time
+(shared among all the multipart uploads). Chunks are buffered in memory
+and are normally 8 MiB so increasing <code>--transfers</code> will
+increase memory use.</p>
 <h3 id="deleting-files">Deleting files</h3>
-<p>Depending on the enterprise settings for your user, the item will either be actually deleted from Box or moved to the trash.</p>
-<p>Emptying the trash is supported via the rclone however cleanup command however this deletes every trashed file and folder individually so it may take a very long time. Emptying the trash via the WebUI does not have this limitation so it is advised to empty the trash via the WebUI.</p>
+<p>Depending on the enterprise settings for your user, the item will
+either be actually deleted from Box or moved to the trash.</p>
+<p>Emptying the trash is supported via the rclone however cleanup
+command however this deletes every trashed file and folder individually
+so it may take a very long time. Emptying the trash via the WebUI does
+not have this limitation so it is advised to empty the trash via the
+WebUI.</p>
 <h3 id="root-folder-id">Root folder ID</h3>
-<p>You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your Box drive.</p>
-<p>Normally you will leave this blank and rclone will determine the correct root to use itself.</p>
-<p>However you can set this to restrict rclone to a specific folder hierarchy.</p>
-<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display. This will be the last segment of the URL when you open the relevant folder in the Box web interface.</p>
-<p>So if the folder you want rclone to use has a URL which looks like <code>https://app.box.com/folder/11xxxxxxxxx8</code> in the browser, then you use <code>11xxxxxxxxx8</code> as the <code>root_folder_id</code> in the config.</p>
+<p>You can set the <code>root_folder_id</code> for rclone. This is the
+directory (identified by its <code>Folder ID</code>) that rclone
+considers to be the root of your Box drive.</p>
+<p>Normally you will leave this blank and rclone will determine the
+correct root to use itself.</p>
+<p>However you can set this to restrict rclone to a specific folder
+hierarchy.</p>
+<p>In order to do this you will have to find the <code>Folder ID</code>
+of the directory you wish rclone to display. This will be the last
+segment of the URL when you open the relevant folder in the Box web
+interface.</p>
+<p>So if the folder you want rclone to use has a URL which looks like
+<code>https://app.box.com/folder/11xxxxxxxxx8</code> in the browser,
+then you use <code>11xxxxxxxxx8</code> as the
+<code>root_folder_id</code> in the config.</p>
 <h3 id="standard-options-4">Standard options</h3>
 <p>Here are the Standard options specific to box (Box).</p>
 <h4 id="box-client-id">--box-client-id</h4>
@@ -19363,7 +29204,8 @@ y/e/d&gt; y</code></pre>
 <h4 id="box-box-config-file">--box-box-config-file</h4>
 <p>Box App config.json location</p>
 <p>Leave blank normally.</p>
-<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
+<p>Leading <code>~</code> will be expanded in the file name as will
+environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: box_config_file</li>
@@ -19432,7 +29274,8 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="box-root-folder-id">--box-root-folder-id</h4>
-<p>Fill in for rclone to use a non root folder as its starting point.</p>
+<p>Fill in for rclone to use a non root folder as its starting
+point.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_id</li>
@@ -19478,8 +29321,12 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="box-impersonate">--box-impersonate</h4>
 <p>Impersonate this user ID when using a service account.</p>
-<p>Setting this flag allows rclone, when using a JWT service account, to act on behalf of another user by setting the as-user header.</p>
-<p>The user ID is the Box identifier for a user. User IDs can found for any user via the GET /users endpoint, which is only available to admins, or by calling the GET /users/me endpoint with an authenticated user session.</p>
+<p>Setting this flag allows rclone, when using a JWT service account, to
+act on behalf of another user by setting the as-user header.</p>
+<p>The user ID is the Box identifier for a user. User IDs can found for
+any user via the GET /users endpoint, which is only available to admins,
+or by calling the GET /users/me endpoint with an authenticated user
+session.</p>
 <p>See: https://developer.box.com/guides/authentication/jwt/as-user/</p>
 <p>Properties:</p>
 <ul>
@@ -19490,7 +29337,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="box-encoding">--box-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -19508,31 +29356,70 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-8">Limitations</h2>
-<p>Note that Box is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
-<p>Box file names can't have the <code>\</code> character in. rclone maps this to and from an identical looking unicode equivalent <code>＼</code> (U+FF3C Fullwidth Reverse Solidus).</p>
+<p>Note that Box is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".</p>
+<p>Box file names can't have the <code>\</code> character in. rclone
+maps this to and from an identical looking unicode equivalent
+<code>＼</code> (U+FF3C Fullwidth Reverse Solidus).</p>
 <p>Box only supports filenames up to 255 characters in length.</p>
-<p>Box has <a href="https://developer.box.com/guides/api-calls/permissions-and-errors/rate-limits/">API rate limits</a> that sometimes reduce the speed of rclone.</p>
-<p><code>rclone about</code> is not supported by the Box backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p>Box has <a
+href="https://developer.box.com/guides/api-calls/permissions-and-errors/rate-limits/">API
+rate limits</a> that sometimes reduce the speed of rclone.</p>
+<p><code>rclone about</code> is not supported by the Box backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h2 id="get-your-own-box-app-id">Get your own Box App ID</h2>
 <p>Here is how to create your own Box App ID for rclone:</p>
 <ol type="1">
-<li><p>Go to the <a href="https://app.box.com/developers/console">Box Developer Console</a> and login, then click <code>My Apps</code> on the sidebar. Click <code>Create New App</code> and select <code>Custom App</code>.</p></li>
-<li><p>In the first screen on the box that pops up, you can pretty much enter whatever you want. The <code>App Name</code> can be whatever. For <code>Purpose</code> choose automation to avoid having to fill out anything else. Click <code>Next</code>.</p></li>
-<li><p>In the second screen of the creation screen, select <code>User Authentication (OAuth 2.0)</code>. Then click <code>Create App</code>.</p></li>
-<li><p>You should now be on the <code>Configuration</code> tab of your new app. If not, click on it at the top of the webpage. Copy down <code>Client ID</code> and <code>Client Secret</code>, you'll need those for rclone.</p></li>
-<li><p>Under "OAuth 2.0 Redirect URI", add <code>http://127.0.0.1:53682/</code></p></li>
-<li><p>For <code>Application Scopes</code>, select <code>Read all files and folders stored in Box</code> and <code>Write all files and folders stored in box</code> (assuming you want to do both). Leave others unchecked. Click <code>Save Changes</code> at the top right.</p></li>
+<li><p>Go to the <a href="https://app.box.com/developers/console">Box
+Developer Console</a> and login, then click <code>My Apps</code> on the
+sidebar. Click <code>Create New App</code> and select
+<code>Custom App</code>.</p></li>
+<li><p>In the first screen on the box that pops up, you can pretty much
+enter whatever you want. The <code>App Name</code> can be whatever. For
+<code>Purpose</code> choose automation to avoid having to fill out
+anything else. Click <code>Next</code>.</p></li>
+<li><p>In the second screen of the creation screen, select
+<code>User Authentication (OAuth 2.0)</code>. Then click
+<code>Create App</code>.</p></li>
+<li><p>You should now be on the <code>Configuration</code> tab of your
+new app. If not, click on it at the top of the webpage. Copy down
+<code>Client ID</code> and <code>Client Secret</code>, you'll need those
+for rclone.</p></li>
+<li><p>Under "OAuth 2.0 Redirect URI", add
+<code>http://127.0.0.1:53682/</code></p></li>
+<li><p>For <code>Application Scopes</code>, select
+<code>Read all files and folders stored in Box</code> and
+<code>Write all files and folders stored in box</code> (assuming you
+want to do both). Leave others unchecked. Click
+<code>Save Changes</code> at the top right.</p></li>
 </ol>
 <h1 id="cache">Cache</h1>
-<p>The <code>cache</code> remote wraps another existing remote and stores file structure and its data for long running tasks like <code>rclone mount</code>.</p>
+<p>The <code>cache</code> remote wraps another existing remote and
+stores file structure and its data for long running tasks like
+<code>rclone mount</code>.</p>
 <h2 id="status">Status</h2>
-<p>The cache backend code is working but it currently doesn't have a maintainer so there are <a href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22Remote%3A+Cache%22">outstanding bugs</a> which aren't getting fixed.</p>
-<p>The cache backend is due to be phased out in favour of the VFS caching layer eventually which is more tightly integrated into rclone.</p>
-<p>Until this happens we recommend only using the cache backend if you find you can't work without it. There are many docs online describing the use of the cache backend to minimize API hits and by-and-large these are out of date and the cache backend isn't needed in those scenarios any more.</p>
+<p>The cache backend code is working but it currently doesn't have a
+maintainer so there are <a
+href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug+label%3A%22Remote%3A+Cache%22">outstanding
+bugs</a> which aren't getting fixed.</p>
+<p>The cache backend is due to be phased out in favour of the VFS
+caching layer eventually which is more tightly integrated into
+rclone.</p>
+<p>Until this happens we recommend only using the cache backend if you
+find you can't work without it. There are many docs online describing
+the use of the cache backend to minimize API hits and by-and-large these
+are out of date and the cache backend isn't needed in those scenarios
+any more.</p>
 <h2 id="configuration-5">Configuration</h2>
-<p>To get started you just need to have an existing remote which can be configured with <code>cache</code>.</p>
-<p>Here is an example of how to make a remote called <code>test-cache</code>. First run:</p>
+<p>To get started you just need to have an existing remote which can be
+configured with <code>cache</code>.</p>
+<p>Here is an example of how to make a remote called
+<code>test-cache</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -19617,78 +29504,181 @@ chunk_total_size = 10G</code></pre>
 <pre><code>rclone mount --allow-other test-cache: /var/tmp/test-cache</code></pre>
 <h3 id="write-features">Write Features</h3>
 <h3 id="offline-uploading">Offline uploading</h3>
-<p>In an effort to make writing through cache more reliable, the backend now supports this feature which can be activated by specifying a <code>cache-tmp-upload-path</code>.</p>
+<p>In an effort to make writing through cache more reliable, the backend
+now supports this feature which can be activated by specifying a
+<code>cache-tmp-upload-path</code>.</p>
 <p>A files goes through these states when using this feature:</p>
 <ol type="1">
-<li>An upload is started (usually by copying a file on the cache remote)</li>
-<li>When the copy to the temporary location is complete the file is part of the cached remote and looks and behaves like any other file (reading included)</li>
-<li>After <code>cache-tmp-wait-time</code> passes and the file is next in line, <code>rclone move</code> is used to move the file to the cloud provider</li>
-<li>Reading the file still works during the upload but most modifications on it will be prohibited</li>
-<li>Once the move is complete the file is unlocked for modifications as it becomes as any other regular file</li>
-<li>If the file is being read through <code>cache</code> when it's actually deleted from the temporary path then <code>cache</code> will simply swap the source to the cloud provider without interrupting the reading (small blip can happen though)</li>
+<li>An upload is started (usually by copying a file on the cache
+remote)</li>
+<li>When the copy to the temporary location is complete the file is part
+of the cached remote and looks and behaves like any other file (reading
+included)</li>
+<li>After <code>cache-tmp-wait-time</code> passes and the file is next
+in line, <code>rclone move</code> is used to move the file to the cloud
+provider</li>
+<li>Reading the file still works during the upload but most
+modifications on it will be prohibited</li>
+<li>Once the move is complete the file is unlocked for modifications as
+it becomes as any other regular file</li>
+<li>If the file is being read through <code>cache</code> when it's
+actually deleted from the temporary path then <code>cache</code> will
+simply swap the source to the cloud provider without interrupting the
+reading (small blip can happen though)</li>
 </ol>
-<p>Files are uploaded in sequence and only one file is uploaded at a time. Uploads will be stored in a queue and be processed based on the order they were added. The queue and the temporary storage is persistent across restarts but can be cleared on startup with the <code>--cache-db-purge</code> flag.</p>
+<p>Files are uploaded in sequence and only one file is uploaded at a
+time. Uploads will be stored in a queue and be processed based on the
+order they were added. The queue and the temporary storage is persistent
+across restarts but can be cleared on startup with the
+<code>--cache-db-purge</code> flag.</p>
 <h3 id="write-support">Write Support</h3>
-<p>Writes are supported through <code>cache</code>. One caveat is that a mounted cache remote does not add any retry or fallback mechanism to the upload operation. This will depend on the implementation of the wrapped remote. Consider using <code>Offline uploading</code> for reliable writes.</p>
-<p>One special case is covered with <code>cache-writes</code> which will cache the file data at the same time as the upload when it is enabled making it available from the cache store immediately once the upload is finished.</p>
+<p>Writes are supported through <code>cache</code>. One caveat is that a
+mounted cache remote does not add any retry or fallback mechanism to the
+upload operation. This will depend on the implementation of the wrapped
+remote. Consider using <code>Offline uploading</code> for reliable
+writes.</p>
+<p>One special case is covered with <code>cache-writes</code> which will
+cache the file data at the same time as the upload when it is enabled
+making it available from the cache store immediately once the upload is
+finished.</p>
 <h3 id="read-features">Read Features</h3>
 <h4 id="multiple-connections">Multiple connections</h4>
-<p>To counter the high latency between a local PC where rclone is running and cloud providers, the cache remote can split multiple requests to the cloud provider for smaller file chunks and combines them together locally where they can be available almost immediately before the reader usually needs them.</p>
-<p>This is similar to buffering when media files are played online. Rclone will stay around the current marker but always try its best to stay ahead and prepare the data before.</p>
+<p>To counter the high latency between a local PC where rclone is
+running and cloud providers, the cache remote can split multiple
+requests to the cloud provider for smaller file chunks and combines them
+together locally where they can be available almost immediately before
+the reader usually needs them.</p>
+<p>This is similar to buffering when media files are played online.
+Rclone will stay around the current marker but always try its best to
+stay ahead and prepare the data before.</p>
 <h4 id="plex-integration">Plex Integration</h4>
-<p>There is a direct integration with Plex which allows cache to detect during reading if the file is in playback or not. This helps cache to adapt how it queries the cloud provider depending on what is needed for.</p>
-<p>Scans will have a minimum amount of workers (1) while in a confirmed playback cache will deploy the configured number of workers.</p>
-<p>This integration opens the doorway to additional performance improvements which will be explored in the near future.</p>
-<p><strong>Note:</strong> If Plex options are not configured, <code>cache</code> will function with its configured options without adapting any of its settings.</p>
-<p>How to enable? Run <code>rclone config</code> and add all the Plex options (endpoint, username and password) in your remote and it will be automatically enabled.</p>
-<p>Affected settings: - <code>cache-workers</code>: <em>Configured value</em> during confirmed playback or <em>1</em> all the other times</p>
+<p>There is a direct integration with Plex which allows cache to detect
+during reading if the file is in playback or not. This helps cache to
+adapt how it queries the cloud provider depending on what is needed
+for.</p>
+<p>Scans will have a minimum amount of workers (1) while in a confirmed
+playback cache will deploy the configured number of workers.</p>
+<p>This integration opens the doorway to additional performance
+improvements which will be explored in the near future.</p>
+<p><strong>Note:</strong> If Plex options are not configured,
+<code>cache</code> will function with its configured options without
+adapting any of its settings.</p>
+<p>How to enable? Run <code>rclone config</code> and add all the Plex
+options (endpoint, username and password) in your remote and it will be
+automatically enabled.</p>
+<p>Affected settings: - <code>cache-workers</code>: <em>Configured
+value</em> during confirmed playback or <em>1</em> all the other
+times</p>
 <h5 id="certificate-validation">Certificate Validation</h5>
-<p>When the Plex server is configured to only accept secure connections, it is possible to use <code>.plex.direct</code> URLs to ensure certificate validation succeeds. These URLs are used by Plex internally to connect to the Plex server securely.</p>
+<p>When the Plex server is configured to only accept secure connections,
+it is possible to use <code>.plex.direct</code> URLs to ensure
+certificate validation succeeds. These URLs are used by Plex internally
+to connect to the Plex server securely.</p>
 <p>The format for these URLs is the following:</p>
 <p><code>https://ip-with-dots-replaced.server-hash.plex.direct:32400/</code></p>
-<p>The <code>ip-with-dots-replaced</code> part can be any IPv4 address, where the dots have been replaced with dashes, e.g. <code>127.0.0.1</code> becomes <code>127-0-0-1</code>.</p>
-<p>To get the <code>server-hash</code> part, the easiest way is to visit</p>
+<p>The <code>ip-with-dots-replaced</code> part can be any IPv4 address,
+where the dots have been replaced with dashes, e.g.
+<code>127.0.0.1</code> becomes <code>127-0-0-1</code>.</p>
+<p>To get the <code>server-hash</code> part, the easiest way is to
+visit</p>
 <p>https://plex.tv/api/resources?includeHttps=1&amp;X-Plex-Token=your-plex-token</p>
-<p>This page will list all the available Plex servers for your account with at least one <code>.plex.direct</code> link for each. Copy one URL and replace the IP address with the desired address. This can be used as the <code>plex_url</code> value.</p>
+<p>This page will list all the available Plex servers for your account
+with at least one <code>.plex.direct</code> link for each. Copy one URL
+and replace the IP address with the desired address. This can be used as
+the <code>plex_url</code> value.</p>
 <h3 id="known-issues">Known issues</h3>
 <h4 id="mount-and---dir-cache-time">Mount and --dir-cache-time</h4>
-<p>--dir-cache-time controls the first layer of directory caching which works at the mount layer. Being an independent caching mechanism from the <code>cache</code> backend, it will manage its own entries based on the configured time.</p>
-<p>To avoid getting in a scenario where dir cache has obsolete data and cache would have the correct one, try to set <code>--dir-cache-time</code> to a lower time than <code>--cache-info-age</code>. Default values are already configured in this way.</p>
-<h4 id="windows-support---experimental">Windows support - Experimental</h4>
-<p>There are a couple of issues with Windows <code>mount</code> functionality that still require some investigations. It should be considered as experimental thus far as fixes come in for this OS.</p>
-<p>Most of the issues seem to be related to the difference between filesystems on Linux flavors and Windows as cache is heavily dependent on them.</p>
-<p>Any reports or feedback on how cache behaves on this OS is greatly appreciated.</p>
+<p>--dir-cache-time controls the first layer of directory caching which
+works at the mount layer. Being an independent caching mechanism from
+the <code>cache</code> backend, it will manage its own entries based on
+the configured time.</p>
+<p>To avoid getting in a scenario where dir cache has obsolete data and
+cache would have the correct one, try to set
+<code>--dir-cache-time</code> to a lower time than
+<code>--cache-info-age</code>. Default values are already configured in
+this way.</p>
+<h4 id="windows-support---experimental">Windows support -
+Experimental</h4>
+<p>There are a couple of issues with Windows <code>mount</code>
+functionality that still require some investigations. It should be
+considered as experimental thus far as fixes come in for this OS.</p>
+<p>Most of the issues seem to be related to the difference between
+filesystems on Linux flavors and Windows as cache is heavily dependent
+on them.</p>
+<p>Any reports or feedback on how cache behaves on this OS is greatly
+appreciated.</p>
 <ul>
 <li>https://github.com/rclone/rclone/issues/1935</li>
 <li>https://github.com/rclone/rclone/issues/1907</li>
 <li>https://github.com/rclone/rclone/issues/1834</li>
 </ul>
 <h4 id="risk-of-throttling">Risk of throttling</h4>
-<p>Future iterations of the cache backend will make use of the pooling functionality of the cloud provider to synchronize and at the same time make writing through it more tolerant to failures.</p>
-<p>There are a couple of enhancements in track to add these but in the meantime there is a valid concern that the expiring cache listings can lead to cloud provider throttles or bans due to repeated queries on it for very large mounts.</p>
-<p>Some recommendations: - don't use a very small interval for entry information (<code>--cache-info-age</code>) - while writes aren't yet optimised, you can still write through <code>cache</code> which gives you the advantage of adding the file in the cache at the same time if configured to do so.</p>
+<p>Future iterations of the cache backend will make use of the pooling
+functionality of the cloud provider to synchronize and at the same time
+make writing through it more tolerant to failures.</p>
+<p>There are a couple of enhancements in track to add these but in the
+meantime there is a valid concern that the expiring cache listings can
+lead to cloud provider throttles or bans due to repeated queries on it
+for very large mounts.</p>
+<p>Some recommendations: - don't use a very small interval for entry
+information (<code>--cache-info-age</code>) - while writes aren't yet
+optimised, you can still write through <code>cache</code> which gives
+you the advantage of adding the file in the cache at the same time if
+configured to do so.</p>
 <p>Future enhancements:</p>
 <ul>
 <li>https://github.com/rclone/rclone/issues/1937</li>
 <li>https://github.com/rclone/rclone/issues/1936</li>
 </ul>
 <h4 id="cache-and-crypt">cache and crypt</h4>
-<p>One common scenario is to keep your data encrypted in the cloud provider using the <code>crypt</code> remote. <code>crypt</code> uses a similar technique to wrap around an existing remote and handles this translation in a seamless way.</p>
-<p>There is an issue with wrapping the remotes in this order: <strong>cloud remote</strong> -&gt; <strong>crypt</strong> -&gt; <strong>cache</strong></p>
-<p>During testing, I experienced a lot of bans with the remotes in this order. I suspect it might be related to how crypt opens files on the cloud provider which makes it think we're downloading the full file instead of small chunks. Organizing the remotes in this order yields better results: <strong>cloud remote</strong> -&gt; <strong>cache</strong> -&gt; <strong>crypt</strong></p>
+<p>One common scenario is to keep your data encrypted in the cloud
+provider using the <code>crypt</code> remote. <code>crypt</code> uses a
+similar technique to wrap around an existing remote and handles this
+translation in a seamless way.</p>
+<p>There is an issue with wrapping the remotes in this order:
+<strong>cloud remote</strong> -&gt; <strong>crypt</strong> -&gt;
+<strong>cache</strong></p>
+<p>During testing, I experienced a lot of bans with the remotes in this
+order. I suspect it might be related to how crypt opens files on the
+cloud provider which makes it think we're downloading the full file
+instead of small chunks. Organizing the remotes in this order yields
+better results: <strong>cloud remote</strong> -&gt;
+<strong>cache</strong> -&gt; <strong>crypt</strong></p>
 <h4 id="absolute-remote-paths">absolute remote paths</h4>
-<p><code>cache</code> can not differentiate between relative and absolute paths for the wrapped remote. Any path given in the <code>remote</code> config setting and on the command line will be passed to the wrapped remote as is, but for storing the chunks on disk the path will be made relative by removing any leading <code>/</code> character.</p>
-<p>This behavior is irrelevant for most backend types, but there are backends where a leading <code>/</code> changes the effective directory, e.g. in the <code>sftp</code> backend paths starting with a <code>/</code> are relative to the root of the SSH server and paths without are relative to the user home directory. As a result <code>sftp:bin</code> and <code>sftp:/bin</code> will share the same cache folder, even if they represent a different directory on the SSH server.</p>
-<h3 id="cache-and-remote-control---rc">Cache and Remote Control (--rc)</h3>
-<p>Cache supports the new <code>--rc</code> mode in rclone and can be remote controlled through the following end points: By default, the listener is disabled if you do not add the flag.</p>
+<p><code>cache</code> can not differentiate between relative and
+absolute paths for the wrapped remote. Any path given in the
+<code>remote</code> config setting and on the command line will be
+passed to the wrapped remote as is, but for storing the chunks on disk
+the path will be made relative by removing any leading <code>/</code>
+character.</p>
+<p>This behavior is irrelevant for most backend types, but there are
+backends where a leading <code>/</code> changes the effective directory,
+e.g. in the <code>sftp</code> backend paths starting with a
+<code>/</code> are relative to the root of the SSH server and paths
+without are relative to the user home directory. As a result
+<code>sftp:bin</code> and <code>sftp:/bin</code> will share the same
+cache folder, even if they represent a different directory on the SSH
+server.</p>
+<h3 id="cache-and-remote-control---rc">Cache and Remote Control
+(--rc)</h3>
+<p>Cache supports the new <code>--rc</code> mode in rclone and can be
+remote controlled through the following end points: By default, the
+listener is disabled if you do not add the flag.</p>
 <h3 id="rc-cacheexpire">rc cache/expire</h3>
-<p>Purge a remote from the cache backend. Supports either a directory or a file. It supports both encrypted and unencrypted file names if cache is wrapped by crypt.</p>
-<p>Params: - <strong>remote</strong> = path to remote <strong>(required)</strong> - <strong>withData</strong> = true/false to delete cached data (chunks) as well <em>(optional, false by default)</em></p>
+<p>Purge a remote from the cache backend. Supports either a directory or
+a file. It supports both encrypted and unencrypted file names if cache
+is wrapped by crypt.</p>
+<p>Params: - <strong>remote</strong> = path to remote
+<strong>(required)</strong> - <strong>withData</strong> = true/false to
+delete cached data (chunks) as well <em>(optional, false by
+default)</em></p>
 <h3 id="standard-options-5">Standard options</h3>
 <p>Here are the Standard options specific to cache (Cache a remote).</p>
 <h4 id="cache-remote">--cache-remote</h4>
 <p>Remote to cache.</p>
-<p>Normally should contain a ':' and a path, e.g. "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not recommended).</p>
+<p>Normally should contain a ':' and a path, e.g.
+"myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not
+recommended).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: remote</li>
@@ -19716,7 +29706,9 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-plex-password">--cache-plex-password</h4>
 <p>The password of the Plex user.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: plex_password</li>
@@ -19726,7 +29718,9 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-chunk-size">--cache-chunk-size</h4>
 <p>The size of a chunk (partial file data).</p>
-<p>Use lower numbers for slower connections. If the chunk size is changed, any downloaded chunks will be invalid and cache-chunk-path will need to be cleared or unexpected EOF errors will occur.</p>
+<p>Use lower numbers for slower connections. If the chunk size is
+changed, any downloaded chunks will be invalid and cache-chunk-path will
+need to be cleared or unexpected EOF errors will occur.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -19750,7 +29744,10 @@ chunk_total_size = 10G</code></pre>
 </ul></li>
 </ul>
 <h4 id="cache-info-age">--cache-info-age</h4>
-<p>How long to cache file structure information (directory listings, file size, times, etc.). If all write operations are done through the cache then you can safely make this value very large as the cache store will also be updated in real time.</p>
+<p>How long to cache file structure information (directory listings,
+file size, times, etc.). If all write operations are done through the
+cache then you can safely make this value very large as the cache store
+will also be updated in real time.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: info_age</li>
@@ -19775,7 +29772,8 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-chunk-total-size">--cache-chunk-total-size</h4>
 <p>The total size that the chunks can take up on the local disk.</p>
-<p>If the cache exceeds this value then it will start to delete the oldest chunks until it goes under this value.</p>
+<p>If the cache exceeds this value then it will start to delete the
+oldest chunks until it goes under this value.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_total_size</li>
@@ -19810,7 +29808,8 @@ chunk_total_size = 10G</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="cache-plex-insecure">--cache-plex-insecure</h4>
-<p>Skip all certificate verification when connecting to the Plex server.</p>
+<p>Skip all certificate verification when connecting to the Plex
+server.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: plex_insecure</li>
@@ -19830,8 +29829,12 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-chunk-path">--cache-chunk-path</h4>
 <p>Directory to cache chunk files.</p>
-<p>Path to where partial file data (chunks) are stored locally. The remote name is appended to the final path.</p>
-<p>This config follows the "--cache-db-path". If you specify a custom location for "--cache-db-path" and don't specify one for "--cache-chunk-path" then "--cache-chunk-path" will use the same path as "--cache-db-path".</p>
+<p>Path to where partial file data (chunks) are stored locally. The
+remote name is appended to the final path.</p>
+<p>This config follows the "--cache-db-path". If you specify a custom
+location for "--cache-db-path" and don't specify one for
+"--cache-chunk-path" then "--cache-chunk-path" will use the same path as
+"--cache-db-path".</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_path</li>
@@ -19850,7 +29853,9 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-chunk-clean-interval">--cache-chunk-clean-interval</h4>
 <p>How often should the cache perform cleanups of the chunk storage.</p>
-<p>The default value should be ok for most people. If you find that the cache goes over "cache-chunk-total-size" too often then try to lower this value to force it to perform cleanups more often.</p>
+<p>The default value should be ok for most people. If you find that the
+cache goes over "cache-chunk-total-size" too often then try to lower
+this value to force it to perform cleanups more often.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_clean_interval</li>
@@ -19860,8 +29865,13 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-read-retries">--cache-read-retries</h4>
 <p>How many times to retry a read from a cache storage.</p>
-<p>Since reading from a cache stream is independent from downloading file data, readers can get to a point where there's no more data in the cache. Most of the times this can indicate a connectivity issue if cache isn't able to provide file data anymore.</p>
-<p>For really slow connections, increase this to a point where the stream is able to provide data but your experience will be very stuttering.</p>
+<p>Since reading from a cache stream is independent from downloading
+file data, readers can get to a point where there's no more data in the
+cache. Most of the times this can indicate a connectivity issue if cache
+isn't able to provide file data anymore.</p>
+<p>For really slow connections, increase this to a point where the
+stream is able to provide data but your experience will be very
+stuttering.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: read_retries</li>
@@ -19871,8 +29881,15 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-workers">--cache-workers</h4>
 <p>How many workers should run in parallel to download chunks.</p>
-<p>Higher values will mean more parallel processing (better CPU needed) and more concurrent requests on the cloud provider. This impacts several aspects like the cloud provider API limits, more stress on the hardware that rclone runs on but it also means that streams will be more fluid and data will be available much more faster to readers.</p>
-<p><strong>Note</strong>: If the optional Plex integration is enabled then this setting will adapt to the type of reading performed and the value specified here will be used as a maximum number of workers to use.</p>
+<p>Higher values will mean more parallel processing (better CPU needed)
+and more concurrent requests on the cloud provider. This impacts several
+aspects like the cloud provider API limits, more stress on the hardware
+that rclone runs on but it also means that streams will be more fluid
+and data will be available much more faster to readers.</p>
+<p><strong>Note</strong>: If the optional Plex integration is enabled
+then this setting will adapt to the type of reading performed and the
+value specified here will be used as a maximum number of workers to
+use.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: workers</li>
@@ -19882,9 +29899,16 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-chunk-no-memory">--cache-chunk-no-memory</h4>
 <p>Disable the in-memory cache for storing chunks during streaming.</p>
-<p>By default, cache will keep file data during streaming in RAM as well to provide it to readers as fast as possible.</p>
-<p>This transient data is evicted as soon as it is read and the number of chunks stored doesn't exceed the number of workers. However, depending on other settings like "cache-chunk-size" and "cache-workers" this footprint can increase if there are parallel streams too (multiple files being read at the same time).</p>
-<p>If the hardware permits it, use this feature to provide an overall better performance during streaming but it can also be disabled if RAM is not available on the local machine.</p>
+<p>By default, cache will keep file data during streaming in RAM as well
+to provide it to readers as fast as possible.</p>
+<p>This transient data is evicted as soon as it is read and the number
+of chunks stored doesn't exceed the number of workers. However,
+depending on other settings like "cache-chunk-size" and "cache-workers"
+this footprint can increase if there are parallel streams too (multiple
+files being read at the same time).</p>
+<p>If the hardware permits it, use this feature to provide an overall
+better performance during streaming but it can also be disabled if RAM
+is not available on the local machine.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_no_memory</li>
@@ -19893,11 +29917,20 @@ chunk_total_size = 10G</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="cache-rps">--cache-rps</h4>
-<p>Limits the number of requests per second to the source FS (-1 to disable).</p>
-<p>This setting places a hard limit on the number of requests per second that cache will be doing to the cloud provider remote and try to respect that value by setting waits between reads.</p>
-<p>If you find that you're getting banned or limited on the cloud provider through cache and know that a smaller number of requests per second will allow you to work with it then you can use this setting for that.</p>
-<p>A good balance of all the other settings should make this setting useless but it is available to set for more special cases.</p>
-<p><strong>NOTE</strong>: This will limit the number of requests during streams but other API calls to the cloud provider like directory listings will still pass.</p>
+<p>Limits the number of requests per second to the source FS (-1 to
+disable).</p>
+<p>This setting places a hard limit on the number of requests per second
+that cache will be doing to the cloud provider remote and try to respect
+that value by setting waits between reads.</p>
+<p>If you find that you're getting banned or limited on the cloud
+provider through cache and know that a smaller number of requests per
+second will allow you to work with it then you can use this setting for
+that.</p>
+<p>A good balance of all the other settings should make this setting
+useless but it is available to set for more special cases.</p>
+<p><strong>NOTE</strong>: This will limit the number of requests during
+streams but other API calls to the cloud provider like directory
+listings will still pass.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: rps</li>
@@ -19907,7 +29940,9 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-writes">--cache-writes</h4>
 <p>Cache file data on writes through the FS.</p>
-<p>If you need to read files immediately after you upload them through cache you can enable this flag to have their data stored in the cache store at the same time during upload.</p>
+<p>If you need to read files immediately after you upload them through
+cache you can enable this flag to have their data stored in the cache
+store at the same time during upload.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: writes</li>
@@ -19917,8 +29952,11 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-tmp-upload-path">--cache-tmp-upload-path</h4>
 <p>Directory to keep temporary files until they are uploaded.</p>
-<p>This is the path where cache will use as a temporary storage for new files that need to be uploaded to the cloud provider.</p>
-<p>Specifying a value will enable this feature. Without it, it is completely disabled and files will be uploaded directly to the cloud provider</p>
+<p>This is the path where cache will use as a temporary storage for new
+files that need to be uploaded to the cloud provider.</p>
+<p>Specifying a value will enable this feature. Without it, it is
+completely disabled and files will be uploaded directly to the cloud
+provider</p>
 <p>Properties:</p>
 <ul>
 <li>Config: tmp_upload_path</li>
@@ -19927,9 +29965,12 @@ chunk_total_size = 10G</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="cache-tmp-wait-time">--cache-tmp-wait-time</h4>
-<p>How long should files be stored in local cache before being uploaded.</p>
-<p>This is the duration that a file must wait in the temporary location <em>cache-tmp-upload-path</em> before it is selected for upload.</p>
-<p>Note that only one file is uploaded at a time and it can take longer to start the upload if a queue formed for this purpose.</p>
+<p>How long should files be stored in local cache before being
+uploaded.</p>
+<p>This is the duration that a file must wait in the temporary location
+<em>cache-tmp-upload-path</em> before it is selected for upload.</p>
+<p>Note that only one file is uploaded at a time and it can take longer
+to start the upload if a queue formed for this purpose.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: tmp_wait_time</li>
@@ -19939,7 +29980,9 @@ chunk_total_size = 10G</code></pre>
 </ul>
 <h4 id="cache-db-wait-time">--cache-db-wait-time</h4>
 <p>How long to wait for the DB to be available - 0 is unlimited.</p>
-<p>Only one process can have the DB open at any one time, so rclone waits for this duration for the DB to become available before it gives an error.</p>
+<p>Only one process can have the DB open at any one time, so rclone
+waits for this duration for the DB to become available before it gives
+an error.</p>
 <p>If you set it to 0 then it will wait forever.</p>
 <p>Properties:</p>
 <ul>
@@ -19962,17 +30005,32 @@ chunk_total_size = 10G</code></pre>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="stats">stats</h3>
 <p>Print stats on the cache backend in JSON format.</p>
 <pre><code>rclone backend stats remote: [options] [&lt;arguments&gt;+]</code></pre>
 <h1 id="chunker">Chunker</h1>
-<p>The <code>chunker</code> overlay transparently splits large files into smaller chunks during upload to wrapped remote and transparently assembles them back when the file is downloaded. This allows to effectively overcome size limits imposed by storage providers.</p>
+<p>The <code>chunker</code> overlay transparently splits large files
+into smaller chunks during upload to wrapped remote and transparently
+assembles them back when the file is downloaded. This allows to
+effectively overcome size limits imposed by storage providers.</p>
 <h2 id="configuration-6">Configuration</h2>
-<p>To use it, first set up the underlying remote following the configuration instructions for that remote. You can also use a local pathname instead of a remote.</p>
-<p>First check your chosen remote is working - we'll call it <code>remote:path</code> here. Note that anything inside <code>remote:path</code> will be chunked and anything outside won't. This means that if you are using a bucket-based remote (e.g. S3, B2, swift) then you should probably put the bucket in the remote <code>s3:bucket</code>.</p>
-<p>Now configure <code>chunker</code> using <code>rclone config</code>. We will call this one <code>overlay</code> to separate it from the <code>remote</code> itself.</p>
+<p>To use it, first set up the underlying remote following the
+configuration instructions for that remote. You can also use a local
+pathname instead of a remote.</p>
+<p>First check your chosen remote is working - we'll call it
+<code>remote:path</code> here. Note that anything inside
+<code>remote:path</code> will be chunked and anything outside won't.
+This means that if you are using a bucket-based remote (e.g. S3, B2,
+swift) then you should probably put the bucket in the remote
+<code>s3:bucket</code>.</p>
+<p>Now configure <code>chunker</code> using <code>rclone config</code>.
+We will call this one <code>overlay</code> to separate it from the
+<code>remote</code> itself.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -20029,23 +30087,91 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
 <h3 id="specifying-the-remote">Specifying the remote</h3>
-<p>In normal use, make sure the remote has a <code>:</code> in. If you specify the remote without a <code>:</code> then rclone will use a local directory of that name. So if you use a remote of <code>/path/to/secret/files</code> then rclone will chunk stuff in that directory. If you use a remote of <code>name</code> then rclone will put files in a directory called <code>name</code> in the current directory.</p>
+<p>In normal use, make sure the remote has a <code>:</code> in. If you
+specify the remote without a <code>:</code> then rclone will use a local
+directory of that name. So if you use a remote of
+<code>/path/to/secret/files</code> then rclone will chunk stuff in that
+directory. If you use a remote of <code>name</code> then rclone will put
+files in a directory called <code>name</code> in the current
+directory.</p>
 <h3 id="chunking">Chunking</h3>
-<p>When rclone starts a file upload, chunker checks the file size. If it doesn't exceed the configured chunk size, chunker will just pass the file to the wrapped remote (however, see caveat below). If a file is large, chunker will transparently cut data in pieces with temporary names and stream them one by one, on the fly. Each data chunk will contain the specified number of bytes, except for the last one which may have less data. If file size is unknown in advance (this is called a streaming upload), chunker will internally create a temporary copy, record its size and repeat the above process.</p>
-<p>When upload completes, temporary chunk files are finally renamed. This scheme guarantees that operations can be run in parallel and look from outside as atomic. A similar method with hidden temporary chunks is used for other operations (copy/move/rename, etc.). If an operation fails, hidden chunks are normally destroyed, and the target composite file stays intact.</p>
-<p>When a composite file download is requested, chunker transparently assembles it by concatenating data chunks in order. As the split is trivial one could even manually concatenate data chunks together to obtain the original content.</p>
-<p>When the <code>list</code> rclone command scans a directory on wrapped remote, the potential chunk files are accounted for, grouped and assembled into composite directory entries. Any temporary chunks are hidden.</p>
-<p>List and other commands can sometimes come across composite files with missing or invalid chunks, e.g. shadowed by like-named directory or another file. This usually means that wrapped file system has been directly tampered with or damaged. If chunker detects a missing chunk it will by default print warning, skip the whole incomplete group of chunks but proceed with current command. You can set the <code>--chunker-fail-hard</code> flag to have commands abort with error message in such cases.</p>
-<p><strong>Caveat</strong>: As it is now, chunker will always create a temporary file in the backend and then rename it, even if the file is below the chunk threshold. This will result in unnecessary API calls and can severely restrict throughput when handling transfers primarily composed of small files on some backends (e.g. Box). A workaround to this issue is to use chunker only for files above the chunk threshold via <code>--min-size</code> and then perform a separate call without chunker on the remaining files.</p>
+<p>When rclone starts a file upload, chunker checks the file size. If it
+doesn't exceed the configured chunk size, chunker will just pass the
+file to the wrapped remote (however, see caveat below). If a file is
+large, chunker will transparently cut data in pieces with temporary
+names and stream them one by one, on the fly. Each data chunk will
+contain the specified number of bytes, except for the last one which may
+have less data. If file size is unknown in advance (this is called a
+streaming upload), chunker will internally create a temporary copy,
+record its size and repeat the above process.</p>
+<p>When upload completes, temporary chunk files are finally renamed.
+This scheme guarantees that operations can be run in parallel and look
+from outside as atomic. A similar method with hidden temporary chunks is
+used for other operations (copy/move/rename, etc.). If an operation
+fails, hidden chunks are normally destroyed, and the target composite
+file stays intact.</p>
+<p>When a composite file download is requested, chunker transparently
+assembles it by concatenating data chunks in order. As the split is
+trivial one could even manually concatenate data chunks together to
+obtain the original content.</p>
+<p>When the <code>list</code> rclone command scans a directory on
+wrapped remote, the potential chunk files are accounted for, grouped and
+assembled into composite directory entries. Any temporary chunks are
+hidden.</p>
+<p>List and other commands can sometimes come across composite files
+with missing or invalid chunks, e.g. shadowed by like-named directory or
+another file. This usually means that wrapped file system has been
+directly tampered with or damaged. If chunker detects a missing chunk it
+will by default print warning, skip the whole incomplete group of chunks
+but proceed with current command. You can set the
+<code>--chunker-fail-hard</code> flag to have commands abort with error
+message in such cases.</p>
+<p><strong>Caveat</strong>: As it is now, chunker will always create a
+temporary file in the backend and then rename it, even if the file is
+below the chunk threshold. This will result in unnecessary API calls and
+can severely restrict throughput when handling transfers primarily
+composed of small files on some backends (e.g. Box). A workaround to
+this issue is to use chunker only for files above the chunk threshold
+via <code>--min-size</code> and then perform a separate call without
+chunker on the remaining files.</p>
 <h4 id="chunk-names">Chunk names</h4>
-<p>The default chunk name format is <code>*.rclone_chunk.###</code>, hence by default chunk names are <code>BIG_FILE_NAME.rclone_chunk.001</code>, <code>BIG_FILE_NAME.rclone_chunk.002</code> etc. You can configure another name format using the <code>name_format</code> configuration file option. The format uses asterisk <code>*</code> as a placeholder for the base file name and one or more consecutive hash characters <code>#</code> as a placeholder for sequential chunk number. There must be one and only one asterisk. The number of consecutive hash characters defines the minimum length of a string representing a chunk number. If decimal chunk number has less digits than the number of hashes, it is left-padded by zeros. If the decimal string is longer, it is left intact. By default numbering starts from 1 but there is another option that allows user to start from 0, e.g. for compatibility with legacy software.</p>
-<p>For example, if name format is <code>big_*-##.part</code> and original file name is <code>data.txt</code> and numbering starts from 0, then the first chunk will be named <code>big_data.txt-00.part</code>, the 99th chunk will be <code>big_data.txt-98.part</code> and the 302nd chunk will become <code>big_data.txt-301.part</code>.</p>
-<p>Note that <code>list</code> assembles composite directory entries only when chunk names match the configured format and treats non-conforming file names as normal non-chunked files.</p>
-<p>When using <code>norename</code> transactions, chunk names will additionally have a unique file version suffix. For example, <code>BIG_FILE_NAME.rclone_chunk.001_bp562k</code>.</p>
+<p>The default chunk name format is <code>*.rclone_chunk.###</code>,
+hence by default chunk names are
+<code>BIG_FILE_NAME.rclone_chunk.001</code>,
+<code>BIG_FILE_NAME.rclone_chunk.002</code> etc. You can configure
+another name format using the <code>name_format</code> configuration
+file option. The format uses asterisk <code>*</code> as a placeholder
+for the base file name and one or more consecutive hash characters
+<code>#</code> as a placeholder for sequential chunk number. There must
+be one and only one asterisk. The number of consecutive hash characters
+defines the minimum length of a string representing a chunk number. If
+decimal chunk number has less digits than the number of hashes, it is
+left-padded by zeros. If the decimal string is longer, it is left
+intact. By default numbering starts from 1 but there is another option
+that allows user to start from 0, e.g. for compatibility with legacy
+software.</p>
+<p>For example, if name format is <code>big_*-##.part</code> and
+original file name is <code>data.txt</code> and numbering starts from 0,
+then the first chunk will be named <code>big_data.txt-00.part</code>,
+the 99th chunk will be <code>big_data.txt-98.part</code> and the 302nd
+chunk will become <code>big_data.txt-301.part</code>.</p>
+<p>Note that <code>list</code> assembles composite directory entries
+only when chunk names match the configured format and treats
+non-conforming file names as normal non-chunked files.</p>
+<p>When using <code>norename</code> transactions, chunk names will
+additionally have a unique file version suffix. For example,
+<code>BIG_FILE_NAME.rclone_chunk.001_bp562k</code>.</p>
 <h3 id="metadata-4">Metadata</h3>
-<p>Besides data chunks chunker will by default create metadata object for a composite file. The object is named after the original file. Chunker allows user to disable metadata completely (the <code>none</code> format). Note that metadata is normally not created for files smaller than the configured chunk size. This may change in future rclone releases.</p>
+<p>Besides data chunks chunker will by default create metadata object
+for a composite file. The object is named after the original file.
+Chunker allows user to disable metadata completely (the
+<code>none</code> format). Note that metadata is normally not created
+for files smaller than the configured chunk size. This may change in
+future rclone releases.</p>
 <h4 id="simple-json-metadata-format">Simple JSON metadata format</h4>
-<p>This is the default format. It supports hash sums and chunk validation for composite files. Meta objects carry the following fields:</p>
+<p>This is the default format. It supports hash sums and chunk
+validation for composite files. Meta objects carry the following
+fields:</p>
 <ul>
 <li><code>ver</code> - version of format, currently <code>1</code></li>
 <li><code>size</code> - total size of composite file</li>
@@ -20054,39 +30180,130 @@ y/e/d&gt; y</code></pre>
 <li><code>sha1</code> - SHA1 hashsum (if present)</li>
 <li><code>txn</code> - identifies current version of the file</li>
 </ul>
-<p>There is no field for composite file name as it's simply equal to the name of meta object on the wrapped remote. Please refer to respective sections for details on hashsums and modified time handling.</p>
+<p>There is no field for composite file name as it's simply equal to the
+name of meta object on the wrapped remote. Please refer to respective
+sections for details on hashsums and modified time handling.</p>
 <h4 id="no-metadata">No metadata</h4>
-<p>You can disable meta objects by setting the meta format option to <code>none</code>. In this mode chunker will scan directory for all files that follow configured chunk name format, group them by detecting chunks with the same base name and show group names as virtual composite files. This method is more prone to missing chunk errors (especially missing last chunk) than format with metadata enabled.</p>
+<p>You can disable meta objects by setting the meta format option to
+<code>none</code>. In this mode chunker will scan directory for all
+files that follow configured chunk name format, group them by detecting
+chunks with the same base name and show group names as virtual composite
+files. This method is more prone to missing chunk errors (especially
+missing last chunk) than format with metadata enabled.</p>
 <h3 id="hashsums">Hashsums</h3>
-<p>Chunker supports hashsums only when a compatible metadata is present. Hence, if you choose metadata format of <code>none</code>, chunker will report hashsum as <code>UNSUPPORTED</code>.</p>
-<p>Please note that by default metadata is stored only for composite files. If a file is smaller than configured chunk size, chunker will transparently redirect hash requests to wrapped remote, so support depends on that. You will see the empty string as a hashsum of requested type for small files if the wrapped remote doesn't support it.</p>
-<p>Many storage backends support MD5 and SHA1 hash types, so does chunker. With chunker you can choose one or another but not both. MD5 is set by default as the most supported type. Since chunker keeps hashes for composite files and falls back to the wrapped remote hash for non-chunked ones, we advise you to choose the same hash type as supported by wrapped remote so that your file listings look coherent.</p>
-<p>If your storage backend does not support MD5 or SHA1 but you need consistent file hashing, configure chunker with <code>md5all</code> or <code>sha1all</code>. These two modes guarantee given hash for all files. If wrapped remote doesn't support it, chunker will then add metadata to all files, even small. However, this can double the amount of small files in storage and incur additional service charges. You can even use chunker to force md5/sha1 support in any other remote at expense of sidecar meta objects by setting e.g. <code>hash_type=sha1all</code> to force hashsums and <code>chunk_size=1P</code> to effectively disable chunking.</p>
-<p>Normally, when a file is copied to chunker controlled remote, chunker will ask the file source for compatible file hash and revert to on-the-fly calculation if none is found. This involves some CPU overhead but provides a guarantee that given hashsum is available. Also, chunker will reject a server-side copy or move operation if source and destination hashsum types are different resulting in the extra network bandwidth, too. In some rare cases this may be undesired, so chunker provides two optional choices: <code>sha1quick</code> and <code>md5quick</code>. If the source does not support primary hash type and the quick mode is enabled, chunker will try to fall back to the secondary type. This will save CPU and bandwidth but can result in empty hashsums at destination. Beware of consequences: the <code>sync</code> command will revert (sometimes silently) to time/size comparison if compatible hashsums between source and target are not found.</p>
+<p>Chunker supports hashsums only when a compatible metadata is present.
+Hence, if you choose metadata format of <code>none</code>, chunker will
+report hashsum as <code>UNSUPPORTED</code>.</p>
+<p>Please note that by default metadata is stored only for composite
+files. If a file is smaller than configured chunk size, chunker will
+transparently redirect hash requests to wrapped remote, so support
+depends on that. You will see the empty string as a hashsum of requested
+type for small files if the wrapped remote doesn't support it.</p>
+<p>Many storage backends support MD5 and SHA1 hash types, so does
+chunker. With chunker you can choose one or another but not both. MD5 is
+set by default as the most supported type. Since chunker keeps hashes
+for composite files and falls back to the wrapped remote hash for
+non-chunked ones, we advise you to choose the same hash type as
+supported by wrapped remote so that your file listings look
+coherent.</p>
+<p>If your storage backend does not support MD5 or SHA1 but you need
+consistent file hashing, configure chunker with <code>md5all</code> or
+<code>sha1all</code>. These two modes guarantee given hash for all
+files. If wrapped remote doesn't support it, chunker will then add
+metadata to all files, even small. However, this can double the amount
+of small files in storage and incur additional service charges. You can
+even use chunker to force md5/sha1 support in any other remote at
+expense of sidecar meta objects by setting e.g.
+<code>hash_type=sha1all</code> to force hashsums and
+<code>chunk_size=1P</code> to effectively disable chunking.</p>
+<p>Normally, when a file is copied to chunker controlled remote, chunker
+will ask the file source for compatible file hash and revert to
+on-the-fly calculation if none is found. This involves some CPU overhead
+but provides a guarantee that given hashsum is available. Also, chunker
+will reject a server-side copy or move operation if source and
+destination hashsum types are different resulting in the extra network
+bandwidth, too. In some rare cases this may be undesired, so chunker
+provides two optional choices: <code>sha1quick</code> and
+<code>md5quick</code>. If the source does not support primary hash type
+and the quick mode is enabled, chunker will try to fall back to the
+secondary type. This will save CPU and bandwidth but can result in empty
+hashsums at destination. Beware of consequences: the <code>sync</code>
+command will revert (sometimes silently) to time/size comparison if
+compatible hashsums between source and target are not found.</p>
 <h3 id="modification-times-3">Modification times</h3>
-<p>Chunker stores modification times using the wrapped remote so support depends on that. For a small non-chunked file the chunker overlay simply manipulates modification time of the wrapped remote file. For a composite file with metadata chunker will get and set modification time of the metadata object on the wrapped remote. If file is chunked but metadata format is <code>none</code> then chunker will use modification time of the first data chunk.</p>
+<p>Chunker stores modification times using the wrapped remote so support
+depends on that. For a small non-chunked file the chunker overlay simply
+manipulates modification time of the wrapped remote file. For a
+composite file with metadata chunker will get and set modification time
+of the metadata object on the wrapped remote. If file is chunked but
+metadata format is <code>none</code> then chunker will use modification
+time of the first data chunk.</p>
 <h3 id="migrations">Migrations</h3>
-<p>The idiomatic way to migrate to a different chunk size, hash type, transaction style or chunk naming scheme is to:</p>
+<p>The idiomatic way to migrate to a different chunk size, hash type,
+transaction style or chunk naming scheme is to:</p>
 <ul>
-<li>Collect all your chunked files under a directory and have your chunker remote point to it.</li>
-<li>Create another directory (most probably on the same cloud storage) and configure a new remote with desired metadata format, hash type, chunk naming etc.</li>
-<li>Now run <code>rclone sync --interactive oldchunks: newchunks:</code> and all your data will be transparently converted in transfer. This may take some time, yet chunker will try server-side copy if possible.</li>
-<li>After checking data integrity you may remove configuration section of the old remote.</li>
+<li>Collect all your chunked files under a directory and have your
+chunker remote point to it.</li>
+<li>Create another directory (most probably on the same cloud storage)
+and configure a new remote with desired metadata format, hash type,
+chunk naming etc.</li>
+<li>Now run <code>rclone sync --interactive oldchunks: newchunks:</code>
+and all your data will be transparently converted in transfer. This may
+take some time, yet chunker will try server-side copy if possible.</li>
+<li>After checking data integrity you may remove configuration section
+of the old remote.</li>
 </ul>
-<p>If rclone gets killed during a long operation on a big composite file, hidden temporary chunks may stay in the directory. They will not be shown by the <code>list</code> command but will eat up your account quota. Please note that the <code>deletefile</code> command deletes only active chunks of a file. As a workaround, you can use remote of the wrapped file system to see them. An easy way to get rid of hidden garbage is to copy littered directory somewhere using the chunker remote and purge the original directory. The <code>copy</code> command will copy only active chunks while the <code>purge</code> will remove everything including garbage.</p>
+<p>If rclone gets killed during a long operation on a big composite
+file, hidden temporary chunks may stay in the directory. They will not
+be shown by the <code>list</code> command but will eat up your account
+quota. Please note that the <code>deletefile</code> command deletes only
+active chunks of a file. As a workaround, you can use remote of the
+wrapped file system to see them. An easy way to get rid of hidden
+garbage is to copy littered directory somewhere using the chunker remote
+and purge the original directory. The <code>copy</code> command will
+copy only active chunks while the <code>purge</code> will remove
+everything including garbage.</p>
 <h3 id="caveats-and-limitations">Caveats and Limitations</h3>
-<p>Chunker requires wrapped remote to support server-side <code>move</code> (or <code>copy</code> + <code>delete</code>) operations, otherwise it will explicitly refuse to start. This is because it internally renames temporary chunk files to their final names when an operation completes successfully.</p>
-<p>Chunker encodes chunk number in file name, so with default <code>name_format</code> setting it adds 17 characters. Also chunker adds 7 characters of temporary suffix during operations. Many file systems limit base file name without path by 255 characters. Using rclone's crypt remote as a base file system limits file name by 143 characters. Thus, maximum name length is 231 for most files and 119 for chunker-over-crypt. A user in need can change name format to e.g. <code>*.rcc##</code> and save 10 characters (provided at most 99 chunks per file).</p>
-<p>Note that a move implemented using the copy-and-delete method may incur double charging with some cloud storage providers.</p>
-<p>Chunker will not automatically rename existing chunks when you run <code>rclone config</code> on a live remote and change the chunk name format. Beware that in result of this some files which have been treated as chunks before the change can pop up in directory listings as normal files and vice versa. The same warning holds for the chunk size. If you desperately need to change critical chunking settings, you should run data migration as described above.</p>
-<p>If wrapped remote is case insensitive, the chunker overlay will inherit that property (so you can't have a file called "Hello.doc" and "hello.doc" in the same directory).</p>
-<p>Chunker included in rclone releases up to <code>v1.54</code> can sometimes fail to detect metadata produced by recent versions of rclone. We recommend users to keep rclone up-to-date to avoid data corruption.</p>
-<p>Changing <code>transactions</code> is dangerous and requires explicit migration.</p>
+<p>Chunker requires wrapped remote to support server-side
+<code>move</code> (or <code>copy</code> + <code>delete</code>)
+operations, otherwise it will explicitly refuse to start. This is
+because it internally renames temporary chunk files to their final names
+when an operation completes successfully.</p>
+<p>Chunker encodes chunk number in file name, so with default
+<code>name_format</code> setting it adds 17 characters. Also chunker
+adds 7 characters of temporary suffix during operations. Many file
+systems limit base file name without path by 255 characters. Using
+rclone's crypt remote as a base file system limits file name by 143
+characters. Thus, maximum name length is 231 for most files and 119 for
+chunker-over-crypt. A user in need can change name format to e.g.
+<code>*.rcc##</code> and save 10 characters (provided at most 99 chunks
+per file).</p>
+<p>Note that a move implemented using the copy-and-delete method may
+incur double charging with some cloud storage providers.</p>
+<p>Chunker will not automatically rename existing chunks when you run
+<code>rclone config</code> on a live remote and change the chunk name
+format. Beware that in result of this some files which have been treated
+as chunks before the change can pop up in directory listings as normal
+files and vice versa. The same warning holds for the chunk size. If you
+desperately need to change critical chunking settings, you should run
+data migration as described above.</p>
+<p>If wrapped remote is case insensitive, the chunker overlay will
+inherit that property (so you can't have a file called "Hello.doc" and
+"hello.doc" in the same directory).</p>
+<p>Chunker included in rclone releases up to <code>v1.54</code> can
+sometimes fail to detect metadata produced by recent versions of rclone.
+We recommend users to keep rclone up-to-date to avoid data
+corruption.</p>
+<p>Changing <code>transactions</code> is dangerous and requires explicit
+migration.</p>
 <h3 id="standard-options-6">Standard options</h3>
-<p>Here are the Standard options specific to chunker (Transparently chunk/split large files).</p>
+<p>Here are the Standard options specific to chunker (Transparently
+chunk/split large files).</p>
 <h4 id="chunker-remote">--chunker-remote</h4>
 <p>Remote to chunk/unchunk.</p>
-<p>Normally should contain a ':' and a path, e.g. "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not recommended).</p>
+<p>Normally should contain a ':' and a path, e.g.
+"myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not
+recommended).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: remote</li>
@@ -20116,7 +30333,8 @@ y/e/d&gt; y</code></pre>
 <ul>
 <li>"none"
 <ul>
-<li>Pass any hash supported by wrapped remote for non-chunked files.</li>
+<li>Pass any hash supported by wrapped remote for non-chunked
+files.</li>
 <li>Return nothing otherwise.</li>
 </ul></li>
 <li>"md5"
@@ -20147,10 +30365,16 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul>
 <h3 id="advanced-options-6">Advanced options</h3>
-<p>Here are the Advanced options specific to chunker (Transparently chunk/split large files).</p>
+<p>Here are the Advanced options specific to chunker (Transparently
+chunk/split large files).</p>
 <h4 id="chunker-name-format">--chunker-name-format</h4>
 <p>String format of chunk file names.</p>
-<p>The two placeholders are: base file name (*) and chunk number (#...). There must be one and only one asterisk and one or more consecutive hash characters. If chunk number has less digits than the number of hashes, it is left-padded by zeros. If there are more digits in the number, they are left as is. Possible chunk files are ignored if their name does not match given format.</p>
+<p>The two placeholders are: base file name (*) and chunk number (#...).
+There must be one and only one asterisk and one or more consecutive hash
+characters. If chunk number has less digits than the number of hashes,
+it is left-padded by zeros. If there are more digits in the number, they
+are left as is. Possible chunk files are ignored if their name does not
+match given format.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: name_format</li>
@@ -20170,7 +30394,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="chunker-meta-format">--chunker-meta-format</h4>
 <p>Format of the metadata object or "none".</p>
-<p>By default "simplejson". Metadata is a small JSON file named after the composite file.</p>
+<p>By default "simplejson". Metadata is a small JSON file named after
+the composite file.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: meta_format</li>
@@ -20193,7 +30418,8 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul>
 <h4 id="chunker-fail-hard">--chunker-fail-hard</h4>
-<p>Choose how chunker should handle files with missing or invalid chunks.</p>
+<p>Choose how chunker should handle files with missing or invalid
+chunks.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: fail_hard</li>
@@ -20213,7 +30439,8 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul>
 <h4 id="chunker-transactions">--chunker-transactions</h4>
-<p>Choose how chunker should handle temporary files during transactions.</p>
+<p>Choose how chunker should handle temporary files during
+transactions.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: transactions</li>
@@ -20228,17 +30455,23 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 <li>"norename"
 <ul>
-<li>Leave temporary file names and write transaction ID to metadata file.</li>
-<li>Metadata is required for no rename transactions (meta format cannot be "none").</li>
-<li>If you are using norename transactions you should be careful not to downgrade Rclone</li>
-<li>as older versions of Rclone don't support this transaction style and will misinterpret</li>
+<li>Leave temporary file names and write transaction ID to metadata
+file.</li>
+<li>Metadata is required for no rename transactions (meta format cannot
+be "none").</li>
+<li>If you are using norename transactions you should be careful not to
+downgrade Rclone</li>
+<li>as older versions of Rclone don't support this transaction style and
+will misinterpret</li>
 <li>files manipulated by norename transactions.</li>
 <li>This method is EXPERIMENTAL, don't use on production systems.</li>
 </ul></li>
 <li>"auto"
 <ul>
-<li>Rename or norename will be used depending on capabilities of the backend.</li>
-<li>If meta format is set to "none", rename transactions will always be used.</li>
+<li>Rename or norename will be used depending on capabilities of the
+backend.</li>
+<li>If meta format is set to "none", rename transactions will always be
+used.</li>
 <li>This method is EXPERIMENTAL, don't use on production systems.</li>
 </ul></li>
 </ul></li>
@@ -20253,10 +30486,14 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h1 id="citrix-sharefile">Citrix ShareFile</h1>
-<p><a href="https://sharefile.com">Citrix ShareFile</a> is a secure file sharing and transfer service aimed as business.</p>
+<p><a href="https://sharefile.com">Citrix ShareFile</a> is a secure file
+sharing and transfer service aimed as business.</p>
 <h2 id="configuration-7">Configuration</h2>
-<p>The initial setup for Citrix ShareFile involves getting a token from Citrix ShareFile which you can in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>The initial setup for Citrix ShareFile involves getting a token from
+Citrix ShareFile which you can in your browser.
+<code>rclone config</code> walks you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -20316,8 +30553,15 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Citrix ShareFile. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from Citrix ShareFile. This only runs from the
+moment it opens your browser to the moment you get back the verification
+code. This is on <code>http://127.0.0.1:53682/</code> and this it may
+require you to unblock it temporarily if you are running a host
+firewall.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your ShareFile</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -20325,14 +30569,27 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an ShareFile directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h3 id="modification-times-and-hashes-3">Modification times and hashes</h3>
-<p>ShareFile allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
-<p>ShareFile supports MD5 type hashes, so you can use the <code>--checksum</code> flag.</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h3 id="modification-times-and-hashes-3">Modification times and
+hashes</h3>
+<p>ShareFile allows modification times to be set on objects accurate to
+1 second. These will be used to detect whether objects need syncing or
+not.</p>
+<p>ShareFile supports MD5 type hashes, so you can use the
+<code>--checksum</code> flag.</p>
 <h3 id="transfers-2">Transfers</h3>
-<p>For files above 128 MiB rclone will use a chunked transfer. Rclone will upload up to <code>--transfers</code> chunks at the same time (shared among all the multipart uploads). Chunks are buffered in memory and are normally 64 MiB so increasing <code>--transfers</code> will increase memory use.</p>
-<h3 id="restricted-filename-characters-4">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>For files above 128 MiB rclone will use a chunked transfer. Rclone
+will upload up to <code>--transfers</code> chunks at the same time
+(shared among all the multipart uploads). Chunks are buffered in memory
+and are normally 64 MiB so increasing <code>--transfers</code> will
+increase memory use.</p>
+<h3 id="restricted-filename-characters-4">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -20384,7 +30641,9 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not start or end with the following characters. These only get replaced if they are the first or last character in the name:</p>
+<p>File names can also not start or end with the following characters.
+These only get replaced if they are the first or last character in the
+name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -20406,9 +30665,12 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="standard-options-7">Standard options</h3>
-<p>Here are the Standard options specific to sharefile (Citrix Sharefile).</p>
+<p>Here are the Standard options specific to sharefile (Citrix
+Sharefile).</p>
 <h4 id="sharefile-client-id">--sharefile-client-id</h4>
 <p>OAuth Client Id.</p>
 <p>Leave blank normally.</p>
@@ -20431,7 +30693,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="sharefile-root-folder-id">--sharefile-root-folder-id</h4>
 <p>ID of the root folder.</p>
-<p>Leave blank to access "Personal Folders". You can use one of the standard values here or any folder ID (long hex number ID).</p>
+<p>Leave blank to access "Personal Folders". You can use one of the
+standard values here or any folder ID (long hex number ID).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_id</li>
@@ -20458,12 +30721,14 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 <li>"top"
 <ul>
-<li>Access the home, favorites, and shared folders as well as the connectors.</li>
+<li>Access the home, favorites, and shared folders as well as the
+connectors.</li>
 </ul></li>
 </ul></li>
 </ul>
 <h3 id="advanced-options-7">Advanced options</h3>
-<p>Here are the Advanced options specific to sharefile (Citrix Sharefile).</p>
+<p>Here are the Advanced options specific to sharefile (Citrix
+Sharefile).</p>
 <h4 id="sharefile-token">--sharefile-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
 <p>Properties:</p>
@@ -20505,7 +30770,8 @@ y/e/d&gt; y</code></pre>
 <h4 id="sharefile-chunk-size">--sharefile-chunk-size</h4>
 <p>Upload chunk size.</p>
 <p>Must a power of 2 &gt;= 256k.</p>
-<p>Making this larger will improve performance, but note that each chunk is buffered in memory one per transfer.</p>
+<p>Making this larger will improve performance, but note that each chunk
+is buffered in memory one per transfer.</p>
 <p>Reducing this will reduce memory usage but decrease performance.</p>
 <p>Properties:</p>
 <ul>
@@ -20516,7 +30782,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="sharefile-endpoint">--sharefile-endpoint</h4>
 <p>Endpoint for API calls.</p>
-<p>This is usually auto discovered as part of the oauth process, but can be set manually to something like: https://XXX.sharefile.com</p>
+<p>This is usually auto discovered as part of the oauth process, but can
+be set manually to something like: https://XXX.sharefile.com</p>
 <p>Properties:</p>
 <ul>
 <li>Config: endpoint</li>
@@ -20526,13 +30793,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="sharefile-encoding">--sharefile-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_SHAREFILE_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,LeftPeriod,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="sharefile-description">--sharefile-description</h4>
 <p>Description of the remote.</p>
@@ -20544,23 +30813,98 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-9">Limitations</h2>
-<p>Note that ShareFile is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
+<p>Note that ShareFile is case insensitive so you can't have a file
+called "Hello.doc" and one called "hello.doc".</p>
 <p>ShareFile only supports filenames up to 256 characters in length.</p>
-<p><code>rclone about</code> is not supported by the Citrix ShareFile backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the Citrix ShareFile
+backend. Backends without this capability cannot determine free space
+for an rclone mount or use policy <code>mfs</code> (most free space) as
+a member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="crypt">Crypt</h1>
-<p>Rclone <code>crypt</code> remotes encrypt and decrypt other remotes.</p>
-<p>A remote of type <code>crypt</code> does not access a <a href="https://rclone.org/overview/">storage system</a> directly, but instead wraps another remote, which in turn accesses the storage system. This is similar to how <a href="https://rclone.org/alias/">alias</a>, <a href="https://rclone.org/union/">union</a>, <a href="https://rclone.org/chunker/">chunker</a> and a few others work. It makes the usage very flexible, as you can add a layer, in this case an encryption layer, on top of any other backend, even in multiple layers. Rclone's functionality can be used as with any other remote, for example you can <a href="https://rclone.org/commands/rclone_mount/">mount</a> a crypt remote.</p>
-<p>Accessing a storage system through a crypt remote realizes client-side encryption, which makes it safe to keep your data in a location you do not trust will not get compromised. When working against the <code>crypt</code> remote, rclone will automatically encrypt (before uploading) and decrypt (after downloading) on your local system as needed on the fly, leaving the data encrypted at rest in the wrapped remote. If you access the storage system using an application other than rclone, or access the wrapped remote directly using rclone, there will not be any encryption/decryption: Downloading existing content will just give you the encrypted (scrambled) format, and anything you upload will <em>not</em> become encrypted.</p>
-<p>The encryption is a secret-key encryption (also called symmetric key encryption) algorithm, where a password (or pass phrase) is used to generate real encryption key. The password can be supplied by user, or you may chose to let rclone generate one. It will be stored in the configuration file, in a lightly obscured form. If you are in an environment where you are not able to keep your configuration secured, you should add <a href="https://rclone.org/docs/#configuration-encryption">configuration encryption</a> as protection. As long as you have this configuration file, you will be able to decrypt your data. Without the configuration file, as long as you remember the password (or keep it in a safe place), you can re-create the configuration and gain access to the existing data. You may also configure a corresponding remote in a different installation to access the same data. See below for guidance to <a href="#changing-password">changing password</a>.</p>
-<p>Encryption uses <a href="https://en.wikipedia.org/wiki/Salt_(cryptography)">cryptographic salt</a>, to permute the encryption key so that the same string may be encrypted in different ways. When configuring the crypt remote it is optional to enter a salt, or to let rclone generate a unique salt. If omitted, rclone uses a built-in unique string. Normally in cryptography, the salt is stored together with the encrypted content, and do not have to be memorized by the user. This is not the case in rclone, because rclone does not store any additional information on the remotes. Use of custom salt is effectively a second password that must be memorized.</p>
-<p><a href="#file-encryption">File content</a> encryption is performed using <a href="https://godoc.org/golang.org/x/crypto/nacl/secretbox">NaCl SecretBox</a>, based on XSalsa20 cipher and Poly1305 for integrity. <a href="#name-encryption">Names</a> (file- and directory names) are also encrypted by default, but this has some implications and is therefore possible to be turned off.</p>
+<p>Rclone <code>crypt</code> remotes encrypt and decrypt other
+remotes.</p>
+<p>A remote of type <code>crypt</code> does not access a <a
+href="https://rclone.org/overview/">storage system</a> directly, but
+instead wraps another remote, which in turn accesses the storage system.
+This is similar to how <a href="https://rclone.org/alias/">alias</a>, <a
+href="https://rclone.org/union/">union</a>, <a
+href="https://rclone.org/chunker/">chunker</a> and a few others work. It
+makes the usage very flexible, as you can add a layer, in this case an
+encryption layer, on top of any other backend, even in multiple layers.
+Rclone's functionality can be used as with any other remote, for example
+you can <a href="https://rclone.org/commands/rclone_mount/">mount</a> a
+crypt remote.</p>
+<p>Accessing a storage system through a crypt remote realizes
+client-side encryption, which makes it safe to keep your data in a
+location you do not trust will not get compromised. When working against
+the <code>crypt</code> remote, rclone will automatically encrypt (before
+uploading) and decrypt (after downloading) on your local system as
+needed on the fly, leaving the data encrypted at rest in the wrapped
+remote. If you access the storage system using an application other than
+rclone, or access the wrapped remote directly using rclone, there will
+not be any encryption/decryption: Downloading existing content will just
+give you the encrypted (scrambled) format, and anything you upload will
+<em>not</em> become encrypted.</p>
+<p>The encryption is a secret-key encryption (also called symmetric key
+encryption) algorithm, where a password (or pass phrase) is used to
+generate real encryption key. The password can be supplied by user, or
+you may chose to let rclone generate one. It will be stored in the
+configuration file, in a lightly obscured form. If you are in an
+environment where you are not able to keep your configuration secured,
+you should add <a
+href="https://rclone.org/docs/#configuration-encryption">configuration
+encryption</a> as protection. As long as you have this configuration
+file, you will be able to decrypt your data. Without the configuration
+file, as long as you remember the password (or keep it in a safe place),
+you can re-create the configuration and gain access to the existing
+data. You may also configure a corresponding remote in a different
+installation to access the same data. See below for guidance to <a
+href="#changing-password">changing password</a>.</p>
+<p>Encryption uses <a
+href="https://en.wikipedia.org/wiki/Salt_(cryptography)">cryptographic
+salt</a>, to permute the encryption key so that the same string may be
+encrypted in different ways. When configuring the crypt remote it is
+optional to enter a salt, or to let rclone generate a unique salt. If
+omitted, rclone uses a built-in unique string. Normally in cryptography,
+the salt is stored together with the encrypted content, and do not have
+to be memorized by the user. This is not the case in rclone, because
+rclone does not store any additional information on the remotes. Use of
+custom salt is effectively a second password that must be memorized.</p>
+<p><a href="#file-encryption">File content</a> encryption is performed
+using <a
+href="https://godoc.org/golang.org/x/crypto/nacl/secretbox">NaCl
+SecretBox</a>, based on XSalsa20 cipher and Poly1305 for integrity. <a
+href="#name-encryption">Names</a> (file- and directory names) are also
+encrypted by default, but this has some implications and is therefore
+possible to be turned off.</p>
 <h2 id="configuration-8">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>secret</code>.</p>
-<p>To use <code>crypt</code>, first set up the underlying remote. Follow the <code>rclone config</code> instructions for the specific backend.</p>
-<p>Before configuring the crypt remote, check the underlying remote is working. In this example the underlying remote is called <code>remote</code>. We will configure a path <code>path</code> within this remote to contain the encrypted content. Anything inside <code>remote:path</code> will be encrypted and anything outside will not.</p>
-<p>Configure <code>crypt</code> using <code>rclone config</code>. In this example the <code>crypt</code> remote is called <code>secret</code>, to differentiate it from the underlying <code>remote</code>.</p>
-<p>When you are done you can use the crypt remote named <code>secret</code> just as you would with any other remote, e.g. <code>rclone copy D:\docs secret:\docs</code>, and rclone will encrypt and decrypt as needed on the fly. If you access the wrapped remote <code>remote:path</code> directly you will bypass the encryption, and anything you read will be in encrypted form, and anything you write will be unencrypted. To avoid issues it is best to configure a dedicated path for encrypted content, and access it exclusively through a crypt remote.</p>
+<p>Here is an example of how to make a remote called
+<code>secret</code>.</p>
+<p>To use <code>crypt</code>, first set up the underlying remote. Follow
+the <code>rclone config</code> instructions for the specific
+backend.</p>
+<p>Before configuring the crypt remote, check the underlying remote is
+working. In this example the underlying remote is called
+<code>remote</code>. We will configure a path <code>path</code> within
+this remote to contain the encrypted content. Anything inside
+<code>remote:path</code> will be encrypted and anything outside will
+not.</p>
+<p>Configure <code>crypt</code> using <code>rclone config</code>. In
+this example the <code>crypt</code> remote is called
+<code>secret</code>, to differentiate it from the underlying
+<code>remote</code>.</p>
+<p>When you are done you can use the crypt remote named
+<code>secret</code> just as you would with any other remote, e.g.
+<code>rclone copy D:\docs secret:\docs</code>, and rclone will encrypt
+and decrypt as needed on the fly. If you access the wrapped remote
+<code>remote:path</code> directly you will bypass the encryption, and
+anything you read will be in encrypted form, and anything you write will
+be unencrypted. To avoid issues it is best to configure a dedicated path
+for encrypted content, and access it exclusively through a crypt
+remote.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -20646,29 +30990,96 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt;</code></pre>
-<p><strong>Important</strong> The crypt password stored in <code>rclone.conf</code> is lightly obscured. That only protects it from cursory inspection. It is not secure unless <a href="https://rclone.org/docs/#configuration-encryption">configuration encryption</a> of <code>rclone.conf</code> is specified.</p>
-<p>A long passphrase is recommended, or <code>rclone config</code> can generate a random one.</p>
-<p>The obscured password is created using AES-CTR with a static key. The IV (nonce) is stored verbatim at the beginning of the obscured password. This static key is shared between all versions of rclone.</p>
-<p>If you reconfigure rclone with the same passwords/passphrases elsewhere it will be compatible, but the obscured version will be different due to the different salt.</p>
+<p><strong>Important</strong> The crypt password stored in
+<code>rclone.conf</code> is lightly obscured. That only protects it from
+cursory inspection. It is not secure unless <a
+href="https://rclone.org/docs/#configuration-encryption">configuration
+encryption</a> of <code>rclone.conf</code> is specified.</p>
+<p>A long passphrase is recommended, or <code>rclone config</code> can
+generate a random one.</p>
+<p>The obscured password is created using AES-CTR with a static key. The
+IV (nonce) is stored verbatim at the beginning of the obscured password.
+This static key is shared between all versions of rclone.</p>
+<p>If you reconfigure rclone with the same passwords/passphrases
+elsewhere it will be compatible, but the obscured version will be
+different due to the different salt.</p>
 <p>Rclone does not encrypt</p>
 <ul>
 <li>file length - this can be calculated within 16 bytes</li>
 <li>modification time - used for syncing</li>
 </ul>
 <h3 id="specifying-the-remote-1">Specifying the remote</h3>
-<p>When configuring the remote to encrypt/decrypt, you may specify any string that rclone accepts as a source/destination of other commands.</p>
-<p>The primary use case is to specify the path into an already configured remote (e.g. <code>remote:path/to/dir</code> or <code>remote:bucket</code>), such that data in a remote untrusted location can be stored encrypted.</p>
-<p>You may also specify a local filesystem path, such as <code>/path/to/dir</code> on Linux, <code>C:\path\to\dir</code> on Windows. By creating a crypt remote pointing to such a local filesystem path, you can use rclone as a utility for pure local file encryption, for example to keep encrypted files on a removable USB drive.</p>
-<p><strong>Note</strong>: A string which do not contain a <code>:</code> will by rclone be treated as a relative path in the local filesystem. For example, if you enter the name <code>remote</code> without the trailing <code>:</code>, it will be treated as a subdirectory of the current directory with name "remote".</p>
-<p>If a path <code>remote:path/to/dir</code> is specified, rclone stores encrypted files in <code>path/to/dir</code> on the remote. With file name encryption, files saved to <code>secret:subdir/subfile</code> are stored in the unencrypted path <code>path/to/dir</code> but the <code>subdir/subpath</code> element is encrypted.</p>
-<p>The path you specify does not have to exist, rclone will create it when needed.</p>
-<p>If you intend to use the wrapped remote both directly for keeping unencrypted content, as well as through a crypt remote for encrypted content, it is recommended to point the crypt remote to a separate directory within the wrapped remote. If you use a bucket-based storage system (e.g. Swift, S3, Google Compute Storage, B2) it is generally advisable to wrap the crypt remote around a specific bucket (<code>s3:bucket</code>). If wrapping around the entire root of the storage (<code>s3:</code>), and use the optional file name encryption, rclone will encrypt the bucket name.</p>
+<p>When configuring the remote to encrypt/decrypt, you may specify any
+string that rclone accepts as a source/destination of other
+commands.</p>
+<p>The primary use case is to specify the path into an already
+configured remote (e.g. <code>remote:path/to/dir</code> or
+<code>remote:bucket</code>), such that data in a remote untrusted
+location can be stored encrypted.</p>
+<p>You may also specify a local filesystem path, such as
+<code>/path/to/dir</code> on Linux, <code>C:\path\to\dir</code> on
+Windows. By creating a crypt remote pointing to such a local filesystem
+path, you can use rclone as a utility for pure local file encryption,
+for example to keep encrypted files on a removable USB drive.</p>
+<p><strong>Note</strong>: A string which do not contain a <code>:</code>
+will by rclone be treated as a relative path in the local filesystem.
+For example, if you enter the name <code>remote</code> without the
+trailing <code>:</code>, it will be treated as a subdirectory of the
+current directory with name "remote".</p>
+<p>If a path <code>remote:path/to/dir</code> is specified, rclone stores
+encrypted files in <code>path/to/dir</code> on the remote. With file
+name encryption, files saved to <code>secret:subdir/subfile</code> are
+stored in the unencrypted path <code>path/to/dir</code> but the
+<code>subdir/subpath</code> element is encrypted.</p>
+<p>The path you specify does not have to exist, rclone will create it
+when needed.</p>
+<p>If you intend to use the wrapped remote both directly for keeping
+unencrypted content, as well as through a crypt remote for encrypted
+content, it is recommended to point the crypt remote to a separate
+directory within the wrapped remote. If you use a bucket-based storage
+system (e.g. Swift, S3, Google Compute Storage, B2) it is generally
+advisable to wrap the crypt remote around a specific bucket
+(<code>s3:bucket</code>). If wrapping around the entire root of the
+storage (<code>s3:</code>), and use the optional file name encryption,
+rclone will encrypt the bucket name.</p>
 <h3 id="changing-password">Changing password</h3>
-<p>Should the password, or the configuration file containing a lightly obscured form of the password, be compromised, you need to re-encrypt your data with a new password. Since rclone uses secret-key encryption, where the encryption key is generated directly from the password kept on the client, it is not possible to change the password/key of already encrypted content. Just changing the password configured for an existing crypt remote means you will no longer able to decrypt any of the previously encrypted content. The only possibility is to re-upload everything via a crypt remote configured with your new password.</p>
-<p>Depending on the size of your data, your bandwidth, storage quota etc, there are different approaches you can take: - If you have everything in a different location, for example on your local system, you could remove all of the prior encrypted files, change the password for your configured crypt remote (or delete and re-create the crypt configuration), and then re-upload everything from the alternative location. - If you have enough space on the storage system you can create a new crypt remote pointing to a separate directory on the same backend, and then use rclone to copy everything from the original crypt remote to the new, effectively decrypting everything on the fly using the old password and re-encrypting using the new password. When done, delete the original crypt remote directory and finally the rclone crypt configuration with the old password. All data will be streamed from the storage system and back, so you will get half the bandwidth and be charged twice if you have upload and download quota on the storage system.</p>
-<p><strong>Note</strong>: A security problem related to the random password generator was fixed in rclone version 1.53.3 (released 2020-11-19). Passwords generated by rclone config in version 1.49.0 (released 2019-08-26) to 1.53.2 (released 2020-10-26) are not considered secure and should be changed. If you made up your own password, or used rclone version older than 1.49.0 or newer than 1.53.2 to generate it, you are <em>not</em> affected by this issue. See <a href="https://github.com/rclone/rclone/issues/4783">issue #4783</a> for more details, and a tool you can use to check if you are affected.</p>
+<p>Should the password, or the configuration file containing a lightly
+obscured form of the password, be compromised, you need to re-encrypt
+your data with a new password. Since rclone uses secret-key encryption,
+where the encryption key is generated directly from the password kept on
+the client, it is not possible to change the password/key of already
+encrypted content. Just changing the password configured for an existing
+crypt remote means you will no longer able to decrypt any of the
+previously encrypted content. The only possibility is to re-upload
+everything via a crypt remote configured with your new password.</p>
+<p>Depending on the size of your data, your bandwidth, storage quota
+etc, there are different approaches you can take: - If you have
+everything in a different location, for example on your local system,
+you could remove all of the prior encrypted files, change the password
+for your configured crypt remote (or delete and re-create the crypt
+configuration), and then re-upload everything from the alternative
+location. - If you have enough space on the storage system you can
+create a new crypt remote pointing to a separate directory on the same
+backend, and then use rclone to copy everything from the original crypt
+remote to the new, effectively decrypting everything on the fly using
+the old password and re-encrypting using the new password. When done,
+delete the original crypt remote directory and finally the rclone crypt
+configuration with the old password. All data will be streamed from the
+storage system and back, so you will get half the bandwidth and be
+charged twice if you have upload and download quota on the storage
+system.</p>
+<p><strong>Note</strong>: A security problem related to the random
+password generator was fixed in rclone version 1.53.3 (released
+2020-11-19). Passwords generated by rclone config in version 1.49.0
+(released 2019-08-26) to 1.53.2 (released 2020-10-26) are not considered
+secure and should be changed. If you made up your own password, or used
+rclone version older than 1.49.0 or newer than 1.53.2 to generate it,
+you are <em>not</em> affected by this issue. See <a
+href="https://github.com/rclone/rclone/issues/4783">issue #4783</a> for
+more details, and a tool you can use to check if you are affected.</p>
 <h3 id="example">Example</h3>
-<p>Create the following file structure using "standard" file name encryption.</p>
+<p>Create the following file structure using "standard" file name
+encryption.</p>
 <pre><code>plaintext/
 ├── file0.txt
 ├── file1.txt
@@ -20697,7 +31108,9 @@ $ rclone -q ls secret:
         8 file2.txt
         9 file3.txt
        10 subsubdir/file4.txt</code></pre>
-<p>Without file name encryption <code>.bin</code> extensions are added to underlying names. This prevents the cloud provider attempting to interpret file content.</p>
+<p>Without file name encryption <code>.bin</code> extensions are added
+to underlying names. This prevents the cloud provider attempting to
+interpret file content.</p>
 <pre><code>$ rclone -q ls remote:path
        54 file0.txt.bin
        57 subdir/file3.txt.bin
@@ -20721,9 +31134,17 @@ $ rclone -q ls secret:
 <li>can use shortcuts to shorten the directory recursion</li>
 </ul>
 <p>Obfuscation</p>
-<p>This is a simple "rotate" of the filename, with each file having a rot distance based on the filename. Rclone stores the distance at the beginning of the filename. A file called "hello" may become "53.jgnnq".</p>
-<p>Obfuscation is not a strong encryption of filenames, but hinders automated scanning tools picking up on filename patterns. It is an intermediate between "off" and "standard" which allows for longer path segment names.</p>
-<p>There is a possibility with some unicode based filenames that the obfuscation is weak and may map lower case characters to upper case equivalents.</p>
+<p>This is a simple "rotate" of the filename, with each file having a
+rot distance based on the filename. Rclone stores the distance at the
+beginning of the filename. A file called "hello" may become
+"53.jgnnq".</p>
+<p>Obfuscation is not a strong encryption of filenames, but hinders
+automated scanning tools picking up on filename patterns. It is an
+intermediate between "off" and "standard" which allows for longer path
+segment names.</p>
+<p>There is a possibility with some unicode based filenames that the
+obfuscation is weak and may map lower case characters to upper case
+equivalents.</p>
 <p>Obfuscation cannot be relied upon for strong protection.</p>
 <ul>
 <li>file names very lightly obfuscated</li>
@@ -20732,24 +31153,48 @@ $ rclone -q ls secret:
 <li>directory structure visible</li>
 <li>identical files names will have identical uploaded names</li>
 </ul>
-<p>Cloud storage systems have limits on file name length and total path length which rclone is more likely to breach using "Standard" file name encryption. Where file names are 143 or fewer characters in length issues should not be encountered, irrespective of cloud storage provider.</p>
-<p>An experimental advanced option <code>filename_encoding</code> is now provided to address this problem to a certain degree. For cloud storage systems with case sensitive file names (e.g. Google Drive), <code>base64</code> can be used to reduce file name length. For cloud storage systems using UTF-16 to store file names internally (e.g. OneDrive, Dropbox, Box), <code>base32768</code> can be used to drastically reduce file name length.</p>
-<p>An alternative, future rclone file name encryption mode may tolerate backend provider path length limits.</p>
+<p>Cloud storage systems have limits on file name length and total path
+length which rclone is more likely to breach using "Standard" file name
+encryption. Where file names are 143 or fewer characters in length
+issues should not be encountered, irrespective of cloud storage
+provider.</p>
+<p>An experimental advanced option <code>filename_encoding</code> is now
+provided to address this problem to a certain degree. For cloud storage
+systems with case sensitive file names (e.g. Google Drive),
+<code>base64</code> can be used to reduce file name length. For cloud
+storage systems using UTF-16 to store file names internally (e.g.
+OneDrive, Dropbox, Box), <code>base32768</code> can be used to
+drastically reduce file name length.</p>
+<p>An alternative, future rclone file name encryption mode may tolerate
+backend provider path length limits.</p>
 <h3 id="directory-name-encryption">Directory name encryption</h3>
-<p>Crypt offers the option of encrypting dir names or leaving them intact. There are two options:</p>
+<p>Crypt offers the option of encrypting dir names or leaving them
+intact. There are two options:</p>
 <p>True</p>
-<p>Encrypts the whole file path including directory names Example: <code>1/12/123.txt</code> is encrypted to <code>p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0</code></p>
+<p>Encrypts the whole file path including directory names Example:
+<code>1/12/123.txt</code> is encrypted to
+<code>p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0</code></p>
 <p>False</p>
-<p>Only encrypts file names, skips directory names Example: <code>1/12/123.txt</code> is encrypted to <code>1/12/qgm4avr35m5loi1th53ato71v0</code></p>
-<h3 id="modification-times-and-hashes-4">Modification times and hashes</h3>
-<p>Crypt stores modification times using the underlying remote so support depends on that.</p>
-<p>Hashes are not stored for crypt. However the data integrity is protected by an extremely strong crypto authenticator.</p>
-<p>Use the <code>rclone cryptcheck</code> command to check the integrity of an encrypted remote instead of <code>rclone check</code> which can't check the checksums properly.</p>
+<p>Only encrypts file names, skips directory names Example:
+<code>1/12/123.txt</code> is encrypted to
+<code>1/12/qgm4avr35m5loi1th53ato71v0</code></p>
+<h3 id="modification-times-and-hashes-4">Modification times and
+hashes</h3>
+<p>Crypt stores modification times using the underlying remote so
+support depends on that.</p>
+<p>Hashes are not stored for crypt. However the data integrity is
+protected by an extremely strong crypto authenticator.</p>
+<p>Use the <code>rclone cryptcheck</code> command to check the integrity
+of an encrypted remote instead of <code>rclone check</code> which can't
+check the checksums properly.</p>
 <h3 id="standard-options-8">Standard options</h3>
-<p>Here are the Standard options specific to crypt (Encrypt/Decrypt a remote).</p>
+<p>Here are the Standard options specific to crypt (Encrypt/Decrypt a
+remote).</p>
 <h4 id="crypt-remote">--crypt-remote</h4>
 <p>Remote to encrypt/decrypt.</p>
-<p>Normally should contain a ':' and a path, e.g. "myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not recommended).</p>
+<p>Normally should contain a ':' and a path, e.g.
+"myremote:path/to/dir", "myremote:bucket" or maybe "myremote:" (not
+recommended).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: remote</li>
@@ -20783,9 +31228,11 @@ $ rclone -q ls secret:
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="crypt-directory-name-encryption">--crypt-directory-name-encryption</h4>
+<h4
+id="crypt-directory-name-encryption">--crypt-directory-name-encryption</h4>
 <p>Option to either encrypt directory names or leave them intact.</p>
-<p>NB If filename_encryption is "off" then this option will do nothing.</p>
+<p>NB If filename_encryption is "off" then this option will do
+nothing.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: directory_name_encryption</li>
@@ -20806,7 +31253,9 @@ $ rclone -q ls secret:
 </ul>
 <h4 id="crypt-password">--crypt-password</h4>
 <p>Password or pass phrase for encryption.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -20816,8 +31265,11 @@ $ rclone -q ls secret:
 </ul>
 <h4 id="crypt-password2">--crypt-password2</h4>
 <p>Password or pass phrase for salt.</p>
-<p>Optional but recommended. Should be different to the previous password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>Optional but recommended. Should be different to the previous
+password.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password2</li>
@@ -20826,12 +31278,19 @@ $ rclone -q ls secret:
 <li>Required: false</li>
 </ul>
 <h3 id="advanced-options-8">Advanced options</h3>
-<p>Here are the Advanced options specific to crypt (Encrypt/Decrypt a remote).</p>
-<h4 id="crypt-server-side-across-configs">--crypt-server-side-across-configs</h4>
+<p>Here are the Advanced options specific to crypt (Encrypt/Decrypt a
+remote).</p>
+<h4
+id="crypt-server-side-across-configs">--crypt-server-side-across-configs</h4>
 <p>Deprecated: use --server-side-across-configs instead.</p>
-<p>Allow server-side operations (e.g. copy) to work across different crypt configs.</p>
-<p>Normally this option is not what you want, but if you have two crypts pointing to the same backend you can use it.</p>
-<p>This can be used, for example, to change file name encryption type without re-uploading all the data. Just make two crypt backends pointing to two different directories with the single changed parameter and use rclone move to move the files between the crypt remotes.</p>
+<p>Allow server-side operations (e.g. copy) to work across different
+crypt configs.</p>
+<p>Normally this option is not what you want, but if you have two crypts
+pointing to the same backend you can use it.</p>
+<p>This can be used, for example, to change file name encryption type
+without re-uploading all the data. Just make two crypt backends pointing
+to two different directories with the single changed parameter and use
+rclone move to move the files between the crypt remotes.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: server_side_across_configs</li>
@@ -20841,8 +31300,12 @@ $ rclone -q ls secret:
 </ul>
 <h4 id="crypt-show-mapping">--crypt-show-mapping</h4>
 <p>For all files listed show how the names encrypt.</p>
-<p>If this flag is set then for each file that the remote is asked to list, it will log (at level INFO) a line stating the decrypted file name and the encrypted file name.</p>
-<p>This is so you can work out which encrypted names are which decrypted names just in case you need to do something with the encrypted file names, or for debugging purposes.</p>
+<p>If this flag is set then for each file that the remote is asked to
+list, it will log (at level INFO) a line stating the decrypted file name
+and the encrypted file name.</p>
+<p>This is so you can work out which encrypted names are which decrypted
+names just in case you need to do something with the encrypted file
+names, or for debugging purposes.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: show_mapping</li>
@@ -20872,7 +31335,9 @@ $ rclone -q ls secret:
 </ul>
 <h4 id="crypt-pass-bad-blocks">--crypt-pass-bad-blocks</h4>
 <p>If set this will pass bad blocks through as all 0.</p>
-<p>This should not be set in normal operation, it should only be set if trying to recover an encrypted file with errors and it is desired to recover as much of the file as possible.</p>
+<p>This should not be set in normal operation, it should only be set if
+trying to recover an encrypted file with errors and it is desired to
+recover as much of the file as possible.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass_bad_blocks</li>
@@ -20881,8 +31346,12 @@ $ rclone -q ls secret:
 <li>Default: false</li>
 </ul>
 <h4 id="crypt-strict-names">--crypt-strict-names</h4>
-<p>If set, this will raise an error when crypt comes across a filename that can't be decrypted.</p>
-<p>(By default, rclone will just log a NOTICE and continue as normal.) This can happen if encrypted and unencrypted files are stored in the same directory (which is not recommended.) It may also indicate a more serious problem that should be investigated.</p>
+<p>If set, this will raise an error when crypt comes across a filename
+that can't be decrypted.</p>
+<p>(By default, rclone will just log a NOTICE and continue as normal.)
+This can happen if encrypted and unencrypted files are stored in the
+same directory (which is not recommended.) It may also indicate a more
+serious problem that should be investigated.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: strict_names</li>
@@ -20892,7 +31361,9 @@ $ rclone -q ls secret:
 </ul>
 <h4 id="crypt-filename-encoding">--crypt-filename-encoding</h4>
 <p>How to encode the encrypted filename to text string.</p>
-<p>This option could help with shortening the encrypted filename. The suitable option would depend on the way your remote count the filename length and if it's case sensitive.</p>
+<p>This option could help with shortening the encrypted filename. The
+suitable option would depend on the way your remote count the filename
+length and if it's case sensitive.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: filename_encoding</li>
@@ -20911,14 +31382,17 @@ $ rclone -q ls secret:
 </ul></li>
 <li>"base32768"
 <ul>
-<li>Encode using base32768. Suitable if your remote counts UTF-16 or</li>
-<li>Unicode codepoint instead of UTF-8 byte length. (Eg. Onedrive, Dropbox)</li>
+<li>Encode using base32768. Suitable if your remote counts UTF-16
+or</li>
+<li>Unicode codepoint instead of UTF-8 byte length. (Eg. Onedrive,
+Dropbox)</li>
 </ul></li>
 </ul></li>
 </ul>
 <h4 id="crypt-suffix">--crypt-suffix</h4>
 <p>If this is set it will override the default suffix of ".bin".</p>
-<p>Setting suffix to "none" will result in an empty suffix. This may be useful when the path length is critical.</p>
+<p>Setting suffix to "none" will result in an empty suffix. This may be
+useful when the path length is critical.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: suffix</li>
@@ -20936,60 +31410,90 @@ $ rclone -q ls secret:
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-5">Metadata</h3>
-<p>Any metadata supported by the underlying remote is read and written.</p>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>Any metadata supported by the underlying remote is read and
+written.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h2 id="backend-commands-3">Backend commands</h2>
 <p>Here are the commands specific to the crypt backend.</p>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="encode">encode</h3>
 <p>Encode the given filename(s)</p>
 <pre><code>rclone backend encode remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This encodes the filenames given as arguments returning a list of strings of the encoded results.</p>
+<p>This encodes the filenames given as arguments returning a list of
+strings of the encoded results.</p>
 <p>Usage Example:</p>
 <pre><code>rclone backend encode crypt: file1 [file2...]
 rclone rc backend/command command=encode fs=crypt: file1 [file2...]</code></pre>
 <h3 id="decode">decode</h3>
 <p>Decode the given filename(s)</p>
 <pre><code>rclone backend decode remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This decodes the filenames given as arguments returning a list of strings of the decoded results. It will return an error if any of the inputs are invalid.</p>
+<p>This decodes the filenames given as arguments returning a list of
+strings of the decoded results. It will return an error if any of the
+inputs are invalid.</p>
 <p>Usage Example:</p>
 <pre><code>rclone backend decode crypt: encryptedfile1 [encryptedfile2...]
 rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile2...]</code></pre>
-<h2 id="backing-up-an-encrypted-remote">Backing up an encrypted remote</h2>
-<p>If you wish to backup an encrypted remote, it is recommended that you use <code>rclone sync</code> on the encrypted files, and make sure the passwords are the same in the new encrypted remote.</p>
+<h2 id="backing-up-an-encrypted-remote">Backing up an encrypted
+remote</h2>
+<p>If you wish to backup an encrypted remote, it is recommended that you
+use <code>rclone sync</code> on the encrypted files, and make sure the
+passwords are the same in the new encrypted remote.</p>
 <p>This will have the following advantages</p>
 <ul>
 <li><code>rclone sync</code> will check the checksums while copying</li>
-<li>you can use <code>rclone check</code> between the encrypted remotes</li>
+<li>you can use <code>rclone check</code> between the encrypted
+remotes</li>
 <li>you don't decrypt and encrypt unnecessarily</li>
 </ul>
-<p>For example, let's say you have your original remote at <code>remote:</code> with the encrypted version at <code>eremote:</code> with path <code>remote:crypt</code>. You would then set up the new remote <code>remote2:</code> and then the encrypted version <code>eremote2:</code> with path <code>remote2:crypt</code> using the same passwords as <code>eremote:</code>.</p>
+<p>For example, let's say you have your original remote at
+<code>remote:</code> with the encrypted version at <code>eremote:</code>
+with path <code>remote:crypt</code>. You would then set up the new
+remote <code>remote2:</code> and then the encrypted version
+<code>eremote2:</code> with path <code>remote2:crypt</code> using the
+same passwords as <code>eremote:</code>.</p>
 <p>To sync the two remotes you would do</p>
 <pre><code>rclone sync --interactive remote:crypt remote2:crypt</code></pre>
 <p>And to check the integrity you would do</p>
 <pre><code>rclone check remote:crypt remote2:crypt</code></pre>
 <h2 id="file-formats">File formats</h2>
 <h3 id="file-encryption">File encryption</h3>
-<p>Files are encrypted 1:1 source file to destination object. The file has a header and is divided into chunks.</p>
+<p>Files are encrypted 1:1 source file to destination object. The file
+has a header and is divided into chunks.</p>
 <h4 id="header-1">Header</h4>
 <ul>
 <li>8 bytes magic string <code>RCLONE\x00\x00</code></li>
 <li>24 bytes Nonce (IV)</li>
 </ul>
-<p>The initial nonce is generated from the operating systems crypto strong random number generator. The nonce is incremented for each chunk read making sure each nonce is unique for each block written. The chance of a nonce being reused is minuscule. If you wrote an exabyte of data (10¹⁸ bytes) you would have a probability of approximately 2×10⁻³² of re-using a nonce.</p>
+<p>The initial nonce is generated from the operating systems crypto
+strong random number generator. The nonce is incremented for each chunk
+read making sure each nonce is unique for each block written. The chance
+of a nonce being reused is minuscule. If you wrote an exabyte of data
+(10¹⁸ bytes) you would have a probability of approximately 2×10⁻³² of
+re-using a nonce.</p>
 <h4 id="chunk">Chunk</h4>
-<p>Each chunk will contain 64 KiB of data, except for the last one which may have less data. The data chunk is in standard NaCl SecretBox format. SecretBox uses XSalsa20 and Poly1305 to encrypt and authenticate messages.</p>
+<p>Each chunk will contain 64 KiB of data, except for the last one which
+may have less data. The data chunk is in standard NaCl SecretBox format.
+SecretBox uses XSalsa20 and Poly1305 to encrypt and authenticate
+messages.</p>
 <p>Each chunk contains:</p>
 <ul>
 <li>16 Bytes of Poly1305 authenticator</li>
 <li>1 - 65536 bytes XSalsa20 encrypted data</li>
 </ul>
-<p>64k chunk size was chosen as the best performing chunk size (the authenticator takes too much time below this and the performance drops off due to cache effects above this). Note that these chunks are buffered in memory so they can't be too big.</p>
-<p>This uses a 32 byte (256 bit key) key derived from the user password.</p>
+<p>64k chunk size was chosen as the best performing chunk size (the
+authenticator takes too much time below this and the performance drops
+off due to cache effects above this). Note that these chunks are
+buffered in memory so they can't be too big.</p>
+<p>This uses a 32 byte (256 bit key) key derived from the user
+password.</p>
 <h4 id="examples-1">Examples</h4>
 <p>1 byte file will encrypt to</p>
 <ul>
@@ -21002,37 +31506,63 @@ rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile
 <li>32 bytes header</li>
 <li>16 chunks of 65568 bytes</li>
 </ul>
-<p>1049120 bytes total (a 0.05% overhead). This is the overhead for big files.</p>
+<p>1049120 bytes total (a 0.05% overhead). This is the overhead for big
+files.</p>
 <h3 id="name-encryption">Name encryption</h3>
-<p>File names are encrypted segment by segment - the path is broken up into <code>/</code> separated strings and these are encrypted individually.</p>
-<p>File segments are padded using PKCS#7 to a multiple of 16 bytes before encryption.</p>
-<p>They are then encrypted with EME using AES with 256 bit key. EME (ECB-Mix-ECB) is a wide-block encryption mode presented in the 2003 paper "A Parallelizable Enciphering Mode" by Halevi and Rogaway.</p>
-<p>This makes for deterministic encryption which is what we want - the same filename must encrypt to the same thing otherwise we can't find it on the cloud storage system.</p>
+<p>File names are encrypted segment by segment - the path is broken up
+into <code>/</code> separated strings and these are encrypted
+individually.</p>
+<p>File segments are padded using PKCS#7 to a multiple of 16 bytes
+before encryption.</p>
+<p>They are then encrypted with EME using AES with 256 bit key. EME
+(ECB-Mix-ECB) is a wide-block encryption mode presented in the 2003
+paper "A Parallelizable Enciphering Mode" by Halevi and Rogaway.</p>
+<p>This makes for deterministic encryption which is what we want - the
+same filename must encrypt to the same thing otherwise we can't find it
+on the cloud storage system.</p>
 <p>This means that</p>
 <ul>
 <li>filenames with the same name will encrypt the same</li>
 <li>filenames which start the same won't have a common prefix</li>
 </ul>
-<p>This uses a 32 byte key (256 bits) and a 16 byte (128 bits) IV both of which are derived from the user password.</p>
-<p>After encryption they are written out using a modified version of standard <code>base32</code> encoding as described in RFC4648. The standard encoding is modified in two ways:</p>
+<p>This uses a 32 byte key (256 bits) and a 16 byte (128 bits) IV both
+of which are derived from the user password.</p>
+<p>After encryption they are written out using a modified version of
+standard <code>base32</code> encoding as described in RFC4648. The
+standard encoding is modified in two ways:</p>
 <ul>
 <li>it becomes lower case (no-one likes upper case filenames!)</li>
 <li>we strip the padding character <code>=</code></li>
 </ul>
-<p><code>base32</code> is used rather than the more efficient <code>base64</code> so rclone can be used on case insensitive remotes (e.g. Windows, Box, Dropbox, Onedrive etc).</p>
+<p><code>base32</code> is used rather than the more efficient
+<code>base64</code> so rclone can be used on case insensitive remotes
+(e.g. Windows, Box, Dropbox, Onedrive etc).</p>
 <h3 id="key-derivation">Key derivation</h3>
-<p>Rclone uses <code>scrypt</code> with parameters <code>N=16384, r=8, p=1</code> with an optional user supplied salt (password2) to derive the 32+32+16 = 80 bytes of key material required. If the user doesn't supply a salt then rclone uses an internal one.</p>
-<p><code>scrypt</code> makes it impractical to mount a dictionary attack on rclone encrypted data. For full protection against this you should always use a salt.</p>
+<p>Rclone uses <code>scrypt</code> with parameters
+<code>N=16384, r=8, p=1</code> with an optional user supplied salt
+(password2) to derive the 32+32+16 = 80 bytes of key material required.
+If the user doesn't supply a salt then rclone uses an internal one.</p>
+<p><code>scrypt</code> makes it impractical to mount a dictionary attack
+on rclone encrypted data. For full protection against this you should
+always use a salt.</p>
 <h2 id="see-also-90">SEE ALSO</h2>
 <ul>
-<li><a href="https://rclone.org/commands/rclone_cryptdecode/">rclone cryptdecode</a> - Show forward/reverse mapping of encrypted filenames</li>
+<li><a href="https://rclone.org/commands/rclone_cryptdecode/">rclone
+cryptdecode</a> - Show forward/reverse mapping of encrypted
+filenames</li>
 </ul>
 <h1 id="compress">Compress</h1>
 <h2 id="warning">Warning</h2>
-<p>This remote is currently <strong>experimental</strong>. Things may break and data may be lost. Anything you do with this remote is at your own risk. Please understand the risks associated with using experimental code and don't use this remote in critical applications.</p>
-<p>The <code>Compress</code> remote adds compression to another remote. It is best used with remotes containing many large compressible files.</p>
+<p>This remote is currently <strong>experimental</strong>. Things may
+break and data may be lost. Anything you do with this remote is at your
+own risk. Please understand the risks associated with using experimental
+code and don't use this remote in critical applications.</p>
+<p>The <code>Compress</code> remote adds compression to another remote.
+It is best used with remotes containing many large compressible
+files.</p>
 <h2 id="configuration-9">Configuration</h2>
-<p>To use this remote, all you need to do is specify another remote and a compression mode to use:</p>
+<p>To use this remote, all you need to do is specify another remote and
+a compression mode to use:</p>
 <pre><code>Current remotes:
 
 Name                 Type
@@ -21081,13 +31611,27 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
 <h3 id="compression-modes">Compression Modes</h3>
-<p>Currently only gzip compression is supported. It provides a decent balance between speed and size and is well supported by other applications. Compression strength can further be configured via an advanced setting where 0 is no compression and 9 is strongest compression.</p>
+<p>Currently only gzip compression is supported. It provides a decent
+balance between speed and size and is well supported by other
+applications. Compression strength can further be configured via an
+advanced setting where 0 is no compression and 9 is strongest
+compression.</p>
 <h3 id="file-types">File types</h3>
-<p>If you open a remote wrapped by compress, you will see that there are many files with an extension corresponding to the compression algorithm you chose. These files are standard files that can be opened by various archive programs, but they have some hidden metadata that allows them to be used by rclone. While you may download and decompress these files at will, do <strong>not</strong> manually delete or rename files. Files without correct metadata files will not be recognized by rclone.</p>
+<p>If you open a remote wrapped by compress, you will see that there are
+many files with an extension corresponding to the compression algorithm
+you chose. These files are standard files that can be opened by various
+archive programs, but they have some hidden metadata that allows them to
+be used by rclone. While you may download and decompress these files at
+will, do <strong>not</strong> manually delete or rename files. Files
+without correct metadata files will not be recognized by rclone.</p>
 <h3 id="file-names">File names</h3>
-<p>The compressed files will be named <code>*.###########.gz</code> where <code>*</code> is the base file and the <code>#</code> part is base64 encoded size of the uncompressed file. The file names should not be changed by anything other than the rclone compression backend.</p>
+<p>The compressed files will be named <code>*.###########.gz</code>
+where <code>*</code> is the base file and the <code>#</code> part is
+base64 encoded size of the uncompressed file. The file names should not
+be changed by anything other than the rclone compression backend.</p>
 <h3 id="standard-options-9">Standard options</h3>
-<p>Here are the Standard options specific to compress (Compress a remote).</p>
+<p>Here are the Standard options specific to compress (Compress a
+remote).</p>
 <h4 id="compress-remote">--compress-remote</h4>
 <p>Remote to compress.</p>
 <p>Properties:</p>
@@ -21114,11 +31658,15 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul>
 <h3 id="advanced-options-9">Advanced options</h3>
-<p>Here are the Advanced options specific to compress (Compress a remote).</p>
+<p>Here are the Advanced options specific to compress (Compress a
+remote).</p>
 <h4 id="compress-level">--compress-level</h4>
 <p>GZIP compression level (-2 to 9).</p>
-<p>Generally -1 (default, equivalent to 5) is recommended. Levels 1 to 9 increase compression at the cost of speed. Going past 6 generally offers very little return.</p>
-<p>Level -2 uses Huffman encoding only. Only use if you know what you are doing. Level 0 turns off compression.</p>
+<p>Generally -1 (default, equivalent to 5) is recommended. Levels 1 to 9
+increase compression at the cost of speed. Going past 6 generally offers
+very little return.</p>
+<p>Level -2 uses Huffman encoding only. Only use if you know what you
+are doing. Level 0 turns off compression.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: level</li>
@@ -21127,8 +31675,11 @@ y/e/d&gt; y</code></pre>
 <li>Default: -1</li>
 </ul>
 <h4 id="compress-ram-cache-limit">--compress-ram-cache-limit</h4>
-<p>Some remotes don't allow the upload of files with unknown size. In this case the compressed file will need to be cached to determine it's size.</p>
-<p>Files smaller than this limit will be cached in RAM, files larger than this limit will be cached on disk.</p>
+<p>Some remotes don't allow the upload of files with unknown size. In
+this case the compressed file will need to be cached to determine it's
+size.</p>
+<p>Files smaller than this limit will be cached in RAM, files larger
+than this limit will be cached on disk.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: ram_cache_limit</li>
@@ -21146,10 +31697,13 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-6">Metadata</h3>
-<p>Any metadata supported by the underlying remote is read and written.</p>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>Any metadata supported by the underlying remote is read and
+written.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h1 id="combine">Combine</h1>
-<p>The <code>combine</code> backend joins remotes together into a single directory tree.</p>
+<p>The <code>combine</code> backend joins remotes together into a single
+directory tree.</p>
 <p>For example you might have a remote for images on one provider:</p>
 <pre><code>$ rclone tree s3:imagesbucket
 /
@@ -21160,7 +31714,8 @@ y/e/d&gt; y</code></pre>
 /
 ├── file1.txt
 └── file2.txt</code></pre>
-<p>The <code>combine</code> backend can join these together into a synthetic directory structure like this:</p>
+<p>The <code>combine</code> backend can join these together into a
+synthetic directory structure like this:</p>
 <pre><code>$ rclone tree combined:
 /
 ├── files
@@ -21169,11 +31724,15 @@ y/e/d&gt; y</code></pre>
 └── images
     ├── image1.jpg
     └── image2.jpg</code></pre>
-<p>You'd do this by specifying an <code>upstreams</code> parameter in the config like this</p>
+<p>You'd do this by specifying an <code>upstreams</code> parameter in
+the config like this</p>
 <pre><code>upstreams = images=s3:imagesbucket files=drive:important/files</code></pre>
-<p>During the initial setup with <code>rclone config</code> you will specify the upstreams remotes as a space separated list. The upstream remotes can either be a local paths or other remotes.</p>
+<p>During the initial setup with <code>rclone config</code> you will
+specify the upstreams remotes as a space separated list. The upstream
+remotes can either be a local paths or other remotes.</p>
 <h2 id="configuration-10">Configuration</h2>
-<p>Here is an example of how to make a combine called <code>remote</code> for the example above. First run:</p>
+<p>Here is an example of how to make a combine called
+<code>remote</code> for the example above. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -21209,9 +31768,12 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<h3 id="configuring-for-google-drive-shared-drives">Configuring for Google Drive Shared Drives</h3>
-<p>Rclone has a convenience feature for making a combine backend for all the shared drives you have access to.</p>
-<p>Assuming your main (non shared drive) Google drive remote is called <code>drive:</code> you would run</p>
+<h3 id="configuring-for-google-drive-shared-drives">Configuring for
+Google Drive Shared Drives</h3>
+<p>Rclone has a convenience feature for making a combine backend for all
+the shared drives you have access to.</p>
+<p>Assuming your main (non shared drive) Google drive remote is called
+<code>drive:</code> you would run</p>
 <pre><code>rclone backend -o config drives drive:</code></pre>
 <p>This would produce something like this:</p>
 <pre><code>[My Drive]
@@ -21225,15 +31787,20 @@ remote = drive,team_drive=0ABCDEFabcdefghijkl,root_folder_id=:
 [AllDrives]
 type = combine
 upstreams = &quot;My Drive=My Drive:&quot; &quot;Test Drive=Test Drive:&quot;</code></pre>
-<p>If you then add that config to your config file (find it with <code>rclone config file</code>) then you can access all the shared drives in one place with the <code>AllDrives:</code> remote.</p>
-<p>See <a href="https://rclone.org/drive/#drives">the Google Drive docs</a> for full info.</p>
+<p>If you then add that config to your config file (find it with
+<code>rclone config file</code>) then you can access all the shared
+drives in one place with the <code>AllDrives:</code> remote.</p>
+<p>See <a href="https://rclone.org/drive/#drives">the Google Drive
+docs</a> for full info.</p>
 <h3 id="standard-options-10">Standard options</h3>
-<p>Here are the Standard options specific to combine (Combine several remotes into one).</p>
+<p>Here are the Standard options specific to combine (Combine several
+remotes into one).</p>
 <h4 id="combine-upstreams">--combine-upstreams</h4>
 <p>Upstreams for combining</p>
 <p>These should be in the form</p>
 <pre><code>dir=remote:path dir2=remote2:path</code></pre>
-<p>Where before the = is specified the root directory and after is the remote to put there.</p>
+<p>Where before the = is specified the root directory and after is the
+remote to put there.</p>
 <p>Embedded spaces can be added using quotes</p>
 <pre><code>&quot;dir=remote:path with space&quot; &quot;dir2=remote2:path with space&quot;</code></pre>
 <p>Properties:</p>
@@ -21244,7 +31811,8 @@ upstreams = &quot;My Drive=My Drive:&quot; &quot;Test Drive=Test Drive:&quot;</c
 <li>Default:</li>
 </ul>
 <h3 id="advanced-options-10">Advanced options</h3>
-<p>Here are the Advanced options specific to combine (Combine several remotes into one).</p>
+<p>Here are the Advanced options specific to combine (Combine several
+remotes into one).</p>
 <h4 id="combine-description">--combine-description</h4>
 <p>Description of the remote.</p>
 <p>Properties:</p>
@@ -21255,14 +31823,20 @@ upstreams = &quot;My Drive=My Drive:&quot; &quot;Test Drive=Test Drive:&quot;</c
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-7">Metadata</h3>
-<p>Any metadata supported by the underlying remote is read and written.</p>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>Any metadata supported by the underlying remote is read and
+written.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h1 id="dropbox">Dropbox</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Dropbox paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
+<p>Dropbox paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
 <h2 id="configuration-11">Configuration</h2>
-<p>The initial setup for dropbox involves getting a token from Dropbox which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>The initial setup for dropbox involves getting a token from Dropbox
+which you need to do in your browser. <code>rclone config</code> walks
+you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>n) New remote
@@ -21296,8 +31870,15 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Dropbox. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and it may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from Dropbox. This only runs from the moment it
+opens your browser to the moment you get back the verification code.
+This is on <code>http://127.0.0.1:53682/</code> and it may require you
+to unblock it temporarily if you are running a host firewall, or use
+manual mode.</p>
 <p>You can then use it like this,</p>
 <p>List directories in top level of your dropbox</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -21307,15 +31888,31 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <h3 id="dropbox-for-business">Dropbox for business</h3>
 <p>Rclone supports Dropbox for business and Team Folders.</p>
-<p>When using Dropbox for business <code>remote:</code> and <code>remote:path/to/file</code> will refer to your personal folder.</p>
-<p>If you wish to see Team Folders you must use a leading <code>/</code> in the path, so <code>rclone lsd remote:/</code> will refer to the root and show you all Team Folders and your User Folder.</p>
-<p>You can then use team folders like this <code>remote:/TeamFolder</code> and <code>remote:/TeamFolder/path/to/file</code>.</p>
-<p>A leading <code>/</code> for a Dropbox personal account will do nothing, but it will take an extra HTTP transaction so it should be avoided.</p>
-<h3 id="modification-times-and-hashes-5">Modification times and hashes</h3>
-<p>Dropbox supports modified times, but the only way to set a modification time is to re-upload the file.</p>
-<p>This means that if you uploaded your data with an older version of rclone which didn't support the v2 API and modified times, rclone will decide to upload all your old data to fix the modification times. If you don't want this to happen use <code>--size-only</code> or <code>--checksum</code> flag to stop it.</p>
-<p>Dropbox supports <a href="https://www.dropbox.com/developers/reference/content-hash">its own hash type</a> which is checked for all transfers.</p>
-<h3 id="restricted-filename-characters-5">Restricted filename characters</h3>
+<p>When using Dropbox for business <code>remote:</code> and
+<code>remote:path/to/file</code> will refer to your personal folder.</p>
+<p>If you wish to see Team Folders you must use a leading <code>/</code>
+in the path, so <code>rclone lsd remote:/</code> will refer to the root
+and show you all Team Folders and your User Folder.</p>
+<p>You can then use team folders like this
+<code>remote:/TeamFolder</code> and
+<code>remote:/TeamFolder/path/to/file</code>.</p>
+<p>A leading <code>/</code> for a Dropbox personal account will do
+nothing, but it will take an extra HTTP transaction so it should be
+avoided.</p>
+<h3 id="modification-times-and-hashes-5">Modification times and
+hashes</h3>
+<p>Dropbox supports modified times, but the only way to set a
+modification time is to re-upload the file.</p>
+<p>This means that if you uploaded your data with an older version of
+rclone which didn't support the v2 API and modified times, rclone will
+decide to upload all your old data to fix the modification times. If you
+don't want this to happen use <code>--size-only</code> or
+<code>--checksum</code> flag to stop it.</p>
+<p>Dropbox supports <a
+href="https://www.dropbox.com/developers/reference/content-hash">its own
+hash type</a> which is checked for all transfers.</p>
+<h3 id="restricted-filename-characters-5">Restricted filename
+characters</h3>
 <table>
 <thead>
 <tr class="header">
@@ -21347,7 +31944,8 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
+<p>File names can also not end with the following characters. These only
+get replaced if they are the last character in the name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -21364,26 +31962,50 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="batch-mode">Batch mode uploads</h3>
-<p>Using batch mode uploads is very important for performance when using the Dropbox API. See <a href="https://developers.dropbox.com/dbx-performance-guide">the dropbox performance guide</a> for more info.</p>
+<p>Using batch mode uploads is very important for performance when using
+the Dropbox API. See <a
+href="https://developers.dropbox.com/dbx-performance-guide">the dropbox
+performance guide</a> for more info.</p>
 <p>There are 3 modes rclone can use for uploads.</p>
 <h4 id="dropbox-batch-mode-off">--dropbox-batch-mode off</h4>
-<p>In this mode rclone will not use upload batching. This was the default before rclone v1.55. It has the disadvantage that it is very likely to encounter <code>too_many_requests</code> errors like this</p>
+<p>In this mode rclone will not use upload batching. This was the
+default before rclone v1.55. It has the disadvantage that it is very
+likely to encounter <code>too_many_requests</code> errors like this</p>
 <pre><code>NOTICE: too_many_requests/.: Too many requests or write operations. Trying again in 15 seconds.</code></pre>
-<p>When rclone receives these it has to wait for 15s or sometimes 300s before continuing which really slows down transfers.</p>
-<p>This will happen especially if <code>--transfers</code> is large, so this mode isn't recommended except for compatibility or investigating problems.</p>
+<p>When rclone receives these it has to wait for 15s or sometimes 300s
+before continuing which really slows down transfers.</p>
+<p>This will happen especially if <code>--transfers</code> is large, so
+this mode isn't recommended except for compatibility or investigating
+problems.</p>
 <h4 id="dropbox-batch-mode-sync">--dropbox-batch-mode sync</h4>
-<p>In this mode rclone will batch up uploads to the size specified by <code>--dropbox-batch-size</code> and commit them together.</p>
-<p>Using this mode means you can use a much higher <code>--transfers</code> parameter (32 or 64 works fine) without receiving <code>too_many_requests</code> errors.</p>
+<p>In this mode rclone will batch up uploads to the size specified by
+<code>--dropbox-batch-size</code> and commit them together.</p>
+<p>Using this mode means you can use a much higher
+<code>--transfers</code> parameter (32 or 64 works fine) without
+receiving <code>too_many_requests</code> errors.</p>
 <p>This mode ensures full data integrity.</p>
-<p>Note that there may be a pause when quitting rclone while rclone finishes up the last batch using this mode.</p>
+<p>Note that there may be a pause when quitting rclone while rclone
+finishes up the last batch using this mode.</p>
 <h4 id="dropbox-batch-mode-async">--dropbox-batch-mode async</h4>
-<p>In this mode rclone will batch up uploads to the size specified by <code>--dropbox-batch-size</code> and commit them together.</p>
-<p>However it will not wait for the status of the batch to be returned to the caller. This means rclone can use a much bigger batch size (much bigger than <code>--transfers</code>), at the cost of not being able to check the status of the upload.</p>
-<p>This provides the maximum possible upload speed especially with lots of small files, however rclone can't check the file got uploaded properly using this mode.</p>
-<p>If you are using this mode then using "rclone check" after the transfer completes is recommended. Or you could do an initial transfer with <code>--dropbox-batch-mode async</code> then do a final transfer with <code>--dropbox-batch-mode sync</code> (the default).</p>
-<p>Note that there may be a pause when quitting rclone while rclone finishes up the last batch using this mode.</p>
+<p>In this mode rclone will batch up uploads to the size specified by
+<code>--dropbox-batch-size</code> and commit them together.</p>
+<p>However it will not wait for the status of the batch to be returned
+to the caller. This means rclone can use a much bigger batch size (much
+bigger than <code>--transfers</code>), at the cost of not being able to
+check the status of the upload.</p>
+<p>This provides the maximum possible upload speed especially with lots
+of small files, however rclone can't check the file got uploaded
+properly using this mode.</p>
+<p>If you are using this mode then using "rclone check" after the
+transfer completes is recommended. Or you could do an initial transfer
+with <code>--dropbox-batch-mode async</code> then do a final transfer
+with <code>--dropbox-batch-mode sync</code> (the default).</p>
+<p>Note that there may be a pause when quitting rclone while rclone
+finishes up the last batch using this mode.</p>
 <h3 id="standard-options-11">Standard options</h3>
 <p>Here are the Standard options specific to dropbox (Dropbox).</p>
 <h4 id="dropbox-client-id">--dropbox-client-id</h4>
@@ -21439,8 +32061,12 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="dropbox-chunk-size">--dropbox-chunk-size</h4>
 <p>Upload chunk size (&lt; 150Mi).</p>
-<p>Any files larger than this will be uploaded in chunks of this size.</p>
-<p>Note that chunks are buffered in memory (one at a time) so rclone can deal with retries. Setting this larger will increase the speed slightly (at most 10% for 128 MiB in tests) at the cost of using more memory. It can be set smaller if you are tight on memory.</p>
+<p>Any files larger than this will be uploaded in chunks of this
+size.</p>
+<p>Note that chunks are buffered in memory (one at a time) so rclone can
+deal with retries. Setting this larger will increase the speed slightly
+(at most 10% for 128 MiB in tests) at the cost of using more memory. It
+can be set smaller if you are tight on memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -21450,9 +32076,17 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="dropbox-impersonate">--dropbox-impersonate</h4>
 <p>Impersonate this user when using a business account.</p>
-<p>Note that if you want to use impersonate, you should make sure this flag is set when running "rclone config" as this will cause rclone to request the "members.read" scope which it won't normally. This is needed to lookup a members email address into the internal ID that dropbox uses in the API.</p>
-<p>Using the "members.read" scope will require a Dropbox Team Admin to approve during the OAuth flow.</p>
-<p>You will have to use your own App (setting your own client_id and client_secret) to use this option as currently rclone's default set of permissions doesn't include "members.read". This can be added once v1.55 or later is in use everywhere.</p>
+<p>Note that if you want to use impersonate, you should make sure this
+flag is set when running "rclone config" as this will cause rclone to
+request the "members.read" scope which it won't normally. This is needed
+to lookup a members email address into the internal ID that dropbox uses
+in the API.</p>
+<p>Using the "members.read" scope will require a Dropbox Team Admin to
+approve during the OAuth flow.</p>
+<p>You will have to use your own App (setting your own client_id and
+client_secret) to use this option as currently rclone's default set of
+permissions doesn't include "members.read". This can be added once v1.55
+or later is in use everywhere.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: impersonate</li>
@@ -21462,7 +32096,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="dropbox-shared-files">--dropbox-shared-files</h4>
 <p>Instructs rclone to work on individual shared files.</p>
-<p>In this mode rclone's features are extremely limited - only list (ls, lsl, etc.) operations and read operations (e.g. downloading) are supported in this mode. All other operations will be disabled.</p>
+<p>In this mode rclone's features are extremely limited - only list (ls,
+lsl, etc.) operations and read operations (e.g. downloading) are
+supported in this mode. All other operations will be disabled.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: shared_files</li>
@@ -21472,9 +32108,18 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="dropbox-shared-folders">--dropbox-shared-folders</h4>
 <p>Instructs rclone to work on shared folders.</p>
-<p>When this flag is used with no path only the List operation is supported and all available shared folders will be listed. If you specify a path the first part will be interpreted as the name of shared folder. Rclone will then try to mount this shared to the root namespace. On success shared folder rclone proceeds normally. The shared folder is now pretty much a normal folder and all normal operations are supported.</p>
-<p>Note that we don't unmount the shared folder afterwards so the --dropbox-shared-folders can be omitted after the first use of a particular shared folder.</p>
-<p>See also --dropbox-root-namespace for an alternative way to work with shared folders.</p>
+<p>When this flag is used with no path only the List operation is
+supported and all available shared folders will be listed. If you
+specify a path the first part will be interpreted as the name of shared
+folder. Rclone will then try to mount this shared to the root namespace.
+On success shared folder rclone proceeds normally. The shared folder is
+now pretty much a normal folder and all normal operations are
+supported.</p>
+<p>Note that we don't unmount the shared folder afterwards so the
+--dropbox-shared-folders can be omitted after the first use of a
+particular shared folder.</p>
+<p>See also --dropbox-root-namespace for an alternative way to work with
+shared folders.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: shared_folders</li>
@@ -21493,7 +32138,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="dropbox-encoding">--dropbox-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -21502,7 +32148,8 @@ y/e/d&gt; y</code></pre>
 <li>Default: Slash,BackSlash,Del,RightSpace,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="dropbox-root-namespace">--dropbox-root-namespace</h4>
-<p>Specify a different Dropbox namespace ID to use as the root for all paths.</p>
+<p>Specify a different Dropbox namespace ID to use as the root for all
+paths.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_namespace</li>
@@ -21513,14 +32160,16 @@ y/e/d&gt; y</code></pre>
 <h4 id="dropbox-batch-mode">--dropbox-batch-mode</h4>
 <p>Upload file batching sync|async|off.</p>
 <p>This sets the batch mode used by rclone.</p>
-<p>For full info see <a href="https://rclone.org/dropbox/#batch-mode">the main docs</a></p>
+<p>For full info see <a
+href="https://rclone.org/dropbox/#batch-mode">the main docs</a></p>
 <p>This has 3 possible values</p>
 <ul>
 <li>off - no batching</li>
 <li>sync - batch uploads and check completion (default)</li>
 <li>async - batch upload and don't check completion</li>
 </ul>
-<p>Rclone will close any outstanding batches when it exits which may make a delay on quit.</p>
+<p>Rclone will close any outstanding batches when it exits which may
+make a delay on quit.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: batch_mode</li>
@@ -21530,15 +32179,21 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="dropbox-batch-size">--dropbox-batch-size</h4>
 <p>Max number of files in upload batch.</p>
-<p>This sets the batch size of files to upload. It has to be less than 1000.</p>
-<p>By default this is 0 which means rclone will calculate the batch size depending on the setting of batch_mode.</p>
+<p>This sets the batch size of files to upload. It has to be less than
+1000.</p>
+<p>By default this is 0 which means rclone will calculate the batch size
+depending on the setting of batch_mode.</p>
 <ul>
 <li>batch_mode: async - default batch_size is 100</li>
-<li>batch_mode: sync - default batch_size is the same as --transfers</li>
+<li>batch_mode: sync - default batch_size is the same as
+--transfers</li>
 <li>batch_mode: off - not in use</li>
 </ul>
-<p>Rclone will close any outstanding batches when it exits which may make a delay on quit.</p>
-<p>Setting this is a great idea if you are uploading lots of small files as it will make them a lot quicker. You can use --transfers 32 to maximise throughput.</p>
+<p>Rclone will close any outstanding batches when it exits which may
+make a delay on quit.</p>
+<p>Setting this is a great idea if you are uploading lots of small files
+as it will make them a lot quicker. You can use --transfers 32 to
+maximise throughput.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: batch_size</li>
@@ -21548,8 +32203,10 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="dropbox-batch-timeout">--dropbox-batch-timeout</h4>
 <p>Max time to allow an idle upload batch before uploading.</p>
-<p>If an upload batch is idle for more than this long then it will be uploaded.</p>
-<p>The default for this is 0 which means rclone will choose a sensible default based on the batch_mode in use.</p>
+<p>If an upload batch is idle for more than this long then it will be
+uploaded.</p>
+<p>The default for this is 0 which means rclone will choose a sensible
+default based on the batch_mode in use.</p>
 <ul>
 <li>batch_mode: async - default batch_timeout is 10s</li>
 <li>batch_mode: sync - default batch_timeout is 500ms</li>
@@ -21562,7 +32219,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: Duration</li>
 <li>Default: 0s</li>
 </ul>
-<h4 id="dropbox-batch-commit-timeout">--dropbox-batch-commit-timeout</h4>
+<h4
+id="dropbox-batch-commit-timeout">--dropbox-batch-commit-timeout</h4>
 <p>Max time to wait for a batch to finish committing</p>
 <p>Properties:</p>
 <ul>
@@ -21581,29 +32239,81 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-10">Limitations</h2>
-<p>Note that Dropbox is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
-<p>There are some file names such as <code>thumbs.db</code> which Dropbox can't store. There is a full list of them in the <a href="https://www.dropbox.com/en/help/145">"Ignored Files" section of this document</a>. Rclone will issue an error message <code>File name disallowed - not uploading</code> if it attempts to upload one of those file names, but the sync won't fail.</p>
-<p>Some errors may occur if you try to sync copyright-protected files because Dropbox has its own <a href="https://techcrunch.com/2014/03/30/how-dropbox-knows-when-youre-sharing-copyrighted-stuff-without-actually-looking-at-your-stuff/">copyright detector</a> that prevents this sort of file being downloaded. This will return the error <code>ERROR : /path/to/your/file: Failed to copy: failed to open source object: path/restricted_content/.</code></p>
-<p>If you have more than 10,000 files in a directory then <code>rclone purge dropbox:dir</code> will return the error <code>Failed to purge: There are too many files involved in this operation</code>. As a work-around do an <code>rclone delete dropbox:dir</code> followed by an <code>rclone rmdir dropbox:dir</code>.</p>
-<p>When using <code>rclone link</code> you'll need to set <code>--expire</code> if using a non-personal account otherwise the visibility may not be correct. (Note that <code>--expire</code> isn't supported on personal accounts). See the <a href="https://forum.rclone.org/t/rclone-link-dropbox-permissions/23211">forum discussion</a> and the <a href="https://github.com/dropbox/dropbox-sdk-go-unofficial/issues/75">dropbox SDK issue</a>.</p>
+<p>Note that Dropbox is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".</p>
+<p>There are some file names such as <code>thumbs.db</code> which
+Dropbox can't store. There is a full list of them in the <a
+href="https://www.dropbox.com/en/help/145">"Ignored Files" section of
+this document</a>. Rclone will issue an error message
+<code>File name disallowed - not uploading</code> if it attempts to
+upload one of those file names, but the sync won't fail.</p>
+<p>Some errors may occur if you try to sync copyright-protected files
+because Dropbox has its own <a
+href="https://techcrunch.com/2014/03/30/how-dropbox-knows-when-youre-sharing-copyrighted-stuff-without-actually-looking-at-your-stuff/">copyright
+detector</a> that prevents this sort of file being downloaded. This will
+return the error
+<code>ERROR : /path/to/your/file: Failed to copy: failed to open source object: path/restricted_content/.</code></p>
+<p>If you have more than 10,000 files in a directory then
+<code>rclone purge dropbox:dir</code> will return the error
+<code>Failed to purge: There are too many files involved in this operation</code>.
+As a work-around do an <code>rclone delete dropbox:dir</code> followed
+by an <code>rclone rmdir dropbox:dir</code>.</p>
+<p>When using <code>rclone link</code> you'll need to set
+<code>--expire</code> if using a non-personal account otherwise the
+visibility may not be correct. (Note that <code>--expire</code> isn't
+supported on personal accounts). See the <a
+href="https://forum.rclone.org/t/rclone-link-dropbox-permissions/23211">forum
+discussion</a> and the <a
+href="https://github.com/dropbox/dropbox-sdk-go-unofficial/issues/75">dropbox
+SDK issue</a>.</p>
 <h2 id="get-your-own-dropbox-app-id">Get your own Dropbox App ID</h2>
-<p>When you use rclone with Dropbox in its default configuration you are using rclone's App ID. This is shared between all the rclone users.</p>
+<p>When you use rclone with Dropbox in its default configuration you are
+using rclone's App ID. This is shared between all the rclone users.</p>
 <p>Here is how to create your own Dropbox App ID for rclone:</p>
 <ol type="1">
-<li><p>Log into the <a href="https://www.dropbox.com/developers/apps/create">Dropbox App console</a> with your Dropbox Account (It need not to be the same account as the Dropbox you want to access)</p></li>
-<li><p>Choose an API =&gt; Usually this should be <code>Dropbox API</code></p></li>
-<li><p>Choose the type of access you want to use =&gt; <code>Full Dropbox</code> or <code>App Folder</code>. If you want to use Team Folders, <code>Full Dropbox</code> is required (<a href="https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-create-team-folder-inside-my-app-s-folder/m-p/601005/highlight/true#M27911">see here</a>).</p></li>
-<li><p>Name your App. The app name is global, so you can't use <code>rclone</code> for example</p></li>
+<li><p>Log into the <a
+href="https://www.dropbox.com/developers/apps/create">Dropbox App
+console</a> with your Dropbox Account (It need not to be the same
+account as the Dropbox you want to access)</p></li>
+<li><p>Choose an API =&gt; Usually this should be
+<code>Dropbox API</code></p></li>
+<li><p>Choose the type of access you want to use =&gt;
+<code>Full Dropbox</code> or <code>App Folder</code>. If you want to use
+Team Folders, <code>Full Dropbox</code> is required (<a
+href="https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-create-team-folder-inside-my-app-s-folder/m-p/601005/highlight/true#M27911">see
+here</a>).</p></li>
+<li><p>Name your App. The app name is global, so you can't use
+<code>rclone</code> for example</p></li>
 <li><p>Click the button <code>Create App</code></p></li>
-<li><p>Switch to the <code>Permissions</code> tab. Enable at least the following permissions: <code>account_info.read</code>, <code>files.metadata.write</code>, <code>files.content.write</code>, <code>files.content.read</code>, <code>sharing.write</code>. The <code>files.metadata.read</code> and <code>sharing.read</code> checkboxes will be marked too. Click <code>Submit</code></p></li>
-<li><p>Switch to the <code>Settings</code> tab. Fill <code>OAuth2 - Redirect URIs</code> as <code>http://localhost:53682/</code> and click on <code>Add</code></p></li>
-<li><p>Find the <code>App key</code> and <code>App secret</code> values on the <code>Settings</code> tab. Use these values in rclone config to add a new remote or edit an existing remote. The <code>App key</code> setting corresponds to <code>client_id</code> in rclone config, the <code>App secret</code> corresponds to <code>client_secret</code></p></li>
+<li><p>Switch to the <code>Permissions</code> tab. Enable at least the
+following permissions: <code>account_info.read</code>,
+<code>files.metadata.write</code>, <code>files.content.write</code>,
+<code>files.content.read</code>, <code>sharing.write</code>. The
+<code>files.metadata.read</code> and <code>sharing.read</code>
+checkboxes will be marked too. Click <code>Submit</code></p></li>
+<li><p>Switch to the <code>Settings</code> tab. Fill
+<code>OAuth2 - Redirect URIs</code> as
+<code>http://localhost:53682/</code> and click on
+<code>Add</code></p></li>
+<li><p>Find the <code>App key</code> and <code>App secret</code> values
+on the <code>Settings</code> tab. Use these values in rclone config to
+add a new remote or edit an existing remote. The <code>App key</code>
+setting corresponds to <code>client_id</code> in rclone config, the
+<code>App secret</code> corresponds to
+<code>client_secret</code></p></li>
 </ol>
 <h1 id="enterprise-file-fabric">Enterprise File Fabric</h1>
-<p>This backend supports <a href="https://storagemadeeasy.com/about/">Storage Made Easy's Enterprise File Fabric™</a> which provides a software solution to integrate and unify File and Object Storage accessible through a global file system.</p>
+<p>This backend supports <a
+href="https://storagemadeeasy.com/about/">Storage Made Easy's Enterprise
+File Fabric™</a> which provides a software solution to integrate and
+unify File and Object Storage accessible through a global file
+system.</p>
 <h2 id="configuration-12">Configuration</h2>
-<p>The initial setup for the Enterprise File Fabric backend involves getting a token from the Enterprise File Fabric which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>The initial setup for the Enterprise File Fabric backend involves
+getting a token from the Enterprise File Fabric which you need to do in
+your browser. <code>rclone config</code> walks you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -21672,21 +32382,41 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone lsd remote:</code></pre>
 <p>List all the files in your Enterprise File Fabric</p>
 <pre><code>rclone ls remote:</code></pre>
-<p>To copy a local directory to an Enterprise File Fabric directory called backup</p>
+<p>To copy a local directory to an Enterprise File Fabric directory
+called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-6">Modification times and hashes</h3>
-<p>The Enterprise File Fabric allows modification times to be set on files accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
-<p>The Enterprise File Fabric does not support any data hashes at this time.</p>
-<h3 id="restricted-filename-characters-6">Restricted filename characters</h3>
-<p>The <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> will be replaced.</p>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<h3 id="modification-times-and-hashes-6">Modification times and
+hashes</h3>
+<p>The Enterprise File Fabric allows modification times to be set on
+files accurate to 1 second. These will be used to detect whether objects
+need syncing or not.</p>
+<p>The Enterprise File Fabric does not support any data hashes at this
+time.</p>
+<h3 id="restricted-filename-characters-6">Restricted filename
+characters</h3>
+<p>The <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> will be replaced.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="empty-files">Empty files</h3>
-<p>Empty files aren't supported by the Enterprise File Fabric. Rclone will therefore upload an empty file as a single space with a mime type of <code>application/vnd.rclone.empty.file</code> and files with that mime type are treated as empty.</p>
+<p>Empty files aren't supported by the Enterprise File Fabric. Rclone
+will therefore upload an empty file as a single space with a mime type
+of <code>application/vnd.rclone.empty.file</code> and files with that
+mime type are treated as empty.</p>
 <h3 id="root-folder-id-1">Root folder ID</h3>
-<p>You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your Enterprise File Fabric.</p>
-<p>Normally you will leave this blank and rclone will determine the correct root to use itself.</p>
-<p>However you can set this to restrict rclone to a specific folder hierarchy.</p>
-<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display. These aren't displayed in the web interface, but you can use <code>rclone lsf</code> to find them, for example</p>
+<p>You can set the <code>root_folder_id</code> for rclone. This is the
+directory (identified by its <code>Folder ID</code>) that rclone
+considers to be the root of your Enterprise File Fabric.</p>
+<p>Normally you will leave this blank and rclone will determine the
+correct root to use itself.</p>
+<p>However you can set this to restrict rclone to a specific folder
+hierarchy.</p>
+<p>In order to do this you will have to find the <code>Folder ID</code>
+of the directory you wish rclone to display. These aren't displayed in
+the web interface, but you can use <code>rclone lsf</code> to find them,
+for example</p>
 <pre><code>$ rclone lsf --dirs-only -Fip --csv filefabric:
 120673758,Burnt PDFs/
 120673759,My Quick Uploads/
@@ -21696,7 +32426,8 @@ y/e/d&gt; y</code></pre>
 120673761,S3 Storage/</code></pre>
 <p>The ID for "S3 Storage" would be <code>120673761</code>.</p>
 <h3 id="standard-options-12">Standard options</h3>
-<p>Here are the Standard options specific to filefabric (Enterprise File Fabric).</p>
+<p>Here are the Standard options specific to filefabric (Enterprise File
+Fabric).</p>
 <h4 id="filefabric-url">--filefabric-url</h4>
 <p>URL of the Enterprise File Fabric to connect to.</p>
 <p>Properties:</p>
@@ -21734,9 +32465,13 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="filefabric-permanent-token">--filefabric-permanent-token</h4>
 <p>Permanent Authentication Token.</p>
-<p>A Permanent Authentication Token can be created in the Enterprise File Fabric, on the users Dashboard under Security, there is an entry you'll see called "My Authentication Tokens". Click the Manage button to create one.</p>
+<p>A Permanent Authentication Token can be created in the Enterprise
+File Fabric, on the users Dashboard under Security, there is an entry
+you'll see called "My Authentication Tokens". Click the Manage button to
+create one.</p>
 <p>These tokens are normally valid for several years.</p>
-<p>For more info see: https://docs.storagemadeeasy.com/organisationcloud/api-tokens</p>
+<p>For more info see:
+https://docs.storagemadeeasy.com/organisationcloud/api-tokens</p>
 <p>Properties:</p>
 <ul>
 <li>Config: permanent_token</li>
@@ -21745,10 +32480,12 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="advanced-options-12">Advanced options</h3>
-<p>Here are the Advanced options specific to filefabric (Enterprise File Fabric).</p>
+<p>Here are the Advanced options specific to filefabric (Enterprise File
+Fabric).</p>
 <h4 id="filefabric-token">--filefabric-token</h4>
 <p>Session Token.</p>
-<p>This is a session token which rclone caches in the config file. It is usually valid for 1 hour.</p>
+<p>This is a session token which rclone caches in the config file. It is
+usually valid for 1 hour.</p>
 <p>Don't set this value - rclone will set it automatically.</p>
 <p>Properties:</p>
 <ul>
@@ -21779,7 +32516,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="filefabric-encoding">--filefabric-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -21797,10 +32535,18 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h1 id="files.com">Files.com</h1>
-<p><a href="https://www.files.com/">Files.com</a> is a cloud storage service that provides a secure and easy way to store and share files.</p>
-<p>The initial setup for filescom involves authenticating with your Files.com account. You can do this by providing your site subdomain, username, and password. Alternatively, you can authenticate using an API Key from <a href="https://www.files.com/docs/sdk-and-apis/api-keys/">Files.com</a>. <code>rclone config</code> walks you through it.</p>
+<p><a href="https://www.files.com/">Files.com</a> is a cloud storage
+service that provides a secure and easy way to store and share
+files.</p>
+<p>The initial setup for filescom involves authenticating with your
+Files.com account. You can do this by providing your site subdomain,
+username, and password. Alternatively, you can authenticate using an API
+Key from <a
+href="https://www.files.com/docs/sdk-and-apis/api-keys/">Files.com</a>.
+<code>rclone config</code> walks you through it.</p>
 <h2 id="configuration-13">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -21866,12 +32612,14 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone mkdir remote:dir</code></pre>
 <p>Recursively List the contents:</p>
 <pre><code>rclone ls remote:</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote directory, deleting any excess files in the directory.</p>
+<p>Sync <code>/home/local/directory</code> to the remote directory,
+deleting any excess files in the directory.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:dir</code></pre>
 <h3 id="standard-options-13">Standard options</h3>
 <p>Here are the Standard options specific to filescom (Files.com).</p>
 <h4 id="filescom-site">--filescom-site</h4>
-<p>Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com).</p>
+<p>Your site subdomain (e.g. mysite) or custom domain (e.g.
+myfiles.customdomain.com).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: site</li>
@@ -21890,7 +32638,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="filescom-password">--filescom-password</h4>
 <p>The password used to authenticate with Files.com.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -21911,13 +32661,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="filescom-encoding">--filescom-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_FILESCOM_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,BackSlash,Del,Ctl,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,BackSlash,Del,Ctl,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="filescom-description">--filescom-description</h4>
 <p>Description of the remote.</p>
@@ -21928,14 +32680,473 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h1 id="ftp">FTP</h1>
-<p>FTP is the File Transfer Protocol. Rclone FTP support is provided using the <a href="https://godoc.org/github.com/jlaffaye/ftp">github.com/jlaffaye/ftp</a> package.</p>
-<p><a href="#limitations">Limitations of Rclone's FTP backend</a></p>
-<p>Paths are specified as <code>remote:path</code>. If the path does not begin with a <code>/</code> it is relative to the home directory of the user. An empty path <code>remote:</code> refers to the user's home directory.</p>
+<h1 id="frostfs">FrostFS</h1>
+<p>Rclone FrostFS support is provided using the <a
+href="https://git.frostfs.info/TrueCloudLab/frostfs-sdk-go">git.frostfs.info/TrueCloudLab/frostfs-sdk-go</a>
+package</p>
 <h2 id="configuration-14">Configuration</h2>
+<p>To create an FrostFS configuration named <code>remote</code>, run</p>
+<pre><code>rclone config</code></pre>
+<p>Rclone config guides you through an interactive setup process. A
+minimal rclone FrostFS remote definition only requires endpoint and path
+to FrostFS user wallet.</p>
+<pre><code>No remotes found, make a new one?
+n) New remote
+s) Set configuration password
+q) Quit config
+n/s/q&gt; n
+
+Enter name for new remote.
+name&gt; remote
+
+Option Storage.
+Type of storage to configure.
+Choose a number from below, or type in your own value.
+ 1 / 1Fichier
+   \ (fichier)
+ 2 / Akamai NetStorage
+   \ (netstorage)
+ 3 / Alias for an existing remote
+   \ (alias)
+ 4 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others
+   \ (s3)
+ 5 / Backblaze B2
+   \ (b2)
+ 6 / Better checksums for other remotes
+   \ (hasher)
+ 7 / Box
+   \ (box)
+ 8 / Cache a remote
+   \ (cache)
+ 9 / Citrix Sharefile
+   \ (sharefile)
+10 / Combine several remotes into one
+   \ (combine)
+11 / Compress a remote
+   \ (compress)
+12 / Distributed, decentralized object storage FrostFS
+   \ (frostfs)
+13 / Dropbox
+   \ (dropbox)
+14 / Encrypt/Decrypt a remote
+   \ (crypt)
+15 / Enterprise File Fabric
+   \ (filefabric)
+16 / FTP
+   \ (ftp)
+17 / Files.com
+   \ (filescom)
+18 / Gofile
+   \ (gofile)
+19 / Google Cloud Storage (this is not Google Drive)
+   \ (google cloud storage)
+20 / Google Drive
+   \ (drive)
+21 / Google Photos
+   \ (google photos)
+22 / HTTP
+   \ (http)
+23 / Hadoop distributed file system
+   \ (hdfs)
+24 / HiDrive
+   \ (hidrive)
+25 / ImageKit.io
+   \ (imagekit)
+26 / In memory object storage system.
+   \ (memory)
+27 / Internet Archive
+   \ (internetarchive)
+28 / Jottacloud
+   \ (jottacloud)
+29 / Koofr, Digi Storage and other Koofr-compatible storage providers
+   \ (koofr)
+30 / Linkbox
+   \ (linkbox)
+31 / Local Disk
+   \ (local)
+32 / Mail.ru Cloud
+   \ (mailru)
+33 / Mega
+   \ (mega)
+34 / Microsoft Azure Blob Storage
+   \ (azureblob)
+35 / Microsoft Azure Files
+   \ (azurefiles)
+36 / Microsoft OneDrive
+   \ (onedrive)
+37 / OpenDrive
+   \ (opendrive)
+38 / OpenStack Swift (Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)
+   \ (swift)
+39 / Oracle Cloud Infrastructure Object Storage
+   \ (oracleobjectstorage)
+40 / Pcloud
+   \ (pcloud)
+41 / PikPak
+   \ (pikpak)
+42 / Pixeldrain Filesystem
+   \ (pixeldrain)
+43 / Proton Drive
+   \ (protondrive)
+44 / Put.io
+   \ (putio)
+45 / QingCloud Object Storage
+   \ (qingstor)
+46 / Quatrix by Maytech
+   \ (quatrix)
+47 / SMB / CIFS
+   \ (smb)
+48 / SSH/SFTP
+   \ (sftp)
+49 / Sia Decentralized Cloud
+   \ (sia)
+50 / Storj Decentralized Cloud Storage
+   \ (storj)
+51 / Sugarsync
+   \ (sugarsync)
+52 / Transparently chunk/split large files
+   \ (chunker)
+53 / Uloz.to
+   \ (ulozto)
+54 / Union merges the contents of several upstream fs
+   \ (union)
+55 / Uptobox
+   \ (uptobox)
+56 / WebDAV
+   \ (webdav)
+57 / Yandex Disk
+   \ (yandex)
+58 / Zoho
+   \ (zoho)
+59 / premiumize.me
+   \ (premiumizeme)
+60 / seafile
+   \ (seafile)
+Storage&gt; frostfs
+
+Option endpoint.
+Endpoints to connect to FrostFS node
+Choose a number from below, or type in your own value.
+ 1 / One endpoint.
+   \ (s01.frostfs.devenv:8080)
+ 2 / Multiple endpoints to form pool.
+   \ (s01.frostfs.devenv:8080 s02.frostfs.devenv:8080)
+ 3 / Multiple endpoints with priority (less value is higher priority). Until s01 is healthy all request will be send to it.
+   \ (s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2)
+ 4 / Multiple endpoints with priority and weights. After s01 is unhealthy requests will be send to s02 and s03 in proportions 10% and 90% respectively.
+   \ (s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1 s03.frostfs.devenv:8080,2,9)
+endpoint&gt; s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+
+Option connection_timeout.
+FrostFS connection timeout
+Enter a value of type Duration. Press Enter for the default (4s).
+connection_timeout&gt; 
+
+Option request_timeout.
+FrostFS request timeout
+Enter a value of type Duration. Press Enter for the default (4s).
+request_timeout&gt; 
+
+Option rebalance_interval.
+FrostFS rebalance connections interval
+Enter a value of type Duration. Press Enter for the default (15s).
+rebalance_interval&gt; 
+
+Option session_expiration.
+FrostFS session expiration epoch
+Enter a signed integer. Press Enter for the default (4294967295).
+session_expiration&gt; 
+
+Option ape_cache_invalidation_duration.
+APE cache invalidation duration
+Enter a value of type Duration. Press Enter for the default (8s).
+ape_cache_invalidation_duration&gt; 
+
+Option ape_cache_invalidation_timeout.
+APE cache invalidation timeout
+Enter a value of type Duration. Press Enter for the default (16s).
+ape_cache_invalidation_timeout&gt; 
+
+Option ape_chain_check_interval.
+The interval for verifying that the APE chain is saved in FrostFS.
+Enter a value of type Duration. Press Enter for the default (500ms).
+ape_chain_check_interval&gt; 
+
+Option rpc_endpoint.
+Endpoint to connect to Neo rpc node
+Enter a value. Press Enter to leave empty.
+rpc_endpoint&gt; 
+
+Option wallet.
+Path to wallet
+Enter a value.
+wallet&gt; /wallets/wallet.conf
+
+Option address.
+Address of account
+Enter a value. Press Enter to leave empty.
+address&gt; 
+
+Option password.
+Password to decrypt wallet
+Enter a value. Press Enter to leave empty.
+password&gt; 
+
+Option placement_policy.
+Placement policy for new containers
+Choose a number from below, or type in your own value of type string.
+Press Enter for the default (REP 3).
+ 1 / Container will have 3 replicas
+   \ (REP 3)
+placement_policy&gt; REP 1
+
+Option container_creation_policy.
+Container creation policy for new containers
+Choose a number from below, or type in your own value of type string.
+Press Enter for the default (private).
+ 1 / Public container, anyone can read and write
+   \ (public-read-write)
+ 2 / Public container, owner can read and write, others can only read
+   \ (public-read)
+ 3 / Private container, only owner has access to it
+   \ (private)
+container_creation_policy&gt; 
+
+Edit advanced config?
+y) Yes
+n) No (default)
+y/n&gt; n
+
+Configuration complete.
+Options:
+- type: frostfs
+- endpoint: s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+- password: M@zPGpWDravchenko/develop/go/playground/play_with_ape/cfg/wallet_akrav.js
+- placement_policy: REP 1
+Keep this &quot;remote&quot; remote?
+y) Yes this is OK (default)
+e) Edit this remote
+d) Delete this remote
+y/e/d&gt; y</code></pre>
+<p>As a remote root directory, you can use either the container
+identifier or its user-friendly name. If you choose to use a container
+name, rclone will create a new container with that name when it's used
+for the first time.</p>
+<p>For example, both of the following commands would be valid if there
+was a <code>~/test-copy</code> directory and a container with the
+identifier
+<code>23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf</code>:</p>
+<pre><code>rclone copy ~/test-copy remote:23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf/test-copy
+rclone copy ~/test-copy remote:container-name/test-copy</code></pre>
+<h3 id="standard-options-14">Standard options</h3>
+<p>Here are the Standard options specific to frostfs (Distributed,
+decentralized object storage FrostFS).</p>
+<h4 id="frostfs-endpoint">--frostfs-endpoint</h4>
+<p>Endpoints to connect to FrostFS node</p>
+<p>Properties:</p>
+<ul>
+<li>Config: endpoint</li>
+<li>Env Var: RCLONE_FROSTFS_ENDPOINT</li>
+<li>Type: string</li>
+<li>Required: true</li>
+<li>Examples:
+<ul>
+<li>"s01.frostfs.devenv:8080"
+<ul>
+<li>One endpoint.</li>
+</ul></li>
+<li>"s01.frostfs.devenv:8080 s02.frostfs.devenv:8080"
+<ul>
+<li>Multiple endpoints to form pool.</li>
+</ul></li>
+<li>"s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2"
+<ul>
+<li>Multiple endpoints with priority (lower value has higher priority).
+Until s01 is healthy, all requests will be sent to it.</li>
+</ul></li>
+<li>"s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1
+s03.frostfs.devenv:8080,2,9"
+<ul>
+<li>Multiple endpoints with priority and weights. After the s01 endpoint
+is unhealthy, requests will be sent to the s02 and s03 endpoints in
+proportions of 10% and 90%, respectively.</li>
+</ul></li>
+</ul></li>
+</ul>
+<h4 id="frostfs-connection-timeout">--frostfs-connection-timeout</h4>
+<p>FrostFS connection timeout</p>
+<p>Properties:</p>
+<ul>
+<li>Config: connection_timeout</li>
+<li>Env Var: RCLONE_FROSTFS_CONNECTION_TIMEOUT</li>
+<li>Type: Duration</li>
+<li>Default: 4s</li>
+</ul>
+<h4 id="frostfs-request-timeout">--frostfs-request-timeout</h4>
+<p>FrostFS request timeout</p>
+<p>Properties:</p>
+<ul>
+<li>Config: request_timeout</li>
+<li>Env Var: RCLONE_FROSTFS_REQUEST_TIMEOUT</li>
+<li>Type: Duration</li>
+<li>Default: 12s</li>
+</ul>
+<h4 id="frostfs-rebalance-interval">--frostfs-rebalance-interval</h4>
+<p>FrostFS rebalance connections interval</p>
+<p>Properties:</p>
+<ul>
+<li>Config: rebalance_interval</li>
+<li>Env Var: RCLONE_FROSTFS_REBALANCE_INTERVAL</li>
+<li>Type: Duration</li>
+<li>Default: 15s</li>
+</ul>
+<h4 id="frostfs-session-expiration">--frostfs-session-expiration</h4>
+<p>FrostFS session expiration epoch</p>
+<p>Properties:</p>
+<ul>
+<li>Config: session_expiration</li>
+<li>Env Var: RCLONE_FROSTFS_SESSION_EXPIRATION</li>
+<li>Type: int</li>
+<li>Default: 4294967295</li>
+</ul>
+<h4
+id="frostfs-ape-cache-invalidation-duration">--frostfs-ape-cache-invalidation-duration</h4>
+<p>APE cache invalidation duration</p>
+<p>Properties:</p>
+<ul>
+<li>Config: ape_cache_invalidation_duration</li>
+<li>Env Var: RCLONE_FROSTFS_APE_CACHE_INVALIDATION_DURATION</li>
+<li>Type: Duration</li>
+<li>Default: 8s</li>
+</ul>
+<h4
+id="frostfs-ape-cache-invalidation-timeout">--frostfs-ape-cache-invalidation-timeout</h4>
+<p>APE cache invalidation timeout</p>
+<p>Properties:</p>
+<ul>
+<li>Config: ape_cache_invalidation_timeout</li>
+<li>Env Var: RCLONE_FROSTFS_APE_CACHE_INVALIDATION_TIMEOUT</li>
+<li>Type: Duration</li>
+<li>Default: 24s</li>
+</ul>
+<h4
+id="frostfs-ape-chain-check-interval">--frostfs-ape-chain-check-interval</h4>
+<p>The interval for verifying that the APE chain is saved in
+FrostFS.</p>
+<p>Properties:</p>
+<ul>
+<li>Config: ape_chain_check_interval</li>
+<li>Env Var: RCLONE_FROSTFS_APE_CHAIN_CHECK_INTERVAL</li>
+<li>Type: Duration</li>
+<li>Default: 500ms</li>
+</ul>
+<h4 id="frostfs-rpc-endpoint">--frostfs-rpc-endpoint</h4>
+<p>Endpoint to connect to Neo rpc node</p>
+<p>Properties:</p>
+<ul>
+<li>Config: rpc_endpoint</li>
+<li>Env Var: RCLONE_FROSTFS_RPC_ENDPOINT</li>
+<li>Type: string</li>
+<li>Required: false</li>
+</ul>
+<h4 id="frostfs-wallet">--frostfs-wallet</h4>
+<p>Path to wallet</p>
+<p>Properties:</p>
+<ul>
+<li>Config: wallet</li>
+<li>Env Var: RCLONE_FROSTFS_WALLET</li>
+<li>Type: string</li>
+<li>Required: true</li>
+</ul>
+<h4 id="frostfs-address">--frostfs-address</h4>
+<p>Address of account</p>
+<p>Properties:</p>
+<ul>
+<li>Config: address</li>
+<li>Env Var: RCLONE_FROSTFS_ADDRESS</li>
+<li>Type: string</li>
+<li>Required: false</li>
+</ul>
+<h4 id="frostfs-password">--frostfs-password</h4>
+<p>Password to decrypt wallet</p>
+<p>Properties:</p>
+<ul>
+<li>Config: password</li>
+<li>Env Var: RCLONE_FROSTFS_PASSWORD</li>
+<li>Type: string</li>
+<li>Required: false</li>
+</ul>
+<h4 id="frostfs-placement-policy">--frostfs-placement-policy</h4>
+<p>Placement policy for new containers</p>
+<p>Properties:</p>
+<ul>
+<li>Config: placement_policy</li>
+<li>Env Var: RCLONE_FROSTFS_PLACEMENT_POLICY</li>
+<li>Type: string</li>
+<li>Default: "REP 3"</li>
+<li>Examples:
+<ul>
+<li>"REP 3"
+<ul>
+<li>Container will have 3 replicas</li>
+</ul></li>
+</ul></li>
+</ul>
+<h4
+id="frostfs-container-creation-policy">--frostfs-container-creation-policy</h4>
+<p>Container creation policy for new containers</p>
+<p>Properties:</p>
+<ul>
+<li>Config: container_creation_policy</li>
+<li>Env Var: RCLONE_FROSTFS_CONTAINER_CREATION_POLICY</li>
+<li>Type: string</li>
+<li>Default: "private"</li>
+<li>Examples:
+<ul>
+<li>"public-read-write"
+<ul>
+<li>Public container, anyone can read and write</li>
+</ul></li>
+<li>"public-read"
+<ul>
+<li>Public container, owner can read and write, others can only
+read</li>
+</ul></li>
+<li>"private"
+<ul>
+<li>Private container, only owner has access to it</li>
+</ul></li>
+</ul></li>
+</ul>
+<h3 id="advanced-options-14">Advanced options</h3>
+<p>Here are the Advanced options specific to frostfs (Distributed,
+decentralized object storage FrostFS).</p>
+<h4 id="frostfs-description">--frostfs-description</h4>
+<p>Description of the remote.</p>
+<p>Properties:</p>
+<ul>
+<li>Config: description</li>
+<li>Env Var: RCLONE_FROSTFS_DESCRIPTION</li>
+<li>Type: string</li>
+<li>Required: false</li>
+</ul>
+<h1 id="ftp">FTP</h1>
+<p>FTP is the File Transfer Protocol. Rclone FTP support is provided
+using the <a
+href="https://godoc.org/github.com/jlaffaye/ftp">github.com/jlaffaye/ftp</a>
+package.</p>
+<p><a href="#limitations">Limitations of Rclone's FTP backend</a></p>
+<p>Paths are specified as <code>remote:path</code>. If the path does not
+begin with a <code>/</code> it is relative to the home directory of the
+user. An empty path <code>remote:</code> refers to the user's home
+directory.</p>
+<h2 id="configuration-15">Configuration</h2>
 <p>To create an FTP configuration named <code>remote</code>, run</p>
 <pre><code>rclone config</code></pre>
-<p>Rclone config guides you through an interactive setup process. A minimal rclone FTP remote definition only requires host, username and password. For an anonymous FTP server, see <a href="#anonymous-ftp">below</a>.</p>
+<p>Rclone config guides you through an interactive setup process. A
+minimal rclone FTP remote definition only requires host, username and
+password. For an anonymous FTP server, see <a
+href="#anonymous-ftp">below</a>.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 r) Rename remote
@@ -21991,27 +33202,53 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>To see all directories in the home directory of <code>remote</code></p>
+<p>To see all directories in the home directory of
+<code>remote</code></p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>Make a new directory</p>
 <pre><code>rclone mkdir remote:path/to/directory</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls remote:path/to/directory</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote directory, deleting any excess files in the directory.</p>
+<p>Sync <code>/home/local/directory</code> to the remote directory,
+deleting any excess files in the directory.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:directory</code></pre>
 <h3 id="anonymous-ftp">Anonymous FTP</h3>
-<p>When connecting to a FTP server that allows anonymous login, you can use the special "anonymous" username. Traditionally, this user account accepts any string as a password, although it is common to use either the password "anonymous" or "guest". Some servers require the use of a valid e-mail address as password.</p>
-<p>Using <a href="#backend-path-to-dir">on-the-fly</a> or <a href="https://rclone.org/docs/#connection-strings">connection string</a> remotes makes it easy to access such servers, without requiring any configuration in advance. The following are examples of that:</p>
+<p>When connecting to a FTP server that allows anonymous login, you can
+use the special "anonymous" username. Traditionally, this user account
+accepts any string as a password, although it is common to use either
+the password "anonymous" or "guest". Some servers require the use of a
+valid e-mail address as password.</p>
+<p>Using <a href="#backend-path-to-dir">on-the-fly</a> or <a
+href="https://rclone.org/docs/#connection-strings">connection string</a>
+remotes makes it easy to access such servers, without requiring any
+configuration in advance. The following are examples of that:</p>
 <pre><code>rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=$(rclone obscure dummy)
 rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=$(rclone obscure dummy):</code></pre>
-<p>The above examples work in Linux shells and in PowerShell, but not Windows Command Prompt. They execute the <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a> command to create a password string in the format required by the <a href="#ftp-pass">pass</a> option. The following examples are exactly the same, except use an already obscured string representation of the same password "dummy", and therefore works even in Windows Command Prompt:</p>
+<p>The above examples work in Linux shells and in PowerShell, but not
+Windows Command Prompt. They execute the <a
+href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>
+command to create a password string in the format required by the <a
+href="#ftp-pass">pass</a> option. The following examples are exactly the
+same, except use an already obscured string representation of the same
+password "dummy", and therefore works even in Windows Command
+Prompt:</p>
 <pre><code>rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM
 rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM:</code></pre>
-<h3 id="implicit-tls">Implicit TLS</h3>
-<p>Rlone FTP supports implicit FTP over TLS servers (FTPS). This has to be enabled in the FTP backend config for the remote, or with <a href="#ftp-tls"><code>--ftp-tls</code></a>. The default FTPS port is <code>990</code>, not <code>21</code> and can be set with <a href="#ftp-port"><code>--ftp-port</code></a>.</p>
-<h3 id="restricted-filename-characters-7">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
-<p>File names cannot end with the following characters. Replacement is limited to the last character in a file name:</p>
+<h3 id="implicit-tlsutil.go">Implicit TLS<a
+href="../../backend/frostfs/util.go">util.go</a></h3>
+<p>Rlone FTP supports implicit FTP over TLS servers (FTPS). This has to
+be enabled in the FTP backend config for the remote, or with <a
+href="#ftp-tls"><code>--ftp-tls</code></a>. The default FTPS port is
+<code>990</code>, not <code>21</code> and can be set with <a
+href="#ftp-port"><code>--ftp-port</code></a>. <a
+href="../../backend/frostfs/util.go">util.go</a> ### Restricted filename
+characters</p>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
+<p>File names cannot end with the following characters. Replacement is
+limited to the last character in a file name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -22028,7 +33265,8 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </tr>
 </tbody>
 </table>
-<p>Not all FTP servers can have all characters in file names, for example:</p>
+<p>Not all FTP servers can have all characters in file names, for
+example:</p>
 <table>
 <thead>
 <tr class="header">
@@ -22047,8 +33285,10 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </tr>
 </tbody>
 </table>
-<p>This backend's interactive configuration wizard provides a selection of sensible encoding settings for major FTP servers: ProFTPd, PureFTPd, VsFTPd. Just hit a selection number when prompted.</p>
-<h3 id="standard-options-14">Standard options</h3>
+<p>This backend's interactive configuration wizard provides a selection
+of sensible encoding settings for major FTP servers: ProFTPd, PureFTPd,
+VsFTPd. Just hit a selection number when prompted.</p>
+<h3 id="standard-options-15">Standard options</h3>
 <p>Here are the Standard options specific to ftp (FTP).</p>
 <h4 id="ftp-host">--ftp-host</h4>
 <p>FTP host to connect to.</p>
@@ -22080,7 +33320,9 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </ul>
 <h4 id="ftp-pass">--ftp-pass</h4>
 <p>FTP password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass</li>
@@ -22090,7 +33332,10 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </ul>
 <h4 id="ftp-tls">--ftp-tls</h4>
 <p>Use Implicit FTPS (FTP over TLS).</p>
-<p>When using implicit FTP over TLS the client connects using TLS right from the start which breaks compatibility with non-TLS-aware servers. This is usually served over port 990 rather than port 21. Cannot be used in combination with explicit FTPS.</p>
+<p>When using implicit FTP over TLS the client connects using TLS right
+from the start which breaks compatibility with non-TLS-aware servers.
+This is usually served over port 990 rather than port 21. Cannot be used
+in combination with explicit FTPS.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: tls</li>
@@ -22100,7 +33345,9 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </ul>
 <h4 id="ftp-explicit-tls">--ftp-explicit-tls</h4>
 <p>Use Explicit FTPS (FTP over TLS).</p>
-<p>When using explicit FTP over TLS the client explicitly requests security from the server in order to upgrade a plain text connection to an encrypted one. Cannot be used in combination with implicit FTPS.</p>
+<p>When using explicit FTP over TLS the client explicitly requests
+security from the server in order to upgrade a plain text connection to
+an encrypted one. Cannot be used in combination with implicit FTPS.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: explicit_tls</li>
@@ -22108,14 +33355,21 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="advanced-options-14">Advanced options</h3>
+<h3 id="advanced-options-15">Advanced options</h3>
 <p>Here are the Advanced options specific to ftp (FTP).</p>
 <h4 id="ftp-concurrency">--ftp-concurrency</h4>
 <p>Maximum number of FTP simultaneous connections, 0 for unlimited.</p>
-<p>Note that setting this is very likely to cause deadlocks so it should be used with care.</p>
-<p>If you are doing a sync or copy then make sure concurrency is one more than the sum of <code>--transfers</code> and <code>--checkers</code>.</p>
-<p>If you use <code>--check-first</code> then it just needs to be one more than the maximum of <code>--checkers</code> and <code>--transfers</code>.</p>
-<p>So for <code>concurrency 3</code> you'd use <code>--checkers 2 --transfers 2 --check-first</code> or <code>--checkers 1 --transfers 1</code>.</p>
+<p>Note that setting this is very likely to cause deadlocks so it should
+be used with care.</p>
+<p>If you are doing a sync or copy then make sure concurrency is one
+more than the sum of <code>--transfers</code> and
+<code>--checkers</code>.</p>
+<p>If you use <code>--check-first</code> then it just needs to be one
+more than the maximum of <code>--checkers</code> and
+<code>--transfers</code>.</p>
+<p>So for <code>concurrency 3</code> you'd use
+<code>--checkers 2 --transfers 2 --check-first</code> or
+<code>--checkers 1 --transfers 1</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: concurrency</li>
@@ -22169,7 +33423,8 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 <li>Default: false</li>
 </ul>
 <h4 id="ftp-force-list-hidden">--ftp-force-list-hidden</h4>
-<p>Use LIST -a to force listing of hidden files and folders. This will disable the use of MLSD.</p>
+<p>Use LIST -a to force listing of hidden files and folders. This will
+disable the use of MLSD.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: force_list_hidden</li>
@@ -22179,7 +33434,8 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </ul>
 <h4 id="ftp-idle-timeout">--ftp-idle-timeout</h4>
 <p>Max time before closing idle connections.</p>
-<p>If no connections have been returned to the connection pool in the time given, rclone will empty the connection pool.</p>
+<p>If no connections have been returned to the connection pool in the
+time given, rclone will empty the connection pool.</p>
 <p>Set to 0 to keep connections indefinitely.</p>
 <p>Properties:</p>
 <ul>
@@ -22199,7 +33455,9 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </ul>
 <h4 id="ftp-tls-cache-size">--ftp-tls-cache-size</h4>
 <p>Size of TLS session cache for all control and data connections.</p>
-<p>TLS cache allows to resume TLS sessions and reuse PSK between connections. Increase if default size is not enough resulting in TLS resumption errors. Enabled by default. Use 0 to disable.</p>
+<p>TLS cache allows to resume TLS sessions and reuse PSK between
+connections. Increase if default size is not enough resulting in TLS
+resumption errors. Enabled by default. Use 0 to disable.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: tls_cache_size</li>
@@ -22227,7 +33485,8 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </ul>
 <h4 id="ftp-ask-password">--ftp-ask-password</h4>
 <p>Allow asking for FTP password when needed.</p>
-<p>If this is set and no password is supplied then rclone will ask for a password</p>
+<p>If this is set and no password is supplied then rclone will ask for a
+password</p>
 <p>Properties:</p>
 <ul>
 <li>Config: ask_password</li>
@@ -22252,7 +33511,8 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 </ul>
 <h4 id="ftp-encoding">--ftp-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -22285,25 +33545,66 @@ rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-11">Limitations</h2>
-<p>FTP servers acting as rclone remotes must support <code>passive</code> mode. The mode cannot be configured as <code>passive</code> is the only supported one. Rclone's FTP implementation is not compatible with <code>active</code> mode as <a href="https://github.com/jlaffaye/ftp/issues/29">the library it uses doesn't support it</a>. This will likely never be supported due to security concerns.</p>
-<p>Rclone's FTP backend does not support any checksums but can compare file sizes.</p>
-<p><code>rclone about</code> is not supported by the FTP backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
-<p>The implementation of : <code>--dump headers</code>, <code>--dump bodies</code>, <code>--dump auth</code> for debugging isn't the same as for rclone HTTP based backends - it has less fine grained control.</p>
-<p><code>--timeout</code> isn't supported (but <code>--contimeout</code> is).</p>
+<p>FTP servers acting as rclone remotes must support
+<code>passive</code> mode. The mode cannot be configured as
+<code>passive</code> is the only supported one. Rclone's FTP
+implementation is not compatible with <code>active</code> mode as <a
+href="https://github.com/jlaffaye/ftp/issues/29">the library it uses
+doesn't support it</a>. This will likely never be supported due to
+security concerns.</p>
+<p>Rclone's FTP backend does not support any checksums but can compare
+file sizes.</p>
+<p><code>rclone about</code> is not supported by the FTP backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p>The implementation of : <code>--dump headers</code>,
+<code>--dump bodies</code>, <code>--dump auth</code> for debugging isn't
+the same as for rclone HTTP based backends - it has less fine grained
+control.</p>
+<p><code>--timeout</code> isn't supported (but <code>--contimeout</code>
+is).</p>
 <p><code>--bind</code> isn't supported.</p>
-<p>Rclone's FTP backend could support server-side move but does not at present.</p>
-<p>The <code>ftp_proxy</code> environment variable is not currently supported.</p>
+<p>Rclone's FTP backend could support server-side move but does not at
+present.</p>
+<p>The <code>ftp_proxy</code> environment variable is not currently
+supported.</p>
 <h3 id="modification-times-4">Modification times</h3>
-<p>File modification time (timestamps) is supported to 1 second resolution for major FTP servers: ProFTPd, PureFTPd, VsFTPd, and FileZilla FTP server. The <code>VsFTPd</code> server has non-standard implementation of time related protocol commands and needs a special configuration setting: <code>writing_mdtm = true</code>.</p>
-<p>Support for precise file time with other FTP servers varies depending on what protocol extensions they advertise. If all the <code>MLSD</code>, <code>MDTM</code> and <code>MFTM</code> extensions are present, rclone will use them together to provide precise time. Otherwise the times you see on the FTP server through rclone are those of the last file upload.</p>
-<p>You can use the following command to check whether rclone can use precise time with your FTP server: <code>rclone backend features your_ftp_remote:</code> (the trailing colon is important). Look for the number in the line tagged by <code>Precision</code> designating the remote time precision expressed as nanoseconds. A value of <code>1000000000</code> means that file time precision of 1 second is available. A value of <code>3153600000000000000</code> (or another large number) means "unsupported".</p>
+<p>File modification time (timestamps) is supported to 1 second
+resolution for major FTP servers: ProFTPd, PureFTPd, VsFTPd, and
+FileZilla FTP server. The <code>VsFTPd</code> server has non-standard
+implementation of time related protocol commands and needs a special
+configuration setting: <code>writing_mdtm = true</code>.</p>
+<p>Support for precise file time with other FTP servers varies depending
+on what protocol extensions they advertise. If all the
+<code>MLSD</code>, <code>MDTM</code> and <code>MFTM</code> extensions
+are present, rclone will use them together to provide precise time.
+Otherwise the times you see on the FTP server through rclone are those
+of the last file upload.</p>
+<p>You can use the following command to check whether rclone can use
+precise time with your FTP server:
+<code>rclone backend features your_ftp_remote:</code> (the trailing
+colon is important). Look for the number in the line tagged by
+<code>Precision</code> designating the remote time precision expressed
+as nanoseconds. A value of <code>1000000000</code> means that file time
+precision of 1 second is available. A value of
+<code>3153600000000000000</code> (or another large number) means
+"unsupported".</p>
 <h1 id="gofile">Gofile</h1>
-<p><a href="https://gofile.io">Gofile</a> is a content storage and distribution platform. Its aim is to provide as much service as possible for free or at a very low price.</p>
-<p>The initial setup for Gofile involves logging in to the web interface and going to the "My Profile" section. Copy the "Account API token" for use in the config file.</p>
-<p>Note that if you wish to connect rclone to Gofile you will need a premium account.</p>
-<h2 id="configuration-15">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p><a href="https://gofile.io">Gofile</a> is a content storage and
+distribution platform. Its aim is to provide as much service as possible
+for free or at a very low price.</p>
+<p>The initial setup for Gofile involves logging in to the web interface
+and going to the "My Profile" section. Copy the "Account API token" for
+use in the config file.</p>
+<p>Note that if you wish to connect rclone to Gofile you will need a
+premium account.</p>
+<h2 id="configuration-16">Configuration</h2>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -22347,11 +33648,17 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone lsf remote:</code></pre>
 <p>To copy a local directory to an Gofile directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-7">Modification times and hashes</h3>
+<h3 id="modification-times-and-hashes-7">Modification times and
+hashes</h3>
 <p>Gofile supports modification times with a resolution of 1 second.</p>
-<p>Gofile supports MD5 hashes, so you can use the <code>--checksum</code> flag.</p>
-<h3 id="restricted-filename-characters-8">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>Gofile supports MD5 hashes, so you can use the
+<code>--checksum</code> flag.</p>
+<h3 id="restricted-filename-characters-7">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -22408,7 +33715,9 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not start or end with the following characters. These only get replaced if they are the first or last character in the name:</p>
+<p>File names can also not start or end with the following characters.
+These only get replaced if they are the first or last character in the
+name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -22425,23 +33734,36 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="public-links">Public Links</h3>
-<p>Gofile supports <code>rclone link</code> to make public links to files or directories. If you specify a directory it will download as a <code>zip</code> file. You can use the <code>--expire</code> flag to specify the time the link should be valid. Note that <code>rclone link --unlink</code> removes all the public links for a file.</p>
+<p>Gofile supports <code>rclone link</code> to make public links to
+files or directories. If you specify a directory it will download as a
+<code>zip</code> file. You can use the <code>--expire</code> flag to
+specify the time the link should be valid. Note that
+<code>rclone link --unlink</code> removes all the public links for a
+file.</p>
 <h3 id="root-folder-id-2">Root folder ID</h3>
-<p>You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your Gofile drive.</p>
-<p>Normally you will leave this blank and rclone will determine the correct root to use itself and fill in the value in the config file.</p>
-<p>However you can set this to restrict rclone to a specific folder hierarchy.</p>
-<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display.</p>
+<p>You can set the <code>root_folder_id</code> for rclone. This is the
+directory (identified by its <code>Folder ID</code>) that rclone
+considers to be the root of your Gofile drive.</p>
+<p>Normally you will leave this blank and rclone will determine the
+correct root to use itself and fill in the value in the config file.</p>
+<p>However you can set this to restrict rclone to a specific folder
+hierarchy.</p>
+<p>In order to do this you will have to find the <code>Folder ID</code>
+of the directory you wish rclone to display.</p>
 <p>You can do this with rclone</p>
 <pre><code>$ rclone lsf -Fip --dirs-only remote:
 d6341f53-ee65-4f29-9f59-d11e8070b2a0;Files/
 f4f5c9b8-6ece-478b-b03e-4538edfe5a1c;Photos/
 d50e356c-29ca-4b27-a3a7-494d91026e04;Videos/</code></pre>
-<p>The ID to use is the part before the <code>;</code> so you could set</p>
+<p>The ID to use is the part before the <code>;</code> so you could
+set</p>
 <pre><code>root_folder_id = d6341f53-ee65-4f29-9f59-d11e8070b2a0</code></pre>
 <p>To restrict rclone to the <code>Files</code> directory.</p>
-<h3 id="standard-options-15">Standard options</h3>
+<h3 id="standard-options-16">Standard options</h3>
 <p>Here are the Standard options specific to gofile (Gofile).</p>
 <h4 id="gofile-access-token">--gofile-access-token</h4>
 <p>API Access token</p>
@@ -22453,12 +33775,13 @@ d50e356c-29ca-4b27-a3a7-494d91026e04;Videos/</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-15">Advanced options</h3>
+<h3 id="advanced-options-16">Advanced options</h3>
 <p>Here are the Advanced options specific to gofile (Gofile).</p>
 <h4 id="gofile-root-folder-id">--gofile-root-folder-id</h4>
 <p>ID of the root folder</p>
 <p>Leave this blank normally, rclone will fill it in automatically.</p>
-<p>If you want rclone to be restricted to a particular folder you can fill it in - see the docs for more info.</p>
+<p>If you want rclone to be restricted to a particular folder you can
+fill it in - see the docs for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_id</li>
@@ -22487,13 +33810,15 @@ d50e356c-29ca-4b27-a3a7-494d91026e04;Videos/</code></pre>
 </ul>
 <h4 id="gofile-encoding">--gofile-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_GOFILE_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,LeftPeriod,RightPeriod,InvalidUtf8,Dot,Exclamation</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,LeftPeriod,RightPeriod,InvalidUtf8,Dot,Exclamation</li>
 </ul>
 <h4 id="gofile-description">--gofile-description</h4>
 <p>Description of the remote.</p>
@@ -22505,19 +33830,36 @@ d50e356c-29ca-4b27-a3a7-494d91026e04;Videos/</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-12">Limitations</h2>
-<p>Gofile only supports filenames up to 255 characters in length, where a character is a unicode character.</p>
-<p>Directories should not be cached for more than 24h otherwise files in the directory may not be downloadable. In practice this means when using a VFS based rclone command such as <code>rclone mount</code> you should make sure <code>--dir-cache-time</code> is less than <code>24h</code>.</p>
-<p>Note that Gofile is currently limited to a total of 100,000 items. If you attempt to upload more than that you will get <code>error-limit-100000</code>. This limit may be lifted in the future.</p>
+<p>Gofile only supports filenames up to 255 characters in length, where
+a character is a unicode character.</p>
+<p>Directories should not be cached for more than 24h otherwise files in
+the directory may not be downloadable. In practice this means when using
+a VFS based rclone command such as <code>rclone mount</code> you should
+make sure <code>--dir-cache-time</code> is less than
+<code>24h</code>.</p>
+<p>Note that Gofile is currently limited to a total of 100,000 items. If
+you attempt to upload more than that you will get
+<code>error-limit-100000</code>. This limit may be lifted in the
+future.</p>
 <h3 id="duplicated-files-1">Duplicated files</h3>
-<p>Gofile is capable of having files with duplicated file names. For instance two files called <code>hello.txt</code> in the same directory.</p>
-<p>Rclone cannot sync that to a normal file system but it can be fixed with the <code>rclone dedupe</code> command.</p>
-<p>Duplicated files cause problems with the syncing and you will see messages in the log about duplicates.</p>
+<p>Gofile is capable of having files with duplicated file names. For
+instance two files called <code>hello.txt</code> in the same
+directory.</p>
+<p>Rclone cannot sync that to a normal file system but it can be fixed
+with the <code>rclone dedupe</code> command.</p>
+<p>Duplicated files cause problems with the syncing and you will see
+messages in the log about duplicates.</p>
 <p>Use <code>rclone dedupe</code> to fix duplicated files.</p>
 <h1 id="google-cloud-storage-1">Google Cloud Storage</h1>
-<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
-<h2 id="configuration-16">Configuration</h2>
-<p>The initial setup for google cloud storage involves getting a token from Google Cloud Storage which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths are specified as <code>remote:bucket</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
+<h2 id="configuration-17">Configuration</h2>
+<p>The initial setup for google cloud storage involves getting a token
+from Google Cloud Storage which you need to do in your browser.
+<code>rclone config</code> walks you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>n) New remote
@@ -22640,30 +33982,81 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if using web browser to automatically authenticate. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
-<p>This remote is called <code>remote</code> and can now be used like this</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from Google if using web browser to automatically
+authenticate. This only runs from the moment it opens your browser to
+the moment you get back the verification code. This is on
+<code>http://127.0.0.1:53682/</code> and this it may require you to
+unblock it temporarily if you are running a host firewall, or use manual
+mode.</p>
+<p>This remote is called <code>remote</code> and can now be used like
+this</p>
 <p>See all the buckets in your project</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>Make a new bucket</p>
 <pre><code>rclone mkdir remote:bucket</code></pre>
 <p>List the contents of a bucket</p>
 <pre><code>rclone ls remote:bucket</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote bucket, deleting any excess files in the bucket.</p>
+<p>Sync <code>/home/local/directory</code> to the remote bucket,
+deleting any excess files in the bucket.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:bucket</code></pre>
 <h3 id="service-account-support">Service Account support</h3>
-<p>You can set up rclone with Google Cloud Storage in an unattended mode, i.e. not tied to a specific end-user Google account. This is useful when you want to synchronise files onto machines that don't have actively logged-in users, for example build machines.</p>
-<p>To get credentials for Google Cloud Platform <a href="https://cloud.google.com/iam/docs/service-accounts">IAM Service Accounts</a>, please head to the <a href="https://console.cloud.google.com/permissions/serviceaccounts">Service Account</a> section of the Google Developer Console. Service Accounts behave just like normal <code>User</code> permissions in <a href="https://cloud.google.com/storage/docs/access-control">Google Cloud Storage ACLs</a>, so you can limit their access (e.g. make them read only). After creating an account, a JSON file containing the Service Account's credentials will be downloaded onto your machines. These credentials are what rclone will use for authentication.</p>
-<p>To use a Service Account instead of OAuth2 token flow, enter the path to your Service Account credentials at the <code>service_account_file</code> prompt and rclone won't use the browser based authentication flow. If you'd rather stuff the contents of the credentials file into the rclone config file, you can set <code>service_account_credentials</code> with the actual contents of the file instead, or set the equivalent environment variable.</p>
+<p>You can set up rclone with Google Cloud Storage in an unattended
+mode, i.e. not tied to a specific end-user Google account. This is
+useful when you want to synchronise files onto machines that don't have
+actively logged-in users, for example build machines.</p>
+<p>To get credentials for Google Cloud Platform <a
+href="https://cloud.google.com/iam/docs/service-accounts">IAM Service
+Accounts</a>, please head to the <a
+href="https://console.cloud.google.com/permissions/serviceaccounts">Service
+Account</a> section of the Google Developer Console. Service Accounts
+behave just like normal <code>User</code> permissions in <a
+href="https://cloud.google.com/storage/docs/access-control">Google Cloud
+Storage ACLs</a>, so you can limit their access (e.g. make them read
+only). After creating an account, a JSON file containing the Service
+Account's credentials will be downloaded onto your machines. These
+credentials are what rclone will use for authentication.</p>
+<p>To use a Service Account instead of OAuth2 token flow, enter the path
+to your Service Account credentials at the
+<code>service_account_file</code> prompt and rclone won't use the
+browser based authentication flow. If you'd rather stuff the contents of
+the credentials file into the rclone config file, you can set
+<code>service_account_credentials</code> with the actual contents of the
+file instead, or set the equivalent environment variable.</p>
 <h3 id="anonymous-access-1">Anonymous Access</h3>
-<p>For downloads of objects that permit public access you can configure rclone to use anonymous access by setting <code>anonymous</code> to <code>true</code>. With unauthorized access you can't write or create files but only read or list those buckets and objects that have public read access.</p>
-<h3 id="application-default-credentials">Application Default Credentials</h3>
-<p>If no other source of credentials is provided, rclone will fall back to <a href="https://cloud.google.com/video-intelligence/docs/common/auth#authenticating_with_application_default_credentials">Application Default Credentials</a> this is useful both when you already have configured authentication for your developer account, or in production when running on a google compute host. Note that if running in docker, you may need to run additional commands on your google compute machine - <a href="https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud_as_a_docker_credential_helper">see this page</a>.</p>
-<p>Note that in the case application default credentials are used, there is no need to explicitly configure a project number.</p>
+<p>For downloads of objects that permit public access you can configure
+rclone to use anonymous access by setting <code>anonymous</code> to
+<code>true</code>. With unauthorized access you can't write or create
+files but only read or list those buckets and objects that have public
+read access.</p>
+<h3 id="application-default-credentials">Application Default
+Credentials</h3>
+<p>If no other source of credentials is provided, rclone will fall back
+to <a
+href="https://cloud.google.com/video-intelligence/docs/common/auth#authenticating_with_application_default_credentials">Application
+Default Credentials</a> this is useful both when you already have
+configured authentication for your developer account, or in production
+when running on a google compute host. Note that if running in docker,
+you may need to run additional commands on your google compute machine -
+<a
+href="https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud_as_a_docker_credential_helper">see
+this page</a>.</p>
+<p>Note that in the case application default credentials are used, there
+is no need to explicitly configure a project number.</p>
 <h3 id="fast-list-2">--fast-list</h3>
-<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
+<p>This remote supports <code>--fast-list</code> which allows you to use
+fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details.</p>
 <h3 id="custom-upload-headers">Custom upload headers</h3>
-<p>You can set custom upload headers with the <code>--header-upload</code> flag. Google Cloud Storage supports the headers as described in the <a href="https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata">working with metadata documentation</a></p>
+<p>You can set custom upload headers with the
+<code>--header-upload</code> flag. Google Cloud Storage supports the
+headers as described in the <a
+href="https://cloud.google.com/storage/docs/gsutil/addlhelp/WorkingWithObjectMetadata">working
+with metadata documentation</a></p>
 <ul>
 <li>Cache-Control</li>
 <li>Content-Disposition</li>
@@ -22674,12 +34067,27 @@ y/e/d&gt; y</code></pre>
 <li>X-Goog-Meta-</li>
 </ul>
 <p>Eg <code>--header-upload "Content-Type text/potato"</code></p>
-<p>Note that the last of these is for setting custom metadata in the form <code>--header-upload "x-goog-meta-key: value"</code></p>
+<p>Note that the last of these is for setting custom metadata in the
+form <code>--header-upload "x-goog-meta-key: value"</code></p>
 <h3 id="modification-times-5">Modification times</h3>
-<p>Google Cloud Storage stores md5sum natively. Google's <a href="https://cloud.google.com/storage/docs/gsutil">gsutil</a> tool stores modification time with one-second precision as <code>goog-reserved-file-mtime</code> in file metadata.</p>
-<p>To ensure compatibility with gsutil, rclone stores modification time in 2 separate metadata entries. <code>mtime</code> uses RFC3339 format with one-nanosecond precision. <code>goog-reserved-file-mtime</code> uses Unix timestamp format with one-second precision. To get modification time from object metadata, rclone reads the metadata in the following order: <code>mtime</code>, <code>goog-reserved-file-mtime</code>, object updated time.</p>
-<p>Note that rclone's default modify window is 1ns. Files uploaded by gsutil only contain timestamps with one-second precision. If you use rclone to sync files previously uploaded by gsutil, rclone will attempt to update modification time for all these files. To avoid these possibly unnecessary updates, use <code>--modify-window 1s</code>.</p>
-<h3 id="restricted-filename-characters-9">Restricted filename characters</h3>
+<p>Google Cloud Storage stores md5sum natively. Google's <a
+href="https://cloud.google.com/storage/docs/gsutil">gsutil</a> tool
+stores modification time with one-second precision as
+<code>goog-reserved-file-mtime</code> in file metadata.</p>
+<p>To ensure compatibility with gsutil, rclone stores modification time
+in 2 separate metadata entries. <code>mtime</code> uses RFC3339 format
+with one-nanosecond precision. <code>goog-reserved-file-mtime</code>
+uses Unix timestamp format with one-second precision. To get
+modification time from object metadata, rclone reads the metadata in the
+following order: <code>mtime</code>,
+<code>goog-reserved-file-mtime</code>, object updated time.</p>
+<p>Note that rclone's default modify window is 1ns. Files uploaded by
+gsutil only contain timestamps with one-second precision. If you use
+rclone to sync files previously uploaded by gsutil, rclone will attempt
+to update modification time for all these files. To avoid these possibly
+unnecessary updates, use <code>--modify-window 1s</code>.</p>
+<h3 id="restricted-filename-characters-8">Restricted filename
+characters</h3>
 <table>
 <thead>
 <tr class="header">
@@ -22711,9 +34119,12 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<h3 id="standard-options-16">Standard options</h3>
-<p>Here are the Standard options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<h3 id="standard-options-17">Standard options</h3>
+<p>Here are the Standard options specific to google cloud storage
+(Google Cloud Storage (this is not Google Drive)).</p>
 <h4 id="gcs-client-id">--gcs-client-id</h4>
 <p>OAuth Client Id.</p>
 <p>Leave blank normally.</p>
@@ -22736,7 +34147,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gcs-project-number">--gcs-project-number</h4>
 <p>Project number.</p>
-<p>Optional - needed only for list/create/delete buckets - see your developer console.</p>
+<p>Optional - needed only for list/create/delete buckets - see your
+developer console.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: project_number</li>
@@ -22756,8 +34168,10 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gcs-service-account-file">--gcs-service-account-file</h4>
 <p>Service Account Credentials JSON file path.</p>
-<p>Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
-<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
+<p>Leave blank normally. Needed only if you want use SA instead of
+interactive login.</p>
+<p>Leading <code>~</code> will be expanded in the file name as will
+environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: service_account_file</li>
@@ -22765,9 +34179,11 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="gcs-service-account-credentials">--gcs-service-account-credentials</h4>
+<h4
+id="gcs-service-account-credentials">--gcs-service-account-credentials</h4>
 <p>Service Account Credentials JSON blob.</p>
-<p>Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
+<p>Leave blank normally. Needed only if you want use SA instead of
+interactive login.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: service_account_credentials</li>
@@ -22777,7 +34193,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gcs-anonymous">--gcs-anonymous</h4>
 <p>Access public buckets and objects without credentials.</p>
-<p>Set to 'true' if you just want to download files and don't configure credentials.</p>
+<p>Set to 'true' if you just want to download files and don't configure
+credentials.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: anonymous</li>
@@ -22865,7 +34282,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gcs-bucket-policy-only">--gcs-bucket-policy-only</h4>
 <p>Access checks should use bucket-level IAM policies.</p>
-<p>If you want to upload objects to a bucket with Bucket Policy Only set then you will need to set this.</p>
+<p>If you want to upload objects to a bucket with Bucket Policy Only set
+then you will need to set this.</p>
 <p>When it is set, rclone:</p>
 <ul>
 <li>ignores ACLs set on buckets</li>
@@ -23037,7 +34455,8 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul>
 <h4 id="gcs-storage-class">--gcs-storage-class</h4>
-<p>The storage class to use when storing objects in Google Cloud Storage.</p>
+<p>The storage class to use when storing objects in Google Cloud
+Storage.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: storage_class</li>
@@ -23077,8 +34496,10 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul>
 <h4 id="gcs-env-auth">--gcs-env-auth</h4>
-<p>Get GCP IAM credentials from runtime (environment variables or instance meta data if no env vars).</p>
-<p>Only applies if service_account_file and service_account_credentials is blank.</p>
+<p>Get GCP IAM credentials from runtime (environment variables or
+instance meta data if no env vars).</p>
+<p>Only applies if service_account_file and service_account_credentials
+is blank.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: env_auth</li>
@@ -23097,8 +34518,9 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-16">Advanced options</h3>
-<p>Here are the Advanced options specific to google cloud storage (Google Cloud Storage (this is not Google Drive)).</p>
+<h3 id="advanced-options-17">Advanced options</h3>
+<p>Here are the Advanced options specific to google cloud storage
+(Google Cloud Storage (this is not Google Drive)).</p>
 <h4 id="gcs-token">--gcs-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
 <p>Properties:</p>
@@ -23129,8 +34551,10 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="gcs-directory-markers">--gcs-directory-markers</h4>
-<p>Upload an empty object with a trailing slash when a new directory is created</p>
-<p>Empty folders are unsupported for bucket based remotes, this option creates an empty object ending with "/", to persist the folder.</p>
+<p>Upload an empty object with a trailing slash when a new directory is
+created</p>
+<p>Empty folders are unsupported for bucket based remotes, this option
+creates an empty object ending with "/", to persist the folder.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: directory_markers</li>
@@ -23140,7 +34564,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gcs-no-check-bucket">--gcs-no-check-bucket</h4>
 <p>If set, don't attempt to check the bucket exists or create it.</p>
-<p>This can be useful when trying to minimise the number of transactions rclone does if you know the bucket exists already.</p>
+<p>This can be useful when trying to minimise the number of transactions
+rclone does if you know the bucket exists already.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_check_bucket</li>
@@ -23150,8 +34575,13 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gcs-decompress">--gcs-decompress</h4>
 <p>If set this will decompress gzip encoded objects.</p>
-<p>It is possible to upload objects to GCS with "Content-Encoding: gzip" set. Normally rclone will download these files as compressed objects.</p>
-<p>If this flag is set then rclone will decompress these files with "Content-Encoding: gzip" as they are received. This means that rclone can't check the size and hash but the file contents will be decompressed.</p>
+<p>It is possible to upload objects to GCS with "Content-Encoding: gzip"
+set. Normally rclone will download these files as compressed
+objects.</p>
+<p>If this flag is set then rclone will decompress these files with
+"Content-Encoding: gzip" as they are received. This means that rclone
+can't check the size and hash but the file contents will be
+decompressed.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: decompress</li>
@@ -23171,7 +34601,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gcs-encoding">--gcs-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -23189,14 +34620,23 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-13">Limitations</h2>
-<p><code>rclone about</code> is not supported by the Google Cloud Storage backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the Google Cloud
+Storage backend. Backends without this capability cannot determine free
+space for an rclone mount or use policy <code>mfs</code> (most free
+space) as a member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="google-drive">Google Drive</h1>
 <p>Paths are specified as <code>drive:path</code></p>
-<p>Drive paths may be as deep as required, e.g. <code>drive:directory/subdirectory</code>.</p>
-<h2 id="configuration-17">Configuration</h2>
-<p>The initial setup for drive involves getting a token from Google drive which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Drive paths may be as deep as required, e.g.
+<code>drive:directory/subdirectory</code>.</p>
+<h2 id="configuration-18">Configuration</h2>
+<p>The initial setup for drive involves getting a token from Google
+drive which you need to do in your browser. <code>rclone config</code>
+walks you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -23267,8 +34707,16 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if using web browser to automatically authenticate. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and it may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from Google if using web browser to automatically
+authenticate. This only runs from the moment it opens your browser to
+the moment you get back the verification code. This is on
+<code>http://127.0.0.1:53682/</code> and it may require you to unblock
+it temporarily if you are running a host firewall, or use manual
+mode.</p>
 <p>You can then use it like this,</p>
 <p>List directories in top level of your drive</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -23277,63 +34725,127 @@ y/e/d&gt; y</code></pre>
 <p>To copy a local directory to a drive directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <h3 id="scopes">Scopes</h3>
-<p>Rclone allows you to select which scope you would like for rclone to use. This changes what type of token is granted to rclone. <a href="https://developers.google.com/drive/v3/web/about-auth">The scopes are defined here</a>.</p>
-<p>A comma-separated list is allowed e.g. <code>drive.readonly,drive.file</code>.</p>
+<p>Rclone allows you to select which scope you would like for rclone to
+use. This changes what type of token is granted to rclone. <a
+href="https://developers.google.com/drive/v3/web/about-auth">The scopes
+are defined here</a>.</p>
+<p>A comma-separated list is allowed e.g.
+<code>drive.readonly,drive.file</code>.</p>
 <p>The scope are</p>
 <h4 id="drive">drive</h4>
-<p>This is the default scope and allows full access to all files, except for the Application Data Folder (see below).</p>
+<p>This is the default scope and allows full access to all files, except
+for the Application Data Folder (see below).</p>
 <p>Choose this one if you aren't sure.</p>
 <h4 id="drive.readonly">drive.readonly</h4>
-<p>This allows read only access to all files. Files may be listed and downloaded but not uploaded, renamed or deleted.</p>
+<p>This allows read only access to all files. Files may be listed and
+downloaded but not uploaded, renamed or deleted.</p>
 <h4 id="drive.file">drive.file</h4>
-<p>With this scope rclone can read/view/modify only those files and folders it creates.</p>
-<p>So if you uploaded files to drive via the web interface (or any other means) they will not be visible to rclone.</p>
-<p>This can be useful if you are using rclone to backup data and you want to be sure confidential data on your drive is not visible to rclone.</p>
+<p>With this scope rclone can read/view/modify only those files and
+folders it creates.</p>
+<p>So if you uploaded files to drive via the web interface (or any other
+means) they will not be visible to rclone.</p>
+<p>This can be useful if you are using rclone to backup data and you
+want to be sure confidential data on your drive is not visible to
+rclone.</p>
 <p>Files created with this scope are visible in the web interface.</p>
 <h4 id="drive.appfolder">drive.appfolder</h4>
-<p>This gives rclone its own private area to store files. Rclone will not be able to see any other files on your drive and you won't be able to see rclone's files from the web interface either.</p>
+<p>This gives rclone its own private area to store files. Rclone will
+not be able to see any other files on your drive and you won't be able
+to see rclone's files from the web interface either.</p>
 <h4 id="drive.metadata.readonly">drive.metadata.readonly</h4>
-<p>This allows read only access to file names only. It does not allow rclone to download or upload data, or rename or delete files or directories.</p>
+<p>This allows read only access to file names only. It does not allow
+rclone to download or upload data, or rename or delete files or
+directories.</p>
 <h3 id="root-folder-id-3">Root folder ID</h3>
-<p>This option has been moved to the advanced section. You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your drive.</p>
-<p>Normally you will leave this blank and rclone will determine the correct root to use itself.</p>
-<p>However you can set this to restrict rclone to a specific folder hierarchy or to access data within the "Computers" tab on the drive web interface (where files from Google's Backup and Sync desktop program go).</p>
-<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display. This will be the last segment of the URL when you open the relevant folder in the drive web interface.</p>
-<p>So if the folder you want rclone to use has a URL which looks like <code>https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh</code> in the browser, then you use <code>1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh</code> as the <code>root_folder_id</code> in the config.</p>
-<p><strong>NB</strong> folders under the "Computers" tab seem to be read only (drive gives a 500 error) when using rclone.</p>
-<p>There doesn't appear to be an API to discover the folder IDs of the "Computers" tab - please contact us if you know otherwise!</p>
-<p>Note also that rclone can't access any data under the "Backups" tab on the google drive web interface yet.</p>
+<p>This option has been moved to the advanced section. You can set the
+<code>root_folder_id</code> for rclone. This is the directory
+(identified by its <code>Folder ID</code>) that rclone considers to be
+the root of your drive.</p>
+<p>Normally you will leave this blank and rclone will determine the
+correct root to use itself.</p>
+<p>However you can set this to restrict rclone to a specific folder
+hierarchy or to access data within the "Computers" tab on the drive web
+interface (where files from Google's Backup and Sync desktop program
+go).</p>
+<p>In order to do this you will have to find the <code>Folder ID</code>
+of the directory you wish rclone to display. This will be the last
+segment of the URL when you open the relevant folder in the drive web
+interface.</p>
+<p>So if the folder you want rclone to use has a URL which looks like
+<code>https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh</code>
+in the browser, then you use
+<code>1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh</code> as the
+<code>root_folder_id</code> in the config.</p>
+<p><strong>NB</strong> folders under the "Computers" tab seem to be read
+only (drive gives a 500 error) when using rclone.</p>
+<p>There doesn't appear to be an API to discover the folder IDs of the
+"Computers" tab - please contact us if you know otherwise!</p>
+<p>Note also that rclone can't access any data under the "Backups" tab
+on the google drive web interface yet.</p>
 <h3 id="service-account-support-1">Service Account support</h3>
-<p>You can set up rclone with Google Drive in an unattended mode, i.e. not tied to a specific end-user Google account. This is useful when you want to synchronise files onto machines that don't have actively logged-in users, for example build machines.</p>
-<p>To use a Service Account instead of OAuth2 token flow, enter the path to your Service Account credentials at the <code>service_account_file</code> prompt during <code>rclone config</code> and rclone won't use the browser based authentication flow. If you'd rather stuff the contents of the credentials file into the rclone config file, you can set <code>service_account_credentials</code> with the actual contents of the file instead, or set the equivalent environment variable.</p>
-<h4 id="use-case---google-workspace-account-and-individual-drive">Use case - Google Workspace account and individual Drive</h4>
-<p>Let's say that you are the administrator of a Google Workspace. The goal is to read or write data on an individual's Drive account, who IS a member of the domain. We'll call the domain <strong>example.com</strong>, and the user <strong>foo@example.com</strong>.</p>
+<p>You can set up rclone with Google Drive in an unattended mode, i.e.
+not tied to a specific end-user Google account. This is useful when you
+want to synchronise files onto machines that don't have actively
+logged-in users, for example build machines.</p>
+<p>To use a Service Account instead of OAuth2 token flow, enter the path
+to your Service Account credentials at the
+<code>service_account_file</code> prompt during
+<code>rclone config</code> and rclone won't use the browser based
+authentication flow. If you'd rather stuff the contents of the
+credentials file into the rclone config file, you can set
+<code>service_account_credentials</code> with the actual contents of the
+file instead, or set the equivalent environment variable.</p>
+<h4 id="use-case---google-workspace-account-and-individual-drive">Use
+case - Google Workspace account and individual Drive</h4>
+<p>Let's say that you are the administrator of a Google Workspace. The
+goal is to read or write data on an individual's Drive account, who IS a
+member of the domain. We'll call the domain
+<strong>example.com</strong>, and the user
+<strong>foo@example.com</strong>.</p>
 <p>There's a few steps we need to go through to accomplish this:</p>
-<h5 id="create-a-service-account-for-example.com">1. Create a service account for example.com</h5>
+<h5 id="create-a-service-account-for-example.com">1. Create a service
+account for example.com</h5>
 <ul>
-<li>To create a service account and obtain its credentials, go to the <a href="https://console.developers.google.com">Google Developer Console</a>.</li>
-<li>You must have a project - create one if you don't and make sure you are on the selected project.</li>
+<li>To create a service account and obtain its credentials, go to the <a
+href="https://console.developers.google.com">Google Developer
+Console</a>.</li>
+<li>You must have a project - create one if you don't and make sure you
+are on the selected project.</li>
 <li>Then go to "IAM &amp; admin" -&gt; "Service Accounts".</li>
-<li>Use the "Create Service Account" button. Fill in "Service account name" and "Service account ID" with something that identifies your client.</li>
+<li>Use the "Create Service Account" button. Fill in "Service account
+name" and "Service account ID" with something that identifies your
+client.</li>
 <li>Select "Create And Continue". Step 2 and 3 are optional.</li>
 <li>Click on the newly created service account</li>
 <li>Click "Keys" and then "Add Key" and then "Create new key"</li>
 <li>Choose type "JSON" and click create</li>
-<li>This will download a small JSON file that rclone will use for authentication.</li>
+<li>This will download a small JSON file that rclone will use for
+authentication.</li>
 </ul>
-<p>If you ever need to remove access, press the "Delete service account key" button.</p>
-<h5 id="allowing-api-access-to-example.com-google-drive">2. Allowing API access to example.com Google Drive</h5>
+<p>If you ever need to remove access, press the "Delete service account
+key" button.</p>
+<h5 id="allowing-api-access-to-example.com-google-drive">2. Allowing API
+access to example.com Google Drive</h5>
 <ul>
-<li>Go to example.com's <a href="https://admin.google.com">Workspace Admin Console</a></li>
+<li>Go to example.com's <a href="https://admin.google.com">Workspace
+Admin Console</a></li>
 <li>Go into "Security" (or use the search bar)</li>
 <li>Select "Access and data control" and then "API controls"</li>
 <li>Click "Manage domain-wide delegation"</li>
 <li>Click "Add new"</li>
-<li>In the "Client ID" field enter the service account's "Client ID" - this can be found in the Developer Console under "IAM &amp; Admin" -&gt; "Service Accounts", then "View Client ID" for the newly created service account. It is a ~21 character numerical string.</li>
-<li>In the next field, "OAuth Scopes", enter <code>https://www.googleapis.com/auth/drive</code> to grant read/write access to Google Drive specifically. You can also use <code>https://www.googleapis.com/auth/drive.readonly</code> for read only access.</li>
+<li>In the "Client ID" field enter the service account's "Client ID" -
+this can be found in the Developer Console under "IAM &amp; Admin" -&gt;
+"Service Accounts", then "View Client ID" for the newly created service
+account. It is a ~21 character numerical string.</li>
+<li>In the next field, "OAuth Scopes", enter
+<code>https://www.googleapis.com/auth/drive</code> to grant read/write
+access to Google Drive specifically. You can also use
+<code>https://www.googleapis.com/auth/drive.readonly</code> for read
+only access.</li>
 <li>Click "Authorise"</li>
 </ul>
-<h5 id="configure-rclone-assuming-a-new-install">3. Configure rclone, assuming a new install</h5>
+<h5 id="configure-rclone-assuming-a-new-install">3. Configure rclone,
+assuming a new install</h5>
 <pre><code>rclone config
 
 n/s/q&gt; n         # New
@@ -23352,15 +34864,28 @@ y/n&gt;             # Auto config, n
 <li>The arguments do:
 <ul>
 <li><code>-v</code> - verbose logging</li>
-<li><code>--drive-impersonate foo@example.com</code> - this is what does the magic, pretending to be user foo.</li>
+<li><code>--drive-impersonate foo@example.com</code> - this is what does
+the magic, pretending to be user foo.</li>
 <li><code>lsf</code> - list files in a parsing friendly way</li>
-<li><code>gdrive:backup</code> - use the remote called gdrive, work in the folder named backup.</li>
+<li><code>gdrive:backup</code> - use the remote called gdrive, work in
+the folder named backup.</li>
 </ul></li>
 </ul>
-<p>Note: in case you configured a specific root folder on gdrive and rclone is unable to access the contents of that folder when using <code>--drive-impersonate</code>, do this instead: - in the gdrive web interface, share your root folder with the user/email of the new Service Account you created/selected at step 1 - use rclone without specifying the <code>--drive-impersonate</code> option, like this: <code>rclone -v lsf gdrive:backup</code></p>
+<p>Note: in case you configured a specific root folder on gdrive and
+rclone is unable to access the contents of that folder when using
+<code>--drive-impersonate</code>, do this instead: - in the gdrive web
+interface, share your root folder with the user/email of the new Service
+Account you created/selected at step 1 - use rclone without specifying
+the <code>--drive-impersonate</code> option, like this:
+<code>rclone -v lsf gdrive:backup</code></p>
 <h3 id="shared-drives-team-drives">Shared drives (team drives)</h3>
-<p>If you want to configure the remote to point to a Google Shared Drive (previously known as Team Drives) then answer <code>y</code> to the question <code>Configure this as a Shared Drive (Team Drive)?</code>.</p>
-<p>This will fetch the list of Shared Drives from google and allow you to configure which one you want to use. You can also type in a Shared Drive ID if you prefer.</p>
+<p>If you want to configure the remote to point to a Google Shared Drive
+(previously known as Team Drives) then answer <code>y</code> to the
+question
+<code>Configure this as a Shared Drive (Team Drive)?</code>.</p>
+<p>This will fetch the list of Shared Drives from google and allow you
+to configure which one you want to use. You can also type in a Shared
+Drive ID if you prefer.</p>
 <p>For example:</p>
 <pre><code>Configure this as a Shared Drive (Team Drive)?
 y) Yes
@@ -23388,16 +34913,28 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
 <h3 id="fast-list-3">--fast-list</h3>
-<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
-<p>It does this by combining multiple <code>list</code> calls into a single API request.</p>
-<p>This works by combining many <code>'%s' in parents</code> filters into one expression. To list the contents of directories a, b and c, the following requests will be send by the regular <code>List</code> function:</p>
+<p>This remote supports <code>--fast-list</code> which allows you to use
+fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details.</p>
+<p>It does this by combining multiple <code>list</code> calls into a
+single API request.</p>
+<p>This works by combining many <code>'%s' in parents</code> filters
+into one expression. To list the contents of directories a, b and c, the
+following requests will be send by the regular <code>List</code>
+function:</p>
 <pre><code>trashed=false and &#39;a&#39; in parents
 trashed=false and &#39;b&#39; in parents
 trashed=false and &#39;c&#39; in parents</code></pre>
 <p>These can now be combined into a single request:</p>
 <pre><code>trashed=false and (&#39;a&#39; in parents or &#39;b&#39; in parents or &#39;c&#39; in parents)</code></pre>
-<p>The implementation of <code>ListR</code> will put up to 50 <code>parents</code> filters into one request. It will use the <code>--checkers</code> value to specify the number of requests to run in parallel.</p>
-<p>In tests, these batch requests were up to 20x faster than the regular method. Running the following command against different sized folders gives:</p>
+<p>The implementation of <code>ListR</code> will put up to 50
+<code>parents</code> filters into one request. It will use the
+<code>--checkers</code> value to specify the number of requests to run
+in parallel.</p>
+<p>In tests, these batch requests were up to 20x faster than the regular
+method. Running the following command against different sized folders
+gives:</p>
 <pre><code>rclone lsjson -vv -R --checkers=6 gdrive:folder</code></pre>
 <p>small folder (220 directories, 700 files):</p>
 <ul>
@@ -23409,63 +34946,144 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>without <code>--fast-list</code>: 22:05 min</li>
 <li>with <code>--fast-list</code>: 58s</li>
 </ul>
-<h3 id="modification-times-and-hashes-8">Modification times and hashes</h3>
+<h3 id="modification-times-and-hashes-8">Modification times and
+hashes</h3>
 <p>Google drive stores modification times accurate to 1 ms.</p>
-<p>Hash algorithms MD5, SHA1 and SHA256 are supported. Note, however, that a small fraction of files uploaded may not have SHA1 or SHA256 hashes especially if they were uploaded before 2018.</p>
-<h3 id="restricted-filename-characters-10">Restricted filename characters</h3>
-<p>Only Invalid UTF-8 bytes will be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<p>In contrast to other backends, <code>/</code> can also be used in names and <code>.</code> or <code>..</code> are valid names.</p>
+<p>Hash algorithms MD5, SHA1 and SHA256 are supported. Note, however,
+that a small fraction of files uploaded may not have SHA1 or SHA256
+hashes especially if they were uploaded before 2018.</p>
+<h3 id="restricted-filename-characters-9">Restricted filename
+characters</h3>
+<p>Only Invalid UTF-8 bytes will be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<p>In contrast to other backends, <code>/</code> can also be used in
+names and <code>.</code> or <code>..</code> are valid names.</p>
 <h3 id="revisions">Revisions</h3>
-<p>Google drive stores revisions of files. When you upload a change to an existing file to google drive using rclone it will create a new revision of that file.</p>
-<p>Revisions follow the standard google policy which at time of writing was</p>
+<p>Google drive stores revisions of files. When you upload a change to
+an existing file to google drive using rclone it will create a new
+revision of that file.</p>
+<p>Revisions follow the standard google policy which at time of writing
+was</p>
 <ul>
-<li>They are deleted after 30 days or 100 revisions (whatever comes first).</li>
+<li>They are deleted after 30 days or 100 revisions (whatever comes
+first).</li>
 <li>They do not count towards a user storage quota.</li>
 </ul>
 <h3 id="deleting-files-1">Deleting files</h3>
-<p>By default rclone will send all files to the trash when deleting files. If deleting them permanently is required then use the <code>--drive-use-trash=false</code> flag, or set the equivalent environment variable.</p>
+<p>By default rclone will send all files to the trash when deleting
+files. If deleting them permanently is required then use the
+<code>--drive-use-trash=false</code> flag, or set the equivalent
+environment variable.</p>
 <h3 id="shortcuts">Shortcuts</h3>
-<p>In March 2020 Google introduced a new feature in Google Drive called <a href="https://support.google.com/drive/answer/9700156">drive shortcuts</a> (<a href="https://developers.google.com/drive/api/v3/shortcuts">API</a>). These will (by September 2020) <a href="https://cloud.google.com/blog/products/g-suite/simplifying-google-drives-folder-structure-and-sharing-models">replace the ability for files or folders to be in multiple folders at once</a>.</p>
-<p>Shortcuts are files that link to other files on Google Drive somewhat like a symlink in unix, except they point to the underlying file data (e.g. the inode in unix terms) so they don't break if the source is renamed or moved about.</p>
+<p>In March 2020 Google introduced a new feature in Google Drive called
+<a href="https://support.google.com/drive/answer/9700156">drive
+shortcuts</a> (<a
+href="https://developers.google.com/drive/api/v3/shortcuts">API</a>).
+These will (by September 2020) <a
+href="https://cloud.google.com/blog/products/g-suite/simplifying-google-drives-folder-structure-and-sharing-models">replace
+the ability for files or folders to be in multiple folders at
+once</a>.</p>
+<p>Shortcuts are files that link to other files on Google Drive somewhat
+like a symlink in unix, except they point to the underlying file data
+(e.g. the inode in unix terms) so they don't break if the source is
+renamed or moved about.</p>
 <p>By default rclone treats these as follows.</p>
 <p>For shortcuts pointing to files:</p>
 <ul>
 <li>When listing a file shortcut appears as the destination file.</li>
-<li>When downloading the contents of the destination file is downloaded.</li>
-<li>When updating shortcut file with a non shortcut file, the shortcut is removed then a new file is uploaded in place of the shortcut.</li>
-<li>When server-side moving (renaming) the shortcut is renamed, not the destination file.</li>
-<li>When server-side copying the shortcut is copied, not the contents of the shortcut. (unless <code>--drive-copy-shortcut-content</code> is in use in which case the contents of the shortcut gets copied).</li>
+<li>When downloading the contents of the destination file is
+downloaded.</li>
+<li>When updating shortcut file with a non shortcut file, the shortcut
+is removed then a new file is uploaded in place of the shortcut.</li>
+<li>When server-side moving (renaming) the shortcut is renamed, not the
+destination file.</li>
+<li>When server-side copying the shortcut is copied, not the contents of
+the shortcut. (unless <code>--drive-copy-shortcut-content</code> is in
+use in which case the contents of the shortcut gets copied).</li>
 <li>When deleting the shortcut is deleted not the linked file.</li>
-<li>When setting the modification time, the modification time of the linked file will be set.</li>
+<li>When setting the modification time, the modification time of the
+linked file will be set.</li>
 </ul>
 <p>For shortcuts pointing to folders:</p>
 <ul>
-<li>When listing the shortcut appears as a folder and that folder will contain the contents of the linked folder appear (including any sub folders)</li>
-<li>When downloading the contents of the linked folder and sub contents are downloaded</li>
-<li>When uploading to a shortcut folder the file will be placed in the linked folder</li>
-<li>When server-side moving (renaming) the shortcut is renamed, not the destination folder</li>
-<li>When server-side copying the contents of the linked folder is copied, not the shortcut.</li>
-<li>When deleting with <code>rclone rmdir</code> or <code>rclone purge</code> the shortcut is deleted not the linked folder.</li>
-<li><strong>NB</strong> When deleting with <code>rclone remove</code> or <code>rclone mount</code> the contents of the linked folder will be deleted.</li>
+<li>When listing the shortcut appears as a folder and that folder will
+contain the contents of the linked folder appear (including any sub
+folders)</li>
+<li>When downloading the contents of the linked folder and sub contents
+are downloaded</li>
+<li>When uploading to a shortcut folder the file will be placed in the
+linked folder</li>
+<li>When server-side moving (renaming) the shortcut is renamed, not the
+destination folder</li>
+<li>When server-side copying the contents of the linked folder is
+copied, not the shortcut.</li>
+<li>When deleting with <code>rclone rmdir</code> or
+<code>rclone purge</code> the shortcut is deleted not the linked
+folder.</li>
+<li><strong>NB</strong> When deleting with <code>rclone remove</code> or
+<code>rclone mount</code> the contents of the linked folder will be
+deleted.</li>
 </ul>
-<p>The <a href="https://rclone.org/commands/rclone_backend/">rclone backend</a> command can be used to create shortcuts.</p>
-<p>Shortcuts can be completely ignored with the <code>--drive-skip-shortcuts</code> flag or the corresponding <code>skip_shortcuts</code> configuration setting.</p>
-<p>If you have shortcuts that lead to an infinite recursion in your drive (e.g. a shortcut pointing to a parent folder), <code>skip_shortcuts</code> might be mandatory to be able to copy the drive.</p>
+<p>The <a href="https://rclone.org/commands/rclone_backend/">rclone
+backend</a> command can be used to create shortcuts.</p>
+<p>Shortcuts can be completely ignored with the
+<code>--drive-skip-shortcuts</code> flag or the corresponding
+<code>skip_shortcuts</code> configuration setting.</p>
+<p>If you have shortcuts that lead to an infinite recursion in your
+drive (e.g. a shortcut pointing to a parent folder),
+<code>skip_shortcuts</code> might be mandatory to be able to copy the
+drive.</p>
 <h3 id="emptying-trash">Emptying trash</h3>
-<p>If you wish to empty your trash you can use the <code>rclone cleanup remote:</code> command which will permanently delete all your trashed files. This command does not take any path arguments.</p>
-<p>Note that Google Drive takes some time (minutes to days) to empty the trash even though the command returns within a few seconds. No output is echoed, so there will be no confirmation even using -v or -vv.</p>
+<p>If you wish to empty your trash you can use the
+<code>rclone cleanup remote:</code> command which will permanently
+delete all your trashed files. This command does not take any path
+arguments.</p>
+<p>Note that Google Drive takes some time (minutes to days) to empty the
+trash even though the command returns within a few seconds. No output is
+echoed, so there will be no confirmation even using -v or -vv.</p>
 <h3 id="quota-information">Quota information</h3>
-<p>To view your current quota you can use the <code>rclone about remote:</code> command which will display your usage limit (quota), the usage in Google Drive, the size of all files in the Trash and the space used by other Google services such as Gmail. This command does not take any path arguments.</p>
-<h4 id="importexport-of-google-documents">Import/Export of google documents</h4>
-<p>Google documents can be exported from and uploaded to Google Drive.</p>
-<p>When rclone downloads a Google doc it chooses a format to download depending upon the <code>--drive-export-formats</code> setting. By default the export formats are <code>docx,xlsx,pptx,svg</code> which are a sensible default for an editable document.</p>
-<p>When choosing a format, rclone runs down the list provided in order and chooses the first file format the doc can be exported as from the list. If the file can't be exported to a format on the formats list, then rclone will choose a format from the default list.</p>
-<p>If you prefer an archive copy then you might use <code>--drive-export-formats pdf</code>, or if you prefer openoffice/libreoffice formats you might use <code>--drive-export-formats ods,odt,odp</code>.</p>
-<p>Note that rclone adds the extension to the google doc, so if it is called <code>My Spreadsheet</code> on google docs, it will be exported as <code>My Spreadsheet.xlsx</code> or <code>My Spreadsheet.pdf</code> etc.</p>
-<p>When importing files into Google Drive, rclone will convert all files with an extension in <code>--drive-import-formats</code> to their associated document type. rclone will not convert any files by default, since the conversion is lossy process.</p>
-<p>The conversion must result in a file with the same extension when the <code>--drive-export-formats</code> rules are applied to the uploaded document.</p>
+<p>To view your current quota you can use the
+<code>rclone about remote:</code> command which will display your usage
+limit (quota), the usage in Google Drive, the size of all files in the
+Trash and the space used by other Google services such as Gmail. This
+command does not take any path arguments.</p>
+<h4 id="importexport-of-google-documents">Import/Export of google
+documents</h4>
+<p>Google documents can be exported from and uploaded to Google
+Drive.</p>
+<p>When rclone downloads a Google doc it chooses a format to download
+depending upon the <code>--drive-export-formats</code> setting. By
+default the export formats are <code>docx,xlsx,pptx,svg</code> which are
+a sensible default for an editable document.</p>
+<p>When choosing a format, rclone runs down the list provided in order
+and chooses the first file format the doc can be exported as from the
+list. If the file can't be exported to a format on the formats list,
+then rclone will choose a format from the default list.</p>
+<p>If you prefer an archive copy then you might use
+<code>--drive-export-formats pdf</code>, or if you prefer
+openoffice/libreoffice formats you might use
+<code>--drive-export-formats ods,odt,odp</code>.</p>
+<p>Note that rclone adds the extension to the google doc, so if it is
+called <code>My Spreadsheet</code> on google docs, it will be exported
+as <code>My Spreadsheet.xlsx</code> or <code>My Spreadsheet.pdf</code>
+etc.</p>
+<p>When importing files into Google Drive, rclone will convert all files
+with an extension in <code>--drive-import-formats</code> to their
+associated document type. rclone will not convert any files by default,
+since the conversion is lossy process.</p>
+<p>The conversion must result in a file with the same extension when the
+<code>--drive-export-formats</code> rules are applied to the uploaded
+document.</p>
 <p>Here are some examples for allowed and prohibited conversions.</p>
 <table>
+<colgroup>
+<col style="width: 24%" />
+<col style="width: 24%" />
+<col style="width: 17%" />
+<col style="width: 21%" />
+<col style="width: 12%" />
+</colgroup>
 <thead>
 <tr class="header">
 <th>export-formats</th>
@@ -23527,9 +35145,23 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </tr>
 </tbody>
 </table>
-<p>This limitation can be disabled by specifying <code>--drive-allow-import-name-change</code>. When using this flag, rclone can convert multiple files types resulting in the same document type at once, e.g. with <code>--drive-import-formats docx,odt,txt</code>, all files having these extension would result in a document represented as a docx file. This brings the additional risk of overwriting a document, if multiple files have the same stem. Many rclone operations will not handle this name change in any way. They assume an equal name when copying files and might copy the file again or delete them when the name changes.</p>
-<p>Here are the possible export extensions with their corresponding mime types. Most of these can also be used for importing, but there more that are not listed here. Some of these additional ones might only be available when the operating system provides the correct MIME type entries.</p>
-<p>This list can be changed by Google Drive at any time and might not represent the currently available conversions.</p>
+<p>This limitation can be disabled by specifying
+<code>--drive-allow-import-name-change</code>. When using this flag,
+rclone can convert multiple files types resulting in the same document
+type at once, e.g. with
+<code>--drive-import-formats docx,odt,txt</code>, all files having these
+extension would result in a document represented as a docx file. This
+brings the additional risk of overwriting a document, if multiple files
+have the same stem. Many rclone operations will not handle this name
+change in any way. They assume an equal name when copying files and
+might copy the file again or delete them when the name changes.</p>
+<p>Here are the possible export extensions with their corresponding mime
+types. Most of these can also be used for importing, but there more that
+are not listed here. Some of these additional ones might only be
+available when the operating system provides the correct MIME type
+entries.</p>
+<p>This list can be changed by Google Drive at any time and might not
+represent the currently available conversions.</p>
 <table>
 <colgroup>
 <col style="width: 28%" />
@@ -23666,7 +35298,11 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Google documents can also be exported as link files. These files will open a browser window for the Google Docs website of that document when opened. The link file extension has to be specified as a <code>--drive-export-formats</code> parameter. They will match all available Google Documents.</p>
+<p>Google documents can also be exported as link files. These files will
+open a browser window for the Google Docs website of that document when
+opened. The link file extension has to be specified as a
+<code>--drive-export-formats</code> parameter. They will match all
+available Google Documents.</p>
 <table>
 <thead>
 <tr class="header">
@@ -23698,10 +35334,13 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </tr>
 </tbody>
 </table>
-<h3 id="standard-options-17">Standard options</h3>
+<h3 id="standard-options-18">Standard options</h3>
 <p>Here are the Standard options specific to drive (Google Drive).</p>
 <h4 id="drive-client-id">--drive-client-id</h4>
-<p>Google Application Client Id Setting your own is recommended. See https://rclone.org/drive/#making-your-own-client-id for how to create your own. If you leave this blank, it will use an internal key which is low performance.</p>
+<p>Google Application Client Id Setting your own is recommended. See
+https://rclone.org/drive/#making-your-own-client-id for how to create
+your own. If you leave this blank, it will use an internal key which is
+low performance.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: client_id</li>
@@ -23720,7 +35359,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="drive-scope">--drive-scope</h4>
-<p>Comma separated list of scopes that rclone should use when requesting access from drive.</p>
+<p>Comma separated list of scopes that rclone should use when requesting
+access from drive.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: scope</li>
@@ -23741,7 +35381,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <ul>
 <li>Access to files created by rclone only.</li>
 <li>These are visible in the drive website.</li>
-<li>File authorization is revoked when the user deauthorizes the app.</li>
+<li>File authorization is revoked when the user deauthorizes the
+app.</li>
 </ul></li>
 <li>"drive.appfolder"
 <ul>
@@ -23757,8 +35398,10 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-service-account-file">--drive-service-account-file</h4>
 <p>Service Account Credentials JSON file path.</p>
-<p>Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
-<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
+<p>Leave blank normally. Needed only if you want use SA instead of
+interactive login.</p>
+<p>Leading <code>~</code> will be expanded in the file name as will
+environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: service_account_file</li>
@@ -23775,7 +35418,7 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="advanced-options-17">Advanced options</h3>
+<h3 id="advanced-options-18">Advanced options</h3>
 <p>Here are the Advanced options specific to drive (Google Drive).</p>
 <h4 id="drive-token">--drive-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
@@ -23808,7 +35451,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-root-folder-id">--drive-root-folder-id</h4>
 <p>ID of the root folder. Leave blank normally.</p>
-<p>Fill in to access "Computers" folders (see docs), or for rclone to use a non root folder as its starting point.</p>
+<p>Fill in to access "Computers" folders (see docs), or for rclone to
+use a non root folder as its starting point.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_id</li>
@@ -23816,9 +35460,11 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="drive-service-account-credentials">--drive-service-account-credentials</h4>
+<h4
+id="drive-service-account-credentials">--drive-service-account-credentials</h4>
 <p>Service Account Credentials JSON blob.</p>
-<p>Leave blank normally. Needed only if you want use SA instead of interactive login.</p>
+<p>Leave blank normally. Needed only if you want use SA instead of
+interactive login.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: service_account_credentials</li>
@@ -23846,7 +35492,9 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-use-trash">--drive-use-trash</h4>
 <p>Send files to the trash instead of deleting permanently.</p>
-<p>Defaults to true, namely sending files to the trash. Use <code>--drive-use-trash=false</code> to delete files permanently instead.</p>
+<p>Defaults to true, namely sending files to the trash. Use
+<code>--drive-use-trash=false</code> to delete files permanently
+instead.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_trash</li>
@@ -23856,8 +35504,10 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-copy-shortcut-content">--drive-copy-shortcut-content</h4>
 <p>Server side copy contents of shortcuts instead of the shortcut.</p>
-<p>When doing server side copies, normally rclone will copy shortcuts as shortcuts.</p>
-<p>If this flag is used then rclone will copy the contents of shortcuts rather than shortcuts themselves when doing server side copies.</p>
+<p>When doing server side copies, normally rclone will copy shortcuts as
+shortcuts.</p>
+<p>If this flag is used then rclone will copy the contents of shortcuts
+rather than shortcuts themselves when doing server side copies.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: copy_shortcut_content</li>
@@ -23877,11 +35527,15 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-show-all-gdocs">--drive-show-all-gdocs</h4>
 <p>Show all Google Docs including non-exportable ones in listings.</p>
-<p>If you try a server side copy on a Google Form without this flag, you will get this error:</p>
+<p>If you try a server side copy on a Google Form without this flag, you
+will get this error:</p>
 <pre><code>No export formats found for &quot;application/vnd.google-apps.form&quot;</code></pre>
-<p>However adding this flag will allow the form to be server side copied.</p>
-<p>Note that rclone doesn't add extensions to the Google Docs file names in this mode.</p>
-<p>Do <strong>not</strong> use this flag when trying to download Google Docs - rclone will fail to download them.</p>
+<p>However adding this flag will allow the form to be server side
+copied.</p>
+<p>Note that rclone doesn't add extensions to the Google Docs file names
+in this mode.</p>
+<p>Do <strong>not</strong> use this flag when trying to download Google
+Docs - rclone will fail to download them.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: show_all_gdocs</li>
@@ -23891,10 +35545,13 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-skip-checksum-gphotos">--drive-skip-checksum-gphotos</h4>
 <p>Skip checksums on Google photos and videos only.</p>
-<p>Use this if you get checksum errors when transferring Google photos or videos.</p>
-<p>Setting this flag will cause Google photos and videos to return a blank checksums.</p>
+<p>Use this if you get checksum errors when transferring Google photos
+or videos.</p>
+<p>Setting this flag will cause Google photos and videos to return a
+blank checksums.</p>
 <p>Google photos are identified by being in the "photos" space.</p>
-<p>Corrupted checksums are caused by Google modifying the image/video but not updating the checksum.</p>
+<p>Corrupted checksums are caused by Google modifying the image/video
+but not updating the checksum.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: skip_checksum_gphotos</li>
@@ -23904,8 +35561,11 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-shared-with-me">--drive-shared-with-me</h4>
 <p>Only show files that are shared with me.</p>
-<p>Instructs rclone to operate on your "Shared with me" folder (where Google Drive lets you access the files and folders others have shared with you).</p>
-<p>This works both with the "list" (lsd, lsl, etc.) and the "copy" commands (copy, sync, etc.), and with all other commands too.</p>
+<p>Instructs rclone to operate on your "Shared with me" folder (where
+Google Drive lets you access the files and folders others have shared
+with you).</p>
+<p>This works both with the "list" (lsd, lsl, etc.) and the "copy"
+commands (copy, sync, etc.), and with all other commands too.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: shared_with_me</li>
@@ -23915,7 +35575,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-trashed-only">--drive-trashed-only</h4>
 <p>Only show files that are in the trash.</p>
-<p>This will show trashed files in their original directory structure.</p>
+<p>This will show trashed files in their original directory
+structure.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: trashed_only</li>
@@ -23942,7 +35603,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="drive-export-formats">--drive-export-formats</h4>
-<p>Comma separated list of preferred formats for downloading Google docs.</p>
+<p>Comma separated list of preferred formats for downloading Google
+docs.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: export_formats</li>
@@ -23951,7 +35613,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Default: "docx,xlsx,pptx,svg"</li>
 </ul>
 <h4 id="drive-import-formats">--drive-import-formats</h4>
-<p>Comma separated list of preferred formats for uploading Google docs.</p>
+<p>Comma separated list of preferred formats for uploading Google
+docs.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: import_formats</li>
@@ -23959,9 +35622,11 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="drive-allow-import-name-change">--drive-allow-import-name-change</h4>
+<h4
+id="drive-allow-import-name-change">--drive-allow-import-name-change</h4>
 <p>Allow the filetype to change when uploading Google docs.</p>
-<p>E.g. file.doc to file.docx. This will confuse sync and reupload every time.</p>
+<p>E.g. file.doc to file.docx. This will confuse sync and reupload every
+time.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: allow_import_name_change</li>
@@ -23971,10 +35636,19 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-use-created-date">--drive-use-created-date</h4>
 <p>Use file created date instead of modified date.</p>
-<p>Useful when downloading data and you want the creation date used in place of the last modified date.</p>
-<p><strong>WARNING</strong>: This flag may have some unexpected consequences.</p>
-<p>When uploading to your drive all files will be overwritten unless they haven't been modified since their creation. And the inverse will occur while downloading. This side effect can be avoided by using the "--checksum" flag.</p>
-<p>This feature was implemented to retain photos capture date as recorded by google photos. You will first need to check the "Create a Google Photos folder" option in your google drive settings. You can then copy or move the photos locally and use the date the image was taken (created) set as the modification date.</p>
+<p>Useful when downloading data and you want the creation date used in
+place of the last modified date.</p>
+<p><strong>WARNING</strong>: This flag may have some unexpected
+consequences.</p>
+<p>When uploading to your drive all files will be overwritten unless
+they haven't been modified since their creation. And the inverse will
+occur while downloading. This side effect can be avoided by using the
+"--checksum" flag.</p>
+<p>This feature was implemented to retain photos capture date as
+recorded by google photos. You will first need to check the "Create a
+Google Photos folder" option in your google drive settings. You can then
+copy or move the photos locally and use the date the image was taken
+(created) set as the modification date.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_created_date</li>
@@ -23984,8 +35658,10 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-use-shared-date">--drive-use-shared-date</h4>
 <p>Use date file was shared instead of modified date.</p>
-<p>Note that, as with "--drive-use-created-date", this flag may have unexpected consequences when uploading/downloading files.</p>
-<p>If both this flag and "--drive-use-created-date" are set, the created date is used.</p>
+<p>Note that, as with "--drive-use-created-date", this flag may have
+unexpected consequences when uploading/downloading files.</p>
+<p>If both this flag and "--drive-use-created-date" are set, the created
+date is used.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_shared_date</li>
@@ -24023,7 +35699,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <h4 id="drive-chunk-size">--drive-chunk-size</h4>
 <p>Upload chunk size.</p>
 <p>Must a power of 2 &gt;= 256k.</p>
-<p>Making this larger will improve performance, but note that each chunk is buffered in memory one per transfer.</p>
+<p>Making this larger will improve performance, but note that each chunk
+is buffered in memory one per transfer.</p>
 <p>Reducing this will reduce memory usage but decrease performance.</p>
 <p>Properties:</p>
 <ul>
@@ -24033,9 +35710,17 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Default: 8Mi</li>
 </ul>
 <h4 id="drive-acknowledge-abuse">--drive-acknowledge-abuse</h4>
-<p>Set to allow files which return cannotDownloadAbusiveFile to be downloaded.</p>
-<p>If downloading a file returns the error "This file has been identified as malware or spam and cannot be downloaded" with the error code "cannotDownloadAbusiveFile" then supply this flag to rclone to indicate you acknowledge the risks of downloading the file and rclone will download it anyway.</p>
-<p>Note that if you are using service account it will need Manager permission (not Content Manager) to for this flag to work. If the SA does not have the right permission, Google will just ignore the flag.</p>
+<p>Set to allow files which return cannotDownloadAbusiveFile to be
+downloaded.</p>
+<p>If downloading a file returns the error "This file has been
+identified as malware or spam and cannot be downloaded" with the error
+code "cannotDownloadAbusiveFile" then supply this flag to rclone to
+indicate you acknowledge the risks of downloading the file and rclone
+will download it anyway.</p>
+<p>Note that if you are using service account it will need Manager
+permission (not Content Manager) to for this flag to work. If the SA
+does not have the right permission, Google will just ignore the
+flag.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: acknowledge_abuse</li>
@@ -24054,10 +35739,16 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-size-as-quota">--drive-size-as-quota</h4>
 <p>Show sizes as storage quota usage, not actual size.</p>
-<p>Show the size of a file as the storage quota used. This is the current version plus any older versions that have been set to keep forever.</p>
-<p><strong>WARNING</strong>: This flag may have some unexpected consequences.</p>
-<p>It is not recommended to set this flag in your config - the recommended usage is using the flag form --drive-size-as-quota when doing rclone ls/lsl/lsf/lsjson/etc only.</p>
-<p>If you do use this flag for syncing (not recommended) then you will need to use --ignore size also.</p>
+<p>Show the size of a file as the storage quota used. This is the
+current version plus any older versions that have been set to keep
+forever.</p>
+<p><strong>WARNING</strong>: This flag may have some unexpected
+consequences.</p>
+<p>It is not recommended to set this flag in your config - the
+recommended usage is using the flag form --drive-size-as-quota when
+doing rclone ls/lsl/lsf/lsjson/etc only.</p>
+<p>If you do use this flag for syncing (not recommended) then you will
+need to use --ignore size also.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: size_as_quota</li>
@@ -24092,10 +35783,15 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Type: int</li>
 <li>Default: 100</li>
 </ul>
-<h4 id="drive-server-side-across-configs">--drive-server-side-across-configs</h4>
+<h4
+id="drive-server-side-across-configs">--drive-server-side-across-configs</h4>
 <p>Deprecated: use --server-side-across-configs instead.</p>
-<p>Allow server-side operations (e.g. copy) to work across different drive configs.</p>
-<p>This can be useful if you wish to do a server-side copy between two different Google drives. Note that this isn't enabled by default because it isn't easy to tell if it will work between any two configurations.</p>
+<p>Allow server-side operations (e.g. copy) to work across different
+drive configs.</p>
+<p>This can be useful if you wish to do a server-side copy between two
+different Google drives. Note that this isn't enabled by default because
+it isn't easy to tell if it will work between any two
+configurations.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: server_side_across_configs</li>
@@ -24105,7 +35801,10 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-disable-http2">--drive-disable-http2</h4>
 <p>Disable drive using http2.</p>
-<p>There is currently an unsolved issue with the google drive backend and HTTP/2. HTTP/2 is therefore disabled by default for the drive backend but can be re-enabled here. When the issue is solved this flag will be removed.</p>
+<p>There is currently an unsolved issue with the google drive backend
+and HTTP/2. HTTP/2 is therefore disabled by default for the drive
+backend but can be re-enabled here. When the issue is solved this flag
+will be removed.</p>
 <p>See: https://github.com/rclone/rclone/issues/3631</p>
 <p>Properties:</p>
 <ul>
@@ -24116,8 +35815,13 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-stop-on-upload-limit">--drive-stop-on-upload-limit</h4>
 <p>Make upload limit errors be fatal.</p>
-<p>At the time of writing it is only possible to upload 750 GiB of data to Google Drive a day (this is an undocumented limit). When this limit is reached Google Drive produces a slightly different error message. When this flag is set it causes these errors to be fatal. These will stop the in-progress sync.</p>
-<p>Note that this detection is relying on error message strings which Google don't document so it may break in the future.</p>
+<p>At the time of writing it is only possible to upload 750 GiB of data
+to Google Drive a day (this is an undocumented limit). When this limit
+is reached Google Drive produces a slightly different error message.
+When this flag is set it causes these errors to be fatal. These will
+stop the in-progress sync.</p>
+<p>Note that this detection is relying on error message strings which
+Google don't document so it may break in the future.</p>
 <p>See: https://github.com/rclone/rclone/issues/3857</p>
 <p>Properties:</p>
 <ul>
@@ -24126,10 +35830,16 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="drive-stop-on-download-limit">--drive-stop-on-download-limit</h4>
+<h4
+id="drive-stop-on-download-limit">--drive-stop-on-download-limit</h4>
 <p>Make download limit errors be fatal.</p>
-<p>At the time of writing it is only possible to download 10 TiB of data from Google Drive a day (this is an undocumented limit). When this limit is reached Google Drive produces a slightly different error message. When this flag is set it causes these errors to be fatal. These will stop the in-progress sync.</p>
-<p>Note that this detection is relying on error message strings which Google don't document so it may break in the future.</p>
+<p>At the time of writing it is only possible to download 10 TiB of data
+from Google Drive a day (this is an undocumented limit). When this limit
+is reached Google Drive produces a slightly different error message.
+When this flag is set it causes these errors to be fatal. These will
+stop the in-progress sync.</p>
+<p>Note that this detection is relying on error message strings which
+Google don't document so it may break in the future.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: stop_on_download_limit</li>
@@ -24139,7 +35849,10 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-skip-shortcuts">--drive-skip-shortcuts</h4>
 <p>If set skip shortcut files.</p>
-<p>Normally rclone dereferences shortcut files making them appear as if they are the original file (see <a href="#shortcuts">the shortcuts section</a>). If this flag is set then rclone will ignore shortcut files completely.</p>
+<p>Normally rclone dereferences shortcut files making them appear as if
+they are the original file (see <a href="#shortcuts">the shortcuts
+section</a>). If this flag is set then rclone will ignore shortcut files
+completely.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: skip_shortcuts</li>
@@ -24147,9 +35860,11 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="drive-skip-dangling-shortcuts">--drive-skip-dangling-shortcuts</h4>
+<h4
+id="drive-skip-dangling-shortcuts">--drive-skip-dangling-shortcuts</h4>
 <p>If set skip dangling shortcut files.</p>
-<p>If this is set then rclone will not show any dangling shortcuts in listings.</p>
+<p>If this is set then rclone will not show any dangling shortcuts in
+listings.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: skip_dangling_shortcuts</li>
@@ -24161,10 +35876,16 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <p>Resource key for accessing a link-shared file.</p>
 <p>If you need to access files shared with a link like this</p>
 <pre><code>https://drive.google.com/drive/folders/XXX?resourcekey=YYY&amp;usp=sharing</code></pre>
-<p>Then you will need to use the first part "XXX" as the "root_folder_id" and the second part "YYY" as the "resource_key" otherwise you will get 404 not found errors when trying to access the directory.</p>
+<p>Then you will need to use the first part "XXX" as the
+"root_folder_id" and the second part "YYY" as the "resource_key"
+otherwise you will get 404 not found errors when trying to access the
+directory.</p>
 <p>See: https://developers.google.com/drive/api/guides/resource-keys</p>
-<p>This resource key requirement only applies to a subset of old files.</p>
-<p>Note also that opening the folder once in the web interface (with the user you've authenticated rclone with) seems to be enough so that the resource key is not needed.</p>
+<p>This resource key requirement only applies to a subset of old
+files.</p>
+<p>Note also that opening the folder once in the web interface (with the
+user you've authenticated rclone with) seems to be enough so that the
+resource key is not needed.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: resource_key</li>
@@ -24174,10 +35895,19 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-fast-list-bug-fix">--drive-fast-list-bug-fix</h4>
 <p>Work around a bug in Google Drive listing.</p>
-<p>Normally rclone will work around a bug in Google Drive when using --fast-list (ListR) where the search "(A in parents) or (B in parents)" returns nothing sometimes. See #3114, #4289 and https://issuetracker.google.com/issues/149522397</p>
-<p>Rclone detects this by finding no items in more than one directory when listing and retries them as lists of individual directories.</p>
-<p>This means that if you have a lot of empty directories rclone will end up listing them all individually and this can take many more API calls.</p>
-<p>This flag allows the work-around to be disabled. This is <strong>not</strong> recommended in normal use - only if you have a particular case you are having trouble with like many empty directories.</p>
+<p>Normally rclone will work around a bug in Google Drive when using
+--fast-list (ListR) where the search "(A in parents) or (B in parents)"
+returns nothing sometimes. See #3114, #4289 and
+https://issuetracker.google.com/issues/149522397</p>
+<p>Rclone detects this by finding no items in more than one directory
+when listing and retries them as lists of individual directories.</p>
+<p>This means that if you have a lot of empty directories rclone will
+end up listing them all individually and this can take many more API
+calls.</p>
+<p>This flag allows the work-around to be disabled. This is
+<strong>not</strong> recommended in normal use - only if you have a
+particular case you are having trouble with like many empty
+directories.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: fast_list_bug_fix</li>
@@ -24187,8 +35917,12 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-metadata-owner">--drive-metadata-owner</h4>
 <p>Control whether owner should be read or written in metadata.</p>
-<p>Owner is a standard part of the file metadata so is easy to read. But it isn't always desirable to set the owner from the metadata.</p>
-<p>Note that you can't set the owner on Shared Drives, and that setting ownership will generate an email to the new owner (this can't be disabled), and you can't transfer ownership to someone outside your organization.</p>
+<p>Owner is a standard part of the file metadata so is easy to read. But
+it isn't always desirable to set the owner from the metadata.</p>
+<p>Note that you can't set the owner on Shared Drives, and that setting
+ownership will generate an email to the new owner (this can't be
+disabled), and you can't transfer ownership to someone outside your
+organization.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: metadata_owner</li>
@@ -24220,9 +35954,13 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul></li>
 </ul>
 <h4 id="drive-metadata-permissions">--drive-metadata-permissions</h4>
-<p>Control whether permissions should be read or written in metadata.</p>
-<p>Reading permissions metadata from files can be done quickly, but it isn't always desirable to set the permissions from the metadata.</p>
-<p>Note that rclone drops any inherited permissions on Shared Drives and any owner permission on My Drives as these are duplicated in the owner metadata.</p>
+<p>Control whether permissions should be read or written in
+metadata.</p>
+<p>Reading permissions metadata from files can be done quickly, but it
+isn't always desirable to set the permissions from the metadata.</p>
+<p>Note that rclone drops any inherited permissions on Shared Drives and
+any owner permission on My Drives as these are duplicated in the owner
+metadata.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: metadata_permissions</li>
@@ -24255,9 +35993,17 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-metadata-labels">--drive-metadata-labels</h4>
 <p>Control whether labels should be read or written in metadata.</p>
-<p>Reading labels metadata from files takes an extra API transaction and will slow down listings. It isn't always desirable to set the labels from the metadata.</p>
-<p>The format of labels is documented in the drive API documentation at https://developers.google.com/drive/api/reference/rest/v3/Label - rclone just provides a JSON dump of this format.</p>
-<p>When setting labels, the label and fields must already exist - rclone will not create them. This means that if you are transferring labels from two different accounts you will have to create the labels in advance and use the metadata mapper to translate the IDs between the two accounts.</p>
+<p>Reading labels metadata from files takes an extra API transaction and
+will slow down listings. It isn't always desirable to set the labels
+from the metadata.</p>
+<p>The format of labels is documented in the drive API documentation at
+https://developers.google.com/drive/api/reference/rest/v3/Label - rclone
+just provides a JSON dump of this format.</p>
+<p>When setting labels, the label and fields must already exist - rclone
+will not create them. This means that if you are transferring labels
+from two different accounts you will have to create the labels in
+advance and use the metadata mapper to translate the IDs between the two
+accounts.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: metadata_labels</li>
@@ -24290,7 +36036,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </ul>
 <h4 id="drive-encoding">--drive-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -24299,8 +36046,10 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Default: InvalidUtf8</li>
 </ul>
 <h4 id="drive-env-auth">--drive-env-auth</h4>
-<p>Get IAM credentials from runtime (environment variables or instance meta data if no env vars).</p>
-<p>Only applies if service_account_file and service_account_credentials is blank.</p>
+<p>Get IAM credentials from runtime (environment variables or instance
+meta data if no env vars).</p>
+<p>Only applies if service_account_file and service_account_credentials
+is blank.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: env_auth</li>
@@ -24329,9 +36078,11 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-8">Metadata</h3>
-<p>User metadata is stored in the properties field of the drive object.</p>
+<p>User metadata is stored in the properties field of the drive
+object.</p>
 <p>Metadata is supported on files and directories.</p>
-<p>Here are the possible system metadata items for the drive backend.</p>
+<p>Here are the possible system metadata items for the drive
+backend.</p>
 <table>
 <colgroup>
 <col style="width: 15%" />
@@ -24352,7 +36103,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 <tbody>
 <tr class="odd">
 <td>btime</td>
-<td>Time of file birth (creation) with mS accuracy. Note that this is only writable on fresh uploads - it can't be written for updates.</td>
+<td>Time of file birth (creation) with mS accuracy. Note that this is
+only writable on fresh uploads - it can't be written for updates.</td>
 <td>RFC 3339</td>
 <td>2006-01-02T15:04:05.999Z07:00</td>
 <td>N</td>
@@ -24366,7 +36118,8 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </tr>
 <tr class="odd">
 <td>copy-requires-writer-permission</td>
-<td>Whether the options to copy, print, or download this file, should be disabled for readers and commenters.</td>
+<td>Whether the options to copy, print, or download this file, should be
+disabled for readers and commenters.</td>
 <td>boolean</td>
 <td>true</td>
 <td>N</td>
@@ -24380,14 +36133,16 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </tr>
 <tr class="odd">
 <td>folder-color-rgb</td>
-<td>The color for a folder or a shortcut to a folder as an RGB hex string.</td>
+<td>The color for a folder or a shortcut to a folder as an RGB hex
+string.</td>
 <td>string</td>
 <td>881133</td>
 <td>N</td>
 </tr>
 <tr class="even">
 <td>labels</td>
-<td>Labels attached to this file in a JSON dump of Googled drive format. Enable with --drive-metadata-labels.</td>
+<td>Labels attached to this file in a JSON dump of Googled drive format.
+Enable with --drive-metadata-labels.</td>
 <td>JSON</td>
 <td>[]</td>
 <td>N</td>
@@ -24401,14 +36156,17 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </tr>
 <tr class="even">
 <td>owner</td>
-<td>The owner of the file. Usually an email address. Enable with --drive-metadata-owner.</td>
+<td>The owner of the file. Usually an email address. Enable with
+--drive-metadata-owner.</td>
 <td>string</td>
 <td>user@example.com</td>
 <td>N</td>
 </tr>
 <tr class="odd">
 <td>permissions</td>
-<td>Permissions in a JSON dump of Google drive format. On shared drives these will only be present if they aren't inherited. Enable with --drive-metadata-permissions.</td>
+<td>Permissions in a JSON dump of Google drive format. On shared drives
+these will only be present if they aren't inherited. Enable with
+--drive-metadata-permissions.</td>
 <td>JSON</td>
 <td>{}</td>
 <td>N</td>
@@ -24429,25 +36187,32 @@ trashed=false and &#39;c&#39; in parents</code></pre>
 </tr>
 <tr class="even">
 <td>writers-can-share</td>
-<td>Whether users with only writer permission can modify the file's permissions. Not populated and ignored when setting for items in shared drives.</td>
+<td>Whether users with only writer permission can modify the file's
+permissions. Not populated and ignored when setting for items in shared
+drives.</td>
 <td>boolean</td>
 <td>false</td>
 <td>N</td>
 </tr>
 </tbody>
 </table>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h2 id="backend-commands-4">Backend commands</h2>
 <p>Here are the commands specific to the drive backend.</p>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="get">get</h3>
 <p>Get command for fetching the drive config parameters</p>
 <pre><code>rclone backend get remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This is a get command which will be used to fetch the various drive config parameters</p>
+<p>This is a get command which will be used to fetch the various drive
+config parameters</p>
 <p>Usage Examples:</p>
 <pre><code>rclone backend get drive: [-o service_account_file] [-o chunk_size]
 rclone rc backend/command command=get fs=drive: [-o service_account_file] [-o chunk_size]</code></pre>
@@ -24459,7 +36224,8 @@ rclone rc backend/command command=get fs=drive: [-o service_account_file] [-o ch
 <h3 id="set-1">set</h3>
 <p>Set command for updating the drive config parameters</p>
 <pre><code>rclone backend set remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This is a set command which will be used to update the various drive config parameters</p>
+<p>This is a set command which will be used to update the various drive
+config parameters</p>
 <p>Usage Examples:</p>
 <pre><code>rclone backend set drive: [-o service_account_file=sa.json] [-o chunk_size=67108864]
 rclone rc backend/command command=set fs=drive: [-o service_account_file=sa.json] [-o chunk_size=67108864]</code></pre>
@@ -24475,8 +36241,14 @@ rclone rc backend/command command=set fs=drive: [-o service_account_file=sa.json
 <p>Usage:</p>
 <pre><code>rclone backend shortcut drive: source_item destination_shortcut
 rclone backend shortcut drive: source_item -o target=drive2: destination_shortcut</code></pre>
-<p>In the first example this creates a shortcut from the "source_item" which can be a file or a directory to the "destination_shortcut". The "source_item" and the "destination_shortcut" should be relative paths from "drive:"</p>
-<p>In the second example this creates a shortcut from the "source_item" relative to "drive:" to the "destination_shortcut" relative to "drive2:". This may fail with a permission error if the user authenticated with "drive2:" can't read files from "drive:".</p>
+<p>In the first example this creates a shortcut from the "source_item"
+which can be a file or a directory to the "destination_shortcut". The
+"source_item" and the "destination_shortcut" should be relative paths
+from "drive:"</p>
+<p>In the second example this creates a shortcut from the "source_item"
+relative to "drive:" to the "destination_shortcut" relative to
+"drive2:". This may fail with a permission error if the user
+authenticated with "drive2:" can't read files from "drive:".</p>
 <p>Options:</p>
 <ul>
 <li>"target": optional target remote for the shortcut destination</li>
@@ -24484,7 +36256,8 @@ rclone backend shortcut drive: source_item -o target=drive2: destination_shortcu
 <h3 id="drives">drives</h3>
 <p>List the Shared Drives available to this account</p>
 <pre><code>rclone backend drives remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command lists the Shared Drives (Team Drives) available to this account.</p>
+<p>This command lists the Shared Drives (Team Drives) available to this
+account.</p>
 <p>Usage:</p>
 <pre><code>rclone backend [-o config] drives drive:</code></pre>
 <p>This will return a JSON list of objects like this</p>
@@ -24500,7 +36273,9 @@ rclone backend shortcut drive: source_item -o target=drive2: destination_shortcu
         &quot;name&quot;: &quot;Test Drive&quot;
     }
 ]</code></pre>
-<p>With the -o config parameter it will output the list in a format suitable for adding to a config file to make aliases for all the drives found and a combined drive.</p>
+<p>With the -o config parameter it will output the list in a format
+suitable for adding to a config file to make aliases for all the drives
+found and a combined drive.</p>
 <pre><code>[My Drive]
 type = alias
 remote = drive,team_drive=0ABCDEF-01234567890,root_folder_id=:
@@ -24512,16 +36287,23 @@ remote = drive,team_drive=0ABCDEFabcdefghijkl,root_folder_id=:
 [AllDrives]
 type = combine
 upstreams = &quot;My Drive=My Drive:&quot; &quot;Test Drive=Test Drive:&quot;</code></pre>
-<p>Adding this to the rclone config file will cause those team drives to be accessible with the aliases shown. Any illegal characters will be substituted with "_" and duplicate names will have numbers suffixed. It will also add a remote called AllDrives which shows all the shared drives combined into one directory tree.</p>
+<p>Adding this to the rclone config file will cause those team drives to
+be accessible with the aliases shown. Any illegal characters will be
+substituted with "_" and duplicate names will have numbers suffixed. It
+will also add a remote called AllDrives which shows all the shared
+drives combined into one directory tree.</p>
 <h3 id="untrash">untrash</h3>
 <p>Untrash files and directories</p>
 <pre><code>rclone backend untrash remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command untrashes all the files and directories in the directory passed in recursively.</p>
+<p>This command untrashes all the files and directories in the directory
+passed in recursively.</p>
 <p>Usage:</p>
-<p>This takes an optional directory to trash which make this easier to use via the API.</p>
+<p>This takes an optional directory to trash which make this easier to
+use via the API.</p>
 <pre><code>rclone backend untrash drive:directory
 rclone backend --interactive untrash drive:directory subdir</code></pre>
-<p>Use the --interactive/-i or --dry-run flag to see what would be restored before restoring it.</p>
+<p>Use the --interactive/-i or --dry-run flag to see what would be
+restored before restoring it.</p>
 <p>Result:</p>
 <pre><code>{
     &quot;Untrashed&quot;: 17,
@@ -24534,10 +36316,16 @@ rclone backend --interactive untrash drive:directory subdir</code></pre>
 <p>Usage:</p>
 <pre><code>rclone backend copyid drive: ID path
 rclone backend copyid drive: ID1 path1 ID2 path2</code></pre>
-<p>It copies the drive file with ID given to the path (an rclone path which will be passed internally to rclone copyto). The ID and path pairs can be repeated.</p>
-<p>The path should end with a / to indicate copy the file as named to this directory. If it doesn't end with a / then the last path component will be used as the file name.</p>
-<p>If the destination is a drive backend then server-side copying will be attempted if possible.</p>
-<p>Use the --interactive/-i or --dry-run flag to see what would be copied before copying.</p>
+<p>It copies the drive file with ID given to the path (an rclone path
+which will be passed internally to rclone copyto). The ID and path pairs
+can be repeated.</p>
+<p>The path should end with a / to indicate copy the file as named to
+this directory. If it doesn't end with a / then the last path component
+will be used as the file name.</p>
+<p>If the destination is a drive backend then server-side copying will
+be attempted if possible.</p>
+<p>Use the --interactive/-i or --dry-run flag to see what would be
+copied before copying.</p>
 <h3 id="exportformats">exportformats</h3>
 <p>Dump the export formats for debug purposes</p>
 <pre><code>rclone backend exportformats remote: [options] [&lt;arguments&gt;+]</code></pre>
@@ -24550,10 +36338,14 @@ rclone backend copyid drive: ID1 path1 ID2 path2</code></pre>
 <p>This command lists files based on a query</p>
 <p>Usage:</p>
 <pre><code>rclone backend query drive: query</code></pre>
-<p>The query syntax is documented at <a href="https://developers.google.com/drive/api/guides/ref-search-terms">Google Drive Search query terms and operators</a>.</p>
+<p>The query syntax is documented at <a
+href="https://developers.google.com/drive/api/guides/ref-search-terms">Google
+Drive Search query terms and operators</a>.</p>
 <p>For example:</p>
 <pre><code>rclone backend query drive: &quot;&#39;0ABc9DEFGHIJKLMNop0QRatUVW3X&#39; in parents and name contains &#39;foo&#39;&quot;</code></pre>
-<p>If the query contains literal ' or  characters, these need to be escaped with  characters. "'" becomes "'" and "" becomes "\", for example to match a file named "foo ' .txt":</p>
+<p>If the query contains literal ' or  characters, these need to be
+escaped with  characters. "'" becomes "'" and "" becomes "\", for
+example to match a file named "foo ' .txt":</p>
 <pre><code>rclone backend query drive: &quot;name = &#39;foo \&#39; \\\.txt&#39;&quot;</code></pre>
 <p>The result is a JSON array of matches, for example:</p>
 <pre><code>[
@@ -24574,60 +36366,161 @@ rclone backend copyid drive: ID1 path1 ID2 path2</code></pre>
 }
 ]</code></pre>
 <h2 id="limitations-14">Limitations</h2>
-<p>Drive has quite a lot of rate limiting. This causes rclone to be limited to transferring about 2 files per second only. Individual files may be transferred much faster at 100s of MiB/s but lots of small files can take a long time.</p>
-<p>Server side copies are also subject to a separate rate limit. If you see User rate limit exceeded errors, wait at least 24 hours and retry. You can disable server-side copies with <code>--disable copy</code> to download and upload the files if you prefer.</p>
+<p>Drive has quite a lot of rate limiting. This causes rclone to be
+limited to transferring about 2 files per second only. Individual files
+may be transferred much faster at 100s of MiB/s but lots of small files
+can take a long time.</p>
+<p>Server side copies are also subject to a separate rate limit. If you
+see User rate limit exceeded errors, wait at least 24 hours and retry.
+You can disable server-side copies with <code>--disable copy</code> to
+download and upload the files if you prefer.</p>
 <h3 id="limitations-of-google-docs">Limitations of Google Docs</h3>
-<p>Google docs will appear as size -1 in <code>rclone ls</code>, <code>rclone ncdu</code> etc, and as size 0 in anything which uses the VFS layer, e.g. <code>rclone mount</code> and <code>rclone serve</code>. When calculating directory totals, e.g. in <code>rclone size</code> and <code>rclone ncdu</code>, they will be counted in as empty files.</p>
-<p>This is because rclone can't find out the size of the Google docs without downloading them.</p>
-<p>Google docs will transfer correctly with <code>rclone sync</code>, <code>rclone copy</code> etc as rclone knows to ignore the size when doing the transfer.</p>
-<p>However an unfortunate consequence of this is that you may not be able to download Google docs using <code>rclone mount</code>. If it doesn't work you will get a 0 sized file. If you try again the doc may gain its correct size and be downloadable. Whether it will work on not depends on the application accessing the mount and the OS you are running - experiment to find out if it does work for you!</p>
+<p>Google docs will appear as size -1 in <code>rclone ls</code>,
+<code>rclone ncdu</code> etc, and as size 0 in anything which uses the
+VFS layer, e.g. <code>rclone mount</code> and <code>rclone serve</code>.
+When calculating directory totals, e.g. in <code>rclone size</code> and
+<code>rclone ncdu</code>, they will be counted in as empty files.</p>
+<p>This is because rclone can't find out the size of the Google docs
+without downloading them.</p>
+<p>Google docs will transfer correctly with <code>rclone sync</code>,
+<code>rclone copy</code> etc as rclone knows to ignore the size when
+doing the transfer.</p>
+<p>However an unfortunate consequence of this is that you may not be
+able to download Google docs using <code>rclone mount</code>. If it
+doesn't work you will get a 0 sized file. If you try again the doc may
+gain its correct size and be downloadable. Whether it will work on not
+depends on the application accessing the mount and the OS you are
+running - experiment to find out if it does work for you!</p>
 <h3 id="duplicated-files-2">Duplicated files</h3>
-<p>Sometimes, for no reason I've been able to track down, drive will duplicate a file that rclone uploads. Drive unlike all the other remotes can have duplicated files.</p>
-<p>Duplicated files cause problems with the syncing and you will see messages in the log about duplicates.</p>
+<p>Sometimes, for no reason I've been able to track down, drive will
+duplicate a file that rclone uploads. Drive unlike all the other remotes
+can have duplicated files.</p>
+<p>Duplicated files cause problems with the syncing and you will see
+messages in the log about duplicates.</p>
 <p>Use <code>rclone dedupe</code> to fix duplicated files.</p>
-<p>Note that this isn't just a problem with rclone, even Google Photos on Android duplicates files on drive sometimes.</p>
-<h3 id="rclone-appears-to-be-re-copying-files-it-shouldnt">Rclone appears to be re-copying files it shouldn't</h3>
-<p>The most likely cause of this is the duplicated file issue above - run <code>rclone dedupe</code> and check your logs for duplicate object or directory messages.</p>
-<p>This can also be caused by a delay/caching on google drive's end when comparing directory listings. Specifically with team drives used in combination with --fast-list. Files that were uploaded recently may not appear on the directory list sent to rclone when using --fast-list.</p>
-<p>Waiting a moderate period of time between attempts (estimated to be approximately 1 hour) and/or not using --fast-list both seem to be effective in preventing the problem.</p>
-<h3 id="sha1-or-sha256-hashes-may-be-missing">SHA1 or SHA256 hashes may be missing</h3>
-<p>All files have MD5 hashes, but a small fraction of files uploaded may not have SHA1 or SHA256 hashes especially if they were uploaded before 2018.</p>
+<p>Note that this isn't just a problem with rclone, even Google Photos
+on Android duplicates files on drive sometimes.</p>
+<h3 id="rclone-appears-to-be-re-copying-files-it-shouldnt">Rclone
+appears to be re-copying files it shouldn't</h3>
+<p>The most likely cause of this is the duplicated file issue above -
+run <code>rclone dedupe</code> and check your logs for duplicate object
+or directory messages.</p>
+<p>This can also be caused by a delay/caching on google drive's end when
+comparing directory listings. Specifically with team drives used in
+combination with --fast-list. Files that were uploaded recently may not
+appear on the directory list sent to rclone when using --fast-list.</p>
+<p>Waiting a moderate period of time between attempts (estimated to be
+approximately 1 hour) and/or not using --fast-list both seem to be
+effective in preventing the problem.</p>
+<h3 id="sha1-or-sha256-hashes-may-be-missing">SHA1 or SHA256 hashes may
+be missing</h3>
+<p>All files have MD5 hashes, but a small fraction of files uploaded may
+not have SHA1 or SHA256 hashes especially if they were uploaded before
+2018.</p>
 <h2 id="making-your-own-client_id">Making your own client_id</h2>
-<p>When you use rclone with Google drive in its default configuration you are using rclone's client_id. This is shared between all the rclone users. There is a global rate limit on the number of queries per second that each client_id can do set by Google. rclone already has a high quota and I will continue to make sure it is high enough by contacting Google.</p>
-<p>It is strongly recommended to use your own client ID as the default rclone ID is heavily used. If you have multiple services running, it is recommended to use an API key for each service. The default Google quota is 10 transactions per second so it is recommended to stay under that number as if you use more than that, it will cause rclone to rate limit and make things slower.</p>
+<p>When you use rclone with Google drive in its default configuration
+you are using rclone's client_id. This is shared between all the rclone
+users. There is a global rate limit on the number of queries per second
+that each client_id can do set by Google. rclone already has a high
+quota and I will continue to make sure it is high enough by contacting
+Google.</p>
+<p>It is strongly recommended to use your own client ID as the default
+rclone ID is heavily used. If you have multiple services running, it is
+recommended to use an API key for each service. The default Google quota
+is 10 transactions per second so it is recommended to stay under that
+number as if you use more than that, it will cause rclone to rate limit
+and make things slower.</p>
 <p>Here is how to create your own Google Drive client ID for rclone:</p>
 <ol type="1">
-<li><p>Log into the <a href="https://console.developers.google.com/">Google API Console</a> with your Google account. It doesn't matter what Google account you use. (It need not be the same account as the Google Drive you want to access)</p></li>
+<li><p>Log into the <a
+href="https://console.developers.google.com/">Google API Console</a>
+with your Google account. It doesn't matter what Google account you use.
+(It need not be the same account as the Google Drive you want to
+access)</p></li>
 <li><p>Select a project or create a new project.</p></li>
-<li><p>Under "ENABLE APIS AND SERVICES" search for "Drive", and enable the "Google Drive API".</p></li>
-<li><p>Click "Credentials" in the left-side panel (not "Create credentials", which opens the wizard).</p></li>
-<li><p>If you already configured an "Oauth Consent Screen", then skip to the next step; if not, click on "CONFIGURE CONSENT SCREEN" button (near the top right corner of the right panel), then select "External" and click on "CREATE"; on the next screen, enter an "Application name" ("rclone" is OK); enter "User Support Email" (your own email is OK); enter "Developer Contact Email" (your own email is OK); then click on "Save" (all other data is optional). You will also have to add <a href="https://developers.google.com/drive/api/guides/api-specific-auth">some scopes</a>, including</p></li>
+<li><p>Under "ENABLE APIS AND SERVICES" search for "Drive", and enable
+the "Google Drive API".</p></li>
+<li><p>Click "Credentials" in the left-side panel (not "Create
+credentials", which opens the wizard).</p></li>
+<li><p>If you already configured an "Oauth Consent Screen", then skip to
+the next step; if not, click on "CONFIGURE CONSENT SCREEN" button (near
+the top right corner of the right panel), then select "External" and
+click on "CREATE"; on the next screen, enter an "Application name"
+("rclone" is OK); enter "User Support Email" (your own email is OK);
+enter "Developer Contact Email" (your own email is OK); then click on
+"Save" (all other data is optional). You will also have to add <a
+href="https://developers.google.com/drive/api/guides/api-specific-auth">some
+scopes</a>, including</p></li>
 </ol>
 <ul>
 <li><code>https://www.googleapis.com/auth/docs</code></li>
-<li><code>https://www.googleapis.com/auth/drive</code> in order to be able to edit, create and delete files with RClone.</li>
-<li><code>https://www.googleapis.com/auth/drive.metadata.readonly</code> which you may also want to add.</li>
-<li>If you want to add all at once, comma separated it would be <code>https://www.googleapis.com/auth/docs,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.metadata.readonly</code>.</li>
+<li><code>https://www.googleapis.com/auth/drive</code> in order to be
+able to edit, create and delete files with RClone.</li>
+<li><code>https://www.googleapis.com/auth/drive.metadata.readonly</code>
+which you may also want to add.</li>
+<li>If you want to add all at once, comma separated it would be
+<code>https://www.googleapis.com/auth/docs,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.metadata.readonly</code>.</li>
 </ul>
 <ol start="6" type="1">
-<li><p>After adding scopes, click "Save and continue" to add test users. Be sure to add your own account to the test users. Once you've added yourself as a test user and saved the changes, click again on "Credentials" on the left panel to go back to the "Credentials" screen.</p>
-<p>(PS: if you are a GSuite user, you could also select "Internal" instead of "External" above, but this will restrict API use to Google Workspace users in your organisation).</p></li>
-<li><p>Click on the "+ CREATE CREDENTIALS" button at the top of the screen, then select "OAuth client ID".</p></li>
-<li><p>Choose an application type of "Desktop app" and click "Create". (the default name is fine)</p></li>
-<li><p>It will show you a client ID and client secret. Make a note of these.</p>
-<p>(If you selected "External" at Step 5 continue to Step 10. If you chose "Internal" you don't need to publish and can skip straight to Step 11 but your destination drive must be part of the same Google Workspace.)</p></li>
-<li><p>Go to "Oauth consent screen" and then click "PUBLISH APP" button and confirm. You will also want to add yourself as a test user.</p></li>
+<li><p>After adding scopes, click "Save and continue" to add test users.
+Be sure to add your own account to the test users. Once you've added
+yourself as a test user and saved the changes, click again on
+"Credentials" on the left panel to go back to the "Credentials"
+screen.</p>
+<p>(PS: if you are a GSuite user, you could also select "Internal"
+instead of "External" above, but this will restrict API use to Google
+Workspace users in your organisation).</p></li>
+<li><p>Click on the "+ CREATE CREDENTIALS" button at the top of the
+screen, then select "OAuth client ID".</p></li>
+<li><p>Choose an application type of "Desktop app" and click "Create".
+(the default name is fine)</p></li>
+<li><p>It will show you a client ID and client secret. Make a note of
+these.</p>
+<p>(If you selected "External" at Step 5 continue to Step 10. If you
+chose "Internal" you don't need to publish and can skip straight to Step
+11 but your destination drive must be part of the same Google
+Workspace.)</p></li>
+<li><p>Go to "Oauth consent screen" and then click "PUBLISH APP" button
+and confirm. You will also want to add yourself as a test user.</p></li>
 <li><p>Provide the noted client ID and client secret to rclone.</p></li>
 </ol>
-<p>Be aware that, due to the "enhanced security" recently introduced by Google, you are theoretically expected to "submit your app for verification" and then wait a few weeks(!) for their response; in practice, you can go right ahead and use the client ID and client secret with rclone, the only issue will be a very scary confirmation screen shown when you connect via your browser for rclone to be able to get its token-id (but as this only happens during the remote configuration, it's not such a big deal). Keeping the application in "Testing" will work as well, but the limitation is that any grants will expire after a week, which can be annoying to refresh constantly. If, for whatever reason, a short grant time is not a problem, then keeping the application in testing mode would also be sufficient.</p>
-<p>(Thanks to <span class="citation" data-cites="balazer">@balazer</span> on github for these instructions.)</p>
-<p>Sometimes, creation of an OAuth consent in Google API Console fails due to an error message “The request failed because changes to one of the field of the resource is not supported”. As a convenient workaround, the necessary Google Drive API key can be created on the <a href="https://developers.google.com/drive/api/v3/quickstart/python">Python Quickstart</a> page. Just push the Enable the Drive API button to receive the Client ID and Secret. Note that it will automatically create a new project in the API Console.</p>
+<p>Be aware that, due to the "enhanced security" recently introduced by
+Google, you are theoretically expected to "submit your app for
+verification" and then wait a few weeks(!) for their response; in
+practice, you can go right ahead and use the client ID and client secret
+with rclone, the only issue will be a very scary confirmation screen
+shown when you connect via your browser for rclone to be able to get its
+token-id (but as this only happens during the remote configuration, it's
+not such a big deal). Keeping the application in "Testing" will work as
+well, but the limitation is that any grants will expire after a week,
+which can be annoying to refresh constantly. If, for whatever reason, a
+short grant time is not a problem, then keeping the application in
+testing mode would also be sufficient.</p>
+<p>(Thanks to <span class="citation"
+data-cites="balazer">@balazer</span> on github for these
+instructions.)</p>
+<p>Sometimes, creation of an OAuth consent in Google API Console fails
+due to an error message “The request failed because changes to one of
+the field of the resource is not supported”. As a convenient workaround,
+the necessary Google Drive API key can be created on the <a
+href="https://developers.google.com/drive/api/v3/quickstart/python">Python
+Quickstart</a> page. Just push the Enable the Drive API button to
+receive the Client ID and Secret. Note that it will automatically create
+a new project in the API Console.</p>
 <h1 id="google-photos">Google Photos</h1>
-<p>The rclone backend for <a href="https://www.google.com/photos/about/">Google Photos</a> is a specialized backend for transferring photos and videos to and from Google Photos.</p>
-<p><strong>NB</strong> The Google Photos API which rclone uses has quite a few limitations, so please read the <a href="#limitations">limitations section</a> carefully to make sure it is suitable for your use.</p>
-<h2 id="configuration-18">Configuration</h2>
-<p>The initial setup for google cloud storage involves getting a token from Google Photos which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>The rclone backend for <a
+href="https://www.google.com/photos/about/">Google Photos</a> is a
+specialized backend for transferring photos and videos to and from
+Google Photos.</p>
+<p><strong>NB</strong> The Google Photos API which rclone uses has quite
+a few limitations, so please read the <a href="#limitations">limitations
+section</a> carefully to make sure it is suitable for your use.</p>
+<h2 id="configuration-19">Configuration</h2>
+<p>The initial setup for google cloud storage involves getting a token
+from Google Photos which you need to do in your browser.
+<code>rclone config</code> walks you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -24690,21 +36583,39 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Google if using web browser to automatically authenticate. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
-<p>This remote is called <code>remote</code> and can now be used like this</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from Google if using web browser to automatically
+authenticate. This only runs from the moment it opens your browser to
+the moment you get back the verification code. This is on
+<code>http://127.0.0.1:53682/</code> and this may require you to unblock
+it temporarily if you are running a host firewall, or use manual
+mode.</p>
+<p>This remote is called <code>remote</code> and can now be used like
+this</p>
 <p>See all the albums in your photos</p>
 <pre><code>rclone lsd remote:album</code></pre>
 <p>Make a new album</p>
 <pre><code>rclone mkdir remote:album/newAlbum</code></pre>
 <p>List the contents of an album</p>
 <pre><code>rclone ls remote:album/newAlbum</code></pre>
-<p>Sync <code>/home/local/images</code> to the Google Photos, removing any excess files in the album.</p>
+<p>Sync <code>/home/local/images</code> to the Google Photos, removing
+any excess files in the album.</p>
 <pre><code>rclone sync --interactive /home/local/image remote:album/newAlbum</code></pre>
 <h3 id="layout">Layout</h3>
-<p>As Google Photos is not a general purpose cloud storage system, the backend is laid out to help you navigate it.</p>
-<p>The directories under <code>media</code> show different ways of categorizing the media. Each file will appear multiple times. So if you want to make a backup of your google photos you might choose to backup <code>remote:media/by-month</code>. (<strong>NB</strong> <code>remote:media/by-day</code> is rather slow at the moment so avoid for syncing.)</p>
-<p>Note that all your photos and videos will appear somewhere under <code>media</code>, but they may not appear under <code>album</code> unless you've put them into albums.</p>
+<p>As Google Photos is not a general purpose cloud storage system, the
+backend is laid out to help you navigate it.</p>
+<p>The directories under <code>media</code> show different ways of
+categorizing the media. Each file will appear multiple times. So if you
+want to make a backup of your google photos you might choose to backup
+<code>remote:media/by-month</code>. (<strong>NB</strong>
+<code>remote:media/by-day</code> is rather slow at the moment so avoid
+for syncing.)</p>
+<p>Note that all your photos and videos will appear somewhere under
+<code>media</code>, but they may not appear under <code>album</code>
+unless you've put them into albums.</p>
 <pre><code>/
 - upload
     - file1.jpg
@@ -24751,9 +36662,20 @@ y/e/d&gt; y</code></pre>
     - favorites
         - file1.jpg
         - file2.jpg</code></pre>
-<p>There are two writable parts of the tree, the <code>upload</code> directory and sub directories of the <code>album</code> directory.</p>
-<p>The <code>upload</code> directory is for uploading files you don't want to put into albums. This will be empty to start with and will contain the files you've uploaded for one rclone session only, becoming empty again when you restart rclone. The use case for this would be if you have a load of files you just want to once off dump into Google Photos. For repeated syncing, uploading to <code>album</code> will work better.</p>
-<p>Directories within the <code>album</code> directory are also writeable and you may create new directories (albums) under <code>album</code>. If you copy files with a directory hierarchy in there then rclone will create albums with the <code>/</code> character in them. For example if you do</p>
+<p>There are two writable parts of the tree, the <code>upload</code>
+directory and sub directories of the <code>album</code> directory.</p>
+<p>The <code>upload</code> directory is for uploading files you don't
+want to put into albums. This will be empty to start with and will
+contain the files you've uploaded for one rclone session only, becoming
+empty again when you restart rclone. The use case for this would be if
+you have a load of files you just want to once off dump into Google
+Photos. For repeated syncing, uploading to <code>album</code> will work
+better.</p>
+<p>Directories within the <code>album</code> directory are also
+writeable and you may create new directories (albums) under
+<code>album</code>. If you copy files with a directory hierarchy in
+there then rclone will create albums with the <code>/</code> character
+in them. For example if you do</p>
 <pre><code>rclone copy /path/to/images remote:album/images</code></pre>
 <p>and the images directory contains</p>
 <pre><code>images
@@ -24763,7 +36685,8 @@ y/e/d&gt; y</code></pre>
     dir2
         dir3
             file3.jpg</code></pre>
-<p>Then rclone will create the following albums with the following files in</p>
+<p>Then rclone will create the following albums with the following files
+in</p>
 <ul>
 <li>images
 <ul>
@@ -24778,10 +36701,15 @@ y/e/d&gt; y</code></pre>
 <li>file3.jpg</li>
 </ul></li>
 </ul>
-<p>This means that you can use the <code>album</code> path pretty much like a normal filesystem and it is a good target for repeated syncing.</p>
-<p>The <code>shared-album</code> directory shows albums shared with you or by you. This is similar to the Sharing tab in the Google Photos web interface.</p>
-<h3 id="standard-options-18">Standard options</h3>
-<p>Here are the Standard options specific to google photos (Google Photos).</p>
+<p>This means that you can use the <code>album</code> path pretty much
+like a normal filesystem and it is a good target for repeated
+syncing.</p>
+<p>The <code>shared-album</code> directory shows albums shared with you
+or by you. This is similar to the Sharing tab in the Google Photos web
+interface.</p>
+<h3 id="standard-options-19">Standard options</h3>
+<p>Here are the Standard options specific to google photos (Google
+Photos).</p>
 <h4 id="gphotos-client-id">--gphotos-client-id</h4>
 <p>OAuth Client Id.</p>
 <p>Leave blank normally.</p>
@@ -24804,7 +36732,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gphotos-read-only">--gphotos-read-only</h4>
 <p>Set to make the Google Photos backend read only.</p>
-<p>If you choose read only then rclone will only request read only access to your photos, otherwise rclone will request full access.</p>
+<p>If you choose read only then rclone will only request read only
+access to your photos, otherwise rclone will request full access.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: read_only</li>
@@ -24812,8 +36741,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="advanced-options-18">Advanced options</h3>
-<p>Here are the Advanced options specific to google photos (Google Photos).</p>
+<h3 id="advanced-options-19">Advanced options</h3>
+<p>Here are the Advanced options specific to google photos (Google
+Photos).</p>
 <h4 id="gphotos-token">--gphotos-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
 <p>Properties:</p>
@@ -24845,7 +36775,11 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gphotos-read-size">--gphotos-read-size</h4>
 <p>Set to read the size of media items.</p>
-<p>Normally rclone does not read the size of media items since this takes another transaction. This isn't necessary for syncing. However rclone mount needs to know the size of files in advance of reading them, so setting this flag when using rclone mount is recommended if you want to read the media.</p>
+<p>Normally rclone does not read the size of media items since this
+takes another transaction. This isn't necessary for syncing. However
+rclone mount needs to know the size of files in advance of reading them,
+so setting this flag when using rclone mount is recommended if you want
+to read the media.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: read_size</li>
@@ -24854,7 +36788,8 @@ y/e/d&gt; y</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="gphotos-start-year">--gphotos-start-year</h4>
-<p>Year limits the photos to be downloaded to those which are uploaded after the given year.</p>
+<p>Year limits the photos to be downloaded to those which are uploaded
+after the given year.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: start_year</li>
@@ -24864,10 +36799,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gphotos-include-archived">--gphotos-include-archived</h4>
 <p>Also view and download archived media.</p>
-<p>By default, rclone does not request archived media. Thus, when syncing, archived media is not visible in directory listings or transferred.</p>
-<p>Note that media in albums is always visible and synced, no matter their archive status.</p>
-<p>With this flag, archived media are always visible in directory listings and transferred.</p>
-<p>Without this flag, archived media will not be visible in directory listings and won't be transferred.</p>
+<p>By default, rclone does not request archived media. Thus, when
+syncing, archived media is not visible in directory listings or
+transferred.</p>
+<p>Note that media in albums is always visible and synced, no matter
+their archive status.</p>
+<p>With this flag, archived media are always visible in directory
+listings and transferred.</p>
+<p>Without this flag, archived media will not be visible in directory
+listings and won't be transferred.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: include_archived</li>
@@ -24877,7 +36817,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gphotos-encoding">--gphotos-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -24894,7 +36835,8 @@ y/e/d&gt; y</code></pre>
 <li>sync - batch uploads and check completion (default)</li>
 <li>async - batch upload and don't check completion</li>
 </ul>
-<p>Rclone will close any outstanding batches when it exits which may make a delay on quit.</p>
+<p>Rclone will close any outstanding batches when it exits which may
+make a delay on quit.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: batch_mode</li>
@@ -24904,15 +36846,21 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gphotos-batch-size">--gphotos-batch-size</h4>
 <p>Max number of files in upload batch.</p>
-<p>This sets the batch size of files to upload. It has to be less than 50.</p>
-<p>By default this is 0 which means rclone will calculate the batch size depending on the setting of batch_mode.</p>
+<p>This sets the batch size of files to upload. It has to be less than
+50.</p>
+<p>By default this is 0 which means rclone will calculate the batch size
+depending on the setting of batch_mode.</p>
 <ul>
 <li>batch_mode: async - default batch_size is 50</li>
-<li>batch_mode: sync - default batch_size is the same as --transfers</li>
+<li>batch_mode: sync - default batch_size is the same as
+--transfers</li>
 <li>batch_mode: off - not in use</li>
 </ul>
-<p>Rclone will close any outstanding batches when it exits which may make a delay on quit.</p>
-<p>Setting this is a great idea if you are uploading lots of small files as it will make them a lot quicker. You can use --transfers 32 to maximise throughput.</p>
+<p>Rclone will close any outstanding batches when it exits which may
+make a delay on quit.</p>
+<p>Setting this is a great idea if you are uploading lots of small files
+as it will make them a lot quicker. You can use --transfers 32 to
+maximise throughput.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: batch_size</li>
@@ -24922,8 +36870,10 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="gphotos-batch-timeout">--gphotos-batch-timeout</h4>
 <p>Max time to allow an idle upload batch before uploading.</p>
-<p>If an upload batch is idle for more than this long then it will be uploaded.</p>
-<p>The default for this is 0 which means rclone will choose a sensible default based on the batch_mode in use.</p>
+<p>If an upload batch is idle for more than this long then it will be
+uploaded.</p>
+<p>The default for this is 0 which means rclone will choose a sensible
+default based on the batch_mode in use.</p>
 <ul>
 <li>batch_mode: async - default batch_timeout is 10s</li>
 <li>batch_mode: sync - default batch_timeout is 1s</li>
@@ -24936,7 +36886,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: Duration</li>
 <li>Default: 0s</li>
 </ul>
-<h4 id="gphotos-batch-commit-timeout">--gphotos-batch-commit-timeout</h4>
+<h4
+id="gphotos-batch-commit-timeout">--gphotos-batch-commit-timeout</h4>
 <p>Max time to wait for a batch to finish committing</p>
 <p>Properties:</p>
 <ul>
@@ -24955,38 +36906,107 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-15">Limitations</h2>
-<p>Only images and videos can be uploaded. If you attempt to upload non videos or images or formats that Google Photos doesn't understand, rclone will upload the file, then Google Photos will give an error when it is put turned into a media item.</p>
-<p>Note that all media items uploaded to Google Photos through the API are stored in full resolution at "original quality" and <strong>will</strong> count towards your storage quota in your Google Account. The API does <strong>not</strong> offer a way to upload in "high quality" mode..</p>
-<p><code>rclone about</code> is not supported by the Google Photos backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> See <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p>Only images and videos can be uploaded. If you attempt to upload non
+videos or images or formats that Google Photos doesn't understand,
+rclone will upload the file, then Google Photos will give an error when
+it is put turned into a media item.</p>
+<p>Note that all media items uploaded to Google Photos through the API
+are stored in full resolution at "original quality" and
+<strong>will</strong> count towards your storage quota in your Google
+Account. The API does <strong>not</strong> offer a way to upload in
+"high quality" mode..</p>
+<p><code>rclone about</code> is not supported by the Google Photos
+backend. Backends without this capability cannot determine free space
+for an rclone mount or use policy <code>mfs</code> (most free space) as
+a member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> See <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h3 id="downloading-images">Downloading Images</h3>
-<p>When Images are downloaded this strips EXIF location (according to the docs and my tests). This is a limitation of the Google Photos API and is covered by <a href="https://issuetracker.google.com/issues/112096115">bug #112096115</a>.</p>
-<p><strong>The current google API does not allow photos to be downloaded at original resolution. This is very important if you are, for example, relying on "Google Photos" as a backup of your photos. You will not be able to use rclone to redownload original images. You could use 'google takeout' to recover the original photos as a last resort</strong></p>
+<p>When Images are downloaded this strips EXIF location (according to
+the docs and my tests). This is a limitation of the Google Photos API
+and is covered by <a
+href="https://issuetracker.google.com/issues/112096115">bug
+#112096115</a>.</p>
+<p><strong>The current google API does not allow photos to be downloaded
+at original resolution. This is very important if you are, for example,
+relying on "Google Photos" as a backup of your photos. You will not be
+able to use rclone to redownload original images. You could use 'google
+takeout' to recover the original photos as a last resort</strong></p>
 <h3 id="downloading-videos">Downloading Videos</h3>
-<p>When videos are downloaded they are downloaded in a really compressed version of the video compared to downloading it via the Google Photos web interface. This is covered by <a href="https://issuetracker.google.com/issues/113672044">bug #113672044</a>.</p>
+<p>When videos are downloaded they are downloaded in a really compressed
+version of the video compared to downloading it via the Google Photos
+web interface. This is covered by <a
+href="https://issuetracker.google.com/issues/113672044">bug
+#113672044</a>.</p>
 <h3 id="duplicates">Duplicates</h3>
-<p>If a file name is duplicated in a directory then rclone will add the file ID into its name. So two files called <code>file.jpg</code> would then appear as <code>file {123456}.jpg</code> and <code>file {ABCDEF}.jpg</code> (the actual IDs are a lot longer alas!).</p>
-<p>If you upload the same image (with the same binary data) twice then Google Photos will deduplicate it. However it will retain the filename from the first upload which may confuse rclone. For example if you uploaded an image to <code>upload</code> then uploaded the same image to <code>album/my_album</code> the filename of the image in <code>album/my_album</code> will be what it was uploaded with initially, not what you uploaded it with to <code>album</code>. In practise this shouldn't cause too many problems.</p>
+<p>If a file name is duplicated in a directory then rclone will add the
+file ID into its name. So two files called <code>file.jpg</code> would
+then appear as <code>file {123456}.jpg</code> and
+<code>file {ABCDEF}.jpg</code> (the actual IDs are a lot longer
+alas!).</p>
+<p>If you upload the same image (with the same binary data) twice then
+Google Photos will deduplicate it. However it will retain the filename
+from the first upload which may confuse rclone. For example if you
+uploaded an image to <code>upload</code> then uploaded the same image to
+<code>album/my_album</code> the filename of the image in
+<code>album/my_album</code> will be what it was uploaded with initially,
+not what you uploaded it with to <code>album</code>. In practise this
+shouldn't cause too many problems.</p>
 <h3 id="modification-times-6">Modification times</h3>
-<p>The date shown of media in Google Photos is the creation date as determined by the EXIF information, or the upload date if that is not known.</p>
-<p>This is not changeable by rclone and is not the modification date of the media on local disk. This means that rclone cannot use the dates from Google Photos for syncing purposes.</p>
+<p>The date shown of media in Google Photos is the creation date as
+determined by the EXIF information, or the upload date if that is not
+known.</p>
+<p>This is not changeable by rclone and is not the modification date of
+the media on local disk. This means that rclone cannot use the dates
+from Google Photos for syncing purposes.</p>
 <h3 id="size">Size</h3>
-<p>The Google Photos API does not return the size of media. This means that when syncing to Google Photos, rclone can only do a file existence check.</p>
-<p>It is possible to read the size of the media, but this needs an extra HTTP HEAD request per media item so is <strong>very slow</strong> and uses up a lot of transactions. This can be enabled with the <code>--gphotos-read-size</code> option or the <code>read_size = true</code> config parameter.</p>
-<p>If you want to use the backend with <code>rclone mount</code> you may need to enable this flag (depending on your OS and application using the photos) otherwise you may not be able to read media off the mount. You'll need to experiment to see if it works for you without the flag.</p>
+<p>The Google Photos API does not return the size of media. This means
+that when syncing to Google Photos, rclone can only do a file existence
+check.</p>
+<p>It is possible to read the size of the media, but this needs an extra
+HTTP HEAD request per media item so is <strong>very slow</strong> and
+uses up a lot of transactions. This can be enabled with the
+<code>--gphotos-read-size</code> option or the
+<code>read_size = true</code> config parameter.</p>
+<p>If you want to use the backend with <code>rclone mount</code> you may
+need to enable this flag (depending on your OS and application using the
+photos) otherwise you may not be able to read media off the mount.
+You'll need to experiment to see if it works for you without the
+flag.</p>
 <h3 id="albums">Albums</h3>
-<p>Rclone can only upload files to albums it created. This is a <a href="https://developers.google.com/photos/library/guides/manage-albums">limitation of the Google Photos API</a>.</p>
+<p>Rclone can only upload files to albums it created. This is a <a
+href="https://developers.google.com/photos/library/guides/manage-albums">limitation
+of the Google Photos API</a>.</p>
 <p>Rclone can remove files it uploaded from albums it created only.</p>
 <h3 id="deleting-files-2">Deleting files</h3>
-<p>Rclone can remove files from albums it created, but note that the Google Photos API does not allow media to be deleted permanently so this media will still remain. See <a href="https://issuetracker.google.com/issues/109759781">bug #109759781</a>.</p>
-<p>Rclone cannot delete files anywhere except under <code>album</code>.</p>
+<p>Rclone can remove files from albums it created, but note that the
+Google Photos API does not allow media to be deleted permanently so this
+media will still remain. See <a
+href="https://issuetracker.google.com/issues/109759781">bug
+#109759781</a>.</p>
+<p>Rclone cannot delete files anywhere except under
+<code>album</code>.</p>
 <h3 id="deleting-albums">Deleting albums</h3>
-<p>The Google Photos API does not support deleting albums - see <a href="https://issuetracker.google.com/issues/135714733">bug #135714733</a>.</p>
+<p>The Google Photos API does not support deleting albums - see <a
+href="https://issuetracker.google.com/issues/135714733">bug
+#135714733</a>.</p>
 <h1 id="hasher">Hasher</h1>
-<p>Hasher is a special overlay backend to create remotes which handle checksums for other remotes. It's main functions include: - Emulate hash types unimplemented by backends - Cache checksums to help with slow hashing of large local or (S)FTP files - Warm up checksum cache from external SUM files</p>
+<p>Hasher is a special overlay backend to create remotes which handle
+checksums for other remotes. It's main functions include: - Emulate hash
+types unimplemented by backends - Cache checksums to help with slow
+hashing of large local or (S)FTP files - Warm up checksum cache from
+external SUM files</p>
 <h2 id="getting-started-1">Getting started</h2>
-<p>To use Hasher, first set up the underlying remote following the configuration instructions for that remote. You can also use a local pathname instead of a remote. Check that your base remote is working.</p>
-<p>Let's call the base remote <code>myRemote:path</code> here. Note that anything inside <code>myRemote:path</code> will be handled by hasher and anything outside won't. This means that if you are using a bucket based remote (S3, B2, Swift) then you should put the bucket in the remote <code>s3:bucket</code>.</p>
+<p>To use Hasher, first set up the underlying remote following the
+configuration instructions for that remote. You can also use a local
+pathname instead of a remote. Check that your base remote is
+working.</p>
+<p>Let's call the base remote <code>myRemote:path</code> here. Note that
+anything inside <code>myRemote:path</code> will be handled by hasher and
+anything outside won't. This means that if you are using a bucket based
+remote (S3, B2, Swift) then you should put the bucket in the remote
+<code>s3:bucket</code>.</p>
 <p>Now proceed to interactive or manual configuration.</p>
 <h3 id="interactive-configuration">Interactive configuration</h3>
 <p>Run <code>rclone config</code>:</p>
@@ -25028,7 +37048,10 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
 <h3 id="manual-configuration">Manual configuration</h3>
-<p>Run <code>rclone config path</code> to see the path of current active config file, usually <code>YOURHOME/.config/rclone/rclone.conf</code>. Open it in your favorite text editor, find section for the base remote and create new section for hasher like in the following examples:</p>
+<p>Run <code>rclone config path</code> to see the path of current active
+config file, usually <code>YOURHOME/.config/rclone/rclone.conf</code>.
+Open it in your favorite text editor, find section for the base remote
+and create new section for hasher like in the following examples:</p>
 <pre><code>[Hasher1]
 type = hasher
 remote = myRemote:path
@@ -25040,31 +37063,73 @@ type = hasher
 remote = /local/path
 hashes = dropbox,sha1
 max_age = 24h</code></pre>
-<p>Hasher takes basically the following parameters: - <code>remote</code> is required, - <code>hashes</code> is a comma separated list of supported checksums (by default <code>md5,sha1</code>), - <code>max_age</code> - maximum time to keep a checksum value in the cache, <code>0</code> will disable caching completely, <code>off</code> will cache "forever" (that is until the files get changed).</p>
-<p>Make sure the <code>remote</code> has <code>:</code> (colon) in. If you specify the remote without a colon then rclone will use a local directory of that name. So if you use a remote of <code>/local/path</code> then rclone will handle hashes for that directory. If you use <code>remote = name</code> literally then rclone will put files <strong>in a directory called <code>name</code> located under current directory</strong>.</p>
+<p>Hasher takes basically the following parameters: -
+<code>remote</code> is required, - <code>hashes</code> is a comma
+separated list of supported checksums (by default
+<code>md5,sha1</code>), - <code>max_age</code> - maximum time to keep a
+checksum value in the cache, <code>0</code> will disable caching
+completely, <code>off</code> will cache "forever" (that is until the
+files get changed).</p>
+<p>Make sure the <code>remote</code> has <code>:</code> (colon) in. If
+you specify the remote without a colon then rclone will use a local
+directory of that name. So if you use a remote of
+<code>/local/path</code> then rclone will handle hashes for that
+directory. If you use <code>remote = name</code> literally then rclone
+will put files <strong>in a directory called <code>name</code> located
+under current directory</strong>.</p>
 <h2 id="usage-1">Usage</h2>
 <h3 id="basic-operations">Basic operations</h3>
-<p>Now you can use it as <code>Hasher2:subdir/file</code> instead of base remote. Hasher will transparently update cache with new checksums when a file is fully read or overwritten, like:</p>
+<p>Now you can use it as <code>Hasher2:subdir/file</code> instead of
+base remote. Hasher will transparently update cache with new checksums
+when a file is fully read or overwritten, like:</p>
 <pre><code>rclone copy External:path/file Hasher:dest/path
 
 rclone cat Hasher:path/to/file &gt; /dev/null</code></pre>
-<p>The way to refresh <strong>all</strong> cached checksums (even unsupported by the base backend) for a subtree is to <strong>re-download</strong> all files in the subtree. For example, use <code>hashsum --download</code> using <strong>any</strong> supported hashsum on the command line (we just care to re-read):</p>
+<p>The way to refresh <strong>all</strong> cached checksums (even
+unsupported by the base backend) for a subtree is to
+<strong>re-download</strong> all files in the subtree. For example, use
+<code>hashsum --download</code> using <strong>any</strong> supported
+hashsum on the command line (we just care to re-read):</p>
 <pre><code>rclone hashsum MD5 --download Hasher:path/to/subtree &gt; /dev/null
 
 rclone backend dump Hasher:path/to/subtree</code></pre>
-<p>You can print or drop hashsum cache using custom backend commands:</p>
+<p>You can print or drop hashsum cache using custom backend
+commands:</p>
 <pre><code>rclone backend dump Hasher:dir/subdir
 
 rclone backend drop Hasher:</code></pre>
 <h3 id="pre-seed-from-a-sum-file">Pre-Seed from a SUM File</h3>
-<p>Hasher supports two backend commands: generic SUM file <code>import</code> and faster but less consistent <code>stickyimport</code>.</p>
+<p>Hasher supports two backend commands: generic SUM file
+<code>import</code> and faster but less consistent
+<code>stickyimport</code>.</p>
 <pre><code>rclone backend import Hasher:dir/subdir SHA1 /path/to/SHA1SUM [--checkers 4]</code></pre>
-<p>Instead of SHA1 it can be any hash supported by the remote. The last argument can point to either a local or an <code>other-remote:path</code> text file in SUM format. The command will parse the SUM file, then walk down the path given by the first argument, snapshot current fingerprints and fill in the cache entries correspondingly. - Paths in the SUM file are treated as relative to <code>hasher:dir/subdir</code>. - The command will <strong>not</strong> check that supplied values are correct. You <strong>must know</strong> what you are doing. - This is a one-time action. The SUM file will not get "attached" to the remote. Cache entries can still be overwritten later, should the object's fingerprint change. - The tree walk can take long depending on the tree size. You can increase <code>--checkers</code> to make it faster. Or use <code>stickyimport</code> if you don't care about fingerprints and consistency.</p>
+<p>Instead of SHA1 it can be any hash supported by the remote. The last
+argument can point to either a local or an
+<code>other-remote:path</code> text file in SUM format. The command will
+parse the SUM file, then walk down the path given by the first argument,
+snapshot current fingerprints and fill in the cache entries
+correspondingly. - Paths in the SUM file are treated as relative to
+<code>hasher:dir/subdir</code>. - The command will <strong>not</strong>
+check that supplied values are correct. You <strong>must know</strong>
+what you are doing. - This is a one-time action. The SUM file will not
+get "attached" to the remote. Cache entries can still be overwritten
+later, should the object's fingerprint change. - The tree walk can take
+long depending on the tree size. You can increase
+<code>--checkers</code> to make it faster. Or use
+<code>stickyimport</code> if you don't care about fingerprints and
+consistency.</p>
 <pre><code>rclone backend stickyimport hasher:path/to/data sha1 remote:/path/to/sum.sha1</code></pre>
-<p><code>stickyimport</code> is similar to <code>import</code> but works much faster because it does not need to stat existing files and skips initial tree walk. Instead of binding cache entries to file fingerprints it creates <em>sticky</em> entries bound to the file name alone ignoring size, modification time etc. Such hash entries can be replaced only by <code>purge</code>, <code>delete</code>, <code>backend drop</code> or by full re-read/re-write of the files.</p>
+<p><code>stickyimport</code> is similar to <code>import</code> but works
+much faster because it does not need to stat existing files and skips
+initial tree walk. Instead of binding cache entries to file fingerprints
+it creates <em>sticky</em> entries bound to the file name alone ignoring
+size, modification time etc. Such hash entries can be replaced only by
+<code>purge</code>, <code>delete</code>, <code>backend drop</code> or by
+full re-read/re-write of the files.</p>
 <h2 id="configuration-reference">Configuration reference</h2>
-<h3 id="standard-options-19">Standard options</h3>
-<p>Here are the Standard options specific to hasher (Better checksums for other remotes).</p>
+<h3 id="standard-options-20">Standard options</h3>
+<p>Here are the Standard options specific to hasher (Better checksums
+for other remotes).</p>
 <h4 id="hasher-remote">--hasher-remote</h4>
 <p>Remote to cache checksums for (e.g. myRemote:path).</p>
 <p>Properties:</p>
@@ -25084,7 +37149,8 @@ rclone backend drop Hasher:</code></pre>
 <li>Default: md5,sha1</li>
 </ul>
 <h4 id="hasher-max-age">--hasher-max-age</h4>
-<p>Maximum time to keep checksums in cache (0 = no cache, off = cache forever).</p>
+<p>Maximum time to keep checksums in cache (0 = no cache, off = cache
+forever).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: max_age</li>
@@ -25092,10 +37158,12 @@ rclone backend drop Hasher:</code></pre>
 <li>Type: Duration</li>
 <li>Default: off</li>
 </ul>
-<h3 id="advanced-options-19">Advanced options</h3>
-<p>Here are the Advanced options specific to hasher (Better checksums for other remotes).</p>
+<h3 id="advanced-options-20">Advanced options</h3>
+<p>Here are the Advanced options specific to hasher (Better checksums
+for other remotes).</p>
 <h4 id="hasher-auto-size">--hasher-auto-size</h4>
-<p>Auto-update checksum for files smaller than this size (disabled by default).</p>
+<p>Auto-update checksum for files smaller than this size (disabled by
+default).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: auto_size</li>
@@ -25113,19 +37181,25 @@ rclone backend drop Hasher:</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-9">Metadata</h3>
-<p>Any metadata supported by the underlying remote is read and written.</p>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>Any metadata supported by the underlying remote is read and
+written.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h2 id="backend-commands-5">Backend commands</h2>
 <p>Here are the commands specific to the hasher backend.</p>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="drop">drop</h3>
 <p>Drop cache</p>
 <pre><code>rclone backend drop remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>Completely drop checksum cache. Usage Example: rclone backend drop hasher:</p>
+<p>Completely drop checksum cache. Usage Example: rclone backend drop
+hasher:</p>
 <h3 id="dump">dump</h3>
 <p>Dump the database</p>
 <pre><code>rclone backend dump remote: [options] [&lt;arguments&gt;+]</code></pre>
@@ -25137,41 +37211,76 @@ rclone backend drop Hasher:</code></pre>
 <h3 id="import">import</h3>
 <p>Import a SUM file</p>
 <pre><code>rclone backend import remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>Amend hash cache from a SUM file and bind checksums to files by size/time. Usage Example: rclone backend import hasher:subdir md5 /path/to/sum.md5</p>
+<p>Amend hash cache from a SUM file and bind checksums to files by
+size/time. Usage Example: rclone backend import hasher:subdir md5
+/path/to/sum.md5</p>
 <h3 id="stickyimport">stickyimport</h3>
 <p>Perform fast import of a SUM file</p>
 <pre><code>rclone backend stickyimport remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>Fill hash cache from a SUM file without verifying file fingerprints. Usage Example: rclone backend stickyimport hasher:subdir md5 remote:path/to/sum.md5</p>
-<h2 id="implementation-details-advanced">Implementation details (advanced)</h2>
-<p>This section explains how various rclone operations work on a hasher remote.</p>
-<p><strong>Disclaimer. This section describes current implementation which can change in future rclone versions!.</strong></p>
+<p>Fill hash cache from a SUM file without verifying file fingerprints.
+Usage Example: rclone backend stickyimport hasher:subdir md5
+remote:path/to/sum.md5</p>
+<h2 id="implementation-details-advanced">Implementation details
+(advanced)</h2>
+<p>This section explains how various rclone operations work on a hasher
+remote.</p>
+<p><strong>Disclaimer. This section describes current implementation
+which can change in future rclone versions!.</strong></p>
 <h3 id="hashsum-command">Hashsum command</h3>
-<p>The <code>rclone hashsum</code> (or <code>md5sum</code> or <code>sha1sum</code>) command will:</p>
+<p>The <code>rclone hashsum</code> (or <code>md5sum</code> or
+<code>sha1sum</code>) command will:</p>
 <ol type="1">
 <li>if requested hash is supported by lower level, just pass it.</li>
-<li>if object size is below <code>auto_size</code> then download object and calculate <em>requested</em> hashes on the fly.</li>
-<li>if unsupported and the size is big enough, build object <code>fingerprint</code> (including size, modtime if supported, first-found <em>other</em> hash if any).</li>
-<li>if the strict match is found in cache for the requested remote, return the stored hash.</li>
-<li>if remote found but fingerprint mismatched, then purge the entry and proceed to step 6.</li>
-<li>if remote not found or had no requested hash type or after step 5: download object, calculate all <em>supported</em> hashes on the fly and store in cache; return requested hash.</li>
+<li>if object size is below <code>auto_size</code> then download object
+and calculate <em>requested</em> hashes on the fly.</li>
+<li>if unsupported and the size is big enough, build object
+<code>fingerprint</code> (including size, modtime if supported,
+first-found <em>other</em> hash if any).</li>
+<li>if the strict match is found in cache for the requested remote,
+return the stored hash.</li>
+<li>if remote found but fingerprint mismatched, then purge the entry and
+proceed to step 6.</li>
+<li>if remote not found or had no requested hash type or after step 5:
+download object, calculate all <em>supported</em> hashes on the fly and
+store in cache; return requested hash.</li>
 </ol>
 <h3 id="other-operations">Other operations</h3>
 <ul>
-<li>any time a hash is requested, follow the logic from 1-4 from <code>hashsum</code> above</li>
-<li>whenever a file is uploaded or downloaded <strong>in full</strong>, capture the stream to calculate all supported hashes on the fly and update database</li>
-<li>server-side <code>move</code> will update keys of existing cache entries</li>
+<li>any time a hash is requested, follow the logic from 1-4 from
+<code>hashsum</code> above</li>
+<li>whenever a file is uploaded or downloaded <strong>in full</strong>,
+capture the stream to calculate all supported hashes on the fly and
+update database</li>
+<li>server-side <code>move</code> will update keys of existing cache
+entries</li>
 <li><code>deletefile</code> will remove a single cache entry</li>
-<li><code>purge</code> will remove all cache entries under the purged path</li>
+<li><code>purge</code> will remove all cache entries under the purged
+path</li>
 </ul>
-<p>Note that setting <code>max_age = 0</code> will disable checksum caching completely.</p>
-<p>If you set <code>max_age = off</code>, checksums in cache will never age, unless you fully rewrite or delete the file.</p>
+<p>Note that setting <code>max_age = 0</code> will disable checksum
+caching completely.</p>
+<p>If you set <code>max_age = off</code>, checksums in cache will never
+age, unless you fully rewrite or delete the file.</p>
 <h3 id="cache-storage">Cache storage</h3>
-<p>Cached checksums are stored as <code>bolt</code> database files under rclone cache directory, usually <code>~/.cache/rclone/kv/</code>. Databases are maintained one per <em>base</em> backend, named like <code>BaseRemote~hasher.bolt</code>. Checksums for multiple <code>alias</code>-es into a single base backend will be stored in the single database. All local paths are treated as aliases into the <code>local</code> backend (unless encrypted or chunked) and stored in <code>~/.cache/rclone/kv/local~hasher.bolt</code>. Databases can be shared between multiple rclone processes.</p>
+<p>Cached checksums are stored as <code>bolt</code> database files under
+rclone cache directory, usually <code>~/.cache/rclone/kv/</code>.
+Databases are maintained one per <em>base</em> backend, named like
+<code>BaseRemote~hasher.bolt</code>. Checksums for multiple
+<code>alias</code>-es into a single base backend will be stored in the
+single database. All local paths are treated as aliases into the
+<code>local</code> backend (unless encrypted or chunked) and stored in
+<code>~/.cache/rclone/kv/local~hasher.bolt</code>. Databases can be
+shared between multiple rclone processes.</p>
 <h1 id="hdfs">HDFS</h1>
-<p><a href="https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html">HDFS</a> is a distributed file-system, part of the <a href="https://hadoop.apache.org/">Apache Hadoop</a> framework.</p>
-<p>Paths are specified as <code>remote:</code> or <code>remote:path/to/dir</code>.</p>
-<h2 id="configuration-19">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p><a
+href="https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html">HDFS</a>
+is a distributed file-system, part of the <a
+href="https://hadoop.apache.org/">Apache Hadoop</a> framework.</p>
+<p>Paths are specified as <code>remote:</code> or
+<code>remote:path/to/dir</code>.</p>
+<h2 id="configuration-20">Configuration</h2>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -25231,15 +37340,20 @@ c) Copy remote
 s) Set configuration password
 q) Quit config
 e/n/d/r/c/s/q&gt; q</code></pre>
-<p>This remote is called <code>remote</code> and can now be used like this</p>
+<p>This remote is called <code>remote</code> and can now be used like
+this</p>
 <p>See all the top level directories</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls remote:directory</code></pre>
-<p>Sync the remote <code>directory</code> to <code>/home/local/directory</code>, deleting any excess files.</p>
+<p>Sync the remote <code>directory</code> to
+<code>/home/local/directory</code>, deleting any excess files.</p>
 <pre><code>rclone sync --interactive remote:directory /home/local/directory</code></pre>
-<h3 id="setting-up-your-own-hdfs-instance-for-testing">Setting up your own HDFS instance for testing</h3>
-<p>You may start with a <a href="https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/SingleCluster.html">manual setup</a> or use the docker image from the tests:</p>
+<h3 id="setting-up-your-own-hdfs-instance-for-testing">Setting up your
+own HDFS instance for testing</h3>
+<p>You may start with a <a
+href="https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/SingleCluster.html">manual
+setup</a> or use the docker image from the tests:</p>
 <p>If you want to build the docker image</p>
 <pre><code>git clone https://github.com/rclone/rclone.git
 cd rclone/fstest/testserver/images/test-hdfs
@@ -25247,20 +37361,28 @@ docker build --rm -t rclone/test-hdfs .</code></pre>
 <p>Or you can just use the latest one pushed</p>
 <pre><code>docker run --rm --name &quot;rclone-hdfs&quot; -p 127.0.0.1:9866:9866 -p 127.0.0.1:8020:8020 --hostname &quot;rclone-hdfs&quot; rclone/test-hdfs</code></pre>
 <p><strong>NB</strong> it need few seconds to startup.</p>
-<p>For this docker image the remote needs to be configured like this:</p>
+<p>For this docker image the remote needs to be configured like
+this:</p>
 <pre><code>[remote]
 type = hdfs
 namenode = 127.0.0.1:8020
 username = root</code></pre>
-<p>You can stop this image with <code>docker kill rclone-hdfs</code> (<strong>NB</strong> it does not use volumes, so all data uploaded will be lost.)</p>
+<p>You can stop this image with <code>docker kill rclone-hdfs</code>
+(<strong>NB</strong> it does not use volumes, so all data uploaded will
+be lost.)</p>
 <h3 id="modification-times-7">Modification times</h3>
 <p>Time accurate to 1 second is stored.</p>
 <h3 id="checksum">Checksum</h3>
 <p>No checksums are implemented.</p>
 <h3 id="usage-information">Usage information</h3>
-<p>You can use the <code>rclone about remote:</code> command which will display filesystem size and current usage.</p>
-<h3 id="restricted-filename-characters-11">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>You can use the <code>rclone about remote:</code> command which will
+display filesystem size and current usage.</p>
+<h3 id="restricted-filename-characters-10">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -25277,12 +37399,15 @@ username = root</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>.</p>
-<h3 id="standard-options-20">Standard options</h3>
-<p>Here are the Standard options specific to hdfs (Hadoop distributed file system).</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>.</p>
+<h3 id="standard-options-21">Standard options</h3>
+<p>Here are the Standard options specific to hdfs (Hadoop distributed
+file system).</p>
 <h4 id="hdfs-namenode">--hdfs-namenode</h4>
 <p>Hadoop name nodes and ports.</p>
-<p>E.g. "namenode-1:8020,namenode-2:8020,..." to connect to host namenodes at port 8020.</p>
+<p>E.g. "namenode-1:8020,namenode-2:8020,..." to connect to host
+namenodes at port 8020.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: namenode</li>
@@ -25306,11 +37431,15 @@ username = root</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-20">Advanced options</h3>
-<p>Here are the Advanced options specific to hdfs (Hadoop distributed file system).</p>
+<h3 id="advanced-options-21">Advanced options</h3>
+<p>Here are the Advanced options specific to hdfs (Hadoop distributed
+file system).</p>
 <h4 id="hdfs-service-principal-name">--hdfs-service-principal-name</h4>
 <p>Kerberos service principal name for the namenode.</p>
-<p>Enables KERBEROS authentication. Specifies the Service Principal Name (SERVICE/FQDN) for the namenode. E.g. "hdfs/namenode.hadoop.docker" for namenode running as service 'hdfs' with FQDN 'namenode.hadoop.docker'.</p>
+<p>Enables KERBEROS authentication. Specifies the Service Principal Name
+(SERVICE/FQDN) for the namenode. E.g. "hdfs/namenode.hadoop.docker" for
+namenode running as service 'hdfs' with FQDN
+'namenode.hadoop.docker'.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: service_principal_name</li>
@@ -25318,9 +37447,14 @@ username = root</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="hdfs-data-transfer-protection">--hdfs-data-transfer-protection</h4>
-<p>Kerberos data transfer protection: authentication|integrity|privacy.</p>
-<p>Specifies whether or not authentication, data signature integrity checks, and wire encryption are required when communicating with the datanodes. Possible values are 'authentication', 'integrity' and 'privacy'. Used only with KERBEROS enabled.</p>
+<h4
+id="hdfs-data-transfer-protection">--hdfs-data-transfer-protection</h4>
+<p>Kerberos data transfer protection:
+authentication|integrity|privacy.</p>
+<p>Specifies whether or not authentication, data signature integrity
+checks, and wire encryption are required when communicating with the
+datanodes. Possible values are 'authentication', 'integrity' and
+'privacy'. Used only with KERBEROS enabled.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: data_transfer_protection</li>
@@ -25337,7 +37471,8 @@ username = root</code></pre>
 </ul>
 <h4 id="hdfs-encoding">--hdfs-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -25361,10 +37496,14 @@ username = root</code></pre>
 </ul>
 <h1 id="hidrive">HiDrive</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<p>The initial setup for hidrive involves getting a token from HiDrive which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<h2 id="configuration-20">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<p>The initial setup for hidrive involves getting a token from HiDrive
+which you need to do in your browser. <code>rclone config</code> walks
+you through it.</p>
+<h2 id="configuration-21">Configuration</h2>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found - make a new one
@@ -25407,9 +37546,19 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p><strong>You should be aware that OAuth-tokens can be used to access your account and hence should not be shared with other persons.</strong> See the <a href="#keeping-your-tokens-safe">below section</a> for more information.</p>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from HiDrive. This only runs from the moment it opens your browser to the moment you get back the verification code. The webserver runs on <code>http://127.0.0.1:53682/</code>. If local port <code>53682</code> is protected by a firewall you may need to temporarily unblock the firewall to complete authorization.</p>
+<p><strong>You should be aware that OAuth-tokens can be used to access
+your account and hence should not be shared with other persons.</strong>
+See the <a href="#keeping-your-tokens-safe">below section</a> for more
+information.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from HiDrive. This only runs from the moment it
+opens your browser to the moment you get back the verification code. The
+webserver runs on <code>http://127.0.0.1:53682/</code>. If local port
+<code>53682</code> is protected by a firewall you may need to
+temporarily unblock the firewall to complete authorization.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your HiDrive root folder</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -25418,50 +37567,98 @@ y/e/d&gt; y</code></pre>
 <p>To copy a local directory to a HiDrive directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <h3 id="keeping-your-tokens-safe">Keeping your tokens safe</h3>
-<p>Any OAuth-tokens will be stored by rclone in the remote's configuration file as unencrypted text. Anyone can use a valid refresh-token to access your HiDrive filesystem without knowing your password. Therefore you should make sure no one else can access your configuration.</p>
-<p>It is possible to encrypt rclone's configuration file. You can find information on securing your configuration file by viewing the <a href="https://rclone.org/docs/#configuration-encryption">configuration encryption docs</a>.</p>
+<p>Any OAuth-tokens will be stored by rclone in the remote's
+configuration file as unencrypted text. Anyone can use a valid
+refresh-token to access your HiDrive filesystem without knowing your
+password. Therefore you should make sure no one else can access your
+configuration.</p>
+<p>It is possible to encrypt rclone's configuration file. You can find
+information on securing your configuration file by viewing the <a
+href="https://rclone.org/docs/#configuration-encryption">configuration
+encryption docs</a>.</p>
 <h3 id="invalid-refresh-token-1">Invalid refresh token</h3>
-<p>As can be verified <a href="https://developer.hidrive.com/basics-flows/">here</a>, each <code>refresh_token</code> (for Native Applications) is valid for 60 days. If used to access HiDrivei, its validity will be automatically extended.</p>
+<p>As can be verified <a
+href="https://developer.hidrive.com/basics-flows/">here</a>, each
+<code>refresh_token</code> (for Native Applications) is valid for 60
+days. If used to access HiDrivei, its validity will be automatically
+extended.</p>
 <p>This means that if you</p>
 <ul>
 <li>Don't use the HiDrive remote for 60 days</li>
 </ul>
-<p>then rclone will return an error which includes a text that implies the refresh token is <em>invalid</em> or <em>expired</em>.</p>
-<p>To fix this you will need to authorize rclone to access your HiDrive account again.</p>
+<p>then rclone will return an error which includes a text that implies
+the refresh token is <em>invalid</em> or <em>expired</em>.</p>
+<p>To fix this you will need to authorize rclone to access your HiDrive
+account again.</p>
 <p>Using</p>
 <pre><code>rclone config reconnect remote:</code></pre>
-<p>the process is very similar to the process of initial setup exemplified before.</p>
-<h3 id="modification-times-and-hashes-9">Modification times and hashes</h3>
-<p>HiDrive allows modification times to be set on objects accurate to 1 second.</p>
-<p>HiDrive supports <a href="https://static.hidrive.com/dev/0001">its own hash type</a> which is used to verify the integrity of file contents after successful transfers.</p>
-<h3 id="restricted-filename-characters-12">Restricted filename characters</h3>
-<p>HiDrive cannot store files or folders that include <code>/</code> (0x2F) or null-bytes (0x00) in their name. Any other characters can be used in the names of files or folders. Additionally, files or folders cannot be named either of the following: <code>.</code> or <code>..</code></p>
-<p>Therefore rclone will automatically replace these characters, if files or folders are stored or accessed with such names.</p>
-<p>You can read about how this filename encoding works in general <a href="overview/#restricted-filenames">here</a>.</p>
-<p>Keep in mind that HiDrive only supports file or folder names with a length of 255 characters or less.</p>
+<p>the process is very similar to the process of initial setup
+exemplified before.</p>
+<h3 id="modification-times-and-hashes-9">Modification times and
+hashes</h3>
+<p>HiDrive allows modification times to be set on objects accurate to 1
+second.</p>
+<p>HiDrive supports <a href="https://static.hidrive.com/dev/0001">its
+own hash type</a> which is used to verify the integrity of file contents
+after successful transfers.</p>
+<h3 id="restricted-filename-characters-11">Restricted filename
+characters</h3>
+<p>HiDrive cannot store files or folders that include <code>/</code>
+(0x2F) or null-bytes (0x00) in their name. Any other characters can be
+used in the names of files or folders. Additionally, files or folders
+cannot be named either of the following: <code>.</code> or
+<code>..</code></p>
+<p>Therefore rclone will automatically replace these characters, if
+files or folders are stored or accessed with such names.</p>
+<p>You can read about how this filename encoding works in general <a
+href="overview/#restricted-filenames">here</a>.</p>
+<p>Keep in mind that HiDrive only supports file or folder names with a
+length of 255 characters or less.</p>
 <h3 id="transfers-3">Transfers</h3>
-<p>HiDrive limits file sizes per single request to a maximum of 2 GiB. To allow storage of larger files and allow for better upload performance, the hidrive backend will use a chunked transfer for files larger than 96 MiB. Rclone will upload multiple parts/chunks of the file at the same time. Chunks in the process of being uploaded are buffered in memory, so you may want to restrict this behaviour on systems with limited resources.</p>
+<p>HiDrive limits file sizes per single request to a maximum of 2 GiB.
+To allow storage of larger files and allow for better upload
+performance, the hidrive backend will use a chunked transfer for files
+larger than 96 MiB. Rclone will upload multiple parts/chunks of the file
+at the same time. Chunks in the process of being uploaded are buffered
+in memory, so you may want to restrict this behaviour on systems with
+limited resources.</p>
 <p>You can customize this behaviour using the following options:</p>
 <ul>
 <li><code>chunk_size</code>: size of file parts</li>
-<li><code>upload_cutoff</code>: files larger or equal to this in size will use a chunked transfer</li>
-<li><code>upload_concurrency</code>: number of file-parts to upload at the same time</li>
+<li><code>upload_cutoff</code>: files larger or equal to this in size
+will use a chunked transfer</li>
+<li><code>upload_concurrency</code>: number of file-parts to upload at
+the same time</li>
 </ul>
-<p>See the below section about configuration options for more details.</p>
+<p>See the below section about configuration options for more
+details.</p>
 <h3 id="root-folder">Root folder</h3>
-<p>You can set the root folder for rclone. This is the directory that rclone considers to be the root of your HiDrive.</p>
-<p>Usually, you will leave this blank, and rclone will use the root of the account.</p>
-<p>However, you can set this to restrict rclone to a specific folder hierarchy.</p>
-<p>This works by prepending the contents of the <code>root_prefix</code> option to any paths accessed by rclone. For example, the following two ways to access the home directory are equivalent:</p>
+<p>You can set the root folder for rclone. This is the directory that
+rclone considers to be the root of your HiDrive.</p>
+<p>Usually, you will leave this blank, and rclone will use the root of
+the account.</p>
+<p>However, you can set this to restrict rclone to a specific folder
+hierarchy.</p>
+<p>This works by prepending the contents of the <code>root_prefix</code>
+option to any paths accessed by rclone. For example, the following two
+ways to access the home directory are equivalent:</p>
 <pre><code>rclone lsd --hidrive-root-prefix=&quot;/users/test/&quot; remote:path
 
 rclone lsd remote:/users/test/path</code></pre>
-<p>See the below section about configuration options for more details.</p>
+<p>See the below section about configuration options for more
+details.</p>
 <h3 id="directory-member-count">Directory member count</h3>
-<p>By default, rclone will know the number of directory members contained in a directory. For example, <code>rclone lsd</code> uses this information.</p>
-<p>The acquisition of this information will result in additional time costs for HiDrive's API. When dealing with large directory structures, it may be desirable to circumvent this time cost, especially when this information is not explicitly needed. For this, the <code>disable_fetching_member_count</code> option can be used.</p>
-<p>See the below section about configuration options for more details.</p>
-<h3 id="standard-options-21">Standard options</h3>
+<p>By default, rclone will know the number of directory members
+contained in a directory. For example, <code>rclone lsd</code> uses this
+information.</p>
+<p>The acquisition of this information will result in additional time
+costs for HiDrive's API. When dealing with large directory structures,
+it may be desirable to circumvent this time cost, especially when this
+information is not explicitly needed. For this, the
+<code>disable_fetching_member_count</code> option can be used.</p>
+<p>See the below section about configuration options for more
+details.</p>
+<h3 id="standard-options-22">Standard options</h3>
 <p>Here are the Standard options specific to hidrive (HiDrive).</p>
 <h4 id="hidrive-client-id">--hidrive-client-id</h4>
 <p>OAuth Client Id.</p>
@@ -25484,7 +37681,8 @@ rclone lsd remote:/users/test/path</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="hidrive-scope-access">--hidrive-scope-access</h4>
-<p>Access permissions that rclone should use when requesting access from HiDrive.</p>
+<p>Access permissions that rclone should use when requesting access from
+HiDrive.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: scope_access</li>
@@ -25503,7 +37701,7 @@ rclone lsd remote:/users/test/path</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-21">Advanced options</h3>
+<h3 id="advanced-options-22">Advanced options</h3>
 <p>Here are the Advanced options specific to hidrive (HiDrive).</p>
 <h4 id="hidrive-token">--hidrive-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
@@ -25535,7 +37733,8 @@ rclone lsd remote:/users/test/path</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="hidrive-scope-role">--hidrive-scope-role</h4>
-<p>User-level that rclone should use when requesting access from HiDrive.</p>
+<p>User-level that rclone should use when requesting access from
+HiDrive.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: scope_role</li>
@@ -25561,7 +37760,9 @@ rclone lsd remote:/users/test/path</code></pre>
 </ul>
 <h4 id="hidrive-root-prefix">--hidrive-root-prefix</h4>
 <p>The root/parent folder for all paths.</p>
-<p>Fill in to use the specified folder as the parent for all paths given to the remote. This way rclone can use any folder as its starting point.</p>
+<p>Fill in to use the specified folder as the parent for all paths given
+to the remote. This way rclone can use any folder as its starting
+point.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_prefix</li>
@@ -25573,7 +37774,8 @@ rclone lsd remote:/users/test/path</code></pre>
 <li>"/"
 <ul>
 <li>The topmost directory accessible by rclone.</li>
-<li>This will be equivalent with "root" if rclone uses a regular HiDrive user account.</li>
+<li>This will be equivalent with "root" if rclone uses a regular HiDrive
+user account.</li>
 </ul></li>
 <li>"root"
 <ul>
@@ -25582,7 +37784,9 @@ rclone lsd remote:/users/test/path</code></pre>
 <li>""
 <ul>
 <li>This specifies that there is no root-prefix for your paths.</li>
-<li>When using this you will always need to specify paths to this remote with a valid parent e.g. "remote:/path/to/dir" or "remote:root/path/to/dir".</li>
+<li>When using this you will always need to specify paths to this remote
+with a valid parent e.g. "remote:/path/to/dir" or
+"remote:root/path/to/dir".</li>
 </ul></li>
 </ul></li>
 </ul>
@@ -25596,9 +37800,12 @@ rclone lsd remote:/users/test/path</code></pre>
 <li>Type: string</li>
 <li>Default: "https://api.hidrive.strato.com/2.1"</li>
 </ul>
-<h4 id="hidrive-disable-fetching-member-count">--hidrive-disable-fetching-member-count</h4>
-<p>Do not fetch number of objects in directories unless it is absolutely necessary.</p>
-<p>Requests may be faster if the number of objects in subdirectories is not fetched.</p>
+<h4
+id="hidrive-disable-fetching-member-count">--hidrive-disable-fetching-member-count</h4>
+<p>Do not fetch number of objects in directories unless it is absolutely
+necessary.</p>
+<p>Requests may be faster if the number of objects in subdirectories is
+not fetched.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_fetching_member_count</li>
@@ -25608,9 +37815,15 @@ rclone lsd remote:/users/test/path</code></pre>
 </ul>
 <h4 id="hidrive-chunk-size">--hidrive-chunk-size</h4>
 <p>Chunksize for chunked uploads.</p>
-<p>Any files larger than the configured cutoff (or files of unknown size) will be uploaded in chunks of this size.</p>
-<p>The upper limit for this is 2147483647 bytes (about 2.000Gi). That is the maximum amount of bytes a single upload-operation will support. Setting this above the upper limit or to a negative value will cause uploads to fail.</p>
-<p>Setting this to larger values may increase the upload speed at the cost of using more memory. It can be set to smaller values smaller to save on memory.</p>
+<p>Any files larger than the configured cutoff (or files of unknown
+size) will be uploaded in chunks of this size.</p>
+<p>The upper limit for this is 2147483647 bytes (about 2.000Gi). That is
+the maximum amount of bytes a single upload-operation will support.
+Setting this above the upper limit or to a negative value will cause
+uploads to fail.</p>
+<p>Setting this to larger values may increase the upload speed at the
+cost of using more memory. It can be set to smaller values smaller to
+save on memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -25620,8 +37833,11 @@ rclone lsd remote:/users/test/path</code></pre>
 </ul>
 <h4 id="hidrive-upload-cutoff">--hidrive-upload-cutoff</h4>
 <p>Cutoff/Threshold for chunked uploads.</p>
-<p>Any files larger than this will be uploaded in chunks of the configured chunksize.</p>
-<p>The upper limit for this is 2147483647 bytes (about 2.000Gi). That is the maximum amount of bytes a single upload-operation will support. Setting this above the upper limit will cause uploads to fail.</p>
+<p>Any files larger than this will be uploaded in chunks of the
+configured chunksize.</p>
+<p>The upper limit for this is 2147483647 bytes (about 2.000Gi). That is
+the maximum amount of bytes a single upload-operation will support.
+Setting this above the upper limit will cause uploads to fail.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_cutoff</li>
@@ -25631,8 +37847,12 @@ rclone lsd remote:/users/test/path</code></pre>
 </ul>
 <h4 id="hidrive-upload-concurrency">--hidrive-upload-concurrency</h4>
 <p>Concurrency for chunked uploads.</p>
-<p>This is the upper limit for how many transfers for the same file are running concurrently. Setting this above to a value smaller than 1 will cause uploads to deadlock.</p>
-<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
+<p>This is the upper limit for how many transfers for the same file are
+running concurrently. Setting this above to a value smaller than 1 will
+cause uploads to deadlock.</p>
+<p>If you are uploading small numbers of large files over high-speed
+links and these uploads do not fully utilize your bandwidth, then
+increasing this may help to speed up the transfers.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_concurrency</li>
@@ -25642,7 +37862,8 @@ rclone lsd remote:/users/test/path</code></pre>
 </ul>
 <h4 id="hidrive-encoding">--hidrive-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -25661,20 +37882,56 @@ rclone lsd remote:/users/test/path</code></pre>
 </ul>
 <h2 id="limitations-17">Limitations</h2>
 <h3 id="symbolic-links">Symbolic links</h3>
-<p>HiDrive is able to store symbolic links (<em>symlinks</em>) by design, for example, when unpacked from a zip archive.</p>
-<p>There exists no direct mechanism to manage native symlinks in remotes. As such this implementation has chosen to ignore any native symlinks present in the remote. rclone will not be able to access or show any symlinks stored in the hidrive-remote. This means symlinks cannot be individually removed, copied, or moved, except when removing, copying, or moving the parent folder.</p>
-<p><em>This does not affect the <code>.rclonelink</code>-files that rclone uses to encode and store symbolic links.</em></p>
+<p>HiDrive is able to store symbolic links (<em>symlinks</em>) by
+design, for example, when unpacked from a zip archive.</p>
+<p>There exists no direct mechanism to manage native symlinks in
+remotes. As such this implementation has chosen to ignore any native
+symlinks present in the remote. rclone will not be able to access or
+show any symlinks stored in the hidrive-remote. This means symlinks
+cannot be individually removed, copied, or moved, except when removing,
+copying, or moving the parent folder.</p>
+<p><em>This does not affect the <code>.rclonelink</code>-files that
+rclone uses to encode and store symbolic links.</em></p>
 <h3 id="sparse-files">Sparse files</h3>
 <p>It is possible to store sparse files in HiDrive.</p>
-<p>Note that copying a sparse file will expand the holes into null-byte (0x00) regions that will then consume disk space. Likewise, when downloading a sparse file, the resulting file will have null-byte regions in the place of file holes.</p>
+<p>Note that copying a sparse file will expand the holes into null-byte
+(0x00) regions that will then consume disk space. Likewise, when
+downloading a sparse file, the resulting file will have null-byte
+regions in the place of file holes.</p>
 <h1 id="http">HTTP</h1>
-<p>The HTTP remote is a read only remote for reading files of a webserver. The webserver should provide file listings which rclone will read and turn into a remote. This has been tested with common webservers such as Apache/Nginx/Caddy and will likely work with file listings from most web servers. (If it doesn't then please file an issue, or send a pull request!)</p>
-<p>Paths are specified as <code>remote:</code> or <code>remote:path</code>.</p>
-<p>The <code>remote:</code> represents the configured <a href="#http-url">url</a>, and any path following it will be resolved relative to this url, according to the URL standard. This means with remote url <code>https://beta.rclone.org/branch</code> and path <code>fix</code>, the resolved URL will be <code>https://beta.rclone.org/branch/fix</code>, while with path <code>/fix</code> the resolved URL will be <code>https://beta.rclone.org/fix</code> as the absolute path is resolved from the root of the domain.</p>
-<p>If the path following the <code>remote:</code> ends with <code>/</code> it will be assumed to point to a directory. If the path does not end with <code>/</code>, then a HEAD request is sent and the response used to decide if it it is treated as a file or a directory (run with <code>-vv</code> to see details). When <a href="#http-no-head">--http-no-head</a> is specified, a path without ending <code>/</code> is always assumed to be a file. If rclone incorrectly assumes the path is a file, the solution is to specify the path with ending <code>/</code>. When you know the path is a directory, ending it with <code>/</code> is always better as it avoids the initial HEAD request.</p>
-<p>To just download a single file it is easier to use <a href="https://rclone.org/commands/rclone_copyurl/">copyurl</a>.</p>
-<h2 id="configuration-21">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>The HTTP remote is a read only remote for reading files of a
+webserver. The webserver should provide file listings which rclone will
+read and turn into a remote. This has been tested with common webservers
+such as Apache/Nginx/Caddy and will likely work with file listings from
+most web servers. (If it doesn't then please file an issue, or send a
+pull request!)</p>
+<p>Paths are specified as <code>remote:</code> or
+<code>remote:path</code>.</p>
+<p>The <code>remote:</code> represents the configured <a
+href="#http-url">url</a>, and any path following it will be resolved
+relative to this url, according to the URL standard. This means with
+remote url <code>https://beta.rclone.org/branch</code> and path
+<code>fix</code>, the resolved URL will be
+<code>https://beta.rclone.org/branch/fix</code>, while with path
+<code>/fix</code> the resolved URL will be
+<code>https://beta.rclone.org/fix</code> as the absolute path is
+resolved from the root of the domain.</p>
+<p>If the path following the <code>remote:</code> ends with
+<code>/</code> it will be assumed to point to a directory. If the path
+does not end with <code>/</code>, then a HEAD request is sent and the
+response used to decide if it it is treated as a file or a directory
+(run with <code>-vv</code> to see details). When <a
+href="#http-no-head">--http-no-head</a> is specified, a path without
+ending <code>/</code> is always assumed to be a file. If rclone
+incorrectly assumes the path is a file, the solution is to specify the
+path with ending <code>/</code>. When you know the path is a directory,
+ending it with <code>/</code> is always better as it avoids the initial
+HEAD request.</p>
+<p>To just download a single file it is easier to use <a
+href="https://rclone.org/commands/rclone_copyurl/">copyurl</a>.</p>
+<h2 id="configuration-22">Configuration</h2>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -25719,29 +37976,34 @@ c) Copy remote
 s) Set configuration password
 q) Quit config
 e/n/d/r/c/s/q&gt; q</code></pre>
-<p>This remote is called <code>remote</code> and can now be used like this</p>
+<p>This remote is called <code>remote</code> and can now be used like
+this</p>
 <p>See all the top level directories</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls remote:directory</code></pre>
-<p>Sync the remote <code>directory</code> to <code>/home/local/directory</code>, deleting any excess files.</p>
+<p>Sync the remote <code>directory</code> to
+<code>/home/local/directory</code>, deleting any excess files.</p>
 <pre><code>rclone sync --interactive remote:directory /home/local/directory</code></pre>
 <h3 id="read-only">Read only</h3>
-<p>This remote is read only - you can't upload files to an HTTP server.</p>
+<p>This remote is read only - you can't upload files to an HTTP
+server.</p>
 <h3 id="modification-times-8">Modification times</h3>
 <p>Most HTTP servers store time accurate to 1 second.</p>
 <h3 id="checksum-1">Checksum</h3>
 <p>No checksums are stored.</p>
 <h3 id="usage-without-a-config-file">Usage without a config file</h3>
-<p>Since the http remote only has one config parameter it is easy to use without a config file:</p>
+<p>Since the http remote only has one config parameter it is easy to use
+without a config file:</p>
 <pre><code>rclone lsd --http-url https://beta.rclone.org :http:</code></pre>
 <p>or:</p>
 <pre><code>rclone lsd :http,url=&#39;https://beta.rclone.org&#39;:</code></pre>
-<h3 id="standard-options-22">Standard options</h3>
+<h3 id="standard-options-23">Standard options</h3>
 <p>Here are the Standard options specific to http (HTTP).</p>
 <h4 id="http-url">--http-url</h4>
 <p>URL of HTTP host to connect to.</p>
-<p>E.g. "https://example.com", or "https://user:pass@example.com" to use a username and password.</p>
+<p>E.g. "https://example.com", or "https://user:pass@example.com" to use
+a username and password.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: url</li>
@@ -25758,14 +38020,18 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="advanced-options-22">Advanced options</h3>
+<h3 id="advanced-options-23">Advanced options</h3>
 <p>Here are the Advanced options specific to http (HTTP).</p>
 <h4 id="http-headers">--http-headers</h4>
 <p>Set HTTP headers for all transactions.</p>
 <p>Use this to set additional HTTP headers for all transactions.</p>
-<p>The input format is comma separated list of key,value pairs. Standard <a href="https://godoc.org/encoding/csv">CSV encoding</a> may be used.</p>
-<p>For example, to set a Cookie use 'Cookie,name=value', or '"Cookie","name=value"'.</p>
-<p>You can set multiple headers, e.g. '"Cookie","name=value","Authorization","xxx"'.</p>
+<p>The input format is comma separated list of key,value pairs. Standard
+<a href="https://godoc.org/encoding/csv">CSV encoding</a> may be
+used.</p>
+<p>For example, to set a Cookie use 'Cookie,name=value', or
+'"Cookie","name=value"'.</p>
+<p>You can set multiple headers, e.g.
+'"Cookie","name=value","Authorization","xxx"'.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: headers</li>
@@ -25775,9 +38041,14 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </ul>
 <h4 id="http-no-slash">--http-no-slash</h4>
 <p>Set this if the site doesn't end directories with /.</p>
-<p>Use this if your target website does not use / on the end of directories.</p>
-<p>A / on the end of a path is how rclone normally tells the difference between files and directories. If this flag is set, then rclone will treat all files with Content-Type: text/html as directories and read URLs from them rather than downloading them.</p>
-<p>Note that this may cause rclone to confuse genuine HTML files with directories.</p>
+<p>Use this if your target website does not use / on the end of
+directories.</p>
+<p>A / on the end of a path is how rclone normally tells the difference
+between files and directories. If this flag is set, then rclone will
+treat all files with Content-Type: text/html as directories and read
+URLs from them rather than downloading them.</p>
+<p>Note that this may cause rclone to confuse genuine HTML files with
+directories.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_slash</li>
@@ -25787,13 +38058,19 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </ul>
 <h4 id="http-no-head">--http-no-head</h4>
 <p>Don't use HEAD requests.</p>
-<p>HEAD requests are mainly used to find file sizes in dir listing. If your site is being very slow to load then you can try this option. Normally rclone does a HEAD request for each potential file in a directory listing to:</p>
+<p>HEAD requests are mainly used to find file sizes in dir listing. If
+your site is being very slow to load then you can try this option.
+Normally rclone does a HEAD request for each potential file in a
+directory listing to:</p>
 <ul>
 <li>find its size</li>
 <li>check it really exists</li>
 <li>check to see if it is a directory</li>
 </ul>
-<p>If you set this option, rclone will not do the HEAD request. This will mean that directory listings are much quicker, but rclone won't have the times or sizes of any files, and some files that don't exist may be in the listing.</p>
+<p>If you set this option, rclone will not do the HEAD request. This
+will mean that directory listings are much quicker, but rclone won't
+have the times or sizes of any files, and some files that don't exist
+may be in the listing.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_head</li>
@@ -25815,32 +38092,53 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="set-2">set</h3>
 <p>Set command for updating the config parameters.</p>
 <pre><code>rclone backend set remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This set command can be used to update the config parameters for a running http backend.</p>
+<p>This set command can be used to update the config parameters for a
+running http backend.</p>
 <p>Usage Examples:</p>
 <pre><code>rclone backend set remote: [-o opt_name=opt_value] [-o opt_name2=opt_value2]
 rclone rc backend/command command=set fs=remote: [-o opt_name=opt_value] [-o opt_name2=opt_value2]
 rclone rc backend/command command=set fs=remote: -o url=https://example.com</code></pre>
 <p>The option keys are named as they are in the config file.</p>
-<p>This rebuilds the connection to the http backend when it is called with the new parameters. Only new parameters need be passed as the values will default to those currently in use.</p>
+<p>This rebuilds the connection to the http backend when it is called
+with the new parameters. Only new parameters need be passed as the
+values will default to those currently in use.</p>
 <p>It doesn't return anything.</p>
 <h2 id="limitations-18">Limitations</h2>
-<p><code>rclone about</code> is not supported by the HTTP backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the HTTP backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="imagekit">ImageKit</h1>
-<p>This is a backend for the <a href="https://imagekit.io/">ImageKit.io</a> storage service.</p>
+<p>This is a backend for the <a
+href="https://imagekit.io/">ImageKit.io</a> storage service.</p>
 <h4 id="about-imagekit">About ImageKit</h4>
-<p><a href="https://imagekit.io/">ImageKit.io</a> provides real-time image and video optimizations, transformations, and CDN delivery. Over 1,000 businesses and 70,000 developers trust ImageKit with their images and videos on the web.</p>
+<p><a href="https://imagekit.io/">ImageKit.io</a> provides real-time
+image and video optimizations, transformations, and CDN delivery. Over
+1,000 businesses and 70,000 developers trust ImageKit with their images
+and videos on the web.</p>
 <h4 id="accounts-pricing">Accounts &amp; Pricing</h4>
-<p>To use this backend, you need to <a href="https://imagekit.io/registration/">create an account</a> on ImageKit. Start with a free plan with generous usage limits. Then, as your requirements grow, upgrade to a plan that best fits your needs. See <a href="https://imagekit.io/plans">the pricing details</a>.</p>
-<h2 id="configuration-22">Configuration</h2>
+<p>To use this backend, you need to <a
+href="https://imagekit.io/registration/">create an account</a> on
+ImageKit. Start with a free plan with generous usage limits. Then, as
+your requirements grow, upgrade to a plan that best fits your needs. See
+<a href="https://imagekit.io/plans">the pricing details</a>.</p>
+<h2 id="configuration-23">Configuration</h2>
 <p>Here is an example of making an imagekit configuration.</p>
-<p>Firstly create a <a href="https://imagekit.io/">ImageKit.io</a> account and choose a plan.</p>
-<p>You will need to log in and get the <code>publicKey</code> and <code>privateKey</code> for your account from the developer section.</p>
+<p>Firstly create a <a href="https://imagekit.io/">ImageKit.io</a>
+account and choose a plan.</p>
+<p>You will need to log in and get the <code>publicKey</code> and
+<code>privateKey</code> for your account from the developer section.</p>
 <p>Now run</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
@@ -25904,10 +38202,11 @@ y/e/d&gt; y</code></pre>
 <p>ImageKit does not support modification times or hashes yet.</p>
 <h3 id="checksums">Checksums</h3>
 <p>No checksums are supported.</p>
-<h3 id="standard-options-23">Standard options</h3>
+<h3 id="standard-options-24">Standard options</h3>
 <p>Here are the Standard options specific to imagekit (ImageKit.io).</p>
 <h4 id="imagekit-endpoint">--imagekit-endpoint</h4>
-<p>You can find your ImageKit.io URL endpoint in your <a href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
+<p>You can find your ImageKit.io URL endpoint in your <a
+href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
 <p>Properties:</p>
 <ul>
 <li>Config: endpoint</li>
@@ -25916,7 +38215,8 @@ y/e/d&gt; y</code></pre>
 <li>Required: true</li>
 </ul>
 <h4 id="imagekit-public-key">--imagekit-public-key</h4>
-<p>You can find your ImageKit.io public key in your <a href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
+<p>You can find your ImageKit.io public key in your <a
+href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
 <p>Properties:</p>
 <ul>
 <li>Config: public_key</li>
@@ -25925,7 +38225,8 @@ y/e/d&gt; y</code></pre>
 <li>Required: true</li>
 </ul>
 <h4 id="imagekit-private-key">--imagekit-private-key</h4>
-<p>You can find your ImageKit.io private key in your <a href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
+<p>You can find your ImageKit.io private key in your <a
+href="https://imagekit.io/dashboard/developer/api-keys">dashboard</a></p>
 <p>Properties:</p>
 <ul>
 <li>Config: private_key</li>
@@ -25933,10 +38234,11 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: true</li>
 </ul>
-<h3 id="advanced-options-23">Advanced options</h3>
+<h3 id="advanced-options-24">Advanced options</h3>
 <p>Here are the Advanced options specific to imagekit (ImageKit.io).</p>
 <h4 id="imagekit-only-signed">--imagekit-only-signed</h4>
-<p>If you have configured <code>Restrict unsigned image URLs</code> in your dashboard settings, set this to true.</p>
+<p>If you have configured <code>Restrict unsigned image URLs</code> in
+your dashboard settings, set this to true.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: only_signed</li>
@@ -25964,13 +38266,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="imagekit-encoding">--imagekit-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_IMAGEKIT_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Dollar,Question,Hash,Percent,BackSlash,Del,Ctl,InvalidUtf8,Dot,SquareBracket</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Dollar,Question,Hash,Percent,BackSlash,Del,Ctl,InvalidUtf8,Dot,SquareBracket</li>
 </ul>
 <h4 id="imagekit-description">--imagekit-description</h4>
 <p>Description of the remote.</p>
@@ -25982,8 +38286,10 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-10">Metadata</h3>
-<p>Any metadata supported by the underlying remote is read and written.</p>
-<p>Here are the possible system metadata items for the imagekit backend.</p>
+<p>Any metadata supported by the underlying remote is read and
+written.</p>
+<p>Here are the possible system metadata items for the imagekit
+backend.</p>
 <table>
 <colgroup>
 <col style="width: 15%" />
@@ -26032,7 +38338,8 @@ y/e/d&gt; y</code></pre>
 </tr>
 <tr class="odd">
 <td>google-tags</td>
-<td>AI generated tags by Google Cloud Vision associated with the image</td>
+<td>AI generated tags by Google Cloud Vision associated with the
+image</td>
 <td>string</td>
 <td>tag1,tag2</td>
 <td><strong>Y</strong></td>
@@ -26081,36 +38388,82 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h1 id="internet-archive">Internet Archive</h1>
-<p>The Internet Archive backend utilizes Items on <a href="https://archive.org/">archive.org</a></p>
-<p>Refer to <a href="https://archive.org/services/docs/api/ias3.html">IAS3 API documentation</a> for the API this backend uses.</p>
-<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:item/path/to/dir</code>.</p>
+<p>The Internet Archive backend utilizes Items on <a
+href="https://archive.org/">archive.org</a></p>
+<p>Refer to <a
+href="https://archive.org/services/docs/api/ias3.html">IAS3 API
+documentation</a> for the API this backend uses.</p>
+<p>Paths are specified as <code>remote:bucket</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g. <code>remote:item/path/to/dir</code>.</p>
 <p>Unlike S3, listing up all items uploaded by you isn't supported.</p>
 <p>Once you have made a remote, you can use it like this:</p>
 <p>Make a new item</p>
 <pre><code>rclone mkdir remote:item</code></pre>
 <p>List the contents of a item</p>
 <pre><code>rclone ls remote:item</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote item, deleting any excess files in the item.</p>
+<p>Sync <code>/home/local/directory</code> to the remote item, deleting
+any excess files in the item.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:item</code></pre>
 <h2 id="notes">Notes</h2>
-<p>Because of Internet Archive's architecture, it enqueues write operations (and extra post-processings) in a per-item queue. You can check item's queue at https://catalogd.archive.org/history/item-name-here . Because of that, all uploads/deletes will not show up immediately and takes some time to be available. The per-item queue is enqueued to an another queue, Item Deriver Queue. <a href="https://catalogd.archive.org/catalog.php?whereami=1">You can check the status of Item Deriver Queue here.</a> This queue has a limit, and it may block you from uploading, or even deleting. You should avoid uploading a lot of small files for better behavior.</p>
-<p>You can optionally wait for the server's processing to finish, by setting non-zero value to <code>wait_archive</code> key. By making it wait, rclone can do normal file comparison. Make sure to set a large enough value (e.g. <code>30m0s</code> for smaller files) as it can take a long time depending on server's queue.</p>
+<p>Because of Internet Archive's architecture, it enqueues write
+operations (and extra post-processings) in a per-item queue. You can
+check item's queue at
+https://catalogd.archive.org/history/item-name-here . Because of that,
+all uploads/deletes will not show up immediately and takes some time to
+be available. The per-item queue is enqueued to an another queue, Item
+Deriver Queue. <a
+href="https://catalogd.archive.org/catalog.php?whereami=1">You can check
+the status of Item Deriver Queue here.</a> This queue has a limit, and
+it may block you from uploading, or even deleting. You should avoid
+uploading a lot of small files for better behavior.</p>
+<p>You can optionally wait for the server's processing to finish, by
+setting non-zero value to <code>wait_archive</code> key. By making it
+wait, rclone can do normal file comparison. Make sure to set a large
+enough value (e.g. <code>30m0s</code> for smaller files) as it can take
+a long time depending on server's queue.</p>
 <h2 id="about-metadata">About metadata</h2>
-<p>This backend supports setting, updating and reading metadata of each file. The metadata will appear as file metadata on Internet Archive. However, some fields are reserved by both Internet Archive and rclone.</p>
-<p>The following are reserved by Internet Archive: - <code>name</code> - <code>source</code> - <code>size</code> - <code>md5</code> - <code>crc32</code> - <code>sha1</code> - <code>format</code> - <code>old_version</code> - <code>viruscheck</code> - <code>summation</code></p>
-<p>Trying to set values to these keys is ignored with a warning. Only setting <code>mtime</code> is an exception. Doing so make it the identical behavior as setting ModTime.</p>
-<p>rclone reserves all the keys starting with <code>rclone-</code>. Setting value for these keys will give you warnings, but values are set according to request.</p>
-<p>If there are multiple values for a key, only the first one is returned. This is a limitation of rclone, that supports one value per one key. It can be triggered when you did a server-side copy.</p>
-<p>Reading metadata will also provide custom (non-standard nor reserved) ones.</p>
-<h2 id="filtering-auto-generated-files">Filtering auto generated files</h2>
-<p>The Internet Archive automatically creates metadata files after upload. These can cause problems when doing an <code>rclone sync</code> as rclone will try, and fail, to delete them. These metadata files are not changeable, as they are created by the Internet Archive automatically.</p>
-<p>These auto-created files can be excluded from the sync using <a href="https://rclone.org/filtering/#metadata">metadata filtering</a>.</p>
+<p>This backend supports setting, updating and reading metadata of each
+file. The metadata will appear as file metadata on Internet Archive.
+However, some fields are reserved by both Internet Archive and
+rclone.</p>
+<p>The following are reserved by Internet Archive: - <code>name</code> -
+<code>source</code> - <code>size</code> - <code>md5</code> -
+<code>crc32</code> - <code>sha1</code> - <code>format</code> -
+<code>old_version</code> - <code>viruscheck</code> -
+<code>summation</code></p>
+<p>Trying to set values to these keys is ignored with a warning. Only
+setting <code>mtime</code> is an exception. Doing so make it the
+identical behavior as setting ModTime.</p>
+<p>rclone reserves all the keys starting with <code>rclone-</code>.
+Setting value for these keys will give you warnings, but values are set
+according to request.</p>
+<p>If there are multiple values for a key, only the first one is
+returned. This is a limitation of rclone, that supports one value per
+one key. It can be triggered when you did a server-side copy.</p>
+<p>Reading metadata will also provide custom (non-standard nor reserved)
+ones.</p>
+<h2 id="filtering-auto-generated-files">Filtering auto generated
+files</h2>
+<p>The Internet Archive automatically creates metadata files after
+upload. These can cause problems when doing an <code>rclone sync</code>
+as rclone will try, and fail, to delete them. These metadata files are
+not changeable, as they are created by the Internet Archive
+automatically.</p>
+<p>These auto-created files can be excluded from the sync using <a
+href="https://rclone.org/filtering/#metadata">metadata
+filtering</a>.</p>
 <pre><code>rclone sync ... --metadata-exclude &quot;source=metadata&quot; --metadata-exclude &quot;format=Metadata&quot;</code></pre>
-<p>Which excludes from the sync any files which have the <code>source=metadata</code> or <code>format=Metadata</code> flags which are added to Internet Archive auto-created files.</p>
-<h2 id="configuration-23">Configuration</h2>
-<p>Here is an example of making an internetarchive configuration. Most applies to the other providers as well, any differences are described <a href="#providers">below</a>.</p>
+<p>Which excludes from the sync any files which have the
+<code>source=metadata</code> or <code>format=Metadata</code> flags which
+are added to Internet Archive auto-created files.</p>
+<h2 id="configuration-24">Configuration</h2>
+<p>Here is an example of making an internetarchive configuration. Most
+applies to the other providers as well, any differences are described <a
+href="#providers">below</a>.</p>
 <p>First run</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
@@ -26178,11 +38531,14 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<h3 id="standard-options-24">Standard options</h3>
-<p>Here are the Standard options specific to internetarchive (Internet Archive).</p>
-<h4 id="internetarchive-access-key-id">--internetarchive-access-key-id</h4>
+<h3 id="standard-options-25">Standard options</h3>
+<p>Here are the Standard options specific to internetarchive (Internet
+Archive).</p>
+<h4
+id="internetarchive-access-key-id">--internetarchive-access-key-id</h4>
 <p>IAS3 Access Key.</p>
-<p>Leave blank for anonymous access. You can find one here: https://archive.org/account/s3.php</p>
+<p>Leave blank for anonymous access. You can find one here:
+https://archive.org/account/s3.php</p>
 <p>Properties:</p>
 <ul>
 <li>Config: access_key_id</li>
@@ -26190,7 +38546,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="internetarchive-secret-access-key">--internetarchive-secret-access-key</h4>
+<h4
+id="internetarchive-secret-access-key">--internetarchive-secret-access-key</h4>
 <p>IAS3 Secret Key (password).</p>
 <p>Leave blank for anonymous access.</p>
 <p>Properties:</p>
@@ -26200,8 +38557,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-24">Advanced options</h3>
-<p>Here are the Advanced options specific to internetarchive (Internet Archive).</p>
+<h3 id="advanced-options-25">Advanced options</h3>
+<p>Here are the Advanced options specific to internetarchive (Internet
+Archive).</p>
 <h4 id="internetarchive-endpoint">--internetarchive-endpoint</h4>
 <p>IAS3 Endpoint.</p>
 <p>Leave blank for default value.</p>
@@ -26212,7 +38570,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: "https://s3.us.archive.org"</li>
 </ul>
-<h4 id="internetarchive-front-endpoint">--internetarchive-front-endpoint</h4>
+<h4
+id="internetarchive-front-endpoint">--internetarchive-front-endpoint</h4>
 <p>Host of InternetArchive Frontend.</p>
 <p>Leave blank for default value.</p>
 <p>Properties:</p>
@@ -26222,8 +38581,13 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: "https://archive.org"</li>
 </ul>
-<h4 id="internetarchive-disable-checksum">--internetarchive-disable-checksum</h4>
-<p>Don't ask the server to test against MD5 checksum calculated by rclone. Normally rclone will calculate the MD5 checksum of the input before uploading it so it can ask the server to check the object against checksum. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
+<h4
+id="internetarchive-disable-checksum">--internetarchive-disable-checksum</h4>
+<p>Don't ask the server to test against MD5 checksum calculated by
+rclone. Normally rclone will calculate the MD5 checksum of the input
+before uploading it so it can ask the server to check the object against
+checksum. This is great for data integrity checking but can cause long
+delays for large files to start uploading.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_checksum</li>
@@ -26231,8 +38595,12 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: true</li>
 </ul>
-<h4 id="internetarchive-wait-archive">--internetarchive-wait-archive</h4>
-<p>Timeout for waiting the server's processing tasks (specifically archive and book_op) to finish. Only enable if you need to be guaranteed to be reflected after write operations. 0 to disable waiting. No errors to be thrown in case of timeout.</p>
+<h4
+id="internetarchive-wait-archive">--internetarchive-wait-archive</h4>
+<p>Timeout for waiting the server's processing tasks (specifically
+archive and book_op) to finish. Only enable if you need to be guaranteed
+to be reflected after write operations. 0 to disable waiting. No errors
+to be thrown in case of timeout.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: wait_archive</li>
@@ -26242,7 +38610,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="internetarchive-encoding">--internetarchive-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -26260,9 +38629,13 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-11">Metadata</h3>
-<p>Metadata fields provided by Internet Archive. If there are multiple values for a key, only the first one is returned. This is a limitation of Rclone, that supports one value per one key.</p>
-<p>Owner is able to add custom keys. Metadata feature grabs all the keys including them.</p>
-<p>Here are the possible system metadata items for the internetarchive backend.</p>
+<p>Metadata fields provided by Internet Archive. If there are multiple
+values for a key, only the first one is returned. This is a limitation
+of Rclone, that supports one value per one key.</p>
+<p>Owner is able to add custom keys. Metadata feature grabs all the keys
+including them.</p>
+<p>Here are the possible system metadata items for the internetarchive
+backend.</p>
 <table>
 <colgroup>
 <col style="width: 15%" />
@@ -26318,7 +38691,8 @@ y/e/d&gt; y</code></pre>
 </tr>
 <tr class="even">
 <td>old_version</td>
-<td>Whether the file was replaced and moved by keep-old-version flag</td>
+<td>Whether the file was replaced and moved by keep-old-version
+flag</td>
 <td>boolean</td>
 <td>true</td>
 <td><strong>Y</strong></td>
@@ -26339,7 +38713,8 @@ y/e/d&gt; y</code></pre>
 </tr>
 <tr class="odd">
 <td>rclone-update-track</td>
-<td>Random value used by Rclone for tracking changes inside Internet Archive</td>
+<td>Random value used by Rclone for tracking changes inside Internet
+Archive</td>
 <td>string</td>
 <td>aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa</td>
 <td>N</td>
@@ -26381,33 +38756,97 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h1 id="jottacloud">Jottacloud</h1>
-<p>Jottacloud is a cloud storage service provider from a Norwegian company, using its own datacenters in Norway. In addition to the official service at <a href="https://www.jottacloud.com/">jottacloud.com</a>, it also provides white-label solutions to different companies, such as: * Telia * Telia Cloud (cloud.telia.se) * Telia Sky (sky.telia.no) * Tele2 * Tele2 Cloud (mittcloud.tele2.se) * Onlime * Onlime Cloud Storage (onlime.dk) * Elkjøp (with subsidiaries): * Elkjøp Cloud (cloud.elkjop.no) * Elgiganten Sweden (cloud.elgiganten.se) * Elgiganten Denmark (cloud.elgiganten.dk) * Giganti Cloud (cloud.gigantti.fi) * ELKO Cloud (cloud.elko.is)</p>
-<p>Most of the white-label versions are supported by this backend, although may require different authentication setup - described below.</p>
+<p>Jottacloud is a cloud storage service provider from a Norwegian
+company, using its own datacenters in Norway. In addition to the
+official service at <a
+href="https://www.jottacloud.com/">jottacloud.com</a>, it also provides
+white-label solutions to different companies, such as: * Telia * Telia
+Cloud (cloud.telia.se) * Telia Sky (sky.telia.no) * Tele2 * Tele2 Cloud
+(mittcloud.tele2.se) * Onlime * Onlime Cloud Storage (onlime.dk) *
+Elkjøp (with subsidiaries): * Elkjøp Cloud (cloud.elkjop.no) *
+Elgiganten Sweden (cloud.elgiganten.se) * Elgiganten Denmark
+(cloud.elgiganten.dk) * Giganti Cloud (cloud.gigantti.fi) * ELKO Cloud
+(cloud.elko.is)</p>
+<p>Most of the white-label versions are supported by this backend,
+although may require different authentication setup - described
+below.</p>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
 <h2 id="authentication-types">Authentication types</h2>
-<p>Some of the whitelabel versions uses a different authentication method than the official service, and you have to choose the correct one when setting up the remote.</p>
+<p>Some of the whitelabel versions uses a different authentication
+method than the official service, and you have to choose the correct one
+when setting up the remote.</p>
 <h3 id="standard-authentication">Standard authentication</h3>
-<p>The standard authentication method used by the official service (jottacloud.com), as well as some of the whitelabel services, requires you to generate a single-use personal login token from the account security settings in the service's web interface. Log in to your account, go to "Settings" and then "Security", or use the direct link presented to you by rclone when configuring the remote: <a href="https://www.jottacloud.com/web/secure" class="uri">https://www.jottacloud.com/web/secure</a>. Scroll down to the section "Personal login token", and click the "Generate" button. Note that if you are using a whitelabel service you probably can't use the direct link, you need to find the same page in their dedicated web interface, and also it may be in a different location than described above.</p>
-<p>To access your account from multiple instances of rclone, you need to configure each of them with a separate personal login token. E.g. you create a Jottacloud remote with rclone in one location, and copy the configuration file to a second location where you also want to run rclone and access the same remote. Then you need to replace the token for one of them, using the <a href="https://rclone.org/commands/rclone_config_reconnect/">config reconnect</a> command, which requires you to generate a new personal login token and supply as input. If you do not do this, the token may easily end up being invalidated, resulting in both instances failing with an error message something along the lines of:</p>
+<p>The standard authentication method used by the official service
+(jottacloud.com), as well as some of the whitelabel services, requires
+you to generate a single-use personal login token from the account
+security settings in the service's web interface. Log in to your
+account, go to "Settings" and then "Security", or use the direct link
+presented to you by rclone when configuring the remote: <a
+href="https://www.jottacloud.com/web/secure"
+class="uri">https://www.jottacloud.com/web/secure</a>. Scroll down to
+the section "Personal login token", and click the "Generate" button.
+Note that if you are using a whitelabel service you probably can't use
+the direct link, you need to find the same page in their dedicated web
+interface, and also it may be in a different location than described
+above.</p>
+<p>To access your account from multiple instances of rclone, you need to
+configure each of them with a separate personal login token. E.g. you
+create a Jottacloud remote with rclone in one location, and copy the
+configuration file to a second location where you also want to run
+rclone and access the same remote. Then you need to replace the token
+for one of them, using the <a
+href="https://rclone.org/commands/rclone_config_reconnect/">config
+reconnect</a> command, which requires you to generate a new personal
+login token and supply as input. If you do not do this, the token may
+easily end up being invalidated, resulting in both instances failing
+with an error message something along the lines of:</p>
 <pre><code>oauth2: cannot fetch token: 400 Bad Request
 Response: {&quot;error&quot;:&quot;invalid_grant&quot;,&quot;error_description&quot;:&quot;Stale token&quot;}</code></pre>
-<p>When this happens, you need to replace the token as described above to be able to use your remote again.</p>
-<p>All personal login tokens you have taken into use will be listed in the web interface under "My logged in devices", and from the right side of that list you can click the "X" button to revoke individual tokens.</p>
+<p>When this happens, you need to replace the token as described above
+to be able to use your remote again.</p>
+<p>All personal login tokens you have taken into use will be listed in
+the web interface under "My logged in devices", and from the right side
+of that list you can click the "X" button to revoke individual
+tokens.</p>
 <h3 id="legacy-authentication">Legacy authentication</h3>
-<p>If you are using one of the whitelabel versions (e.g. from Elkjøp) you may not have the option to generate a CLI token. In this case you'll have to use the legacy authentication. To do this select yes when the setup asks for legacy authentication and enter your username and password. The rest of the setup is identical to the default setup.</p>
+<p>If you are using one of the whitelabel versions (e.g. from Elkjøp)
+you may not have the option to generate a CLI token. In this case you'll
+have to use the legacy authentication. To do this select yes when the
+setup asks for legacy authentication and enter your username and
+password. The rest of the setup is identical to the default setup.</p>
 <h3 id="telia-cloud-authentication">Telia Cloud authentication</h3>
-<p>Similar to other whitelabel versions Telia Cloud doesn't offer the option of creating a CLI token, and additionally uses a separate authentication flow where the username is generated internally. To setup rclone to use Telia Cloud, choose Telia Cloud authentication in the setup. The rest of the setup is identical to the default setup.</p>
+<p>Similar to other whitelabel versions Telia Cloud doesn't offer the
+option of creating a CLI token, and additionally uses a separate
+authentication flow where the username is generated internally. To setup
+rclone to use Telia Cloud, choose Telia Cloud authentication in the
+setup. The rest of the setup is identical to the default setup.</p>
 <h3 id="tele2-cloud-authentication">Tele2 Cloud authentication</h3>
-<p>As Tele2-Com Hem merger was completed this authentication can be used for former Com Hem Cloud and Tele2 Cloud customers as no support for creating a CLI token exists, and additionally uses a separate authentication flow where the username is generated internally. To setup rclone to use Tele2 Cloud, choose Tele2 Cloud authentication in the setup. The rest of the setup is identical to the default setup.</p>
-<h3 id="onlime-cloud-storage-authentication">Onlime Cloud Storage authentication</h3>
-<p>Onlime has sold access to Jottacloud proper, while providing localized support to Danish Customers, but have recently set up their own hosting, transferring their customers from Jottacloud servers to their own ones.</p>
-<p>This, of course, necessitates using their servers for authentication, but otherwise functionality and architecture seems equivalent to Jottacloud.</p>
-<p>To setup rclone to use Onlime Cloud Storage, choose Onlime Cloud authentication in the setup. The rest of the setup is identical to the default setup.</p>
-<h2 id="configuration-24">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code> with the default setup. First run:</p>
+<p>As Tele2-Com Hem merger was completed this authentication can be used
+for former Com Hem Cloud and Tele2 Cloud customers as no support for
+creating a CLI token exists, and additionally uses a separate
+authentication flow where the username is generated internally. To setup
+rclone to use Tele2 Cloud, choose Tele2 Cloud authentication in the
+setup. The rest of the setup is identical to the default setup.</p>
+<h3 id="onlime-cloud-storage-authentication">Onlime Cloud Storage
+authentication</h3>
+<p>Onlime has sold access to Jottacloud proper, while providing
+localized support to Danish Customers, but have recently set up their
+own hosting, transferring their customers from Jottacloud servers to
+their own ones.</p>
+<p>This, of course, necessitates using their servers for authentication,
+but otherwise functionality and architecture seems equivalent to
+Jottacloud.</p>
+<p>To setup rclone to use Onlime Cloud Storage, choose Onlime Cloud
+authentication in the setup. The rest of the setup is identical to the
+default setup.</p>
+<h2 id="configuration-25">Configuration</h2>
+<p>Here is an example of how to make a remote called <code>remote</code>
+with the default setup. First run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -26499,23 +38938,68 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone lsd remote:</code></pre>
 <p>List all the files in your Jottacloud</p>
 <pre><code>rclone ls remote:</code></pre>
-<p>To copy a local directory to an Jottacloud directory called backup</p>
+<p>To copy a local directory to an Jottacloud directory called
+backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <h3 id="devices-and-mountpoints">Devices and Mountpoints</h3>
-<p>The official Jottacloud client registers a device for each computer you install it on, and shows them in the backup section of the user interface. For each folder you select for backup it will create a mountpoint within this device. A built-in device called Jotta is special, and contains mountpoints Archive, Sync and some others, used for corresponding features in official clients.</p>
-<p>With rclone you'll want to use the standard Jotta/Archive device/mountpoint in most cases. However, you may for example want to access files from the sync or backup functionality provided by the official clients, and rclone therefore provides the option to select other devices and mountpoints during config.</p>
-<p>You are allowed to create new devices and mountpoints. All devices except the built-in Jotta device are treated as backup devices by official Jottacloud clients, and the mountpoints on them are individual backup sets.</p>
-<p>With the built-in Jotta device, only existing, built-in, mountpoints can be selected. In addition to the mentioned Archive and Sync, it may contain several other mountpoints such as: Latest, Links, Shared and Trash. All of these are special mountpoints with a different internal representation than the "regular" mountpoints. Rclone will only to a very limited degree support them. Generally you should avoid these, unless you know what you are doing.</p>
+<p>The official Jottacloud client registers a device for each computer
+you install it on, and shows them in the backup section of the user
+interface. For each folder you select for backup it will create a
+mountpoint within this device. A built-in device called Jotta is
+special, and contains mountpoints Archive, Sync and some others, used
+for corresponding features in official clients.</p>
+<p>With rclone you'll want to use the standard Jotta/Archive
+device/mountpoint in most cases. However, you may for example want to
+access files from the sync or backup functionality provided by the
+official clients, and rclone therefore provides the option to select
+other devices and mountpoints during config.</p>
+<p>You are allowed to create new devices and mountpoints. All devices
+except the built-in Jotta device are treated as backup devices by
+official Jottacloud clients, and the mountpoints on them are individual
+backup sets.</p>
+<p>With the built-in Jotta device, only existing, built-in, mountpoints
+can be selected. In addition to the mentioned Archive and Sync, it may
+contain several other mountpoints such as: Latest, Links, Shared and
+Trash. All of these are special mountpoints with a different internal
+representation than the "regular" mountpoints. Rclone will only to a
+very limited degree support them. Generally you should avoid these,
+unless you know what you are doing.</p>
 <h3 id="fast-list-4">--fast-list</h3>
-<p>This backend supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
-<p>Note that the implementation in Jottacloud always uses only a single API request to get the entire list, so for large folders this could lead to long wait time before the first results are shown.</p>
-<p>Note also that with rclone version 1.58 and newer, information about <a href="https://rclone.org/overview/#mime-type">MIME types</a> and metadata item <a href="#metadata">utime</a> are not available when using <code>--fast-list</code>.</p>
-<h3 id="modification-times-and-hashes-10">Modification times and hashes</h3>
-<p>Jottacloud allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
-<p>Jottacloud supports MD5 type hashes, so you can use the <code>--checksum</code> flag.</p>
-<p>Note that Jottacloud requires the MD5 hash before upload so if the source does not have an MD5 checksum then the file will be cached temporarily on disk (in location given by <a href="https://rclone.org/docs/#temp-dir-dir">--temp-dir</a>) before it is uploaded. Small files will be cached in memory - see the <a href="#jottacloud-md5-memory-limit">--jottacloud-md5-memory-limit</a> flag. When uploading from local disk the source checksum is always available, so this does not apply. Starting with rclone version 1.52 the same is true for encrypted remotes (in older versions the crypt backend would not calculate hashes for uploads from local disk, so the Jottacloud backend had to do it as described above).</p>
-<h3 id="restricted-filename-characters-13">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>This backend supports <code>--fast-list</code> which allows you to
+use fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details.</p>
+<p>Note that the implementation in Jottacloud always uses only a single
+API request to get the entire list, so for large folders this could lead
+to long wait time before the first results are shown.</p>
+<p>Note also that with rclone version 1.58 and newer, information about
+<a href="https://rclone.org/overview/#mime-type">MIME types</a> and
+metadata item <a href="#metadata">utime</a> are not available when using
+<code>--fast-list</code>.</p>
+<h3 id="modification-times-and-hashes-10">Modification times and
+hashes</h3>
+<p>Jottacloud allows modification times to be set on objects accurate to
+1 second. These will be used to detect whether objects need syncing or
+not.</p>
+<p>Jottacloud supports MD5 type hashes, so you can use the
+<code>--checksum</code> flag.</p>
+<p>Note that Jottacloud requires the MD5 hash before upload so if the
+source does not have an MD5 checksum then the file will be cached
+temporarily on disk (in location given by <a
+href="https://rclone.org/docs/#temp-dir-dir">--temp-dir</a>) before it
+is uploaded. Small files will be cached in memory - see the <a
+href="#jottacloud-md5-memory-limit">--jottacloud-md5-memory-limit</a>
+flag. When uploading from local disk the source checksum is always
+available, so this does not apply. Starting with rclone version 1.52 the
+same is true for encrypted remotes (in older versions the crypt backend
+would not calculate hashes for uploads from local disk, so the
+Jottacloud backend had to do it as described above).</p>
+<h3 id="restricted-filename-characters-12">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -26562,16 +39046,34 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in XML strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in XML strings.</p>
 <h3 id="deleting-files-3">Deleting files</h3>
-<p>By default, rclone will send all files to the trash when deleting files. They will be permanently deleted automatically after 30 days. You may bypass the trash and permanently delete files immediately by using the <a href="#jottacloud-hard-delete">--jottacloud-hard-delete</a> flag, or set the equivalent environment variable. Emptying the trash is supported by the <a href="https://rclone.org/commands/rclone_cleanup/">cleanup</a> command.</p>
+<p>By default, rclone will send all files to the trash when deleting
+files. They will be permanently deleted automatically after 30 days. You
+may bypass the trash and permanently delete files immediately by using
+the <a href="#jottacloud-hard-delete">--jottacloud-hard-delete</a> flag,
+or set the equivalent environment variable. Emptying the trash is
+supported by the <a
+href="https://rclone.org/commands/rclone_cleanup/">cleanup</a>
+command.</p>
 <h3 id="versions-3">Versions</h3>
-<p>Jottacloud supports file versioning. When rclone uploads a new version of a file it creates a new version of it. Currently rclone only supports retrieving the current version but older versions can be accessed via the Jottacloud Website.</p>
-<p>Versioning can be disabled by <code>--jottacloud-no-versions</code> option. This is achieved by deleting the remote file prior to uploading a new version. If the upload the fails no version of the file will be available in the remote.</p>
+<p>Jottacloud supports file versioning. When rclone uploads a new
+version of a file it creates a new version of it. Currently rclone only
+supports retrieving the current version but older versions can be
+accessed via the Jottacloud Website.</p>
+<p>Versioning can be disabled by <code>--jottacloud-no-versions</code>
+option. This is achieved by deleting the remote file prior to uploading
+a new version. If the upload the fails no version of the file will be
+available in the remote.</p>
 <h3 id="quota-information-1">Quota information</h3>
-<p>To view your current quota you can use the <code>rclone about remote:</code> command which will display your usage limit (unless it is unlimited) and the current usage.</p>
-<h3 id="standard-options-25">Standard options</h3>
-<p>Here are the Standard options specific to jottacloud (Jottacloud).</p>
+<p>To view your current quota you can use the
+<code>rclone about remote:</code> command which will display your usage
+limit (unless it is unlimited) and the current usage.</p>
+<h3 id="standard-options-26">Standard options</h3>
+<p>Here are the Standard options specific to jottacloud
+(Jottacloud).</p>
 <h4 id="jottacloud-client-id">--jottacloud-client-id</h4>
 <p>OAuth Client Id.</p>
 <p>Leave blank normally.</p>
@@ -26592,8 +39094,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-25">Advanced options</h3>
-<p>Here are the Advanced options specific to jottacloud (Jottacloud).</p>
+<h3 id="advanced-options-26">Advanced options</h3>
+<p>Here are the Advanced options specific to jottacloud
+(Jottacloud).</p>
 <h4 id="jottacloud-token">--jottacloud-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
 <p>Properties:</p>
@@ -26624,7 +39127,8 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="jottacloud-md5-memory-limit">--jottacloud-md5-memory-limit</h4>
-<p>Files bigger than this will be cached on disk to calculate the MD5 if required.</p>
+<p>Files bigger than this will be cached on disk to calculate the MD5 if
+required.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: md5_memory_limit</li>
@@ -26634,7 +39138,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="jottacloud-trashed-only">--jottacloud-trashed-only</h4>
 <p>Only show files that are in the trash.</p>
-<p>This will show trashed files in their original directory structure.</p>
+<p>This will show trashed files in their original directory
+structure.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: trashed_only</li>
@@ -26651,7 +39156,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="jottacloud-upload-resume-limit">--jottacloud-upload-resume-limit</h4>
+<h4
+id="jottacloud-upload-resume-limit">--jottacloud-upload-resume-limit</h4>
 <p>Files bigger than this can be resumed if the upload fail's.</p>
 <p>Properties:</p>
 <ul>
@@ -26661,7 +39167,8 @@ y/e/d&gt; y</code></pre>
 <li>Default: 10Mi</li>
 </ul>
 <h4 id="jottacloud-no-versions">--jottacloud-no-versions</h4>
-<p>Avoid server side versioning by deleting files and recreating files instead of overwriting them.</p>
+<p>Avoid server side versioning by deleting files and recreating files
+instead of overwriting them.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_versions</li>
@@ -26671,13 +39178,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="jottacloud-encoding">--jottacloud-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_JOTTACLOUD_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Del,Ctl,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="jottacloud-description">--jottacloud-description</h4>
 <p>Description of the remote.</p>
@@ -26689,8 +39198,10 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-12">Metadata</h3>
-<p>Jottacloud has limited support for metadata, currently an extended set of timestamps.</p>
-<p>Here are the possible system metadata items for the jottacloud backend.</p>
+<p>Jottacloud has limited support for metadata, currently an extended
+set of timestamps.</p>
+<p>Here are the possible system metadata items for the jottacloud
+backend.</p>
 <table>
 <colgroup>
 <col style="width: 15%" />
@@ -26732,26 +39243,42 @@ y/e/d&gt; y</code></pre>
 </tr>
 <tr class="even">
 <td>utime</td>
-<td>Time of last upload, when current revision was created, generated by backend</td>
+<td>Time of last upload, when current revision was created, generated by
+backend</td>
 <td>RFC 3339</td>
 <td>2006-01-02T15:04:05.999999999Z07:00</td>
 <td><strong>Y</strong></td>
 </tr>
 </tbody>
 </table>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h2 id="limitations-19">Limitations</h2>
-<p>Note that Jottacloud is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
-<p>There are quite a few characters that can't be in Jottacloud file names. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a ? in it will be mapped to ？ instead.</p>
-<p>Jottacloud only supports filenames up to 255 characters in length.</p>
+<p>Note that Jottacloud is case insensitive so you can't have a file
+called "Hello.doc" and one called "hello.doc".</p>
+<p>There are quite a few characters that can't be in Jottacloud file
+names. Rclone will map these names to and from an identical looking
+unicode equivalent. For example if a file has a ? in it will be mapped
+to ？ instead.</p>
+<p>Jottacloud only supports filenames up to 255 characters in
+length.</p>
 <h2 id="troubleshooting-1">Troubleshooting</h2>
-<p>Jottacloud exhibits some inconsistent behaviours regarding deleted files and folders which may cause Copy, Move and DirMove operations to previously deleted paths to fail. Emptying the trash should help in such cases.</p>
+<p>Jottacloud exhibits some inconsistent behaviours regarding deleted
+files and folders which may cause Copy, Move and DirMove operations to
+previously deleted paths to fail. Emptying the trash should help in such
+cases.</p>
 <h1 id="koofr">Koofr</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-25">Configuration</h2>
-<p>The initial setup for Koofr involves creating an application password for rclone. You can do that by opening the Koofr <a href="https://app.koofr.net/app/admin/preferences/password">web application</a>, giving the password a nice name like <code>rclone</code> and clicking on generate.</p>
-<p>Here is an example of how to make a remote called <code>koofr</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-26">Configuration</h2>
+<p>The initial setup for Koofr involves creating an application password
+for rclone. You can do that by opening the Koofr <a
+href="https://app.koofr.net/app/admin/preferences/password">web
+application</a>, giving the password a nice name like
+<code>rclone</code> and clicking on generate.</p>
+<p>Here is an example of how to make a remote called <code>koofr</code>.
+First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -26809,7 +39336,9 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>You can choose to edit advanced config in order to enter your own service URL if you use an on-premise or white label Koofr instance, or choose an alternative mount instead of your primary storage.</p>
+<p>You can choose to edit advanced config in order to enter your own
+service URL if you use an on-premise or white label Koofr instance, or
+choose an alternative mount instead of your primary storage.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your Koofr</p>
 <pre><code>rclone lsd koofr:</code></pre>
@@ -26817,8 +39346,12 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls koofr:</code></pre>
 <p>To copy a local directory to an Koofr directory called backup</p>
 <pre><code>rclone copy /home/source koofr:backup</code></pre>
-<h3 id="restricted-filename-characters-14">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<h3 id="restricted-filename-characters-13">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -26835,9 +39368,12 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in XML strings.</p>
-<h3 id="standard-options-26">Standard options</h3>
-<p>Here are the Standard options specific to koofr (Koofr, Digi Storage and other Koofr-compatible storage providers).</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in XML strings.</p>
+<h3 id="standard-options-27">Standard options</h3>
+<p>Here are the Standard options specific to koofr (Koofr, Digi Storage
+and other Koofr-compatible storage providers).</p>
 <h4 id="koofr-provider">--koofr-provider</h4>
 <p>Choose your storage provider.</p>
 <p>Properties:</p>
@@ -26882,8 +39418,11 @@ y/e/d&gt; y</code></pre>
 <li>Required: true</li>
 </ul>
 <h4 id="koofr-password">--koofr-password</h4>
-<p>Your password for rclone generate one at https://app.koofr.net/app/admin/preferences/password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>Your password for rclone generate one at
+https://app.koofr.net/app/admin/preferences/password.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -26892,8 +39431,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: true</li>
 </ul>
-<h3 id="advanced-options-26">Advanced options</h3>
-<p>Here are the Advanced options specific to koofr (Koofr, Digi Storage and other Koofr-compatible storage providers).</p>
+<h3 id="advanced-options-27">Advanced options</h3>
+<p>Here are the Advanced options specific to koofr (Koofr, Digi Storage
+and other Koofr-compatible storage providers).</p>
 <h4 id="koofr-mountid">--koofr-mountid</h4>
 <p>Mount ID of the mount to use.</p>
 <p>If omitted, the primary mount is used.</p>
@@ -26906,7 +39446,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="koofr-setmtime">--koofr-setmtime</h4>
 <p>Does the backend support setting modification time.</p>
-<p>Set this to false if you use a mount ID that points to a Dropbox or Amazon Drive backend.</p>
+<p>Set this to false if you use a mount ID that points to a Dropbox or
+Amazon Drive backend.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: setmtime</li>
@@ -26916,7 +39457,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="koofr-encoding">--koofr-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -26934,13 +39476,19 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-20">Limitations</h2>
-<p>Note that Koofr is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
+<p>Note that Koofr is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".</p>
 <h2 id="providers-2">Providers</h2>
 <h3 id="koofr-1">Koofr</h3>
-<p>This is the original <a href="https://koofr.eu">Koofr</a> storage provider used as main example and described in the <a href="#configuration">configuration</a> section above.</p>
+<p>This is the original <a href="https://koofr.eu">Koofr</a> storage
+provider used as main example and described in the <a
+href="#configuration">configuration</a> section above.</p>
 <h3 id="digi-storage">Digi Storage</h3>
-<p><a href="https://www.digi.ro/servicii/online/digi-storage">Digi Storage</a> is a cloud storage service run by <a href="https://www.digi.ro/">Digi.ro</a> that provides a Koofr API.</p>
-<p>Here is an example of how to make a remote called <code>ds</code>. First run:</p>
+<p><a href="https://www.digi.ro/servicii/online/digi-storage">Digi
+Storage</a> is a cloud storage service run by <a
+href="https://www.digi.ro/">Digi.ro</a> that provides a Koofr API.</p>
+<p>Here is an example of how to make a remote called <code>ds</code>.
+First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -26998,8 +39546,11 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
 <h3 id="other">Other</h3>
-<p>You may also want to use another, public or private storage provider that runs a Koofr API compatible service, by simply providing the base URL to connect to.</p>
-<p>Here is an example of how to make a remote called <code>other</code>. First run:</p>
+<p>You may also want to use another, public or private storage provider
+that runs a Koofr API compatible service, by simply providing the base
+URL to connect to.</p>
+<p>Here is an example of how to make a remote called <code>other</code>.
+First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -27062,8 +39613,9 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
 <h1 id="linkbox">Linkbox</h1>
-<p>Linkbox is <a href="https://linkbox.to/">a private cloud drive</a>.</p>
-<h2 id="configuration-26">Configuration</h2>
+<p>Linkbox is <a href="https://linkbox.to/">a private cloud
+drive</a>.</p>
+<h2 id="configuration-27">Configuration</h2>
 <p>Here is an example of making a remote for Linkbox.</p>
 <p>First run:</p>
 <pre><code> rclone config</code></pre>
@@ -27099,7 +39651,7 @@ e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y
 </code></pre>
-<h3 id="standard-options-27">Standard options</h3>
+<h3 id="standard-options-28">Standard options</h3>
 <p>Here are the Standard options specific to linkbox (Linkbox).</p>
 <h4 id="linkbox-token">--linkbox-token</h4>
 <p>Token from https://www.linkbox.to/admin/account</p>
@@ -27110,7 +39662,7 @@ y/e/d&gt; y
 <li>Type: string</li>
 <li>Required: true</li>
 </ul>
-<h3 id="advanced-options-27">Advanced options</h3>
+<h3 id="advanced-options-28">Advanced options</h3>
 <p>Here are the Advanced options specific to linkbox (Linkbox).</p>
 <h4 id="linkbox-description">--linkbox-description</h4>
 <p>Description of the remote.</p>
@@ -27122,30 +39674,47 @@ y/e/d&gt; y
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-21">Limitations</h2>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h1 id="mail.ru-cloud">Mail.ru Cloud</h1>
-<p><a href="https://cloud.mail.ru/">Mail.ru Cloud</a> is a cloud storage provided by a Russian internet company <a href="https://mail.ru">Mail.Ru Group</a>. The official desktop client is <a href="https://disk-o.cloud/en">Disk-O:</a>, available on Windows and Mac OS.</p>
+<p><a href="https://cloud.mail.ru/">Mail.ru Cloud</a> is a cloud storage
+provided by a Russian internet company <a href="https://mail.ru">Mail.Ru
+Group</a>. The official desktop client is <a
+href="https://disk-o.cloud/en">Disk-O:</a>, available on Windows and Mac
+OS.</p>
 <h2 id="features-highlights">Features highlights</h2>
 <ul>
-<li>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code></li>
-<li>Files have a <code>last modified time</code> property, directories don't</li>
+<li>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code></li>
+<li>Files have a <code>last modified time</code> property, directories
+don't</li>
 <li>Deleted files are by default moved to the trash</li>
 <li>Files and directories can be shared via public links</li>
-<li>Partial uploads or streaming are not supported, file size must be known before upload</li>
-<li>Maximum file size is limited to 2G for a free account, unlimited for paid accounts</li>
-<li>Storage keeps hash for all files and performs transparent deduplication, the hash algorithm is a modified SHA1</li>
-<li>If a particular file is already present in storage, one can quickly submit file hash instead of long file upload (this optimization is supported by rclone)</li>
+<li>Partial uploads or streaming are not supported, file size must be
+known before upload</li>
+<li>Maximum file size is limited to 2G for a free account, unlimited for
+paid accounts</li>
+<li>Storage keeps hash for all files and performs transparent
+deduplication, the hash algorithm is a modified SHA1</li>
+<li>If a particular file is already present in storage, one can quickly
+submit file hash instead of long file upload (this optimization is
+supported by rclone)</li>
 </ul>
-<h2 id="configuration-27">Configuration</h2>
+<h2 id="configuration-28">Configuration</h2>
 <p>Here is an example of making a mailru configuration.</p>
 <p>First create a Mail.ru Cloud account and choose a tariff.</p>
-<p>You will need to log in and create an app password for rclone. Rclone <strong>will not work</strong> with your normal username and password - it will give an error like <code>oauth2: server response missing access_token</code>.</p>
+<p>You will need to log in and create an app password for rclone. Rclone
+<strong>will not work</strong> with your normal username and password -
+it will give an error like
+<code>oauth2: server response missing access_token</code>.</p>
 <ul>
 <li>Click on your user icon in the top right</li>
 <li>Go to Security / "Пароль и безопасность"</li>
 <li>Click password for apps / "Пароли для внешних приложений"</li>
 <li>Add the password - give it a name - eg "rclone"</li>
-<li>Copy the password and use this password below - your normal login password won't work.</li>
+<li>Copy the password and use this password below - your normal login
+password won't work.</li>
 </ul>
 <p>Now run</p>
 <pre><code>rclone config</code></pre>
@@ -27207,24 +39776,44 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>Configuration of this backend does not require a local web browser. You can use the configured backend as shown below:</p>
+<p>Configuration of this backend does not require a local web browser.
+You can use the configured backend as shown below:</p>
 <p>See top level directories</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>Make a new directory</p>
 <pre><code>rclone mkdir remote:directory</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls remote:directory</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote path, deleting any excess files in the path.</p>
+<p>Sync <code>/home/local/directory</code> to the remote path, deleting
+any excess files in the path.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:directory</code></pre>
-<h3 id="modification-times-and-hashes-11">Modification times and hashes</h3>
-<p>Files support a modification time attribute with up to 1 second precision. Directories do not have a modification time, which is shown as "Jan 1 1970".</p>
-<p>File hashes are supported, with a custom Mail.ru algorithm based on SHA1. If file size is less than or equal to the SHA1 block size (20 bytes), its hash is simply its data right-padded with zero bytes. Hashes of a larger file is computed as a SHA1 of the file data bytes concatenated with a decimal representation of the data length.</p>
+<h3 id="modification-times-and-hashes-11">Modification times and
+hashes</h3>
+<p>Files support a modification time attribute with up to 1 second
+precision. Directories do not have a modification time, which is shown
+as "Jan 1 1970".</p>
+<p>File hashes are supported, with a custom Mail.ru algorithm based on
+SHA1. If file size is less than or equal to the SHA1 block size (20
+bytes), its hash is simply its data right-padded with zero bytes. Hashes
+of a larger file is computed as a SHA1 of the file data bytes
+concatenated with a decimal representation of the data length.</p>
 <h3 id="emptying-trash-1">Emptying Trash</h3>
-<p>Removing a file or directory actually moves it to the trash, which is not visible to rclone but can be seen in a web browser. The trashed file still occupies part of total quota. If you wish to empty your trash and free some quota, you can use the <code>rclone cleanup remote:</code> command, which will permanently delete all your trashed files. This command does not take any path arguments.</p>
+<p>Removing a file or directory actually moves it to the trash, which is
+not visible to rclone but can be seen in a web browser. The trashed file
+still occupies part of total quota. If you wish to empty your trash and
+free some quota, you can use the <code>rclone cleanup remote:</code>
+command, which will permanently delete all your trashed files. This
+command does not take any path arguments.</p>
 <h3 id="quota-information-2">Quota information</h3>
-<p>To view your current quota you can use the <code>rclone about remote:</code> command which will display your usage limit (quota) and the current usage.</p>
-<h3 id="restricted-filename-characters-15">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>To view your current quota you can use the
+<code>rclone about remote:</code> command which will display your usage
+limit (quota) and the current usage.</p>
+<h3 id="restricted-filename-characters-14">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -27276,8 +39865,10 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<h3 id="standard-options-28">Standard options</h3>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<h3 id="standard-options-29">Standard options</h3>
 <p>Here are the Standard options specific to mailru (Mail.ru Cloud).</p>
 <h4 id="mailru-client-id">--mailru-client-id</h4>
 <p>OAuth Client Id.</p>
@@ -27310,8 +39901,12 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="mailru-pass">--mailru-pass</h4>
 <p>Password.</p>
-<p>This must be an app password - rclone will not work with your normal password. See the Configuration section in the docs for how to make an app password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>This must be an app password - rclone will not work with your normal
+password. See the Configuration section in the docs for how to make an
+app password.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass</li>
@@ -27321,7 +39916,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="mailru-speedup-enable">--mailru-speedup-enable</h4>
 <p>Skip full upload if there is another file with same data hash.</p>
-<p>This feature is called "speedup" or "put by hash". It is especially efficient in case of generally available files like popular books, video or audio clips, because files are searched by hash in all accounts of all mailru users. It is meaningless and ineffective if source file is unique or encrypted. Please note that rclone may need local memory and disk space to calculate content hash in advance and decide whether full upload is required. Also, if rclone does not know file size in advance (e.g. in case of streaming or partial uploads), it will not even try this optimization.</p>
+<p>This feature is called "speedup" or "put by hash". It is especially
+efficient in case of generally available files like popular books, video
+or audio clips, because files are searched by hash in all accounts of
+all mailru users. It is meaningless and ineffective if source file is
+unique or encrypted. Please note that rclone may need local memory and
+disk space to calculate content hash in advance and decide whether full
+upload is required. Also, if rclone does not know file size in advance
+(e.g. in case of streaming or partial uploads), it will not even try
+this optimization.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: speedup_enable</li>
@@ -27340,7 +39943,7 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-28">Advanced options</h3>
+<h3 id="advanced-options-29">Advanced options</h3>
 <p>Here are the Advanced options specific to mailru (Mail.ru Cloud).</p>
 <h4 id="mailru-token">--mailru-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
@@ -27371,15 +39974,19 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="mailru-speedup-file-patterns">--mailru-speedup-file-patterns</h4>
-<p>Comma separated list of file name patterns eligible for speedup (put by hash).</p>
-<p>Patterns are case insensitive and can contain '*' or '?' meta characters.</p>
+<h4
+id="mailru-speedup-file-patterns">--mailru-speedup-file-patterns</h4>
+<p>Comma separated list of file name patterns eligible for speedup (put
+by hash).</p>
+<p>Patterns are case insensitive and can contain '*' or '?' meta
+characters.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: speedup_file_patterns</li>
 <li>Env Var: RCLONE_MAILRU_SPEEDUP_FILE_PATTERNS</li>
 <li>Type: string</li>
-<li>Default: "<em>.mkv,</em>.avi,<em>.mp4,</em>.mp3,<em>.zip,</em>.gz,<em>.rar,</em>.pdf"</li>
+<li>Default:
+"<em>.mkv,</em>.avi,<em>.mp4,</em>.mp3,<em>.zip,</em>.gz,<em>.rar,</em>.pdf"</li>
 <li>Examples:
 <ul>
 <li>""
@@ -27401,8 +40008,10 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul>
 <h4 id="mailru-speedup-max-disk">--mailru-speedup-max-disk</h4>
-<p>This option allows you to disable speedup (put by hash) for large files.</p>
-<p>Reason is that preliminary hashing can exhaust your RAM or disk space.</p>
+<p>This option allows you to disable speedup (put by hash) for large
+files.</p>
+<p>Reason is that preliminary hashing can exhaust your RAM or disk
+space.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: speedup_max_disk</li>
@@ -27421,12 +40030,14 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 <li>"3G"
 <ul>
-<li>Choose this option if you have less than 3Gb free on local disk.</li>
+<li>Choose this option if you have less than 3Gb free on local
+disk.</li>
 </ul></li>
 </ul></li>
 </ul>
 <h4 id="mailru-speedup-max-memory">--mailru-speedup-max-memory</h4>
-<p>Files larger than the size given below will always be hashed on disk.</p>
+<p>Files larger than the size given below will always be hashed on
+disk.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: speedup_max_memory</li>
@@ -27437,7 +40048,8 @@ y/e/d&gt; y</code></pre>
 <ul>
 <li>"0"
 <ul>
-<li>Preliminary hashing will always be done in a temporary disk location.</li>
+<li>Preliminary hashing will always be done in a temporary disk
+location.</li>
 </ul></li>
 <li>"32M"
 <ul>
@@ -27471,7 +40083,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="mailru-user-agent">--mailru-user-agent</h4>
 <p>HTTP user agent used internally by client.</p>
-<p>Defaults to "rclone/VERSION" or "--user-agent" provided on command line.</p>
+<p>Defaults to "rclone/VERSION" or "--user-agent" provided on command
+line.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: user_agent</li>
@@ -27481,7 +40094,11 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="mailru-quirks">--mailru-quirks</h4>
 <p>Comma separated list of internal maintenance flags.</p>
-<p>This option must not be used by an ordinary user. It is intended only to facilitate remote troubleshooting of backend issues. Strict meaning of flags is not documented and not guaranteed to persist between releases. Quirks will be removed when the backend grows stable. Supported quirks: atomicmkdir binlist unknowndirs</p>
+<p>This option must not be used by an ordinary user. It is intended only
+to facilitate remote troubleshooting of backend issues. Strict meaning
+of flags is not documented and not guaranteed to persist between
+releases. Quirks will be removed when the backend grows stable.
+Supported quirks: atomicmkdir binlist unknowndirs</p>
 <p>Properties:</p>
 <ul>
 <li>Config: quirks</li>
@@ -27491,13 +40108,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="mailru-encoding">--mailru-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_MAILRU_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="mailru-description">--mailru-description</h4>
 <p>Description of the remote.</p>
@@ -27509,15 +40128,25 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-22">Limitations</h2>
-<p>File size limits depend on your account. A single file size is limited by 2G for a free account and unlimited for paid tariffs. Please refer to the Mail.ru site for the total uploaded size limits.</p>
-<p>Note that Mailru is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
+<p>File size limits depend on your account. A single file size is
+limited by 2G for a free account and unlimited for paid tariffs. Please
+refer to the Mail.ru site for the total uploaded size limits.</p>
+<p>Note that Mailru is case insensitive so you can't have a file called
+"Hello.doc" and one called "hello.doc".</p>
 <h1 id="mega">Mega</h1>
-<p><a href="https://mega.nz/">Mega</a> is a cloud storage and file hosting service known for its security feature where all files are encrypted locally before they are uploaded. This prevents anyone (including employees of Mega) from accessing the files without knowledge of the key used for encryption.</p>
-<p>This is an rclone backend for Mega which supports the file transfer features of Mega using the same client side encryption.</p>
+<p><a href="https://mega.nz/">Mega</a> is a cloud storage and file
+hosting service known for its security feature where all files are
+encrypted locally before they are uploaded. This prevents anyone
+(including employees of Mega) from accessing the files without knowledge
+of the key used for encryption.</p>
+<p>This is an rclone backend for Mega which supports the file transfer
+features of Mega using the same client side encryption.</p>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-28">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-29">Configuration</h2>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -27555,7 +40184,9 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p><strong>NOTE:</strong> The encryption keys need to have been already generated after a regular login via the browser, otherwise attempting to use the credentials in <code>rclone</code> will fail.</p>
+<p><strong>NOTE:</strong> The encryption keys need to have been already
+generated after a regular login via the browser, otherwise attempting to
+use the credentials in <code>rclone</code> will fail.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your Mega</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -27563,9 +40194,11 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an Mega directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-12">Modification times and hashes</h3>
+<h3 id="modification-times-and-hashes-12">Modification times and
+hashes</h3>
 <p>Mega does not support modification times or hashes yet.</p>
-<h3 id="restricted-filename-characters-16">Restricted filename characters</h3>
+<h3 id="restricted-filename-characters-15">Restricted filename
+characters</h3>
 <table>
 <thead>
 <tr class="header">
@@ -27587,37 +40220,81 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="duplicated-files-3">Duplicated files</h3>
-<p>Mega can have two files with exactly the same name and path (unlike a normal file system).</p>
-<p>Duplicated files cause problems with the syncing and you will see messages in the log about duplicates.</p>
+<p>Mega can have two files with exactly the same name and path (unlike a
+normal file system).</p>
+<p>Duplicated files cause problems with the syncing and you will see
+messages in the log about duplicates.</p>
 <p>Use <code>rclone dedupe</code> to fix duplicated files.</p>
 <h3 id="failure-to-log-in">Failure to log-in</h3>
 <h4 id="object-not-found">Object not found</h4>
-<p>If you are connecting to your Mega remote for the first time, to test access and synchronization, you may receive an error such as</p>
+<p>If you are connecting to your Mega remote for the first time, to test
+access and synchronization, you may receive an error such as</p>
 <pre><code>Failed to create file system for &quot;my-mega-remote:&quot;: 
 couldn&#39;t login: Object (typically, node or user) not found</code></pre>
-<p>The diagnostic steps often recommended in the <a href="https://forum.rclone.org/search?q=mega">rclone forum</a> start with the <strong>MEGAcmd</strong> utility. Note that this refers to the official C++ command from https://github.com/meganz/MEGAcmd and not the go language built command from t3rm1n4l/megacmd that is no longer maintained.</p>
-<p>Follow the instructions for installing MEGAcmd and try accessing your remote as they recommend. You can establish whether or not you can log in using MEGAcmd, and obtain diagnostic information to help you, and search or work with others in the forum.</p>
+<p>The diagnostic steps often recommended in the <a
+href="https://forum.rclone.org/search?q=mega">rclone forum</a> start
+with the <strong>MEGAcmd</strong> utility. Note that this refers to the
+official C++ command from https://github.com/meganz/MEGAcmd and not the
+go language built command from t3rm1n4l/megacmd that is no longer
+maintained.</p>
+<p>Follow the instructions for installing MEGAcmd and try accessing your
+remote as they recommend. You can establish whether or not you can log
+in using MEGAcmd, and obtain diagnostic information to help you, and
+search or work with others in the forum.</p>
 <pre><code>MEGA CMD&gt; login me@example.com
 Password:
 Fetching nodes ...
 Loading transfers from local cache
 Login complete as me@example.com
 me@example.com:/$ </code></pre>
-<p>Note that some have found issues with passwords containing special characters. If you can not log on with rclone, but MEGAcmd logs on just fine, then consider changing your password temporarily to pure alphanumeric characters, in case that helps.</p>
-<h4 id="repeated-commands-blocks-access">Repeated commands blocks access</h4>
-<p>Mega remotes seem to get blocked (reject logins) under "heavy use". We haven't worked out the exact blocking rules but it seems to be related to fast paced, successive rclone commands.</p>
-<p>For example, executing this command 90 times in a row <code>rclone link remote:file</code> will cause the remote to become "blocked". This is not an abnormal situation, for example if you wish to get the public links of a directory with hundred of files... After more or less a week, the remote will remote accept rclone logins normally again.</p>
-<p>You can mitigate this issue by mounting the remote it with <code>rclone mount</code>. This will log-in when mounting and a log-out when unmounting only. You can also run <code>rclone rcd</code> and then use <code>rclone rc</code> to run the commands over the API to avoid logging in each time.</p>
-<p>Rclone does not currently close mega sessions (you can see them in the web interface), however closing the sessions does not solve the issue.</p>
-<p>If you space rclone commands by 3 seconds it will avoid blocking the remote. We haven't identified the exact blocking rules, so perhaps one could execute the command 80 times without waiting and avoid blocking by waiting 3 seconds, then continuing...</p>
-<p>Note that this has been observed by trial and error and might not be set in stone.</p>
-<p>Other tools seem not to produce this blocking effect, as they use a different working approach (state-based, using sessionIDs instead of log-in) which isn't compatible with the current stateless rclone approach.</p>
-<p>Note that once blocked, the use of other tools (such as megacmd) is not a sure workaround: following megacmd login times have been observed in succession for blocked remote: 7 minutes, 20 min, 30min, 30 min, 30min. Web access looks unaffected though.</p>
-<p>Investigation is continuing in relation to workarounds based on timeouts, pacers, retrials and tpslimits - if you discover something relevant, please post on the forum.</p>
-<p>So, if rclone was working nicely and suddenly you are unable to log-in and you are sure the user and the password are correct, likely you have got the remote blocked for a while.</p>
-<h3 id="standard-options-29">Standard options</h3>
+<p>Note that some have found issues with passwords containing special
+characters. If you can not log on with rclone, but MEGAcmd logs on just
+fine, then consider changing your password temporarily to pure
+alphanumeric characters, in case that helps.</p>
+<h4 id="repeated-commands-blocks-access">Repeated commands blocks
+access</h4>
+<p>Mega remotes seem to get blocked (reject logins) under "heavy use".
+We haven't worked out the exact blocking rules but it seems to be
+related to fast paced, successive rclone commands.</p>
+<p>For example, executing this command 90 times in a row
+<code>rclone link remote:file</code> will cause the remote to become
+"blocked". This is not an abnormal situation, for example if you wish to
+get the public links of a directory with hundred of files... After more
+or less a week, the remote will remote accept rclone logins normally
+again.</p>
+<p>You can mitigate this issue by mounting the remote it with
+<code>rclone mount</code>. This will log-in when mounting and a log-out
+when unmounting only. You can also run <code>rclone rcd</code> and then
+use <code>rclone rc</code> to run the commands over the API to avoid
+logging in each time.</p>
+<p>Rclone does not currently close mega sessions (you can see them in
+the web interface), however closing the sessions does not solve the
+issue.</p>
+<p>If you space rclone commands by 3 seconds it will avoid blocking the
+remote. We haven't identified the exact blocking rules, so perhaps one
+could execute the command 80 times without waiting and avoid blocking by
+waiting 3 seconds, then continuing...</p>
+<p>Note that this has been observed by trial and error and might not be
+set in stone.</p>
+<p>Other tools seem not to produce this blocking effect, as they use a
+different working approach (state-based, using sessionIDs instead of
+log-in) which isn't compatible with the current stateless rclone
+approach.</p>
+<p>Note that once blocked, the use of other tools (such as megacmd) is
+not a sure workaround: following megacmd login times have been observed
+in succession for blocked remote: 7 minutes, 20 min, 30min, 30 min,
+30min. Web access looks unaffected though.</p>
+<p>Investigation is continuing in relation to workarounds based on
+timeouts, pacers, retrials and tpslimits - if you discover something
+relevant, please post on the forum.</p>
+<p>So, if rclone was working nicely and suddenly you are unable to
+log-in and you are sure the user and the password are correct, likely
+you have got the remote blocked for a while.</p>
+<h3 id="standard-options-30">Standard options</h3>
 <p>Here are the Standard options specific to mega (Mega).</p>
 <h4 id="mega-user">--mega-user</h4>
 <p>User name.</p>
@@ -27630,7 +40307,9 @@ me@example.com:/$ </code></pre>
 </ul>
 <h4 id="mega-pass">--mega-pass</h4>
 <p>Password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass</li>
@@ -27638,11 +40317,12 @@ me@example.com:/$ </code></pre>
 <li>Type: string</li>
 <li>Required: true</li>
 </ul>
-<h3 id="advanced-options-29">Advanced options</h3>
+<h3 id="advanced-options-30">Advanced options</h3>
 <p>Here are the Advanced options specific to mega (Mega).</p>
 <h4 id="mega-debug">--mega-debug</h4>
 <p>Output more debug from Mega.</p>
-<p>If this flag is set (along with -vv) it will print further debugging information from the mega backend.</p>
+<p>If this flag is set (along with -vv) it will print further debugging
+information from the mega backend.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: debug</li>
@@ -27652,7 +40332,9 @@ me@example.com:/$ </code></pre>
 </ul>
 <h4 id="mega-hard-delete">--mega-hard-delete</h4>
 <p>Delete files permanently rather than putting them into the trash.</p>
-<p>Normally the mega backend will put all deletions into the trash rather than permanently deleting them. If you specify this then rclone will permanently delete objects instead.</p>
+<p>Normally the mega backend will put all deletions into the trash
+rather than permanently deleting them. If you specify this then rclone
+will permanently delete objects instead.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: hard_delete</li>
@@ -27662,7 +40344,11 @@ me@example.com:/$ </code></pre>
 </ul>
 <h4 id="mega-use-https">--mega-use-https</h4>
 <p>Use HTTPS for transfers.</p>
-<p>MEGA uses plain text HTTP connections by default. Some ISPs throttle HTTP connections, this causes transfers to become very slow. Enabling this will force MEGA to use HTTPS for all transfers. HTTPS is normally not necessary since all data is already encrypted anyway. Enabling it will increase CPU usage and add network overhead.</p>
+<p>MEGA uses plain text HTTP connections by default. Some ISPs throttle
+HTTP connections, this causes transfers to become very slow. Enabling
+this will force MEGA to use HTTPS for all transfers. HTTPS is normally
+not necessary since all data is already encrypted anyway. Enabling it
+will increase CPU usage and add network overhead.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_https</li>
@@ -27672,7 +40358,8 @@ me@example.com:/$ </code></pre>
 </ul>
 <h4 id="mega-encoding">--mega-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -27690,15 +40377,30 @@ me@example.com:/$ </code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="process-killed">Process <code>killed</code></h3>
-<p>On accounts with large files or something else, memory usage can significantly increase when executing list/sync instructions. When running on cloud providers (like AWS with EC2), check if the instance type has sufficient memory/CPU to execute the commands. Use the resource monitoring tools to inspect after sending the commands. Look <a href="https://forum.rclone.org/t/rclone-with-mega-appears-to-work-only-in-some-accounts/40233/4">at this issue</a>.</p>
+<p>On accounts with large files or something else, memory usage can
+significantly increase when executing list/sync instructions. When
+running on cloud providers (like AWS with EC2), check if the instance
+type has sufficient memory/CPU to execute the commands. Use the resource
+monitoring tools to inspect after sending the commands. Look <a
+href="https://forum.rclone.org/t/rclone-with-mega-appears-to-work-only-in-some-accounts/40233/4">at
+this issue</a>.</p>
 <h2 id="limitations-23">Limitations</h2>
-<p>This backend uses the <a href="https://github.com/t3rm1n4l/go-mega">go-mega go library</a> which is an opensource go library implementing the Mega API. There doesn't appear to be any documentation for the mega protocol beyond the <a href="https://github.com/meganz/sdk">mega C++ SDK</a> source code so there are likely quite a few errors still remaining in this library.</p>
+<p>This backend uses the <a
+href="https://github.com/t3rm1n4l/go-mega">go-mega go library</a> which
+is an opensource go library implementing the Mega API. There doesn't
+appear to be any documentation for the mega protocol beyond the <a
+href="https://github.com/meganz/sdk">mega C++ SDK</a> source code so
+there are likely quite a few errors still remaining in this library.</p>
 <p>Mega allows duplicate files which may confuse rclone.</p>
 <h1 id="memory">Memory</h1>
-<p>The memory backend is an in RAM backend. It does not persist its data - use the local backend for that.</p>
-<p>The memory backend behaves like a bucket-based remote (e.g. like s3). Because it has no parameters you can just use it with the <code>:memory:</code> remote name.</p>
-<h2 id="configuration-29">Configuration</h2>
-<p>You can configure it as a remote like this with <code>rclone config</code> too if you want to:</p>
+<p>The memory backend is an in RAM backend. It does not persist its data
+- use the local backend for that.</p>
+<p>The memory backend behaves like a bucket-based remote (e.g. like s3).
+Because it has no parameters you can just use it with the
+<code>:memory:</code> remote name.</p>
+<h2 id="configuration-30">Configuration</h2>
+<p>You can configure it as a remote like this with
+<code>rclone config</code> too if you want to:</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -27725,16 +40427,23 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>Because the memory backend isn't persistent it is most useful for testing or with an rclone server or rclone mount, e.g.</p>
+<p>Because the memory backend isn't persistent it is most useful for
+testing or with an rclone server or rclone mount, e.g.</p>
 <pre><code>rclone mount :memory: /mnt/tmp
 rclone serve webdav :memory:
 rclone serve sftp :memory:</code></pre>
-<h3 id="modification-times-and-hashes-13">Modification times and hashes</h3>
-<p>The memory backend supports MD5 hashes and modification times accurate to 1 nS.</p>
-<h3 id="restricted-filename-characters-17">Restricted filename characters</h3>
-<p>The memory backend replaces the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a>.</p>
-<h3 id="advanced-options-30">Advanced options</h3>
-<p>Here are the Advanced options specific to memory (In memory object storage system.).</p>
+<h3 id="modification-times-and-hashes-13">Modification times and
+hashes</h3>
+<p>The memory backend supports MD5 hashes and modification times
+accurate to 1 nS.</p>
+<h3 id="restricted-filename-characters-16">Restricted filename
+characters</h3>
+<p>The memory backend replaces the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a>.</p>
+<h3 id="advanced-options-31">Advanced options</h3>
+<p>Here are the Advanced options specific to memory (In memory object
+storage system.).</p>
 <h4 id="memory-description">--memory-description</h4>
 <p>Description of the remote.</p>
 <p>Properties:</p>
@@ -27745,13 +40454,25 @@ rclone serve sftp :memory:</code></pre>
 <li>Required: false</li>
 </ul>
 <h1 id="akamai-netstorage">Akamai NetStorage</h1>
-<p>Paths are specified as <code>remote:</code> You may put subdirectories in too, e.g. <code>remote:/path/to/dir</code>. If you have a CP code you can use that as the folder after the domain such as &lt;domain&gt;/&lt;cpcode&gt;/&lt;internal directories within cpcode&gt;.</p>
-<p>For example, this is commonly configured with or without a CP code: * <strong>With a CP code</strong>. <code>[your-domain-prefix]-nsu.akamaihd.net/123456/subdirectory/</code> * <strong>Without a CP code</strong>. <code>[your-domain-prefix]-nsu.akamaihd.net</code></p>
-<p>See all buckets rclone lsd remote: The initial setup for Netstorage involves getting an account and secret. Use <code>rclone config</code> to walk you through the setup process.</p>
-<h2 id="configuration-30">Configuration</h2>
-<p>Here's an example of how to make a remote called <code>ns1</code>.</p>
+<p>Paths are specified as <code>remote:</code> You may put
+subdirectories in too, e.g. <code>remote:/path/to/dir</code>. If you
+have a CP code you can use that as the folder after the domain such as
+&lt;domain&gt;/&lt;cpcode&gt;/&lt;internal directories within
+cpcode&gt;.</p>
+<p>For example, this is commonly configured with or without a CP code: *
+<strong>With a CP code</strong>.
+<code>[your-domain-prefix]-nsu.akamaihd.net/123456/subdirectory/</code>
+* <strong>Without a CP code</strong>.
+<code>[your-domain-prefix]-nsu.akamaihd.net</code></p>
+<p>See all buckets rclone lsd remote: The initial setup for Netstorage
+involves getting an account and secret. Use <code>rclone config</code>
+to walk you through the setup process.</p>
+<h2 id="configuration-31">Configuration</h2>
+<p>Here's an example of how to make a remote called
+<code>ns1</code>.</p>
 <ol type="1">
-<li>To begin the interactive configuration process, enter this command:</li>
+<li>To begin the interactive configuration process, enter this
+command:</li>
 </ol>
 <pre><code>rclone config</code></pre>
 <ol start="2" type="1">
@@ -27762,11 +40483,13 @@ d) Delete remote
 q) Quit config
 e/n/d/q&gt; n</code></pre>
 <ol start="3" type="1">
-<li>For this example, enter <code>ns1</code> when you reach the name&gt; prompt.</li>
+<li>For this example, enter <code>ns1</code> when you reach the name&gt;
+prompt.</li>
 </ol>
 <pre><code>name&gt; ns1</code></pre>
 <ol start="4" type="1">
-<li>Enter <code>netstorage</code> as the type of storage to configure.</li>
+<li>Enter <code>netstorage</code> as the type of storage to
+configure.</li>
 </ol>
 <pre><code>Type of storage to configure.
 Enter a string value. Press Enter for the default (&quot;&quot;).
@@ -27775,7 +40498,9 @@ XX / NetStorage
    \ &quot;netstorage&quot;
 Storage&gt; netstorage</code></pre>
 <ol start="5" type="1">
-<li>Select between the HTTP or HTTPS protocol. Most users should choose HTTPS, which is the default. HTTP is provided primarily for debugging purposes.</li>
+<li>Select between the HTTP or HTTPS protocol. Most users should choose
+HTTPS, which is the default. HTTP is provided primarily for debugging
+purposes.</li>
 </ol>
 <pre><code>Enter a string value. Press Enter for the default (&quot;&quot;).
 Choose a number from below, or type in your own value
@@ -27785,7 +40510,9 @@ Choose a number from below, or type in your own value
    \ &quot;https&quot;
 protocol&gt; 1</code></pre>
 <ol start="6" type="1">
-<li>Specify your NetStorage host, CP code, and any necessary content paths using this format: <code>&lt;domain&gt;/&lt;cpcode&gt;/&lt;content&gt;/</code></li>
+<li>Specify your NetStorage host, CP code, and any necessary content
+paths using this format:
+<code>&lt;domain&gt;/&lt;cpcode&gt;/&lt;content&gt;/</code></li>
 </ol>
 <pre><code>Enter a string value. Press Enter for the default (&quot;&quot;).
 host&gt; baseball-nsu.akamaihd.net/123456/content/</code></pre>
@@ -27795,7 +40522,10 @@ host&gt; baseball-nsu.akamaihd.net/123456/content/</code></pre>
 <pre><code>Enter a string value. Press Enter for the default (&quot;&quot;).
 account&gt; username</code></pre>
 <ol start="8" type="1">
-<li>Set the Netstorage account secret/G2O key which will be used for authentication purposes. Select the <code>y</code> option to set your own password then enter your secret. Note: The secret is stored in the <code>rclone.conf</code> file with hex-encoded encryption.</li>
+<li>Set the Netstorage account secret/G2O key which will be used for
+authentication purposes. Select the <code>y</code> option to set your
+own password then enter your secret. Note: The secret is stored in the
+<code>rclone.conf</code> file with hex-encoded encryption.</li>
 </ol>
 <pre><code>y) Yes type in my own password
 g) Generate random password
@@ -27820,47 +40550,113 @@ d) Delete this remote
 y/e/d&gt; y</code></pre>
 <p>This remote is called <code>ns1</code> and can now be used.</p>
 <h2 id="example-operations">Example operations</h2>
-<p>Get started with rclone and NetStorage with these examples. For additional rclone commands, visit https://rclone.org/commands/.</p>
-<h3 id="see-contents-of-a-directory-in-your-project">See contents of a directory in your project</h3>
+<p>Get started with rclone and NetStorage with these examples. For
+additional rclone commands, visit https://rclone.org/commands/.</p>
+<h3 id="see-contents-of-a-directory-in-your-project">See contents of a
+directory in your project</h3>
 <pre><code>rclone lsd ns1:/974012/testing/</code></pre>
-<h3 id="sync-the-contents-local-with-remote">Sync the contents local with remote</h3>
+<h3 id="sync-the-contents-local-with-remote">Sync the contents local
+with remote</h3>
 <pre><code>rclone sync . ns1:/974012/testing/</code></pre>
-<h3 id="upload-local-content-to-remote">Upload local content to remote</h3>
+<h3 id="upload-local-content-to-remote">Upload local content to
+remote</h3>
 <pre><code>rclone copy notes.txt ns1:/974012/testing/</code></pre>
 <h3 id="delete-content-on-remote">Delete content on remote</h3>
 <pre><code>rclone delete ns1:/974012/testing/notes.txt</code></pre>
-<h3 id="move-or-copy-content-between-cp-codes.">Move or copy content between CP codes.</h3>
-<p>Your credentials must have access to two CP codes on the same remote. You can't perform operations between different remotes.</p>
+<h3 id="move-or-copy-content-between-cp-codes.">Move or copy content
+between CP codes.</h3>
+<p>Your credentials must have access to two CP codes on the same remote.
+You can't perform operations between different remotes.</p>
 <pre><code>rclone move ns1:/974012/testing/notes.txt ns1:/974450/testing2/</code></pre>
 <h2 id="features-2">Features</h2>
 <h3 id="symlink-support">Symlink Support</h3>
-<p>The Netstorage backend changes the rclone <code>--links, -l</code> behavior. When uploading, instead of creating the .rclonelink file, use the "symlink" API in order to create the corresponding symlink on the remote. The .rclonelink file will not be created, the upload will be intercepted and only the symlink file that matches the source file name with no suffix will be created on the remote.</p>
-<p>This will effectively allow commands like copy/copyto, move/moveto and sync to upload from local to remote and download from remote to local directories with symlinks. Due to internal rclone limitations, it is not possible to upload an individual symlink file to any remote backend. You can always use the "backend symlink" command to create a symlink on the NetStorage server, refer to "symlink" section below.</p>
-<p>Individual symlink files on the remote can be used with the commands like "cat" to print the destination name, or "delete" to delete symlink, or copy, copy/to and move/moveto to download from the remote to local. Note: individual symlink files on the remote should be specified including the suffix .rclonelink.</p>
-<p><strong>Note</strong>: No file with the suffix .rclonelink should ever exist on the server since it is not possible to actually upload/create a file with .rclonelink suffix with rclone, it can only exist if it is manually created through a non-rclone method on the remote.</p>
-<h3 id="implicit-vs.-explicit-directories">Implicit vs. Explicit Directories</h3>
+<p>The Netstorage backend changes the rclone <code>--links, -l</code>
+behavior. When uploading, instead of creating the .rclonelink file, use
+the "symlink" API in order to create the corresponding symlink on the
+remote. The .rclonelink file will not be created, the upload will be
+intercepted and only the symlink file that matches the source file name
+with no suffix will be created on the remote.</p>
+<p>This will effectively allow commands like copy/copyto, move/moveto
+and sync to upload from local to remote and download from remote to
+local directories with symlinks. Due to internal rclone limitations, it
+is not possible to upload an individual symlink file to any remote
+backend. You can always use the "backend symlink" command to create a
+symlink on the NetStorage server, refer to "symlink" section below.</p>
+<p>Individual symlink files on the remote can be used with the commands
+like "cat" to print the destination name, or "delete" to delete symlink,
+or copy, copy/to and move/moveto to download from the remote to local.
+Note: individual symlink files on the remote should be specified
+including the suffix .rclonelink.</p>
+<p><strong>Note</strong>: No file with the suffix .rclonelink should
+ever exist on the server since it is not possible to actually
+upload/create a file with .rclonelink suffix with rclone, it can only
+exist if it is manually created through a non-rclone method on the
+remote.</p>
+<h3 id="implicit-vs.-explicit-directories">Implicit vs. Explicit
+Directories</h3>
 <p>With NetStorage, directories can exist in one of two forms:</p>
 <ol type="1">
-<li><strong>Explicit Directory</strong>. This is an actual, physical directory that you have created in a storage group.</li>
-<li><strong>Implicit Directory</strong>. This refers to a directory within a path that has not been physically created. For example, during upload of a file, nonexistent subdirectories can be specified in the target path. NetStorage creates these as "implicit." While the directories aren't physically created, they exist implicitly and the noted path is connected with the uploaded file.</li>
+<li><strong>Explicit Directory</strong>. This is an actual, physical
+directory that you have created in a storage group.</li>
+<li><strong>Implicit Directory</strong>. This refers to a directory
+within a path that has not been physically created. For example, during
+upload of a file, nonexistent subdirectories can be specified in the
+target path. NetStorage creates these as "implicit." While the
+directories aren't physically created, they exist implicitly and the
+noted path is connected with the uploaded file.</li>
 </ol>
-<p>Rclone will intercept all file uploads and mkdir commands for the NetStorage remote and will explicitly issue the mkdir command for each directory in the uploading path. This will help with the interoperability with the other Akamai services such as SFTP and the Content Management Shell (CMShell). Rclone will not guarantee correctness of operations with implicit directories which might have been created as a result of using an upload API directly.</p>
-<h3 id="fast-list-listr-support"><code>--fast-list</code> / ListR support</h3>
-<p>NetStorage remote supports the ListR feature by using the "list" NetStorage API action to return a lexicographical list of all objects within the specified CP code, recursing into subdirectories as they're encountered.</p>
+<p>Rclone will intercept all file uploads and mkdir commands for the
+NetStorage remote and will explicitly issue the mkdir command for each
+directory in the uploading path. This will help with the
+interoperability with the other Akamai services such as SFTP and the
+Content Management Shell (CMShell). Rclone will not guarantee
+correctness of operations with implicit directories which might have
+been created as a result of using an upload API directly.</p>
+<h3 id="fast-list-listr-support"><code>--fast-list</code> / ListR
+support</h3>
+<p>NetStorage remote supports the ListR feature by using the "list"
+NetStorage API action to return a lexicographical list of all objects
+within the specified CP code, recursing into subdirectories as they're
+encountered.</p>
 <ul>
-<li><p><strong>Rclone will use the ListR method for some commands by default</strong>. Commands such as <code>lsf -R</code> will use ListR by default. To disable this, include the <code>--disable listR</code> option to use the non-recursive method of listing objects.</p></li>
-<li><p><strong>Rclone will not use the ListR method for some commands</strong>. Commands such as <code>sync</code> don't use ListR by default. To force using the ListR method, include the <code>--fast-list</code> option.</p></li>
+<li><p><strong>Rclone will use the ListR method for some commands by
+default</strong>. Commands such as <code>lsf -R</code> will use ListR by
+default. To disable this, include the <code>--disable listR</code>
+option to use the non-recursive method of listing objects.</p></li>
+<li><p><strong>Rclone will not use the ListR method for some
+commands</strong>. Commands such as <code>sync</code> don't use ListR by
+default. To force using the ListR method, include the
+<code>--fast-list</code> option.</p></li>
 </ul>
-<p>There are pros and cons of using the ListR method, refer to <a href="https://rclone.org/docs/#fast-list">rclone documentation</a>. In general, the sync command over an existing deep tree on the remote will run faster with the "--fast-list" flag but with extra memory usage as a side effect. It might also result in higher CPU utilization but the whole task can be completed faster.</p>
-<p><strong>Note</strong>: There is a known limitation that "lsf -R" will display number of files in the directory and directory size as -1 when ListR method is used. The workaround is to pass "--disable listR" flag if these numbers are important in the output.</p>
+<p>There are pros and cons of using the ListR method, refer to <a
+href="https://rclone.org/docs/#fast-list">rclone documentation</a>. In
+general, the sync command over an existing deep tree on the remote will
+run faster with the "--fast-list" flag but with extra memory usage as a
+side effect. It might also result in higher CPU utilization but the
+whole task can be completed faster.</p>
+<p><strong>Note</strong>: There is a known limitation that "lsf -R" will
+display number of files in the directory and directory size as -1 when
+ListR method is used. The workaround is to pass "--disable listR" flag
+if these numbers are important in the output.</p>
 <h3 id="purge-1">Purge</h3>
-<p>NetStorage remote supports the purge feature by using the "quick-delete" NetStorage API action. The quick-delete action is disabled by default for security reasons and can be enabled for the account through the Akamai portal. Rclone will first try to use quick-delete action for the purge command and if this functionality is disabled then will fall back to a standard delete method.</p>
-<p><strong>Note</strong>: Read the <a href="https://learn.akamai.com/en-us/webhelp/netstorage/netstorage-http-api-developer-guide/GUID-15836617-9F50-405A-833C-EA2556756A30.html">NetStorage Usage API</a> for considerations when using "quick-delete". In general, using quick-delete method will not delete the tree immediately and objects targeted for quick-delete may still be accessible.</p>
-<h3 id="standard-options-30">Standard options</h3>
-<p>Here are the Standard options specific to netstorage (Akamai NetStorage).</p>
+<p>NetStorage remote supports the purge feature by using the
+"quick-delete" NetStorage API action. The quick-delete action is
+disabled by default for security reasons and can be enabled for the
+account through the Akamai portal. Rclone will first try to use
+quick-delete action for the purge command and if this functionality is
+disabled then will fall back to a standard delete method.</p>
+<p><strong>Note</strong>: Read the <a
+href="https://learn.akamai.com/en-us/webhelp/netstorage/netstorage-http-api-developer-guide/GUID-15836617-9F50-405A-833C-EA2556756A30.html">NetStorage
+Usage API</a> for considerations when using "quick-delete". In general,
+using quick-delete method will not delete the tree immediately and
+objects targeted for quick-delete may still be accessible.</p>
+<h3 id="standard-options-31">Standard options</h3>
+<p>Here are the Standard options specific to netstorage (Akamai
+NetStorage).</p>
 <h4 id="netstorage-host">--netstorage-host</h4>
 <p>Domain+path of NetStorage host to connect to.</p>
-<p>Format should be <code>&lt;domain&gt;/&lt;internal folders&gt;</code></p>
+<p>Format should be
+<code>&lt;domain&gt;/&lt;internal folders&gt;</code></p>
 <p>Properties:</p>
 <ul>
 <li>Config: host</li>
@@ -27879,8 +40675,11 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="netstorage-secret">--netstorage-secret</h4>
 <p>Set the NetStorage account secret/G2O key for authentication.</p>
-<p>Please choose the 'y' option to set your own password then enter your secret.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>Please choose the 'y' option to set your own password then enter your
+secret.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: secret</li>
@@ -27888,11 +40687,13 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: true</li>
 </ul>
-<h3 id="advanced-options-31">Advanced options</h3>
-<p>Here are the Advanced options specific to netstorage (Akamai NetStorage).</p>
+<h3 id="advanced-options-32">Advanced options</h3>
+<p>Here are the Advanced options specific to netstorage (Akamai
+NetStorage).</p>
 <h4 id="netstorage-protocol">--netstorage-protocol</h4>
 <p>Select between HTTP or HTTPS protocol.</p>
-<p>Most users should choose HTTPS, which is the default. HTTP is provided primarily for debugging purposes.</p>
+<p>Most users should choose HTTPS, which is the default. HTTP is
+provided primarily for debugging purposes.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: protocol</li>
@@ -27925,20 +40726,33 @@ y/e/d&gt; y</code></pre>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="du">du</h3>
 <p>Return disk usage information for a specified directory</p>
 <pre><code>rclone backend du remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>The usage information returned, includes the targeted directory as well as all files stored in any sub-directories that may exist.</p>
+<p>The usage information returned, includes the targeted directory as
+well as all files stored in any sub-directories that may exist.</p>
 <h3 id="symlink">symlink</h3>
-<p>You can create a symbolic link in ObjectStore with the symlink action.</p>
+<p>You can create a symbolic link in ObjectStore with the symlink
+action.</p>
 <pre><code>rclone backend symlink remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>The desired path location (including applicable sub-directories) ending in the object that will be the target of the symlink (for example, /links/mylink). Include the file extension for the object, if applicable. <code>rclone backend symlink &lt;src&gt; &lt;path&gt;</code></p>
+<p>The desired path location (including applicable sub-directories)
+ending in the object that will be the target of the symlink (for
+example, /links/mylink). Include the file extension for the object, if
+applicable.
+<code>rclone backend symlink &lt;src&gt; &lt;path&gt;</code></p>
 <h1 id="microsoft-azure-blob-storage">Microsoft Azure Blob Storage</h1>
-<p>Paths are specified as <code>remote:container</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:container/path/to/dir</code>.</p>
-<h2 id="configuration-31">Configuration</h2>
-<p>Here is an example of making a Microsoft Azure Blob Storage configuration. For a remote called <code>remote</code>. First run:</p>
+<p>Paths are specified as <code>remote:container</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g.
+<code>remote:container/path/to/dir</code>.</p>
+<h2 id="configuration-32">Configuration</h2>
+<p>Here is an example of making a Microsoft Azure Blob Storage
+configuration. For a remote called <code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -27978,18 +40792,41 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone mkdir remote:container</code></pre>
 <p>List the contents of a container</p>
 <pre><code>rclone ls remote:container</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote container, deleting any excess files in the container.</p>
+<p>Sync <code>/home/local/directory</code> to the remote container,
+deleting any excess files in the container.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:container</code></pre>
 <h3 id="fast-list-5">--fast-list</h3>
-<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
-<h3 id="modification-times-and-hashes-14">Modification times and hashes</h3>
-<p>The modification time is stored as metadata on the object with the <code>mtime</code> key. It is stored using RFC3339 Format time with nanosecond precision. The metadata is supplied during directory listings so there is no performance overhead to using it.</p>
-<p>If you wish to use the Azure standard <code>LastModified</code> time stored on the object as the modified time, then use the <code>--use-server-modtime</code> flag. Note that rclone can't set <code>LastModified</code>, so using the <code>--update</code> flag when syncing is recommended if using <code>--use-server-modtime</code>.</p>
-<p>MD5 hashes are stored with blobs. However blobs that were uploaded in chunks only have an MD5 if the source remote was capable of MD5 hashes, e.g. the local disk.</p>
+<p>This remote supports <code>--fast-list</code> which allows you to use
+fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details.</p>
+<h3 id="modification-times-and-hashes-14">Modification times and
+hashes</h3>
+<p>The modification time is stored as metadata on the object with the
+<code>mtime</code> key. It is stored using RFC3339 Format time with
+nanosecond precision. The metadata is supplied during directory listings
+so there is no performance overhead to using it.</p>
+<p>If you wish to use the Azure standard <code>LastModified</code> time
+stored on the object as the modified time, then use the
+<code>--use-server-modtime</code> flag. Note that rclone can't set
+<code>LastModified</code>, so using the <code>--update</code> flag when
+syncing is recommended if using <code>--use-server-modtime</code>.</p>
+<p>MD5 hashes are stored with blobs. However blobs that were uploaded in
+chunks only have an MD5 if the source remote was capable of MD5 hashes,
+e.g. the local disk.</p>
 <h3 id="performance-1">Performance</h3>
-<p>When uploading large files, increasing the value of <code>--azureblob-upload-concurrency</code> will increase performance at the cost of using more memory. The default of 16 is set quite conservatively to use less memory. It maybe be necessary raise it to 64 or higher to fully utilize a 1 GBit/s link with a single file transfer.</p>
-<h3 id="restricted-filename-characters-18">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>When uploading large files, increasing the value of
+<code>--azureblob-upload-concurrency</code> will increase performance at
+the cost of using more memory. The default of 16 is set quite
+conservatively to use less memory. It maybe be necessary raise it to 64
+or higher to fully utilize a 1 GBit/s link with a single file
+transfer.</p>
+<h3 id="restricted-filename-characters-17">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -28011,7 +40848,8 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
+<p>File names can also not end with the following characters. These only
+get replaced if they are the last character in the name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -28028,11 +40866,15 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="authentication">Authentication</h3>
-<p>There are a number of ways of supplying credentials for Azure Blob Storage. Rclone tries them in the order of the sections below.</p>
+<p>There are a number of ways of supplying credentials for Azure Blob
+Storage. Rclone tries them in the order of the sections below.</p>
 <h4 id="env-auth">Env Auth</h4>
-<p>If the <code>env_auth</code> config parameter is <code>true</code> then rclone will pull credentials from the environment or runtime.</p>
+<p>If the <code>env_auth</code> config parameter is <code>true</code>
+then rclone will pull credentials from the environment or runtime.</p>
 <p>It tries these authentication methods in this order:</p>
 <ol type="1">
 <li>Environment Variables</li>
@@ -28040,44 +40882,73 @@ y/e/d&gt; y</code></pre>
 <li>Azure CLI credentials (as used by the az tool)</li>
 </ol>
 <p>These are described in the following sections</p>
-<h5 id="env-auth-1.-environment-variables">Env Auth: 1. Environment Variables</h5>
-<p>If <code>env_auth</code> is set and environment variables are present rclone authenticates a service principal with a secret or certificate, or a user with a password, depending on which environment variable are set. It reads configuration from these variables, in the following order:</p>
+<h5 id="env-auth-1.-environment-variables">Env Auth: 1. Environment
+Variables</h5>
+<p>If <code>env_auth</code> is set and environment variables are present
+rclone authenticates a service principal with a secret or certificate,
+or a user with a password, depending on which environment variable are
+set. It reads configuration from these variables, in the following
+order:</p>
 <ol type="1">
 <li>Service principal with client secret
 <ul>
-<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
+<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant.
+Also called its "directory" ID.</li>
 <li><code>AZURE_CLIENT_ID</code>: the service principal's client ID</li>
-<li><code>AZURE_CLIENT_SECRET</code>: one of the service principal's client secrets</li>
+<li><code>AZURE_CLIENT_SECRET</code>: one of the service principal's
+client secrets</li>
 </ul></li>
 <li>Service principal with certificate
 <ul>
-<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
+<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant.
+Also called its "directory" ID.</li>
 <li><code>AZURE_CLIENT_ID</code>: the service principal's client ID</li>
-<li><code>AZURE_CLIENT_CERTIFICATE_PATH</code>: path to a PEM or PKCS12 certificate file including the private key.</li>
-<li><code>AZURE_CLIENT_CERTIFICATE_PASSWORD</code>: (optional) password for the certificate file.</li>
-<li><code>AZURE_CLIENT_SEND_CERTIFICATE_CHAIN</code>: (optional) Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to "true" or "1", authentication requests include the x5c header.</li>
+<li><code>AZURE_CLIENT_CERTIFICATE_PATH</code>: path to a PEM or PKCS12
+certificate file including the private key.</li>
+<li><code>AZURE_CLIENT_CERTIFICATE_PASSWORD</code>: (optional) password
+for the certificate file.</li>
+<li><code>AZURE_CLIENT_SEND_CERTIFICATE_CHAIN</code>: (optional)
+Specifies whether an authentication request will include an x5c header
+to support subject name / issuer based authentication. When set to
+"true" or "1", authentication requests include the x5c header.</li>
 </ul></li>
 <li>User with username and password
 <ul>
-<li><code>AZURE_TENANT_ID</code>: (optional) tenant to authenticate in. Defaults to "organizations".</li>
-<li><code>AZURE_CLIENT_ID</code>: client ID of the application the user will authenticate to</li>
-<li><code>AZURE_USERNAME</code>: a username (usually an email address)</li>
+<li><code>AZURE_TENANT_ID</code>: (optional) tenant to authenticate in.
+Defaults to "organizations".</li>
+<li><code>AZURE_CLIENT_ID</code>: client ID of the application the user
+will authenticate to</li>
+<li><code>AZURE_USERNAME</code>: a username (usually an email
+address)</li>
 <li><code>AZURE_PASSWORD</code>: the user's password</li>
 </ul></li>
 <li>Workload Identity
 <ul>
 <li><code>AZURE_TENANT_ID</code>: Tenant to authenticate in.</li>
-<li><code>AZURE_CLIENT_ID</code>: Client ID of the application the user will authenticate to.</li>
-<li><code>AZURE_FEDERATED_TOKEN_FILE</code>: Path to projected service account token file.</li>
-<li><code>AZURE_AUTHORITY_HOST</code>: Authority of an Azure Active Directory endpoint (default: login.microsoftonline.com).</li>
+<li><code>AZURE_CLIENT_ID</code>: Client ID of the application the user
+will authenticate to.</li>
+<li><code>AZURE_FEDERATED_TOKEN_FILE</code>: Path to projected service
+account token file.</li>
+<li><code>AZURE_AUTHORITY_HOST</code>: Authority of an Azure Active
+Directory endpoint (default: login.microsoftonline.com).</li>
 </ul></li>
 </ol>
-<h5 id="env-auth-2.-managed-service-identity-credentials">Env Auth: 2. Managed Service Identity Credentials</h5>
-<p>When using Managed Service Identity if the VM(SS) on which this program is running has a system-assigned identity, it will be used by default. If the resource has no system-assigned but exactly one user-assigned identity, the user-assigned identity will be used by default.</p>
-<p>If the resource has multiple user-assigned identities you will need to unset <code>env_auth</code> and set <code>use_msi</code> instead. See the <a href="#use_msi"><code>use_msi</code> section</a>.</p>
-<h5 id="env-auth-3.-azure-cli-credentials-as-used-by-the-az-tool">Env Auth: 3. Azure CLI credentials (as used by the az tool)</h5>
-<p>Credentials created with the <code>az</code> tool can be picked up using <code>env_auth</code>.</p>
-<p>For example if you were to login with a service principal like this:</p>
+<h5 id="env-auth-2.-managed-service-identity-credentials">Env Auth: 2.
+Managed Service Identity Credentials</h5>
+<p>When using Managed Service Identity if the VM(SS) on which this
+program is running has a system-assigned identity, it will be used by
+default. If the resource has no system-assigned but exactly one
+user-assigned identity, the user-assigned identity will be used by
+default.</p>
+<p>If the resource has multiple user-assigned identities you will need
+to unset <code>env_auth</code> and set <code>use_msi</code> instead. See
+the <a href="#use_msi"><code>use_msi</code> section</a>.</p>
+<h5 id="env-auth-3.-azure-cli-credentials-as-used-by-the-az-tool">Env
+Auth: 3. Azure CLI credentials (as used by the az tool)</h5>
+<p>Credentials created with the <code>az</code> tool can be picked up
+using <code>env_auth</code>.</p>
+<p>For example if you were to login with a service principal like
+this:</p>
 <pre><code>az login --service-principal -u XXX -p XXX --tenant XXX</code></pre>
 <p>Then you could access rclone resources like this:</p>
 <pre><code>rclone lsf :azureblob,env_auth,account=ACCOUNT:CONTAINER</code></pre>
@@ -28086,61 +40957,112 @@ y/e/d&gt; y</code></pre>
 <p>Which is analogous to using the <code>az</code> tool:</p>
 <pre><code>az storage blob list --container-name CONTAINER --account-name ACCOUNT --auth-mode login</code></pre>
 <h4 id="account-and-shared-key">Account and Shared Key</h4>
-<p>This is the most straight forward and least flexible way. Just fill in the <code>account</code> and <code>key</code> lines and leave the rest blank.</p>
+<p>This is the most straight forward and least flexible way. Just fill
+in the <code>account</code> and <code>key</code> lines and leave the
+rest blank.</p>
 <h4 id="sas-url">SAS URL</h4>
 <p>This can be an account level SAS URL or container level SAS URL.</p>
-<p>To use it leave <code>account</code> and <code>key</code> blank and fill in <code>sas_url</code>.</p>
-<p>An account level SAS URL or container level SAS URL can be obtained from the Azure portal or the Azure Storage Explorer. To get a container level SAS URL right click on a container in the Azure Blob explorer in the Azure portal.</p>
-<p>If you use a container level SAS URL, rclone operations are permitted only on a particular container, e.g.</p>
+<p>To use it leave <code>account</code> and <code>key</code> blank and
+fill in <code>sas_url</code>.</p>
+<p>An account level SAS URL or container level SAS URL can be obtained
+from the Azure portal or the Azure Storage Explorer. To get a container
+level SAS URL right click on a container in the Azure Blob explorer in
+the Azure portal.</p>
+<p>If you use a container level SAS URL, rclone operations are permitted
+only on a particular container, e.g.</p>
 <pre><code>rclone ls azureblob:container</code></pre>
-<p>You can also list the single container from the root. This will only show the container specified by the SAS URL.</p>
+<p>You can also list the single container from the root. This will only
+show the container specified by the SAS URL.</p>
 <pre><code>$ rclone lsd azureblob:
 container/</code></pre>
-<p>Note that you can't see or access any other containers - this will fail</p>
+<p>Note that you can't see or access any other containers - this will
+fail</p>
 <pre><code>rclone ls azureblob:othercontainer</code></pre>
-<p>Container level SAS URLs are useful for temporarily allowing third parties access to a single container or putting credentials into an untrusted environment such as a CI build server.</p>
-<h4 id="service-principal-with-client-secret">Service principal with client secret</h4>
-<p>If these variables are set, rclone will authenticate with a service principal with a client secret.</p>
+<p>Container level SAS URLs are useful for temporarily allowing third
+parties access to a single container or putting credentials into an
+untrusted environment such as a CI build server.</p>
+<h4 id="service-principal-with-client-secret">Service principal with
+client secret</h4>
+<p>If these variables are set, rclone will authenticate with a service
+principal with a client secret.</p>
 <ul>
-<li><code>tenant</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
+<li><code>tenant</code>: ID of the service principal's tenant. Also
+called its "directory" ID.</li>
 <li><code>client_id</code>: the service principal's client ID</li>
-<li><code>client_secret</code>: one of the service principal's client secrets</li>
+<li><code>client_secret</code>: one of the service principal's client
+secrets</li>
 </ul>
-<p>The credentials can also be placed in a file using the <code>service_principal_file</code> configuration option.</p>
-<h4 id="service-principal-with-certificate">Service principal with certificate</h4>
-<p>If these variables are set, rclone will authenticate with a service principal with certificate.</p>
+<p>The credentials can also be placed in a file using the
+<code>service_principal_file</code> configuration option.</p>
+<h4 id="service-principal-with-certificate">Service principal with
+certificate</h4>
+<p>If these variables are set, rclone will authenticate with a service
+principal with certificate.</p>
 <ul>
-<li><code>tenant</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
+<li><code>tenant</code>: ID of the service principal's tenant. Also
+called its "directory" ID.</li>
 <li><code>client_id</code>: the service principal's client ID</li>
-<li><code>client_certificate_path</code>: path to a PEM or PKCS12 certificate file including the private key.</li>
-<li><code>client_certificate_password</code>: (optional) password for the certificate file.</li>
-<li><code>client_send_certificate_chain</code>: (optional) Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to "true" or "1", authentication requests include the x5c header.</li>
+<li><code>client_certificate_path</code>: path to a PEM or PKCS12
+certificate file including the private key.</li>
+<li><code>client_certificate_password</code>: (optional) password for
+the certificate file.</li>
+<li><code>client_send_certificate_chain</code>: (optional) Specifies
+whether an authentication request will include an x5c header to support
+subject name / issuer based authentication. When set to "true" or "1",
+authentication requests include the x5c header.</li>
 </ul>
-<p><strong>NB</strong> <code>client_certificate_password</code> must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
-<h4 id="user-with-username-and-password">User with username and password</h4>
-<p>If these variables are set, rclone will authenticate with username and password.</p>
+<p><strong>NB</strong> <code>client_certificate_password</code> must be
+obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
+<h4 id="user-with-username-and-password">User with username and
+password</h4>
+<p>If these variables are set, rclone will authenticate with username
+and password.</p>
 <ul>
-<li><code>tenant</code>: (optional) tenant to authenticate in. Defaults to "organizations".</li>
-<li><code>client_id</code>: client ID of the application the user will authenticate to</li>
+<li><code>tenant</code>: (optional) tenant to authenticate in. Defaults
+to "organizations".</li>
+<li><code>client_id</code>: client ID of the application the user will
+authenticate to</li>
 <li><code>username</code>: a username (usually an email address)</li>
 <li><code>password</code>: the user's password</li>
 </ul>
-<p>Microsoft doesn't recommend this kind of authentication, because it's less secure than other authentication flows. This method is not interactive, so it isn't compatible with any form of multi-factor authentication, and the application must already have user or admin consent. This credential can only authenticate work and school accounts; it can't authenticate Microsoft accounts.</p>
-<p><strong>NB</strong> <code>password</code> must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>Microsoft doesn't recommend this kind of authentication, because it's
+less secure than other authentication flows. This method is not
+interactive, so it isn't compatible with any form of multi-factor
+authentication, and the application must already have user or admin
+consent. This credential can only authenticate work and school accounts;
+it can't authenticate Microsoft accounts.</p>
+<p><strong>NB</strong> <code>password</code> must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <h4 id="use_msi">Managed Service Identity Credentials</h4>
-<p>If <code>use_msi</code> is set then managed service identity credentials are used. This authentication only works when running in an Azure service. <code>env_auth</code> needs to be unset to use this.</p>
-<p>However if you have multiple user identities to choose from these must be explicitly specified using exactly one of the <code>msi_object_id</code>, <code>msi_client_id</code>, or <code>msi_mi_res_id</code> parameters.</p>
-<p>If none of <code>msi_object_id</code>, <code>msi_client_id</code>, or <code>msi_mi_res_id</code> is set, this is is equivalent to using <code>env_auth</code>.</p>
+<p>If <code>use_msi</code> is set then managed service identity
+credentials are used. This authentication only works when running in an
+Azure service. <code>env_auth</code> needs to be unset to use this.</p>
+<p>However if you have multiple user identities to choose from these
+must be explicitly specified using exactly one of the
+<code>msi_object_id</code>, <code>msi_client_id</code>, or
+<code>msi_mi_res_id</code> parameters.</p>
+<p>If none of <code>msi_object_id</code>, <code>msi_client_id</code>, or
+<code>msi_mi_res_id</code> is set, this is is equivalent to using
+<code>env_auth</code>.</p>
 <h4 id="anonymous">Anonymous</h4>
-<p>If you want to access resources with public anonymous access then set <code>account</code> only. You can do this without making an rclone config:</p>
+<p>If you want to access resources with public anonymous access then set
+<code>account</code> only. You can do this without making an rclone
+config:</p>
 <pre><code>rclone lsf :azureblob,account=ACCOUNT:CONTAINER</code></pre>
-<h3 id="standard-options-31">Standard options</h3>
-<p>Here are the Standard options specific to azureblob (Microsoft Azure Blob Storage).</p>
+<h3 id="standard-options-32">Standard options</h3>
+<p>Here are the Standard options specific to azureblob (Microsoft Azure
+Blob Storage).</p>
 <h4 id="azureblob-account">--azureblob-account</h4>
 <p>Azure Storage Account Name.</p>
 <p>Set this to the Azure Storage Account Name in use.</p>
-<p>Leave blank to use SAS URL or Emulator, otherwise it needs to be set.</p>
-<p>If this is blank and if env_auth is set it will be read from the environment variable <code>AZURE_STORAGE_ACCOUNT_NAME</code> if possible.</p>
+<p>Leave blank to use SAS URL or Emulator, otherwise it needs to be
+set.</p>
+<p>If this is blank and if env_auth is set it will be read from the
+environment variable <code>AZURE_STORAGE_ACCOUNT_NAME</code> if
+possible.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: account</li>
@@ -28149,8 +41071,10 @@ container/</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="azureblob-env-auth">--azureblob-env-auth</h4>
-<p>Read credentials from runtime (environment variables, CLI or MSI).</p>
-<p>See the <a href="/azureblob#authentication">authentication docs</a> for full info.</p>
+<p>Read credentials from runtime (environment variables, CLI or
+MSI).</p>
+<p>See the <a href="/azureblob#authentication">authentication docs</a>
+for full info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: env_auth</li>
@@ -28179,8 +41103,10 @@ container/</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="azureblob-tenant">--azureblob-tenant</h4>
-<p>ID of the service principal's tenant. Also called its directory ID.</p>
-<p>Set this if using - Service principal with client secret - Service principal with certificate - User with username and password</p>
+<p>ID of the service principal's tenant. Also called its directory
+ID.</p>
+<p>Set this if using - Service principal with client secret - Service
+principal with certificate - User with username and password</p>
 <p>Properties:</p>
 <ul>
 <li>Config: tenant</li>
@@ -28190,7 +41116,8 @@ container/</code></pre>
 </ul>
 <h4 id="azureblob-client-id">--azureblob-client-id</h4>
 <p>The ID of the client in use.</p>
-<p>Set this if using - Service principal with client secret - Service principal with certificate - User with username and password</p>
+<p>Set this if using - Service principal with client secret - Service
+principal with certificate - User with username and password</p>
 <p>Properties:</p>
 <ul>
 <li>Config: client_id</li>
@@ -28208,8 +41135,10 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="azureblob-client-certificate-path">--azureblob-client-certificate-path</h4>
-<p>Path to a PEM or PKCS12 certificate file including the private key.</p>
+<h4
+id="azureblob-client-certificate-path">--azureblob-client-certificate-path</h4>
+<p>Path to a PEM or PKCS12 certificate file including the private
+key.</p>
 <p>Set this if using - Service principal with certificate</p>
 <p>Properties:</p>
 <ul>
@@ -28218,11 +41147,14 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="azureblob-client-certificate-password">--azureblob-client-certificate-password</h4>
+<h4
+id="azureblob-client-certificate-password">--azureblob-client-certificate-password</h4>
 <p>Password for the certificate file (optional).</p>
 <p>Optionally set this if using - Service principal with certificate</p>
 <p>And the certificate has a password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: client_certificate_password</li>
@@ -28230,11 +41162,15 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-32">Advanced options</h3>
-<p>Here are the Advanced options specific to azureblob (Microsoft Azure Blob Storage).</p>
-<h4 id="azureblob-client-send-certificate-chain">--azureblob-client-send-certificate-chain</h4>
+<h3 id="advanced-options-33">Advanced options</h3>
+<p>Here are the Advanced options specific to azureblob (Microsoft Azure
+Blob Storage).</p>
+<h4
+id="azureblob-client-send-certificate-chain">--azureblob-client-send-certificate-chain</h4>
 <p>Send the certificate chain when using certificate auth.</p>
-<p>Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to true, authentication requests include the x5c header.</p>
+<p>Specifies whether an authentication request will include an x5c
+header to support subject name / issuer based authentication. When set
+to true, authentication requests include the x5c header.</p>
 <p>Optionally set this if using - Service principal with certificate</p>
 <p>Properties:</p>
 <ul>
@@ -28256,7 +41192,9 @@ container/</code></pre>
 <h4 id="azureblob-password">--azureblob-password</h4>
 <p>The user's password</p>
 <p>Set this if using - User with username and password</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -28264,15 +41202,25 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="azureblob-service-principal-file">--azureblob-service-principal-file</h4>
-<p>Path to file containing credentials for use with a service principal.</p>
-<p>Leave blank normally. Needed only if you want to use a service principal instead of interactive login.</p>
+<h4
+id="azureblob-service-principal-file">--azureblob-service-principal-file</h4>
+<p>Path to file containing credentials for use with a service
+principal.</p>
+<p>Leave blank normally. Needed only if you want to use a service
+principal instead of interactive login.</p>
 <pre><code>$ az ad sp create-for-rbac --name &quot;&lt;name&gt;&quot; \
   --role &quot;Storage Blob Data Owner&quot; \
   --scopes &quot;/subscriptions/&lt;subscription&gt;/resourceGroups/&lt;resource-group&gt;/providers/Microsoft.Storage/storageAccounts/&lt;storage-account&gt;/blobServices/default/containers/&lt;container&gt;&quot; \
   &gt; azure-principal.json</code></pre>
-<p>See <a href="https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli">"Create an Azure service principal"</a> and <a href="https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-rbac-cli">"Assign an Azure role for access to blob data"</a> pages for more details.</p>
-<p>It may be more convenient to put the credentials directly into the rclone config file under the <code>client_id</code>, <code>tenant</code> and <code>client_secret</code> keys instead of setting <code>service_principal_file</code>.</p>
+<p>See <a
+href="https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli">"Create
+an Azure service principal"</a> and <a
+href="https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-rbac-cli">"Assign
+an Azure role for access to blob data"</a> pages for more details.</p>
+<p>It may be more convenient to put the credentials directly into the
+rclone config file under the <code>client_id</code>, <code>tenant</code>
+and <code>client_secret</code> keys instead of setting
+<code>service_principal_file</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: service_principal_file</li>
@@ -28281,9 +41229,19 @@ container/</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="azureblob-use-msi">--azureblob-use-msi</h4>
-<p>Use a managed service identity to authenticate (only works in Azure).</p>
-<p>When true, use a <a href="https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/">managed service identity</a> to authenticate to Azure Storage instead of a SAS token or account key.</p>
-<p>If the VM(SS) on which this program is running has a system-assigned identity, it will be used by default. If the resource has no system-assigned but exactly one user-assigned identity, the user-assigned identity will be used by default. If the resource has multiple user-assigned identities, the identity to use must be explicitly specified using exactly one of the msi_object_id, msi_client_id, or msi_mi_res_id parameters.</p>
+<p>Use a managed service identity to authenticate (only works in
+Azure).</p>
+<p>When true, use a <a
+href="https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/">managed
+service identity</a> to authenticate to Azure Storage instead of a SAS
+token or account key.</p>
+<p>If the VM(SS) on which this program is running has a system-assigned
+identity, it will be used by default. If the resource has no
+system-assigned but exactly one user-assigned identity, the
+user-assigned identity will be used by default. If the resource has
+multiple user-assigned identities, the identity to use must be
+explicitly specified using exactly one of the msi_object_id,
+msi_client_id, or msi_mi_res_id parameters.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_msi</li>
@@ -28342,7 +41300,8 @@ container/</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="azureblob-upload-cutoff">--azureblob-upload-cutoff</h4>
-<p>Cutoff for switching to chunked upload (&lt;= 256 MiB) (deprecated).</p>
+<p>Cutoff for switching to chunked upload (&lt;= 256 MiB)
+(deprecated).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_cutoff</li>
@@ -28352,7 +41311,9 @@ container/</code></pre>
 </ul>
 <h4 id="azureblob-chunk-size">--azureblob-chunk-size</h4>
 <p>Upload chunk size.</p>
-<p>Note that this is stored in memory and there may be up to "--transfers" * "--azureblob-upload-concurrency" chunks stored at once in memory.</p>
+<p>Note that this is stored in memory and there may be up to
+"--transfers" * "--azureblob-upload-concurrency" chunks stored at once
+in memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -28360,12 +41321,20 @@ container/</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 4Mi</li>
 </ul>
-<h4 id="azureblob-upload-concurrency">--azureblob-upload-concurrency</h4>
+<h4
+id="azureblob-upload-concurrency">--azureblob-upload-concurrency</h4>
 <p>Concurrency for multipart uploads.</p>
-<p>This is the number of chunks of the same file that are uploaded concurrently.</p>
-<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
-<p>In tests, upload speed increases almost linearly with upload concurrency. For example to fill a gigabit pipe it may be necessary to raise this to 64. Note that this will use more memory.</p>
-<p>Note that chunks are stored in memory and there may be up to "--transfers" * "--azureblob-upload-concurrency" chunks stored at once in memory.</p>
+<p>This is the number of chunks of the same file that are uploaded
+concurrently.</p>
+<p>If you are uploading small numbers of large files over high-speed
+links and these uploads do not fully utilize your bandwidth, then
+increasing this may help to speed up the transfers.</p>
+<p>In tests, upload speed increases almost linearly with upload
+concurrency. For example to fill a gigabit pipe it may be necessary to
+raise this to 64. Note that this will use more memory.</p>
+<p>Note that chunks are stored in memory and there may be up to
+"--transfers" * "--azureblob-upload-concurrency" chunks stored at once
+in memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_concurrency</li>
@@ -28375,7 +41344,13 @@ container/</code></pre>
 </ul>
 <h4 id="azureblob-list-chunk">--azureblob-list-chunk</h4>
 <p>Size of blob list.</p>
-<p>This sets the number of blobs requested in each listing chunk. Default is the maximum, 5000. "List blobs" requests are permitted 2 minutes per megabyte to complete. If an operation is taking longer than 2 minutes per megabyte on average, it will time out ( <a href="https://docs.microsoft.com/en-us/rest/api/storageservices/setting-timeouts-for-blob-service-operations#exceptions-to-default-timeout-interval">source</a> ). This can be used to limit the number of blobs items to return, to avoid the time out.</p>
+<p>This sets the number of blobs requested in each listing chunk.
+Default is the maximum, 5000. "List blobs" requests are permitted 2
+minutes per megabyte to complete. If an operation is taking longer than
+2 minutes per megabyte on average, it will time out ( <a
+href="https://docs.microsoft.com/en-us/rest/api/storageservices/setting-timeouts-for-blob-service-operations#exceptions-to-default-timeout-interval">source</a>
+). This can be used to limit the number of blobs items to return, to
+avoid the time out.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: list_chunk</li>
@@ -28385,8 +41360,15 @@ container/</code></pre>
 </ul>
 <h4 id="azureblob-access-tier">--azureblob-access-tier</h4>
 <p>Access tier of blob: hot, cool, cold or archive.</p>
-<p>Archived blobs can be restored by setting access tier to hot, cool or cold. Leave blank if you intend to use default access tier, which is set at account level</p>
-<p>If there is no "access tier" specified, rclone doesn't apply any tier. rclone performs "Set Tier" operation on blobs while uploading, if objects are not modified, specifying "access tier" to new one will have no effect. If blobs are in "archive tier" at remote, trying to perform data transfer operations from remote will not be allowed. User should first restore by tiering blob to "Hot", "Cool" or "Cold".</p>
+<p>Archived blobs can be restored by setting access tier to hot, cool or
+cold. Leave blank if you intend to use default access tier, which is set
+at account level</p>
+<p>If there is no "access tier" specified, rclone doesn't apply any
+tier. rclone performs "Set Tier" operation on blobs while uploading, if
+objects are not modified, specifying "access tier" to new one will have
+no effect. If blobs are in "archive tier" at remote, trying to perform
+data transfer operations from remote will not be allowed. User should
+first restore by tiering blob to "Hot", "Cool" or "Cold".</p>
 <p>Properties:</p>
 <ul>
 <li>Config: access_tier</li>
@@ -28394,11 +41376,18 @@ container/</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="azureblob-archive-tier-delete">--azureblob-archive-tier-delete</h4>
+<h4
+id="azureblob-archive-tier-delete">--azureblob-archive-tier-delete</h4>
 <p>Delete archive tier blobs before overwriting.</p>
-<p>Archive tier blobs cannot be updated. So without this flag, if you attempt to update an archive tier blob, then rclone will produce the error:</p>
+<p>Archive tier blobs cannot be updated. So without this flag, if you
+attempt to update an archive tier blob, then rclone will produce the
+error:</p>
 <pre><code>can&#39;t update archive tier blob without --azureblob-archive-tier-delete</code></pre>
-<p>With this flag set then before rclone attempts to overwrite an archive tier blob, it will delete the existing blob before uploading its replacement. This has the potential for data loss if the upload fails (unlike updating a normal blob) and also may cost more since deleting archive tier blobs early may be chargable.</p>
+<p>With this flag set then before rclone attempts to overwrite an
+archive tier blob, it will delete the existing blob before uploading its
+replacement. This has the potential for data loss if the upload fails
+(unlike updating a normal blob) and also may cost more since deleting
+archive tier blobs early may be chargable.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: archive_tier_delete</li>
@@ -28408,7 +41397,10 @@ container/</code></pre>
 </ul>
 <h4 id="azureblob-disable-checksum">--azureblob-disable-checksum</h4>
 <p>Don't store MD5 checksum with object metadata.</p>
-<p>Normally rclone will calculate the MD5 checksum of the input before uploading it so it can add it to metadata on the object. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
+<p>Normally rclone will calculate the MD5 checksum of the input before
+uploading it so it can add it to metadata on the object. This is great
+for data integrity checking but can cause long delays for large files to
+start uploading.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_checksum</li>
@@ -28416,8 +41408,10 @@ container/</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="azureblob-memory-pool-flush-time">--azureblob-memory-pool-flush-time</h4>
-<p>How often internal memory buffer pools will be flushed. (no longer used)</p>
+<h4
+id="azureblob-memory-pool-flush-time">--azureblob-memory-pool-flush-time</h4>
+<p>How often internal memory buffer pools will be flushed. (no longer
+used)</p>
 <p>Properties:</p>
 <ul>
 <li>Config: memory_pool_flush_time</li>
@@ -28425,8 +41419,10 @@ container/</code></pre>
 <li>Type: Duration</li>
 <li>Default: 1m0s</li>
 </ul>
-<h4 id="azureblob-memory-pool-use-mmap">--azureblob-memory-pool-use-mmap</h4>
-<p>Whether to use mmap buffers in internal memory pool. (no longer used)</p>
+<h4
+id="azureblob-memory-pool-use-mmap">--azureblob-memory-pool-use-mmap</h4>
+<p>Whether to use mmap buffers in internal memory pool. (no longer
+used)</p>
 <p>Properties:</p>
 <ul>
 <li>Config: memory_pool_use_mmap</li>
@@ -28436,7 +41432,8 @@ container/</code></pre>
 </ul>
 <h4 id="azureblob-encoding">--azureblob-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -28456,12 +41453,14 @@ container/</code></pre>
 <ul>
 <li>""
 <ul>
-<li>The container and its blobs can be accessed only with an authorized request.</li>
+<li>The container and its blobs can be accessed only with an authorized
+request.</li>
 <li>It's a default value.</li>
 </ul></li>
 <li>"blob"
 <ul>
-<li>Blob data within this container can be read via anonymous request.</li>
+<li>Blob data within this container can be read via anonymous
+request.</li>
 </ul></li>
 <li>"container"
 <ul>
@@ -28470,9 +41469,12 @@ container/</code></pre>
 </ul></li>
 </ul>
 <h4 id="azureblob-directory-markers">--azureblob-directory-markers</h4>
-<p>Upload an empty object with a trailing slash when a new directory is created</p>
-<p>Empty folders are unsupported for bucket based remotes, this option creates an empty object ending with "/", to persist the folder.</p>
-<p>This object also has the metadata "hdi_isfolder = true" to conform to the Microsoft standard.</p>
+<p>Upload an empty object with a trailing slash when a new directory is
+created</p>
+<p>Empty folders are unsupported for bucket based remotes, this option
+creates an empty object ending with "/", to persist the folder.</p>
+<p>This object also has the metadata "hdi_isfolder = true" to conform to
+the Microsoft standard.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: directory_markers</li>
@@ -28480,9 +41482,11 @@ container/</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="azureblob-no-check-container">--azureblob-no-check-container</h4>
+<h4
+id="azureblob-no-check-container">--azureblob-no-check-container</h4>
 <p>If set, don't attempt to check the container exists or create it.</p>
-<p>This can be useful when trying to minimise the number of transactions rclone does if you know the container exists already.</p>
+<p>This can be useful when trying to minimise the number of transactions
+rclone does if you know the container exists already.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_check_container</li>
@@ -28519,7 +41523,8 @@ container/</code></pre>
 </ul></li>
 <li>"only"
 <ul>
-<li>Specify 'only' to remove only the snapshots but keep the root blob.</li>
+<li>Specify 'only' to remove only the snapshots but keep the root
+blob.</li>
 </ul></li>
 </ul></li>
 </ul>
@@ -28533,7 +41538,8 @@ container/</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="custom-upload-headers-1">Custom upload headers</h3>
-<p>You can set custom upload headers with the <code>--header-upload</code> flag.</p>
+<p>You can set custom upload headers with the
+<code>--header-upload</code> flag.</p>
 <ul>
 <li>Cache-Control</li>
 <li>Content-Disposition</li>
@@ -28543,17 +41549,38 @@ container/</code></pre>
 </ul>
 <p>Eg <code>--header-upload "Content-Type: text/potato"</code></p>
 <h2 id="limitations-24">Limitations</h2>
-<p>MD5 sums are only uploaded with chunked files if the source has an MD5 sum. This will always be the case for a local to azure copy.</p>
-<p><code>rclone about</code> is not supported by the Microsoft Azure Blob storage backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
-<h2 id="azure-storage-emulator-support">Azure Storage Emulator Support</h2>
-<p>You can run rclone with the storage emulator (usually <em>azurite</em>).</p>
-<p>To do this, just set up a new remote with <code>rclone config</code> following the instructions in the introduction and set <code>use_emulator</code> in the advanced settings as <code>true</code>. You do not need to provide a default account name nor an account key. But you can override them in the <code>account</code> and <code>key</code> options. (Prior to v1.61 they were hard coded to <em>azurite</em>'s <code>devstoreaccount1</code>.)</p>
-<p>Also, if you want to access a storage emulator instance running on a different machine, you can override the <code>endpoint</code> parameter in the advanced settings, setting it to <code>http(s)://&lt;host&gt;:&lt;port&gt;/devstoreaccount1</code> (e.g. <code>http://10.254.2.5:10000/devstoreaccount1</code>).</p>
-<h1 id="microsoft-azure-files-storage">Microsoft Azure Files Storage</h1>
-<p>Paths are specified as <code>remote:</code> You may put subdirectories in too, e.g. <code>remote:path/to/dir</code>.</p>
-<h2 id="configuration-32">Configuration</h2>
-<p>Here is an example of making a Microsoft Azure Files Storage configuration. For a remote called <code>remote</code>. First run:</p>
+<p>MD5 sums are only uploaded with chunked files if the source has an
+MD5 sum. This will always be the case for a local to azure copy.</p>
+<p><code>rclone about</code> is not supported by the Microsoft Azure
+Blob storage backend. Backends without this capability cannot determine
+free space for an rclone mount or use policy <code>mfs</code> (most free
+space) as a member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<h2 id="azure-storage-emulator-support">Azure Storage Emulator
+Support</h2>
+<p>You can run rclone with the storage emulator (usually
+<em>azurite</em>).</p>
+<p>To do this, just set up a new remote with <code>rclone config</code>
+following the instructions in the introduction and set
+<code>use_emulator</code> in the advanced settings as <code>true</code>.
+You do not need to provide a default account name nor an account key.
+But you can override them in the <code>account</code> and
+<code>key</code> options. (Prior to v1.61 they were hard coded to
+<em>azurite</em>'s <code>devstoreaccount1</code>.)</p>
+<p>Also, if you want to access a storage emulator instance running on a
+different machine, you can override the <code>endpoint</code> parameter
+in the advanced settings, setting it to
+<code>http(s)://&lt;host&gt;:&lt;port&gt;/devstoreaccount1</code> (e.g.
+<code>http://10.254.2.5:10000/devstoreaccount1</code>).</p>
+<h1 id="microsoft-azure-files-storage">Microsoft Azure Files
+Storage</h1>
+<p>Paths are specified as <code>remote:</code> You may put
+subdirectories in too, e.g. <code>remote:path/to/dir</code>.</p>
+<h2 id="configuration-33">Configuration</h2>
+<p>Here is an example of making a Microsoft Azure Files Storage
+configuration. For a remote called <code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -28626,14 +41653,25 @@ y/e/d&gt; </code></pre>
 <pre><code>rclone mkdir remote:dir</code></pre>
 <p>Recursively List the contents:</p>
 <pre><code>rclone ls remote:</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote directory, deleting any excess files in the directory.</p>
+<p>Sync <code>/home/local/directory</code> to the remote directory,
+deleting any excess files in the directory.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:dir</code></pre>
 <h3 id="modified-time">Modified time</h3>
-<p>The modified time is stored as Azure standard <code>LastModified</code> time on files</p>
+<p>The modified time is stored as Azure standard
+<code>LastModified</code> time on files</p>
 <h3 id="performance-2">Performance</h3>
-<p>When uploading large files, increasing the value of <code>--azurefiles-upload-concurrency</code> will increase performance at the cost of using more memory. The default of 16 is set quite conservatively to use less memory. It maybe be necessary raise it to 64 or higher to fully utilize a 1 GBit/s link with a single file transfer.</p>
-<h3 id="restricted-filename-characters-19">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>When uploading large files, increasing the value of
+<code>--azurefiles-upload-concurrency</code> will increase performance
+at the cost of using more memory. The default of 16 is set quite
+conservatively to use less memory. It maybe be necessary raise it to 64
+or higher to fully utilize a 1 GBit/s link with a single file
+transfer.</p>
+<h3 id="restricted-filename-characters-18">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -28685,7 +41723,8 @@ y/e/d&gt; </code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
+<p>File names can also not end with the following characters. These only
+get replaced if they are the last character in the name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -28702,13 +41741,18 @@ y/e/d&gt; </code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="hashes-1">Hashes</h3>
-<p>MD5 hashes are stored with files. Not all files will have MD5 hashes as these have to be uploaded with the file.</p>
+<p>MD5 hashes are stored with files. Not all files will have MD5 hashes
+as these have to be uploaded with the file.</p>
 <h3 id="authentication">Authentication</h3>
-<p>There are a number of ways of supplying credentials for Azure Files Storage. Rclone tries them in the order of the sections below.</p>
+<p>There are a number of ways of supplying credentials for Azure Files
+Storage. Rclone tries them in the order of the sections below.</p>
 <h4 id="env-auth-1">Env Auth</h4>
-<p>If the <code>env_auth</code> config parameter is <code>true</code> then rclone will pull credentials from the environment or runtime.</p>
+<p>If the <code>env_auth</code> config parameter is <code>true</code>
+then rclone will pull credentials from the environment or runtime.</p>
 <p>It tries these authentication methods in this order:</p>
 <ol type="1">
 <li>Environment Variables</li>
@@ -28716,94 +41760,166 @@ y/e/d&gt; </code></pre>
 <li>Azure CLI credentials (as used by the az tool)</li>
 </ol>
 <p>These are described in the following sections</p>
-<h5 id="env-auth-1.-environment-variables-1">Env Auth: 1. Environment Variables</h5>
-<p>If <code>env_auth</code> is set and environment variables are present rclone authenticates a service principal with a secret or certificate, or a user with a password, depending on which environment variable are set. It reads configuration from these variables, in the following order:</p>
+<h5 id="env-auth-1.-environment-variables-1">Env Auth: 1. Environment
+Variables</h5>
+<p>If <code>env_auth</code> is set and environment variables are present
+rclone authenticates a service principal with a secret or certificate,
+or a user with a password, depending on which environment variable are
+set. It reads configuration from these variables, in the following
+order:</p>
 <ol type="1">
 <li>Service principal with client secret
 <ul>
-<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
+<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant.
+Also called its "directory" ID.</li>
 <li><code>AZURE_CLIENT_ID</code>: the service principal's client ID</li>
-<li><code>AZURE_CLIENT_SECRET</code>: one of the service principal's client secrets</li>
+<li><code>AZURE_CLIENT_SECRET</code>: one of the service principal's
+client secrets</li>
 </ul></li>
 <li>Service principal with certificate
 <ul>
-<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
+<li><code>AZURE_TENANT_ID</code>: ID of the service principal's tenant.
+Also called its "directory" ID.</li>
 <li><code>AZURE_CLIENT_ID</code>: the service principal's client ID</li>
-<li><code>AZURE_CLIENT_CERTIFICATE_PATH</code>: path to a PEM or PKCS12 certificate file including the private key.</li>
-<li><code>AZURE_CLIENT_CERTIFICATE_PASSWORD</code>: (optional) password for the certificate file.</li>
-<li><code>AZURE_CLIENT_SEND_CERTIFICATE_CHAIN</code>: (optional) Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to "true" or "1", authentication requests include the x5c header.</li>
+<li><code>AZURE_CLIENT_CERTIFICATE_PATH</code>: path to a PEM or PKCS12
+certificate file including the private key.</li>
+<li><code>AZURE_CLIENT_CERTIFICATE_PASSWORD</code>: (optional) password
+for the certificate file.</li>
+<li><code>AZURE_CLIENT_SEND_CERTIFICATE_CHAIN</code>: (optional)
+Specifies whether an authentication request will include an x5c header
+to support subject name / issuer based authentication. When set to
+"true" or "1", authentication requests include the x5c header.</li>
 </ul></li>
 <li>User with username and password
 <ul>
-<li><code>AZURE_TENANT_ID</code>: (optional) tenant to authenticate in. Defaults to "organizations".</li>
-<li><code>AZURE_CLIENT_ID</code>: client ID of the application the user will authenticate to</li>
-<li><code>AZURE_USERNAME</code>: a username (usually an email address)</li>
+<li><code>AZURE_TENANT_ID</code>: (optional) tenant to authenticate in.
+Defaults to "organizations".</li>
+<li><code>AZURE_CLIENT_ID</code>: client ID of the application the user
+will authenticate to</li>
+<li><code>AZURE_USERNAME</code>: a username (usually an email
+address)</li>
 <li><code>AZURE_PASSWORD</code>: the user's password</li>
 </ul></li>
 <li>Workload Identity
 <ul>
 <li><code>AZURE_TENANT_ID</code>: Tenant to authenticate in.</li>
-<li><code>AZURE_CLIENT_ID</code>: Client ID of the application the user will authenticate to.</li>
-<li><code>AZURE_FEDERATED_TOKEN_FILE</code>: Path to projected service account token file.</li>
-<li><code>AZURE_AUTHORITY_HOST</code>: Authority of an Azure Active Directory endpoint (default: login.microsoftonline.com).</li>
+<li><code>AZURE_CLIENT_ID</code>: Client ID of the application the user
+will authenticate to.</li>
+<li><code>AZURE_FEDERATED_TOKEN_FILE</code>: Path to projected service
+account token file.</li>
+<li><code>AZURE_AUTHORITY_HOST</code>: Authority of an Azure Active
+Directory endpoint (default: login.microsoftonline.com).</li>
 </ul></li>
 </ol>
-<h5 id="env-auth-2.-managed-service-identity-credentials-1">Env Auth: 2. Managed Service Identity Credentials</h5>
-<p>When using Managed Service Identity if the VM(SS) on which this program is running has a system-assigned identity, it will be used by default. If the resource has no system-assigned but exactly one user-assigned identity, the user-assigned identity will be used by default.</p>
-<p>If the resource has multiple user-assigned identities you will need to unset <code>env_auth</code> and set <code>use_msi</code> instead. See the <a href="#use_msi"><code>use_msi</code> section</a>.</p>
-<h5 id="env-auth-3.-azure-cli-credentials-as-used-by-the-az-tool-1">Env Auth: 3. Azure CLI credentials (as used by the az tool)</h5>
-<p>Credentials created with the <code>az</code> tool can be picked up using <code>env_auth</code>.</p>
-<p>For example if you were to login with a service principal like this:</p>
+<h5 id="env-auth-2.-managed-service-identity-credentials-1">Env Auth: 2.
+Managed Service Identity Credentials</h5>
+<p>When using Managed Service Identity if the VM(SS) on which this
+program is running has a system-assigned identity, it will be used by
+default. If the resource has no system-assigned but exactly one
+user-assigned identity, the user-assigned identity will be used by
+default.</p>
+<p>If the resource has multiple user-assigned identities you will need
+to unset <code>env_auth</code> and set <code>use_msi</code> instead. See
+the <a href="#use_msi"><code>use_msi</code> section</a>.</p>
+<h5 id="env-auth-3.-azure-cli-credentials-as-used-by-the-az-tool-1">Env
+Auth: 3. Azure CLI credentials (as used by the az tool)</h5>
+<p>Credentials created with the <code>az</code> tool can be picked up
+using <code>env_auth</code>.</p>
+<p>For example if you were to login with a service principal like
+this:</p>
 <pre><code>az login --service-principal -u XXX -p XXX --tenant XXX</code></pre>
 <p>Then you could access rclone resources like this:</p>
 <pre><code>rclone lsf :azurefiles,env_auth,account=ACCOUNT:</code></pre>
 <p>Or</p>
 <pre><code>rclone lsf --azurefiles-env-auth --azurefiles-account=ACCOUNT :azurefiles:</code></pre>
 <h4 id="account-and-shared-key-1">Account and Shared Key</h4>
-<p>This is the most straight forward and least flexible way. Just fill in the <code>account</code> and <code>key</code> lines and leave the rest blank.</p>
+<p>This is the most straight forward and least flexible way. Just fill
+in the <code>account</code> and <code>key</code> lines and leave the
+rest blank.</p>
 <h4 id="sas-url-1">SAS URL</h4>
-<p>To use it leave <code>account</code>, <code>key</code> and <code>connection_string</code> blank and fill in <code>sas_url</code>.</p>
+<p>To use it leave <code>account</code>, <code>key</code> and
+<code>connection_string</code> blank and fill in
+<code>sas_url</code>.</p>
 <h4 id="connection-string">Connection String</h4>
-<p>To use it leave <code>account</code>, <code>key</code> and "sas_url" blank and fill in <code>connection_string</code>.</p>
-<h4 id="service-principal-with-client-secret-1">Service principal with client secret</h4>
-<p>If these variables are set, rclone will authenticate with a service principal with a client secret.</p>
+<p>To use it leave <code>account</code>, <code>key</code> and "sas_url"
+blank and fill in <code>connection_string</code>.</p>
+<h4 id="service-principal-with-client-secret-1">Service principal with
+client secret</h4>
+<p>If these variables are set, rclone will authenticate with a service
+principal with a client secret.</p>
 <ul>
-<li><code>tenant</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
+<li><code>tenant</code>: ID of the service principal's tenant. Also
+called its "directory" ID.</li>
 <li><code>client_id</code>: the service principal's client ID</li>
-<li><code>client_secret</code>: one of the service principal's client secrets</li>
+<li><code>client_secret</code>: one of the service principal's client
+secrets</li>
 </ul>
-<p>The credentials can also be placed in a file using the <code>service_principal_file</code> configuration option.</p>
-<h4 id="service-principal-with-certificate-1">Service principal with certificate</h4>
-<p>If these variables are set, rclone will authenticate with a service principal with certificate.</p>
+<p>The credentials can also be placed in a file using the
+<code>service_principal_file</code> configuration option.</p>
+<h4 id="service-principal-with-certificate-1">Service principal with
+certificate</h4>
+<p>If these variables are set, rclone will authenticate with a service
+principal with certificate.</p>
 <ul>
-<li><code>tenant</code>: ID of the service principal's tenant. Also called its "directory" ID.</li>
+<li><code>tenant</code>: ID of the service principal's tenant. Also
+called its "directory" ID.</li>
 <li><code>client_id</code>: the service principal's client ID</li>
-<li><code>client_certificate_path</code>: path to a PEM or PKCS12 certificate file including the private key.</li>
-<li><code>client_certificate_password</code>: (optional) password for the certificate file.</li>
-<li><code>client_send_certificate_chain</code>: (optional) Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to "true" or "1", authentication requests include the x5c header.</li>
+<li><code>client_certificate_path</code>: path to a PEM or PKCS12
+certificate file including the private key.</li>
+<li><code>client_certificate_password</code>: (optional) password for
+the certificate file.</li>
+<li><code>client_send_certificate_chain</code>: (optional) Specifies
+whether an authentication request will include an x5c header to support
+subject name / issuer based authentication. When set to "true" or "1",
+authentication requests include the x5c header.</li>
 </ul>
-<p><strong>NB</strong> <code>client_certificate_password</code> must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
-<h4 id="user-with-username-and-password-1">User with username and password</h4>
-<p>If these variables are set, rclone will authenticate with username and password.</p>
+<p><strong>NB</strong> <code>client_certificate_password</code> must be
+obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
+<h4 id="user-with-username-and-password-1">User with username and
+password</h4>
+<p>If these variables are set, rclone will authenticate with username
+and password.</p>
 <ul>
-<li><code>tenant</code>: (optional) tenant to authenticate in. Defaults to "organizations".</li>
-<li><code>client_id</code>: client ID of the application the user will authenticate to</li>
+<li><code>tenant</code>: (optional) tenant to authenticate in. Defaults
+to "organizations".</li>
+<li><code>client_id</code>: client ID of the application the user will
+authenticate to</li>
 <li><code>username</code>: a username (usually an email address)</li>
 <li><code>password</code>: the user's password</li>
 </ul>
-<p>Microsoft doesn't recommend this kind of authentication, because it's less secure than other authentication flows. This method is not interactive, so it isn't compatible with any form of multi-factor authentication, and the application must already have user or admin consent. This credential can only authenticate work and school accounts; it can't authenticate Microsoft accounts.</p>
-<p><strong>NB</strong> <code>password</code> must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>Microsoft doesn't recommend this kind of authentication, because it's
+less secure than other authentication flows. This method is not
+interactive, so it isn't compatible with any form of multi-factor
+authentication, and the application must already have user or admin
+consent. This credential can only authenticate work and school accounts;
+it can't authenticate Microsoft accounts.</p>
+<p><strong>NB</strong> <code>password</code> must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <h4 id="use_msi">Managed Service Identity Credentials</h4>
-<p>If <code>use_msi</code> is set then managed service identity credentials are used. This authentication only works when running in an Azure service. <code>env_auth</code> needs to be unset to use this.</p>
-<p>However if you have multiple user identities to choose from these must be explicitly specified using exactly one of the <code>msi_object_id</code>, <code>msi_client_id</code>, or <code>msi_mi_res_id</code> parameters.</p>
-<p>If none of <code>msi_object_id</code>, <code>msi_client_id</code>, or <code>msi_mi_res_id</code> is set, this is is equivalent to using <code>env_auth</code>.</p>
-<h3 id="standard-options-32">Standard options</h3>
-<p>Here are the Standard options specific to azurefiles (Microsoft Azure Files).</p>
+<p>If <code>use_msi</code> is set then managed service identity
+credentials are used. This authentication only works when running in an
+Azure service. <code>env_auth</code> needs to be unset to use this.</p>
+<p>However if you have multiple user identities to choose from these
+must be explicitly specified using exactly one of the
+<code>msi_object_id</code>, <code>msi_client_id</code>, or
+<code>msi_mi_res_id</code> parameters.</p>
+<p>If none of <code>msi_object_id</code>, <code>msi_client_id</code>, or
+<code>msi_mi_res_id</code> is set, this is is equivalent to using
+<code>env_auth</code>.</p>
+<h3 id="standard-options-33">Standard options</h3>
+<p>Here are the Standard options specific to azurefiles (Microsoft Azure
+Files).</p>
 <h4 id="azurefiles-account">--azurefiles-account</h4>
 <p>Azure Storage Account Name.</p>
 <p>Set this to the Azure Storage Account Name in use.</p>
-<p>Leave blank to use SAS URL or connection string, otherwise it needs to be set.</p>
-<p>If this is blank and if env_auth is set it will be read from the environment variable <code>AZURE_STORAGE_ACCOUNT_NAME</code> if possible.</p>
+<p>Leave blank to use SAS URL or connection string, otherwise it needs
+to be set.</p>
+<p>If this is blank and if env_auth is set it will be read from the
+environment variable <code>AZURE_STORAGE_ACCOUNT_NAME</code> if
+possible.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: account</li>
@@ -28822,8 +41938,10 @@ y/e/d&gt; </code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="azurefiles-env-auth">--azurefiles-env-auth</h4>
-<p>Read credentials from runtime (environment variables, CLI or MSI).</p>
-<p>See the <a href="/azurefiles#authentication">authentication docs</a> for full info.</p>
+<p>Read credentials from runtime (environment variables, CLI or
+MSI).</p>
+<p>See the <a href="/azurefiles#authentication">authentication docs</a>
+for full info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: env_auth</li>
@@ -28851,7 +41969,8 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="azurefiles-connection-string">--azurefiles-connection-string</h4>
+<h4
+id="azurefiles-connection-string">--azurefiles-connection-string</h4>
 <p>Azure Files Connection String.</p>
 <p>Properties:</p>
 <ul>
@@ -28861,8 +41980,10 @@ y/e/d&gt; </code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="azurefiles-tenant">--azurefiles-tenant</h4>
-<p>ID of the service principal's tenant. Also called its directory ID.</p>
-<p>Set this if using - Service principal with client secret - Service principal with certificate - User with username and password</p>
+<p>ID of the service principal's tenant. Also called its directory
+ID.</p>
+<p>Set this if using - Service principal with client secret - Service
+principal with certificate - User with username and password</p>
 <p>Properties:</p>
 <ul>
 <li>Config: tenant</li>
@@ -28872,7 +41993,8 @@ y/e/d&gt; </code></pre>
 </ul>
 <h4 id="azurefiles-client-id">--azurefiles-client-id</h4>
 <p>The ID of the client in use.</p>
-<p>Set this if using - Service principal with client secret - Service principal with certificate - User with username and password</p>
+<p>Set this if using - Service principal with client secret - Service
+principal with certificate - User with username and password</p>
 <p>Properties:</p>
 <ul>
 <li>Config: client_id</li>
@@ -28890,8 +42012,10 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="azurefiles-client-certificate-path">--azurefiles-client-certificate-path</h4>
-<p>Path to a PEM or PKCS12 certificate file including the private key.</p>
+<h4
+id="azurefiles-client-certificate-path">--azurefiles-client-certificate-path</h4>
+<p>Path to a PEM or PKCS12 certificate file including the private
+key.</p>
 <p>Set this if using - Service principal with certificate</p>
 <p>Properties:</p>
 <ul>
@@ -28900,11 +42024,14 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="azurefiles-client-certificate-password">--azurefiles-client-certificate-password</h4>
+<h4
+id="azurefiles-client-certificate-password">--azurefiles-client-certificate-password</h4>
 <p>Password for the certificate file (optional).</p>
 <p>Optionally set this if using - Service principal with certificate</p>
 <p>And the certificate has a password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: client_certificate_password</li>
@@ -28912,11 +42039,15 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-33">Advanced options</h3>
-<p>Here are the Advanced options specific to azurefiles (Microsoft Azure Files).</p>
-<h4 id="azurefiles-client-send-certificate-chain">--azurefiles-client-send-certificate-chain</h4>
+<h3 id="advanced-options-34">Advanced options</h3>
+<p>Here are the Advanced options specific to azurefiles (Microsoft Azure
+Files).</p>
+<h4
+id="azurefiles-client-send-certificate-chain">--azurefiles-client-send-certificate-chain</h4>
 <p>Send the certificate chain when using certificate auth.</p>
-<p>Specifies whether an authentication request will include an x5c header to support subject name / issuer based authentication. When set to true, authentication requests include the x5c header.</p>
+<p>Specifies whether an authentication request will include an x5c
+header to support subject name / issuer based authentication. When set
+to true, authentication requests include the x5c header.</p>
 <p>Optionally set this if using - Service principal with certificate</p>
 <p>Properties:</p>
 <ul>
@@ -28938,7 +42069,9 @@ y/e/d&gt; </code></pre>
 <h4 id="azurefiles-password">--azurefiles-password</h4>
 <p>The user's password</p>
 <p>Set this if using - User with username and password</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -28946,16 +42079,27 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="azurefiles-service-principal-file">--azurefiles-service-principal-file</h4>
-<p>Path to file containing credentials for use with a service principal.</p>
-<p>Leave blank normally. Needed only if you want to use a service principal instead of interactive login.</p>
+<h4
+id="azurefiles-service-principal-file">--azurefiles-service-principal-file</h4>
+<p>Path to file containing credentials for use with a service
+principal.</p>
+<p>Leave blank normally. Needed only if you want to use a service
+principal instead of interactive login.</p>
 <pre><code>$ az ad sp create-for-rbac --name &quot;&lt;name&gt;&quot; \
   --role &quot;Storage Files Data Owner&quot; \
   --scopes &quot;/subscriptions/&lt;subscription&gt;/resourceGroups/&lt;resource-group&gt;/providers/Microsoft.Storage/storageAccounts/&lt;storage-account&gt;/blobServices/default/containers/&lt;container&gt;&quot; \
   &gt; azure-principal.json</code></pre>
-<p>See <a href="https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli">"Create an Azure service principal"</a> and <a href="https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-rbac-cli">"Assign an Azure role for access to files data"</a> pages for more details.</p>
-<p><strong>NB</strong> this section needs updating for Azure Files - pull requests appreciated!</p>
-<p>It may be more convenient to put the credentials directly into the rclone config file under the <code>client_id</code>, <code>tenant</code> and <code>client_secret</code> keys instead of setting <code>service_principal_file</code>.</p>
+<p>See <a
+href="https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli">"Create
+an Azure service principal"</a> and <a
+href="https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-rbac-cli">"Assign
+an Azure role for access to files data"</a> pages for more details.</p>
+<p><strong>NB</strong> this section needs updating for Azure Files -
+pull requests appreciated!</p>
+<p>It may be more convenient to put the credentials directly into the
+rclone config file under the <code>client_id</code>, <code>tenant</code>
+and <code>client_secret</code> keys instead of setting
+<code>service_principal_file</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: service_principal_file</li>
@@ -28964,9 +42108,19 @@ y/e/d&gt; </code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="azurefiles-use-msi">--azurefiles-use-msi</h4>
-<p>Use a managed service identity to authenticate (only works in Azure).</p>
-<p>When true, use a <a href="https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/">managed service identity</a> to authenticate to Azure Storage instead of a SAS token or account key.</p>
-<p>If the VM(SS) on which this program is running has a system-assigned identity, it will be used by default. If the resource has no system-assigned but exactly one user-assigned identity, the user-assigned identity will be used by default. If the resource has multiple user-assigned identities, the identity to use must be explicitly specified using exactly one of the msi_object_id, msi_client_id, or msi_mi_res_id parameters.</p>
+<p>Use a managed service identity to authenticate (only works in
+Azure).</p>
+<p>When true, use a <a
+href="https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/">managed
+service identity</a> to authenticate to Azure Storage instead of a SAS
+token or account key.</p>
+<p>If the VM(SS) on which this program is running has a system-assigned
+identity, it will be used by default. If the resource has no
+system-assigned but exactly one user-assigned identity, the
+user-assigned identity will be used by default. If the resource has
+multiple user-assigned identities, the identity to use must be
+explicitly specified using exactly one of the msi_object_id,
+msi_client_id, or msi_mi_res_id parameters.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_msi</li>
@@ -29016,7 +42170,9 @@ y/e/d&gt; </code></pre>
 </ul>
 <h4 id="azurefiles-chunk-size">--azurefiles-chunk-size</h4>
 <p>Upload chunk size.</p>
-<p>Note that this is stored in memory and there may be up to "--transfers" * "--azurefile-upload-concurrency" chunks stored at once in memory.</p>
+<p>Note that this is stored in memory and there may be up to
+"--transfers" * "--azurefile-upload-concurrency" chunks stored at once
+in memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -29024,11 +42180,17 @@ y/e/d&gt; </code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 4Mi</li>
 </ul>
-<h4 id="azurefiles-upload-concurrency">--azurefiles-upload-concurrency</h4>
+<h4
+id="azurefiles-upload-concurrency">--azurefiles-upload-concurrency</h4>
 <p>Concurrency for multipart uploads.</p>
-<p>This is the number of chunks of the same file that are uploaded concurrently.</p>
-<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
-<p>Note that chunks are stored in memory and there may be up to "--transfers" * "--azurefile-upload-concurrency" chunks stored at once in memory.</p>
+<p>This is the number of chunks of the same file that are uploaded
+concurrently.</p>
+<p>If you are uploading small numbers of large files over high-speed
+links and these uploads do not fully utilize your bandwidth, then
+increasing this may help to speed up the transfers.</p>
+<p>Note that chunks are stored in memory and there may be up to
+"--transfers" * "--azurefile-upload-concurrency" chunks stored at once
+in memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_concurrency</li>
@@ -29038,14 +42200,18 @@ y/e/d&gt; </code></pre>
 </ul>
 <h4 id="azurefiles-max-stream-size">--azurefiles-max-stream-size</h4>
 <p>Max size for streamed files.</p>
-<p>Azure files needs to know in advance how big the file will be. When rclone doesn't know it uses this value instead.</p>
-<p>This will be used when rclone is streaming data, the most common uses are:</p>
+<p>Azure files needs to know in advance how big the file will be. When
+rclone doesn't know it uses this value instead.</p>
+<p>This will be used when rclone is streaming data, the most common uses
+are:</p>
 <ul>
-<li>Uploading files with <code>--vfs-cache-mode off</code> with <code>rclone mount</code></li>
+<li>Uploading files with <code>--vfs-cache-mode off</code> with
+<code>rclone mount</code></li>
 <li>Using <code>rclone rcat</code></li>
 <li>Copying files with unknown length</li>
 </ul>
-<p>You will need this much free space in the share as the file will be this size temporarily.</p>
+<p>You will need this much free space in the share as the file will be
+this size temporarily.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: max_stream_size</li>
@@ -29055,13 +42221,15 @@ y/e/d&gt; </code></pre>
 </ul>
 <h4 id="azurefiles-encoding">--azurefiles-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_AZUREFILES_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,RightPeriod,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="azurefiles-description">--azurefiles-description</h4>
 <p>Description of the remote.</p>
@@ -29073,7 +42241,8 @@ y/e/d&gt; </code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="custom-upload-headers-2">Custom upload headers</h3>
-<p>You can set custom upload headers with the <code>--header-upload</code> flag.</p>
+<p>You can set custom upload headers with the
+<code>--header-upload</code> flag.</p>
 <ul>
 <li>Cache-Control</li>
 <li>Content-Disposition</li>
@@ -29083,13 +42252,18 @@ y/e/d&gt; </code></pre>
 </ul>
 <p>Eg <code>--header-upload "Content-Type: text/potato"</code></p>
 <h2 id="limitations-25">Limitations</h2>
-<p>MD5 sums are only uploaded with chunked files if the source has an MD5 sum. This will always be the case for a local to azure copy.</p>
+<p>MD5 sums are only uploaded with chunked files if the source has an
+MD5 sum. This will always be the case for a local to azure copy.</p>
 <h1 id="microsoft-onedrive">Microsoft OneDrive</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-33">Configuration</h2>
-<p>The initial setup for OneDrive involves getting a token from Microsoft which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-34">Configuration</h2>
+<p>The initial setup for OneDrive involves getting a token from
+Microsoft which you need to do in your browser.
+<code>rclone config</code> walks you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>e) Edit existing remote
@@ -29164,8 +42338,14 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Microsoft. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from Microsoft. This only runs from the moment it
+opens your browser to the moment you get back the verification code.
+This is on <code>http://127.0.0.1:53682/</code> and this it may require
+you to unblock it temporarily if you are running a host firewall.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your OneDrive</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -29173,47 +42353,136 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an OneDrive directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="getting-your-own-client-id-and-key">Getting your own Client ID and Key</h3>
-<p>rclone uses a default Client ID when talking to OneDrive, unless a custom <code>client_id</code> is specified in the config. The default Client ID and Key are shared by all rclone users when performing requests.</p>
-<p>You may choose to create and use your own Client ID, in case the default one does not work well for you. For example, you might see throttling.</p>
-<h4 id="creating-client-id-for-onedrive-personal">Creating Client ID for OneDrive Personal</h4>
+<h3 id="getting-your-own-client-id-and-key">Getting your own Client ID
+and Key</h3>
+<p>rclone uses a default Client ID when talking to OneDrive, unless a
+custom <code>client_id</code> is specified in the config. The default
+Client ID and Key are shared by all rclone users when performing
+requests.</p>
+<p>You may choose to create and use your own Client ID, in case the
+default one does not work well for you. For example, you might see
+throttling.</p>
+<h4 id="creating-client-id-for-onedrive-personal">Creating Client ID for
+OneDrive Personal</h4>
 <p>To create your own Client ID, please follow these steps:</p>
 <ol type="1">
-<li>Open https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade and then click <code>New registration</code>.</li>
-<li>Enter a name for your app, choose account type <code>Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)</code>, select <code>Web</code> in <code>Redirect URI</code>, then type (do not copy and paste) <code>http://localhost:53682/</code> and click Register. Copy and keep the <code>Application (client) ID</code> under the app name for later use.</li>
-<li>Under <code>manage</code> select <code>Certificates &amp; secrets</code>, click <code>New client secret</code>. Enter a description (can be anything) and set <code>Expires</code> to 24 months. Copy and keep that secret <em>Value</em> for later use (you <em>won't</em> be able to see this value afterwards).</li>
-<li>Under <code>manage</code> select <code>API permissions</code>, click <code>Add a permission</code> and select <code>Microsoft Graph</code> then select <code>delegated permissions</code>.</li>
-<li>Search and select the following permissions: <code>Files.Read</code>, <code>Files.ReadWrite</code>, <code>Files.Read.All</code>, <code>Files.ReadWrite.All</code>, <code>offline_access</code>, <code>User.Read</code> and <code>Sites.Read.All</code> (if custom access scopes are configured, select the permissions accordingly). Once selected click <code>Add permissions</code> at the bottom.</li>
+<li>Open
+https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
+and then click <code>New registration</code>.</li>
+<li>Enter a name for your app, choose account type
+<code>Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)</code>,
+select <code>Web</code> in <code>Redirect URI</code>, then type (do not
+copy and paste) <code>http://localhost:53682/</code> and click Register.
+Copy and keep the <code>Application (client) ID</code> under the app
+name for later use.</li>
+<li>Under <code>manage</code> select
+<code>Certificates &amp; secrets</code>, click
+<code>New client secret</code>. Enter a description (can be anything)
+and set <code>Expires</code> to 24 months. Copy and keep that secret
+<em>Value</em> for later use (you <em>won't</em> be able to see this
+value afterwards).</li>
+<li>Under <code>manage</code> select <code>API permissions</code>, click
+<code>Add a permission</code> and select <code>Microsoft Graph</code>
+then select <code>delegated permissions</code>.</li>
+<li>Search and select the following permissions:
+<code>Files.Read</code>, <code>Files.ReadWrite</code>,
+<code>Files.Read.All</code>, <code>Files.ReadWrite.All</code>,
+<code>offline_access</code>, <code>User.Read</code> and
+<code>Sites.Read.All</code> (if custom access scopes are configured,
+select the permissions accordingly). Once selected click
+<code>Add permissions</code> at the bottom.</li>
 </ol>
-<p>Now the application is complete. Run <code>rclone config</code> to create or edit a OneDrive remote. Supply the app ID and password as Client ID and Secret, respectively. rclone will walk you through the remaining steps.</p>
-<p>The access_scopes option allows you to configure the permissions requested by rclone. See <a href="https://docs.microsoft.com/en-us/graph/permissions-reference#files-permissions">Microsoft Docs</a> for more information about the different scopes.</p>
-<p>The <code>Sites.Read.All</code> permission is required if you need to <a href="https://github.com/rclone/rclone/pull/5883">search SharePoint sites when configuring the remote</a>. However, if that permission is not assigned, you need to exclude <code>Sites.Read.All</code> from your access scopes or set <code>disable_site_permission</code> option to true in the advanced options.</p>
-<h4 id="creating-client-id-for-onedrive-business">Creating Client ID for OneDrive Business</h4>
-<p>The steps for OneDrive Personal may or may not work for OneDrive Business, depending on the security settings of the organization. A common error is that the publisher of the App is not verified.</p>
-<p>You may try to <a href="https://docs.microsoft.com/en-us/azure/active-directory/develop/publisher-verification-overview">verify you account</a>, or try to limit the App to your organization only, as shown below.</p>
+<p>Now the application is complete. Run <code>rclone config</code> to
+create or edit a OneDrive remote. Supply the app ID and password as
+Client ID and Secret, respectively. rclone will walk you through the
+remaining steps.</p>
+<p>The access_scopes option allows you to configure the permissions
+requested by rclone. See <a
+href="https://docs.microsoft.com/en-us/graph/permissions-reference#files-permissions">Microsoft
+Docs</a> for more information about the different scopes.</p>
+<p>The <code>Sites.Read.All</code> permission is required if you need to
+<a href="https://github.com/rclone/rclone/pull/5883">search SharePoint
+sites when configuring the remote</a>. However, if that permission is
+not assigned, you need to exclude <code>Sites.Read.All</code> from your
+access scopes or set <code>disable_site_permission</code> option to true
+in the advanced options.</p>
+<h4 id="creating-client-id-for-onedrive-business">Creating Client ID for
+OneDrive Business</h4>
+<p>The steps for OneDrive Personal may or may not work for OneDrive
+Business, depending on the security settings of the organization. A
+common error is that the publisher of the App is not verified.</p>
+<p>You may try to <a
+href="https://docs.microsoft.com/en-us/azure/active-directory/develop/publisher-verification-overview">verify
+you account</a>, or try to limit the App to your organization only, as
+shown below.</p>
 <ol type="1">
 <li>Make sure to create the App with your business account.</li>
-<li>Follow the steps above to create an App. However, we need a different account type here: <code>Accounts in this organizational directory only (*** - Single tenant)</code>. Note that you can also change the account type after creating the App.</li>
-<li>Find the <a href="https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-to-find-tenant">tenant ID</a> of your organization.</li>
-<li>In the rclone config, set <code>auth_url</code> to <code>https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/authorize</code>.</li>
-<li>In the rclone config, set <code>token_url</code> to <code>https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/token</code>.</li>
+<li>Follow the steps above to create an App. However, we need a
+different account type here:
+<code>Accounts in this organizational directory only (*** - Single tenant)</code>.
+Note that you can also change the account type after creating the
+App.</li>
+<li>Find the <a
+href="https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-to-find-tenant">tenant
+ID</a> of your organization.</li>
+<li>In the rclone config, set <code>auth_url</code> to
+<code>https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/authorize</code>.</li>
+<li>In the rclone config, set <code>token_url</code> to
+<code>https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/token</code>.</li>
 </ol>
-<p>Note: If you have a special region, you may need a different host in step 4 and 5. Here are <a href="https://github.com/rclone/rclone/blob/bc23bf11db1c78c6ebbf8ea538fbebf7058b4176/backend/onedrive/onedrive.go#L86">some hints</a>.</p>
-<h3 id="modification-times-and-hashes-15">Modification times and hashes</h3>
-<p>OneDrive allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
-<p>OneDrive Personal, OneDrive for Business and Sharepoint Server support <a href="https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash">QuickXorHash</a>.</p>
-<p>Before rclone 1.62 the default hash for Onedrive Personal was <code>SHA1</code>. For rclone 1.62 and above the default for all Onedrive backends is <code>QuickXorHash</code>.</p>
-<p>Starting from July 2023 <code>SHA1</code> support is being phased out in Onedrive Personal in favour of <code>QuickXorHash</code>. If necessary the <code>--onedrive-hash-type</code> flag (or <code>hash_type</code> config option) can be used to select <code>SHA1</code> during the transition period if this is important your workflow.</p>
-<p>For all types of OneDrive you can use the <code>--checksum</code> flag.</p>
+<p>Note: If you have a special region, you may need a different host in
+step 4 and 5. Here are <a
+href="https://github.com/rclone/rclone/blob/bc23bf11db1c78c6ebbf8ea538fbebf7058b4176/backend/onedrive/onedrive.go#L86">some
+hints</a>.</p>
+<h3 id="modification-times-and-hashes-15">Modification times and
+hashes</h3>
+<p>OneDrive allows modification times to be set on objects accurate to 1
+second. These will be used to detect whether objects need syncing or
+not.</p>
+<p>OneDrive Personal, OneDrive for Business and Sharepoint Server
+support <a
+href="https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash">QuickXorHash</a>.</p>
+<p>Before rclone 1.62 the default hash for Onedrive Personal was
+<code>SHA1</code>. For rclone 1.62 and above the default for all
+Onedrive backends is <code>QuickXorHash</code>.</p>
+<p>Starting from July 2023 <code>SHA1</code> support is being phased out
+in Onedrive Personal in favour of <code>QuickXorHash</code>. If
+necessary the <code>--onedrive-hash-type</code> flag (or
+<code>hash_type</code> config option) can be used to select
+<code>SHA1</code> during the transition period if this is important your
+workflow.</p>
+<p>For all types of OneDrive you can use the <code>--checksum</code>
+flag.</p>
 <h3 id="fast-list-6">--fast-list</h3>
-<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
-<p>This must be enabled with the <code>--onedrive-delta</code> flag (or <code>delta = true</code> in the config file) as it can cause performance degradation.</p>
-<p>It does this by using the delta listing facilities of OneDrive which returns all the files in the remote very efficiently. This is much more efficient than listing directories recursively and is Microsoft's recommended way of reading all the file information from a drive.</p>
-<p>This can be useful with <code>rclone mount</code> and <a href="https://rclone.org/rc/#vfs-refresh">rclone rc vfs/refresh recursive=true</a>) to very quickly fill the mount with information about all the files.</p>
-<p>The API used for the recursive listing (<code>ListR</code>) only supports listing from the root of the drive. This will become increasingly inefficient the further away you get from the root as rclone will have to discard files outside of the directory you are using.</p>
-<p>Some commands (like <code>rclone lsf -R</code>) will use <code>ListR</code> by default - you can turn this off with <code>--disable ListR</code> if you need to.</p>
-<h3 id="restricted-filename-characters-20">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>This remote supports <code>--fast-list</code> which allows you to use
+fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details.</p>
+<p>This must be enabled with the <code>--onedrive-delta</code> flag (or
+<code>delta = true</code> in the config file) as it can cause
+performance degradation.</p>
+<p>It does this by using the delta listing facilities of OneDrive which
+returns all the files in the remote very efficiently. This is much more
+efficient than listing directories recursively and is Microsoft's
+recommended way of reading all the file information from a drive.</p>
+<p>This can be useful with <code>rclone mount</code> and <a
+href="https://rclone.org/rc/#vfs-refresh">rclone rc vfs/refresh
+recursive=true</a>) to very quickly fill the mount with information
+about all the files.</p>
+<p>The API used for the recursive listing (<code>ListR</code>) only
+supports listing from the root of the drive. This will become
+increasingly inefficient the further away you get from the root as
+rclone will have to discard files outside of the directory you are
+using.</p>
+<p>Some commands (like <code>rclone lsf -R</code>) will use
+<code>ListR</code> by default - you can turn this off with
+<code>--disable ListR</code> if you need to.</p>
+<h3 id="restricted-filename-characters-19">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -29265,7 +42534,8 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
+<p>File names can also not end with the following characters. These only
+get replaced if they are the last character in the name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -29287,7 +42557,8 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not begin with the following characters. These only get replaced if they are the first character in the name:</p>
+<p>File names can also not begin with the following characters. These
+only get replaced if they are the first character in the name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -29309,11 +42580,17 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="deleting-files-4">Deleting files</h3>
-<p>Any files you delete with rclone will end up in the trash. Microsoft doesn't provide an API to permanently delete files, nor to empty the trash, so you will have to do that with one of Microsoft's apps or via the OneDrive website.</p>
-<h3 id="standard-options-33">Standard options</h3>
-<p>Here are the Standard options specific to onedrive (Microsoft OneDrive).</p>
+<p>Any files you delete with rclone will end up in the trash. Microsoft
+doesn't provide an API to permanently delete files, nor to empty the
+trash, so you will have to do that with one of Microsoft's apps or via
+the OneDrive website.</p>
+<h3 id="standard-options-34">Standard options</h3>
+<p>Here are the Standard options specific to onedrive (Microsoft
+OneDrive).</p>
 <h4 id="onedrive-client-id">--onedrive-client-id</h4>
 <p>OAuth Client Id.</p>
 <p>Leave blank normally.</p>
@@ -29362,8 +42639,9 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-34">Advanced options</h3>
-<p>Here are the Advanced options specific to onedrive (Microsoft OneDrive).</p>
+<h3 id="advanced-options-35">Advanced options</h3>
+<p>Here are the Advanced options specific to onedrive (Microsoft
+OneDrive).</p>
 <h4 id="onedrive-token">--onedrive-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
 <p>Properties:</p>
@@ -29394,8 +42672,13 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="onedrive-chunk-size">--onedrive-chunk-size</h4>
-<p>Chunk size to upload files with - must be multiple of 320k (327,680 bytes).</p>
-<p>Above this size files will be chunked - must be multiple of 320k (327,680 bytes) and should not exceed 250M (262,144,000 bytes) else you may encounter "Microsoft.SharePoint.Client.InvalidClientQueryException: The request message is too big." Note that the chunks will be buffered into memory.</p>
+<p>Chunk size to upload files with - must be multiple of 320k (327,680
+bytes).</p>
+<p>Above this size files will be chunked - must be multiple of 320k
+(327,680 bytes) and should not exceed 250M (262,144,000 bytes) else you
+may encounter "Microsoft.SharePoint.Client.InvalidClientQueryException:
+The request message is too big." Note that the chunks will be buffered
+into memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -29423,7 +42706,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="onedrive-root-folder-id">--onedrive-root-folder-id</h4>
 <p>ID of the root folder.</p>
-<p>This isn't normally needed, but in special circumstances you might know the folder ID that you wish to access but not be able to get there through a path traversal.</p>
+<p>This isn't normally needed, but in special circumstances you might
+know the folder ID that you wish to access but not be able to get there
+through a path traversal.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_id</li>
@@ -29433,16 +42718,19 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="onedrive-access-scopes">--onedrive-access-scopes</h4>
 <p>Set scopes to be requested by rclone.</p>
-<p>Choose or manually enter a custom space separated list with all scopes, that rclone should request.</p>
+<p>Choose or manually enter a custom space separated list with all
+scopes, that rclone should request.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: access_scopes</li>
 <li>Env Var: RCLONE_ONEDRIVE_ACCESS_SCOPES</li>
 <li>Type: SpaceSepList</li>
-<li>Default: Files.Read Files.ReadWrite Files.Read.All Files.ReadWrite.All Sites.Read.All offline_access</li>
+<li>Default: Files.Read Files.ReadWrite Files.Read.All
+Files.ReadWrite.All Sites.Read.All offline_access</li>
 <li>Examples:
 <ul>
-<li>"Files.Read Files.ReadWrite Files.Read.All Files.ReadWrite.All Sites.Read.All offline_access"
+<li>"Files.Read Files.ReadWrite Files.Read.All Files.ReadWrite.All
+Sites.Read.All offline_access"
 <ul>
 <li>Read and write access to all resources</li>
 </ul></li>
@@ -29450,16 +42738,24 @@ y/e/d&gt; y</code></pre>
 <ul>
 <li>Read only access to all resources</li>
 </ul></li>
-<li>"Files.Read Files.ReadWrite Files.Read.All Files.ReadWrite.All offline_access"
+<li>"Files.Read Files.ReadWrite Files.Read.All Files.ReadWrite.All
+offline_access"
 <ul>
-<li>Read and write access to all resources, without the ability to browse SharePoint sites.</li>
+<li>Read and write access to all resources, without the ability to
+browse SharePoint sites.</li>
 <li>Same as if disable_site_permission was set to true</li>
 </ul></li>
 </ul></li>
 </ul>
-<h4 id="onedrive-disable-site-permission">--onedrive-disable-site-permission</h4>
+<h4
+id="onedrive-disable-site-permission">--onedrive-disable-site-permission</h4>
 <p>Disable the request for Sites.Read.All permission.</p>
-<p>If set to true, you will no longer be able to search for a SharePoint site when configuring drive ID, because rclone will not request Sites.Read.All permission. Set it to true if your organization didn't assign Sites.Read.All permission to the application, and your organization disallows users to consent app permission request on their own.</p>
+<p>If set to true, you will no longer be able to search for a SharePoint
+site when configuring drive ID, because rclone will not request
+Sites.Read.All permission. Set it to true if your organization didn't
+assign Sites.Read.All permission to the application, and your
+organization disallows users to consent app permission request on their
+own.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_site_permission</li>
@@ -29467,9 +42763,14 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="onedrive-expose-onenote-files">--onedrive-expose-onenote-files</h4>
+<h4
+id="onedrive-expose-onenote-files">--onedrive-expose-onenote-files</h4>
 <p>Set to make OneNote files show up in directory listings.</p>
-<p>By default, rclone will hide OneNote files in directory listings because operations like "Open" and "Update" won't work on them. But this behaviour may also prevent you from deleting them. If you want to delete OneNote files or otherwise want them to show up in directory listing, set this option.</p>
+<p>By default, rclone will hide OneNote files in directory listings
+because operations like "Open" and "Update" won't work on them. But this
+behaviour may also prevent you from deleting them. If you want to delete
+OneNote files or otherwise want them to show up in directory listing,
+set this option.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: expose_onenote_files</li>
@@ -29477,10 +42778,19 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="onedrive-server-side-across-configs">--onedrive-server-side-across-configs</h4>
+<h4
+id="onedrive-server-side-across-configs">--onedrive-server-side-across-configs</h4>
 <p>Deprecated: use --server-side-across-configs instead.</p>
-<p>Allow server-side operations (e.g. copy) to work across different onedrive configs.</p>
-<p>This will work if you are copying between two OneDrive <em>Personal</em> drives AND the files to copy are already shared between them. Additionally, it should also function for a user who has access permissions both between Onedrive for <em>business</em> and <em>SharePoint</em> under the <em>same tenant</em>, and between <em>SharePoint</em> and another <em>SharePoint</em> under the <em>same tenant</em>. In other cases, rclone will fall back to normal copy (which will be slightly slower).</p>
+<p>Allow server-side operations (e.g. copy) to work across different
+onedrive configs.</p>
+<p>This will work if you are copying between two OneDrive
+<em>Personal</em> drives AND the files to copy are already shared
+between them. Additionally, it should also function for a user who has
+access permissions both between Onedrive for <em>business</em> and
+<em>SharePoint</em> under the <em>same tenant</em>, and between
+<em>SharePoint</em> and another <em>SharePoint</em> under the <em>same
+tenant</em>. In other cases, rclone will fall back to normal copy (which
+will be slightly slower).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: server_side_across_configs</li>
@@ -29499,10 +42809,13 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="onedrive-no-versions">--onedrive-no-versions</h4>
 <p>Remove all versions on modifying operations.</p>
-<p>Onedrive for business creates versions when rclone uploads new files overwriting an existing one and when it sets the modification time.</p>
+<p>Onedrive for business creates versions when rclone uploads new files
+overwriting an existing one and when it sets the modification time.</p>
 <p>These versions take up space out of the quota.</p>
-<p>This flag checks for versions after file upload and setting modification time and removes all but the last version.</p>
-<p><strong>NB</strong> Onedrive personal can't currently delete versions so don't use this flag there.</p>
+<p>This flag checks for versions after file upload and setting
+modification time and removes all but the last version.</p>
+<p><strong>NB</strong> Onedrive personal can't currently delete versions
+so don't use this flag there.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_versions</li>
@@ -29512,8 +42825,11 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="onedrive-hard-delete">--onedrive-hard-delete</h4>
 <p>Permanently delete files on removal.</p>
-<p>Normally files will get sent to the recycle bin on deletion. Setting this flag causes them to be permanently deleted. Use with care.</p>
-<p>OneDrive personal accounts do not support the permanentDelete API, it only applies to OneDrive for Business and SharePoint document libraries.</p>
+<p>Normally files will get sent to the recycle bin on deletion. Setting
+this flag causes them to be permanently deleted. Use with care.</p>
+<p>OneDrive personal accounts do not support the permanentDelete API, it
+only applies to OneDrive for Business and SharePoint document
+libraries.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: hard_delete</li>
@@ -29539,7 +42855,8 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 <li>"organization"
 <ul>
-<li>Anyone signed into your organization (tenant) can use the link to get access.</li>
+<li>Anyone signed into your organization (tenant) can use the link to
+get access.</li>
 <li>Only available in OneDrive for Business and SharePoint.</li>
 </ul></li>
 </ul></li>
@@ -29570,7 +42887,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="onedrive-link-password">--onedrive-link-password</h4>
 <p>Set the password for links created by the link command.</p>
-<p>At the time of writing this only works with OneDrive personal paid accounts.</p>
+<p>At the time of writing this only works with OneDrive personal paid
+accounts.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: link_password</li>
@@ -29580,11 +42898,18 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="onedrive-hash-type">--onedrive-hash-type</h4>
 <p>Specify the hash in use for the backend.</p>
-<p>This specifies the hash type in use. If set to "auto" it will use the default hash which is QuickXorHash.</p>
-<p>Before rclone 1.62 an SHA1 hash was used by default for Onedrive Personal. For 1.62 and later the default is to use a QuickXorHash for all onedrive types. If an SHA1 hash is desired then set this option accordingly.</p>
-<p>From July 2023 QuickXorHash will be the only available hash for both OneDrive for Business and OneDrive Personal.</p>
+<p>This specifies the hash type in use. If set to "auto" it will use the
+default hash which is QuickXorHash.</p>
+<p>Before rclone 1.62 an SHA1 hash was used by default for Onedrive
+Personal. For 1.62 and later the default is to use a QuickXorHash for
+all onedrive types. If an SHA1 hash is desired then set this option
+accordingly.</p>
+<p>From July 2023 QuickXorHash will be the only available hash for both
+OneDrive for Business and OneDrive Personal.</p>
 <p>This can be set to "none" to not use any hashes.</p>
-<p>If the hash requested does not exist on the object, it will be returned as an empty string which is treated as a missing hash by rclone.</p>
+<p>If the hash requested does not exist on the object, it will be
+returned as an empty string which is treated as a missing hash by
+rclone.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: hash_type</li>
@@ -29621,10 +42946,14 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="onedrive-av-override">--onedrive-av-override</h4>
 <p>Allows download of files the server thinks has a virus.</p>
-<p>The onedrive/sharepoint server may check files uploaded with an Anti Virus checker. If it detects any potential viruses or malware it will block download of the file.</p>
+<p>The onedrive/sharepoint server may check files uploaded with an Anti
+Virus checker. If it detects any potential viruses or malware it will
+block download of the file.</p>
 <p>In this case you will see a message like this</p>
 <pre><code>server reports this file is infected with a virus - use --onedrive-av-override to download anyway: Infected (name of virus): 403 Forbidden: </code></pre>
-<p>If you are 100% sure you want to download this file anyway then use the --onedrive-av-override flag, or av_override = true in the config file.</p>
+<p>If you are 100% sure you want to download this file anyway then use
+the --onedrive-av-override flag, or av_override = true in the config
+file.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: av_override</li>
@@ -29633,16 +42962,28 @@ y/e/d&gt; y</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="onedrive-delta">--onedrive-delta</h4>
-<p>If set rclone will use delta listing to implement recursive listings.</p>
-<p>If this flag is set the onedrive backend will advertise <code>ListR</code> support for recursive listings.</p>
+<p>If set rclone will use delta listing to implement recursive
+listings.</p>
+<p>If this flag is set the onedrive backend will advertise
+<code>ListR</code> support for recursive listings.</p>
 <p>Setting this flag speeds up these things greatly:</p>
 <pre><code>rclone lsf -R onedrive:
 rclone size onedrive:
 rclone rc vfs/refresh recursive=true</code></pre>
-<p><strong>However</strong> the delta listing API <strong>only</strong> works at the root of the drive. If you use it not at the root then it recurses from the root and discards all the data that is not under the directory you asked for. So it will be correct but may not be very efficient.</p>
+<p><strong>However</strong> the delta listing API <strong>only</strong>
+works at the root of the drive. If you use it not at the root then it
+recurses from the root and discards all the data that is not under the
+directory you asked for. So it will be correct but may not be very
+efficient.</p>
 <p>This is why this flag is not set as the default.</p>
-<p>As a rule of thumb if nearly all of your data is under rclone's root directory (the <code>root/directory</code> in <code>onedrive:root/directory</code>) then using this flag will be be a big performance win. If your data is mostly not under the root then using this flag will be a big performance loss.</p>
-<p>It is recommended if you are mounting your onedrive at the root (or near the root when using crypt) and using rclone <code>rc vfs/refresh</code>.</p>
+<p>As a rule of thumb if nearly all of your data is under rclone's root
+directory (the <code>root/directory</code> in
+<code>onedrive:root/directory</code>) then using this flag will be be a
+big performance win. If your data is mostly not under the root then
+using this flag will be a big performance loss.</p>
+<p>It is recommended if you are mounting your onedrive at the root (or
+near the root when using crypt) and using rclone
+<code>rc vfs/refresh</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: delta</li>
@@ -29650,9 +42991,12 @@ rclone rc vfs/refresh recursive=true</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="onedrive-metadata-permissions">--onedrive-metadata-permissions</h4>
-<p>Control whether permissions should be read or written in metadata.</p>
-<p>Reading permissions metadata from files can be done quickly, but it isn't always desirable to set the permissions from the metadata.</p>
+<h4
+id="onedrive-metadata-permissions">--onedrive-metadata-permissions</h4>
+<p>Control whether permissions should be read or written in
+metadata.</p>
+<p>Reading permissions metadata from files can be done quickly, but it
+isn't always desirable to set the permissions from the metadata.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: metadata_permissions</li>
@@ -29685,13 +43029,15 @@ rclone rc vfs/refresh recursive=true</code></pre>
 </ul>
 <h4 id="onedrive-encoding">--onedrive-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_ONEDRIVE_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="onedrive-description">--onedrive-description</h4>
 <p>Description of the remote.</p>
@@ -29703,88 +43049,130 @@ rclone rc vfs/refresh recursive=true</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-13">Metadata</h3>
-<p>OneDrive supports System Metadata (not User Metadata, as of this writing) for both files and directories. Much of the metadata is read-only, and there are some differences between OneDrive Personal and Business (see table below for details).</p>
-<p>Permissions are also supported, if <code>--onedrive-metadata-permissions</code> is set. The accepted values for <code>--onedrive-metadata-permissions</code> are "<code>read</code>", "<code>write</code>", "<code>read,write</code>", and "<code>off</code>" (the default). "<code>write</code>" supports adding new permissions, updating the "role" of existing permissions, and removing permissions. Updating and removing require the Permission ID to be known, so it is recommended to use "<code>read,write</code>" instead of "<code>write</code>" if you wish to update/remove permissions.</p>
-<p>Permissions are read/written in JSON format using the same schema as the <a href="https://learn.microsoft.com/en-us/onedrive/developer/rest-api/resources/permission?view=odsp-graph-online">OneDrive API</a>, which differs slightly between OneDrive Personal and Business.</p>
+<p>OneDrive supports System Metadata (not User Metadata, as of this
+writing) for both files and directories. Much of the metadata is
+read-only, and there are some differences between OneDrive Personal and
+Business (see table below for details).</p>
+<p>Permissions are also supported, if
+<code>--onedrive-metadata-permissions</code> is set. The accepted values
+for <code>--onedrive-metadata-permissions</code> are
+"<code>read</code>", "<code>write</code>", "<code>read,write</code>",
+and "<code>off</code>" (the default). "<code>write</code>" supports
+adding new permissions, updating the "role" of existing permissions, and
+removing permissions. Updating and removing require the Permission ID to
+be known, so it is recommended to use "<code>read,write</code>" instead
+of "<code>write</code>" if you wish to update/remove permissions.</p>
+<p>Permissions are read/written in JSON format using the same schema as
+the <a
+href="https://learn.microsoft.com/en-us/onedrive/developer/rest-api/resources/permission?view=odsp-graph-online">OneDrive
+API</a>, which differs slightly between OneDrive Personal and
+Business.</p>
 <p>Example for OneDrive Personal:</p>
-<div class="sourceCode" id="cb1260"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb1260-1"><a href="#cb1260-1" aria-hidden="true"></a><span class="ot">[</span></span>
-<span id="cb1260-2"><a href="#cb1260-2" aria-hidden="true"></a>    <span class="fu">{</span></span>
-<span id="cb1260-3"><a href="#cb1260-3" aria-hidden="true"></a>        <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;1234567890ABC!123&quot;</span><span class="fu">,</span></span>
-<span id="cb1260-4"><a href="#cb1260-4" aria-hidden="true"></a>        <span class="dt">&quot;grantedTo&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1260-5"><a href="#cb1260-5" aria-hidden="true"></a>            <span class="dt">&quot;user&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1260-6"><a href="#cb1260-6" aria-hidden="true"></a>                <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;ryan@contoso.com&quot;</span></span>
-<span id="cb1260-7"><a href="#cb1260-7" aria-hidden="true"></a>            <span class="fu">},</span></span>
-<span id="cb1260-8"><a href="#cb1260-8" aria-hidden="true"></a>            <span class="dt">&quot;application&quot;</span><span class="fu">:</span> <span class="fu">{},</span></span>
-<span id="cb1260-9"><a href="#cb1260-9" aria-hidden="true"></a>            <span class="dt">&quot;device&quot;</span><span class="fu">:</span> <span class="fu">{}</span></span>
-<span id="cb1260-10"><a href="#cb1260-10" aria-hidden="true"></a>        <span class="fu">},</span></span>
-<span id="cb1260-11"><a href="#cb1260-11" aria-hidden="true"></a>        <span class="dt">&quot;invitation&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1260-12"><a href="#cb1260-12" aria-hidden="true"></a>            <span class="dt">&quot;email&quot;</span><span class="fu">:</span> <span class="st">&quot;ryan@contoso.com&quot;</span></span>
-<span id="cb1260-13"><a href="#cb1260-13" aria-hidden="true"></a>        <span class="fu">},</span></span>
-<span id="cb1260-14"><a href="#cb1260-14" aria-hidden="true"></a>        <span class="dt">&quot;link&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1260-15"><a href="#cb1260-15" aria-hidden="true"></a>            <span class="dt">&quot;webUrl&quot;</span><span class="fu">:</span> <span class="st">&quot;https://1drv.ms/t/s!1234567890ABC&quot;</span></span>
-<span id="cb1260-16"><a href="#cb1260-16" aria-hidden="true"></a>        <span class="fu">},</span></span>
-<span id="cb1260-17"><a href="#cb1260-17" aria-hidden="true"></a>        <span class="dt">&quot;roles&quot;</span><span class="fu">:</span> <span class="ot">[</span></span>
-<span id="cb1260-18"><a href="#cb1260-18" aria-hidden="true"></a>            <span class="st">&quot;read&quot;</span></span>
-<span id="cb1260-19"><a href="#cb1260-19" aria-hidden="true"></a>        <span class="ot">]</span><span class="fu">,</span></span>
-<span id="cb1260-20"><a href="#cb1260-20" aria-hidden="true"></a>        <span class="dt">&quot;shareId&quot;</span><span class="fu">:</span> <span class="st">&quot;s!1234567890ABC&quot;</span></span>
-<span id="cb1260-21"><a href="#cb1260-21" aria-hidden="true"></a>    <span class="fu">}</span></span>
-<span id="cb1260-22"><a href="#cb1260-22" aria-hidden="true"></a><span class="ot">]</span></span></code></pre></div>
+<div class="sourceCode" id="cb1263"><pre
+class="sourceCode json"><code class="sourceCode json"><span id="cb1263-1"><a href="#cb1263-1" aria-hidden="true" tabindex="-1"></a><span class="ot">[</span></span>
+<span id="cb1263-2"><a href="#cb1263-2" aria-hidden="true" tabindex="-1"></a>    <span class="fu">{</span></span>
+<span id="cb1263-3"><a href="#cb1263-3" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;1234567890ABC!123&quot;</span><span class="fu">,</span></span>
+<span id="cb1263-4"><a href="#cb1263-4" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;grantedTo&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1263-5"><a href="#cb1263-5" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;user&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1263-6"><a href="#cb1263-6" aria-hidden="true" tabindex="-1"></a>                <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;ryan@contoso.com&quot;</span></span>
+<span id="cb1263-7"><a href="#cb1263-7" aria-hidden="true" tabindex="-1"></a>            <span class="fu">},</span></span>
+<span id="cb1263-8"><a href="#cb1263-8" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;application&quot;</span><span class="fu">:</span> <span class="fu">{},</span></span>
+<span id="cb1263-9"><a href="#cb1263-9" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;device&quot;</span><span class="fu">:</span> <span class="fu">{}</span></span>
+<span id="cb1263-10"><a href="#cb1263-10" aria-hidden="true" tabindex="-1"></a>        <span class="fu">},</span></span>
+<span id="cb1263-11"><a href="#cb1263-11" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;invitation&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1263-12"><a href="#cb1263-12" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;email&quot;</span><span class="fu">:</span> <span class="st">&quot;ryan@contoso.com&quot;</span></span>
+<span id="cb1263-13"><a href="#cb1263-13" aria-hidden="true" tabindex="-1"></a>        <span class="fu">},</span></span>
+<span id="cb1263-14"><a href="#cb1263-14" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;link&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1263-15"><a href="#cb1263-15" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;webUrl&quot;</span><span class="fu">:</span> <span class="st">&quot;https://1drv.ms/t/s!1234567890ABC&quot;</span></span>
+<span id="cb1263-16"><a href="#cb1263-16" aria-hidden="true" tabindex="-1"></a>        <span class="fu">},</span></span>
+<span id="cb1263-17"><a href="#cb1263-17" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;roles&quot;</span><span class="fu">:</span> <span class="ot">[</span></span>
+<span id="cb1263-18"><a href="#cb1263-18" aria-hidden="true" tabindex="-1"></a>            <span class="st">&quot;read&quot;</span></span>
+<span id="cb1263-19"><a href="#cb1263-19" aria-hidden="true" tabindex="-1"></a>        <span class="ot">]</span><span class="fu">,</span></span>
+<span id="cb1263-20"><a href="#cb1263-20" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;shareId&quot;</span><span class="fu">:</span> <span class="st">&quot;s!1234567890ABC&quot;</span></span>
+<span id="cb1263-21"><a href="#cb1263-21" aria-hidden="true" tabindex="-1"></a>    <span class="fu">}</span></span>
+<span id="cb1263-22"><a href="#cb1263-22" aria-hidden="true" tabindex="-1"></a><span class="ot">]</span></span></code></pre></div>
 <p>Example for OneDrive Business:</p>
-<div class="sourceCode" id="cb1261"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb1261-1"><a href="#cb1261-1" aria-hidden="true"></a><span class="ot">[</span></span>
-<span id="cb1261-2"><a href="#cb1261-2" aria-hidden="true"></a>    <span class="fu">{</span></span>
-<span id="cb1261-3"><a href="#cb1261-3" aria-hidden="true"></a>        <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;48d31887-5fad-4d73-a9f5-3c356e68a038&quot;</span><span class="fu">,</span></span>
-<span id="cb1261-4"><a href="#cb1261-4" aria-hidden="true"></a>        <span class="dt">&quot;grantedToIdentities&quot;</span><span class="fu">:</span> <span class="ot">[</span></span>
-<span id="cb1261-5"><a href="#cb1261-5" aria-hidden="true"></a>            <span class="fu">{</span></span>
-<span id="cb1261-6"><a href="#cb1261-6" aria-hidden="true"></a>                <span class="dt">&quot;user&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1261-7"><a href="#cb1261-7" aria-hidden="true"></a>                    <span class="dt">&quot;displayName&quot;</span><span class="fu">:</span> <span class="st">&quot;ryan@contoso.com&quot;</span></span>
-<span id="cb1261-8"><a href="#cb1261-8" aria-hidden="true"></a>                <span class="fu">},</span></span>
-<span id="cb1261-9"><a href="#cb1261-9" aria-hidden="true"></a>                <span class="dt">&quot;application&quot;</span><span class="fu">:</span> <span class="fu">{},</span></span>
-<span id="cb1261-10"><a href="#cb1261-10" aria-hidden="true"></a>                <span class="dt">&quot;device&quot;</span><span class="fu">:</span> <span class="fu">{}</span></span>
-<span id="cb1261-11"><a href="#cb1261-11" aria-hidden="true"></a>            <span class="fu">}</span></span>
-<span id="cb1261-12"><a href="#cb1261-12" aria-hidden="true"></a>        <span class="ot">]</span><span class="fu">,</span></span>
-<span id="cb1261-13"><a href="#cb1261-13" aria-hidden="true"></a>        <span class="dt">&quot;link&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1261-14"><a href="#cb1261-14" aria-hidden="true"></a>            <span class="dt">&quot;type&quot;</span><span class="fu">:</span> <span class="st">&quot;view&quot;</span><span class="fu">,</span></span>
-<span id="cb1261-15"><a href="#cb1261-15" aria-hidden="true"></a>            <span class="dt">&quot;scope&quot;</span><span class="fu">:</span> <span class="st">&quot;users&quot;</span><span class="fu">,</span></span>
-<span id="cb1261-16"><a href="#cb1261-16" aria-hidden="true"></a>            <span class="dt">&quot;webUrl&quot;</span><span class="fu">:</span> <span class="st">&quot;https://contoso.sharepoint.com/:w:/t/design/a577ghg9hgh737613bmbjf839026561fmzhsr85ng9f3hjck2t5s&quot;</span></span>
-<span id="cb1261-17"><a href="#cb1261-17" aria-hidden="true"></a>        <span class="fu">},</span></span>
-<span id="cb1261-18"><a href="#cb1261-18" aria-hidden="true"></a>        <span class="dt">&quot;roles&quot;</span><span class="fu">:</span> <span class="ot">[</span></span>
-<span id="cb1261-19"><a href="#cb1261-19" aria-hidden="true"></a>            <span class="st">&quot;read&quot;</span></span>
-<span id="cb1261-20"><a href="#cb1261-20" aria-hidden="true"></a>        <span class="ot">]</span><span class="fu">,</span></span>
-<span id="cb1261-21"><a href="#cb1261-21" aria-hidden="true"></a>        <span class="dt">&quot;shareId&quot;</span><span class="fu">:</span> <span class="st">&quot;u!LKj1lkdlals90j1nlkascl&quot;</span></span>
-<span id="cb1261-22"><a href="#cb1261-22" aria-hidden="true"></a>    <span class="fu">}</span><span class="ot">,</span></span>
-<span id="cb1261-23"><a href="#cb1261-23" aria-hidden="true"></a>    <span class="fu">{</span></span>
-<span id="cb1261-24"><a href="#cb1261-24" aria-hidden="true"></a>        <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;5D33DD65C6932946&quot;</span><span class="fu">,</span></span>
-<span id="cb1261-25"><a href="#cb1261-25" aria-hidden="true"></a>        <span class="dt">&quot;grantedTo&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1261-26"><a href="#cb1261-26" aria-hidden="true"></a>            <span class="dt">&quot;user&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1261-27"><a href="#cb1261-27" aria-hidden="true"></a>                <span class="dt">&quot;displayName&quot;</span><span class="fu">:</span> <span class="st">&quot;John Doe&quot;</span><span class="fu">,</span></span>
-<span id="cb1261-28"><a href="#cb1261-28" aria-hidden="true"></a>                <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;efee1b77-fb3b-4f65-99d6-274c11914d12&quot;</span></span>
-<span id="cb1261-29"><a href="#cb1261-29" aria-hidden="true"></a>            <span class="fu">},</span></span>
-<span id="cb1261-30"><a href="#cb1261-30" aria-hidden="true"></a>            <span class="dt">&quot;application&quot;</span><span class="fu">:</span> <span class="fu">{},</span></span>
-<span id="cb1261-31"><a href="#cb1261-31" aria-hidden="true"></a>            <span class="dt">&quot;device&quot;</span><span class="fu">:</span> <span class="fu">{}</span></span>
-<span id="cb1261-32"><a href="#cb1261-32" aria-hidden="true"></a>        <span class="fu">},</span></span>
-<span id="cb1261-33"><a href="#cb1261-33" aria-hidden="true"></a>        <span class="dt">&quot;roles&quot;</span><span class="fu">:</span> <span class="ot">[</span></span>
-<span id="cb1261-34"><a href="#cb1261-34" aria-hidden="true"></a>            <span class="st">&quot;owner&quot;</span></span>
-<span id="cb1261-35"><a href="#cb1261-35" aria-hidden="true"></a>        <span class="ot">]</span><span class="fu">,</span></span>
-<span id="cb1261-36"><a href="#cb1261-36" aria-hidden="true"></a>        <span class="dt">&quot;shareId&quot;</span><span class="fu">:</span> <span class="st">&quot;FWxc1lasfdbEAGM5fI7B67aB5ZMPDMmQ11U&quot;</span></span>
-<span id="cb1261-37"><a href="#cb1261-37" aria-hidden="true"></a>    <span class="fu">}</span></span>
-<span id="cb1261-38"><a href="#cb1261-38" aria-hidden="true"></a><span class="ot">]</span></span></code></pre></div>
-<p>To write permissions, pass in a "permissions" metadata key using this same format. The <a href="https://rclone.org/docs/#metadata-mapper"><code>--metadata-mapper</code></a> tool can be very helpful for this.</p>
-<p>When adding permissions, an email address can be provided in the <code>User.ID</code> or <code>DisplayName</code> properties of <code>grantedTo</code> or <code>grantedToIdentities</code>. Alternatively, an ObjectID can be provided in <code>User.ID</code>. At least one valid recipient must be provided in order to add a permission for a user. Creating a Public Link is also supported, if <code>Link.Scope</code> is set to <code>"anonymous"</code>.</p>
-<p>Example request to add a "read" permission with <code>--metadata-mapper</code>:</p>
-<div class="sourceCode" id="cb1262"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb1262-1"><a href="#cb1262-1" aria-hidden="true"></a><span class="fu">{</span></span>
-<span id="cb1262-2"><a href="#cb1262-2" aria-hidden="true"></a>    <span class="dt">&quot;Metadata&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
-<span id="cb1262-3"><a href="#cb1262-3" aria-hidden="true"></a>        <span class="dt">&quot;permissions&quot;</span><span class="fu">:</span> <span class="st">&quot;[{</span><span class="ch">\&quot;</span><span class="st">grantedToIdentities</span><span class="ch">\&quot;</span><span class="st">:[{</span><span class="ch">\&quot;</span><span class="st">user</span><span class="ch">\&quot;</span><span class="st">:{</span><span class="ch">\&quot;</span><span class="st">id</span><span class="ch">\&quot;</span><span class="st">:</span><span class="ch">\&quot;</span><span class="st">ryan@contoso.com</span><span class="ch">\&quot;</span><span class="st">}}],</span><span class="ch">\&quot;</span><span class="st">roles</span><span class="ch">\&quot;</span><span class="st">:[</span><span class="ch">\&quot;</span><span class="st">read</span><span class="ch">\&quot;</span><span class="st">]}]&quot;</span></span>
-<span id="cb1262-4"><a href="#cb1262-4" aria-hidden="true"></a>    <span class="fu">}</span></span>
-<span id="cb1262-5"><a href="#cb1262-5" aria-hidden="true"></a><span class="fu">}</span></span></code></pre></div>
-<p>Note that adding a permission can fail if a conflicting permission already exists for the file/folder.</p>
-<p>To update an existing permission, include both the Permission ID and the new <code>roles</code> to be assigned. <code>roles</code> is the only property that can be changed.</p>
-<p>To remove permissions, pass in a blob containing only the permissions you wish to keep (which can be empty, to remove all.) Note that the <code>owner</code> role will be ignored, as it cannot be removed.</p>
-<p>Note that both reading and writing permissions requires extra API calls, so if you don't need to read or write permissions it is recommended to omit <code>--onedrive-metadata-permissions</code>.</p>
-<p>Metadata and permissions are supported for Folders (directories) as well as Files. Note that setting the <code>mtime</code> or <code>btime</code> on a Folder requires one extra API call on OneDrive Business only.</p>
-<p>OneDrive does not currently support User Metadata. When writing metadata, only writeable system properties will be written -- any read-only or unrecognized keys passed in will be ignored.</p>
-<p>TIP: to see the metadata and permissions for any file or folder, run:</p>
+<div class="sourceCode" id="cb1264"><pre
+class="sourceCode json"><code class="sourceCode json"><span id="cb1264-1"><a href="#cb1264-1" aria-hidden="true" tabindex="-1"></a><span class="ot">[</span></span>
+<span id="cb1264-2"><a href="#cb1264-2" aria-hidden="true" tabindex="-1"></a>    <span class="fu">{</span></span>
+<span id="cb1264-3"><a href="#cb1264-3" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;48d31887-5fad-4d73-a9f5-3c356e68a038&quot;</span><span class="fu">,</span></span>
+<span id="cb1264-4"><a href="#cb1264-4" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;grantedToIdentities&quot;</span><span class="fu">:</span> <span class="ot">[</span></span>
+<span id="cb1264-5"><a href="#cb1264-5" aria-hidden="true" tabindex="-1"></a>            <span class="fu">{</span></span>
+<span id="cb1264-6"><a href="#cb1264-6" aria-hidden="true" tabindex="-1"></a>                <span class="dt">&quot;user&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1264-7"><a href="#cb1264-7" aria-hidden="true" tabindex="-1"></a>                    <span class="dt">&quot;displayName&quot;</span><span class="fu">:</span> <span class="st">&quot;ryan@contoso.com&quot;</span></span>
+<span id="cb1264-8"><a href="#cb1264-8" aria-hidden="true" tabindex="-1"></a>                <span class="fu">},</span></span>
+<span id="cb1264-9"><a href="#cb1264-9" aria-hidden="true" tabindex="-1"></a>                <span class="dt">&quot;application&quot;</span><span class="fu">:</span> <span class="fu">{},</span></span>
+<span id="cb1264-10"><a href="#cb1264-10" aria-hidden="true" tabindex="-1"></a>                <span class="dt">&quot;device&quot;</span><span class="fu">:</span> <span class="fu">{}</span></span>
+<span id="cb1264-11"><a href="#cb1264-11" aria-hidden="true" tabindex="-1"></a>            <span class="fu">}</span></span>
+<span id="cb1264-12"><a href="#cb1264-12" aria-hidden="true" tabindex="-1"></a>        <span class="ot">]</span><span class="fu">,</span></span>
+<span id="cb1264-13"><a href="#cb1264-13" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;link&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1264-14"><a href="#cb1264-14" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;type&quot;</span><span class="fu">:</span> <span class="st">&quot;view&quot;</span><span class="fu">,</span></span>
+<span id="cb1264-15"><a href="#cb1264-15" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;scope&quot;</span><span class="fu">:</span> <span class="st">&quot;users&quot;</span><span class="fu">,</span></span>
+<span id="cb1264-16"><a href="#cb1264-16" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;webUrl&quot;</span><span class="fu">:</span> <span class="st">&quot;https://contoso.sharepoint.com/:w:/t/design/a577ghg9hgh737613bmbjf839026561fmzhsr85ng9f3hjck2t5s&quot;</span></span>
+<span id="cb1264-17"><a href="#cb1264-17" aria-hidden="true" tabindex="-1"></a>        <span class="fu">},</span></span>
+<span id="cb1264-18"><a href="#cb1264-18" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;roles&quot;</span><span class="fu">:</span> <span class="ot">[</span></span>
+<span id="cb1264-19"><a href="#cb1264-19" aria-hidden="true" tabindex="-1"></a>            <span class="st">&quot;read&quot;</span></span>
+<span id="cb1264-20"><a href="#cb1264-20" aria-hidden="true" tabindex="-1"></a>        <span class="ot">]</span><span class="fu">,</span></span>
+<span id="cb1264-21"><a href="#cb1264-21" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;shareId&quot;</span><span class="fu">:</span> <span class="st">&quot;u!LKj1lkdlals90j1nlkascl&quot;</span></span>
+<span id="cb1264-22"><a href="#cb1264-22" aria-hidden="true" tabindex="-1"></a>    <span class="fu">}</span><span class="ot">,</span></span>
+<span id="cb1264-23"><a href="#cb1264-23" aria-hidden="true" tabindex="-1"></a>    <span class="fu">{</span></span>
+<span id="cb1264-24"><a href="#cb1264-24" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;5D33DD65C6932946&quot;</span><span class="fu">,</span></span>
+<span id="cb1264-25"><a href="#cb1264-25" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;grantedTo&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1264-26"><a href="#cb1264-26" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;user&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1264-27"><a href="#cb1264-27" aria-hidden="true" tabindex="-1"></a>                <span class="dt">&quot;displayName&quot;</span><span class="fu">:</span> <span class="st">&quot;John Doe&quot;</span><span class="fu">,</span></span>
+<span id="cb1264-28"><a href="#cb1264-28" aria-hidden="true" tabindex="-1"></a>                <span class="dt">&quot;id&quot;</span><span class="fu">:</span> <span class="st">&quot;efee1b77-fb3b-4f65-99d6-274c11914d12&quot;</span></span>
+<span id="cb1264-29"><a href="#cb1264-29" aria-hidden="true" tabindex="-1"></a>            <span class="fu">},</span></span>
+<span id="cb1264-30"><a href="#cb1264-30" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;application&quot;</span><span class="fu">:</span> <span class="fu">{},</span></span>
+<span id="cb1264-31"><a href="#cb1264-31" aria-hidden="true" tabindex="-1"></a>            <span class="dt">&quot;device&quot;</span><span class="fu">:</span> <span class="fu">{}</span></span>
+<span id="cb1264-32"><a href="#cb1264-32" aria-hidden="true" tabindex="-1"></a>        <span class="fu">},</span></span>
+<span id="cb1264-33"><a href="#cb1264-33" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;roles&quot;</span><span class="fu">:</span> <span class="ot">[</span></span>
+<span id="cb1264-34"><a href="#cb1264-34" aria-hidden="true" tabindex="-1"></a>            <span class="st">&quot;owner&quot;</span></span>
+<span id="cb1264-35"><a href="#cb1264-35" aria-hidden="true" tabindex="-1"></a>        <span class="ot">]</span><span class="fu">,</span></span>
+<span id="cb1264-36"><a href="#cb1264-36" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;shareId&quot;</span><span class="fu">:</span> <span class="st">&quot;FWxc1lasfdbEAGM5fI7B67aB5ZMPDMmQ11U&quot;</span></span>
+<span id="cb1264-37"><a href="#cb1264-37" aria-hidden="true" tabindex="-1"></a>    <span class="fu">}</span></span>
+<span id="cb1264-38"><a href="#cb1264-38" aria-hidden="true" tabindex="-1"></a><span class="ot">]</span></span></code></pre></div>
+<p>To write permissions, pass in a "permissions" metadata key using this
+same format. The <a
+href="https://rclone.org/docs/#metadata-mapper"><code>--metadata-mapper</code></a>
+tool can be very helpful for this.</p>
+<p>When adding permissions, an email address can be provided in the
+<code>User.ID</code> or <code>DisplayName</code> properties of
+<code>grantedTo</code> or <code>grantedToIdentities</code>.
+Alternatively, an ObjectID can be provided in <code>User.ID</code>. At
+least one valid recipient must be provided in order to add a permission
+for a user. Creating a Public Link is also supported, if
+<code>Link.Scope</code> is set to <code>"anonymous"</code>.</p>
+<p>Example request to add a "read" permission with
+<code>--metadata-mapper</code>:</p>
+<div class="sourceCode" id="cb1265"><pre
+class="sourceCode json"><code class="sourceCode json"><span id="cb1265-1"><a href="#cb1265-1" aria-hidden="true" tabindex="-1"></a><span class="fu">{</span></span>
+<span id="cb1265-2"><a href="#cb1265-2" aria-hidden="true" tabindex="-1"></a>    <span class="dt">&quot;Metadata&quot;</span><span class="fu">:</span> <span class="fu">{</span></span>
+<span id="cb1265-3"><a href="#cb1265-3" aria-hidden="true" tabindex="-1"></a>        <span class="dt">&quot;permissions&quot;</span><span class="fu">:</span> <span class="st">&quot;[{</span><span class="ch">\&quot;</span><span class="st">grantedToIdentities</span><span class="ch">\&quot;</span><span class="st">:[{</span><span class="ch">\&quot;</span><span class="st">user</span><span class="ch">\&quot;</span><span class="st">:{</span><span class="ch">\&quot;</span><span class="st">id</span><span class="ch">\&quot;</span><span class="st">:</span><span class="ch">\&quot;</span><span class="st">ryan@contoso.com</span><span class="ch">\&quot;</span><span class="st">}}],</span><span class="ch">\&quot;</span><span class="st">roles</span><span class="ch">\&quot;</span><span class="st">:[</span><span class="ch">\&quot;</span><span class="st">read</span><span class="ch">\&quot;</span><span class="st">]}]&quot;</span></span>
+<span id="cb1265-4"><a href="#cb1265-4" aria-hidden="true" tabindex="-1"></a>    <span class="fu">}</span></span>
+<span id="cb1265-5"><a href="#cb1265-5" aria-hidden="true" tabindex="-1"></a><span class="fu">}</span></span></code></pre></div>
+<p>Note that adding a permission can fail if a conflicting permission
+already exists for the file/folder.</p>
+<p>To update an existing permission, include both the Permission ID and
+the new <code>roles</code> to be assigned. <code>roles</code> is the
+only property that can be changed.</p>
+<p>To remove permissions, pass in a blob containing only the permissions
+you wish to keep (which can be empty, to remove all.) Note that the
+<code>owner</code> role will be ignored, as it cannot be removed.</p>
+<p>Note that both reading and writing permissions requires extra API
+calls, so if you don't need to read or write permissions it is
+recommended to omit <code>--onedrive-metadata-permissions</code>.</p>
+<p>Metadata and permissions are supported for Folders (directories) as
+well as Files. Note that setting the <code>mtime</code> or
+<code>btime</code> on a Folder requires one extra API call on OneDrive
+Business only.</p>
+<p>OneDrive does not currently support User Metadata. When writing
+metadata, only writeable system properties will be written -- any
+read-only or unrecognized keys passed in will be ignored.</p>
+<p>TIP: to see the metadata and permissions for any file or folder,
+run:</p>
 <pre><code>rclone lsjson remote:path --stat -M --onedrive-metadata-permissions read</code></pre>
-<p>Here are the possible system metadata items for the onedrive backend.</p>
+<p>Here are the possible system metadata items for the onedrive
+backend.</p>
 <table>
 <colgroup>
 <col style="width: 15%" />
@@ -29805,7 +43193,8 @@ rclone rc vfs/refresh recursive=true</code></pre>
 <tbody>
 <tr class="odd">
 <td>btime</td>
-<td>Time of file birth (creation) with S accuracy (mS for OneDrive Personal).</td>
+<td>Time of file birth (creation) with S accuracy (mS for OneDrive
+Personal).</td>
 <td>RFC 3339</td>
 <td>2006-01-02T15:04:05Z</td>
 <td>N</td>
@@ -29833,7 +43222,8 @@ rclone rc vfs/refresh recursive=true</code></pre>
 </tr>
 <tr class="odd">
 <td>description</td>
-<td>A short description of the file. Max 1024 characters. Only supported for OneDrive Personal.</td>
+<td>A short description of the file. Max 1024 characters. Only supported
+for OneDrive Personal.</td>
 <td>string</td>
 <td>Contract for signing</td>
 <td>N</td>
@@ -29868,21 +43258,27 @@ rclone rc vfs/refresh recursive=true</code></pre>
 </tr>
 <tr class="even">
 <td>mtime</td>
-<td>Time of last modification with S accuracy (mS for OneDrive Personal).</td>
+<td>Time of last modification with S accuracy (mS for OneDrive
+Personal).</td>
 <td>RFC 3339</td>
 <td>2006-01-02T15:04:05Z</td>
 <td>N</td>
 </tr>
 <tr class="odd">
 <td>package-type</td>
-<td>If present, indicates that this item is a package instead of a folder or file. Packages are treated like files in some contexts and folders in others.</td>
+<td>If present, indicates that this item is a package instead of a
+folder or file. Packages are treated like files in some contexts and
+folders in others.</td>
 <td>string</td>
 <td>oneNote</td>
 <td><strong>Y</strong></td>
 </tr>
 <tr class="even">
 <td>permissions</td>
-<td>Permissions in a JSON dump of OneDrive format. Enable with --onedrive-metadata-permissions. Properties: id, grantedTo, grantedToIdentities, invitation, inheritedFrom, link, roles, shareId</td>
+<td>Permissions in a JSON dump of OneDrive format. Enable with
+--onedrive-metadata-permissions. Properties: id, grantedTo,
+grantedToIdentities, invitation, inheritedFrom, link, roles,
+shareId</td>
 <td>JSON</td>
 <td>{}</td>
 <td>N</td>
@@ -29903,14 +43299,16 @@ rclone rc vfs/refresh recursive=true</code></pre>
 </tr>
 <tr class="odd">
 <td>shared-scope</td>
-<td>If shared, indicates the scope of how the item is shared: anonymous, organization, or users.</td>
+<td>If shared, indicates the scope of how the item is shared: anonymous,
+organization, or users.</td>
 <td>string</td>
 <td>users</td>
 <td><strong>Y</strong></td>
 </tr>
 <tr class="even">
 <td>shared-time</td>
-<td>Time when the item was shared, with S accuracy (mS for OneDrive Personal).</td>
+<td>Time when the item was shared, with S accuracy (mS for OneDrive
+Personal).</td>
 <td>RFC 3339</td>
 <td>2006-01-02T15:04:05Z</td>
 <td><strong>Y</strong></td>
@@ -29924,104 +43322,253 @@ rclone rc vfs/refresh recursive=true</code></pre>
 </tr>
 </tbody>
 </table>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h2 id="limitations-26">Limitations</h2>
-<p>If you don't use rclone for 90 days the refresh token will expire. This will result in authorization problems. This is easy to fix by running the <code>rclone config reconnect remote:</code> command to get a new token and refresh token.</p>
+<p>If you don't use rclone for 90 days the refresh token will expire.
+This will result in authorization problems. This is easy to fix by
+running the <code>rclone config reconnect remote:</code> command to get
+a new token and refresh token.</p>
 <h3 id="naming">Naming</h3>
-<p>Note that OneDrive is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
-<p>There are quite a few characters that can't be in OneDrive file names. These can't occur on Windows platforms, but on non-Windows platforms they are common. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a <code>?</code> in it will be mapped to <code>？</code> instead.</p>
+<p>Note that OneDrive is case insensitive so you can't have a file
+called "Hello.doc" and one called "hello.doc".</p>
+<p>There are quite a few characters that can't be in OneDrive file
+names. These can't occur on Windows platforms, but on non-Windows
+platforms they are common. Rclone will map these names to and from an
+identical looking unicode equivalent. For example if a file has a
+<code>?</code> in it will be mapped to <code>？</code> instead.</p>
 <h3 id="file-sizes">File sizes</h3>
-<p>The largest allowed file size is 250 GiB for both OneDrive Personal and OneDrive for Business <a href="https://support.microsoft.com/en-us/office/invalid-file-names-and-file-types-in-onedrive-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa?ui=en-us&amp;rs=en-us&amp;ad=us#individualfilesize">(Updated 13 Jan 2021)</a>.</p>
+<p>The largest allowed file size is 250 GiB for both OneDrive Personal
+and OneDrive for Business <a
+href="https://support.microsoft.com/en-us/office/invalid-file-names-and-file-types-in-onedrive-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa?ui=en-us&amp;rs=en-us&amp;ad=us#individualfilesize">(Updated
+13 Jan 2021)</a>.</p>
 <h3 id="path-length">Path length</h3>
-<p>The entire path, including the file name, must contain fewer than 400 characters for OneDrive, OneDrive for Business and SharePoint Online. If you are encrypting file and folder names with rclone, you may want to pay attention to this limitation because the encrypted names are typically longer than the original ones.</p>
+<p>The entire path, including the file name, must contain fewer than 400
+characters for OneDrive, OneDrive for Business and SharePoint Online. If
+you are encrypting file and folder names with rclone, you may want to
+pay attention to this limitation because the encrypted names are
+typically longer than the original ones.</p>
 <h3 id="number-of-files">Number of files</h3>
-<p>OneDrive seems to be OK with at least 50,000 files in a folder, but at 100,000 rclone will get errors listing the directory like <code>couldn’t list files: UnknownError:</code>. See <a href="https://github.com/rclone/rclone/issues/2707">#2707</a> for more info.</p>
-<p>An official document about the limitations for different types of OneDrive can be found <a href="https://support.office.com/en-us/article/invalid-file-names-and-file-types-in-onedrive-onedrive-for-business-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa">here</a>.</p>
+<p>OneDrive seems to be OK with at least 50,000 files in a folder, but
+at 100,000 rclone will get errors listing the directory like
+<code>couldn’t list files: UnknownError:</code>. See <a
+href="https://github.com/rclone/rclone/issues/2707">#2707</a> for more
+info.</p>
+<p>An official document about the limitations for different types of
+OneDrive can be found <a
+href="https://support.office.com/en-us/article/invalid-file-names-and-file-types-in-onedrive-onedrive-for-business-and-sharepoint-64883a5d-228e-48f5-b3d2-eb39e07630fa">here</a>.</p>
 <h2 id="versions-4">Versions</h2>
-<p>Every change in a file OneDrive causes the service to create a new version of the file. This counts against a users quota. For example changing the modification time of a file creates a second version, so the file apparently uses twice the space.</p>
-<p>For example the <code>copy</code> command is affected by this as rclone copies the file and then afterwards sets the modification time to match the source file which uses another version.</p>
-<p>You can use the <code>rclone cleanup</code> command (see below) to remove all old versions.</p>
-<p>Or you can set the <code>no_versions</code> parameter to <code>true</code> and rclone will remove versions after operations which create new versions. This takes extra transactions so only enable it if you need it.</p>
-<p><strong>Note</strong> At the time of writing Onedrive Personal creates versions (but not for setting the modification time) but the API for removing them returns "API not found" so cleanup and <code>no_versions</code> should not be used on Onedrive Personal.</p>
+<p>Every change in a file OneDrive causes the service to create a new
+version of the file. This counts against a users quota. For example
+changing the modification time of a file creates a second version, so
+the file apparently uses twice the space.</p>
+<p>For example the <code>copy</code> command is affected by this as
+rclone copies the file and then afterwards sets the modification time to
+match the source file which uses another version.</p>
+<p>You can use the <code>rclone cleanup</code> command (see below) to
+remove all old versions.</p>
+<p>Or you can set the <code>no_versions</code> parameter to
+<code>true</code> and rclone will remove versions after operations which
+create new versions. This takes extra transactions so only enable it if
+you need it.</p>
+<p><strong>Note</strong> At the time of writing Onedrive Personal
+creates versions (but not for setting the modification time) but the API
+for removing them returns "API not found" so cleanup and
+<code>no_versions</code> should not be used on Onedrive Personal.</p>
 <h3 id="disabling-versioning">Disabling versioning</h3>
-<p>Starting October 2018, users will no longer be able to disable versioning by default. This is because Microsoft has brought an <a href="https://techcommunity.microsoft.com/t5/Microsoft-OneDrive-Blog/New-Updates-to-OneDrive-and-SharePoint-Team-Site-Versioning/ba-p/204390">update</a> to the mechanism. To change this new default setting, a PowerShell command is required to be run by a SharePoint admin. If you are an admin, you can run these commands in PowerShell to change that setting:</p>
+<p>Starting October 2018, users will no longer be able to disable
+versioning by default. This is because Microsoft has brought an <a
+href="https://techcommunity.microsoft.com/t5/Microsoft-OneDrive-Blog/New-Updates-to-OneDrive-and-SharePoint-Team-Site-Versioning/ba-p/204390">update</a>
+to the mechanism. To change this new default setting, a PowerShell
+command is required to be run by a SharePoint admin. If you are an
+admin, you can run these commands in PowerShell to change that
+setting:</p>
 <ol type="1">
-<li><code>Install-Module -Name Microsoft.Online.SharePoint.PowerShell</code> (in case you haven't installed this already)</li>
+<li><code>Install-Module -Name Microsoft.Online.SharePoint.PowerShell</code>
+(in case you haven't installed this already)</li>
 <li><code>Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking</code></li>
-<li><code>Connect-SPOService -Url https://YOURSITE-admin.sharepoint.com -Credential YOU@YOURSITE.COM</code> (replacing <code>YOURSITE</code>, <code>YOU</code>, <code>YOURSITE.COM</code> with the actual values; this will prompt for your credentials)</li>
+<li><code>Connect-SPOService -Url https://YOURSITE-admin.sharepoint.com -Credential YOU@YOURSITE.COM</code>
+(replacing <code>YOURSITE</code>, <code>YOU</code>,
+<code>YOURSITE.COM</code> with the actual values; this will prompt for
+your credentials)</li>
 <li><code>Set-SPOTenant -EnableMinimumVersionRequirement $False</code></li>
-<li><code>Disconnect-SPOService</code> (to disconnect from the server)</li>
+<li><code>Disconnect-SPOService</code> (to disconnect from the
+server)</li>
 </ol>
-<p><em>Below are the steps for normal users to disable versioning. If you don't see the "No Versioning" option, make sure the above requirements are met.</em></p>
-<p>User <a href="https://github.com/Weropol">Weropol</a> has found a method to disable versioning on OneDrive</p>
+<p><em>Below are the steps for normal users to disable versioning. If
+you don't see the "No Versioning" option, make sure the above
+requirements are met.</em></p>
+<p>User <a href="https://github.com/Weropol">Weropol</a> has found a
+method to disable versioning on OneDrive</p>
 <ol type="1">
-<li>Open the settings menu by clicking on the gear symbol at the top of the OneDrive Business page.</li>
+<li>Open the settings menu by clicking on the gear symbol at the top of
+the OneDrive Business page.</li>
 <li>Click Site settings.</li>
-<li>Once on the Site settings page, navigate to Site Administration &gt; Site libraries and lists.</li>
+<li>Once on the Site settings page, navigate to Site Administration &gt;
+Site libraries and lists.</li>
 <li>Click Customize "Documents".</li>
 <li>Click General Settings &gt; Versioning Settings.</li>
-<li>Under Document Version History select the option No versioning. Note: This will disable the creation of new file versions, but will not remove any previous versions. Your documents are safe.</li>
+<li>Under Document Version History select the option No versioning.
+Note: This will disable the creation of new file versions, but will not
+remove any previous versions. Your documents are safe.</li>
 <li>Apply the changes by clicking OK.</li>
-<li>Use rclone to upload or modify files. (I also use the --no-update-modtime flag)</li>
+<li>Use rclone to upload or modify files. (I also use the
+--no-update-modtime flag)</li>
 <li>Restore the versioning settings after using rclone. (Optional)</li>
 </ol>
 <h2 id="cleanup-4">Cleanup</h2>
-<p>OneDrive supports <code>rclone cleanup</code> which causes rclone to look through every file under the path supplied and delete all version but the current version. Because this involves traversing all the files, then querying each file for versions it can be quite slow. Rclone does <code>--checkers</code> tests in parallel. The command also supports <code>--interactive</code>/<code>i</code> or <code>--dry-run</code> which is a great way to see what it would do.</p>
+<p>OneDrive supports <code>rclone cleanup</code> which causes rclone to
+look through every file under the path supplied and delete all version
+but the current version. Because this involves traversing all the files,
+then querying each file for versions it can be quite slow. Rclone does
+<code>--checkers</code> tests in parallel. The command also supports
+<code>--interactive</code>/<code>i</code> or <code>--dry-run</code>
+which is a great way to see what it would do.</p>
 <pre><code>rclone cleanup --interactive remote:path/subdir # interactively remove all old version for path/subdir
 rclone cleanup remote:path/subdir               # unconditionally remove all old version for path/subdir</code></pre>
-<p><strong>NB</strong> Onedrive personal can't currently delete versions</p>
+<p><strong>NB</strong> Onedrive personal can't currently delete
+versions</p>
 <h2 id="troubleshooting-2">Troubleshooting</h2>
-<h3 id="excessive-throttling-or-blocked-on-sharepoint">Excessive throttling or blocked on SharePoint</h3>
-<p>If you experience excessive throttling or is being blocked on SharePoint then it may help to set the user agent explicitly with a flag like this: <code>--user-agent "ISV|rclone.org|rclone/v1.55.1"</code></p>
-<p>The specific details can be found in the Microsoft document: <a href="https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#how-to-decorate-your-http-traffic-to-avoid-throttling">Avoid getting throttled or blocked in SharePoint Online</a></p>
-<h3 id="unexpected-file-sizehash-differences-on-sharepoint">Unexpected file size/hash differences on Sharepoint</h3>
-<p>It is a <a href="https://github.com/OneDrive/onedrive-api-docs/issues/935#issuecomment-441741631">known</a> issue that Sharepoint (not OneDrive or OneDrive for Business) silently modifies uploaded files, mainly Office files (.docx, .xlsx, etc.), causing file size and hash checks to fail. There are also other situations that will cause OneDrive to report inconsistent file sizes. To use rclone with such affected files on Sharepoint, you may disable these checks with the following command line arguments:</p>
+<h3 id="excessive-throttling-or-blocked-on-sharepoint">Excessive
+throttling or blocked on SharePoint</h3>
+<p>If you experience excessive throttling or is being blocked on
+SharePoint then it may help to set the user agent explicitly with a flag
+like this: <code>--user-agent "ISV|rclone.org|rclone/v1.55.1"</code></p>
+<p>The specific details can be found in the Microsoft document: <a
+href="https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online#how-to-decorate-your-http-traffic-to-avoid-throttling">Avoid
+getting throttled or blocked in SharePoint Online</a></p>
+<h3 id="unexpected-file-sizehash-differences-on-sharepoint">Unexpected
+file size/hash differences on Sharepoint</h3>
+<p>It is a <a
+href="https://github.com/OneDrive/onedrive-api-docs/issues/935#issuecomment-441741631">known</a>
+issue that Sharepoint (not OneDrive or OneDrive for Business) silently
+modifies uploaded files, mainly Office files (.docx, .xlsx, etc.),
+causing file size and hash checks to fail. There are also other
+situations that will cause OneDrive to report inconsistent file sizes.
+To use rclone with such affected files on Sharepoint, you may disable
+these checks with the following command line arguments:</p>
 <pre><code>--ignore-checksum --ignore-size</code></pre>
-<p>Alternatively, if you have write access to the OneDrive files, it may be possible to fix this problem for certain files, by attempting the steps below. Open the web interface for <a href="https://onedrive.live.com">OneDrive</a> and find the affected files (which will be in the error messages/log for rclone). Simply click on each of these files, causing OneDrive to open them on the web. This will cause each file to be converted in place to a format that is functionally equivalent but which will no longer trigger the size discrepancy. Once all problematic files are converted you will no longer need the ignore options above.</p>
-<h3 id="replacingdeleting-existing-files-on-sharepoint-gets-item-not-found">Replacing/deleting existing files on Sharepoint gets "item not found"</h3>
-<p>It is a <a href="https://github.com/OneDrive/onedrive-api-docs/issues/1068">known</a> issue that Sharepoint (not OneDrive or OneDrive for Business) may return "item not found" errors when users try to replace or delete uploaded files; this seems to mainly affect Office files (.docx, .xlsx, etc.) and web files (.html, .aspx, etc.). As a workaround, you may use the <code>--backup-dir &lt;BACKUP_DIR&gt;</code> command line argument so rclone moves the files to be replaced/deleted into a given backup directory (instead of directly replacing/deleting them). For example, to instruct rclone to move the files into the directory <code>rclone-backup-dir</code> on backend <code>mysharepoint</code>, you may use:</p>
+<p>Alternatively, if you have write access to the OneDrive files, it may
+be possible to fix this problem for certain files, by attempting the
+steps below. Open the web interface for <a
+href="https://onedrive.live.com">OneDrive</a> and find the affected
+files (which will be in the error messages/log for rclone). Simply click
+on each of these files, causing OneDrive to open them on the web. This
+will cause each file to be converted in place to a format that is
+functionally equivalent but which will no longer trigger the size
+discrepancy. Once all problematic files are converted you will no longer
+need the ignore options above.</p>
+<h3
+id="replacingdeleting-existing-files-on-sharepoint-gets-item-not-found">Replacing/deleting
+existing files on Sharepoint gets "item not found"</h3>
+<p>It is a <a
+href="https://github.com/OneDrive/onedrive-api-docs/issues/1068">known</a>
+issue that Sharepoint (not OneDrive or OneDrive for Business) may return
+"item not found" errors when users try to replace or delete uploaded
+files; this seems to mainly affect Office files (.docx, .xlsx, etc.) and
+web files (.html, .aspx, etc.). As a workaround, you may use the
+<code>--backup-dir &lt;BACKUP_DIR&gt;</code> command line argument so
+rclone moves the files to be replaced/deleted into a given backup
+directory (instead of directly replacing/deleting them). For example, to
+instruct rclone to move the files into the directory
+<code>rclone-backup-dir</code> on backend <code>mysharepoint</code>, you
+may use:</p>
 <pre><code>--backup-dir mysharepoint:rclone-backup-dir</code></pre>
 <h3 id="access_denied-aadsts65005">access_denied (AADSTS65005)</h3>
 <pre><code>Error: access_denied
 Code: AADSTS65005
 Description: Using application &#39;rclone&#39; is currently not supported for your organization [YOUR_ORGANIZATION] because it is in an unmanaged state. An administrator needs to claim ownership of the company by DNS validation of [YOUR_ORGANIZATION] before the application rclone can be provisioned.</code></pre>
-<p>This means that rclone can't use the OneDrive for Business API with your account. You can't do much about it, maybe write an email to your admins.</p>
-<p>However, there are other ways to interact with your OneDrive account. Have a look at the WebDAV backend: https://rclone.org/webdav/#sharepoint</p>
+<p>This means that rclone can't use the OneDrive for Business API with
+your account. You can't do much about it, maybe write an email to your
+admins.</p>
+<p>However, there are other ways to interact with your OneDrive account.
+Have a look at the WebDAV backend:
+https://rclone.org/webdav/#sharepoint</p>
 <h3 id="invalid_grant-aadsts50076">invalid_grant (AADSTS50076)</h3>
 <pre><code>Error: invalid_grant
 Code: AADSTS50076
 Description: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access &#39;...&#39;.</code></pre>
-<p>If you see the error above after enabling multi-factor authentication for your account, you can fix it by refreshing your OAuth refresh token. To do that, run <code>rclone config</code>, and choose to edit your OneDrive backend. Then, you don't need to actually make any changes until you reach this question: <code>Already have a token - refresh?</code>. For this question, answer <code>y</code> and go through the process to refresh your token, just like the first time the backend is configured. After this, rclone should work again for this backend.</p>
-<h3 id="invalid-request-when-making-public-links">Invalid request when making public links</h3>
-<p>On Sharepoint and OneDrive for Business, <code>rclone link</code> may return an "Invalid request" error. A possible cause is that the organisation admin didn't allow public links to be made for the organisation/sharepoint library. To fix the permissions as an admin, take a look at the docs: <a href="https://docs.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off">1</a>, <a href="https://support.microsoft.com/en-us/office/set-up-and-manage-access-requests-94b26e0b-2822-49d4-929a-8455698654b3">2</a>.</p>
-<h3 id="can-not-access-shared-with-me-files">Can not access <code>Shared</code> with me files</h3>
-<p>Shared with me files is not supported by rclone <a href="https://github.com/rclone/rclone/issues/4062">currently</a>, but there is a workaround:</p>
+<p>If you see the error above after enabling multi-factor authentication
+for your account, you can fix it by refreshing your OAuth refresh token.
+To do that, run <code>rclone config</code>, and choose to edit your
+OneDrive backend. Then, you don't need to actually make any changes
+until you reach this question:
+<code>Already have a token - refresh?</code>. For this question, answer
+<code>y</code> and go through the process to refresh your token, just
+like the first time the backend is configured. After this, rclone should
+work again for this backend.</p>
+<h3 id="invalid-request-when-making-public-links">Invalid request when
+making public links</h3>
+<p>On Sharepoint and OneDrive for Business, <code>rclone link</code> may
+return an "Invalid request" error. A possible cause is that the
+organisation admin didn't allow public links to be made for the
+organisation/sharepoint library. To fix the permissions as an admin,
+take a look at the docs: <a
+href="https://docs.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off">1</a>,
+<a
+href="https://support.microsoft.com/en-us/office/set-up-and-manage-access-requests-94b26e0b-2822-49d4-929a-8455698654b3">2</a>.</p>
+<h3 id="can-not-access-shared-with-me-files">Can not access
+<code>Shared</code> with me files</h3>
+<p>Shared with me files is not supported by rclone <a
+href="https://github.com/rclone/rclone/issues/4062">currently</a>, but
+there is a workaround:</p>
 <ol type="1">
-<li>Visit <a href="https://onedrive.live.com/">https://onedrive.live.com</a></li>
-<li>Right click a item in <code>Shared</code>, then click <code>Add shortcut to My files</code> in the context <img src="https://user-images.githubusercontent.com/60313789/206118040-7e762b3b-aa61-41a1-8649-cc18889f3572.png" title="Screenshot (Shared with me)" alt="make_shortcut" /></li>
-<li>The shortcut will appear in <code>My files</code>, you can access it with rclone, it behaves like a normal folder/file. <img src="https://i.imgur.com/0S8H3li.png" title="Screenshot (My Files)" alt="in_my_files" /> <img src="https://i.imgur.com/2Iq66sW.png" title="Screenshot (rclone mount)" alt="rclone_mount" /></li>
+<li>Visit <a
+href="https://onedrive.live.com/">https://onedrive.live.com</a></li>
+<li>Right click a item in <code>Shared</code>, then click
+<code>Add shortcut to My files</code> in the context <img
+src="https://user-images.githubusercontent.com/60313789/206118040-7e762b3b-aa61-41a1-8649-cc18889f3572.png"
+title="Screenshot (Shared with me)" alt="make_shortcut" /></li>
+<li>The shortcut will appear in <code>My files</code>, you can access it
+with rclone, it behaves like a normal folder/file. <img
+src="https://i.imgur.com/0S8H3li.png" title="Screenshot (My Files)"
+alt="in_my_files" /> <img src="https://i.imgur.com/2Iq66sW.png"
+title="Screenshot (rclone mount)" alt="rclone_mount" /></li>
 </ol>
-<h3 id="live-photos-uploaded-from-ios-small-video-clips-in-.heic-files">Live Photos uploaded from iOS (small video clips in .heic files)</h3>
-<p>The iOS OneDrive app introduced <a href="https://techcommunity.microsoft.com/t5/microsoft-onedrive-blog/live-photos-come-to-onedrive/ba-p/1953452">upload and storage</a> of <a href="https://support.apple.com/en-gb/HT207310">Live Photos</a> in 2020. The usage and download of these uploaded Live Photos is unfortunately still work-in-progress and this introduces several issues when copying, synchronising and mounting – both in rclone and in the native OneDrive client on Windows.</p>
-<p>The root cause can easily be seen if you locate one of your Live Photos in the OneDrive web interface. Then download the photo from the web interface. You will then see that the size of downloaded .heic file is smaller than the size displayed in the web interface. The downloaded file is smaller because it only contains a single frame (still photo) extracted from the Live Photo (movie) stored in OneDrive.</p>
-<p>The different sizes will cause <code>rclone copy/sync</code> to repeatedly recopy unmodified photos something like this:</p>
+<h3
+id="live-photos-uploaded-from-ios-small-video-clips-in-.heic-files">Live
+Photos uploaded from iOS (small video clips in .heic files)</h3>
+<p>The iOS OneDrive app introduced <a
+href="https://techcommunity.microsoft.com/t5/microsoft-onedrive-blog/live-photos-come-to-onedrive/ba-p/1953452">upload
+and storage</a> of <a
+href="https://support.apple.com/en-gb/HT207310">Live Photos</a> in 2020.
+The usage and download of these uploaded Live Photos is unfortunately
+still work-in-progress and this introduces several issues when copying,
+synchronising and mounting – both in rclone and in the native OneDrive
+client on Windows.</p>
+<p>The root cause can easily be seen if you locate one of your Live
+Photos in the OneDrive web interface. Then download the photo from the
+web interface. You will then see that the size of downloaded .heic file
+is smaller than the size displayed in the web interface. The downloaded
+file is smaller because it only contains a single frame (still photo)
+extracted from the Live Photo (movie) stored in OneDrive.</p>
+<p>The different sizes will cause <code>rclone copy/sync</code> to
+repeatedly recopy unmodified photos something like this:</p>
 <pre><code>DEBUG : 20230203_123826234_iOS.heic: Sizes differ (src 4470314 vs dst 1298667)
 DEBUG : 20230203_123826234_iOS.heic: sha1 = fc2edde7863b7a7c93ca6771498ac797f8460750 OK
 INFO  : 20230203_123826234_iOS.heic: Copied (replaced existing)</code></pre>
-<p>These recopies can be worked around by adding <code>--ignore-size</code>. Please note that this workaround only syncs the still-picture not the movie clip, and relies on modification dates being correctly updated on all files in all situations.</p>
-<p>The different sizes will also cause <code>rclone check</code> to report size errors something like this:</p>
+<p>These recopies can be worked around by adding
+<code>--ignore-size</code>. Please note that this workaround only syncs
+the still-picture not the movie clip, and relies on modification dates
+being correctly updated on all files in all situations.</p>
+<p>The different sizes will also cause <code>rclone check</code> to
+report size errors something like this:</p>
 <pre><code>ERROR : 20230203_123826234_iOS.heic: sizes differ</code></pre>
-<p>These check errors can be suppressed by adding <code>--ignore-size</code>.</p>
-<p>The different sizes will also cause <code>rclone mount</code> to fail downloading with an error something like this:</p>
+<p>These check errors can be suppressed by adding
+<code>--ignore-size</code>.</p>
+<p>The different sizes will also cause <code>rclone mount</code> to fail
+downloading with an error something like this:</p>
 <pre><code>ERROR : 20230203_123826234_iOS.heic: ReadFileHandle.Read error: low level retry 1/10: unexpected EOF</code></pre>
 <p>or like this when using <code>--cache-mode=full</code>:</p>
 <pre><code>INFO  : 20230203_123826234_iOS.heic: vfs cache: downloader: error count now 1: vfs reader: failed to write to cache file: 416 Requested Range Not Satisfiable:
 ERROR : 20230203_123826234_iOS.heic: vfs cache: failed to download: vfs reader: failed to write to cache file: 416 Requested Range Not Satisfiable:</code></pre>
 <h1 id="opendrive">OpenDrive</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-34">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-35">Configuration</h2>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>n) New remote
@@ -30062,10 +43609,14 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an OpenDrive directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-16">Modification times and hashes</h3>
-<p>OpenDrive allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not.</p>
+<h3 id="modification-times-and-hashes-16">Modification times and
+hashes</h3>
+<p>OpenDrive allows modification times to be set on objects accurate to
+1 second. These will be used to detect whether objects need syncing or
+not.</p>
 <p>The MD5 hash algorithm is supported.</p>
-<h3 id="restricted-filename-characters-21">Restricted filename characters</h3>
+<h3 id="restricted-filename-characters-20">Restricted filename
+characters</h3>
 <table>
 <thead>
 <tr class="header">
@@ -30127,7 +43678,9 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names can also not begin or end with the following characters. These only get replaced if they are the first or last character in the name:</p>
+<p>File names can also not begin or end with the following characters.
+These only get replaced if they are the first or last character in the
+name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -30164,8 +43717,10 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<h3 id="standard-options-34">Standard options</h3>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<h3 id="standard-options-35">Standard options</h3>
 <p>Here are the Standard options specific to opendrive (OpenDrive).</p>
 <h4 id="opendrive-username">--opendrive-username</h4>
 <p>Username.</p>
@@ -30178,7 +43733,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="opendrive-password">--opendrive-password</h4>
 <p>Password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -30186,21 +43743,24 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: true</li>
 </ul>
-<h3 id="advanced-options-35">Advanced options</h3>
+<h3 id="advanced-options-36">Advanced options</h3>
 <p>Here are the Advanced options specific to opendrive (OpenDrive).</p>
 <h4 id="opendrive-encoding">--opendrive-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_OPENDRIVE_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,LeftSpace,LeftCrLfHtVt,RightSpace,RightCrLfHtVt,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="opendrive-chunk-size">--opendrive-chunk-size</h4>
 <p>Files will be uploaded in chunks this size.</p>
-<p>Note that these chunks are buffered in memory so increasing them will increase memory use.</p>
+<p>Note that these chunks are buffered in memory so increasing them will
+increase memory use.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -30218,22 +43778,43 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-27">Limitations</h2>
-<p>Note that OpenDrive is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
-<p>There are quite a few characters that can't be in OpenDrive file names. These can't occur on Windows platforms, but on non-Windows platforms they are common. Rclone will map these names to and from an identical looking unicode equivalent. For example if a file has a <code>?</code> in it will be mapped to <code>？</code> instead.</p>
-<p><code>rclone about</code> is not supported by the OpenDrive backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p>Note that OpenDrive is case insensitive so you can't have a file
+called "Hello.doc" and one called "hello.doc".</p>
+<p>There are quite a few characters that can't be in OpenDrive file
+names. These can't occur on Windows platforms, but on non-Windows
+platforms they are common. Rclone will map these names to and from an
+identical looking unicode equivalent. For example if a file has a
+<code>?</code> in it will be mapped to <code>？</code> instead.</p>
+<p><code>rclone about</code> is not supported by the OpenDrive backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="oracle-object-storage">Oracle Object Storage</h1>
 <ul>
-<li><a href="https://docs.oracle.com/en-us/iaas/Content/Object/Concepts/objectstorageoverview.htm">Oracle Object Storage Overview</a></li>
-<li><a href="https://www.oracle.com/cloud/storage/object-storage/faq/">Oracle Object Storage FAQ</a></li>
-<li><a href="https://docs.oracle.com/en-us/iaas/Content/Resources/Assets/whitepapers/oci-object-storage-best-practices.pdf">Oracle Object Storage Limits</a></li>
+<li><a
+href="https://docs.oracle.com/en-us/iaas/Content/Object/Concepts/objectstorageoverview.htm">Oracle
+Object Storage Overview</a></li>
+<li><a
+href="https://www.oracle.com/cloud/storage/object-storage/faq/">Oracle
+Object Storage FAQ</a></li>
+<li><a
+href="https://docs.oracle.com/en-us/iaas/Content/Resources/Assets/whitepapers/oci-object-storage-best-practices.pdf">Oracle
+Object Storage Limits</a></li>
 </ul>
-<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
-<p>Sample command to transfer local artifacts to remote:bucket in oracle object storage:</p>
+<p>Paths are specified as <code>remote:bucket</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
+<p>Sample command to transfer local artifacts to remote:bucket in oracle
+object storage:</p>
 <p><code>rclone -vvv  --progress --stats-one-line --max-stats-groups 10 --log-format date,time,UTC,longfile --fast-list --buffer-size 256Mi --oos-no-check-bucket --oos-upload-cutoff 10Mi --multi-thread-cutoff 16Mi --multi-thread-streams 3000 --transfers 3000 --checkers 64  --retries 2  --oos-chunk-size 10Mi --oos-upload-concurrency 10000  --oos-attempt-resume-upload --oos-leave-parts-on-error sync ./artifacts  remote:bucket -vv</code></p>
-<h2 id="configuration-35">Configuration</h2>
-<p>Here is an example of making an oracle object storage configuration. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<h2 id="configuration-36">Configuration</h2>
+<p>Here is an example of making an oracle object storage configuration.
+<code>rclone config</code> walks you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>n) New remote
@@ -30343,7 +43924,11 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:bucket
 rclone ls remote:bucket --max-depth 1</code></pre>
 <h2 id="authentication-providers">Authentication Providers</h2>
-<p>OCI has various authentication methods. To learn more about authentication methods please refer <a href="https://docs.oracle.com/en-us/iaas/Content/API/Concepts/sdk_authentication_methods.htm">oci authentication methods</a> These choices can be specified in the rclone config file.</p>
+<p>OCI has various authentication methods. To learn more about
+authentication methods please refer <a
+href="https://docs.oracle.com/en-us/iaas/Content/API/Concepts/sdk_authentication_methods.htm">oci
+authentication methods</a> These choices can be specified in the rclone
+config file.</p>
 <p>Rclone supports the following OCI authentication provider.</p>
 <pre><code>User Principal
 Instance Principal
@@ -30351,7 +43936,8 @@ Resource Principal
 Workload Identity
 No authentication</code></pre>
 <h3 id="user-principal">User Principal</h3>
-<p>Sample rclone config file for Authentication Provider User Principal:</p>
+<p>Sample rclone config file for Authentication Provider User
+Principal:</p>
 <pre><code>[oos]
 type = oracleobjectstorage
 namespace = id&lt;redacted&gt;34
@@ -30360,11 +43946,18 @@ region = us-ashburn-1
 provider = user_principal_auth
 config_file = /home/opc/.oci/config
 config_profile = Default</code></pre>
-<p>Advantages: - One can use this method from any server within OCI or on-premises or from other cloud provider.</p>
-<p>Considerations: - you need to configure user’s privileges / policy to allow access to object storage - Overhead of managing users and keys. - If the user is deleted, the config file will no longer work and may cause automation regressions that use the user's credentials.</p>
+<p>Advantages: - One can use this method from any server within OCI or
+on-premises or from other cloud provider.</p>
+<p>Considerations: - you need to configure user’s privileges / policy to
+allow access to object storage - Overhead of managing users and keys. -
+If the user is deleted, the config file will no longer work and may
+cause automation regressions that use the user's credentials.</p>
 <h3 id="instance-principal">Instance Principal</h3>
-<p>An OCI compute instance can be authorized to use rclone by using it's identity and certificates as an instance principal. With this approach no credentials have to be stored and managed.</p>
-<p>Sample rclone configuration file for Authentication Provider Instance Principal:</p>
+<p>An OCI compute instance can be authorized to use rclone by using it's
+identity and certificates as an instance principal. With this approach
+no credentials have to be stored and managed.</p>
+<p>Sample rclone configuration file for Authentication Provider Instance
+Principal:</p>
 <pre><code>[opc@rclone ~]$ cat ~/.config/rclone/rclone.conf
 [oos]
 type = oracleobjectstorage
@@ -30374,23 +43967,34 @@ region = us-ashburn-1
 provider = instance_principal_auth</code></pre>
 <p>Advantages:</p>
 <ul>
-<li>With instance principals, you don't need to configure user credentials and transfer/ save it to disk in your compute instances or rotate the credentials.</li>
+<li>With instance principals, you don't need to configure user
+credentials and transfer/ save it to disk in your compute instances or
+rotate the credentials.</li>
 <li>You don’t need to deal with users and keys.</li>
-<li>Greatly helps in automation as you don't have to manage access keys, user private keys, storing them in vault, using kms etc.</li>
+<li>Greatly helps in automation as you don't have to manage access keys,
+user private keys, storing them in vault, using kms etc.</li>
 </ul>
 <p>Considerations:</p>
 <ul>
-<li>You need to configure a dynamic group having this instance as member and add policy to read object storage to that dynamic group.</li>
-<li>Everyone who has access to this machine can execute the CLI commands.</li>
-<li>It is applicable for oci compute instances only. It cannot be used on external instance or resources.</li>
+<li>You need to configure a dynamic group having this instance as member
+and add policy to read object storage to that dynamic group.</li>
+<li>Everyone who has access to this machine can execute the CLI
+commands.</li>
+<li>It is applicable for oci compute instances only. It cannot be used
+on external instance or resources.</li>
 </ul>
 <h3 id="resource-principal">Resource Principal</h3>
-<p>Resource principal auth is very similar to instance principal auth but used for resources that are not compute instances such as <a href="https://docs.oracle.com/en-us/iaas/Content/Functions/Concepts/functionsoverview.htm">serverless functions</a>. To use resource principal ensure Rclone process is started with these environment variables set in its process.</p>
+<p>Resource principal auth is very similar to instance principal auth
+but used for resources that are not compute instances such as <a
+href="https://docs.oracle.com/en-us/iaas/Content/Functions/Concepts/functionsoverview.htm">serverless
+functions</a>. To use resource principal ensure Rclone process is
+started with these environment variables set in its process.</p>
 <pre><code>export OCI_RESOURCE_PRINCIPAL_VERSION=2.2
 export OCI_RESOURCE_PRINCIPAL_REGION=us-ashburn-1
 export OCI_RESOURCE_PRINCIPAL_PRIVATE_PEM=/usr/share/model-server/key.pem
 export OCI_RESOURCE_PRINCIPAL_RPST=/usr/share/model-server/security_token</code></pre>
-<p>Sample rclone configuration file for Authentication Provider Resource Principal:</p>
+<p>Sample rclone configuration file for Authentication Provider Resource
+Principal:</p>
 <pre><code>[oos]
 type = oracleobjectstorage
 namespace = id&lt;redacted&gt;34
@@ -30398,32 +44002,64 @@ compartment = ocid1.compartment.oc1..aa&lt;redacted&gt;ba
 region = us-ashburn-1
 provider = resource_principal_auth</code></pre>
 <h3 id="workload-identity">Workload Identity</h3>
-<p>Workload Identity auth may be used when running Rclone from Kubernetes pod on a Container Engine for Kubernetes (OKE) cluster. For more details on configuring Workload Identity, see <a href="https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contenggrantingworkloadaccesstoresources.htm">Granting Workloads Access to OCI Resources</a>. To use workload identity, ensure Rclone is started with these environment variables set in its process.</p>
+<p>Workload Identity auth may be used when running Rclone from
+Kubernetes pod on a Container Engine for Kubernetes (OKE) cluster. For
+more details on configuring Workload Identity, see <a
+href="https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contenggrantingworkloadaccesstoresources.htm">Granting
+Workloads Access to OCI Resources</a>. To use workload identity, ensure
+Rclone is started with these environment variables set in its
+process.</p>
 <pre><code>export OCI_RESOURCE_PRINCIPAL_VERSION=2.2
 export OCI_RESOURCE_PRINCIPAL_REGION=us-ashburn-1</code></pre>
 <h3 id="no-authentication">No authentication</h3>
-<p>Public buckets do not require any authentication mechanism to read objects. Sample rclone configuration file for No authentication:</p>
+<p>Public buckets do not require any authentication mechanism to read
+objects. Sample rclone configuration file for No authentication:</p>
 <pre><code>[oos]
 type = oracleobjectstorage
 namespace = id&lt;redacted&gt;34
 compartment = ocid1.compartment.oc1..aa&lt;redacted&gt;ba
 region = us-ashburn-1
 provider = no_auth</code></pre>
-<h3 id="modification-times-and-hashes-17">Modification times and hashes</h3>
-<p>The modification time is stored as metadata on the object as <code>opc-meta-mtime</code> as floating point since the epoch, accurate to 1 ns.</p>
-<p>If the modification time needs to be updated rclone will attempt to perform a server side copy to update the modification if the object can be copied in a single part. In the case the object is larger than 5Gb, the object will be uploaded rather than copied.</p>
-<p>Note that reading this from the object takes an additional <code>HEAD</code> request as the metadata isn't returned in object listings.</p>
+<h3 id="modification-times-and-hashes-17">Modification times and
+hashes</h3>
+<p>The modification time is stored as metadata on the object as
+<code>opc-meta-mtime</code> as floating point since the epoch, accurate
+to 1 ns.</p>
+<p>If the modification time needs to be updated rclone will attempt to
+perform a server side copy to update the modification if the object can
+be copied in a single part. In the case the object is larger than 5Gb,
+the object will be uploaded rather than copied.</p>
+<p>Note that reading this from the object takes an additional
+<code>HEAD</code> request as the metadata isn't returned in object
+listings.</p>
 <p>The MD5 hash algorithm is supported.</p>
 <h3 id="multipart-uploads-1">Multipart uploads</h3>
-<p>rclone supports multipart uploads with OOS which means that it can upload files bigger than 5 GiB.</p>
-<p>Note that files uploaded <em>both</em> with multipart upload <em>and</em> through crypt remotes do not have MD5 sums.</p>
-<p>rclone switches from single part uploads to multipart uploads at the point specified by <code>--oos-upload-cutoff</code>. This can be a maximum of 5 GiB and a minimum of 0 (ie always upload multipart files).</p>
-<p>The chunk sizes used in the multipart upload are specified by <code>--oos-chunk-size</code> and the number of chunks uploaded concurrently is specified by <code>--oos-upload-concurrency</code>.</p>
-<p>Multipart uploads will use <code>--transfers</code> * <code>--oos-upload-concurrency</code> * <code>--oos-chunk-size</code> extra memory. Single part uploads to not use extra memory.</p>
-<p>Single part transfers can be faster than multipart transfers or slower depending on your latency from oos - the more latency, the more likely single part transfers will be faster.</p>
-<p>Increasing <code>--oos-upload-concurrency</code> will increase throughput (8 would be a sensible value) and increasing <code>--oos-chunk-size</code> also increases throughput (16M would be sensible). Increasing either of these will use more memory. The default values are high enough to gain most of the possible performance without using too much memory.</p>
-<h3 id="standard-options-35">Standard options</h3>
-<p>Here are the Standard options specific to oracleobjectstorage (Oracle Cloud Infrastructure Object Storage).</p>
+<p>rclone supports multipart uploads with OOS which means that it can
+upload files bigger than 5 GiB.</p>
+<p>Note that files uploaded <em>both</em> with multipart upload
+<em>and</em> through crypt remotes do not have MD5 sums.</p>
+<p>rclone switches from single part uploads to multipart uploads at the
+point specified by <code>--oos-upload-cutoff</code>. This can be a
+maximum of 5 GiB and a minimum of 0 (ie always upload multipart
+files).</p>
+<p>The chunk sizes used in the multipart upload are specified by
+<code>--oos-chunk-size</code> and the number of chunks uploaded
+concurrently is specified by <code>--oos-upload-concurrency</code>.</p>
+<p>Multipart uploads will use <code>--transfers</code> *
+<code>--oos-upload-concurrency</code> * <code>--oos-chunk-size</code>
+extra memory. Single part uploads to not use extra memory.</p>
+<p>Single part transfers can be faster than multipart transfers or
+slower depending on your latency from oos - the more latency, the more
+likely single part transfers will be faster.</p>
+<p>Increasing <code>--oos-upload-concurrency</code> will increase
+throughput (8 would be a sensible value) and increasing
+<code>--oos-chunk-size</code> also increases throughput (16M would be
+sensible). Increasing either of these will use more memory. The default
+values are high enough to gain most of the possible performance without
+using too much memory.</p>
+<h3 id="standard-options-36">Standard options</h3>
+<p>Here are the Standard options specific to oracleobjectstorage (Oracle
+Cloud Infrastructure Object Storage).</p>
 <h4 id="oos-provider">--oos-provider</h4>
 <p>Choose your Auth Provider</p>
 <p>Properties:</p>
@@ -30436,23 +44072,29 @@ provider = no_auth</code></pre>
 <ul>
 <li>"env_auth"
 <ul>
-<li>automatically pickup the credentials from runtime(env), first one to provide auth wins</li>
+<li>automatically pickup the credentials from runtime(env), first one to
+provide auth wins</li>
 </ul></li>
 <li>"user_principal_auth"
 <ul>
 <li>use an OCI user and an API key for authentication.</li>
-<li>you’ll need to put in a config file your tenancy OCID, user OCID, region, the path, fingerprint to an API key.</li>
+<li>you’ll need to put in a config file your tenancy OCID, user OCID,
+region, the path, fingerprint to an API key.</li>
 <li>https://docs.oracle.com/en-us/iaas/Content/API/Concepts/sdkconfig.htm</li>
 </ul></li>
 <li>"instance_principal_auth"
 <ul>
-<li>use instance principals to authorize an instance to make API calls.</li>
-<li>each instance has its own identity, and authenticates using the certificates that are read from instance metadata.</li>
+<li>use instance principals to authorize an instance to make API
+calls.</li>
+<li>each instance has its own identity, and authenticates using the
+certificates that are read from instance metadata.</li>
 <li>https://docs.oracle.com/en-us/iaas/Content/Identity/Tasks/callingservicesfrominstances.htm</li>
 </ul></li>
 <li>"workload_identity_auth"
 <ul>
-<li>use workload identity to grant OCI Container Engine for Kubernetes workloads policy-driven access to OCI resources using OCI Identity and Access Management (IAM).</li>
+<li>use workload identity to grant OCI Container Engine for Kubernetes
+workloads policy-driven access to OCI resources using OCI Identity and
+Access Management (IAM).</li>
 <li>https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contenggrantingworkloadaccesstoresources.htm</li>
 </ul></li>
 <li>"resource_principal_auth"
@@ -30461,7 +44103,8 @@ provider = no_auth</code></pre>
 </ul></li>
 <li>"no_auth"
 <ul>
-<li>no credentials needed, this is typically for reading public buckets</li>
+<li>no credentials needed, this is typically for reading public
+buckets</li>
 </ul></li>
 </ul></li>
 </ul>
@@ -30537,10 +44180,12 @@ provider = no_auth</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-36">Advanced options</h3>
-<p>Here are the Advanced options specific to oracleobjectstorage (Oracle Cloud Infrastructure Object Storage).</p>
+<h3 id="advanced-options-37">Advanced options</h3>
+<p>Here are the Advanced options specific to oracleobjectstorage (Oracle
+Cloud Infrastructure Object Storage).</p>
 <h4 id="oos-storage-tier">--oos-storage-tier</h4>
-<p>The storage class to use when storing new objects in storage. https://docs.oracle.com/en-us/iaas/Content/Object/Concepts/understandingstoragetiers.htm</p>
+<p>The storage class to use when storing new objects in storage.
+https://docs.oracle.com/en-us/iaas/Content/Object/Concepts/understandingstoragetiers.htm</p>
 <p>Properties:</p>
 <ul>
 <li>Config: storage_tier</li>
@@ -30565,7 +44210,8 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-upload-cutoff">--oos-upload-cutoff</h4>
 <p>Cutoff for switching to chunked upload.</p>
-<p>Any files larger than this will be uploaded in chunks of chunk_size. The minimum is 0 and the maximum is 5 GiB.</p>
+<p>Any files larger than this will be uploaded in chunks of chunk_size.
+The minimum is 0 and the maximum is 5 GiB.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_cutoff</li>
@@ -30575,12 +44221,23 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-chunk-size">--oos-chunk-size</h4>
 <p>Chunk size to use for uploading.</p>
-<p>When uploading files larger than upload_cutoff or files with unknown size (e.g. from "rclone rcat" or uploaded with "rclone mount" they will be uploaded as multipart uploads using this chunk size.</p>
-<p>Note that "upload_concurrency" chunks of this size are buffered in memory per transfer.</p>
-<p>If you are transferring large files over high-speed links and you have enough memory, then increasing this will speed up the transfers.</p>
-<p>Rclone will automatically increase the chunk size when uploading a large file of known size to stay below the 10,000 chunks limit.</p>
-<p>Files of unknown size are uploaded with the configured chunk_size. Since the default chunk size is 5 MiB and there can be at most 10,000 chunks, this means that by default the maximum size of a file you can stream upload is 48 GiB. If you wish to stream upload larger files then you will need to increase chunk_size.</p>
-<p>Increasing the chunk size decreases the accuracy of the progress statistics displayed with "-P" flag.</p>
+<p>When uploading files larger than upload_cutoff or files with unknown
+size (e.g. from "rclone rcat" or uploaded with "rclone mount" they will
+be uploaded as multipart uploads using this chunk size.</p>
+<p>Note that "upload_concurrency" chunks of this size are buffered in
+memory per transfer.</p>
+<p>If you are transferring large files over high-speed links and you
+have enough memory, then increasing this will speed up the
+transfers.</p>
+<p>Rclone will automatically increase the chunk size when uploading a
+large file of known size to stay below the 10,000 chunks limit.</p>
+<p>Files of unknown size are uploaded with the configured chunk_size.
+Since the default chunk size is 5 MiB and there can be at most 10,000
+chunks, this means that by default the maximum size of a file you can
+stream upload is 48 GiB. If you wish to stream upload larger files then
+you will need to increase chunk_size.</p>
+<p>Increasing the chunk size decreases the accuracy of the progress
+statistics displayed with "-P" flag.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -30590,9 +44247,12 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-max-upload-parts">--oos-max-upload-parts</h4>
 <p>Maximum number of parts in a multipart upload.</p>
-<p>This option defines the maximum number of multipart chunks to use when doing a multipart upload.</p>
+<p>This option defines the maximum number of multipart chunks to use
+when doing a multipart upload.</p>
 <p>OCI has max parts limit of 10,000 chunks.</p>
-<p>Rclone will automatically increase the chunk size when uploading a large file of a known size to stay below this number of chunks limit.</p>
+<p>Rclone will automatically increase the chunk size when uploading a
+large file of a known size to stay below this number of chunks
+limit.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: max_upload_parts</li>
@@ -30602,8 +44262,11 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-upload-concurrency">--oos-upload-concurrency</h4>
 <p>Concurrency for multipart uploads.</p>
-<p>This is the number of chunks of the same file that are uploaded concurrently.</p>
-<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
+<p>This is the number of chunks of the same file that are uploaded
+concurrently.</p>
+<p>If you are uploading small numbers of large files over high-speed
+links and these uploads do not fully utilize your bandwidth, then
+increasing this may help to speed up the transfers.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_concurrency</li>
@@ -30613,7 +44276,8 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-copy-cutoff">--oos-copy-cutoff</h4>
 <p>Cutoff for switching to multipart copy.</p>
-<p>Any files larger than this that need to be server-side copied will be copied in chunks of this size.</p>
+<p>Any files larger than this that need to be server-side copied will be
+copied in chunks of this size.</p>
 <p>The minimum is 0 and the maximum is 5 GiB.</p>
 <p>Properties:</p>
 <ul>
@@ -30624,7 +44288,8 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-copy-timeout">--oos-copy-timeout</h4>
 <p>Timeout for copy.</p>
-<p>Copy is an asynchronous operation, specify timeout to wait for copy to succeed</p>
+<p>Copy is an asynchronous operation, specify timeout to wait for copy
+to succeed</p>
 <p>Properties:</p>
 <ul>
 <li>Config: copy_timeout</li>
@@ -30634,7 +44299,10 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-disable-checksum">--oos-disable-checksum</h4>
 <p>Don't store MD5 checksum with object metadata.</p>
-<p>Normally rclone will calculate the MD5 checksum of the input before uploading it so it can add it to metadata on the object. This is great for data integrity checking but can cause long delays for large files to start uploading.</p>
+<p>Normally rclone will calculate the MD5 checksum of the input before
+uploading it so it can add it to metadata on the object. This is great
+for data integrity checking but can cause long delays for large files to
+start uploading.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_checksum</li>
@@ -30644,7 +44312,8 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-encoding">--oos-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -30653,9 +44322,13 @@ provider = no_auth</code></pre>
 <li>Default: Slash,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="oos-leave-parts-on-error">--oos-leave-parts-on-error</h4>
-<p>If true avoid calling abort upload on a failure, leaving all successfully uploaded parts for manual recovery.</p>
-<p>It should be set to true for resuming uploads across different sessions.</p>
-<p>WARNING: Storing parts of an incomplete multipart upload counts towards space usage on object storage and will add additional costs if not cleaned up.</p>
+<p>If true avoid calling abort upload on a failure, leaving all
+successfully uploaded parts for manual recovery.</p>
+<p>It should be set to true for resuming uploads across different
+sessions.</p>
+<p>WARNING: Storing parts of an incomplete multipart upload counts
+towards space usage on object storage and will add additional costs if
+not cleaned up.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: leave_parts_on_error</li>
@@ -30664,9 +44337,14 @@ provider = no_auth</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="oos-attempt-resume-upload">--oos-attempt-resume-upload</h4>
-<p>If true attempt to resume previously started multipart upload for the object. This will be helpful to speed up multipart transfers by resuming uploads from past session.</p>
-<p>WARNING: If chunk size differs in resumed session from past incomplete session, then the resumed multipart upload is aborted and a new multipart upload is started with the new chunk size.</p>
-<p>The flag leave_parts_on_error must be true to resume and optimize to skip parts that were already uploaded successfully.</p>
+<p>If true attempt to resume previously started multipart upload for the
+object. This will be helpful to speed up multipart transfers by resuming
+uploads from past session.</p>
+<p>WARNING: If chunk size differs in resumed session from past
+incomplete session, then the resumed multipart upload is aborted and a
+new multipart upload is started with the new chunk size.</p>
+<p>The flag leave_parts_on_error must be true to resume and optimize to
+skip parts that were already uploaded successfully.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: attempt_resume_upload</li>
@@ -30676,8 +44354,10 @@ provider = no_auth</code></pre>
 </ul>
 <h4 id="oos-no-check-bucket">--oos-no-check-bucket</h4>
 <p>If set, don't attempt to check the bucket exists or create it.</p>
-<p>This can be useful when trying to minimise the number of transactions rclone does if you know the bucket exists already.</p>
-<p>It can also be needed if the user you are using does not have bucket creation permissions.</p>
+<p>This can be useful when trying to minimise the number of transactions
+rclone does if you know the bucket exists already.</p>
+<p>It can also be needed if the user you are using does not have bucket
+creation permissions.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_check_bucket</li>
@@ -30686,7 +44366,9 @@ provider = no_auth</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="oos-sse-customer-key-file">--oos-sse-customer-key-file</h4>
-<p>To use SSE-C, a file containing the base64-encoded string of the AES-256 encryption key associated with the object. Please note only one of sse_customer_key_file|sse_customer_key|sse_kms_key_id is needed.'</p>
+<p>To use SSE-C, a file containing the base64-encoded string of the
+AES-256 encryption key associated with the object. Please note only one
+of sse_customer_key_file|sse_customer_key|sse_kms_key_id is needed.'</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sse_customer_key_file</li>
@@ -30702,7 +44384,12 @@ provider = no_auth</code></pre>
 </ul></li>
 </ul>
 <h4 id="oos-sse-customer-key">--oos-sse-customer-key</h4>
-<p>To use SSE-C, the optional header that specifies the base64-encoded 256-bit encryption key to use to encrypt or decrypt the data. Please note only one of sse_customer_key_file|sse_customer_key|sse_kms_key_id is needed. For more information, see Using Your Own Keys for Server-Side Encryption (https://docs.cloud.oracle.com/Content/Object/Tasks/usingyourencryptionkeys.htm)</p>
+<p>To use SSE-C, the optional header that specifies the base64-encoded
+256-bit encryption key to use to encrypt or decrypt the data. Please
+note only one of sse_customer_key_file|sse_customer_key|sse_kms_key_id
+is needed. For more information, see Using Your Own Keys for Server-Side
+Encryption
+(https://docs.cloud.oracle.com/Content/Object/Tasks/usingyourencryptionkeys.htm)</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sse_customer_key</li>
@@ -30718,7 +44405,11 @@ provider = no_auth</code></pre>
 </ul></li>
 </ul>
 <h4 id="oos-sse-customer-key-sha256">--oos-sse-customer-key-sha256</h4>
-<p>If using SSE-C, The optional header that specifies the base64-encoded SHA256 hash of the encryption key. This value is used to check the integrity of the encryption key. see Using Your Own Keys for Server-Side Encryption (https://docs.cloud.oracle.com/Content/Object/Tasks/usingyourencryptionkeys.htm).</p>
+<p>If using SSE-C, The optional header that specifies the base64-encoded
+SHA256 hash of the encryption key. This value is used to check the
+integrity of the encryption key. see Using Your Own Keys for Server-Side
+Encryption
+(https://docs.cloud.oracle.com/Content/Object/Tasks/usingyourencryptionkeys.htm).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sse_customer_key_sha256</li>
@@ -30734,7 +44425,12 @@ provider = no_auth</code></pre>
 </ul></li>
 </ul>
 <h4 id="oos-sse-kms-key-id">--oos-sse-kms-key-id</h4>
-<p>if using your own master key in vault, this header specifies the OCID (https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm) of a master encryption key used to call the Key Management service to generate a data encryption key or to encrypt or decrypt a data encryption key. Please note only one of sse_customer_key_file|sse_customer_key|sse_kms_key_id is needed.</p>
+<p>if using your own master key in vault, this header specifies the OCID
+(https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm)
+of a master encryption key used to call the Key Management service to
+generate a data encryption key or to encrypt or decrypt a data
+encryption key. Please note only one of
+sse_customer_key_file|sse_customer_key|sse_kms_key_id is needed.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sse_kms_key_id</li>
@@ -30750,7 +44446,11 @@ provider = no_auth</code></pre>
 </ul></li>
 </ul>
 <h4 id="oos-sse-customer-algorithm">--oos-sse-customer-algorithm</h4>
-<p>If using SSE-C, the optional header that specifies "AES256" as the encryption algorithm. Object Storage supports "AES256" as the encryption algorithm. For more information, see Using Your Own Keys for Server-Side Encryption (https://docs.cloud.oracle.com/Content/Object/Tasks/usingyourencryptionkeys.htm).</p>
+<p>If using SSE-C, the optional header that specifies "AES256" as the
+encryption algorithm. Object Storage supports "AES256" as the encryption
+algorithm. For more information, see Using Your Own Keys for Server-Side
+Encryption
+(https://docs.cloud.oracle.com/Content/Object/Tasks/usingyourencryptionkeys.htm).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: sse_customer_algorithm</li>
@@ -30779,12 +44479,16 @@ provider = no_auth</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="backend-commands-8">Backend commands</h2>
-<p>Here are the commands specific to the oracleobjectstorage backend.</p>
+<p>Here are the commands specific to the oracleobjectstorage
+backend.</p>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="rename">rename</h3>
 <p>change the name of an object</p>
 <pre><code>rclone backend rename remote: [options] [&lt;arguments&gt;+]</code></pre>
@@ -30794,10 +44498,13 @@ provider = no_auth</code></pre>
 <h3 id="list-multipart-uploads-1">list-multipart-uploads</h3>
 <p>List the unfinished multipart uploads</p>
 <pre><code>rclone backend list-multipart-uploads remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command lists the unfinished multipart uploads in JSON format.</p>
+<p>This command lists the unfinished multipart uploads in JSON
+format.</p>
 <pre><code>rclone backend list-multipart-uploads oos:bucket/path/to/object</code></pre>
-<p>It returns a dictionary of buckets with values as lists of unfinished multipart uploads.</p>
-<p>You can call it with no bucket in which case it lists all bucket, with a bucket or with a bucket and path.</p>
+<p>It returns a dictionary of buckets with values as lists of unfinished
+multipart uploads.</p>
+<p>You can call it with no bucket in which case it lists all bucket,
+with a bucket or with a bucket and path.</p>
 <pre><code>{
   &quot;test-bucket&quot;: [
             {
@@ -30812,8 +44519,10 @@ provider = no_auth</code></pre>
 <h3 id="cleanup-5">cleanup</h3>
 <p>Remove unfinished multipart uploads.</p>
 <pre><code>rclone backend cleanup remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command removes unfinished multipart uploads of age greater than max-age which defaults to 24 hours.</p>
-<p>Note that you can use --interactive/-i or --dry-run with this command to see what it would do.</p>
+<p>This command removes unfinished multipart uploads of age greater than
+max-age which defaults to 24 hours.</p>
+<p>Note that you can use --interactive/-i or --dry-run with this command
+to see what it would do.</p>
 <pre><code>rclone backend cleanup oos:bucket/path/to/object
 rclone backend cleanup -o max-age=7w oos:bucket/path/to/object</code></pre>
 <p>Durations are parsed as per the rest of rclone, 2h, 7d, 7w etc.</p>
@@ -30824,12 +44533,14 @@ rclone backend cleanup -o max-age=7w oos:bucket/path/to/object</code></pre>
 <h3 id="restore-1">restore</h3>
 <p>Restore objects from Archive to Standard storage</p>
 <pre><code>rclone backend restore remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This command can be used to restore one or more objects from Archive to Standard storage.</p>
+<p>This command can be used to restore one or more objects from Archive
+to Standard storage.</p>
 <pre><code>Usage Examples:
 
 rclone backend restore oos:bucket/path/to/directory -o hours=HOURS
 rclone backend restore oos:bucket -o hours=HOURS</code></pre>
-<p>This flag also obeys the filters. Test first with --interactive/-i or --dry-run flags</p>
+<p>This flag also obeys the filters. Test first with --interactive/-i or
+--dry-run flags</p>
 <pre><code>rclone --interactive backend restore --include &quot;*.txt&quot; oos:bucket/path -o hours=72</code></pre>
 <p>All the objects shown will be marked for restore, then</p>
 <pre><code>rclone backend restore --include &quot;*.txt&quot; oos:bucket/path -o hours=72
@@ -30850,13 +44561,18 @@ if not.
 ]</code></pre>
 <p>Options:</p>
 <ul>
-<li>"hours": The number of hours for which this object will be restored. Default is 24 hrs.</li>
+<li>"hours": The number of hours for which this object will be restored.
+Default is 24 hrs.</li>
 </ul>
 <h2 id="tutorials">Tutorials</h2>
-<h3 id="mounting-buckets"><a href="https://rclone.org/oracleobjectstorage/tutorial_mount/">Mounting Buckets</a></h3>
+<h3 id="mounting-buckets"><a
+href="https://rclone.org/oracleobjectstorage/tutorial_mount/">Mounting
+Buckets</a></h3>
 <h1 id="qingstor">QingStor</h1>
-<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
-<h2 id="configuration-36">Configuration</h2>
+<p>Paths are specified as <code>remote:bucket</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
+<h2 id="configuration-37">Configuration</h2>
 <p>Here is an example of making an QingStor configuration. First run</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
@@ -30916,44 +44632,72 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>This remote is called <code>remote</code> and can now be used like this</p>
+<p>This remote is called <code>remote</code> and can now be used like
+this</p>
 <p>See all buckets</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>Make a new bucket</p>
 <pre><code>rclone mkdir remote:bucket</code></pre>
 <p>List the contents of a bucket</p>
 <pre><code>rclone ls remote:bucket</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote bucket, deleting any excess files in the bucket.</p>
+<p>Sync <code>/home/local/directory</code> to the remote bucket,
+deleting any excess files in the bucket.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:bucket</code></pre>
 <h3 id="fast-list-7">--fast-list</h3>
-<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
+<p>This remote supports <code>--fast-list</code> which allows you to use
+fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details.</p>
 <h3 id="multipart-uploads-2">Multipart uploads</h3>
-<p>rclone supports multipart uploads with QingStor which means that it can upload files bigger than 5 GiB. Note that files uploaded with multipart upload don't have an MD5SUM.</p>
-<p>Note that incomplete multipart uploads older than 24 hours can be removed with <code>rclone cleanup remote:bucket</code> just for one bucket <code>rclone cleanup remote:</code> for all buckets. QingStor does not ever remove incomplete multipart uploads so it may be necessary to run this from time to time.</p>
+<p>rclone supports multipart uploads with QingStor which means that it
+can upload files bigger than 5 GiB. Note that files uploaded with
+multipart upload don't have an MD5SUM.</p>
+<p>Note that incomplete multipart uploads older than 24 hours can be
+removed with <code>rclone cleanup remote:bucket</code> just for one
+bucket <code>rclone cleanup remote:</code> for all buckets. QingStor
+does not ever remove incomplete multipart uploads so it may be necessary
+to run this from time to time.</p>
 <h3 id="buckets-and-zone">Buckets and Zone</h3>
-<p>With QingStor you can list buckets (<code>rclone lsd</code>) using any zone, but you can only access the content of a bucket from the zone it was created in. If you attempt to access a bucket from the wrong zone, you will get an error, <code>incorrect zone, the bucket is not in 'XXX' zone</code>.</p>
+<p>With QingStor you can list buckets (<code>rclone lsd</code>) using
+any zone, but you can only access the content of a bucket from the zone
+it was created in. If you attempt to access a bucket from the wrong
+zone, you will get an error,
+<code>incorrect zone, the bucket is not in 'XXX' zone</code>.</p>
 <h3 id="authentication-6">Authentication</h3>
-<p>There are two ways to supply <code>rclone</code> with a set of QingStor credentials. In order of precedence:</p>
+<p>There are two ways to supply <code>rclone</code> with a set of
+QingStor credentials. In order of precedence:</p>
 <ul>
-<li>Directly in the rclone configuration file (as configured by <code>rclone config</code>)
+<li>Directly in the rclone configuration file (as configured by
+<code>rclone config</code>)
 <ul>
-<li>set <code>access_key_id</code> and <code>secret_access_key</code></li>
+<li>set <code>access_key_id</code> and
+<code>secret_access_key</code></li>
 </ul></li>
 <li>Runtime configuration:
 <ul>
-<li>set <code>env_auth</code> to <code>true</code> in the config file</li>
-<li>Exporting the following environment variables before running <code>rclone</code>
+<li>set <code>env_auth</code> to <code>true</code> in the config
+file</li>
+<li>Exporting the following environment variables before running
+<code>rclone</code>
 <ul>
-<li>Access Key ID: <code>QS_ACCESS_KEY_ID</code> or <code>QS_ACCESS_KEY</code></li>
-<li>Secret Access Key: <code>QS_SECRET_ACCESS_KEY</code> or <code>QS_SECRET_KEY</code></li>
+<li>Access Key ID: <code>QS_ACCESS_KEY_ID</code> or
+<code>QS_ACCESS_KEY</code></li>
+<li>Secret Access Key: <code>QS_SECRET_ACCESS_KEY</code> or
+<code>QS_SECRET_KEY</code></li>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="restricted-filename-characters-22">Restricted filename characters</h3>
-<p>The control characters 0x00-0x1F and / are replaced as in the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a>. Note that 0x7F is not replaced.</p>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<h3 id="standard-options-36">Standard options</h3>
-<p>Here are the Standard options specific to qingstor (QingCloud Object Storage).</p>
+<h3 id="restricted-filename-characters-21">Restricted filename
+characters</h3>
+<p>The control characters 0x00-0x1F and / are replaced as in the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a>. Note that 0x7F is not replaced.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<h3 id="standard-options-37">Standard options</h3>
+<p>Here are the Standard options specific to qingstor (QingCloud Object
+Storage).</p>
 <h4 id="qingstor-env-auth">--qingstor-env-auth</h4>
 <p>Get QingStor credentials from runtime.</p>
 <p>Only applies if access_key_id and secret_access_key is blank.</p>
@@ -30971,7 +44715,8 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 <li>"true"
 <ul>
-<li>Get QingStor credentials from the environment (env vars or IAM).</li>
+<li>Get QingStor credentials from the environment (env vars or
+IAM).</li>
 </ul></li>
 </ul></li>
 </ul>
@@ -30997,7 +44742,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="qingstor-endpoint">--qingstor-endpoint</h4>
 <p>Enter an endpoint URL to connection QingStor API.</p>
-<p>Leave blank will use the default value "https://qingstor.com:443".</p>
+<p>Leave blank will use the default value
+"https://qingstor.com:443".</p>
 <p>Properties:</p>
 <ul>
 <li>Config: endpoint</li>
@@ -31033,8 +44779,9 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-37">Advanced options</h3>
-<p>Here are the Advanced options specific to qingstor (QingCloud Object Storage).</p>
+<h3 id="advanced-options-38">Advanced options</h3>
+<p>Here are the Advanced options specific to qingstor (QingCloud Object
+Storage).</p>
 <h4 id="qingstor-connection-retries">--qingstor-connection-retries</h4>
 <p>Number of connection retries.</p>
 <p>Properties:</p>
@@ -31046,7 +44793,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="qingstor-upload-cutoff">--qingstor-upload-cutoff</h4>
 <p>Cutoff for switching to chunked upload.</p>
-<p>Any files larger than this will be uploaded in chunks of chunk_size. The minimum is 0 and the maximum is 5 GiB.</p>
+<p>Any files larger than this will be uploaded in chunks of chunk_size.
+The minimum is 0 and the maximum is 5 GiB.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_cutoff</li>
@@ -31056,9 +44804,13 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="qingstor-chunk-size">--qingstor-chunk-size</h4>
 <p>Chunk size to use for uploading.</p>
-<p>When uploading files larger than upload_cutoff they will be uploaded as multipart uploads using this chunk size.</p>
-<p>Note that "--qingstor-upload-concurrency" chunks of this size are buffered in memory per transfer.</p>
-<p>If you are transferring large files over high-speed links and you have enough memory, then increasing this will speed up the transfers.</p>
+<p>When uploading files larger than upload_cutoff they will be uploaded
+as multipart uploads using this chunk size.</p>
+<p>Note that "--qingstor-upload-concurrency" chunks of this size are
+buffered in memory per transfer.</p>
+<p>If you are transferring large files over high-speed links and you
+have enough memory, then increasing this will speed up the
+transfers.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -31068,9 +44820,13 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="qingstor-upload-concurrency">--qingstor-upload-concurrency</h4>
 <p>Concurrency for multipart uploads.</p>
-<p>This is the number of chunks of the same file that are uploaded concurrently.</p>
-<p>NB if you set this to &gt; 1 then the checksums of multipart uploads become corrupted (the uploads themselves are not corrupted though).</p>
-<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
+<p>This is the number of chunks of the same file that are uploaded
+concurrently.</p>
+<p>NB if you set this to &gt; 1 then the checksums of multipart uploads
+become corrupted (the uploads themselves are not corrupted though).</p>
+<p>If you are uploading small numbers of large files over high-speed
+links and these uploads do not fully utilize your bandwidth, then
+increasing this may help to speed up the transfers.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_concurrency</li>
@@ -31080,7 +44836,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="qingstor-encoding">--qingstor-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -31098,16 +44855,30 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-28">Limitations</h2>
-<p><code>rclone about</code> is not supported by the qingstor backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the qingstor backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="quatrix">Quatrix</h1>
-<p>Quatrix by Maytech is <a href="https://www.maytech.net/products/quatrix-business">Quatrix Secure Compliant File Sharing | Maytech</a>.</p>
+<p>Quatrix by Maytech is <a
+href="https://www.maytech.net/products/quatrix-business">Quatrix Secure
+Compliant File Sharing | Maytech</a>.</p>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g., <code>remote:directory/subdirectory</code>.</p>
-<p>The initial setup for Quatrix involves getting an API Key from Quatrix. You can get the API key in the user's profile at <code>https://&lt;account&gt;/profile/api-keys</code> or with the help of the API - https://docs.maytech.net/quatrix/quatrix-api/api-explorer#/API-Key/post_api_key_create.</p>
-<p>See complete Swagger documentation for Quatrix - https://docs.maytech.net/quatrix/quatrix-api/api-explorer</p>
-<h2 id="configuration-37">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.,
+<code>remote:directory/subdirectory</code>.</p>
+<p>The initial setup for Quatrix involves getting an API Key from
+Quatrix. You can get the API key in the user's profile at
+<code>https://&lt;account&gt;/profile/api-keys</code> or with the help
+of the API -
+https://docs.maytech.net/quatrix/quatrix-api/api-explorer#/API-Key/post_api_key_create.</p>
+<p>See complete Swagger documentation for Quatrix -
+https://docs.maytech.net/quatrix/quatrix-api/api-explorer</p>
+<h2 id="configuration-38">Configuration</h2>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -31146,7 +44917,11 @@ y/e/d&gt; y</code></pre>
 <p>To copy a local directory to an Quatrix directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <h3 id="api-key-validity">API key validity</h3>
-<p>API Key is created with no expiration date. It will be valid until you delete or deactivate it in your account. After disabling, the API Key can be enabled back. If the API Key was deleted and a new key was created, you can update it in rclone config. The same happens if the hostname was changed.</p>
+<p>API Key is created with no expiration date. It will be valid until
+you delete or deactivate it in your account. After disabling, the API
+Key can be enabled back. If the API Key was deleted and a new key was
+created, you can update it in rclone config. The same happens if the
+hostname was changed.</p>
 <pre><code>$ rclone config
 Current remotes:
 
@@ -31190,17 +44965,44 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<h3 id="modification-times-and-hashes-18">Modification times and hashes</h3>
-<p>Quatrix allows modification times to be set on objects accurate to 1 microsecond. These will be used to detect whether objects need syncing or not.</p>
-<p>Quatrix does not support hashes, so you cannot use the <code>--checksum</code> flag.</p>
-<h3 id="restricted-filename-characters-23">Restricted filename characters</h3>
-<p>File names in Quatrix are case sensitive and have limitations like the maximum length of a filename is 255, and the minimum length is 1. A file name cannot be equal to <code>.</code> or <code>..</code> nor contain <code>/</code> , <code>\</code> or non-printable ascii.</p>
+<h3 id="modification-times-and-hashes-18">Modification times and
+hashes</h3>
+<p>Quatrix allows modification times to be set on objects accurate to 1
+microsecond. These will be used to detect whether objects need syncing
+or not.</p>
+<p>Quatrix does not support hashes, so you cannot use the
+<code>--checksum</code> flag.</p>
+<h3 id="restricted-filename-characters-22">Restricted filename
+characters</h3>
+<p>File names in Quatrix are case sensitive and have limitations like
+the maximum length of a filename is 255, and the minimum length is 1. A
+file name cannot be equal to <code>.</code> or <code>..</code> nor
+contain <code>/</code> , <code>\</code> or non-printable ascii.</p>
 <h3 id="transfers-4">Transfers</h3>
-<p>For files above 50 MiB rclone will use a chunked transfer. Rclone will upload up to <code>--transfers</code> chunks at the same time (shared among all multipart uploads). Chunks are buffered in memory, and the minimal chunk size is 10_000_000 bytes by default, and it can be changed in the advanced configuration, so increasing <code>--transfers</code> will increase the memory use. The chunk size has a maximum size limit, which is set to 100_000_000 bytes by default and can be changed in the advanced configuration. The size of the uploaded chunk will dynamically change depending on the upload speed. The total memory use equals the number of transfers multiplied by the minimal chunk size. In case there's free memory allocated for the upload (which equals the difference of <code>maximal_summary_chunk_size</code> and <code>minimal_chunk_size</code> * <code>transfers</code>), the chunk size may increase in case of high upload speed. As well as it can decrease in case of upload speed problems. If no free memory is available, all chunks will equal <code>minimal_chunk_size</code>.</p>
+<p>For files above 50 MiB rclone will use a chunked transfer. Rclone
+will upload up to <code>--transfers</code> chunks at the same time
+(shared among all multipart uploads). Chunks are buffered in memory, and
+the minimal chunk size is 10_000_000 bytes by default, and it can be
+changed in the advanced configuration, so increasing
+<code>--transfers</code> will increase the memory use. The chunk size
+has a maximum size limit, which is set to 100_000_000 bytes by default
+and can be changed in the advanced configuration. The size of the
+uploaded chunk will dynamically change depending on the upload speed.
+The total memory use equals the number of transfers multiplied by the
+minimal chunk size. In case there's free memory allocated for the upload
+(which equals the difference of <code>maximal_summary_chunk_size</code>
+and <code>minimal_chunk_size</code> * <code>transfers</code>), the chunk
+size may increase in case of high upload speed. As well as it can
+decrease in case of upload speed problems. If no free memory is
+available, all chunks will equal <code>minimal_chunk_size</code>.</p>
 <h3 id="deleting-files-5">Deleting files</h3>
-<p>Files you delete with rclone will end up in Trash and be stored there for 30 days. Quatrix also provides an API to permanently delete files and an API to empty the Trash so that you can remove files permanently from your account.</p>
-<h3 id="standard-options-37">Standard options</h3>
-<p>Here are the Standard options specific to quatrix (Quatrix by Maytech).</p>
+<p>Files you delete with rclone will end up in Trash and be stored there
+for 30 days. Quatrix also provides an API to permanently delete files
+and an API to empty the Trash so that you can remove files permanently
+from your account.</p>
+<h3 id="standard-options-38">Standard options</h3>
+<p>Here are the Standard options specific to quatrix (Quatrix by
+Maytech).</p>
 <h4 id="quatrix-api-key">--quatrix-api-key</h4>
 <p>API key for accessing Quatrix account</p>
 <p>Properties:</p>
@@ -31219,11 +45021,13 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: true</li>
 </ul>
-<h3 id="advanced-options-38">Advanced options</h3>
-<p>Here are the Advanced options specific to quatrix (Quatrix by Maytech).</p>
+<h3 id="advanced-options-39">Advanced options</h3>
+<p>Here are the Advanced options specific to quatrix (Quatrix by
+Maytech).</p>
 <h4 id="quatrix-encoding">--quatrix-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -31231,7 +45035,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: Encoding</li>
 <li>Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
-<h4 id="quatrix-effective-upload-time">--quatrix-effective-upload-time</h4>
+<h4
+id="quatrix-effective-upload-time">--quatrix-effective-upload-time</h4>
 <p>Wanted upload time for one chunk</p>
 <p>Properties:</p>
 <ul>
@@ -31249,8 +45054,10 @@ y/e/d&gt; y</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 9.537Mi</li>
 </ul>
-<h4 id="quatrix-maximal-summary-chunk-size">--quatrix-maximal-summary-chunk-size</h4>
-<p>The maximal summary for all chunks. It should not be less than 'transfers'*'minimal_chunk_size'</p>
+<h4
+id="quatrix-maximal-summary-chunk-size">--quatrix-maximal-summary-chunk-size</h4>
+<p>The maximal summary for all chunks. It should not be less than
+'transfers'*'minimal_chunk_size'</p>
 <p>Properties:</p>
 <ul>
 <li>Config: maximal_summary_chunk_size</li>
@@ -31267,7 +45074,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="quatrix-skip-project-folders">--quatrix-skip-project-folders</h4>
+<h4
+id="quatrix-skip-project-folders">--quatrix-skip-project-folders</h4>
 <p>Skip project folders in operations</p>
 <p>Properties:</p>
 <ul>
@@ -31286,18 +45094,69 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="storage-usage">Storage usage</h2>
-<p>The storage usage in Quatrix is restricted to the account during the purchase. You can restrict any user with a smaller storage limit. The account limit is applied if the user has no custom storage limit. Once you've reached the limit, the upload of files will fail. This can be fixed by freeing up the space or increasing the quota.</p>
+<p>The storage usage in Quatrix is restricted to the account during the
+purchase. You can restrict any user with a smaller storage limit. The
+account limit is applied if the user has no custom storage limit. Once
+you've reached the limit, the upload of files will fail. This can be
+fixed by freeing up the space or increasing the quota.</p>
 <h2 id="server-side-operations">Server-side operations</h2>
-<p>Quatrix supports server-side operations (copy and move). In case of conflict, files are overwritten during server-side operation.</p>
+<p>Quatrix supports server-side operations (copy and move). In case of
+conflict, files are overwritten during server-side operation.</p>
 <h1 id="sia">Sia</h1>
-<p>Sia (<a href="https://sia.tech/">sia.tech</a>) is a decentralized cloud storage platform based on the <a href="https://wikipedia.org/wiki/Blockchain">blockchain</a> technology. With rclone you can use it like any other remote filesystem or mount Sia folders locally. The technology behind it involves a number of new concepts such as Siacoins and Wallet, Blockchain and Consensus, Renting and Hosting, and so on. If you are new to it, you'd better first familiarize yourself using their excellent <a href="https://support.sia.tech/">support documentation</a>.</p>
+<p>Sia (<a href="https://sia.tech/">sia.tech</a>) is a decentralized
+cloud storage platform based on the <a
+href="https://wikipedia.org/wiki/Blockchain">blockchain</a> technology.
+With rclone you can use it like any other remote filesystem or mount Sia
+folders locally. The technology behind it involves a number of new
+concepts such as Siacoins and Wallet, Blockchain and Consensus, Renting
+and Hosting, and so on. If you are new to it, you'd better first
+familiarize yourself using their excellent <a
+href="https://support.sia.tech/">support documentation</a>.</p>
 <h2 id="introduction-1">Introduction</h2>
-<p>Before you can use rclone with Sia, you will need to have a running copy of <code>Sia-UI</code> or <code>siad</code> (the Sia daemon) locally on your computer or on local network (e.g. a NAS). Please follow the <a href="https://sia.tech/get-started">Get started</a> guide and install one.</p>
-<p>rclone interacts with Sia network by talking to the Sia daemon via <a href="https://sia.tech/docs/">HTTP API</a> which is usually available on port <em>9980</em>. By default you will run the daemon locally on the same computer so it's safe to leave the API password blank (the API URL will be <code>http://127.0.0.1:9980</code> making external access impossible).</p>
-<p>However, if you want to access Sia daemon running on another node, for example due to memory constraints or because you want to share single daemon between several rclone and Sia-UI instances, you'll need to make a few more provisions: - Ensure you have <em>Sia daemon</em> installed directly or in a <a href="https://github.com/SiaFoundation/siad/pkgs/container/siad">docker container</a> because Sia-UI does not support this mode natively. - Run it on externally accessible port, for example provide <code>--api-addr :9980</code> and <code>--disable-api-security</code> arguments on the daemon command line. - Enforce API password for the <code>siad</code> daemon via environment variable <code>SIA_API_PASSWORD</code> or text file named <code>apipassword</code> in the daemon directory. - Set rclone backend option <code>api_password</code> taking it from above locations.</p>
-<p>Notes: 1. If your wallet is locked, rclone cannot unlock it automatically. You should either unlock it in advance by using Sia-UI or via command line <code>siac wallet unlock</code>. Alternatively you can make <code>siad</code> unlock your wallet automatically upon startup by running it with environment variable <code>SIA_WALLET_PASSWORD</code>. 2. If <code>siad</code> cannot find the <code>SIA_API_PASSWORD</code> variable or the <code>apipassword</code> file in the <code>SIA_DIR</code> directory, it will generate a random password and store in the text file named <code>apipassword</code> under <code>YOUR_HOME/.sia/</code> directory on Unix or <code>C:\Users\YOUR_HOME\AppData\Local\Sia\apipassword</code> on Windows. Remember this when you configure password in rclone. 3. The only way to use <code>siad</code> without API password is to run it <strong>on localhost</strong> with command line argument <code>--authorize-api=false</code>, but this is insecure and <strong>strongly discouraged</strong>.</p>
-<h2 id="configuration-38">Configuration</h2>
-<p>Here is an example of how to make a <code>sia</code> remote called <code>mySia</code>. First, run:</p>
+<p>Before you can use rclone with Sia, you will need to have a running
+copy of <code>Sia-UI</code> or <code>siad</code> (the Sia daemon)
+locally on your computer or on local network (e.g. a NAS). Please follow
+the <a href="https://sia.tech/get-started">Get started</a> guide and
+install one.</p>
+<p>rclone interacts with Sia network by talking to the Sia daemon via <a
+href="https://sia.tech/docs/">HTTP API</a> which is usually available on
+port <em>9980</em>. By default you will run the daemon locally on the
+same computer so it's safe to leave the API password blank (the API URL
+will be <code>http://127.0.0.1:9980</code> making external access
+impossible).</p>
+<p>However, if you want to access Sia daemon running on another node,
+for example due to memory constraints or because you want to share
+single daemon between several rclone and Sia-UI instances, you'll need
+to make a few more provisions: - Ensure you have <em>Sia daemon</em>
+installed directly or in a <a
+href="https://github.com/SiaFoundation/siad/pkgs/container/siad">docker
+container</a> because Sia-UI does not support this mode natively. - Run
+it on externally accessible port, for example provide
+<code>--api-addr :9980</code> and <code>--disable-api-security</code>
+arguments on the daemon command line. - Enforce API password for the
+<code>siad</code> daemon via environment variable
+<code>SIA_API_PASSWORD</code> or text file named
+<code>apipassword</code> in the daemon directory. - Set rclone backend
+option <code>api_password</code> taking it from above locations.</p>
+<p>Notes: 1. If your wallet is locked, rclone cannot unlock it
+automatically. You should either unlock it in advance by using Sia-UI or
+via command line <code>siac wallet unlock</code>. Alternatively you can
+make <code>siad</code> unlock your wallet automatically upon startup by
+running it with environment variable <code>SIA_WALLET_PASSWORD</code>.
+2. If <code>siad</code> cannot find the <code>SIA_API_PASSWORD</code>
+variable or the <code>apipassword</code> file in the
+<code>SIA_DIR</code> directory, it will generate a random password and
+store in the text file named <code>apipassword</code> under
+<code>YOUR_HOME/.sia/</code> directory on Unix or
+<code>C:\Users\YOUR_HOME\AppData\Local\Sia\apipassword</code> on
+Windows. Remember this when you configure password in rclone. 3. The
+only way to use <code>siad</code> without API password is to run it
+<strong>on localhost</strong> with command line argument
+<code>--authorize-api=false</code>, but this is insecure and
+<strong>strongly discouraged</strong>.</p>
+<h2 id="configuration-39">Configuration</h2>
+<p>Here is an example of how to make a <code>sia</code> remote called
+<code>mySia</code>. First, run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -31353,14 +45212,18 @@ y/e/d&gt; y</code></pre>
 </ul>
 <pre><code>rclone ls mySia:</code></pre>
 <ul>
-<li>Upload a local directory to the Sia directory called <em>backup</em></li>
+<li>Upload a local directory to the Sia directory called
+<em>backup</em></li>
 </ul>
 <pre><code>rclone copy /home/source mySia:backup</code></pre>
-<h3 id="standard-options-38">Standard options</h3>
-<p>Here are the Standard options specific to sia (Sia Decentralized Cloud).</p>
+<h3 id="standard-options-39">Standard options</h3>
+<p>Here are the Standard options specific to sia (Sia Decentralized
+Cloud).</p>
 <h4 id="sia-api-url">--sia-api-url</h4>
 <p>Sia daemon API URL, like http://sia.daemon.host:9980.</p>
-<p>Note that siad must run with --disable-api-security to open API port for other hosts (not recommended). Keep default if Sia daemon runs on localhost.</p>
+<p>Note that siad must run with --disable-api-security to open API port
+for other hosts (not recommended). Keep default if Sia daemon runs on
+localhost.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: api_url</li>
@@ -31370,8 +45233,11 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="sia-api-password">--sia-api-password</h4>
 <p>Sia Daemon API Password.</p>
-<p>Can be found in the apipassword file located in HOME/.sia/ or in the daemon directory.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>Can be found in the apipassword file located in HOME/.sia/ or in the
+daemon directory.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: api_password</li>
@@ -31379,11 +45245,13 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-39">Advanced options</h3>
-<p>Here are the Advanced options specific to sia (Sia Decentralized Cloud).</p>
+<h3 id="advanced-options-40">Advanced options</h3>
+<p>Here are the Advanced options specific to sia (Sia Decentralized
+Cloud).</p>
 <h4 id="sia-user-agent">--sia-user-agent</h4>
 <p>Siad User Agent</p>
-<p>Sia daemon requires the 'Sia-Agent' user agent by default for security</p>
+<p>Sia daemon requires the 'Sia-Agent' user agent by default for
+security</p>
 <p>Properties:</p>
 <ul>
 <li>Config: user_agent</li>
@@ -31393,7 +45261,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="sia-encoding">--sia-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -31415,21 +45284,39 @@ y/e/d&gt; y</code></pre>
 <li>Modification times not supported</li>
 <li>Checksums not supported</li>
 <li><code>rclone about</code> not supported</li>
-<li>rclone can work only with <em>Siad</em> or <em>Sia-UI</em> at the moment, the <strong>SkyNet daemon is not supported yet.</strong></li>
-<li>Sia does not allow control characters or symbols like question and pound signs in file names. rclone will transparently <a href="https://rclone.org/overview/#encoding">encode</a> them for you, but you'd better be aware</li>
+<li>rclone can work only with <em>Siad</em> or <em>Sia-UI</em> at the
+moment, the <strong>SkyNet daemon is not supported yet.</strong></li>
+<li>Sia does not allow control characters or symbols like question and
+pound signs in file names. rclone will transparently <a
+href="https://rclone.org/overview/#encoding">encode</a> them for you,
+but you'd better be aware</li>
 </ul>
 <h1 id="swift">Swift</h1>
-<p>Swift refers to <a href="https://docs.openstack.org/swift/latest/">OpenStack Object Storage</a>. Commercial implementations of that being:</p>
+<p>Swift refers to <a
+href="https://docs.openstack.org/swift/latest/">OpenStack Object
+Storage</a>. Commercial implementations of that being:</p>
 <ul>
-<li><a href="https://www.rackspace.com/cloud/files/">Rackspace Cloud Files</a></li>
-<li><a href="https://www.memset.com/cloud/storage/">Memset Memstore</a></li>
-<li><a href="https://www.ovh.co.uk/public-cloud/storage/object-storage/">OVH Object Storage</a></li>
-<li><a href="https://docs.oracle.com/en-us/iaas/integration/doc/configure-object-storage.html">Oracle Cloud Storage</a></li>
-<li><a href="https://www.blomp.com/cloud-storage/">Blomp Cloud Storage</a></li>
-<li><a href="https://console.bluemix.net/docs/infrastructure/objectstorage-swift/index.html">IBM Bluemix Cloud ObjectStorage Swift</a></li>
+<li><a href="https://www.rackspace.com/cloud/files/">Rackspace Cloud
+Files</a></li>
+<li><a href="https://www.memset.com/cloud/storage/">Memset
+Memstore</a></li>
+<li><a
+href="https://www.ovh.co.uk/public-cloud/storage/object-storage/">OVH
+Object Storage</a></li>
+<li><a
+href="https://docs.oracle.com/en-us/iaas/integration/doc/configure-object-storage.html">Oracle
+Cloud Storage</a></li>
+<li><a href="https://www.blomp.com/cloud-storage/">Blomp Cloud
+Storage</a></li>
+<li><a
+href="https://console.bluemix.net/docs/infrastructure/objectstorage-swift/index.html">IBM
+Bluemix Cloud ObjectStorage Swift</a></li>
 </ul>
-<p>Paths are specified as <code>remote:container</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:container/path/to/dir</code>.</p>
-<h2 id="configuration-39">Configuration</h2>
+<p>Paths are specified as <code>remote:container</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g.
+<code>remote:container/path/to/dir</code>.</p>
+<h2 id="configuration-40">Configuration</h2>
 <p>Here is an example of making a swift configuration. First run</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
@@ -31523,17 +45410,21 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>This remote is called <code>remote</code> and can now be used like this</p>
+<p>This remote is called <code>remote</code> and can now be used like
+this</p>
 <p>See all containers</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>Make a new container</p>
 <pre><code>rclone mkdir remote:container</code></pre>
 <p>List the contents of a container</p>
 <pre><code>rclone ls remote:container</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote container, deleting any excess files in the container.</p>
+<p>Sync <code>/home/local/directory</code> to the remote container,
+deleting any excess files in the container.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:container</code></pre>
-<h3 id="configuration-from-an-openstack-credentials-file">Configuration from an OpenStack credentials file</h3>
-<p>An OpenStack credentials file typically looks something something like this (without the comments)</p>
+<h3 id="configuration-from-an-openstack-credentials-file">Configuration
+from an OpenStack credentials file</h3>
+<p>An OpenStack credentials file typically looks something something
+like this (without the comments)</p>
 <pre><code>export OS_AUTH_URL=https://a.provider.net/v2.0
 export OS_TENANT_ID=ffffffffffffffffffffffffffffffff
 export OS_TENANT_NAME=&quot;1234567890123456&quot;
@@ -31543,36 +45434,75 @@ read -sr OS_PASSWORD_INPUT
 export OS_PASSWORD=$OS_PASSWORD_INPUT
 export OS_REGION_NAME=&quot;SBG1&quot;
 if [ -z &quot;$OS_REGION_NAME&quot; ]; then unset OS_REGION_NAME; fi</code></pre>
-<p>The config file needs to look something like this where <code>$OS_USERNAME</code> represents the value of the <code>OS_USERNAME</code> variable - <code>123abc567xy</code> in the example above.</p>
+<p>The config file needs to look something like this where
+<code>$OS_USERNAME</code> represents the value of the
+<code>OS_USERNAME</code> variable - <code>123abc567xy</code> in the
+example above.</p>
 <pre><code>[remote]
 type = swift
 user = $OS_USERNAME
 key = $OS_PASSWORD
 auth = $OS_AUTH_URL
 tenant = $OS_TENANT_NAME</code></pre>
-<p>Note that you may (or may not) need to set <code>region</code> too - try without first.</p>
-<h3 id="configuration-from-the-environment">Configuration from the environment</h3>
-<p>If you prefer you can configure rclone to use swift using a standard set of OpenStack environment variables.</p>
-<p>When you run through the config, make sure you choose <code>true</code> for <code>env_auth</code> and leave everything else blank.</p>
-<p>rclone will then set any empty config parameters from the environment using standard OpenStack environment variables. There is <a href="https://godoc.org/github.com/ncw/swift#Connection.ApplyEnvironment">a list of the variables</a> in the docs for the swift library.</p>
-<h3 id="using-an-alternate-authentication-method">Using an alternate authentication method</h3>
-<p>If your OpenStack installation uses a non-standard authentication method that might not be yet supported by rclone or the underlying swift library, you can authenticate externally (e.g. calling manually the <code>openstack</code> commands to get a token). Then, you just need to pass the two configuration variables <code>auth_token</code> and <code>storage_url</code>. If they are both provided, the other variables are ignored. rclone will not try to authenticate but instead assume it is already authenticated and use these two variables to access the OpenStack installation.</p>
-<h4 id="using-rclone-without-a-config-file">Using rclone without a config file</h4>
-<p>You can use rclone with swift without a config file, if desired, like this:</p>
+<p>Note that you may (or may not) need to set <code>region</code> too -
+try without first.</p>
+<h3 id="configuration-from-the-environment">Configuration from the
+environment</h3>
+<p>If you prefer you can configure rclone to use swift using a standard
+set of OpenStack environment variables.</p>
+<p>When you run through the config, make sure you choose
+<code>true</code> for <code>env_auth</code> and leave everything else
+blank.</p>
+<p>rclone will then set any empty config parameters from the environment
+using standard OpenStack environment variables. There is <a
+href="https://godoc.org/github.com/ncw/swift#Connection.ApplyEnvironment">a
+list of the variables</a> in the docs for the swift library.</p>
+<h3 id="using-an-alternate-authentication-method">Using an alternate
+authentication method</h3>
+<p>If your OpenStack installation uses a non-standard authentication
+method that might not be yet supported by rclone or the underlying swift
+library, you can authenticate externally (e.g. calling manually the
+<code>openstack</code> commands to get a token). Then, you just need to
+pass the two configuration variables <code>auth_token</code> and
+<code>storage_url</code>. If they are both provided, the other variables
+are ignored. rclone will not try to authenticate but instead assume it
+is already authenticated and use these two variables to access the
+OpenStack installation.</p>
+<h4 id="using-rclone-without-a-config-file">Using rclone without a
+config file</h4>
+<p>You can use rclone with swift without a config file, if desired, like
+this:</p>
 <pre><code>source openstack-credentials-file
 export RCLONE_CONFIG_MYREMOTE_TYPE=swift
 export RCLONE_CONFIG_MYREMOTE_ENV_AUTH=true
 rclone lsd myremote:</code></pre>
 <h3 id="fast-list-8">--fast-list</h3>
-<p>This remote supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details.</p>
-<h3 id="update-and---use-server-modtime">--update and --use-server-modtime</h3>
-<p>As noted below, the modified time is stored on metadata on the object. It is used by default for all operations that require checking the time a file was last updated. It allows rclone to treat the remote more like a true filesystem, but it is inefficient because it requires an extra API call to retrieve the metadata.</p>
-<p>For many operations, the time the object was last uploaded to the remote is sufficient to determine if it is "dirty". By using <code>--update</code> along with <code>--use-server-modtime</code>, you can avoid the extra API call and simply upload files whose local modtime is newer than the time it was last uploaded.</p>
-<h3 id="modification-times-and-hashes-19">Modification times and hashes</h3>
-<p>The modified time is stored as metadata on the object as <code>X-Object-Meta-Mtime</code> as floating point since the epoch accurate to 1 ns.</p>
-<p>This is a de facto standard (used in the official python-swiftclient amongst others) for storing the modification time for an object.</p>
+<p>This remote supports <code>--fast-list</code> which allows you to use
+fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details.</p>
+<h3 id="update-and---use-server-modtime">--update and
+--use-server-modtime</h3>
+<p>As noted below, the modified time is stored on metadata on the
+object. It is used by default for all operations that require checking
+the time a file was last updated. It allows rclone to treat the remote
+more like a true filesystem, but it is inefficient because it requires
+an extra API call to retrieve the metadata.</p>
+<p>For many operations, the time the object was last uploaded to the
+remote is sufficient to determine if it is "dirty". By using
+<code>--update</code> along with <code>--use-server-modtime</code>, you
+can avoid the extra API call and simply upload files whose local modtime
+is newer than the time it was last uploaded.</p>
+<h3 id="modification-times-and-hashes-19">Modification times and
+hashes</h3>
+<p>The modified time is stored as metadata on the object as
+<code>X-Object-Meta-Mtime</code> as floating point since the epoch
+accurate to 1 ns.</p>
+<p>This is a de facto standard (used in the official python-swiftclient
+amongst others) for storing the modification time for an object.</p>
 <p>The MD5 hash algorithm is supported.</p>
-<h3 id="restricted-filename-characters-24">Restricted filename characters</h3>
+<h3 id="restricted-filename-characters-23">Restricted filename
+characters</h3>
 <table>
 <thead>
 <tr class="header">
@@ -31594,11 +45524,15 @@ rclone lsd myremote:</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<h3 id="standard-options-39">Standard options</h3>
-<p>Here are the Standard options specific to swift (OpenStack Swift (Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)).</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<h3 id="standard-options-40">Standard options</h3>
+<p>Here are the Standard options specific to swift (OpenStack Swift
+(Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)).</p>
 <h4 id="swift-env-auth">--swift-env-auth</h4>
-<p>Get swift credentials from environment variables in standard OpenStack form.</p>
+<p>Get swift credentials from environment variables in standard
+OpenStack form.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: env_auth</li>
@@ -31677,7 +45611,8 @@ rclone lsd myremote:</code></pre>
 </ul></li>
 </ul>
 <h4 id="swift-user-id">--swift-user-id</h4>
-<p>User ID to log in - optional - most swift systems use user and leave this blank (v3 auth) (OS_USER_ID).</p>
+<p>User ID to log in - optional - most swift systems use user and leave
+this blank (v3 auth) (OS_USER_ID).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: user_id</li>
@@ -31695,7 +45630,8 @@ rclone lsd myremote:</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="swift-tenant">--swift-tenant</h4>
-<p>Tenant name - optional for v1 auth, this or tenant_id required otherwise (OS_TENANT_NAME or OS_PROJECT_NAME).</p>
+<p>Tenant name - optional for v1 auth, this or tenant_id required
+otherwise (OS_TENANT_NAME or OS_PROJECT_NAME).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: tenant</li>
@@ -31704,7 +45640,8 @@ rclone lsd myremote:</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="swift-tenant-id">--swift-tenant-id</h4>
-<p>Tenant ID - optional for v1 auth, this or tenant required otherwise (OS_TENANT_ID).</p>
+<p>Tenant ID - optional for v1 auth, this or tenant required otherwise
+(OS_TENANT_ID).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: tenant_id</li>
@@ -31740,7 +45677,8 @@ rclone lsd myremote:</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="swift-auth-token">--swift-auth-token</h4>
-<p>Auth Token from alternate authentication - optional (OS_AUTH_TOKEN).</p>
+<p>Auth Token from alternate authentication - optional
+(OS_AUTH_TOKEN).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: auth_token</li>
@@ -31748,7 +45686,8 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="swift-application-credential-id">--swift-application-credential-id</h4>
+<h4
+id="swift-application-credential-id">--swift-application-credential-id</h4>
 <p>Application Credential ID (OS_APPLICATION_CREDENTIAL_ID).</p>
 <p>Properties:</p>
 <ul>
@@ -31757,7 +45696,8 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="swift-application-credential-name">--swift-application-credential-name</h4>
+<h4
+id="swift-application-credential-name">--swift-application-credential-name</h4>
 <p>Application Credential Name (OS_APPLICATION_CREDENTIAL_NAME).</p>
 <p>Properties:</p>
 <ul>
@@ -31766,7 +45706,8 @@ rclone lsd myremote:</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="swift-application-credential-secret">--swift-application-credential-secret</h4>
+<h4
+id="swift-application-credential-secret">--swift-application-credential-secret</h4>
 <p>Application Credential Secret (OS_APPLICATION_CREDENTIAL_SECRET).</p>
 <p>Properties:</p>
 <ul>
@@ -31776,7 +45717,8 @@ rclone lsd myremote:</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="swift-auth-version">--swift-auth-version</h4>
-<p>AuthVersion - optional - set to (1,2,3) if your auth URL has no version (ST_AUTH_VERSION).</p>
+<p>AuthVersion - optional - set to (1,2,3) if your auth URL has no
+version (ST_AUTH_VERSION).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: auth_version</li>
@@ -31785,7 +45727,8 @@ rclone lsd myremote:</code></pre>
 <li>Default: 0</li>
 </ul>
 <h4 id="swift-endpoint-type">--swift-endpoint-type</h4>
-<p>Endpoint type to choose from the service catalogue (OS_ENDPOINT_TYPE).</p>
+<p>Endpoint type to choose from the service catalogue
+(OS_ENDPOINT_TYPE).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: endpoint_type</li>
@@ -31810,7 +45753,10 @@ rclone lsd myremote:</code></pre>
 </ul>
 <h4 id="swift-storage-policy">--swift-storage-policy</h4>
 <p>The storage policy to use when creating a new container.</p>
-<p>This applies the specified storage policy when creating a new container. The policy cannot be changed afterwards. The allowed configuration values and their meaning depend on your Swift storage provider.</p>
+<p>This applies the specified storage policy when creating a new
+container. The policy cannot be changed afterwards. The allowed
+configuration values and their meaning depend on your Swift storage
+provider.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: storage_policy</li>
@@ -31833,11 +45779,13 @@ rclone lsd myremote:</code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-40">Advanced options</h3>
-<p>Here are the Advanced options specific to swift (OpenStack Swift (Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)).</p>
+<h3 id="advanced-options-41">Advanced options</h3>
+<p>Here are the Advanced options specific to swift (OpenStack Swift
+(Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)).</p>
 <h4 id="swift-leave-parts-on-error">--swift-leave-parts-on-error</h4>
 <p>If true avoid calling abort upload on a failure.</p>
-<p>It should be set to true for resuming uploads across different sessions.</p>
+<p>It should be set to true for resuming uploads across different
+sessions.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: leave_parts_on_error</li>
@@ -31845,11 +45793,16 @@ rclone lsd myremote:</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="swift-fetch-until-empty-page">--swift-fetch-until-empty-page</h4>
+<h4
+id="swift-fetch-until-empty-page">--swift-fetch-until-empty-page</h4>
 <p>When paginating, always fetch unless we received an empty page.</p>
-<p>Consider using this option if rclone listings show fewer objects than expected, or if repeated syncs copy unchanged objects.</p>
-<p>It is safe to enable this, but rclone may make more API calls than necessary.</p>
-<p>This is one of a pair of workarounds to handle implementations of the Swift API that do not implement pagination as expected. See also "partial_page_fetch_threshold".</p>
+<p>Consider using this option if rclone listings show fewer objects than
+expected, or if repeated syncs copy unchanged objects.</p>
+<p>It is safe to enable this, but rclone may make more API calls than
+necessary.</p>
+<p>This is one of a pair of workarounds to handle implementations of the
+Swift API that do not implement pagination as expected. See also
+"partial_page_fetch_threshold".</p>
 <p>Properties:</p>
 <ul>
 <li>Config: fetch_until_empty_page</li>
@@ -31857,11 +45810,17 @@ rclone lsd myremote:</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="swift-partial-page-fetch-threshold">--swift-partial-page-fetch-threshold</h4>
-<p>When paginating, fetch if the current page is within this percentage of the limit.</p>
-<p>Consider using this option if rclone listings show fewer objects than expected, or if repeated syncs copy unchanged objects.</p>
-<p>It is safe to enable this, but rclone may make more API calls than necessary.</p>
-<p>This is one of a pair of workarounds to handle implementations of the Swift API that do not implement pagination as expected. See also "fetch_until_empty_page".</p>
+<h4
+id="swift-partial-page-fetch-threshold">--swift-partial-page-fetch-threshold</h4>
+<p>When paginating, fetch if the current page is within this percentage
+of the limit.</p>
+<p>Consider using this option if rclone listings show fewer objects than
+expected, or if repeated syncs copy unchanged objects.</p>
+<p>It is safe to enable this, but rclone may make more API calls than
+necessary.</p>
+<p>This is one of a pair of workarounds to handle implementations of the
+Swift API that do not implement pagination as expected. See also
+"fetch_until_empty_page".</p>
 <p>Properties:</p>
 <ul>
 <li>Config: partial_page_fetch_threshold</li>
@@ -31871,7 +45830,11 @@ rclone lsd myremote:</code></pre>
 </ul>
 <h4 id="swift-chunk-size">--swift-chunk-size</h4>
 <p>Above this size files will be chunked.</p>
-<p>Above this size files will be chunked into a a <code>_segments</code> container or a <code>.file-segments</code> directory. (See the <code>use_segments_container</code> option for more info). Default for this is 5 GiB which is its maximum value, which means only files above this size will be chunked.</p>
+<p>Above this size files will be chunked into a a <code>_segments</code>
+container or a <code>.file-segments</code> directory. (See the
+<code>use_segments_container</code> option for more info). Default for
+this is 5 GiB which is its maximum value, which means only files above
+this size will be chunked.</p>
 <p>Rclone uploads chunked files as dynamic large objects (DLO).</p>
 <p>Properties:</p>
 <ul>
@@ -31882,9 +45845,14 @@ rclone lsd myremote:</code></pre>
 </ul>
 <h4 id="swift-no-chunk">--swift-no-chunk</h4>
 <p>Don't chunk files during streaming upload.</p>
-<p>When doing streaming uploads (e.g. using <code>rcat</code> or <code>mount</code> with <code>--vfs-cache-mode off</code>) setting this flag will cause the swift backend to not upload chunked files.</p>
-<p>This will limit the maximum streamed upload size to 5 GiB. This is useful because non chunked files are easier to deal with and have an MD5SUM.</p>
-<p>Rclone will still chunk files bigger than <code>chunk_size</code> when doing normal copy operations.</p>
+<p>When doing streaming uploads (e.g. using <code>rcat</code> or
+<code>mount</code> with <code>--vfs-cache-mode off</code>) setting this
+flag will cause the swift backend to not upload chunked files.</p>
+<p>This will limit the maximum streamed upload size to 5 GiB. This is
+useful because non chunked files are easier to deal with and have an
+MD5SUM.</p>
+<p>Rclone will still chunk files bigger than <code>chunk_size</code>
+when doing normal copy operations.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_chunk</li>
@@ -31894,10 +45862,25 @@ rclone lsd myremote:</code></pre>
 </ul>
 <h4 id="swift-no-large-objects">--swift-no-large-objects</h4>
 <p>Disable support for static and dynamic large objects</p>
-<p>Swift cannot transparently store files bigger than 5 GiB. There are two schemes for chunking large files, static large objects (SLO) or dynamic large objects (DLO), and the API does not allow rclone to determine whether a file is a static or dynamic large object without doing a HEAD on the object. Since these need to be treated differently, this means rclone has to issue HEAD requests for objects for example when reading checksums.</p>
-<p>When <code>no_large_objects</code> is set, rclone will assume that there are no static or dynamic large objects stored. This means it can stop doing the extra HEAD calls which in turn increases performance greatly especially when doing a swift to swift transfer with <code>--checksum</code> set.</p>
-<p>Setting this option implies <code>no_chunk</code> and also that no files will be uploaded in chunks, so files bigger than 5 GiB will just fail on upload.</p>
-<p>If you set this option and there <strong>are</strong> static or dynamic large objects, then this will give incorrect hashes for them. Downloads will succeed, but other operations such as Remove and Copy will fail.</p>
+<p>Swift cannot transparently store files bigger than 5 GiB. There are
+two schemes for chunking large files, static large objects (SLO) or
+dynamic large objects (DLO), and the API does not allow rclone to
+determine whether a file is a static or dynamic large object without
+doing a HEAD on the object. Since these need to be treated differently,
+this means rclone has to issue HEAD requests for objects for example
+when reading checksums.</p>
+<p>When <code>no_large_objects</code> is set, rclone will assume that
+there are no static or dynamic large objects stored. This means it can
+stop doing the extra HEAD calls which in turn increases performance
+greatly especially when doing a swift to swift transfer with
+<code>--checksum</code> set.</p>
+<p>Setting this option implies <code>no_chunk</code> and also that no
+files will be uploaded in chunks, so files bigger than 5 GiB will just
+fail on upload.</p>
+<p>If you set this option and there <strong>are</strong> static or
+dynamic large objects, then this will give incorrect hashes for them.
+Downloads will succeed, but other operations such as Remove and Copy
+will fail.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_large_objects</li>
@@ -31905,12 +45888,29 @@ rclone lsd myremote:</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="swift-use-segments-container">--swift-use-segments-container</h4>
+<h4
+id="swift-use-segments-container">--swift-use-segments-container</h4>
 <p>Choose destination for large object segments</p>
-<p>Swift cannot transparently store files bigger than 5 GiB and rclone will chunk files larger than <code>chunk_size</code> (default 5 GiB) in order to upload them.</p>
-<p>If this value is <code>true</code> the chunks will be stored in an additional container named the same as the destination container but with <code>_segments</code> appended. This means that there won't be any duplicated data in the original container but having another container may not be acceptable.</p>
-<p>If this value is <code>false</code> the chunks will be stored in a <code>.file-segments</code> directory in the root of the container. This directory will be omitted when listing the container. Some providers (eg Blomp) require this mode as creating additional containers isn't allowed. If it is desired to see the <code>.file-segments</code> directory in the root then this flag must be set to <code>true</code>.</p>
-<p>If this value is <code>unset</code> (the default), then rclone will choose the value to use. It will be <code>false</code> unless rclone detects any <code>auth_url</code>s that it knows need it to be <code>true</code>. In this case you'll see a message in the DEBUG log.</p>
+<p>Swift cannot transparently store files bigger than 5 GiB and rclone
+will chunk files larger than <code>chunk_size</code> (default 5 GiB) in
+order to upload them.</p>
+<p>If this value is <code>true</code> the chunks will be stored in an
+additional container named the same as the destination container but
+with <code>_segments</code> appended. This means that there won't be any
+duplicated data in the original container but having another container
+may not be acceptable.</p>
+<p>If this value is <code>false</code> the chunks will be stored in a
+<code>.file-segments</code> directory in the root of the container. This
+directory will be omitted when listing the container. Some providers (eg
+Blomp) require this mode as creating additional containers isn't
+allowed. If it is desired to see the <code>.file-segments</code>
+directory in the root then this flag must be set to
+<code>true</code>.</p>
+<p>If this value is <code>unset</code> (the default), then rclone will
+choose the value to use. It will be <code>false</code> unless rclone
+detects any <code>auth_url</code>s that it knows need it to be
+<code>true</code>. In this case you'll see a message in the DEBUG
+log.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_segments_container</li>
@@ -31920,7 +45920,8 @@ rclone lsd myremote:</code></pre>
 </ul>
 <h4 id="swift-encoding">--swift-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -31938,28 +45939,52 @@ rclone lsd myremote:</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-30">Limitations</h2>
-<p>The Swift API doesn't return a correct MD5SUM for segmented files (Dynamic or Static Large Objects) so rclone won't check or use the MD5SUM for these.</p>
+<p>The Swift API doesn't return a correct MD5SUM for segmented files
+(Dynamic or Static Large Objects) so rclone won't check or use the
+MD5SUM for these.</p>
 <h2 id="troubleshooting-3">Troubleshooting</h2>
-<h3 id="rclone-gives-failed-to-create-file-system-for-remote-bad-request">Rclone gives Failed to create file system for "remote:": Bad Request</h3>
-<p>Due to an oddity of the underlying swift library, it gives a "Bad Request" error rather than a more sensible error when the authentication fails for Swift.</p>
-<p>So this most likely means your username / password is wrong. You can investigate further with the <code>--dump-bodies</code> flag.</p>
-<p>This may also be caused by specifying the region when you shouldn't have (e.g. OVH).</p>
-<h3 id="rclone-gives-failed-to-create-file-system-response-didnt-have-storage-url-and-auth-token">Rclone gives Failed to create file system: Response didn't have storage url and auth token</h3>
-<p>This is most likely caused by forgetting to specify your tenant when setting up a swift remote.</p>
+<h3
+id="rclone-gives-failed-to-create-file-system-for-remote-bad-request">Rclone
+gives Failed to create file system for "remote:": Bad Request</h3>
+<p>Due to an oddity of the underlying swift library, it gives a "Bad
+Request" error rather than a more sensible error when the authentication
+fails for Swift.</p>
+<p>So this most likely means your username / password is wrong. You can
+investigate further with the <code>--dump-bodies</code> flag.</p>
+<p>This may also be caused by specifying the region when you shouldn't
+have (e.g. OVH).</p>
+<h3
+id="rclone-gives-failed-to-create-file-system-response-didnt-have-storage-url-and-auth-token">Rclone
+gives Failed to create file system: Response didn't have storage url and
+auth token</h3>
+<p>This is most likely caused by forgetting to specify your tenant when
+setting up a swift remote.</p>
 <h2 id="ovh-cloud-archive">OVH Cloud Archive</h2>
-<p>To use rclone with OVH cloud archive, first use <code>rclone config</code> to set up a <code>swift</code> backend with OVH, choosing <code>pca</code> as the <code>storage_policy</code>.</p>
+<p>To use rclone with OVH cloud archive, first use
+<code>rclone config</code> to set up a <code>swift</code> backend with
+OVH, choosing <code>pca</code> as the <code>storage_policy</code>.</p>
 <h3 id="uploading-objects">Uploading Objects</h3>
-<p>Uploading objects to OVH cloud archive is no different to object storage, you just simply run the command you like (move, copy or sync) to upload the objects. Once uploaded the objects will show in a "Frozen" state within the OVH control panel.</p>
+<p>Uploading objects to OVH cloud archive is no different to object
+storage, you just simply run the command you like (move, copy or sync)
+to upload the objects. Once uploaded the objects will show in a "Frozen"
+state within the OVH control panel.</p>
 <h3 id="retrieving-objects">Retrieving Objects</h3>
-<p>To retrieve objects use <code>rclone copy</code> as normal. If the objects are in a frozen state then rclone will ask for them all to be unfrozen and it will wait at the end of the output with a message like the following:</p>
+<p>To retrieve objects use <code>rclone copy</code> as normal. If the
+objects are in a frozen state then rclone will ask for them all to be
+unfrozen and it will wait at the end of the output with a message like
+the following:</p>
 <p><code>2019/03/23 13:06:33 NOTICE: Received retry after error - sleeping until 2019-03-23T13:16:33.481657164+01:00 (9m59.99985121s)</code></p>
 <p>Rclone will wait for the time specified then retry the copy.</p>
 <h1 id="pcloud">pCloud</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-40">Configuration</h2>
-<p>The initial setup for pCloud involves getting a token from pCloud which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-41">Configuration</h2>
+<p>The initial setup for pCloud involves getting a token from pCloud
+which you need to do in your browser. <code>rclone config</code> walks
+you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -32002,8 +46027,14 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from pCloud. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from pCloud. This only runs from the moment it
+opens your browser to the moment you get back the verification code.
+This is on <code>http://127.0.0.1:53682/</code> and this it may require
+you to unblock it temporarily if you are running a host firewall.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your pCloud</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -32011,11 +46042,21 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to a pCloud directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-20">Modification times and hashes</h3>
-<p>pCloud allows modification times to be set on objects accurate to 1 second. These will be used to detect whether objects need syncing or not. In order to set a Modification time pCloud requires the object be re-uploaded.</p>
-<p>pCloud supports MD5 and SHA1 hashes in the US region, and SHA1 and SHA256 hashes in the EU region, so you can use the <code>--checksum</code> flag.</p>
-<h3 id="restricted-filename-characters-25">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<h3 id="modification-times-and-hashes-20">Modification times and
+hashes</h3>
+<p>pCloud allows modification times to be set on objects accurate to 1
+second. These will be used to detect whether objects need syncing or
+not. In order to set a Modification time pCloud requires the object be
+re-uploaded.</p>
+<p>pCloud supports MD5 and SHA1 hashes in the US region, and SHA1 and
+SHA256 hashes in the EU region, so you can use the
+<code>--checksum</code> flag.</p>
+<h3 id="restricted-filename-characters-24">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -32032,18 +46073,36 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="deleting-files-6">Deleting files</h3>
-<p>Deleted files will be moved to the trash. Your subscription level will determine how long items stay in the trash. <code>rclone cleanup</code> can be used to empty the trash.</p>
+<p>Deleted files will be moved to the trash. Your subscription level
+will determine how long items stay in the trash.
+<code>rclone cleanup</code> can be used to empty the trash.</p>
 <h3 id="emptying-the-trash">Emptying the trash</h3>
-<p>Due to an API limitation, the <code>rclone cleanup</code> command will only work if you set your username and password in the advanced options for this backend. Since we generally want to avoid storing user passwords in the rclone config file, we advise you to only set this up if you need the <code>rclone cleanup</code> command to work.</p>
+<p>Due to an API limitation, the <code>rclone cleanup</code> command
+will only work if you set your username and password in the advanced
+options for this backend. Since we generally want to avoid storing user
+passwords in the rclone config file, we advise you to only set this up
+if you need the <code>rclone cleanup</code> command to work.</p>
 <h3 id="root-folder-id-4">Root folder ID</h3>
-<p>You can set the <code>root_folder_id</code> for rclone. This is the directory (identified by its <code>Folder ID</code>) that rclone considers to be the root of your pCloud drive.</p>
-<p>Normally you will leave this blank and rclone will determine the correct root to use itself.</p>
-<p>However you can set this to restrict rclone to a specific folder hierarchy.</p>
-<p>In order to do this you will have to find the <code>Folder ID</code> of the directory you wish rclone to display. This will be the <code>folder</code> field of the URL when you open the relevant folder in the pCloud web interface.</p>
-<p>So if the folder you want rclone to use has a URL which looks like <code>https://my.pcloud.com/#page=filemanager&amp;folder=5xxxxxxxx8&amp;tpl=foldergrid</code> in the browser, then you use <code>5xxxxxxxx8</code> as the <code>root_folder_id</code> in the config.</p>
-<h3 id="standard-options-40">Standard options</h3>
+<p>You can set the <code>root_folder_id</code> for rclone. This is the
+directory (identified by its <code>Folder ID</code>) that rclone
+considers to be the root of your pCloud drive.</p>
+<p>Normally you will leave this blank and rclone will determine the
+correct root to use itself.</p>
+<p>However you can set this to restrict rclone to a specific folder
+hierarchy.</p>
+<p>In order to do this you will have to find the <code>Folder ID</code>
+of the directory you wish rclone to display. This will be the
+<code>folder</code> field of the URL when you open the relevant folder
+in the pCloud web interface.</p>
+<p>So if the folder you want rclone to use has a URL which looks like
+<code>https://my.pcloud.com/#page=filemanager&amp;folder=5xxxxxxxx8&amp;tpl=foldergrid</code>
+in the browser, then you use <code>5xxxxxxxx8</code> as the
+<code>root_folder_id</code> in the config.</p>
+<h3 id="standard-options-41">Standard options</h3>
 <p>Here are the Standard options specific to pcloud (Pcloud).</p>
 <h4 id="pcloud-client-id">--pcloud-client-id</h4>
 <p>OAuth Client Id.</p>
@@ -32065,7 +46124,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-41">Advanced options</h3>
+<h3 id="advanced-options-42">Advanced options</h3>
 <p>Here are the Advanced options specific to pcloud (Pcloud).</p>
 <h4 id="pcloud-token">--pcloud-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
@@ -32098,7 +46157,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pcloud-encoding">--pcloud-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -32107,7 +46167,8 @@ y/e/d&gt; y</code></pre>
 <li>Default: Slash,BackSlash,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="pcloud-root-folder-id">--pcloud-root-folder-id</h4>
-<p>Fill in for rclone to use a non root folder as its starting point.</p>
+<p>Fill in for rclone to use a non root folder as its starting
+point.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_id</li>
@@ -32117,7 +46178,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pcloud-hostname">--pcloud-hostname</h4>
 <p>Hostname to connect to.</p>
-<p>This is normally set when rclone initially does the oauth connection, however you will need to set it by hand if you are using remote config with rclone authorize.</p>
+<p>This is normally set when rclone initially does the oauth connection,
+however you will need to set it by hand if you are using remote config
+with rclone authorize.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: hostname</li>
@@ -32138,7 +46201,10 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pcloud-username">--pcloud-username</h4>
 <p>Your pcloud username.</p>
-<p>This is only required when you want to use the cleanup command. Due to a bug in the pcloud API the required API does not support OAuth authentication so we have to rely on user password authentication for it.</p>
+<p>This is only required when you want to use the cleanup command. Due
+to a bug in the pcloud API the required API does not support OAuth
+authentication so we have to rely on user password authentication for
+it.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: username</li>
@@ -32148,7 +46214,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pcloud-password">--pcloud-password</h4>
 <p>Your pcloud password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -32166,9 +46234,11 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h1 id="pikpak">PikPak</h1>
-<p>PikPak is <a href="https://mypikpak.com/">a private cloud drive</a>.</p>
-<p>Paths are specified as <code>remote:path</code>, and may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-41">Configuration</h2>
+<p>PikPak is <a href="https://mypikpak.com/">a private cloud
+drive</a>.</p>
+<p>Paths are specified as <code>remote:path</code>, and may be as deep
+as required, e.g. <code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-42">Configuration</h2>
 <p>Here is an example of making a remote for PikPak.</p>
 <p>First run:</p>
 <pre><code> rclone config</code></pre>
@@ -32221,10 +46291,13 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<h3 id="modification-times-and-hashes-21">Modification times and hashes</h3>
-<p>PikPak keeps modification times on objects, and updates them when uploading objects, but it does not support changing only the modification time</p>
+<h3 id="modification-times-and-hashes-21">Modification times and
+hashes</h3>
+<p>PikPak keeps modification times on objects, and updates them when
+uploading objects, but it does not support changing only the
+modification time</p>
 <p>The MD5 hash algorithm is supported.</p>
-<h3 id="standard-options-41">Standard options</h3>
+<h3 id="standard-options-42">Standard options</h3>
 <p>Here are the Standard options specific to pikpak (PikPak).</p>
 <h4 id="pikpak-user">--pikpak-user</h4>
 <p>Pikpak username.</p>
@@ -32237,7 +46310,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pikpak-pass">--pikpak-pass</h4>
 <p>Pikpak password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass</li>
@@ -32245,7 +46320,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: true</li>
 </ul>
-<h3 id="advanced-options-42">Advanced options</h3>
+<h3 id="advanced-options-43">Advanced options</h3>
 <p>Here are the Advanced options specific to pikpak (PikPak).</p>
 <h4 id="pikpak-device-id">--pikpak-device-id</h4>
 <p>Device ID used for authorization.</p>
@@ -32258,17 +46333,21 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pikpak-user-agent">--pikpak-user-agent</h4>
 <p>HTTP user agent for pikpak.</p>
-<p>Defaults to "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0" or "--pikpak-user-agent" provided on command line.</p>
+<p>Defaults to "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0)
+Gecko/20100101 Firefox/129.0" or "--pikpak-user-agent" provided on
+command line.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: user_agent</li>
 <li>Env Var: RCLONE_PIKPAK_USER_AGENT</li>
 <li>Type: string</li>
-<li>Default: "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0"</li>
+<li>Default: "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0)
+Gecko/20100101 Firefox/129.0"</li>
 </ul>
 <h4 id="pikpak-root-folder-id">--pikpak-root-folder-id</h4>
 <p>ID of the root folder. Leave blank normally.</p>
-<p>Fill in for rclone to use a non root folder as its starting point.</p>
+<p>Fill in for rclone to use a non root folder as its starting
+point.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_id</li>
@@ -32278,7 +46357,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pikpak-use-trash">--pikpak-use-trash</h4>
 <p>Send files to the trash instead of deleting permanently.</p>
-<p>Defaults to true, namely sending files to the trash. Use <code>--pikpak-use-trash=false</code> to delete files permanently instead.</p>
+<p>Defaults to true, namely sending files to the trash. Use
+<code>--pikpak-use-trash=false</code> to delete files permanently
+instead.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_trash</li>
@@ -32288,7 +46369,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pikpak-trashed-only">--pikpak-trashed-only</h4>
 <p>Only show files that are in the trash.</p>
-<p>This will show trashed files in their original directory structure.</p>
+<p>This will show trashed files in their original directory
+structure.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: trashed_only</li>
@@ -32297,7 +46379,8 @@ y/e/d&gt; y</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="pikpak-hash-memory-limit">--pikpak-hash-memory-limit</h4>
-<p>Files bigger than this will be cached on disk to calculate hash if required.</p>
+<p>Files bigger than this will be cached on disk to calculate hash if
+required.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: hash_memory_limit</li>
@@ -32308,10 +46391,16 @@ y/e/d&gt; y</code></pre>
 <h4 id="pikpak-chunk-size">--pikpak-chunk-size</h4>
 <p>Chunk size for multipart uploads.</p>
 <p>Large files will be uploaded in chunks of this size.</p>
-<p>Note that this is stored in memory and there may be up to "--transfers" * "--pikpak-upload-concurrency" chunks stored at once in memory.</p>
-<p>If you are transferring large files over high-speed links and you have enough memory, then increasing this will speed up the transfers.</p>
-<p>Rclone will automatically increase the chunk size when uploading a large file of known size to stay below the 10,000 chunks limit.</p>
-<p>Increasing the chunk size decreases the accuracy of the progress statistics displayed with "-P" flag.</p>
+<p>Note that this is stored in memory and there may be up to
+"--transfers" * "--pikpak-upload-concurrency" chunks stored at once in
+memory.</p>
+<p>If you are transferring large files over high-speed links and you
+have enough memory, then increasing this will speed up the
+transfers.</p>
+<p>Rclone will automatically increase the chunk size when uploading a
+large file of known size to stay below the 10,000 chunks limit.</p>
+<p>Increasing the chunk size decreases the accuracy of the progress
+statistics displayed with "-P" flag.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -32321,9 +46410,14 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pikpak-upload-concurrency">--pikpak-upload-concurrency</h4>
 <p>Concurrency for multipart uploads.</p>
-<p>This is the number of chunks of the same file that are uploaded concurrently for multipart uploads.</p>
-<p>Note that chunks are stored in memory and there may be up to "--transfers" * "--pikpak-upload-concurrency" chunks stored at once in memory.</p>
-<p>If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.</p>
+<p>This is the number of chunks of the same file that are uploaded
+concurrently for multipart uploads.</p>
+<p>Note that chunks are stored in memory and there may be up to
+"--transfers" * "--pikpak-upload-concurrency" chunks stored at once in
+memory.</p>
+<p>If you are uploading small numbers of large files over high-speed
+links and these uploads do not fully utilize your bandwidth, then
+increasing this may help to speed up the transfers.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upload_concurrency</li>
@@ -32333,13 +46427,15 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="pikpak-encoding">--pikpak-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_PIKPAK_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,LeftSpace,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="pikpak-description">--pikpak-description</h4>
 <p>Description of the remote.</p>
@@ -32355,15 +46451,19 @@ y/e/d&gt; y</code></pre>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="addurl">addurl</h3>
 <p>Add offline download task for url</p>
 <pre><code>rclone backend addurl remote: [options] [&lt;arguments&gt;+]</code></pre>
 <p>This command adds offline download task for url.</p>
 <p>Usage:</p>
 <pre><code>rclone backend addurl pikpak:dirpath url</code></pre>
-<p>Downloads will be stored in 'dirpath'. If 'dirpath' is invalid, download will fallback to default 'My Pack' folder.</p>
+<p>Downloads will be stored in 'dirpath'. If 'dirpath' is invalid,
+download will fallback to default 'My Pack' folder.</p>
 <h3 id="decompress">decompress</h3>
 <p>Request decompress of a file/files in a folder</p>
 <pre><code>rclone backend decompress remote: [options] [&lt;arguments&gt;+]</code></pre>
@@ -32371,7 +46471,10 @@ y/e/d&gt; y</code></pre>
 <p>Usage:</p>
 <pre><code>rclone backend decompress pikpak:dirpath {filename} -o password=password
 rclone backend decompress pikpak:dirpath {filename} -o delete-src-file</code></pre>
-<p>An optional argument 'filename' can be specified for a file located in 'pikpak:dirpath'. You may want to pass '-o password=password' for a password-protected files. Also, pass '-o delete-src-file' to delete source files after decompression finished.</p>
+<p>An optional argument 'filename' can be specified for a file located
+in 'pikpak:dirpath'. You may want to pass '-o password=password' for a
+password-protected files. Also, pass '-o delete-src-file' to delete
+source files after decompression finished.</p>
 <p>Result:</p>
 <pre><code>{
     &quot;Decompressed&quot;: 17,
@@ -32380,15 +46483,32 @@ rclone backend decompress pikpak:dirpath {filename} -o delete-src-file</code></p
 }</code></pre>
 <h2 id="limitations-31">Limitations</h2>
 <h3 id="hashes-may-be-empty">Hashes may be empty</h3>
-<p>PikPak supports MD5 hash, but sometimes given empty especially for user-uploaded files.</p>
-<h3 id="deleted-files-still-visible-with-trashed-only">Deleted files still visible with trashed-only</h3>
-<p>Deleted files will still be visible with <code>--pikpak-trashed-only</code> even after the trash emptied. This goes away after few days.</p>
+<p>PikPak supports MD5 hash, but sometimes given empty especially for
+user-uploaded files.</p>
+<h3 id="deleted-files-still-visible-with-trashed-only">Deleted files
+still visible with trashed-only</h3>
+<p>Deleted files will still be visible with
+<code>--pikpak-trashed-only</code> even after the trash emptied. This
+goes away after few days.</p>
 <h1 id="pixeldrain">Pixeldrain</h1>
-<p>This is the backend for Pixeldrain's premium filesystem feature. This is not the same as pixeldrain's free file sharing product. The filesystem requires either a Pro subscription or the Prepaid plan. <a href="https://pixeldrain.com/#pro">More information on subscriptions</a>.</p>
-<p>An overview of the filesystem's features and limitations is available in the <a href="https://pixeldrain.com/filesystem">filesystem guide</a> on pixeldrain.</p>
+<p>This is the backend for Pixeldrain's premium filesystem feature. This
+is not the same as pixeldrain's free file sharing product. The
+filesystem requires either a Pro subscription or the Prepaid plan. <a
+href="https://pixeldrain.com/#pro">More information on
+subscriptions</a>.</p>
+<p>An overview of the filesystem's features and limitations is available
+in the <a href="https://pixeldrain.com/filesystem">filesystem guide</a>
+on pixeldrain.</p>
 <h3 id="usage-with-account">Usage with account</h3>
-<p>To use the personal filesystem you will need a <a href="https://pixeldrain.com/register">pixeldrain account</a> and either the Prepaid plan or one of the Patreon-based subscriptions. After registering and subscribing, your personal filesystem will be available at this link: https://pixeldrain.com/d/me.</p>
-<p>Go to the <a href="https://pixeldrain.com/user/api_keys">API keys page</a> on your account and generate a new API key for rclone. Then run <code>rclone config</code> and use the API key to create a new backend.</p>
+<p>To use the personal filesystem you will need a <a
+href="https://pixeldrain.com/register">pixeldrain account</a> and either
+the Prepaid plan or one of the Patreon-based subscriptions. After
+registering and subscribing, your personal filesystem will be available
+at this link: https://pixeldrain.com/d/me.</p>
+<p>Go to the <a href="https://pixeldrain.com/user/api_keys">API keys
+page</a> on your account and generate a new API key for rclone. Then run
+<code>rclone config</code> and use the API key to create a new
+backend.</p>
 <p>Example:</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
@@ -32452,14 +46572,23 @@ s) Set configuration password
 q) Quit config
 e/n/d/r/c/s/q&gt; q</code></pre>
 <h3 id="usage-without-account">Usage without account</h3>
-<p>It is possible to gain read-only access to publicly shared directories through rclone. For this you only need a directory ID. The directory ID can be found in the URL of a shared directory, the URL will look like this <code>https://pixeldrain.com/d/abcd1234</code> where <code>abcd1234</code> is the directory ID. Directory IDs in your own filesystem can also be listed with the <code>lsf</code> command:</p>
+<p>It is possible to gain read-only access to publicly shared
+directories through rclone. For this you only need a directory ID. The
+directory ID can be found in the URL of a shared directory, the URL will
+look like this <code>https://pixeldrain.com/d/abcd1234</code> where
+<code>abcd1234</code> is the directory ID. Directory IDs in your own
+filesystem can also be listed with the <code>lsf</code> command:</p>
 <p><code>rclone lsf Pixeldrain: --dirs-only -Fpi</code></p>
-<p>This will print directories in your <code>Pixeldrain</code> home directory and their public IDs.</p>
-<p>Enter this directory ID in the rclone config and you will be able to access the directory.</p>
-<h3 id="standard-options-42">Standard options</h3>
-<p>Here are the Standard options specific to pixeldrain (Pixeldrain Filesystem).</p>
+<p>This will print directories in your <code>Pixeldrain</code> home
+directory and their public IDs.</p>
+<p>Enter this directory ID in the rclone config and you will be able to
+access the directory.</p>
+<h3 id="standard-options-43">Standard options</h3>
+<p>Here are the Standard options specific to pixeldrain (Pixeldrain
+Filesystem).</p>
 <h4 id="pixeldrain-api-key">--pixeldrain-api-key</h4>
-<p>API key for your pixeldrain account. Found on https://pixeldrain.com/user/api_keys.</p>
+<p>API key for your pixeldrain account. Found on
+https://pixeldrain.com/user/api_keys.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: api_key</li>
@@ -32469,7 +46598,8 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </ul>
 <h4 id="pixeldrain-root-folder-id">--pixeldrain-root-folder-id</h4>
 <p>Root of the filesystem to use.</p>
-<p>Set to 'me' to use your personal filesystem. Set to a shared directory ID to use a shared directory.</p>
+<p>Set to 'me' to use your personal filesystem. Set to a shared
+directory ID to use a shared directory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_id</li>
@@ -32477,10 +46607,13 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <li>Type: string</li>
 <li>Default: "me"</li>
 </ul>
-<h3 id="advanced-options-43">Advanced options</h3>
-<p>Here are the Advanced options specific to pixeldrain (Pixeldrain Filesystem).</p>
+<h3 id="advanced-options-44">Advanced options</h3>
+<p>Here are the Advanced options specific to pixeldrain (Pixeldrain
+Filesystem).</p>
 <h4 id="pixeldrain-api-url">--pixeldrain-api-url</h4>
-<p>The API endpoint to connect to. In the vast majority of cases it's fine to leave this at default. It is only intended to be changed for testing purposes.</p>
+<p>The API endpoint to connect to. In the vast majority of cases it's
+fine to leave this at default. It is only intended to be changed for
+testing purposes.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: api_url</li>
@@ -32499,7 +46632,8 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </ul>
 <h3 id="metadata-14">Metadata</h3>
 <p>Pixeldrain supports file modes and creation times.</p>
-<p>Here are the possible system metadata items for the pixeldrain backend.</p>
+<p>Here are the possible system metadata items for the pixeldrain
+backend.</p>
 <table>
 <colgroup>
 <col style="width: 15%" />
@@ -32541,13 +46675,19 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </tr>
 </tbody>
 </table>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h1 id="premiumize.me">premiumize.me</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-42">Configuration</h2>
-<p>The initial setup for <a href="https://premiumize.me/">premiumize.me</a> involves getting a token from premiumize.me which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-43">Configuration</h2>
+<p>The initial setup for <a
+href="https://premiumize.me/">premiumize.me</a> involves getting a token
+from premiumize.me which you need to do in your browser.
+<code>rclone config</code> walks you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -32587,19 +46727,33 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; </code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from premiumize.me. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from premiumize.me. This only runs from the moment
+it opens your browser to the moment you get back the verification code.
+This is on <code>http://127.0.0.1:53682/</code> and this it may require
+you to unblock it temporarily if you are running a host firewall.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your premiumize.me</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>List all the files in your premiumize.me</p>
 <pre><code>rclone ls remote:</code></pre>
-<p>To copy a local directory to an premiumize.me directory called backup</p>
+<p>To copy a local directory to an premiumize.me directory called
+backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-22">Modification times and hashes</h3>
-<p>premiumize.me does not support modification times or hashes, therefore syncing will default to <code>--size-only</code> checking. Note that using <code>--update</code> will work.</p>
-<h3 id="restricted-filename-characters-26">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<h3 id="modification-times-and-hashes-22">Modification times and
+hashes</h3>
+<p>premiumize.me does not support modification times or hashes,
+therefore syncing will default to <code>--size-only</code> checking.
+Note that using <code>--update</code> will work.</p>
+<h3 id="restricted-filename-characters-25">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -32621,9 +46775,12 @@ y/e/d&gt; </code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<h3 id="standard-options-43">Standard options</h3>
-<p>Here are the Standard options specific to premiumizeme (premiumize.me).</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<h3 id="standard-options-44">Standard options</h3>
+<p>Here are the Standard options specific to premiumizeme
+(premiumize.me).</p>
 <h4 id="premiumizeme-client-id">--premiumizeme-client-id</h4>
 <p>OAuth Client Id.</p>
 <p>Leave blank normally.</p>
@@ -32654,8 +46811,9 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-44">Advanced options</h3>
-<p>Here are the Advanced options specific to premiumizeme (premiumize.me).</p>
+<h3 id="advanced-options-45">Advanced options</h3>
+<p>Here are the Advanced options specific to premiumizeme
+(premiumize.me).</p>
 <h4 id="premiumizeme-token">--premiumizeme-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
 <p>Properties:</p>
@@ -32687,7 +46845,8 @@ y/e/d&gt; </code></pre>
 </ul>
 <h4 id="premiumizeme-encoding">--premiumizeme-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -32705,18 +46864,34 @@ y/e/d&gt; </code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-32">Limitations</h2>
-<p>Note that premiumize.me is case insensitive so you can't have a file called "Hello.doc" and one called "hello.doc".</p>
-<p>premiumize.me file names can't have the <code>\</code> or <code>"</code> characters in. rclone maps these to and from an identical looking unicode equivalents <code>＼</code> and <code>＂</code></p>
-<p>premiumize.me only supports filenames up to 255 characters in length.</p>
+<p>Note that premiumize.me is case insensitive so you can't have a file
+called "Hello.doc" and one called "hello.doc".</p>
+<p>premiumize.me file names can't have the <code>\</code> or
+<code>"</code> characters in. rclone maps these to and from an identical
+looking unicode equivalents <code>＼</code> and <code>＂</code></p>
+<p>premiumize.me only supports filenames up to 255 characters in
+length.</p>
 <h1 id="proton-drive">Proton Drive</h1>
-<p><a href="https://proton.me/drive">Proton Drive</a> is an end-to-end encrypted Swiss vault for your files that protects your data.</p>
-<p>This is an rclone backend for Proton Drive which supports the file transfer features of Proton Drive using the same client-side encryption.</p>
-<p>Due to the fact that Proton Drive doesn't publish its API documentation, this backend is implemented with best efforts by reading the open-sourced client source code and observing the Proton Drive traffic in the browser.</p>
-<p><strong>NB</strong> This backend is currently in Beta. It is believed to be correct and all the integration tests pass. However the Proton Drive protocol has evolved over time there may be accounts it is not compatible with. Please <a href="https://forum.rclone.org/">post on the rclone forum</a> if you find an incompatibility.</p>
+<p><a href="https://proton.me/drive">Proton Drive</a> is an end-to-end
+encrypted Swiss vault for your files that protects your data.</p>
+<p>This is an rclone backend for Proton Drive which supports the file
+transfer features of Proton Drive using the same client-side
+encryption.</p>
+<p>Due to the fact that Proton Drive doesn't publish its API
+documentation, this backend is implemented with best efforts by reading
+the open-sourced client source code and observing the Proton Drive
+traffic in the browser.</p>
+<p><strong>NB</strong> This backend is currently in Beta. It is believed
+to be correct and all the integration tests pass. However the Proton
+Drive protocol has evolved over time there may be accounts it is not
+compatible with. Please <a href="https://forum.rclone.org/">post on the
+rclone forum</a> if you find an incompatibility.</p>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
 <h2 id="configurations">Configurations</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -32758,27 +46933,48 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p><strong>NOTE:</strong> The Proton Drive encryption keys need to have been already generated after a regular login via the browser, otherwise attempting to use the credentials in <code>rclone</code> will fail.</p>
+<p><strong>NOTE:</strong> The Proton Drive encryption keys need to have
+been already generated after a regular login via the browser, otherwise
+attempting to use the credentials in <code>rclone</code> will fail.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your Proton Drive</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>List all the files in your Proton Drive</p>
 <pre><code>rclone ls remote:</code></pre>
-<p>To copy a local directory to an Proton Drive directory called backup</p>
+<p>To copy a local directory to an Proton Drive directory called
+backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-23">Modification times and hashes</h3>
-<p>Proton Drive Bridge does not support updating modification times yet.</p>
+<h3 id="modification-times-and-hashes-23">Modification times and
+hashes</h3>
+<p>Proton Drive Bridge does not support updating modification times
+yet.</p>
 <p>The SHA1 hash algorithm is supported.</p>
-<h3 id="restricted-filename-characters-27">Restricted filename characters</h3>
-<p>Invalid UTF-8 bytes will be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, also left and right spaces will be removed (<a href="https://github.com/ProtonMail/WebClients/blob/b4eba99d241af4fdae06ff7138bd651a40ef5d3c/applications/drive/src/app/store/_links/validation.ts#L51">code reference</a>)</p>
+<h3 id="restricted-filename-characters-26">Restricted filename
+characters</h3>
+<p>Invalid UTF-8 bytes will be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, also left
+and right spaces will be removed (<a
+href="https://github.com/ProtonMail/WebClients/blob/b4eba99d241af4fdae06ff7138bd651a40ef5d3c/applications/drive/src/app/store/_links/validation.ts#L51">code
+reference</a>)</p>
 <h3 id="duplicated-files-4">Duplicated files</h3>
-<p>Proton Drive can not have two files with exactly the same name and path. If the conflict occurs, depending on the advanced config, the file might or might not be overwritten.</p>
-<h3 id="mailbox-password"><a href="https://proton.me/support/the-difference-between-the-mailbox-password-and-login-password">Mailbox password</a></h3>
+<p>Proton Drive can not have two files with exactly the same name and
+path. If the conflict occurs, depending on the advanced config, the file
+might or might not be overwritten.</p>
+<h3 id="mailbox-password"><a
+href="https://proton.me/support/the-difference-between-the-mailbox-password-and-login-password">Mailbox
+password</a></h3>
 <p>Please set your mailbox password in the advanced config section.</p>
 <h3 id="caching">Caching</h3>
-<p>The cache is currently built for the case when the rclone is the only instance performing operations to the mount point. The event system, which is the proton API system that provides visibility of what has changed on the drive, is yet to be implemented, so updates from other clients won’t be reflected in the cache. Thus, if there are concurrent clients accessing the same mount point, then we might have a problem with caching the stale data.</p>
-<h3 id="standard-options-44">Standard options</h3>
-<p>Here are the Standard options specific to protondrive (Proton Drive).</p>
+<p>The cache is currently built for the case when the rclone is the only
+instance performing operations to the mount point. The event system,
+which is the proton API system that provides visibility of what has
+changed on the drive, is yet to be implemented, so updates from other
+clients won’t be reflected in the cache. Thus, if there are concurrent
+clients accessing the same mount point, then we might have a problem
+with caching the stale data.</p>
+<h3 id="standard-options-45">Standard options</h3>
+<p>Here are the Standard options specific to protondrive (Proton
+Drive).</p>
 <h4 id="protondrive-username">--protondrive-username</h4>
 <p>The username of your proton account</p>
 <p>Properties:</p>
@@ -32790,7 +46986,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="protondrive-password">--protondrive-password</h4>
 <p>The password of your proton account.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -32801,7 +46999,8 @@ y/e/d&gt; y</code></pre>
 <h4 id="protondrive-2fa">--protondrive-2fa</h4>
 <p>The 2FA code</p>
 <p>The value can also be provided with --protondrive-2fa=000000</p>
-<p>The 2FA code of your proton drive account if the account is set up with two-factor authentication</p>
+<p>The 2FA code of your proton drive account if the account is set up
+with two-factor authentication</p>
 <p>Properties:</p>
 <ul>
 <li>Config: 2fa</li>
@@ -32809,12 +47008,18 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-45">Advanced options</h3>
-<p>Here are the Advanced options specific to protondrive (Proton Drive).</p>
-<h4 id="protondrive-mailbox-password">--protondrive-mailbox-password</h4>
+<h3 id="advanced-options-46">Advanced options</h3>
+<p>Here are the Advanced options specific to protondrive (Proton
+Drive).</p>
+<h4
+id="protondrive-mailbox-password">--protondrive-mailbox-password</h4>
 <p>The mailbox password of your two-password proton account.</p>
-<p>For more information regarding the mailbox password, please check the following official knowledge base article: https://proton.me/support/the-difference-between-the-mailbox-password-and-login-password</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>For more information regarding the mailbox password, please check the
+following official knowledge base article:
+https://proton.me/support/the-difference-between-the-mailbox-password-and-login-password</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: mailbox_password</li>
@@ -32831,7 +47036,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="protondrive-client-access-token">--protondrive-client-access-token</h4>
+<h4
+id="protondrive-client-access-token">--protondrive-client-access-token</h4>
 <p>Client access token key (internal use only)</p>
 <p>Properties:</p>
 <ul>
@@ -32840,7 +47046,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="protondrive-client-refresh-token">--protondrive-client-refresh-token</h4>
+<h4
+id="protondrive-client-refresh-token">--protondrive-client-refresh-token</h4>
 <p>Client refresh token key (internal use only)</p>
 <p>Properties:</p>
 <ul>
@@ -32849,7 +47056,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="protondrive-client-salted-key-pass">--protondrive-client-salted-key-pass</h4>
+<h4
+id="protondrive-client-salted-key-pass">--protondrive-client-salted-key-pass</h4>
 <p>Client salted key pass key (internal use only)</p>
 <p>Properties:</p>
 <ul>
@@ -32860,7 +47068,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="protondrive-encoding">--protondrive-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -32868,9 +47077,14 @@ y/e/d&gt; y</code></pre>
 <li>Type: Encoding</li>
 <li>Default: Slash,LeftSpace,RightSpace,InvalidUtf8,Dot</li>
 </ul>
-<h4 id="protondrive-original-file-size">--protondrive-original-file-size</h4>
+<h4
+id="protondrive-original-file-size">--protondrive-original-file-size</h4>
 <p>Return the file size before encryption</p>
-<p>The size of the encrypted file will be different from (bigger than) the original file size. Unless there is a reason to return the file size after encryption is performed, otherwise, set this option to true, as features like Open() which will need to be supplied with original content size, will fail to operate properly</p>
+<p>The size of the encrypted file will be different from (bigger than)
+the original file size. Unless there is a reason to return the file size
+after encryption is performed, otherwise, set this option to true, as
+features like Open() which will need to be supplied with original
+content size, will fail to operate properly</p>
 <p>Properties:</p>
 <ul>
 <li>Config: original_file_size</li>
@@ -32880,7 +47094,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="protondrive-app-version">--protondrive-app-version</h4>
 <p>The app version string</p>
-<p>The app version string indicates the client that is currently performing the API request. This information is required and will be sent with every API request.</p>
+<p>The app version string indicates the client that is currently
+performing the API request. This information is required and will be
+sent with every API request.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: app_version</li>
@@ -32888,11 +47104,21 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: "macos-drive@1.0.0-alpha.1+rclone"</li>
 </ul>
-<h4 id="protondrive-replace-existing-draft">--protondrive-replace-existing-draft</h4>
+<h4
+id="protondrive-replace-existing-draft">--protondrive-replace-existing-draft</h4>
 <p>Create a new revision when filename conflict is detected</p>
-<p>When a file upload is cancelled or failed before completion, a draft will be created and the subsequent upload of the same file to the same location will be reported as a conflict.</p>
-<p>The value can also be set by --protondrive-replace-existing-draft=true</p>
-<p>If the option is set to true, the draft will be replaced and then the upload operation will restart. If there are other clients also uploading at the same file location at the same time, the behavior is currently unknown. Need to set to true for integration tests. If the option is set to false, an error "a draft exist - usually this means a file is being uploaded at another client, or, there was a failed upload attempt" will be returned, and no upload will happen.</p>
+<p>When a file upload is cancelled or failed before completion, a draft
+will be created and the subsequent upload of the same file to the same
+location will be reported as a conflict.</p>
+<p>The value can also be set by
+--protondrive-replace-existing-draft=true</p>
+<p>If the option is set to true, the draft will be replaced and then the
+upload operation will restart. If there are other clients also uploading
+at the same file location at the same time, the behavior is currently
+unknown. Need to set to true for integration tests. If the option is set
+to false, an error "a draft exist - usually this means a file is being
+uploaded at another client, or, there was a failed upload attempt" will
+be returned, and no upload will happen.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: replace_existing_draft</li>
@@ -32902,9 +47128,19 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="protondrive-enable-caching">--protondrive-enable-caching</h4>
 <p>Caches the files and folders metadata to reduce API calls</p>
-<p>Notice: If you are mounting ProtonDrive as a VFS, please disable this feature, as the current implementation doesn't update or clear the cache when there are external changes.</p>
-<p>The files and folders on ProtonDrive are represented as links with keyrings, which can be cached to improve performance and be friendly to the API server.</p>
-<p>The cache is currently built for the case when the rclone is the only instance performing operations to the mount point. The event system, which is the proton API system that provides visibility of what has changed on the drive, is yet to be implemented, so updates from other clients won’t be reflected in the cache. Thus, if there are concurrent clients accessing the same mount point, then we might have a problem with caching the stale data.</p>
+<p>Notice: If you are mounting ProtonDrive as a VFS, please disable this
+feature, as the current implementation doesn't update or clear the cache
+when there are external changes.</p>
+<p>The files and folders on ProtonDrive are represented as links with
+keyrings, which can be cached to improve performance and be friendly to
+the API server.</p>
+<p>The cache is currently built for the case when the rclone is the only
+instance performing operations to the mount point. The event system,
+which is the proton API system that provides visibility of what has
+changed on the drive, is yet to be implemented, so updates from other
+clients won’t be reflected in the cache. Thus, if there are concurrent
+clients accessing the same mount point, then we might have a problem
+with caching the stale data.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: enable_caching</li>
@@ -32922,16 +47158,40 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-33">Limitations</h2>
-<p>This backend uses the <a href="https://github.com/henrybear327/Proton-API-Bridge">Proton-API-Bridge</a>, which is based on <a href="https://github.com/henrybear327/go-proton-api">go-proton-api</a>, a fork of the <a href="https://github.com/ProtonMail/go-proton-api">official repo</a>.</p>
-<p>There is no official API documentation available from Proton Drive. But, thanks to Proton open sourcing <a href="https://github.com/ProtonMail/go-proton-api">proton-go-api</a> and the web, iOS, and Android client codebases, we don't need to completely reverse engineer the APIs by observing the web client traffic!</p>
-<p><a href="https://github.com/ProtonMail/go-proton-api">proton-go-api</a> provides the basic building blocks of API calls and error handling, such as 429 exponential back-off, but it is pretty much just a barebone interface to the Proton API. For example, the encryption and decryption of the Proton Drive file are not provided in this library.</p>
-<p>The Proton-API-Bridge, attempts to bridge the gap, so rclone can be built on top of this quickly. This codebase handles the intricate tasks before and after calling Proton APIs, particularly the complex encryption scheme, allowing developers to implement features for other software on top of this codebase. There are likely quite a few errors in this library, as there isn't official documentation available.</p>
+<p>This backend uses the <a
+href="https://github.com/henrybear327/Proton-API-Bridge">Proton-API-Bridge</a>,
+which is based on <a
+href="https://github.com/henrybear327/go-proton-api">go-proton-api</a>,
+a fork of the <a
+href="https://github.com/ProtonMail/go-proton-api">official
+repo</a>.</p>
+<p>There is no official API documentation available from Proton Drive.
+But, thanks to Proton open sourcing <a
+href="https://github.com/ProtonMail/go-proton-api">proton-go-api</a> and
+the web, iOS, and Android client codebases, we don't need to completely
+reverse engineer the APIs by observing the web client traffic!</p>
+<p><a
+href="https://github.com/ProtonMail/go-proton-api">proton-go-api</a>
+provides the basic building blocks of API calls and error handling, such
+as 429 exponential back-off, but it is pretty much just a barebone
+interface to the Proton API. For example, the encryption and decryption
+of the Proton Drive file are not provided in this library.</p>
+<p>The Proton-API-Bridge, attempts to bridge the gap, so rclone can be
+built on top of this quickly. This codebase handles the intricate tasks
+before and after calling Proton APIs, particularly the complex
+encryption scheme, allowing developers to implement features for other
+software on top of this codebase. There are likely quite a few errors in
+this library, as there isn't official documentation available.</p>
 <h1 id="put.io">put.io</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>put.io paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-43">Configuration</h2>
-<p>The initial setup for put.io involves getting a token from put.io which you need to do in your browser. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>put.io paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-44">Configuration</h2>
+<p>The initial setup for put.io involves getting a token from put.io
+which you need to do in your browser. <code>rclone config</code> walks
+you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -32985,8 +47245,16 @@ c) Copy remote
 s) Set configuration password
 q) Quit config
 e/n/d/r/c/s/q&gt; q</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from put.io if using web browser to automatically authenticate. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall, or use manual mode.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from put.io if using web browser to automatically
+authenticate. This only runs from the moment it opens your browser to
+the moment you get back the verification code. This is on
+<code>http://127.0.0.1:53682/</code> and this it may require you to
+unblock it temporarily if you are running a host firewall, or use manual
+mode.</p>
 <p>You can then use it like this,</p>
 <p>List directories in top level of your put.io</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -32994,8 +47262,12 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to a put.io directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="restricted-filename-characters-28">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<h3 id="restricted-filename-characters-27">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -33012,8 +47284,10 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<h3 id="standard-options-45">Standard options</h3>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<h3 id="standard-options-46">Standard options</h3>
 <p>Here are the Standard options specific to putio (Put.io).</p>
 <h4 id="putio-client-id">--putio-client-id</h4>
 <p>OAuth Client Id.</p>
@@ -33035,7 +47309,7 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-46">Advanced options</h3>
+<h3 id="advanced-options-47">Advanced options</h3>
 <p>Here are the Advanced options specific to putio (Put.io).</p>
 <h4 id="putio-token">--putio-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
@@ -33068,7 +47342,8 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </ul>
 <h4 id="putio-encoding">--putio-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -33086,17 +47361,33 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-34">Limitations</h2>
-<p>put.io has rate limiting. When you hit a limit, rclone automatically retries after waiting the amount of time requested by the server.</p>
-<p>If you want to avoid ever hitting these limits, you may use the <code>--tpslimit</code> flag with a low number. Note that the imposed limits may be different for different operations, and may change over time.</p>
+<p>put.io has rate limiting. When you hit a limit, rclone automatically
+retries after waiting the amount of time requested by the server.</p>
+<p>If you want to avoid ever hitting these limits, you may use the
+<code>--tpslimit</code> flag with a low number. Note that the imposed
+limits may be different for different operations, and may change over
+time.</p>
 <h1 id="proton-drive-1">Proton Drive</h1>
-<p><a href="https://proton.me/drive">Proton Drive</a> is an end-to-end encrypted Swiss vault for your files that protects your data.</p>
-<p>This is an rclone backend for Proton Drive which supports the file transfer features of Proton Drive using the same client-side encryption.</p>
-<p>Due to the fact that Proton Drive doesn't publish its API documentation, this backend is implemented with best efforts by reading the open-sourced client source code and observing the Proton Drive traffic in the browser.</p>
-<p><strong>NB</strong> This backend is currently in Beta. It is believed to be correct and all the integration tests pass. However the Proton Drive protocol has evolved over time there may be accounts it is not compatible with. Please <a href="https://forum.rclone.org/">post on the rclone forum</a> if you find an incompatibility.</p>
+<p><a href="https://proton.me/drive">Proton Drive</a> is an end-to-end
+encrypted Swiss vault for your files that protects your data.</p>
+<p>This is an rclone backend for Proton Drive which supports the file
+transfer features of Proton Drive using the same client-side
+encryption.</p>
+<p>Due to the fact that Proton Drive doesn't publish its API
+documentation, this backend is implemented with best efforts by reading
+the open-sourced client source code and observing the Proton Drive
+traffic in the browser.</p>
+<p><strong>NB</strong> This backend is currently in Beta. It is believed
+to be correct and all the integration tests pass. However the Proton
+Drive protocol has evolved over time there may be accounts it is not
+compatible with. Please <a href="https://forum.rclone.org/">post on the
+rclone forum</a> if you find an incompatibility.</p>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
 <h2 id="configurations-1">Configurations</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -33138,27 +47429,48 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p><strong>NOTE:</strong> The Proton Drive encryption keys need to have been already generated after a regular login via the browser, otherwise attempting to use the credentials in <code>rclone</code> will fail.</p>
+<p><strong>NOTE:</strong> The Proton Drive encryption keys need to have
+been already generated after a regular login via the browser, otherwise
+attempting to use the credentials in <code>rclone</code> will fail.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories in top level of your Proton Drive</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>List all the files in your Proton Drive</p>
 <pre><code>rclone ls remote:</code></pre>
-<p>To copy a local directory to an Proton Drive directory called backup</p>
+<p>To copy a local directory to an Proton Drive directory called
+backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-24">Modification times and hashes</h3>
-<p>Proton Drive Bridge does not support updating modification times yet.</p>
+<h3 id="modification-times-and-hashes-24">Modification times and
+hashes</h3>
+<p>Proton Drive Bridge does not support updating modification times
+yet.</p>
 <p>The SHA1 hash algorithm is supported.</p>
-<h3 id="restricted-filename-characters-29">Restricted filename characters</h3>
-<p>Invalid UTF-8 bytes will be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, also left and right spaces will be removed (<a href="https://github.com/ProtonMail/WebClients/blob/b4eba99d241af4fdae06ff7138bd651a40ef5d3c/applications/drive/src/app/store/_links/validation.ts#L51">code reference</a>)</p>
+<h3 id="restricted-filename-characters-28">Restricted filename
+characters</h3>
+<p>Invalid UTF-8 bytes will be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, also left
+and right spaces will be removed (<a
+href="https://github.com/ProtonMail/WebClients/blob/b4eba99d241af4fdae06ff7138bd651a40ef5d3c/applications/drive/src/app/store/_links/validation.ts#L51">code
+reference</a>)</p>
 <h3 id="duplicated-files-5">Duplicated files</h3>
-<p>Proton Drive can not have two files with exactly the same name and path. If the conflict occurs, depending on the advanced config, the file might or might not be overwritten.</p>
-<h3 id="mailbox-password-1"><a href="https://proton.me/support/the-difference-between-the-mailbox-password-and-login-password">Mailbox password</a></h3>
+<p>Proton Drive can not have two files with exactly the same name and
+path. If the conflict occurs, depending on the advanced config, the file
+might or might not be overwritten.</p>
+<h3 id="mailbox-password-1"><a
+href="https://proton.me/support/the-difference-between-the-mailbox-password-and-login-password">Mailbox
+password</a></h3>
 <p>Please set your mailbox password in the advanced config section.</p>
 <h3 id="caching-1">Caching</h3>
-<p>The cache is currently built for the case when the rclone is the only instance performing operations to the mount point. The event system, which is the proton API system that provides visibility of what has changed on the drive, is yet to be implemented, so updates from other clients won’t be reflected in the cache. Thus, if there are concurrent clients accessing the same mount point, then we might have a problem with caching the stale data.</p>
-<h3 id="standard-options-46">Standard options</h3>
-<p>Here are the Standard options specific to protondrive (Proton Drive).</p>
+<p>The cache is currently built for the case when the rclone is the only
+instance performing operations to the mount point. The event system,
+which is the proton API system that provides visibility of what has
+changed on the drive, is yet to be implemented, so updates from other
+clients won’t be reflected in the cache. Thus, if there are concurrent
+clients accessing the same mount point, then we might have a problem
+with caching the stale data.</p>
+<h3 id="standard-options-47">Standard options</h3>
+<p>Here are the Standard options specific to protondrive (Proton
+Drive).</p>
 <h4 id="protondrive-username-1">--protondrive-username</h4>
 <p>The username of your proton account</p>
 <p>Properties:</p>
@@ -33170,7 +47482,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="protondrive-password-1">--protondrive-password</h4>
 <p>The password of your proton account.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -33181,7 +47495,8 @@ y/e/d&gt; y</code></pre>
 <h4 id="protondrive-2fa-1">--protondrive-2fa</h4>
 <p>The 2FA code</p>
 <p>The value can also be provided with --protondrive-2fa=000000</p>
-<p>The 2FA code of your proton drive account if the account is set up with two-factor authentication</p>
+<p>The 2FA code of your proton drive account if the account is set up
+with two-factor authentication</p>
 <p>Properties:</p>
 <ul>
 <li>Config: 2fa</li>
@@ -33189,12 +47504,18 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-47">Advanced options</h3>
-<p>Here are the Advanced options specific to protondrive (Proton Drive).</p>
-<h4 id="protondrive-mailbox-password-1">--protondrive-mailbox-password</h4>
+<h3 id="advanced-options-48">Advanced options</h3>
+<p>Here are the Advanced options specific to protondrive (Proton
+Drive).</p>
+<h4
+id="protondrive-mailbox-password-1">--protondrive-mailbox-password</h4>
 <p>The mailbox password of your two-password proton account.</p>
-<p>For more information regarding the mailbox password, please check the following official knowledge base article: https://proton.me/support/the-difference-between-the-mailbox-password-and-login-password</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>For more information regarding the mailbox password, please check the
+following official knowledge base article:
+https://proton.me/support/the-difference-between-the-mailbox-password-and-login-password</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: mailbox_password</li>
@@ -33211,7 +47532,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="protondrive-client-access-token-1">--protondrive-client-access-token</h4>
+<h4
+id="protondrive-client-access-token-1">--protondrive-client-access-token</h4>
 <p>Client access token key (internal use only)</p>
 <p>Properties:</p>
 <ul>
@@ -33220,7 +47542,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="protondrive-client-refresh-token-1">--protondrive-client-refresh-token</h4>
+<h4
+id="protondrive-client-refresh-token-1">--protondrive-client-refresh-token</h4>
 <p>Client refresh token key (internal use only)</p>
 <p>Properties:</p>
 <ul>
@@ -33229,7 +47552,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="protondrive-client-salted-key-pass-1">--protondrive-client-salted-key-pass</h4>
+<h4
+id="protondrive-client-salted-key-pass-1">--protondrive-client-salted-key-pass</h4>
 <p>Client salted key pass key (internal use only)</p>
 <p>Properties:</p>
 <ul>
@@ -33240,7 +47564,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="protondrive-encoding-1">--protondrive-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -33248,9 +47573,14 @@ y/e/d&gt; y</code></pre>
 <li>Type: Encoding</li>
 <li>Default: Slash,LeftSpace,RightSpace,InvalidUtf8,Dot</li>
 </ul>
-<h4 id="protondrive-original-file-size-1">--protondrive-original-file-size</h4>
+<h4
+id="protondrive-original-file-size-1">--protondrive-original-file-size</h4>
 <p>Return the file size before encryption</p>
-<p>The size of the encrypted file will be different from (bigger than) the original file size. Unless there is a reason to return the file size after encryption is performed, otherwise, set this option to true, as features like Open() which will need to be supplied with original content size, will fail to operate properly</p>
+<p>The size of the encrypted file will be different from (bigger than)
+the original file size. Unless there is a reason to return the file size
+after encryption is performed, otherwise, set this option to true, as
+features like Open() which will need to be supplied with original
+content size, will fail to operate properly</p>
 <p>Properties:</p>
 <ul>
 <li>Config: original_file_size</li>
@@ -33260,7 +47590,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="protondrive-app-version-1">--protondrive-app-version</h4>
 <p>The app version string</p>
-<p>The app version string indicates the client that is currently performing the API request. This information is required and will be sent with every API request.</p>
+<p>The app version string indicates the client that is currently
+performing the API request. This information is required and will be
+sent with every API request.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: app_version</li>
@@ -33268,11 +47600,21 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Default: "macos-drive@1.0.0-alpha.1+rclone"</li>
 </ul>
-<h4 id="protondrive-replace-existing-draft-1">--protondrive-replace-existing-draft</h4>
+<h4
+id="protondrive-replace-existing-draft-1">--protondrive-replace-existing-draft</h4>
 <p>Create a new revision when filename conflict is detected</p>
-<p>When a file upload is cancelled or failed before completion, a draft will be created and the subsequent upload of the same file to the same location will be reported as a conflict.</p>
-<p>The value can also be set by --protondrive-replace-existing-draft=true</p>
-<p>If the option is set to true, the draft will be replaced and then the upload operation will restart. If there are other clients also uploading at the same file location at the same time, the behavior is currently unknown. Need to set to true for integration tests. If the option is set to false, an error "a draft exist - usually this means a file is being uploaded at another client, or, there was a failed upload attempt" will be returned, and no upload will happen.</p>
+<p>When a file upload is cancelled or failed before completion, a draft
+will be created and the subsequent upload of the same file to the same
+location will be reported as a conflict.</p>
+<p>The value can also be set by
+--protondrive-replace-existing-draft=true</p>
+<p>If the option is set to true, the draft will be replaced and then the
+upload operation will restart. If there are other clients also uploading
+at the same file location at the same time, the behavior is currently
+unknown. Need to set to true for integration tests. If the option is set
+to false, an error "a draft exist - usually this means a file is being
+uploaded at another client, or, there was a failed upload attempt" will
+be returned, and no upload will happen.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: replace_existing_draft</li>
@@ -33282,9 +47624,19 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="protondrive-enable-caching-1">--protondrive-enable-caching</h4>
 <p>Caches the files and folders metadata to reduce API calls</p>
-<p>Notice: If you are mounting ProtonDrive as a VFS, please disable this feature, as the current implementation doesn't update or clear the cache when there are external changes.</p>
-<p>The files and folders on ProtonDrive are represented as links with keyrings, which can be cached to improve performance and be friendly to the API server.</p>
-<p>The cache is currently built for the case when the rclone is the only instance performing operations to the mount point. The event system, which is the proton API system that provides visibility of what has changed on the drive, is yet to be implemented, so updates from other clients won’t be reflected in the cache. Thus, if there are concurrent clients accessing the same mount point, then we might have a problem with caching the stale data.</p>
+<p>Notice: If you are mounting ProtonDrive as a VFS, please disable this
+feature, as the current implementation doesn't update or clear the cache
+when there are external changes.</p>
+<p>The files and folders on ProtonDrive are represented as links with
+keyrings, which can be cached to improve performance and be friendly to
+the API server.</p>
+<p>The cache is currently built for the case when the rclone is the only
+instance performing operations to the mount point. The event system,
+which is the proton API system that provides visibility of what has
+changed on the drive, is yet to be implemented, so updates from other
+clients won’t be reflected in the cache. Thus, if there are concurrent
+clients accessing the same mount point, then we might have a problem
+with caching the stale data.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: enable_caching</li>
@@ -33302,18 +47654,54 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-35">Limitations</h2>
-<p>This backend uses the <a href="https://github.com/henrybear327/Proton-API-Bridge">Proton-API-Bridge</a>, which is based on <a href="https://github.com/henrybear327/go-proton-api">go-proton-api</a>, a fork of the <a href="https://github.com/ProtonMail/go-proton-api">official repo</a>.</p>
-<p>There is no official API documentation available from Proton Drive. But, thanks to Proton open sourcing <a href="https://github.com/ProtonMail/go-proton-api">proton-go-api</a> and the web, iOS, and Android client codebases, we don't need to completely reverse engineer the APIs by observing the web client traffic!</p>
-<p><a href="https://github.com/ProtonMail/go-proton-api">proton-go-api</a> provides the basic building blocks of API calls and error handling, such as 429 exponential back-off, but it is pretty much just a barebone interface to the Proton API. For example, the encryption and decryption of the Proton Drive file are not provided in this library.</p>
-<p>The Proton-API-Bridge, attempts to bridge the gap, so rclone can be built on top of this quickly. This codebase handles the intricate tasks before and after calling Proton APIs, particularly the complex encryption scheme, allowing developers to implement features for other software on top of this codebase. There are likely quite a few errors in this library, as there isn't official documentation available.</p>
+<p>This backend uses the <a
+href="https://github.com/henrybear327/Proton-API-Bridge">Proton-API-Bridge</a>,
+which is based on <a
+href="https://github.com/henrybear327/go-proton-api">go-proton-api</a>,
+a fork of the <a
+href="https://github.com/ProtonMail/go-proton-api">official
+repo</a>.</p>
+<p>There is no official API documentation available from Proton Drive.
+But, thanks to Proton open sourcing <a
+href="https://github.com/ProtonMail/go-proton-api">proton-go-api</a> and
+the web, iOS, and Android client codebases, we don't need to completely
+reverse engineer the APIs by observing the web client traffic!</p>
+<p><a
+href="https://github.com/ProtonMail/go-proton-api">proton-go-api</a>
+provides the basic building blocks of API calls and error handling, such
+as 429 exponential back-off, but it is pretty much just a barebone
+interface to the Proton API. For example, the encryption and decryption
+of the Proton Drive file are not provided in this library.</p>
+<p>The Proton-API-Bridge, attempts to bridge the gap, so rclone can be
+built on top of this quickly. This codebase handles the intricate tasks
+before and after calling Proton APIs, particularly the complex
+encryption scheme, allowing developers to implement features for other
+software on top of this codebase. There are likely quite a few errors in
+this library, as there isn't official documentation available.</p>
 <h1 id="seafile">Seafile</h1>
-<p>This is a backend for the <a href="https://www.seafile.com/">Seafile</a> storage service: - It works with both the free community edition or the professional edition. - Seafile versions 6.x, 7.x, 8.x and 9.x are all supported. - Encrypted libraries are also supported. - It supports 2FA enabled users - Using a Library API Token is <strong>not</strong> supported</p>
-<h2 id="configuration-44">Configuration</h2>
-<p>There are two distinct modes you can setup your remote: - you point your remote to the <strong>root of the server</strong>, meaning you don't specify a library during the configuration: Paths are specified as <code>remote:library</code>. You may put subdirectories in too, e.g. <code>remote:library/path/to/dir</code>. - you point your remote to a specific library during the configuration: Paths are specified as <code>remote:path/to/dir</code>. <strong>This is the recommended mode when using encrypted libraries</strong>. (<em>This mode is possibly slightly faster than the root mode</em>)</p>
+<p>This is a backend for the <a
+href="https://www.seafile.com/">Seafile</a> storage service: - It works
+with both the free community edition or the professional edition. -
+Seafile versions 6.x, 7.x, 8.x and 9.x are all supported. - Encrypted
+libraries are also supported. - It supports 2FA enabled users - Using a
+Library API Token is <strong>not</strong> supported</p>
+<h2 id="configuration-45">Configuration</h2>
+<p>There are two distinct modes you can setup your remote: - you point
+your remote to the <strong>root of the server</strong>, meaning you
+don't specify a library during the configuration: Paths are specified as
+<code>remote:library</code>. You may put subdirectories in too, e.g.
+<code>remote:library/path/to/dir</code>. - you point your remote to a
+specific library during the configuration: Paths are specified as
+<code>remote:path/to/dir</code>. <strong>This is the recommended mode
+when using encrypted libraries</strong>. (<em>This mode is possibly
+slightly faster than the root mode</em>)</p>
 <h3 id="configuration-in-root-mode">Configuration in root mode</h3>
-<p>Here is an example of making a seafile configuration for a user with <strong>no</strong> two-factor authentication. First run</p>
+<p>Here is an example of making a seafile configuration for a user with
+<strong>no</strong> two-factor authentication. First run</p>
 <pre><code>rclone config</code></pre>
-<p>This will guide you through an interactive setup process. To authenticate you will need the URL of your server, your email (or username) and your password.</p>
+<p>This will guide you through an interactive setup process. To
+authenticate you will need the URL of your server, your email (or
+username) and your password.</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -33377,17 +47765,23 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>This remote is called <code>seafile</code>. It's pointing to the root of your seafile server and can now be used like this:</p>
+<p>This remote is called <code>seafile</code>. It's pointing to the root
+of your seafile server and can now be used like this:</p>
 <p>See all libraries</p>
 <pre><code>rclone lsd seafile:</code></pre>
 <p>Create a new library</p>
 <pre><code>rclone mkdir seafile:library</code></pre>
 <p>List the contents of a library</p>
 <pre><code>rclone ls seafile:library</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote library, deleting any excess files in the library.</p>
+<p>Sync <code>/home/local/directory</code> to the remote library,
+deleting any excess files in the library.</p>
 <pre><code>rclone sync --interactive /home/local/directory seafile:library</code></pre>
-<h3 id="configuration-in-library-mode">Configuration in library mode</h3>
-<p>Here's an example of a configuration in library mode with a user that has the two-factor authentication enabled. Your 2FA code will be asked at the end of the configuration, and will attempt to authenticate you:</p>
+<h3 id="configuration-in-library-mode">Configuration in library
+mode</h3>
+<p>Here's an example of a configuration in library mode with a user that
+has the two-factor authentication enabled. Your 2FA code will be asked
+at the end of the configuration, and will attempt to authenticate
+you:</p>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -33455,20 +47849,32 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>You'll notice your password is blank in the configuration. It's because we only need the password to authenticate you once.</p>
-<p>You specified <code>My Library</code> during the configuration. The root of the remote is pointing at the root of the library <code>My Library</code>:</p>
+<p>You'll notice your password is blank in the configuration. It's
+because we only need the password to authenticate you once.</p>
+<p>You specified <code>My Library</code> during the configuration. The
+root of the remote is pointing at the root of the library
+<code>My Library</code>:</p>
 <p>See all files in the library:</p>
 <pre><code>rclone lsd seafile:</code></pre>
 <p>Create a new directory inside the library</p>
 <pre><code>rclone mkdir seafile:directory</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls seafile:directory</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote library, deleting any excess files in the library.</p>
+<p>Sync <code>/home/local/directory</code> to the remote library,
+deleting any excess files in the library.</p>
 <pre><code>rclone sync --interactive /home/local/directory seafile:</code></pre>
 <h3 id="fast-list-9">--fast-list</h3>
-<p>Seafile version 7+ supports <code>--fast-list</code> which allows you to use fewer transactions in exchange for more memory. See the <a href="https://rclone.org/docs/#fast-list">rclone docs</a> for more details. Please note this is not supported on seafile server version 6.x</p>
-<h3 id="restricted-filename-characters-30">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>Seafile version 7+ supports <code>--fast-list</code> which allows you
+to use fewer transactions in exchange for more memory. See the <a
+href="https://rclone.org/docs/#fast-list">rclone docs</a> for more
+details. Please note this is not supported on seafile server version
+6.x</p>
+<h3 id="restricted-filename-characters-29">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -33495,21 +47901,33 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="seafile-and-rclone-link">Seafile and rclone link</h3>
-<p>Rclone supports generating share links for non-encrypted libraries only. They can either be for a file or a directory:</p>
+<p>Rclone supports generating share links for non-encrypted libraries
+only. They can either be for a file or a directory:</p>
 <pre><code>rclone link seafile:seafile-tutorial.doc
 http://my.seafile.server/f/fdcd8a2f93f84b8b90f4/
 </code></pre>
 <p>or if run on a directory you will get:</p>
 <pre><code>rclone link seafile:dir
 http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
-<p>Please note a share link is unique for each file or directory. If you run a link command on a file/dir that has already been shared, you will get the exact same link.</p>
+<p>Please note a share link is unique for each file or directory. If you
+run a link command on a file/dir that has already been shared, you will
+get the exact same link.</p>
 <h3 id="compatibility">Compatibility</h3>
-<p>It has been actively developed using the <a href="https://github.com/haiwen/seafile-docker">seafile docker image</a> of these versions: - 6.3.4 community edition - 7.0.5 community edition - 7.1.3 community edition - 9.0.10 community edition</p>
-<p>Versions below 6.0 are not supported. Versions between 6.0 and 6.3 haven't been tested and might not work properly.</p>
-<p>Each new version of <code>rclone</code> is automatically tested against the <a href="https://hub.docker.com/r/seafileltd/seafile-mc/">latest docker image</a> of the seafile community server.</p>
-<h3 id="standard-options-47">Standard options</h3>
+<p>It has been actively developed using the <a
+href="https://github.com/haiwen/seafile-docker">seafile docker image</a>
+of these versions: - 6.3.4 community edition - 7.0.5 community edition -
+7.1.3 community edition - 9.0.10 community edition</p>
+<p>Versions below 6.0 are not supported. Versions between 6.0 and 6.3
+haven't been tested and might not work properly.</p>
+<p>Each new version of <code>rclone</code> is automatically tested
+against the <a
+href="https://hub.docker.com/r/seafileltd/seafile-mc/">latest docker
+image</a> of the seafile community server.</p>
+<h3 id="standard-options-48">Standard options</h3>
 <p>Here are the Standard options specific to seafile (seafile).</p>
 <h4 id="seafile-url">--seafile-url</h4>
 <p>URL of seafile host to connect to.</p>
@@ -33538,7 +47956,9 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 </ul>
 <h4 id="seafile-pass">--seafile-pass</h4>
 <p>Password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass</li>
@@ -33547,7 +47967,8 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="seafile-2fa">--seafile-2fa</h4>
-<p>Two-factor authentication ('true' if the account has 2FA enabled).</p>
+<p>Two-factor authentication ('true' if the account has 2FA
+enabled).</p>
 <p>Properties:</p>
 <ul>
 <li>Config: 2fa</li>
@@ -33568,7 +47989,9 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <h4 id="seafile-library-key">--seafile-library-key</h4>
 <p>Library password (for encrypted libraries only).</p>
 <p>Leave blank if you pass it through the command line.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: library_key</li>
@@ -33585,7 +48008,7 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-48">Advanced options</h3>
+<h3 id="advanced-options-49">Advanced options</h3>
 <p>Here are the Advanced options specific to seafile (seafile).</p>
 <h4 id="seafile-create-library">--seafile-create-library</h4>
 <p>Should rclone create a library if it doesn't exist.</p>
@@ -33598,7 +48021,8 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 </ul>
 <h4 id="seafile-encoding">--seafile-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -33616,17 +48040,32 @@ http://my.seafile.server/d/9ea2455f6f55478bbb0d/</code></pre>
 <li>Required: false</li>
 </ul>
 <h1 id="sftp">SFTP</h1>
-<p>SFTP is the <a href="https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol">Secure (or SSH) File Transfer Protocol</a>.</p>
-<p>The SFTP backend can be used with a number of different providers:</p>
+<p>SFTP is the <a
+href="https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol">Secure
+(or SSH) File Transfer Protocol</a>.</p>
+<p>The SFTP backend can be used with a number of different
+providers:</p>
 <ul>
 <li>Hetzner Storage Box</li>
 <li>rsync.net</li>
 </ul>
-<p>SFTP runs over SSH v2 and is installed as standard with most modern SSH installations.</p>
-<p>Paths are specified as <code>remote:path</code>. If the path does not begin with a <code>/</code> it is relative to the home directory of the user. An empty path <code>remote:</code> refers to the user's home directory. For example, <code>rclone lsd remote:</code> would list the home directory of the user configured in the rclone remote config (<code>i.e /home/sftpuser</code>). However, <code>rclone lsd remote:/</code> would list the root directory for remote machine (i.e. <code>/</code>)</p>
-<p>Note that some SFTP servers will need the leading / - Synology is a good example of this. rsync.net and Hetzner, on the other hand, requires users to OMIT the leading /.</p>
-<p>Note that by default rclone will try to execute shell commands on the server, see <a href="#shell-access-considerations">shell access considerations</a>.</p>
-<h2 id="configuration-45">Configuration</h2>
+<p>SFTP runs over SSH v2 and is installed as standard with most modern
+SSH installations.</p>
+<p>Paths are specified as <code>remote:path</code>. If the path does not
+begin with a <code>/</code> it is relative to the home directory of the
+user. An empty path <code>remote:</code> refers to the user's home
+directory. For example, <code>rclone lsd remote:</code> would list the
+home directory of the user configured in the rclone remote config
+(<code>i.e /home/sftpuser</code>). However,
+<code>rclone lsd remote:/</code> would list the root directory for
+remote machine (i.e. <code>/</code>)</p>
+<p>Note that some SFTP servers will need the leading / - Synology is a
+good example of this. rsync.net and Hetzner, on the other hand, requires
+users to OMIT the leading /.</p>
+<p>Note that by default rclone will try to execute shell commands on the
+server, see <a href="#shell-access-considerations">shell access
+considerations</a>.</p>
+<h2 id="configuration-46">Configuration</h2>
 <p>Here is an example of making an SFTP configuration. First run</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process.</p>
@@ -33675,7 +48114,8 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>This remote is called <code>remote</code> and can now be used like this:</p>
+<p>This remote is called <code>remote</code> and can now be used like
+this:</p>
 <p>See all directories in the home directory</p>
 <pre><code>rclone lsd remote:</code></pre>
 <p>See all directories in the root directory</p>
@@ -33684,9 +48124,11 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone mkdir remote:path/to/directory</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls remote:path/to/directory</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote directory, deleting any excess files in the directory.</p>
+<p>Sync <code>/home/local/directory</code> to the remote directory,
+deleting any excess files in the directory.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:directory</code></pre>
-<p>Mount the remote path <code>/srv/www-data/</code> to the local path <code>/mnt/www-data</code></p>
+<p>Mount the remote path <code>/srv/www-data/</code> to the local path
+<code>/mnt/www-data</code></p>
 <pre><code>rclone mount remote:/srv/www-data/ /mnt/www-data</code></pre>
 <h3 id="ssh-authentication">SSH Authentication</h3>
 <p>The SFTP remote supports three authentication methods:</p>
@@ -33695,18 +48137,39 @@ y/e/d&gt; y</code></pre>
 <li>Key file, including certificate signed keys</li>
 <li>ssh-agent</li>
 </ul>
-<p>Key files should be PEM-encoded private key files. For instance <code>/home/$USER/.ssh/id_rsa</code>. Only unencrypted OpenSSH or PEM encrypted files are supported.</p>
-<p>The key file can be specified in either an external file (key_file) or contained within the rclone config file (key_pem). If using key_pem in the config file, the entry should be on a single line with new line ('' or '') separating lines. i.e.</p>
+<p>Key files should be PEM-encoded private key files. For instance
+<code>/home/$USER/.ssh/id_rsa</code>. Only unencrypted OpenSSH or PEM
+encrypted files are supported.</p>
+<p>The key file can be specified in either an external file (key_file)
+or contained within the rclone config file (key_pem). If using key_pem
+in the config file, the entry should be on a single line with new line
+('' or '') separating lines. i.e.</p>
 <pre><code>key_pem = -----BEGIN RSA PRIVATE KEY-----\nMaMbaIXtE\n0gAMbMbaSsd\nMbaass\n-----END RSA PRIVATE KEY-----</code></pre>
-<p>This will generate it correctly for key_pem for use in the config:</p>
+<p>This will generate it correctly for key_pem for use in the
+config:</p>
 <pre><code>awk &#39;{printf &quot;%s\\n&quot;, $0}&#39; &lt; ~/.ssh/id_rsa</code></pre>
-<p>If you don't specify <code>pass</code>, <code>key_file</code>, or <code>key_pem</code> or <code>ask_password</code> then rclone will attempt to contact an ssh-agent. You can also specify <code>key_use_agent</code> to force the usage of an ssh-agent. In this case <code>key_file</code> or <code>key_pem</code> can also be specified to force the usage of a specific key in the ssh-agent.</p>
-<p>Using an ssh-agent is the only way to load encrypted OpenSSH keys at the moment.</p>
-<p>If you set the <code>ask_password</code> option, rclone will prompt for a password when needed and no password has been configured.</p>
+<p>If you don't specify <code>pass</code>, <code>key_file</code>, or
+<code>key_pem</code> or <code>ask_password</code> then rclone will
+attempt to contact an ssh-agent. You can also specify
+<code>key_use_agent</code> to force the usage of an ssh-agent. In this
+case <code>key_file</code> or <code>key_pem</code> can also be specified
+to force the usage of a specific key in the ssh-agent.</p>
+<p>Using an ssh-agent is the only way to load encrypted OpenSSH keys at
+the moment.</p>
+<p>If you set the <code>ask_password</code> option, rclone will prompt
+for a password when needed and no password has been configured.</p>
 <h4 id="certificate-signed-keys">Certificate-signed keys</h4>
-<p>With traditional key-based authentication, you configure your private key only, and the public key built into it will be used during the authentication process.</p>
-<p>If you have a certificate you may use it to sign your public key, creating a separate SSH user certificate that should be used instead of the plain public key extracted from the private key. Then you must provide the path to the user certificate public key file in <code>pubkey_file</code>.</p>
-<p>Note: This is not the traditional public key paired with your private key, typically saved as <code>/home/$USER/.ssh/id_rsa.pub</code>. Setting this path in <code>pubkey_file</code> will not work.</p>
+<p>With traditional key-based authentication, you configure your private
+key only, and the public key built into it will be used during the
+authentication process.</p>
+<p>If you have a certificate you may use it to sign your public key,
+creating a separate SSH user certificate that should be used instead of
+the plain public key extracted from the private key. Then you must
+provide the path to the user certificate public key file in
+<code>pubkey_file</code>.</p>
+<p>Note: This is not the traditional public key paired with your private
+key, typically saved as <code>/home/$USER/.ssh/id_rsa.pub</code>.
+Setting this path in <code>pubkey_file</code> will not work.</p>
 <p>Example:</p>
 <pre><code>[remote]
 type = sftp
@@ -33714,12 +48177,19 @@ host = example.com
 user = sftpuser
 key_file = ~/id_rsa
 pubkey_file = ~/id_rsa-cert.pub</code></pre>
-<p>If you concatenate a cert with a private key then you can specify the merged file in both places.</p>
+<p>If you concatenate a cert with a private key then you can specify the
+merged file in both places.</p>
 <p>Note: the cert must come first in the file. e.g.</p>
 <pre><code>cat id_rsa-cert.pub id_rsa &gt; merged_key</code></pre>
 <h3 id="host-key-validation">Host key validation</h3>
-<p>By default rclone will not check the server's host key for validation. This can allow an attacker to replace a server with their own and if you use password authentication then this can lead to that password being exposed.</p>
-<p>Host key matching, using standard <code>known_hosts</code> files can be turned on by enabling the <code>known_hosts_file</code> option. This can point to the file maintained by <code>OpenSSH</code> or can point to a unique file.</p>
+<p>By default rclone will not check the server's host key for
+validation. This can allow an attacker to replace a server with their
+own and if you use password authentication then this can lead to that
+password being exposed.</p>
+<p>Host key matching, using standard <code>known_hosts</code> files can
+be turned on by enabling the <code>known_hosts_file</code> option. This
+can point to the file maintained by <code>OpenSSH</code> or can point to
+a unique file.</p>
 <p>e.g. using the OpenSSH <code>known_hosts</code> file:</p>
 <pre><code>[remote]
 type = sftp
@@ -33731,46 +48201,167 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 <pre><code>ssh-keyscan -t dsa,rsa,ecdsa,ed25519 example.com &gt;&gt; known_hosts</code></pre>
 <p>There are some limitations:</p>
 <ul>
-<li><code>rclone</code> will not <em>manage</em> this file for you. If the key is missing or wrong then the connection will be refused.</li>
-<li>If the server is set up for a certificate host key then the entry in the <code>known_hosts</code> file <em>must</em> be the <code>@cert-authority</code> entry for the CA</li>
+<li><code>rclone</code> will not <em>manage</em> this file for you. If
+the key is missing or wrong then the connection will be refused.</li>
+<li>If the server is set up for a certificate host key then the entry in
+the <code>known_hosts</code> file <em>must</em> be the
+<code>@cert-authority</code> entry for the CA</li>
 </ul>
-<p>If the host key provided by the server does not match the one in the file (or is missing) then the connection will be aborted and an error returned such as</p>
+<p>If the host key provided by the server does not match the one in the
+file (or is missing) then the connection will be aborted and an error
+returned such as</p>
 <pre><code>NewFs: couldn&#39;t connect SSH: ssh: handshake failed: knownhosts: key mismatch</code></pre>
 <p>or</p>
 <pre><code>NewFs: couldn&#39;t connect SSH: ssh: handshake failed: knownhosts: key is unknown</code></pre>
 <p>If you see an error such as</p>
 <pre><code>NewFs: couldn&#39;t connect SSH: ssh: handshake failed: ssh: no authorities for hostname: example.com:22</code></pre>
-<p>then it is likely the server has presented a CA signed host certificate and you will need to add the appropriate <code>@cert-authority</code> entry.</p>
-<p>The <code>known_hosts_file</code> setting can be set during <code>rclone config</code> as an advanced option.</p>
+<p>then it is likely the server has presented a CA signed host
+certificate and you will need to add the appropriate
+<code>@cert-authority</code> entry.</p>
+<p>The <code>known_hosts_file</code> setting can be set during
+<code>rclone config</code> as an advanced option.</p>
 <h3 id="ssh-agent-on-macos">ssh-agent on macOS</h3>
-<p>Note that there seem to be various problems with using an ssh-agent on macOS due to recent changes in the OS. The most effective work-around seems to be to start an ssh-agent in each session, e.g.</p>
+<p>Note that there seem to be various problems with using an ssh-agent
+on macOS due to recent changes in the OS. The most effective work-around
+seems to be to start an ssh-agent in each session, e.g.</p>
 <pre><code>eval `ssh-agent -s` &amp;&amp; ssh-add -A</code></pre>
 <p>And then at the end of the session</p>
 <pre><code>eval `ssh-agent -k`</code></pre>
 <p>These commands can be used in scripts of course.</p>
 <h3 id="shell-access">Shell access</h3>
-<p>Some functionality of the SFTP backend relies on remote shell access, and the possibility to execute commands. This includes <a href="#checksum">checksum</a>, and in some cases also <a href="#about-command">about</a>. The shell commands that must be executed may be different on different type of shells, and also quoting/escaping of file path arguments containing special characters may be different. Rclone therefore needs to know what type of shell it is, and if shell access is available at all.</p>
-<p>Most servers run on some version of Unix, and then a basic Unix shell can be assumed, without further distinction. Windows 10, Server 2019, and later can also run a SSH server, which is a port of OpenSSH (see official <a href="https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse">installation guide</a>). On a Windows server the shell handling is different: Although it can also be set up to use a Unix type shell, e.g. Cygwin bash, the default is to use Windows Command Prompt (cmd.exe), and PowerShell is a recommended alternative. All of these have behave differently, which rclone must handle.</p>
-<p>Rclone tries to auto-detect what type of shell is used on the server, first time you access the SFTP remote. If a remote shell session is successfully created, it will look for indications that it is CMD or PowerShell, with fall-back to Unix if not something else is detected. If unable to even create a remote shell session, then shell command execution will be disabled entirely. The result is stored in the SFTP remote configuration, in option <code>shell_type</code>, so that the auto-detection only have to be performed once. If you manually set a value for this option before first run, the auto-detection will be skipped, and if you set a different value later this will override any existing. Value <code>none</code> can be set to avoid any attempts at executing shell commands, e.g. if this is not allowed on the server. If you have <code>shell_type = none</code> in the configuration then the <a href="#sftp-ssh">ssh</a> must not be set.</p>
-<p>When the server is <a href="https://rclone.org/commands/rclone_serve_sftp/">rclone serve sftp</a>, the rclone SFTP remote will detect this as a Unix type shell - even if it is running on Windows. This server does not actually have a shell, but it accepts input commands matching the specific ones that the SFTP backend relies on for Unix shells, e.g. <code>md5sum</code> and <code>df</code>. Also it handles the string escape rules used for Unix shell. Treating it as a Unix type shell from a SFTP remote will therefore always be correct, and support all features.</p>
+<p>Some functionality of the SFTP backend relies on remote shell access,
+and the possibility to execute commands. This includes <a
+href="#checksum">checksum</a>, and in some cases also <a
+href="#about-command">about</a>. The shell commands that must be
+executed may be different on different type of shells, and also
+quoting/escaping of file path arguments containing special characters
+may be different. Rclone therefore needs to know what type of shell it
+is, and if shell access is available at all.</p>
+<p>Most servers run on some version of Unix, and then a basic Unix shell
+can be assumed, without further distinction. Windows 10, Server 2019,
+and later can also run a SSH server, which is a port of OpenSSH (see
+official <a
+href="https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse">installation
+guide</a>). On a Windows server the shell handling is different:
+Although it can also be set up to use a Unix type shell, e.g. Cygwin
+bash, the default is to use Windows Command Prompt (cmd.exe), and
+PowerShell is a recommended alternative. All of these have behave
+differently, which rclone must handle.</p>
+<p>Rclone tries to auto-detect what type of shell is used on the server,
+first time you access the SFTP remote. If a remote shell session is
+successfully created, it will look for indications that it is CMD or
+PowerShell, with fall-back to Unix if not something else is detected. If
+unable to even create a remote shell session, then shell command
+execution will be disabled entirely. The result is stored in the SFTP
+remote configuration, in option <code>shell_type</code>, so that the
+auto-detection only have to be performed once. If you manually set a
+value for this option before first run, the auto-detection will be
+skipped, and if you set a different value later this will override any
+existing. Value <code>none</code> can be set to avoid any attempts at
+executing shell commands, e.g. if this is not allowed on the server. If
+you have <code>shell_type = none</code> in the configuration then the <a
+href="#sftp-ssh">ssh</a> must not be set.</p>
+<p>When the server is <a
+href="https://rclone.org/commands/rclone_serve_sftp/">rclone serve
+sftp</a>, the rclone SFTP remote will detect this as a Unix type shell -
+even if it is running on Windows. This server does not actually have a
+shell, but it accepts input commands matching the specific ones that the
+SFTP backend relies on for Unix shells, e.g. <code>md5sum</code> and
+<code>df</code>. Also it handles the string escape rules used for Unix
+shell. Treating it as a Unix type shell from a SFTP remote will
+therefore always be correct, and support all features.</p>
 <h4 id="shell-access-considerations">Shell access considerations</h4>
-<p>The shell type auto-detection logic, described above, means that by default rclone will try to run a shell command the first time a new sftp remote is accessed. If you configure a sftp remote without a config file, e.g. an <a href="https://rclone.org/docs/#backend-path-to-dir%5D">on the fly</a> remote, rclone will have nowhere to store the result, and it will re-run the command on every access. To avoid this you should explicitly set the <code>shell_type</code> option to the correct value, or to <code>none</code> if you want to prevent rclone from executing any remote shell commands.</p>
-<p>It is also important to note that, since the shell type decides how quoting and escaping of file paths used as command-line arguments are performed, configuring the wrong shell type may leave you exposed to command injection exploits. Make sure to confirm the auto-detected shell type, or explicitly set the shell type you know is correct, or disable shell access until you know.</p>
+<p>The shell type auto-detection logic, described above, means that by
+default rclone will try to run a shell command the first time a new sftp
+remote is accessed. If you configure a sftp remote without a config
+file, e.g. an <a
+href="https://rclone.org/docs/#backend-path-to-dir%5D">on the fly</a>
+remote, rclone will have nowhere to store the result, and it will re-run
+the command on every access. To avoid this you should explicitly set the
+<code>shell_type</code> option to the correct value, or to
+<code>none</code> if you want to prevent rclone from executing any
+remote shell commands.</p>
+<p>It is also important to note that, since the shell type decides how
+quoting and escaping of file paths used as command-line arguments are
+performed, configuring the wrong shell type may leave you exposed to
+command injection exploits. Make sure to confirm the auto-detected shell
+type, or explicitly set the shell type you know is correct, or disable
+shell access until you know.</p>
 <h3 id="checksum-2">Checksum</h3>
-<p>SFTP does not natively support checksums (file hash), but rclone is able to use checksumming if the same login has shell access, and can execute remote commands. If there is a command that can calculate compatible checksums on the remote system, Rclone can then be configured to execute this whenever a checksum is needed, and read back the results. Currently MD5 and SHA-1 are supported.</p>
-<p>Normally this requires an external utility being available on the server. By default rclone will try commands <code>md5sum</code>, <code>md5</code> and <code>rclone md5sum</code> for MD5 checksums, and the first one found usable will be picked. Same with <code>sha1sum</code>, <code>sha1</code> and <code>rclone sha1sum</code> commands for SHA-1 checksums. These utilities normally need to be in the remote's PATH to be found.</p>
-<p>In some cases the shell itself is capable of calculating checksums. PowerShell is an example of such a shell. If rclone detects that the remote shell is PowerShell, which means it most probably is a Windows OpenSSH server, rclone will use a predefined script block to produce the checksums when no external checksum commands are found (see <a href="#shell-access">shell access</a>). This assumes PowerShell version 4.0 or newer.</p>
-<p>The options <code>md5sum_command</code> and <code>sha1_command</code> can be used to customize the command to be executed for calculation of checksums. You can for example set a specific path to where md5sum and sha1sum executables are located, or use them to specify some other tools that print checksums in compatible format. The value can include command-line arguments, or even shell script blocks as with PowerShell. Rclone has subcommands <a href="https://rclone.org/commands/rclone_md5sum/">md5sum</a> and <a href="https://rclone.org/commands/rclone_sha1sum/">sha1sum</a> that use compatible format, which means if you have an rclone executable on the server it can be used. As mentioned above, they will be automatically picked up if found in PATH, but if not you can set something like <code>/path/to/rclone md5sum</code> as the value of option <code>md5sum_command</code> to make sure a specific executable is used.</p>
-<p>Remote checksumming is recommended and enabled by default. First time rclone is using a SFTP remote, if options <code>md5sum_command</code> or <code>sha1_command</code> are not set, it will check if any of the default commands for each of them, as described above, can be used. The result will be saved in the remote configuration, so next time it will use the same. Value <code>none</code> will be set if none of the default commands could be used for a specific algorithm, and this algorithm will not be supported by the remote.</p>
-<p>Disabling the checksumming may be required if you are connecting to SFTP servers which are not under your control, and to which the execution of remote shell commands is prohibited. Set the configuration option <code>disable_hashcheck</code> to <code>true</code> to disable checksumming entirely, or set <code>shell_type</code> to <code>none</code> to disable all functionality based on remote shell command execution.</p>
-<h3 id="modification-times-and-hashes-25">Modification times and hashes</h3>
+<p>SFTP does not natively support checksums (file hash), but rclone is
+able to use checksumming if the same login has shell access, and can
+execute remote commands. If there is a command that can calculate
+compatible checksums on the remote system, Rclone can then be configured
+to execute this whenever a checksum is needed, and read back the
+results. Currently MD5 and SHA-1 are supported.</p>
+<p>Normally this requires an external utility being available on the
+server. By default rclone will try commands <code>md5sum</code>,
+<code>md5</code> and <code>rclone md5sum</code> for MD5 checksums, and
+the first one found usable will be picked. Same with
+<code>sha1sum</code>, <code>sha1</code> and <code>rclone sha1sum</code>
+commands for SHA-1 checksums. These utilities normally need to be in the
+remote's PATH to be found.</p>
+<p>In some cases the shell itself is capable of calculating checksums.
+PowerShell is an example of such a shell. If rclone detects that the
+remote shell is PowerShell, which means it most probably is a Windows
+OpenSSH server, rclone will use a predefined script block to produce the
+checksums when no external checksum commands are found (see <a
+href="#shell-access">shell access</a>). This assumes PowerShell version
+4.0 or newer.</p>
+<p>The options <code>md5sum_command</code> and <code>sha1_command</code>
+can be used to customize the command to be executed for calculation of
+checksums. You can for example set a specific path to where md5sum and
+sha1sum executables are located, or use them to specify some other tools
+that print checksums in compatible format. The value can include
+command-line arguments, or even shell script blocks as with PowerShell.
+Rclone has subcommands <a
+href="https://rclone.org/commands/rclone_md5sum/">md5sum</a> and <a
+href="https://rclone.org/commands/rclone_sha1sum/">sha1sum</a> that use
+compatible format, which means if you have an rclone executable on the
+server it can be used. As mentioned above, they will be automatically
+picked up if found in PATH, but if not you can set something like
+<code>/path/to/rclone md5sum</code> as the value of option
+<code>md5sum_command</code> to make sure a specific executable is
+used.</p>
+<p>Remote checksumming is recommended and enabled by default. First time
+rclone is using a SFTP remote, if options <code>md5sum_command</code> or
+<code>sha1_command</code> are not set, it will check if any of the
+default commands for each of them, as described above, can be used. The
+result will be saved in the remote configuration, so next time it will
+use the same. Value <code>none</code> will be set if none of the default
+commands could be used for a specific algorithm, and this algorithm will
+not be supported by the remote.</p>
+<p>Disabling the checksumming may be required if you are connecting to
+SFTP servers which are not under your control, and to which the
+execution of remote shell commands is prohibited. Set the configuration
+option <code>disable_hashcheck</code> to <code>true</code> to disable
+checksumming entirely, or set <code>shell_type</code> to
+<code>none</code> to disable all functionality based on remote shell
+command execution.</p>
+<h3 id="modification-times-and-hashes-25">Modification times and
+hashes</h3>
 <p>Modified times are stored on the server to 1 second precision.</p>
 <p>Modified times are used in syncing and are fully supported.</p>
-<p>Some SFTP servers disable setting/modifying the file modification time after upload (for example, certain configurations of ProFTPd with mod_sftp). If you are using one of these servers, you can set the option <code>set_modtime = false</code> in your RClone backend configuration to disable this behaviour.</p>
+<p>Some SFTP servers disable setting/modifying the file modification
+time after upload (for example, certain configurations of ProFTPd with
+mod_sftp). If you are using one of these servers, you can set the option
+<code>set_modtime = false</code> in your RClone backend configuration to
+disable this behaviour.</p>
 <h3 id="about-command">About command</h3>
-<p>The <code>about</code> command returns the total space, free space, and used space on the remote for the disk of the specified path on the remote or, if not set, the disk of the root on the remote.</p>
-<p>SFTP usually supports the <a href="https://rclone.org/commands/rclone_about/">about</a> command, but it depends on the server. If the server implements the vendor-specific VFS statistics extension, which is normally the case with OpenSSH instances, it will be used. If not, but the same login has access to a Unix shell, where the <code>df</code> command is available (e.g. in the remote's PATH), then this will be used instead. If the server shell is PowerShell, probably with a Windows OpenSSH server, rclone will use a built-in shell command (see <a href="#shell-access">shell access</a>). If none of the above is applicable, <code>about</code> will fail.</p>
-<h3 id="standard-options-48">Standard options</h3>
+<p>The <code>about</code> command returns the total space, free space,
+and used space on the remote for the disk of the specified path on the
+remote or, if not set, the disk of the root on the remote.</p>
+<p>SFTP usually supports the <a
+href="https://rclone.org/commands/rclone_about/">about</a> command, but
+it depends on the server. If the server implements the vendor-specific
+VFS statistics extension, which is normally the case with OpenSSH
+instances, it will be used. If not, but the same login has access to a
+Unix shell, where the <code>df</code> command is available (e.g. in the
+remote's PATH), then this will be used instead. If the server shell is
+PowerShell, probably with a Windows OpenSSH server, rclone will use a
+built-in shell command (see <a href="#shell-access">shell access</a>).
+If none of the above is applicable, <code>about</code> will fail.</p>
+<h3 id="standard-options-49">Standard options</h3>
 <p>Here are the Standard options specific to sftp (SSH/SFTP).</p>
 <h4 id="sftp-host">--sftp-host</h4>
 <p>SSH host to connect to.</p>
@@ -33802,7 +48393,9 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-pass">--sftp-pass</h4>
 <p>SSH password, leave blank to use ssh-agent.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass</li>
@@ -33812,7 +48405,8 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-key-pem">--sftp-key-pem</h4>
 <p>Raw PEM-encoded private key.</p>
-<p>Note that this should be on a single line with line endings replaced with '', eg</p>
+<p>Note that this should be on a single line with line endings replaced
+with '', eg</p>
 <pre><code>key_pem = -----BEGIN RSA PRIVATE KEY-----\nMaMbaIXtE\n0gAMbMbaSsd\nMbaass\n-----END RSA PRIVATE KEY-----</code></pre>
 <p>This will generate the single line correctly:</p>
 <pre><code>awk &#39;{printf &quot;%s\\n&quot;, $0}&#39; &lt; ~/.ssh/id_rsa</code></pre>
@@ -33827,7 +48421,8 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 <h4 id="sftp-key-file">--sftp-key-file</h4>
 <p>Path to PEM-encoded private key file.</p>
 <p>Leave blank or set key-use-agent to use ssh-agent.</p>
-<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
+<p>Leading <code>~</code> will be expanded in the file name as will
+environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: key_file</li>
@@ -33837,8 +48432,11 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-key-file-pass">--sftp-key-file-pass</h4>
 <p>The passphrase to decrypt the PEM-encoded private key file.</p>
-<p>Only PEM encrypted key files (old OpenSSH format) are supported. Encrypted keys in the new OpenSSH format can't be used.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p>Only PEM encrypted key files (old OpenSSH format) are supported.
+Encrypted keys in the new OpenSSH format can't be used.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: key_file_pass</li>
@@ -33848,8 +48446,10 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-pubkey-file">--sftp-pubkey-file</h4>
 <p>Optional path to public key file.</p>
-<p>Set this if you have a signed certificate you want to use for authentication.</p>
-<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
+<p>Set this if you have a signed certificate you want to use for
+authentication.</p>
+<p>Leading <code>~</code> will be expanded in the file name as will
+environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pubkey_file</li>
@@ -33859,7 +48459,11 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-key-use-agent">--sftp-key-use-agent</h4>
 <p>When set forces the usage of the ssh-agent.</p>
-<p>When key-file is also set, the ".pub" file of the specified key-file is read and only the associated key is requested from the ssh-agent. This allows to avoid <code>Too many authentication failures for *username*</code> errors when the ssh-agent contains many keys.</p>
+<p>When key-file is also set, the ".pub" file of the specified key-file
+is read and only the associated key is requested from the ssh-agent.
+This allows to avoid
+<code>Too many authentication failures for *username*</code> errors when
+the ssh-agent contains many keys.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: key_use_agent</li>
@@ -33869,7 +48473,8 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-use-insecure-cipher">--sftp-use-insecure-cipher</h4>
 <p>Enable the use of insecure ciphers and key exchange methods.</p>
-<p>This enables the use of the following insecure ciphers and key exchange methods:</p>
+<p>This enables the use of the following insecure ciphers and key
+exchange methods:</p>
 <ul>
 <li>aes128-cbc</li>
 <li>aes192-cbc</li>
@@ -33878,8 +48483,10 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 <li>diffie-hellman-group-exchange-sha256</li>
 <li>diffie-hellman-group-exchange-sha1</li>
 </ul>
-<p>Those algorithms are insecure and may allow plaintext data to be recovered by an attacker.</p>
-<p>This must be false if you use either ciphers or key_exchange advanced options.</p>
+<p>Those algorithms are insecure and may allow plaintext data to be
+recovered by an attacker.</p>
+<p>This must be false if you use either ciphers or key_exchange advanced
+options.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_insecure_cipher</li>
@@ -33894,13 +48501,17 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul></li>
 <li>"true"
 <ul>
-<li>Enables the use of the aes128-cbc cipher and diffie-hellman-group-exchange-sha256, diffie-hellman-group-exchange-sha1 key exchange.</li>
+<li>Enables the use of the aes128-cbc cipher and
+diffie-hellman-group-exchange-sha256, diffie-hellman-group-exchange-sha1
+key exchange.</li>
 </ul></li>
 </ul></li>
 </ul>
 <h4 id="sftp-disable-hashcheck">--sftp-disable-hashcheck</h4>
-<p>Disable the execution of SSH commands to determine if remote file hashing is available.</p>
-<p>Leave blank or set to false to enable hashing (recommended), set to true to disable hashing.</p>
+<p>Disable the execution of SSH commands to determine if remote file
+hashing is available.</p>
+<p>Leave blank or set to false to enable hashing (recommended), set to
+true to disable hashing.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_hashcheck</li>
@@ -33910,14 +48521,23 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-ssh">--sftp-ssh</h4>
 <p>Path and arguments to external ssh binary.</p>
-<p>Normally rclone will use its internal ssh library to connect to the SFTP server. However it does not implement all possible ssh options so it may be desirable to use an external ssh binary.</p>
-<p>Rclone ignores all the internal config if you use this option and expects you to configure the ssh binary with the user/host/port and any other options you need.</p>
-<p><strong>Important</strong> The ssh command must log in without asking for a password so needs to be configured with keys or certificates.</p>
-<p>Rclone will run the command supplied either with the additional arguments "-s sftp" to access the SFTP subsystem or with commands such as "md5sum /path/to/file" appended to read checksums.</p>
-<p>Any arguments with spaces in should be surrounded by "double quotes".</p>
+<p>Normally rclone will use its internal ssh library to connect to the
+SFTP server. However it does not implement all possible ssh options so
+it may be desirable to use an external ssh binary.</p>
+<p>Rclone ignores all the internal config if you use this option and
+expects you to configure the ssh binary with the user/host/port and any
+other options you need.</p>
+<p><strong>Important</strong> The ssh command must log in without asking
+for a password so needs to be configured with keys or certificates.</p>
+<p>Rclone will run the command supplied either with the additional
+arguments "-s sftp" to access the SFTP subsystem or with commands such
+as "md5sum /path/to/file" appended to read checksums.</p>
+<p>Any arguments with spaces in should be surrounded by "double
+quotes".</p>
 <p>An example setting might be:</p>
 <pre><code>ssh -o ServerAliveInterval=20 user@example.com</code></pre>
-<p>Note that when using an external ssh binary rclone makes a new ssh connection for every hash it calculates.</p>
+<p>Note that when using an external ssh binary rclone makes a new ssh
+connection for every hash it calculates.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: ssh</li>
@@ -33925,12 +48545,13 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 <li>Type: SpaceSepList</li>
 <li>Default:</li>
 </ul>
-<h3 id="advanced-options-49">Advanced options</h3>
+<h3 id="advanced-options-50">Advanced options</h3>
 <p>Here are the Advanced options specific to sftp (SSH/SFTP).</p>
 <h4 id="sftp-known-hosts-file">--sftp-known-hosts-file</h4>
 <p>Optional path to known_hosts file.</p>
 <p>Set this value to enable server host key validation.</p>
-<p>Leading <code>~</code> will be expanded in the file name as will environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
+<p>Leading <code>~</code> will be expanded in the file name as will
+environment variables such as <code>${RCLONE_CONFIG_DIR}</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: known_hosts_file</li>
@@ -33947,7 +48568,8 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-ask-password">--sftp-ask-password</h4>
 <p>Allow asking for SFTP password when needed.</p>
-<p>If this is set and no password is supplied then rclone will: - ask for a password - not contact the ssh agent</p>
+<p>If this is set and no password is supplied then rclone will: - ask
+for a password - not contact the ssh agent</p>
 <p>Properties:</p>
 <ul>
 <li>Config: ask_password</li>
@@ -33957,15 +48579,22 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 </ul>
 <h4 id="sftp-path-override">--sftp-path-override</h4>
 <p>Override path used by SSH shell commands.</p>
-<p>This allows checksum calculation when SFTP and SSH paths are different. This issue affects among others Synology NAS boxes.</p>
-<p>E.g. if shared folders can be found in directories representing volumes:</p>
+<p>This allows checksum calculation when SFTP and SSH paths are
+different. This issue affects among others Synology NAS boxes.</p>
+<p>E.g. if shared folders can be found in directories representing
+volumes:</p>
 <pre><code>rclone sync /home/local/directory remote:/directory --sftp-path-override /volume2/directory</code></pre>
-<p>E.g. if home directory can be found in a shared folder called "home":</p>
+<p>E.g. if home directory can be found in a shared folder called
+"home":</p>
 <pre><code>rclone sync /home/local/directory remote:/home/directory --sftp-path-override /volume1/homes/USER/directory</code></pre>
-<p>To specify only the path to the SFTP remote's root, and allow rclone to add any relative subpaths automatically (including unwrapping/decrypting remotes as necessary), add the '@' character to the beginning of the path.</p>
+<p>To specify only the path to the SFTP remote's root, and allow rclone
+to add any relative subpaths automatically (including
+unwrapping/decrypting remotes as necessary), add the '@' character to
+the beginning of the path.</p>
 <p>E.g. the first example above could be rewritten as:</p>
 <pre><code>rclone sync /home/local/directory remote:/directory --sftp-path-override @/volume2</code></pre>
-<p>Note that when using this method with Synology "home" folders, the full "/homes/USER" path should be specified instead of "/home".</p>
+<p>Note that when using this method with Synology "home" folders, the
+full "/homes/USER" path should be specified instead of "/home".</p>
 <p>E.g. the second example above should be rewritten as:</p>
 <pre><code>rclone sync /home/local/directory remote:/homes/USER/directory --sftp-path-override @/volume1</code></pre>
 <p>Properties:</p>
@@ -34052,9 +48681,12 @@ known_hosts_file = ~/.ssh/known_hosts</code></pre>
 <li>Default: "sftp"</li>
 </ul>
 <h4 id="sftp-server-command">--sftp-server-command</h4>
-<p>Specifies the path or command to run a sftp server on the remote host.</p>
+<p>Specifies the path or command to run a sftp server on the remote
+host.</p>
 <p>The subsystem option is ignored when server_command is defined.</p>
-<p>If adding server_command to the configuration file please note that it should not be enclosed in quotes, since that will make rclone fail.</p>
+<p>If adding server_command to the configuration file please note that
+it should not be enclosed in quotes, since that will make rclone
+fail.</p>
 <p>A working example is:</p>
 <pre><code>[remote_name]
 type = sftp
@@ -34068,8 +48700,13 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 </ul>
 <h4 id="sftp-use-fstat">--sftp-use-fstat</h4>
 <p>If set use fstat instead of stat.</p>
-<p>Some servers limit the amount of open files and calling Stat after opening the file will throw an error from the server. Setting this flag will call Fstat instead of Stat which is called on an already open file handle.</p>
-<p>It has been found that this helps with IBM Sterling SFTP servers which have "extractability" level set to 1 which means only 1 file can be opened at any given time.</p>
+<p>Some servers limit the amount of open files and calling Stat after
+opening the file will throw an error from the server. Setting this flag
+will call Fstat instead of Stat which is called on an already open file
+handle.</p>
+<p>It has been found that this helps with IBM Sterling SFTP servers
+which have "extractability" level set to 1 which means only 1 file can
+be opened at any given time.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: use_fstat</li>
@@ -34077,13 +48714,18 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="sftp-disable-concurrent-reads">--sftp-disable-concurrent-reads</h4>
+<h4
+id="sftp-disable-concurrent-reads">--sftp-disable-concurrent-reads</h4>
 <p>If set don't use concurrent reads.</p>
-<p>Normally concurrent reads are safe to use and not using them will degrade performance, so this option is disabled by default.</p>
-<p>Some servers limit the amount number of times a file can be downloaded. Using concurrent reads can trigger this limit, so if you have a server which returns</p>
+<p>Normally concurrent reads are safe to use and not using them will
+degrade performance, so this option is disabled by default.</p>
+<p>Some servers limit the amount number of times a file can be
+downloaded. Using concurrent reads can trigger this limit, so if you
+have a server which returns</p>
 <pre><code>Failed to copy: file does not exist</code></pre>
 <p>Then you may need to enable this flag.</p>
-<p>If concurrent reads are disabled, the use_fstat option is ignored.</p>
+<p>If concurrent reads are disabled, the use_fstat option is
+ignored.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: disable_concurrent_reads</li>
@@ -34091,9 +48733,11 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="sftp-disable-concurrent-writes">--sftp-disable-concurrent-writes</h4>
+<h4
+id="sftp-disable-concurrent-writes">--sftp-disable-concurrent-writes</h4>
 <p>If set don't use concurrent writes.</p>
-<p>Normally rclone uses concurrent writes to upload files. This improves the performance greatly, especially for distant servers.</p>
+<p>Normally rclone uses concurrent writes to upload files. This improves
+the performance greatly, especially for distant servers.</p>
 <p>This option disables concurrent writes should that be necessary.</p>
 <p>Properties:</p>
 <ul>
@@ -34104,7 +48748,8 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 </ul>
 <h4 id="sftp-idle-timeout">--sftp-idle-timeout</h4>
 <p>Max time before closing idle connections.</p>
-<p>If no connections have been returned to the connection pool in the time given, rclone will empty the connection pool.</p>
+<p>If no connections have been returned to the connection pool in the
+time given, rclone will empty the connection pool.</p>
 <p>Set to 0 to keep connections indefinitely.</p>
 <p>Properties:</p>
 <ul>
@@ -34115,8 +48760,23 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 </ul>
 <h4 id="sftp-chunk-size">--sftp-chunk-size</h4>
 <p>Upload and download chunk size.</p>
-<p>This controls the maximum size of payload in SFTP protocol packets. The RFC limits this to 32768 bytes (32k), which is the default. However, a lot of servers support larger sizes, typically limited to a maximum total package size of 256k, and setting it larger will increase transfer speed dramatically on high latency links. This includes OpenSSH, and, for example, using the value of 255k works well, leaving plenty of room for overhead while still being within a total packet size of 256k.</p>
-<p>Make sure to test thoroughly before using a value higher than 32k, and only use it if you always connect to the same server or after sufficiently broad testing. If you get errors such as "failed to send packet payload: EOF", lots of "connection lost", or "corrupted on transfer", when copying a larger file, try lowering the value. The server run by <a href="/commands/rclone_serve_sftp">rclone serve sftp</a> sends packets with standard 32k maximum payload so you must not set a different chunk_size when downloading files, but it accepts packets up to the 256k total size, so for uploads the chunk_size can be set as for the OpenSSH example above.</p>
+<p>This controls the maximum size of payload in SFTP protocol packets.
+The RFC limits this to 32768 bytes (32k), which is the default. However,
+a lot of servers support larger sizes, typically limited to a maximum
+total package size of 256k, and setting it larger will increase transfer
+speed dramatically on high latency links. This includes OpenSSH, and,
+for example, using the value of 255k works well, leaving plenty of room
+for overhead while still being within a total packet size of 256k.</p>
+<p>Make sure to test thoroughly before using a value higher than 32k,
+and only use it if you always connect to the same server or after
+sufficiently broad testing. If you get errors such as "failed to send
+packet payload: EOF", lots of "connection lost", or "corrupted on
+transfer", when copying a larger file, try lowering the value. The
+server run by <a href="/commands/rclone_serve_sftp">rclone serve
+sftp</a> sends packets with standard 32k maximum payload so you must not
+set a different chunk_size when downloading files, but it accepts
+packets up to the 256k total size, so for uploads the chunk_size can be
+set as for the OpenSSH example above.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: chunk_size</li>
@@ -34126,7 +48786,9 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 </ul>
 <h4 id="sftp-concurrency">--sftp-concurrency</h4>
 <p>The maximum number of outstanding requests for one file</p>
-<p>This controls the maximum number of outstanding requests for one file. Increasing it will increase throughput on high latency links at the cost of using more memory.</p>
+<p>This controls the maximum number of outstanding requests for one
+file. Increasing it will increase throughput on high latency links at
+the cost of using more memory.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: concurrency</li>
@@ -34136,10 +48798,17 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 </ul>
 <h4 id="sftp-connections">--sftp-connections</h4>
 <p>Maximum number of SFTP simultaneous connections, 0 for unlimited.</p>
-<p>Note that setting this is very likely to cause deadlocks so it should be used with care.</p>
-<p>If you are doing a sync or copy then make sure connections is one more than the sum of <code>--transfers</code> and <code>--checkers</code>.</p>
-<p>If you use <code>--check-first</code> then it just needs to be one more than the maximum of <code>--checkers</code> and <code>--transfers</code>.</p>
-<p>So for <code>connections 3</code> you'd use <code>--checkers 2 --transfers 2 --check-first</code> or <code>--checkers 1 --transfers 1</code>.</p>
+<p>Note that setting this is very likely to cause deadlocks so it should
+be used with care.</p>
+<p>If you are doing a sync or copy then make sure connections is one
+more than the sum of <code>--transfers</code> and
+<code>--checkers</code>.</p>
+<p>If you use <code>--check-first</code> then it just needs to be one
+more than the maximum of <code>--checkers</code> and
+<code>--transfers</code>.</p>
+<p>So for <code>connections 3</code> you'd use
+<code>--checkers 2 --transfers 2 --check-first</code> or
+<code>--checkers 1 --transfers 1</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: connections</li>
@@ -34151,7 +48820,8 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 <p>Environment variables to pass to sftp and commands</p>
 <p>Set environment variables in the form:</p>
 <pre><code>VAR=value</code></pre>
-<p>to be passed to the sftp client and to any commands run (eg md5sum).</p>
+<p>to be passed to the sftp client and to any commands run (eg
+md5sum).</p>
 <p>Pass multiple variables space separated, eg</p>
 <pre><code>VAR1=value VAR2=value</code></pre>
 <p>and pass variables with spaces in quotes, eg</p>
@@ -34164,8 +48834,10 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 <li>Default:</li>
 </ul>
 <h4 id="sftp-ciphers">--sftp-ciphers</h4>
-<p>Space separated list of ciphers to be used for session encryption, ordered by preference.</p>
-<p>At least one must match with server configuration. This can be checked for example using ssh -Q cipher.</p>
+<p>Space separated list of ciphers to be used for session encryption,
+ordered by preference.</p>
+<p>At least one must match with server configuration. This can be
+checked for example using ssh -Q cipher.</p>
 <p>This must not be set if use_insecure_cipher is true.</p>
 <p>Example:</p>
 <pre><code>aes128-ctr aes192-ctr aes256-ctr aes128-gcm@openssh.com aes256-gcm@openssh.com</code></pre>
@@ -34177,8 +48849,10 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 <li>Default:</li>
 </ul>
 <h4 id="sftp-key-exchange">--sftp-key-exchange</h4>
-<p>Space separated list of key exchange algorithms, ordered by preference.</p>
-<p>At least one must match with server configuration. This can be checked for example using ssh -Q kex.</p>
+<p>Space separated list of key exchange algorithms, ordered by
+preference.</p>
+<p>At least one must match with server configuration. This can be
+checked for example using ssh -Q kex.</p>
 <p>This must not be set if use_insecure_cipher is true.</p>
 <p>Example:</p>
 <pre><code>sntrup761x25519-sha512@openssh.com curve25519-sha256 curve25519-sha256@libssh.org ecdh-sha2-nistp256</code></pre>
@@ -34190,8 +48864,10 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 <li>Default:</li>
 </ul>
 <h4 id="sftp-macs">--sftp-macs</h4>
-<p>Space separated list of MACs (message authentication code) algorithms, ordered by preference.</p>
-<p>At least one must match with server configuration. This can be checked for example using ssh -Q mac.</p>
+<p>Space separated list of MACs (message authentication code)
+algorithms, ordered by preference.</p>
+<p>At least one must match with server configuration. This can be
+checked for example using ssh -Q mac.</p>
 <p>Example:</p>
 <pre><code>umac-64-etm@openssh.com umac-128-etm@openssh.com hmac-sha2-256-etm@openssh.com</code></pre>
 <p>Properties:</p>
@@ -34202,9 +48878,12 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 <li>Default:</li>
 </ul>
 <h4 id="sftp-host-key-algorithms">--sftp-host-key-algorithms</h4>
-<p>Space separated list of host key algorithms, ordered by preference.</p>
-<p>At least one must match with server configuration. This can be checked for example using ssh -Q HostKeyAlgorithms.</p>
-<p>Note: This can affect the outcome of key negotiation with the server even if server host key validation is not enabled.</p>
+<p>Space separated list of host key algorithms, ordered by
+preference.</p>
+<p>At least one must match with server configuration. This can be
+checked for example using ssh -Q HostKeyAlgorithms.</p>
+<p>Note: This can affect the outcome of key negotiation with the server
+even if server host key validation is not enabled.</p>
 <p>Example:</p>
 <pre><code>ssh-ed25519 ssh-rsa ssh-dss</code></pre>
 <p>Properties:</p>
@@ -34216,7 +48895,8 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 </ul>
 <h4 id="sftp-socks-proxy">--sftp-socks-proxy</h4>
 <p>Socks 5 proxy host.</p>
-<p>Supports the format user:pass@host:port, user@host:port, host:port.</p>
+<p>Supports the format user:pass@host:port, user@host:port,
+host:port.</p>
 <p>Example:</p>
 <pre><code>myUser:myPass@localhost:9005</code></pre>
 <p>Properties:</p>
@@ -34228,10 +48908,15 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 </ul>
 <h4 id="sftp-copy-is-hardlink">--sftp-copy-is-hardlink</h4>
 <p>Set to enable server side copies using hardlinks.</p>
-<p>The SFTP protocol does not define a copy command so normally server side copies are not allowed with the sftp backend.</p>
-<p>However the SFTP protocol does support hardlinking, and if you enable this flag then the sftp backend will support server side copies. These will be implemented by doing a hardlink from the source to the destination.</p>
+<p>The SFTP protocol does not define a copy command so normally server
+side copies are not allowed with the sftp backend.</p>
+<p>However the SFTP protocol does support hardlinking, and if you enable
+this flag then the sftp backend will support server side copies. These
+will be implemented by doing a hardlink from the source to the
+destination.</p>
 <p>Not all sftp servers support this.</p>
-<p>Note that hardlinking two files together will use no additional space as the source and the destination will be the same file.</p>
+<p>Note that hardlinking two files together will use no additional space
+as the source and the destination will be the same file.</p>
 <p>This feature may be useful backups made with --copy-dest.</p>
 <p>Properties:</p>
 <ul>
@@ -34250,27 +48935,60 @@ server_command = sudo /usr/libexec/openssh/sftp-server</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-36">Limitations</h2>
-<p>On some SFTP servers (e.g. Synology) the paths are different for SSH and SFTP so the hashes can't be calculated properly. For them using <code>disable_hashcheck</code> is a good idea.</p>
+<p>On some SFTP servers (e.g. Synology) the paths are different for SSH
+and SFTP so the hashes can't be calculated properly. For them using
+<code>disable_hashcheck</code> is a good idea.</p>
 <p>The only ssh agent supported under Windows is Putty's pageant.</p>
-<p>The Go SSH library disables the use of the aes128-cbc cipher by default, due to security concerns. This can be re-enabled on a per-connection basis by setting the <code>use_insecure_cipher</code> setting in the configuration file to <code>true</code>. Further details on the insecurity of this cipher can be found <a href="http://www.isg.rhul.ac.uk/~kp/SandPfinal.pdf">in this paper</a>.</p>
-<p>SFTP isn't supported under plan9 until <a href="https://github.com/pkg/sftp/issues/156">this issue</a> is fixed.</p>
-<p>Note that since SFTP isn't HTTP based the following flags don't work with it: <code>--dump-headers</code>, <code>--dump-bodies</code>, <code>--dump-auth</code>.</p>
-<p>Note that <code>--timeout</code> and <code>--contimeout</code> are both supported.</p>
+<p>The Go SSH library disables the use of the aes128-cbc cipher by
+default, due to security concerns. This can be re-enabled on a
+per-connection basis by setting the <code>use_insecure_cipher</code>
+setting in the configuration file to <code>true</code>. Further details
+on the insecurity of this cipher can be found <a
+href="http://www.isg.rhul.ac.uk/~kp/SandPfinal.pdf">in this
+paper</a>.</p>
+<p>SFTP isn't supported under plan9 until <a
+href="https://github.com/pkg/sftp/issues/156">this issue</a> is
+fixed.</p>
+<p>Note that since SFTP isn't HTTP based the following flags don't work
+with it: <code>--dump-headers</code>, <code>--dump-bodies</code>,
+<code>--dump-auth</code>.</p>
+<p>Note that <code>--timeout</code> and <code>--contimeout</code> are
+both supported.</p>
 <h2 id="rsync-net">rsync.net</h2>
 <p>rsync.net is supported through the SFTP backend.</p>
-<p>See <a href="https://www.rsync.net/products/rclone.html">rsync.net's documentation of rclone examples</a>.</p>
+<p>See <a href="https://www.rsync.net/products/rclone.html">rsync.net's
+documentation of rclone examples</a>.</p>
 <h2 id="hetzner-storage-box">Hetzner Storage Box</h2>
-<p>Hetzner Storage Boxes are supported through the SFTP backend on port 23.</p>
-<p>See <a href="https://docs.hetzner.com/robot/storage-box/access/access-ssh-rsync-borg#rclone">Hetzner's documentation for details</a></p>
+<p>Hetzner Storage Boxes are supported through the SFTP backend on port
+23.</p>
+<p>See <a
+href="https://docs.hetzner.com/robot/storage-box/access/access-ssh-rsync-borg#rclone">Hetzner's
+documentation for details</a></p>
 <h1 id="smb">SMB</h1>
-<p>SMB is <a href="https://en.wikipedia.org/wiki/Server_Message_Block">a communication protocol to share files over network</a>.</p>
-<p>This relies on <a href="https://github.com/hirochachacha/go-smb2/">go-smb2 library</a> for communication with SMB protocol.</p>
-<p>Paths are specified as <code>remote:sharename</code> (or <code>remote:</code> for the <code>lsd</code> command.) You may put subdirectories in too, e.g. <code>remote:item/path/to/dir</code>.</p>
+<p>SMB is <a href="https://en.wikipedia.org/wiki/Server_Message_Block">a
+communication protocol to share files over network</a>.</p>
+<p>This relies on <a
+href="https://github.com/hirochachacha/go-smb2/">go-smb2 library</a> for
+communication with SMB protocol.</p>
+<p>Paths are specified as <code>remote:sharename</code> (or
+<code>remote:</code> for the <code>lsd</code> command.) You may put
+subdirectories in too, e.g. <code>remote:item/path/to/dir</code>.</p>
 <h2 id="notes-1">Notes</h2>
-<p>The first path segment must be the name of the share, which you entered when you started to share on Windows. On smbd, it's the section title in <code>smb.conf</code> (usually in <code>/etc/samba/</code>) file. You can find shares by querying the root if you're unsure (e.g. <code>rclone lsd remote:</code>).</p>
+<p>The first path segment must be the name of the share, which you
+entered when you started to share on Windows. On smbd, it's the section
+title in <code>smb.conf</code> (usually in <code>/etc/samba/</code>)
+file. You can find shares by querying the root if you're unsure (e.g.
+<code>rclone lsd remote:</code>).</p>
 <p>You can't access to the shared printers from rclone, obviously.</p>
-<p>You can't use Anonymous access for logging in. You have to use the <code>guest</code> user with an empty password instead. The rclone client tries to avoid 8.3 names when uploading files by encoding trailing spaces and periods. Alternatively, <a href="https://rclone.org/local/#paths-on-windows">the local backend</a> on Windows can access SMB servers using UNC paths, by <code>\\server\share</code>. This doesn't apply to non-Windows OSes, such as Linux and macOS.</p>
-<h2 id="configuration-46">Configuration</h2>
+<p>You can't use Anonymous access for logging in. You have to use the
+<code>guest</code> user with an empty password instead. The rclone
+client tries to avoid 8.3 names when uploading files by encoding
+trailing spaces and periods. Alternatively, <a
+href="https://rclone.org/local/#paths-on-windows">the local backend</a>
+on Windows can access SMB servers using UNC paths, by
+<code>\\server\share</code>. This doesn't apply to non-Windows OSes,
+such as Linux and macOS.</p>
+<h2 id="configuration-47">Configuration</h2>
 <p>Here is an example of making a SMB configuration.</p>
 <p>First run</p>
 <pre><code>rclone config</code></pre>
@@ -34345,7 +49063,7 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; d</code></pre>
-<h3 id="standard-options-49">Standard options</h3>
+<h3 id="standard-options-50">Standard options</h3>
 <p>Here are the Standard options specific to smb (SMB / CIFS).</p>
 <h4 id="smb-host">--smb-host</h4>
 <p>SMB server hostname to connect to.</p>
@@ -34377,7 +49095,9 @@ y/e/d&gt; d</code></pre>
 </ul>
 <h4 id="smb-pass">--smb-pass</h4>
 <p>SMB password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass</li>
@@ -34396,7 +49116,9 @@ y/e/d&gt; d</code></pre>
 </ul>
 <h4 id="smb-spn">--smb-spn</h4>
 <p>Service principal name.</p>
-<p>Rclone presents this name to the server. Some servers use this as further authentication, and it often needs to be set for clusters. For example:</p>
+<p>Rclone presents this name to the server. Some servers use this as
+further authentication, and it often needs to be set for clusters. For
+example:</p>
 <pre><code>cifs/remotehost:1020</code></pre>
 <p>Leave blank if not sure.</p>
 <p>Properties:</p>
@@ -34406,11 +49128,12 @@ y/e/d&gt; d</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-50">Advanced options</h3>
+<h3 id="advanced-options-51">Advanced options</h3>
 <p>Here are the Advanced options specific to smb (SMB / CIFS).</p>
 <h4 id="smb-idle-timeout">--smb-idle-timeout</h4>
 <p>Max time before closing idle connections.</p>
-<p>If no connections have been returned to the connection pool in the time given, rclone will empty the connection pool.</p>
+<p>If no connections have been returned to the connection pool in the
+time given, rclone will empty the connection pool.</p>
 <p>Set to 0 to keep connections indefinitely.</p>
 <p>Properties:</p>
 <ul>
@@ -34420,7 +49143,8 @@ y/e/d&gt; d</code></pre>
 <li>Default: 1m0s</li>
 </ul>
 <h4 id="smb-hide-special-share">--smb-hide-special-share</h4>
-<p>Hide special shares (e.g. print$) which users aren't supposed to access.</p>
+<p>Hide special shares (e.g. print$) which users aren't supposed to
+access.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: hide_special_share</li>
@@ -34440,13 +49164,15 @@ y/e/d&gt; d</code></pre>
 </ul>
 <h4 id="smb-encoding">--smb-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_SMB_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,RightPeriod,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="smb-description">--smb-description</h4>
 <p>Description of the remote.</p>
@@ -34458,68 +49184,132 @@ y/e/d&gt; d</code></pre>
 <li>Required: false</li>
 </ul>
 <h1 id="storj-1">Storj</h1>
-<p><a href="https://storj.io">Storj</a> is redefining the cloud to support the future of data—sustainably and economically. Storj leverages the vast global supply of underutilized resources to deliver better security, durability, and performance services. Experience up to 90% lower costs and carbon reduction with Storj.</p>
-<p>Storj is an encrypted, secure, and cost-effective object storage service that enables you to store, back up, and archive large amounts of data in a decentralized manner.</p>
+<p><a href="https://storj.io">Storj</a> is redefining the cloud to
+support the future of data—sustainably and economically. Storj leverages
+the vast global supply of underutilized resources to deliver better
+security, durability, and performance services. Experience up to 90%
+lower costs and carbon reduction with Storj.</p>
+<p>Storj is an encrypted, secure, and cost-effective object storage
+service that enables you to store, back up, and archive large amounts of
+data in a decentralized manner.</p>
 <h2 id="backend-options">Backend options</h2>
-<p>Storj can be used both with this native backend and with the <a href="https://rclone.org/s3/#storj">s3 backend using the Storj S3 compatible gateway</a> (shared or private).</p>
-<p>Use this backend to take advantage of client-side encryption as well as to achieve the best possible download performance. Uploads will be erasure-coded locally, thus a 1gb upload will result in 2.68gb of data being uploaded to storage nodes across the network.</p>
-<p>Use the s3 backend and one of the S3 compatible Hosted Gateways to increase upload performance and reduce the load on your systems and network. Uploads will be encrypted and erasure-coded server-side, thus a 1GB upload will result in only in 1GB of data being uploaded to storage nodes across the network.</p>
+<p>Storj can be used both with this native backend and with the <a
+href="https://rclone.org/s3/#storj">s3 backend using the Storj S3
+compatible gateway</a> (shared or private).</p>
+<p>Use this backend to take advantage of client-side encryption as well
+as to achieve the best possible download performance. Uploads will be
+erasure-coded locally, thus a 1gb upload will result in 2.68gb of data
+being uploaded to storage nodes across the network.</p>
+<p>Use the s3 backend and one of the S3 compatible Hosted Gateways to
+increase upload performance and reduce the load on your systems and
+network. Uploads will be encrypted and erasure-coded server-side, thus a
+1GB upload will result in only in 1GB of data being uploaded to storage
+nodes across the network.</p>
 <p>Side by side comparison with more details:</p>
 <ul>
 <li>Characteristics:
 <ul>
-<li><em>Storj backend</em>: Uses native RPC protocol, connects directly to the storage nodes which hosts the data. Requires more CPU resource of encoding/decoding and has network amplification (especially during the upload), uses lots of TCP connections</li>
-<li><em>S3 backend</em>: Uses S3 compatible HTTP Rest API via the shared gateways. There is no network amplification, but performance depends on the shared gateways and the secret encryption key is shared with the gateway.</li>
+<li><em>Storj backend</em>: Uses native RPC protocol, connects directly
+to the storage nodes which hosts the data. Requires more CPU resource of
+encoding/decoding and has network amplification (especially during the
+upload), uses lots of TCP connections</li>
+<li><em>S3 backend</em>: Uses S3 compatible HTTP Rest API via the shared
+gateways. There is no network amplification, but performance depends on
+the shared gateways and the secret encryption key is shared with the
+gateway.</li>
 </ul></li>
 <li>Typical usage:
 <ul>
-<li><em>Storj backend</em>: Server environments and desktops with enough resources, internet speed and connectivity - and applications where storjs client-side encryption is required.</li>
-<li><em>S3 backend</em>: Desktops and similar with limited resources, internet speed or connectivity.</li>
+<li><em>Storj backend</em>: Server environments and desktops with enough
+resources, internet speed and connectivity - and applications where
+storjs client-side encryption is required.</li>
+<li><em>S3 backend</em>: Desktops and similar with limited resources,
+internet speed or connectivity.</li>
 </ul></li>
 <li>Security:
 <ul>
-<li><em>Storj backend</em>: <strong>strong</strong>. Private encryption key doesn't need to leave the local computer.</li>
-<li><em>S3 backend</em>: <strong>weaker</strong>. Private encryption key is <a href="https://docs.storj.io/dcs/api-reference/s3-compatible-gateway#security-and-encryption">shared with</a> the authentication service of the hosted gateway, where it's stored encrypted. It can be stronger when combining with the rclone <a href="/crypt">crypt</a> backend.</li>
+<li><em>Storj backend</em>: <strong>strong</strong>. Private encryption
+key doesn't need to leave the local computer.</li>
+<li><em>S3 backend</em>: <strong>weaker</strong>. Private encryption key
+is <a
+href="https://docs.storj.io/dcs/api-reference/s3-compatible-gateway#security-and-encryption">shared
+with</a> the authentication service of the hosted gateway, where it's
+stored encrypted. It can be stronger when combining with the rclone <a
+href="/crypt">crypt</a> backend.</li>
 </ul></li>
 <li>Bandwidth usage (upload):
 <ul>
-<li><em>Storj backend</em>: <strong>higher</strong>. As data is erasure coded on the client side both the original data and the parities should be uploaded. About ~2.7 times more data is required to be uploaded. Client may start to upload with even higher number of nodes (~3.7 times more) and abandon/stop the slow uploads.</li>
-<li><em>S3 backend</em>: <strong>normal</strong>. Only the raw data is uploaded, erasure coding happens on the gateway.</li>
+<li><em>Storj backend</em>: <strong>higher</strong>. As data is erasure
+coded on the client side both the original data and the parities should
+be uploaded. About ~2.7 times more data is required to be uploaded.
+Client may start to upload with even higher number of nodes (~3.7 times
+more) and abandon/stop the slow uploads.</li>
+<li><em>S3 backend</em>: <strong>normal</strong>. Only the raw data is
+uploaded, erasure coding happens on the gateway.</li>
 </ul></li>
 <li>Bandwidth usage (download)
 <ul>
-<li><em>Storj backend</em>: <strong>almost normal</strong>. Only the minimal number of data is required, but to avoid very slow data providers a few more sources are used and the slowest are ignored (max 1.2x overhead).</li>
-<li><em>S3 backend</em>: <strong>normal</strong>. Only the raw data is downloaded, erasure coding happens on the shared gateway.</li>
+<li><em>Storj backend</em>: <strong>almost normal</strong>. Only the
+minimal number of data is required, but to avoid very slow data
+providers a few more sources are used and the slowest are ignored (max
+1.2x overhead).</li>
+<li><em>S3 backend</em>: <strong>normal</strong>. Only the raw data is
+downloaded, erasure coding happens on the shared gateway.</li>
 </ul></li>
 <li>CPU usage:
 <ul>
-<li><em>Storj backend</em>: <strong>higher</strong>, but more predictable. Erasure code and encryption/decryption happens locally which requires significant CPU usage.</li>
-<li><em>S3 backend</em>: <strong>less</strong>. Erasure code and encryption/decryption happens on shared s3 gateways (and as is, it depends on the current load on the gateways)</li>
+<li><em>Storj backend</em>: <strong>higher</strong>, but more
+predictable. Erasure code and encryption/decryption happens locally
+which requires significant CPU usage.</li>
+<li><em>S3 backend</em>: <strong>less</strong>. Erasure code and
+encryption/decryption happens on shared s3 gateways (and as is, it
+depends on the current load on the gateways)</li>
 </ul></li>
 <li>TCP connection usage:
 <ul>
-<li><em>Storj backend</em>: <strong>high</strong>. A direct connection is required to each of the Storj nodes resulting in 110 connections on upload and 35 on download per 64 MB segment. Not all the connections are actively used (slow ones are pruned), but they are all opened. <a href="https://rclone.org/storj/#known-issues">Adjusting the max open file limit</a> may be required.</li>
-<li><em>S3 backend</em>: <strong>normal</strong>. Only one connection per download/upload thread is required to the shared gateway.</li>
+<li><em>Storj backend</em>: <strong>high</strong>. A direct connection
+is required to each of the Storj nodes resulting in 110 connections on
+upload and 35 on download per 64 MB segment. Not all the connections are
+actively used (slow ones are pruned), but they are all opened. <a
+href="https://rclone.org/storj/#known-issues">Adjusting the max open
+file limit</a> may be required.</li>
+<li><em>S3 backend</em>: <strong>normal</strong>. Only one connection
+per download/upload thread is required to the shared gateway.</li>
 </ul></li>
 <li>Overall performance:
 <ul>
-<li><em>Storj backend</em>: with enough resources (CPU and bandwidth) <em>storj</em> backend can provide even 2x better performance. Data is directly downloaded to / uploaded from to the client instead of the gateway.</li>
-<li><em>S3 backend</em>: Can be faster on edge devices where CPU and network bandwidth is limited as the shared S3 compatible gateways take care about the encrypting/decryption and erasure coding and no download/upload amplification.</li>
+<li><em>Storj backend</em>: with enough resources (CPU and bandwidth)
+<em>storj</em> backend can provide even 2x better performance. Data is
+directly downloaded to / uploaded from to the client instead of the
+gateway.</li>
+<li><em>S3 backend</em>: Can be faster on edge devices where CPU and
+network bandwidth is limited as the shared S3 compatible gateways take
+care about the encrypting/decryption and erasure coding and no
+download/upload amplification.</li>
 </ul></li>
 <li>Decentralization:
 <ul>
-<li><em>Storj backend</em>: <strong>high</strong>. Data is downloaded directly from the distributed cloud of storage providers.</li>
-<li><em>S3 backend</em>: <strong>low</strong>. Requires a running S3 gateway (either self-hosted or Storj-hosted).</li>
+<li><em>Storj backend</em>: <strong>high</strong>. Data is downloaded
+directly from the distributed cloud of storage providers.</li>
+<li><em>S3 backend</em>: <strong>low</strong>. Requires a running S3
+gateway (either self-hosted or Storj-hosted).</li>
 </ul></li>
 <li>Limitations:
 <ul>
-<li><em>Storj backend</em>: <code>rclone checksum</code> is not possible without download, as checksum metadata is not calculated during upload</li>
-<li><em>S3 backend</em>: secret encryption key is shared with the gateway</li>
+<li><em>Storj backend</em>: <code>rclone checksum</code> is not possible
+without download, as checksum metadata is not calculated during
+upload</li>
+<li><em>S3 backend</em>: secret encryption key is shared with the
+gateway</li>
 </ul></li>
 </ul>
-<h2 id="configuration-47">Configuration</h2>
-<p>To make a new Storj configuration you need one of the following: * Access Grant that someone else shared with you. * <a href="https://documentation.storj.io/getting-started/uploading-your-first-object/create-an-api-key">API Key</a> of a Storj project you are a member of.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<h2 id="configuration-48">Configuration</h2>
+<p>To make a new Storj configuration you need one of the following: *
+Access Grant that someone else shared with you. * <a
+href="https://documentation.storj.io/getting-started/uploading-your-first-object/create-an-api-key">API
+Key</a> of a Storj project you are a member of.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <h3 id="setup-with-access-grant">Setup with access grant</h3>
@@ -34560,7 +49350,8 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<h3 id="setup-with-api-key-and-passphrase">Setup with API key and passphrase</h3>
+<h3 id="setup-with-api-key-and-passphrase">Setup with API key and
+passphrase</h3>
 <pre><code>No remotes found, make a new one?
 n) New remote
 s) Set configuration password
@@ -34614,8 +49405,9 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<h3 id="standard-options-50">Standard options</h3>
-<p>Here are the Standard options specific to storj (Storj Decentralized Cloud Storage).</p>
+<h3 id="standard-options-51">Standard options</h3>
+<p>Here are the Standard options specific to storj (Storj Decentralized
+Cloud Storage).</p>
 <h4 id="storj-provider">--storj-provider</h4>
 <p>Choose an authentication method.</p>
 <p>Properties:</p>
@@ -34632,7 +49424,8 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 <li>"new"
 <ul>
-<li>Create a new access grant from satellite address, API key, and passphrase.</li>
+<li>Create a new access grant from satellite address, API key, and
+passphrase.</li>
 </ul></li>
 </ul></li>
 </ul>
@@ -34648,7 +49441,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="storj-satellite-address">--storj-satellite-address</h4>
 <p>Satellite address.</p>
-<p>Custom satellite address should match the format: <code>&lt;nodeid&gt;@&lt;address&gt;:&lt;port&gt;</code>.</p>
+<p>Custom satellite address should match the format:
+<code>&lt;nodeid&gt;@&lt;address&gt;:&lt;port&gt;</code>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: satellite_address</li>
@@ -34693,8 +49487,9 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-51">Advanced options</h3>
-<p>Here are the Advanced options specific to storj (Storj Decentralized Cloud Storage).</p>
+<h3 id="advanced-options-52">Advanced options</h3>
+<p>Here are the Advanced options specific to storj (Storj Decentralized
+Cloud Storage).</p>
 <h4 id="storj-description">--storj-description</h4>
 <p>Description of the remote.</p>
 <p>Properties:</p>
@@ -34705,53 +49500,72 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="usage-2">Usage</h2>
-<p>Paths are specified as <code>remote:bucket</code> (or <code>remote:</code> for the <code>lsf</code> command.) You may put subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
+<p>Paths are specified as <code>remote:bucket</code> (or
+<code>remote:</code> for the <code>lsf</code> command.) You may put
+subdirectories in too, e.g. <code>remote:bucket/path/to/dir</code>.</p>
 <p>Once configured you can then use <code>rclone</code> like this.</p>
 <h3 id="create-a-new-bucket">Create a new bucket</h3>
-<p>Use the <code>mkdir</code> command to create new bucket, e.g. <code>bucket</code>.</p>
+<p>Use the <code>mkdir</code> command to create new bucket, e.g.
+<code>bucket</code>.</p>
 <pre><code>rclone mkdir remote:bucket</code></pre>
 <h3 id="list-all-buckets">List all buckets</h3>
 <p>Use the <code>lsf</code> command to list all buckets.</p>
 <pre><code>rclone lsf remote:</code></pre>
-<p>Note the colon (<code>:</code>) character at the end of the command line.</p>
+<p>Note the colon (<code>:</code>) character at the end of the command
+line.</p>
 <h3 id="delete-a-bucket">Delete a bucket</h3>
 <p>Use the <code>rmdir</code> command to delete an empty bucket.</p>
 <pre><code>rclone rmdir remote:bucket</code></pre>
-<p>Use the <code>purge</code> command to delete a non-empty bucket with all its content.</p>
+<p>Use the <code>purge</code> command to delete a non-empty bucket with
+all its content.</p>
 <pre><code>rclone purge remote:bucket</code></pre>
 <h3 id="upload-objects">Upload objects</h3>
 <p>Use the <code>copy</code> command to upload an object.</p>
 <pre><code>rclone copy --progress /home/local/directory/file.ext remote:bucket/path/to/dir/</code></pre>
-<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don't need this information.</p>
+<p>The <code>--progress</code> flag is for displaying progress
+information. Remove it if you don't need this information.</p>
 <p>Use a folder in the local path to upload all its objects.</p>
 <pre><code>rclone copy --progress /home/local/directory/ remote:bucket/path/to/dir/</code></pre>
 <p>Only modified files will be copied.</p>
 <h3 id="list-objects">List objects</h3>
-<p>Use the <code>ls</code> command to list recursively all objects in a bucket.</p>
+<p>Use the <code>ls</code> command to list recursively all objects in a
+bucket.</p>
 <pre><code>rclone ls remote:bucket</code></pre>
-<p>Add the folder to the remote path to list recursively all objects in this folder.</p>
+<p>Add the folder to the remote path to list recursively all objects in
+this folder.</p>
 <pre><code>rclone ls remote:bucket/path/to/dir/</code></pre>
-<p>Use the <code>lsf</code> command to list non-recursively all objects in a bucket or a folder.</p>
+<p>Use the <code>lsf</code> command to list non-recursively all objects
+in a bucket or a folder.</p>
 <pre><code>rclone lsf remote:bucket/path/to/dir/</code></pre>
 <h3 id="download-objects">Download objects</h3>
 <p>Use the <code>copy</code> command to download an object.</p>
 <pre><code>rclone copy --progress remote:bucket/path/to/dir/file.ext /home/local/directory/</code></pre>
-<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don't need this information.</p>
+<p>The <code>--progress</code> flag is for displaying progress
+information. Remove it if you don't need this information.</p>
 <p>Use a folder in the remote path to download all its objects.</p>
 <pre><code>rclone copy --progress remote:bucket/path/to/dir/ /home/local/directory/</code></pre>
 <h3 id="delete-objects">Delete objects</h3>
-<p>Use the <code>deletefile</code> command to delete a single object.</p>
+<p>Use the <code>deletefile</code> command to delete a single
+object.</p>
 <pre><code>rclone deletefile remote:bucket/path/to/dir/file.ext</code></pre>
-<p>Use the <code>delete</code> command to delete all object in a folder.</p>
+<p>Use the <code>delete</code> command to delete all object in a
+folder.</p>
 <pre><code>rclone delete remote:bucket/path/to/dir/</code></pre>
-<h3 id="print-the-total-size-of-objects">Print the total size of objects</h3>
-<p>Use the <code>size</code> command to print the total size of objects in a bucket or a folder.</p>
+<h3 id="print-the-total-size-of-objects">Print the total size of
+objects</h3>
+<p>Use the <code>size</code> command to print the total size of objects
+in a bucket or a folder.</p>
 <pre><code>rclone size remote:bucket/path/to/dir/</code></pre>
 <h3 id="sync-two-locations">Sync two Locations</h3>
-<p>Use the <code>sync</code> command to sync the source to the destination, changing the destination only, deleting any excess files.</p>
+<p>Use the <code>sync</code> command to sync the source to the
+destination, changing the destination only, deleting any excess
+files.</p>
 <pre><code>rclone sync --interactive --progress /home/local/directory/ remote:bucket/path/to/dir/</code></pre>
-<p>The <code>--progress</code> flag is for displaying progress information. Remove it if you don't need this information.</p>
-<p>Since this can cause data loss, test first with the <code>--dry-run</code> flag to see exactly what would be copied and deleted.</p>
+<p>The <code>--progress</code> flag is for displaying progress
+information. Remove it if you don't need this information.</p>
+<p>Since this can cause data loss, test first with the
+<code>--dry-run</code> flag to see exactly what would be copied and
+deleted.</p>
 <p>The sync can be done also from Storj to the local file system.</p>
 <pre><code>rclone sync --interactive --progress remote:bucket/path/to/dir/ /home/local/directory/</code></pre>
 <p>Or between two Storj buckets.</p>
@@ -34759,16 +49573,40 @@ y/e/d&gt; y</code></pre>
 <p>Or even between another cloud storage and Storj.</p>
 <pre><code>rclone sync --interactive --progress s3:bucket/path/to/dir/ storj:bucket/path/to/dir/</code></pre>
 <h2 id="limitations-37">Limitations</h2>
-<p><code>rclone about</code> is not supported by the rclone Storj backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the rclone Storj
+backend. Backends without this capability cannot determine free space
+for an rclone mount or use policy <code>mfs</code> (most free space) as
+a member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h2 id="known-issues-1">Known issues</h2>
-<p>If you get errors like <code>too many open files</code> this usually happens when the default <code>ulimit</code> for system max open files is exceeded. Native Storj protocol opens a large number of TCP connections (each of which is counted as an open file). For a single upload stream you can expect 110 TCP connections to be opened. For a single download stream you can expect 35. This batch of connections will be opened for every 64 MiB segment and you should also expect TCP connections to be reused. If you do many transfers you eventually open a connection to most storage nodes (thousands of nodes).</p>
-<p>To fix these, please raise your system limits. You can do this issuing a <code>ulimit -n 65536</code> just before you run rclone. To change the limits more permanently you can add this to your shell startup script, e.g. <code>$HOME/.bashrc</code>, or change the system-wide configuration, usually <code>/etc/sysctl.conf</code> and/or <code>/etc/security/limits.conf</code>, but please refer to your operating system manual.</p>
+<p>If you get errors like <code>too many open files</code> this usually
+happens when the default <code>ulimit</code> for system max open files
+is exceeded. Native Storj protocol opens a large number of TCP
+connections (each of which is counted as an open file). For a single
+upload stream you can expect 110 TCP connections to be opened. For a
+single download stream you can expect 35. This batch of connections will
+be opened for every 64 MiB segment and you should also expect TCP
+connections to be reused. If you do many transfers you eventually open a
+connection to most storage nodes (thousands of nodes).</p>
+<p>To fix these, please raise your system limits. You can do this
+issuing a <code>ulimit -n 65536</code> just before you run rclone. To
+change the limits more permanently you can add this to your shell
+startup script, e.g. <code>$HOME/.bashrc</code>, or change the
+system-wide configuration, usually <code>/etc/sysctl.conf</code> and/or
+<code>/etc/security/limits.conf</code>, but please refer to your
+operating system manual.</p>
 <h1 id="sugarsync">SugarSync</h1>
-<p><a href="https://sugarsync.com">SugarSync</a> is a cloud service that enables active synchronization of files across computers and other devices for file backup, access, syncing, and sharing.</p>
-<h2 id="configuration-48">Configuration</h2>
-<p>The initial setup for SugarSync involves getting a token from SugarSync which you can do with rclone. <code>rclone config</code> walks you through it.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p><a href="https://sugarsync.com">SugarSync</a> is a cloud service that
+enables active synchronization of files across computers and other
+devices for file backup, access, syncing, and sharing.</p>
+<h2 id="configuration-49">Configuration</h2>
+<p>The initial setup for SugarSync involves getting a token from
+SugarSync which you can do with rclone. <code>rclone config</code> walks
+you through it.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -34820,7 +49658,8 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>Note that the config asks for your email and password but doesn't store them, it only uses them to get the initial token.</p>
+<p>Note that the config asks for your email and password but doesn't
+store them, it only uses them to get the initial token.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>List directories (sync folders) in top level of your SugarSync</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -34829,17 +49668,32 @@ y/e/d&gt; y</code></pre>
 <p>To copy a local directory to an SugarSync folder called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<p><strong>NB</strong> you can't create files in the top level folder you have to create a folder, which rclone will create as a "Sync Folder" with SugarSync.</p>
-<h3 id="modification-times-and-hashes-26">Modification times and hashes</h3>
-<p>SugarSync does not support modification times or hashes, therefore syncing will default to <code>--size-only</code> checking. Note that using <code>--update</code> will work as rclone can read the time files were uploaded.</p>
-<h3 id="restricted-filename-characters-31">Restricted filename characters</h3>
-<p>SugarSync replaces the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> except for DEL.</p>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in XML strings.</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<p><strong>NB</strong> you can't create files in the top level folder
+you have to create a folder, which rclone will create as a "Sync Folder"
+with SugarSync.</p>
+<h3 id="modification-times-and-hashes-26">Modification times and
+hashes</h3>
+<p>SugarSync does not support modification times or hashes, therefore
+syncing will default to <code>--size-only</code> checking. Note that
+using <code>--update</code> will work as rclone can read the time files
+were uploaded.</p>
+<h3 id="restricted-filename-characters-30">Restricted filename
+characters</h3>
+<p>SugarSync replaces the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> except for DEL.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in XML strings.</p>
 <h3 id="deleting-files-7">Deleting files</h3>
-<p>Deleted files will be moved to the "Deleted items" folder by default.</p>
-<p>However you can supply the flag <code>--sugarsync-hard-delete</code> or set the config parameter <code>hard_delete = true</code> if you would like files to be deleted straight away.</p>
-<h3 id="standard-options-51">Standard options</h3>
+<p>Deleted files will be moved to the "Deleted items" folder by
+default.</p>
+<p>However you can supply the flag <code>--sugarsync-hard-delete</code>
+or set the config parameter <code>hard_delete = true</code> if you would
+like files to be deleted straight away.</p>
+<h3 id="standard-options-52">Standard options</h3>
 <p>Here are the Standard options specific to sugarsync (Sugarsync).</p>
 <h4 id="sugarsync-app-id">--sugarsync-app-id</h4>
 <p>Sugarsync App ID.</p>
@@ -34861,7 +49715,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="sugarsync-private-access-key">--sugarsync-private-access-key</h4>
+<h4
+id="sugarsync-private-access-key">--sugarsync-private-access-key</h4>
 <p>Sugarsync Private Access Key.</p>
 <p>Leave blank to use rclone's.</p>
 <p>Properties:</p>
@@ -34872,7 +49727,8 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h4 id="sugarsync-hard-delete">--sugarsync-hard-delete</h4>
-<p>Permanently delete files if true otherwise put them in the deleted files.</p>
+<p>Permanently delete files if true otherwise put them in the deleted
+files.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: hard_delete</li>
@@ -34880,7 +49736,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h3 id="advanced-options-52">Advanced options</h3>
+<h3 id="advanced-options-53">Advanced options</h3>
 <p>Here are the Advanced options specific to sugarsync (Sugarsync).</p>
 <h4 id="sugarsync-refresh-token">--sugarsync-refresh-token</h4>
 <p>Sugarsync refresh token.</p>
@@ -34902,7 +49758,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h4 id="sugarsync-authorization-expiry">--sugarsync-authorization-expiry</h4>
+<h4
+id="sugarsync-authorization-expiry">--sugarsync-authorization-expiry</h4>
 <p>Sugarsync authorization expiry.</p>
 <p>Leave blank normally, will be auto configured by rclone.</p>
 <p>Properties:</p>
@@ -34944,7 +49801,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="sugarsync-encoding">--sugarsync-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -34962,14 +49820,22 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-38">Limitations</h2>
-<p><code>rclone about</code> is not supported by the SugarSync backend. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p><code>rclone about</code> is not supported by the SugarSync backend.
+Backends without this capability cannot determine free space for an
+rclone mount or use policy <code>mfs</code> (most free space) as a
+member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="uloz.to">Uloz.to</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<p>The initial setup for Uloz.to involves filling in the user credentials. <code>rclone config</code> walks you through it.</p>
-<h2 id="configuration-49">Configuration</h2>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<p>The initial setup for Uloz.to involves filling in the user
+credentials. <code>rclone config</code> walks you through it.</p>
+<h2 id="configuration-50">Configuration</h2>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -35027,12 +49893,26 @@ y/e/d&gt; y</code></pre>
 <p>To copy a local folder to a Uloz.to folder called backup:</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
 <h3 id="user-credentials">User credentials</h3>
-<p>The only reliable method is to authenticate the user using username and password. Uloz.to offers an API key as well, but it's reserved for the use of Uloz.to's in-house application and using it in different circumstances is unreliable.</p>
-<h3 id="modification-times-and-hashes-27">Modification times and hashes</h3>
-<p>Uloz.to doesn't allow the user to set a custom modification time, or retrieve the hashes after upload. As a result, the integration uses a free form field the API provides to encode client-provided timestamps and hashes. Timestamps are stored with microsecond precision.</p>
-<p>A server calculated MD5 hash of the file is verified upon upload. Afterwards, the backend only serves the client-side calculated hashes. Hashes can also be retrieved upon creating a file download link, but it's impractical for <code>list</code>-like use cases.</p>
-<h3 id="restricted-filename-characters-32">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<p>The only reliable method is to authenticate the user using username
+and password. Uloz.to offers an API key as well, but it's reserved for
+the use of Uloz.to's in-house application and using it in different
+circumstances is unreliable.</p>
+<h3 id="modification-times-and-hashes-27">Modification times and
+hashes</h3>
+<p>Uloz.to doesn't allow the user to set a custom modification time, or
+retrieve the hashes after upload. As a result, the integration uses a
+free form field the API provides to encode client-provided timestamps
+and hashes. Timestamps are stored with microsecond precision.</p>
+<p>A server calculated MD5 hash of the file is verified upon upload.
+Afterwards, the backend only serves the client-side calculated hashes.
+Hashes can also be retrieved upon creating a file download link, but
+it's impractical for <code>list</code>-like use cases.</p>
+<h3 id="restricted-filename-characters-31">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -35049,22 +49929,44 @@ y/e/d&gt; y</code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
 <h3 id="transfers-5">Transfers</h3>
-<p>All files are currently uploaded using a single HTTP request, so for uploading large files a stable connection is necessary. Rclone will upload up to <code>--transfers</code> chunks at the same time (shared among all uploads).</p>
+<p>All files are currently uploaded using a single HTTP request, so for
+uploading large files a stable connection is necessary. Rclone will
+upload up to <code>--transfers</code> chunks at the same time (shared
+among all uploads).</p>
 <h3 id="deleting-files-8">Deleting files</h3>
-<p>By default, files are moved to the recycle bin whereas folders are deleted immediately. Trashed files are permanently deleted after 30 days in the recycle bin.</p>
+<p>By default, files are moved to the recycle bin whereas folders are
+deleted immediately. Trashed files are permanently deleted after 30 days
+in the recycle bin.</p>
 <p>Emptying the trash is currently not implemented in rclone.</p>
 <h3 id="root-folder-id-5">Root folder ID</h3>
-<p>You can set the <code>root_folder_slug</code> for rclone. This is the folder (identified by its <code>Folder slug</code>) that rclone considers to be the root of your Uloz.to drive.</p>
-<p>Normally you will leave this blank and rclone will determine the correct root to use itself. However you can set this to restrict rclone to a specific folder hierarchy.</p>
-<p>In order to do this you will have to find the <code>Folder slug</code> of the folder you wish to use as root. This will be the last segment of the URL when you open the relevant folder in the Uloz.to web interface.</p>
-<p>For example, for exploring a folder with URL <code>https://uloz.to/fm/my-files/foobar</code>, <code>foobar</code> should be used as the root slug.</p>
-<p><code>root_folder_slug</code> can be used alongside a specific path in the remote path. For example, if your remote's <code>root_folder_slug</code> corresponds to <code>/foo/bar</code>, <code>remote:baz/qux</code> will refer to <code>ABSOLUTE_ULOZTO_ROOT/foo/bar/baz/qux</code>.</p>
-<h3 id="standard-options-52">Standard options</h3>
+<p>You can set the <code>root_folder_slug</code> for rclone. This is the
+folder (identified by its <code>Folder slug</code>) that rclone
+considers to be the root of your Uloz.to drive.</p>
+<p>Normally you will leave this blank and rclone will determine the
+correct root to use itself. However you can set this to restrict rclone
+to a specific folder hierarchy.</p>
+<p>In order to do this you will have to find the
+<code>Folder slug</code> of the folder you wish to use as root. This
+will be the last segment of the URL when you open the relevant folder in
+the Uloz.to web interface.</p>
+<p>For example, for exploring a folder with URL
+<code>https://uloz.to/fm/my-files/foobar</code>, <code>foobar</code>
+should be used as the root slug.</p>
+<p><code>root_folder_slug</code> can be used alongside a specific path
+in the remote path. For example, if your remote's
+<code>root_folder_slug</code> corresponds to <code>/foo/bar</code>,
+<code>remote:baz/qux</code> will refer to
+<code>ABSOLUTE_ULOZTO_ROOT/foo/bar/baz/qux</code>.</p>
+<h3 id="standard-options-53">Standard options</h3>
 <p>Here are the Standard options specific to ulozto (Uloz.to).</p>
 <h4 id="ulozto-app-token">--ulozto-app-token</h4>
-<p>The application token identifying the app. An app API key can be either found in the API doc https://uloz.to/upload-resumable-api-beta or obtained from customer service.</p>
+<p>The application token identifying the app. An app API key can be
+either found in the API doc https://uloz.to/upload-resumable-api-beta or
+obtained from customer service.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: app_token</li>
@@ -35083,7 +49985,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="ulozto-password">--ulozto-password</h4>
 <p>The password for the user.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: password</li>
@@ -35091,10 +49995,12 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-53">Advanced options</h3>
+<h3 id="advanced-options-54">Advanced options</h3>
 <p>Here are the Advanced options specific to ulozto (Uloz.to).</p>
 <h4 id="ulozto-root-folder-slug">--ulozto-root-folder-slug</h4>
-<p>If set, rclone will use this folder as the root folder for all operations. For example, if the slug identifies 'foo/bar/', 'ulozto:baz' is equivalent to 'ulozto:foo/bar/baz' without any root slug set.</p>
+<p>If set, rclone will use this folder as the root folder for all
+operations. For example, if the slug identifies 'foo/bar/', 'ulozto:baz'
+is equivalent to 'ulozto:foo/bar/baz' without any root slug set.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: root_folder_slug</li>
@@ -35113,7 +50019,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="ulozto-encoding">--ulozto-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -35131,18 +50038,35 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-39">Limitations</h2>
-<p>Uloz.to file names can't have the <code>\</code> character in. rclone maps this to and from an identical looking unicode equivalent <code>＼</code> (U+FF3C Fullwidth Reverse Solidus).</p>
+<p>Uloz.to file names can't have the <code>\</code> character in. rclone
+maps this to and from an identical looking unicode equivalent
+<code>＼</code> (U+FF3C Fullwidth Reverse Solidus).</p>
 <p>Uloz.to only supports filenames up to 255 characters in length.</p>
-<p>Uloz.to rate limits access to the API, but exact details are undisclosed. Practical testing reveals that hitting the rate limit during normal use is very rare, although not impossible with higher number of concurrently uploaded files.</p>
-<p><code>rclone about</code> is not supported by the Uloz.to backend. Although there's an endpoint to retrieve the information for the UI, it's not exposed in the API. Backends without this capability cannot determine free space for an rclone mount or use policy <code>mfs</code> (most free space) as a member of an rclone union remote.</p>
-<p>See <a href="https://rclone.org/overview/#optional-features">List of backends that do not support rclone about</a> and <a href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
+<p>Uloz.to rate limits access to the API, but exact details are
+undisclosed. Practical testing reveals that hitting the rate limit
+during normal use is very rare, although not impossible with higher
+number of concurrently uploaded files.</p>
+<p><code>rclone about</code> is not supported by the Uloz.to backend.
+Although there's an endpoint to retrieve the information for the UI,
+it's not exposed in the API. Backends without this capability cannot
+determine free space for an rclone mount or use policy <code>mfs</code>
+(most free space) as a member of an rclone union remote.</p>
+<p>See <a href="https://rclone.org/overview/#optional-features">List of
+backends that do not support rclone about</a> and <a
+href="https://rclone.org/commands/rclone_about/">rclone about</a></p>
 <h1 id="uptobox">Uptobox</h1>
-<p>This is a Backend for Uptobox file storage service. Uptobox is closer to a one-click hoster than a traditional cloud storage provider and therefore not suitable for long term storage.</p>
+<p>This is a Backend for Uptobox file storage service. Uptobox is closer
+to a one-click hoster than a traditional cloud storage provider and
+therefore not suitable for long term storage.</p>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-50">Configuration</h2>
-<p>To configure an Uptobox backend you'll need your personal api token. You'll find it in your <a href="https://uptobox.com/my_account">account settings</a></p>
-<p>Here is an example of how to make a remote called <code>remote</code> with the default setup. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-51">Configuration</h2>
+<p>To configure an Uptobox backend you'll need your personal api token.
+You'll find it in your <a href="https://uptobox.com/my_account">account
+settings</a></p>
+<p>Here is an example of how to make a remote called <code>remote</code>
+with the default setup. First run:</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>Current remotes:
@@ -35194,10 +50118,16 @@ y/e/d&gt; </code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an Uptobox directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-28">Modification times and hashes</h3>
-<p>Uptobox supports neither modified times nor checksums. All timestamps will read as that set by <code>--default-time</code>.</p>
-<h3 id="restricted-filename-characters-33">Restricted filename characters</h3>
-<p>In addition to the <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> the following characters are also replaced:</p>
+<h3 id="modification-times-and-hashes-28">Modification times and
+hashes</h3>
+<p>Uptobox supports neither modified times nor checksums. All timestamps
+will read as that set by <code>--default-time</code>.</p>
+<h3 id="restricted-filename-characters-32">Restricted filename
+characters</h3>
+<p>In addition to the <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> the following characters are also
+replaced:</p>
 <table>
 <thead>
 <tr class="header">
@@ -35219,8 +50149,10 @@ y/e/d&gt; </code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in XML strings.</p>
-<h3 id="standard-options-53">Standard options</h3>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in XML strings.</p>
+<h3 id="standard-options-54">Standard options</h3>
 <p>Here are the Standard options specific to uptobox (Uptobox).</p>
 <h4 id="uptobox-access-token">--uptobox-access-token</h4>
 <p>Your access token.</p>
@@ -35232,7 +50164,7 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-54">Advanced options</h3>
+<h3 id="advanced-options-55">Advanced options</h3>
 <p>Here are the Advanced options specific to uptobox (Uptobox).</p>
 <h4 id="uptobox-private">--uptobox-private</h4>
 <p>Set to make uploaded files private</p>
@@ -35245,13 +50177,15 @@ y/e/d&gt; </code></pre>
 </ul>
 <h4 id="uptobox-encoding">--uptobox-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
 <li>Env Var: RCLONE_UPTOBOX_ENCODING</li>
 <li>Type: Encoding</li>
-<li>Default: Slash,LtGt,DoubleQuote,BackQuote,Del,Ctl,LeftSpace,InvalidUtf8,Dot</li>
+<li>Default:
+Slash,LtGt,DoubleQuote,BackQuote,Del,Ctl,LeftSpace,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="uptobox-description">--uptobox-description</h4>
 <p>Description of the remote.</p>
@@ -35263,21 +50197,44 @@ y/e/d&gt; </code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-40">Limitations</h2>
-<p>Uptobox will delete inactive files that have not been accessed in 60 days.</p>
-<p><code>rclone about</code> is not supported by this backend an overview of used space can however been seen in the uptobox web interface.</p>
+<p>Uptobox will delete inactive files that have not been accessed in 60
+days.</p>
+<p><code>rclone about</code> is not supported by this backend an
+overview of used space can however been seen in the uptobox web
+interface.</p>
 <h1 id="union">Union</h1>
-<p>The <code>union</code> backend joins several remotes together to make a single unified view of them.</p>
-<p>During the initial setup with <code>rclone config</code> you will specify the upstream remotes as a space separated list. The upstream remotes can either be a local paths or other remotes.</p>
-<p>The attributes <code>:ro</code>, <code>:nc</code> and <code>:writeback</code> can be attached to the end of the remote to tag the remote as <strong>read only</strong>, <strong>no create</strong> or <strong>writeback</strong>, e.g. <code>remote:directory/subdirectory:ro</code> or <code>remote:directory/subdirectory:nc</code>.</p>
+<p>The <code>union</code> backend joins several remotes together to make
+a single unified view of them.</p>
+<p>During the initial setup with <code>rclone config</code> you will
+specify the upstream remotes as a space separated list. The upstream
+remotes can either be a local paths or other remotes.</p>
+<p>The attributes <code>:ro</code>, <code>:nc</code> and
+<code>:writeback</code> can be attached to the end of the remote to tag
+the remote as <strong>read only</strong>, <strong>no create</strong> or
+<strong>writeback</strong>, e.g.
+<code>remote:directory/subdirectory:ro</code> or
+<code>remote:directory/subdirectory:nc</code>.</p>
 <ul>
-<li><code>:ro</code> means files will only be read from here and never written</li>
-<li><code>:nc</code> means new files or directories won't be created here</li>
-<li><code>:writeback</code> means files found in different remotes will be written back here. See the <a href="#writeback">writeback section</a> for more info.</li>
+<li><code>:ro</code> means files will only be read from here and never
+written</li>
+<li><code>:nc</code> means new files or directories won't be created
+here</li>
+<li><code>:writeback</code> means files found in different remotes will
+be written back here. See the <a href="#writeback">writeback section</a>
+for more info.</li>
 </ul>
-<p>Subfolders can be used in upstream remotes. Assume a union remote named <code>backup</code> with the remotes <code>mydrive:private/backup</code>. Invoking <code>rclone mkdir backup:desktop</code> is exactly the same as invoking <code>rclone mkdir mydrive:private/backup/desktop</code>.</p>
-<p>There is no special handling of paths containing <code>..</code> segments. Invoking <code>rclone mkdir backup:../desktop</code> is exactly the same as invoking <code>rclone mkdir mydrive:private/backup/../desktop</code>.</p>
-<h2 id="configuration-51">Configuration</h2>
-<p>Here is an example of how to make a union called <code>remote</code> for local folders. First run:</p>
+<p>Subfolders can be used in upstream remotes. Assume a union remote
+named <code>backup</code> with the remotes
+<code>mydrive:private/backup</code>. Invoking
+<code>rclone mkdir backup:desktop</code> is exactly the same as invoking
+<code>rclone mkdir mydrive:private/backup/desktop</code>.</p>
+<p>There is no special handling of paths containing <code>..</code>
+segments. Invoking <code>rclone mkdir backup:../desktop</code> is
+exactly the same as invoking
+<code>rclone mkdir mydrive:private/backup/../desktop</code>.</p>
+<h2 id="configuration-52">Configuration</h2>
+<p>Here is an example of how to make a union called <code>remote</code>
+for local folders. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -35334,15 +50291,28 @@ s) Set configuration password
 q) Quit config
 e/n/d/r/c/s/q&gt; q</code></pre>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
-<p>List directories in top level in <code>remote1:dir1</code>, <code>remote2:dir2</code> and <code>remote3:dir3</code></p>
+<p>List directories in top level in <code>remote1:dir1</code>,
+<code>remote2:dir2</code> and <code>remote3:dir3</code></p>
 <pre><code>rclone lsd remote:</code></pre>
-<p>List all the files in <code>remote1:dir1</code>, <code>remote2:dir2</code> and <code>remote3:dir3</code></p>
+<p>List all the files in <code>remote1:dir1</code>,
+<code>remote2:dir2</code> and <code>remote3:dir3</code></p>
 <pre><code>rclone ls remote:</code></pre>
-<p>Copy another local directory to the union directory called source, which will be placed into <code>remote3:dir3</code></p>
+<p>Copy another local directory to the union directory called source,
+which will be placed into <code>remote3:dir3</code></p>
 <pre><code>rclone copy C:\source remote:source</code></pre>
 <h3 id="behavior-policies">Behavior / Policies</h3>
-<p>The behavior of union backend is inspired by <a href="https://github.com/trapexit/mergerfs">trapexit/mergerfs</a>. All functions are grouped into 3 categories: <strong>action</strong>, <strong>create</strong> and <strong>search</strong>. These functions and categories can be assigned a policy which dictates what file or directory is chosen when performing that behavior. Any policy can be assigned to a function or category though some may not be very useful in practice. For instance: <strong>rand</strong> (random) may be useful for file creation (create) but could lead to very odd behavior if used for <code>delete</code> if there were more than one copy of the file.</p>
-<h3 id="function-category-classifications">Function / Category classifications</h3>
+<p>The behavior of union backend is inspired by <a
+href="https://github.com/trapexit/mergerfs">trapexit/mergerfs</a>. All
+functions are grouped into 3 categories: <strong>action</strong>,
+<strong>create</strong> and <strong>search</strong>. These functions and
+categories can be assigned a policy which dictates what file or
+directory is chosen when performing that behavior. Any policy can be
+assigned to a function or category though some may not be very useful in
+practice. For instance: <strong>rand</strong> (random) may be useful for
+file creation (create) but could lead to very odd behavior if used for
+<code>delete</code> if there were more than one copy of the file.</p>
+<h3 id="function-category-classifications">Function / Category
+classifications</h3>
 <table>
 <colgroup>
 <col style="width: 8%" />
@@ -35360,7 +50330,8 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <tr class="odd">
 <td>action</td>
 <td>Writing Existing file</td>
-<td>move, rmdir, rmdirs, delete, purge and copy, sync (as destination when file exist)</td>
+<td>move, rmdir, rmdirs, delete, purge and copy, sync (as destination
+when file exist)</td>
 </tr>
 <tr class="even">
 <td>create</td>
@@ -35380,12 +50351,19 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </tbody>
 </table>
 <h3 id="path-preservation">Path Preservation</h3>
-<p>Policies, as described below, are of two basic types. <code>path preserving</code> and <code>non-path preserving</code>.</p>
-<p>All policies which start with <code>ep</code> (<strong>epff</strong>, <strong>eplfs</strong>, <strong>eplus</strong>, <strong>epmfs</strong>, <strong>eprand</strong>) are <code>path preserving</code>. <code>ep</code> stands for <code>existing path</code>.</p>
-<p>A path preserving policy will only consider upstreams where the relative path being accessed already exists.</p>
-<p>When using non-path preserving policies paths will be created in target upstreams as necessary.</p>
+<p>Policies, as described below, are of two basic types.
+<code>path preserving</code> and <code>non-path preserving</code>.</p>
+<p>All policies which start with <code>ep</code> (<strong>epff</strong>,
+<strong>eplfs</strong>, <strong>eplus</strong>, <strong>epmfs</strong>,
+<strong>eprand</strong>) are <code>path preserving</code>.
+<code>ep</code> stands for <code>existing path</code>.</p>
+<p>A path preserving policy will only consider upstreams where the
+relative path being accessed already exists.</p>
+<p>When using non-path preserving policies paths will be created in
+target upstreams as necessary.</p>
 <h3 id="quota-relevant-policies">Quota Relevant Policies</h3>
-<p>Some policies rely on quota information. These policies should be used only if your upstreams support the respective quota fields.</p>
+<p>Some policies rely on quota information. These policies should be
+used only if your upstreams support the respective quota fields.</p>
 <table>
 <thead>
 <tr class="header">
@@ -35412,17 +50390,28 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </tr>
 </tbody>
 </table>
-<p>To check if your upstream supports the field, run <code>rclone about remote: [flags]</code> and see if the required field exists.</p>
+<p>To check if your upstream supports the field, run
+<code>rclone about remote: [flags]</code> and see if the required field
+exists.</p>
 <h3 id="filters-2">Filters</h3>
-<p>Policies basically search upstream remotes and create a list of files / paths for functions to work on. The policy is responsible for filtering and sorting. The policy type defines the sorting but filtering is mostly uniform as described below.</p>
+<p>Policies basically search upstream remotes and create a list of files
+/ paths for functions to work on. The policy is responsible for
+filtering and sorting. The policy type defines the sorting but filtering
+is mostly uniform as described below.</p>
 <ul>
 <li>No <strong>search</strong> policies filter.</li>
-<li>All <strong>action</strong> policies will filter out remotes which are tagged as <strong>read-only</strong>.</li>
-<li>All <strong>create</strong> policies will filter out remotes which are tagged <strong>read-only</strong> or <strong>no-create</strong>.</li>
+<li>All <strong>action</strong> policies will filter out remotes which
+are tagged as <strong>read-only</strong>.</li>
+<li>All <strong>create</strong> policies will filter out remotes which
+are tagged <strong>read-only</strong> or
+<strong>no-create</strong>.</li>
 </ul>
 <p>If all remotes are filtered an error will be returned.</p>
 <h3 id="policy-descriptions">Policy descriptions</h3>
-<p>The policies definition are inspired by <a href="https://github.com/trapexit/mergerfs">trapexit/mergerfs</a> but not exactly the same. Some policy definition could be different due to the much larger latency of remote file systems.</p>
+<p>The policies definition are inspired by <a
+href="https://github.com/trapexit/mergerfs">trapexit/mergerfs</a> but
+not exactly the same. Some policy definition could be different due to
+the much larger latency of remote file systems.</p>
 <table>
 <colgroup>
 <col style="width: 23%" />
@@ -35437,55 +50426,76 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 <tbody>
 <tr class="odd">
 <td>all</td>
-<td>Search category: same as <strong>epall</strong>. Action category: same as <strong>epall</strong>. Create category: act on all upstreams.</td>
+<td>Search category: same as <strong>epall</strong>. Action category:
+same as <strong>epall</strong>. Create category: act on all
+upstreams.</td>
 </tr>
 <tr class="even">
 <td>epall (existing path, all)</td>
-<td>Search category: Given this order configured, act on the first one found where the relative path exists. Action category: apply to all found. Create category: act on all upstreams where the relative path exists.</td>
+<td>Search category: Given this order configured, act on the first one
+found where the relative path exists. Action category: apply to all
+found. Create category: act on all upstreams where the relative path
+exists.</td>
 </tr>
 <tr class="odd">
 <td>epff (existing path, first found)</td>
-<td>Act on the first one found, by the time upstreams reply, where the relative path exists.</td>
+<td>Act on the first one found, by the time upstreams reply, where the
+relative path exists.</td>
 </tr>
 <tr class="even">
 <td>eplfs (existing path, least free space)</td>
-<td>Of all the upstreams on which the relative path exists choose the one with the least free space.</td>
+<td>Of all the upstreams on which the relative path exists choose the
+one with the least free space.</td>
 </tr>
 <tr class="odd">
 <td>eplus (existing path, least used space)</td>
-<td>Of all the upstreams on which the relative path exists choose the one with the least used space.</td>
+<td>Of all the upstreams on which the relative path exists choose the
+one with the least used space.</td>
 </tr>
 <tr class="even">
 <td>eplno (existing path, least number of objects)</td>
-<td>Of all the upstreams on which the relative path exists choose the one with the least number of objects.</td>
+<td>Of all the upstreams on which the relative path exists choose the
+one with the least number of objects.</td>
 </tr>
 <tr class="odd">
 <td>epmfs (existing path, most free space)</td>
-<td>Of all the upstreams on which the relative path exists choose the one with the most free space.</td>
+<td>Of all the upstreams on which the relative path exists choose the
+one with the most free space.</td>
 </tr>
 <tr class="even">
 <td>eprand (existing path, random)</td>
-<td>Calls <strong>epall</strong> and then randomizes. Returns only one upstream.</td>
+<td>Calls <strong>epall</strong> and then randomizes. Returns only one
+upstream.</td>
 </tr>
 <tr class="odd">
 <td>ff (first found)</td>
-<td>Search category: same as <strong>epff</strong>. Action category: same as <strong>epff</strong>. Create category: Act on the first one found by the time upstreams reply.</td>
+<td>Search category: same as <strong>epff</strong>. Action category:
+same as <strong>epff</strong>. Create category: Act on the first one
+found by the time upstreams reply.</td>
 </tr>
 <tr class="even">
 <td>lfs (least free space)</td>
-<td>Search category: same as <strong>eplfs</strong>. Action category: same as <strong>eplfs</strong>. Create category: Pick the upstream with the least available free space.</td>
+<td>Search category: same as <strong>eplfs</strong>. Action category:
+same as <strong>eplfs</strong>. Create category: Pick the upstream with
+the least available free space.</td>
 </tr>
 <tr class="odd">
 <td>lus (least used space)</td>
-<td>Search category: same as <strong>eplus</strong>. Action category: same as <strong>eplus</strong>. Create category: Pick the upstream with the least used space.</td>
+<td>Search category: same as <strong>eplus</strong>. Action category:
+same as <strong>eplus</strong>. Create category: Pick the upstream with
+the least used space.</td>
 </tr>
 <tr class="even">
 <td>lno (least number of objects)</td>
-<td>Search category: same as <strong>eplno</strong>. Action category: same as <strong>eplno</strong>. Create category: Pick the upstream with the least number of objects.</td>
+<td>Search category: same as <strong>eplno</strong>. Action category:
+same as <strong>eplno</strong>. Create category: Pick the upstream with
+the least number of objects.</td>
 </tr>
 <tr class="odd">
 <td>mfs (most free space)</td>
-<td>Search category: same as <strong>epmfs</strong>. Action category: same as <strong>epmfs</strong>. Create category: Pick the upstream with the most available free space.</td>
+<td>Search category: same as <strong>epmfs</strong>. Action category:
+same as <strong>epmfs</strong>. Create category: Pick the upstream with
+the most available free space.</td>
 </tr>
 <tr class="even">
 <td>newest</td>
@@ -35493,27 +50503,41 @@ e/n/d/r/c/s/q&gt; q</code></pre>
 </tr>
 <tr class="odd">
 <td>rand (random)</td>
-<td>Calls <strong>all</strong> and then randomizes. Returns only one upstream.</td>
+<td>Calls <strong>all</strong> and then randomizes. Returns only one
+upstream.</td>
 </tr>
 </tbody>
 </table>
 <h3 id="writeback">Writeback</h3>
-<p>The tag <code>:writeback</code> on an upstream remote can be used to make a simple cache system like this:</p>
+<p>The tag <code>:writeback</code> on an upstream remote can be used to
+make a simple cache system like this:</p>
 <pre><code>[union]
 type = union
 action_policy = all
 create_policy = all
 search_policy = ff
 upstreams = /local:writeback remote:dir</code></pre>
-<p>When files are opened for read, if the file is in <code>remote:dir</code> but not <code>/local</code> then rclone will copy the file entirely into <code>/local</code> before returning a reference to the file in <code>/local</code>. The copy will be done with the equivalent of <code>rclone copy</code> so will use <code>--multi-thread-streams</code> if configured. Any copies will be logged with an INFO log.</p>
-<p>When files are written, they will be written to both <code>remote:dir</code> and <code>/local</code>.</p>
-<p>As many remotes as desired can be added to <code>upstreams</code> but there should only be one <code>:writeback</code> tag.</p>
-<p>Rclone does not manage the <code>:writeback</code> remote in any way other than writing files back to it. So if you need to expire old files or manage the size then you will have to do this yourself.</p>
-<h3 id="standard-options-54">Standard options</h3>
-<p>Here are the Standard options specific to union (Union merges the contents of several upstream fs).</p>
+<p>When files are opened for read, if the file is in
+<code>remote:dir</code> but not <code>/local</code> then rclone will
+copy the file entirely into <code>/local</code> before returning a
+reference to the file in <code>/local</code>. The copy will be done with
+the equivalent of <code>rclone copy</code> so will use
+<code>--multi-thread-streams</code> if configured. Any copies will be
+logged with an INFO log.</p>
+<p>When files are written, they will be written to both
+<code>remote:dir</code> and <code>/local</code>.</p>
+<p>As many remotes as desired can be added to <code>upstreams</code> but
+there should only be one <code>:writeback</code> tag.</p>
+<p>Rclone does not manage the <code>:writeback</code> remote in any way
+other than writing files back to it. So if you need to expire old files
+or manage the size then you will have to do this yourself.</p>
+<h3 id="standard-options-55">Standard options</h3>
+<p>Here are the Standard options specific to union (Union merges the
+contents of several upstream fs).</p>
 <h4 id="union-upstreams">--union-upstreams</h4>
 <p>List of space separated upstreams.</p>
-<p>Can be 'upstreama:test/dir upstreamb:', '"upstreama:test/space:ro dir" upstreamb:', etc.</p>
+<p>Can be 'upstreama:test/dir upstreamb:', '"upstreama:test/space:ro
+dir" upstreamb:', etc.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: upstreams</li>
@@ -35558,11 +50582,13 @@ upstreams = /local:writeback remote:dir</code></pre>
 <li>Type: int</li>
 <li>Default: 120</li>
 </ul>
-<h3 id="advanced-options-55">Advanced options</h3>
-<p>Here are the Advanced options specific to union (Union merges the contents of several upstream fs).</p>
+<h3 id="advanced-options-56">Advanced options</h3>
+<p>Here are the Advanced options specific to union (Union merges the
+contents of several upstream fs).</p>
 <h4 id="union-min-free-space">--union-min-free-space</h4>
 <p>Minimum viable free space for lfs/eplfs policies.</p>
-<p>If a remote has less than this much free space then it won't be considered for use in lfs or eplfs policies.</p>
+<p>If a remote has less than this much free space then it won't be
+considered for use in lfs or eplfs policies.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: min_free_space</li>
@@ -35580,14 +50606,20 @@ upstreams = /local:writeback remote:dir</code></pre>
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-15">Metadata</h3>
-<p>Any metadata supported by the underlying remote is read and written.</p>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>Any metadata supported by the underlying remote is read and
+written.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h1 id="webdav">WebDAV</h1>
 <p>Paths are specified as <code>remote:path</code></p>
-<p>Paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h2 id="configuration-52">Configuration</h2>
-<p>To configure the WebDAV remote you will need to have a URL for it, and a username and password. If you know what kind of system you are connecting to then rclone can enable extra features.</p>
-<p>Here is an example of how to make a remote called <code>remote</code>. First run:</p>
+<p>Paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h2 id="configuration-53">Configuration</h2>
+<p>To configure the WebDAV remote you will need to have a URL for it,
+and a username and password. If you know what kind of system you are
+connecting to then rclone can enable extra features.</p>
+<p>Here is an example of how to make a remote called
+<code>remote</code>. First run:</p>
 <pre><code> rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
 <pre><code>No remotes found, make a new one?
@@ -35659,10 +50691,17 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone ls remote:</code></pre>
 <p>To copy a local directory to an WebDAV directory called backup</p>
 <pre><code>rclone copy /home/source remote:backup</code></pre>
-<h3 id="modification-times-and-hashes-29">Modification times and hashes</h3>
-<p>Plain WebDAV does not support modified times. However when used with Fastmail Files, Owncloud or Nextcloud rclone will support modified times.</p>
-<p>Likewise plain WebDAV does not support hashes, however when used with Fastmail Files, Owncloud or Nextcloud rclone will support SHA1 and MD5 hashes. Depending on the exact version of Owncloud or Nextcloud hashes may appear on all objects, or only on objects which had a hash uploaded with them.</p>
-<h3 id="standard-options-55">Standard options</h3>
+<h3 id="modification-times-and-hashes-29">Modification times and
+hashes</h3>
+<p>Plain WebDAV does not support modified times. However when used with
+Fastmail Files, Owncloud or Nextcloud rclone will support modified
+times.</p>
+<p>Likewise plain WebDAV does not support hashes, however when used with
+Fastmail Files, Owncloud or Nextcloud rclone will support SHA1 and MD5
+hashes. Depending on the exact version of Owncloud or Nextcloud hashes
+may appear on all objects, or only on objects which had a hash uploaded
+with them.</p>
+<h3 id="standard-options-56">Standard options</h3>
 <p>Here are the Standard options specific to webdav (WebDAV).</p>
 <h4 id="webdav-url">--webdav-url</h4>
 <p>URL of http host to connect to.</p>
@@ -35702,11 +50741,13 @@ y/e/d&gt; y</code></pre>
 </ul></li>
 <li>"sharepoint-ntlm"
 <ul>
-<li>Sharepoint with NTLM authentication, usually self-hosted or on-premises</li>
+<li>Sharepoint with NTLM authentication, usually self-hosted or
+on-premises</li>
 </ul></li>
 <li>"rclone"
 <ul>
-<li>rclone WebDAV server to serve a remote over HTTP via the WebDAV protocol</li>
+<li>rclone WebDAV server to serve a remote over HTTP via the WebDAV
+protocol</li>
 </ul></li>
 <li>"other"
 <ul>
@@ -35716,7 +50757,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="webdav-user">--webdav-user</h4>
 <p>User name.</p>
-<p>In case NTLM authentication is used, the username should be in the format 'Domain'.</p>
+<p>In case NTLM authentication is used, the username should be in the
+format 'Domain'.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: user</li>
@@ -35726,7 +50768,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="webdav-pass">--webdav-pass</h4>
 <p>Password.</p>
-<p><strong>NB</strong> Input to this must be obscured - see <a href="https://rclone.org/commands/rclone_obscure/">rclone obscure</a>.</p>
+<p><strong>NB</strong> Input to this must be obscured - see <a
+href="https://rclone.org/commands/rclone_obscure/">rclone
+obscure</a>.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: pass</li>
@@ -35743,7 +50787,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-56">Advanced options</h3>
+<h3 id="advanced-options-57">Advanced options</h3>
 <p>Here are the Advanced options specific to webdav (WebDAV).</p>
 <h4 id="webdav-bearer-token-command">--webdav-bearer-token-command</h4>
 <p>Command to run to get a bearer token.</p>
@@ -35756,8 +50800,11 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="webdav-encoding">--webdav-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
-<p>Default encoding is Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8 for sharepoint-ntlm or identity otherwise.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
+<p>Default encoding is
+Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,Hash,Percent,BackSlash,Del,Ctl,LeftSpace,LeftTilde,RightSpace,RightPeriod,InvalidUtf8
+for sharepoint-ntlm or identity otherwise.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -35768,9 +50815,13 @@ y/e/d&gt; y</code></pre>
 <h4 id="webdav-headers">--webdav-headers</h4>
 <p>Set HTTP headers for all transactions.</p>
 <p>Use this to set additional HTTP headers for all transactions</p>
-<p>The input format is comma separated list of key,value pairs. Standard <a href="https://godoc.org/encoding/csv">CSV encoding</a> may be used.</p>
-<p>For example, to set a Cookie use 'Cookie,name=value', or '"Cookie","name=value"'.</p>
-<p>You can set multiple headers, e.g. '"Cookie","name=value","Authorization","xxx"'.</p>
+<p>The input format is comma separated list of key,value pairs. Standard
+<a href="https://godoc.org/encoding/csv">CSV encoding</a> may be
+used.</p>
+<p>For example, to set a Cookie use 'Cookie,name=value', or
+'"Cookie","name=value"'.</p>
+<p>You can set multiple headers, e.g.
+'"Cookie","name=value","Authorization","xxx"'.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: headers</li>
@@ -35789,7 +50840,9 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="webdav-nextcloud-chunk-size">--webdav-nextcloud-chunk-size</h4>
 <p>Nextcloud upload chunk size.</p>
-<p>We recommend configuring your NextCloud instance to increase the max chunk size to 1 GB for better upload performances. See https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#adjust-chunk-size-on-nextcloud-side</p>
+<p>We recommend configuring your NextCloud instance to increase the max
+chunk size to 1 GB for better upload performances. See
+https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/big_file_upload_configuration.html#adjust-chunk-size-on-nextcloud-side</p>
 <p>Set to 0 to disable chunked uploading.</p>
 <p>Properties:</p>
 <ul>
@@ -35798,7 +50851,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: SizeSuffix</li>
 <li>Default: 10Mi</li>
 </ul>
-<h4 id="webdav-owncloud-exclude-shares">--webdav-owncloud-exclude-shares</h4>
+<h4
+id="webdav-owncloud-exclude-shares">--webdav-owncloud-exclude-shares</h4>
 <p>Exclude ownCloud shares</p>
 <p>Properties:</p>
 <ul>
@@ -35807,7 +50861,8 @@ y/e/d&gt; y</code></pre>
 <li>Type: bool</li>
 <li>Default: false</li>
 </ul>
-<h4 id="webdav-owncloud-exclude-mounts">--webdav-owncloud-exclude-mounts</h4>
+<h4
+id="webdav-owncloud-exclude-mounts">--webdav-owncloud-exclude-mounts</h4>
 <p>Exclude ownCloud mounted storages</p>
 <p>Properties:</p>
 <ul>
@@ -35817,7 +50872,8 @@ y/e/d&gt; y</code></pre>
 <li>Default: false</li>
 </ul>
 <h4 id="webdav-unix-socket">--webdav-unix-socket</h4>
-<p>Path to a unix domain socket to dial to, instead of opening a TCP connection directly</p>
+<p>Path to a unix domain socket to dial to, instead of opening a TCP
+connection directly</p>
 <p>Properties:</p>
 <ul>
 <li>Config: unix_socket</li>
@@ -35837,23 +50893,53 @@ y/e/d&gt; y</code></pre>
 <h2 id="provider-notes">Provider notes</h2>
 <p>See below for notes on specific providers.</p>
 <h3 id="fastmail-files">Fastmail Files</h3>
-<p>Use <code>https://webdav.fastmail.com/</code> or a subdirectory as the URL, and your Fastmail email <code>username@domain.tld</code> as the username. Follow <a href="https://www.fastmail.help/hc/en-us/articles/360058752854-App-passwords">this documentation</a> to create an app password with access to <code>Files (WebDAV)</code> and use this as the password.</p>
-<p>Fastmail supports modified times using the <code>X-OC-Mtime</code> header.</p>
+<p>Use <code>https://webdav.fastmail.com/</code> or a subdirectory as
+the URL, and your Fastmail email <code>username@domain.tld</code> as the
+username. Follow <a
+href="https://www.fastmail.help/hc/en-us/articles/360058752854-App-passwords">this
+documentation</a> to create an app password with access to
+<code>Files (WebDAV)</code> and use this as the password.</p>
+<p>Fastmail supports modified times using the <code>X-OC-Mtime</code>
+header.</p>
 <h3 id="owncloud">Owncloud</h3>
-<p>Click on the settings cog in the bottom right of the page and this will show the WebDAV URL that rclone needs in the config step. It will look something like <code>https://example.com/remote.php/webdav/</code>.</p>
-<p>Owncloud supports modified times using the <code>X-OC-Mtime</code> header.</p>
+<p>Click on the settings cog in the bottom right of the page and this
+will show the WebDAV URL that rclone needs in the config step. It will
+look something like
+<code>https://example.com/remote.php/webdav/</code>.</p>
+<p>Owncloud supports modified times using the <code>X-OC-Mtime</code>
+header.</p>
 <h3 id="nextcloud">Nextcloud</h3>
-<p>This is configured in an identical way to Owncloud. Note that Nextcloud initially did not support streaming of files (<code>rcat</code>) whereas Owncloud did, but <a href="https://github.com/nextcloud/nextcloud-snap/issues/365">this</a> seems to be fixed as of 2020-11-27 (tested with rclone v1.53.1 and Nextcloud Server v19).</p>
+<p>This is configured in an identical way to Owncloud. Note that
+Nextcloud initially did not support streaming of files
+(<code>rcat</code>) whereas Owncloud did, but <a
+href="https://github.com/nextcloud/nextcloud-snap/issues/365">this</a>
+seems to be fixed as of 2020-11-27 (tested with rclone v1.53.1 and
+Nextcloud Server v19).</p>
 <h3 id="sharepoint-online">Sharepoint Online</h3>
-<p>Rclone can be used with Sharepoint provided by OneDrive for Business or Office365 Education Accounts. This feature is only needed for a few of these Accounts, mostly Office365 Education ones. These accounts are sometimes not verified by the domain owner <a href="https://github.com/rclone/rclone/issues/1975">github#1975</a></p>
-<p>This means that these accounts can't be added using the official API (other Accounts should work with the "onedrive" option). However, it is possible to access them using webdav.</p>
-<p>To use a sharepoint remote with rclone, add it like this: First, you need to get your remote's URL:</p>
+<p>Rclone can be used with Sharepoint provided by OneDrive for Business
+or Office365 Education Accounts. This feature is only needed for a few
+of these Accounts, mostly Office365 Education ones. These accounts are
+sometimes not verified by the domain owner <a
+href="https://github.com/rclone/rclone/issues/1975">github#1975</a></p>
+<p>This means that these accounts can't be added using the official API
+(other Accounts should work with the "onedrive" option). However, it is
+possible to access them using webdav.</p>
+<p>To use a sharepoint remote with rclone, add it like this: First, you
+need to get your remote's URL:</p>
 <ul>
-<li>Go <a href="https://onedrive.live.com/about/en-us/signin/">here</a> to open your OneDrive or to sign in</li>
-<li>Now take a look at your address bar, the URL should look like this: <code>https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/_layouts/15/onedrive.aspx</code></li>
+<li>Go <a href="https://onedrive.live.com/about/en-us/signin/">here</a>
+to open your OneDrive or to sign in</li>
+<li>Now take a look at your address bar, the URL should look like this:
+<code>https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/_layouts/15/onedrive.aspx</code></li>
 </ul>
-<p>You'll only need this URL up to the email address. After that, you'll most likely want to add "/Documents". That subdirectory contains the actual data stored on your OneDrive.</p>
-<p>Add the remote to rclone like this: Configure the <code>url</code> as <code>https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/Documents</code> and use your normal account email and password for <code>user</code> and <code>pass</code>. If you have 2FA enabled, you have to generate an app password. Set the <code>vendor</code> to <code>sharepoint</code>.</p>
+<p>You'll only need this URL up to the email address. After that, you'll
+most likely want to add "/Documents". That subdirectory contains the
+actual data stored on your OneDrive.</p>
+<p>Add the remote to rclone like this: Configure the <code>url</code> as
+<code>https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/Documents</code>
+and use your normal account email and password for <code>user</code> and
+<code>pass</code>. If you have 2FA enabled, you have to generate an app
+password. Set the <code>vendor</code> to <code>sharepoint</code>.</p>
 <p>Your config file should look like this:</p>
 <pre><code>[sharepoint]
 type = webdav
@@ -35861,13 +50947,20 @@ url = https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/Documents
 vendor = sharepoint
 user = YourEmailAddress
 pass = encryptedpassword</code></pre>
-<h3 id="sharepoint-with-ntlm-authentication">Sharepoint with NTLM Authentication</h3>
-<p>Use this option in case your (hosted) Sharepoint is not tied to OneDrive accounts and uses NTLM authentication.</p>
-<p>To get the <code>url</code> configuration, similarly to the above, first navigate to the desired directory in your browser to get the URL, then strip everything after the name of the opened directory.</p>
-<p>Example: If the URL is: https://example.sharepoint.com/sites/12345/Documents/Forms/AllItems.aspx</p>
-<p>The configuration to use would be: https://example.sharepoint.com/sites/12345/Documents</p>
+<h3 id="sharepoint-with-ntlm-authentication">Sharepoint with NTLM
+Authentication</h3>
+<p>Use this option in case your (hosted) Sharepoint is not tied to
+OneDrive accounts and uses NTLM authentication.</p>
+<p>To get the <code>url</code> configuration, similarly to the above,
+first navigate to the desired directory in your browser to get the URL,
+then strip everything after the name of the opened directory.</p>
+<p>Example: If the URL is:
+https://example.sharepoint.com/sites/12345/Documents/Forms/AllItems.aspx</p>
+<p>The configuration to use would be:
+https://example.sharepoint.com/sites/12345/Documents</p>
 <p>Set the <code>vendor</code> to <code>sharepoint-ntlm</code>.</p>
-<p>NTLM uses domain and user name combination for authentication, set <code>user</code> to <code>DOMAIN\username</code>.</p>
+<p>NTLM uses domain and user name combination for authentication, set
+<code>user</code> to <code>DOMAIN\username</code>.</p>
 <p>Your config file should look like this:</p>
 <pre><code>[sharepoint]
 type = webdav
@@ -35875,16 +50968,34 @@ url = https://[YOUR-DOMAIN]/some-path-to/Documents
 vendor = sharepoint-ntlm
 user = DOMAIN\user
 pass = encryptedpassword</code></pre>
-<h4 id="required-flags-for-sharepoint">Required Flags for SharePoint</h4>
-<p>As SharePoint does some special things with uploaded documents, you won't be able to use the documents size or the documents hash to compare if a file has been changed since the upload / which file is newer.</p>
-<p>For Rclone calls copying files (especially Office files such as .docx, .xlsx, etc.) from/to SharePoint (like copy, sync, etc.), you should append these flags to ensure Rclone uses the "Last Modified" datetime property to compare your documents:</p>
+<h4 id="required-flags-for-sharepoint">Required Flags for
+SharePoint</h4>
+<p>As SharePoint does some special things with uploaded documents, you
+won't be able to use the documents size or the documents hash to compare
+if a file has been changed since the upload / which file is newer.</p>
+<p>For Rclone calls copying files (especially Office files such as
+.docx, .xlsx, etc.) from/to SharePoint (like copy, sync, etc.), you
+should append these flags to ensure Rclone uses the "Last Modified"
+datetime property to compare your documents:</p>
 <pre><code>--ignore-size --ignore-checksum --update</code></pre>
 <h2 id="rclone-1">Rclone</h2>
-<p>Use this option if you are hosting remotes over WebDAV provided by rclone. Read <a href="commands/rclone_serve_webdav/">rclone serve webdav</a> for more details.</p>
-<p>rclone serve supports modified times using the <code>X-OC-Mtime</code> header.</p>
+<p>Use this option if you are hosting remotes over WebDAV provided by
+rclone. Read <a href="commands/rclone_serve_webdav/">rclone serve
+webdav</a> for more details.</p>
+<p>rclone serve supports modified times using the
+<code>X-OC-Mtime</code> header.</p>
 <h3 id="dcache">dCache</h3>
-<p>dCache is a storage system that supports many protocols and authentication/authorisation schemes. For WebDAV clients, it allows users to authenticate with username and password (BASIC), X.509, Kerberos, and various bearer tokens, including <a href="https://www.dcache.org/manuals/workshop-2017-05-29-Umea/000-Final/anupam_macaroons_v02.pdf">Macaroons</a> and <a href="https://en.wikipedia.org/wiki/OpenID_Connect">OpenID-Connect</a> access tokens.</p>
-<p>Configure as normal using the <code>other</code> type. Don't enter a username or password, instead enter your Macaroon as the <code>bearer_token</code>.</p>
+<p>dCache is a storage system that supports many protocols and
+authentication/authorisation schemes. For WebDAV clients, it allows
+users to authenticate with username and password (BASIC), X.509,
+Kerberos, and various bearer tokens, including <a
+href="https://www.dcache.org/manuals/workshop-2017-05-29-Umea/000-Final/anupam_macaroons_v02.pdf">Macaroons</a>
+and <a
+href="https://en.wikipedia.org/wiki/OpenID_Connect">OpenID-Connect</a>
+access tokens.</p>
+<p>Configure as normal using the <code>other</code> type. Don't enter a
+username or password, instead enter your Macaroon as the
+<code>bearer_token</code>.</p>
 <p>The config will end up looking something like this.</p>
 <pre><code>[dcache]
 type = webdav
@@ -35893,26 +51004,54 @@ vendor = other
 user =
 pass =
 bearer_token = your-macaroon</code></pre>
-<p>There is a <a href="https://github.com/sara-nl/GridScripts/blob/master/get-macaroon">script</a> that obtains a Macaroon from a dCache WebDAV endpoint, and creates an rclone config file.</p>
-<p>Macaroons may also be obtained from the dCacheView web-browser/JavaScript client that comes with dCache.</p>
+<p>There is a <a
+href="https://github.com/sara-nl/GridScripts/blob/master/get-macaroon">script</a>
+that obtains a Macaroon from a dCache WebDAV endpoint, and creates an
+rclone config file.</p>
+<p>Macaroons may also be obtained from the dCacheView
+web-browser/JavaScript client that comes with dCache.</p>
 <h3 id="openid-connect">OpenID-Connect</h3>
-<p>dCache also supports authenticating with OpenID-Connect access tokens. OpenID-Connect is a protocol (based on OAuth 2.0) that allows services to identify users who have authenticated with some central service.</p>
-<p>Support for OpenID-Connect in rclone is currently achieved using another software package called <a href="https://github.com/indigo-dc/oidc-agent">oidc-agent</a>. This is a command-line tool that facilitates obtaining an access token. Once installed and configured, an access token is obtained by running the <code>oidc-token</code> command. The following example shows a (shortened) access token obtained from the <em>XDC</em> OIDC Provider.</p>
+<p>dCache also supports authenticating with OpenID-Connect access
+tokens. OpenID-Connect is a protocol (based on OAuth 2.0) that allows
+services to identify users who have authenticated with some central
+service.</p>
+<p>Support for OpenID-Connect in rclone is currently achieved using
+another software package called <a
+href="https://github.com/indigo-dc/oidc-agent">oidc-agent</a>. This is a
+command-line tool that facilitates obtaining an access token. Once
+installed and configured, an access token is obtained by running the
+<code>oidc-token</code> command. The following example shows a
+(shortened) access token obtained from the <em>XDC</em> OIDC
+Provider.</p>
 <pre><code>paul@celebrimbor:~$ oidc-token XDC
 eyJraWQ[...]QFXDt0
 paul@celebrimbor:~$</code></pre>
-<p><strong>Note</strong> Before the <code>oidc-token</code> command will work, the refresh token must be loaded into the oidc agent. This is done with the <code>oidc-add</code> command (e.g., <code>oidc-add XDC</code>). This is typically done once per login session. Full details on this and how to register oidc-agent with your OIDC Provider are provided in the <a href="https://indigo-dc.gitbooks.io/oidc-agent/">oidc-agent documentation</a>.</p>
-<p>The rclone <code>bearer_token_command</code> configuration option is used to fetch the access token from oidc-agent.</p>
-<p>Configure as a normal WebDAV endpoint, using the 'other' vendor, leaving the username and password empty. When prompted, choose to edit the advanced config and enter the command to get a bearer token (e.g., <code>oidc-agent XDC</code>).</p>
-<p>The following example config shows a WebDAV endpoint that uses oidc-agent to supply an access token from the <em>XDC</em> OIDC Provider.</p>
+<p><strong>Note</strong> Before the <code>oidc-token</code> command will
+work, the refresh token must be loaded into the oidc agent. This is done
+with the <code>oidc-add</code> command (e.g.,
+<code>oidc-add XDC</code>). This is typically done once per login
+session. Full details on this and how to register oidc-agent with your
+OIDC Provider are provided in the <a
+href="https://indigo-dc.gitbooks.io/oidc-agent/">oidc-agent
+documentation</a>.</p>
+<p>The rclone <code>bearer_token_command</code> configuration option is
+used to fetch the access token from oidc-agent.</p>
+<p>Configure as a normal WebDAV endpoint, using the 'other' vendor,
+leaving the username and password empty. When prompted, choose to edit
+the advanced config and enter the command to get a bearer token (e.g.,
+<code>oidc-agent XDC</code>).</p>
+<p>The following example config shows a WebDAV endpoint that uses
+oidc-agent to supply an access token from the <em>XDC</em> OIDC
+Provider.</p>
 <pre><code>[dcache]
 type = webdav
 url = https://dcache.example.org/
 vendor = other
 bearer_token_command = oidc-token XDC</code></pre>
 <h1 id="yandex-disk">Yandex Disk</h1>
-<p><a href="https://disk.yandex.com">Yandex Disk</a> is a cloud storage solution created by <a href="https://yandex.com">Yandex</a>.</p>
-<h2 id="configuration-53">Configuration</h2>
+<p><a href="https://disk.yandex.com">Yandex Disk</a> is a cloud storage
+solution created by <a href="https://yandex.com">Yandex</a>.</p>
+<h2 id="configuration-54">Configuration</h2>
 <p>Here is an example of making a yandex configuration. First run</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
@@ -35955,8 +51094,14 @@ y) Yes this is OK
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; y</code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Note that rclone runs a webserver on your local machine to collect the token as returned from Yandex Disk. This only runs from the moment it opens your browser to the moment you get back the verification code. This is on <code>http://127.0.0.1:53682/</code> and this it may require you to unblock it temporarily if you are running a host firewall.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Note that rclone runs a webserver on your local machine to collect
+the token as returned from Yandex Disk. This only runs from the moment
+it opens your browser to the moment you get back the verification code.
+This is on <code>http://127.0.0.1:53682/</code> and this it may require
+you to unblock it temporarily if you are running a host firewall.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>See top level directories</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -35964,20 +51109,35 @@ y/e/d&gt; y</code></pre>
 <pre><code>rclone mkdir remote:directory</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls remote:directory</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote path, deleting any excess files in the path.</p>
+<p>Sync <code>/home/local/directory</code> to the remote path, deleting
+any excess files in the path.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:directory</code></pre>
-<p>Yandex paths may be as deep as required, e.g. <code>remote:directory/subdirectory</code>.</p>
-<h3 id="modification-times-and-hashes-30">Modification times and hashes</h3>
-<p>Modified times are supported and are stored accurate to 1 ns in custom metadata called <code>rclone_modified</code> in RFC3339 with nanoseconds format.</p>
+<p>Yandex paths may be as deep as required, e.g.
+<code>remote:directory/subdirectory</code>.</p>
+<h3 id="modification-times-and-hashes-30">Modification times and
+hashes</h3>
+<p>Modified times are supported and are stored accurate to 1 ns in
+custom metadata called <code>rclone_modified</code> in RFC3339 with
+nanoseconds format.</p>
 <p>The MD5 hash algorithm is natively supported by Yandex Disk.</p>
 <h3 id="emptying-trash-2">Emptying Trash</h3>
-<p>If you wish to empty your trash you can use the <code>rclone cleanup remote:</code> command which will permanently delete all your trashed files. This command does not take any path arguments.</p>
+<p>If you wish to empty your trash you can use the
+<code>rclone cleanup remote:</code> command which will permanently
+delete all your trashed files. This command does not take any path
+arguments.</p>
 <h3 id="quota-information-3">Quota information</h3>
-<p>To view your current quota you can use the <code>rclone about remote:</code> command which will display your usage limit (quota) and the current usage.</p>
-<h3 id="restricted-filename-characters-34">Restricted filename characters</h3>
-<p>The <a href="https://rclone.org/overview/#restricted-characters">default restricted characters set</a> are replaced.</p>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be used in JSON strings.</p>
-<h3 id="standard-options-56">Standard options</h3>
+<p>To view your current quota you can use the
+<code>rclone about remote:</code> command which will display your usage
+limit (quota) and the current usage.</p>
+<h3 id="restricted-filename-characters-33">Restricted filename
+characters</h3>
+<p>The <a
+href="https://rclone.org/overview/#restricted-characters">default
+restricted characters set</a> are replaced.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be used in JSON strings.</p>
+<h3 id="standard-options-57">Standard options</h3>
 <p>Here are the Standard options specific to yandex (Yandex Disk).</p>
 <h4 id="yandex-client-id">--yandex-client-id</h4>
 <p>OAuth Client Id.</p>
@@ -35999,7 +51159,7 @@ y/e/d&gt; y</code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h3 id="advanced-options-57">Advanced options</h3>
+<h3 id="advanced-options-58">Advanced options</h3>
 <p>Here are the Advanced options specific to yandex (Yandex Disk).</p>
 <h4 id="yandex-token">--yandex-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
@@ -36041,7 +51201,8 @@ y/e/d&gt; y</code></pre>
 </ul>
 <h4 id="yandex-encoding">--yandex-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -36050,7 +51211,8 @@ y/e/d&gt; y</code></pre>
 <li>Default: Slash,Del,Ctl,InvalidUtf8,Dot</li>
 </ul>
 <h4 id="yandex-spoof-ua">--yandex-spoof-ua</h4>
-<p>Set the user agent to match an official version of the yandex disk client. May help with upload performance.</p>
+<p>Set the user agent to match an official version of the yandex disk
+client. May help with upload performance.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: spoof_ua</li>
@@ -36068,12 +51230,26 @@ y/e/d&gt; y</code></pre>
 <li>Required: false</li>
 </ul>
 <h2 id="limitations-41">Limitations</h2>
-<p>When uploading very large files (bigger than about 5 GiB) you will need to increase the <code>--timeout</code> parameter. This is because Yandex pauses (perhaps to calculate the MD5SUM for the entire file) before returning confirmation that the file has been uploaded. The default handling of timeouts in rclone is to assume a 5 minute pause is an error and close the connection - you'll see <code>net/http: timeout awaiting response headers</code> errors in the logs if this is happening. Setting the timeout to twice the max size of file in GiB should be enough, so if you want to upload a 30 GiB file set a timeout of <code>2 * 30 = 60m</code>, that is <code>--timeout 60m</code>.</p>
-<p>Having a Yandex Mail account is mandatory to use the Yandex.Disk subscription. Token generation will work without a mail account, but Rclone won't be able to complete any actions.</p>
+<p>When uploading very large files (bigger than about 5 GiB) you will
+need to increase the <code>--timeout</code> parameter. This is because
+Yandex pauses (perhaps to calculate the MD5SUM for the entire file)
+before returning confirmation that the file has been uploaded. The
+default handling of timeouts in rclone is to assume a 5 minute pause is
+an error and close the connection - you'll see
+<code>net/http: timeout awaiting response headers</code> errors in the
+logs if this is happening. Setting the timeout to twice the max size of
+file in GiB should be enough, so if you want to upload a 30 GiB file set
+a timeout of <code>2 * 30 = 60m</code>, that is
+<code>--timeout 60m</code>.</p>
+<p>Having a Yandex Mail account is mandatory to use the Yandex.Disk
+subscription. Token generation will work without a mail account, but
+Rclone won't be able to complete any actions.</p>
 <pre><code>[403 - DiskUnsupportedUserAccountTypeError] User account type is not supported.</code></pre>
 <h1 id="zoho-workdrive">Zoho Workdrive</h1>
-<p><a href="https://www.zoho.com/workdrive/">Zoho WorkDrive</a> is a cloud storage solution created by <a href="https://zoho.com">Zoho</a>.</p>
-<h2 id="configuration-54">Configuration</h2>
+<p><a href="https://www.zoho.com/workdrive/">Zoho WorkDrive</a> is a
+cloud storage solution created by <a
+href="https://zoho.com">Zoho</a>.</p>
+<h2 id="configuration-55">Configuration</h2>
 <p>Here is an example of making a zoho configuration. First run</p>
 <pre><code>rclone config</code></pre>
 <p>This will guide you through an interactive setup process:</p>
@@ -36134,8 +51310,15 @@ y) Yes this is OK (default)
 e) Edit this remote
 d) Delete this remote
 y/e/d&gt; </code></pre>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for how to set it up on a machine with no Internet browser available.</p>
-<p>Rclone runs a webserver on your local computer to collect the authorization token from Zoho Workdrive. This is only from the moment your browser is opened until the token is returned. The webserver runs on <code>http://127.0.0.1:53682/</code>. If local port <code>53682</code> is protected by a firewall you may need to temporarily unblock the firewall to complete authorization.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for how to set it up on a machine with no Internet browser
+available.</p>
+<p>Rclone runs a webserver on your local computer to collect the
+authorization token from Zoho Workdrive. This is only from the moment
+your browser is opened until the token is returned. The webserver runs
+on <code>http://127.0.0.1:53682/</code>. If local port
+<code>53682</code> is protected by a firewall you may need to
+temporarily unblock the firewall to complete authorization.</p>
 <p>Once configured you can then use <code>rclone</code> like this,</p>
 <p>See top level directories</p>
 <pre><code>rclone lsd remote:</code></pre>
@@ -36143,17 +51326,25 @@ y/e/d&gt; </code></pre>
 <pre><code>rclone mkdir remote:directory</code></pre>
 <p>List the contents of a directory</p>
 <pre><code>rclone ls remote:directory</code></pre>
-<p>Sync <code>/home/local/directory</code> to the remote path, deleting any excess files in the path.</p>
+<p>Sync <code>/home/local/directory</code> to the remote path, deleting
+any excess files in the path.</p>
 <pre><code>rclone sync --interactive /home/local/directory remote:directory</code></pre>
-<p>Zoho paths may be as deep as required, eg <code>remote:directory/subdirectory</code>.</p>
-<h3 id="modification-times-and-hashes-31">Modification times and hashes</h3>
+<p>Zoho paths may be as deep as required, eg
+<code>remote:directory/subdirectory</code>.</p>
+<h3 id="modification-times-and-hashes-31">Modification times and
+hashes</h3>
 <p>Modified times are currently not supported for Zoho Workdrive</p>
 <p>No hash algorithms are supported.</p>
 <h3 id="usage-information-1">Usage information</h3>
-<p>To view your current quota you can use the <code>rclone about remote:</code> command which will display your current usage.</p>
-<h3 id="restricted-filename-characters-35">Restricted filename characters</h3>
-<p>Only control characters and invalid UTF-8 are replaced. In addition most Unicode full-width characters are not supported at all and will be removed from filenames during upload.</p>
-<h3 id="standard-options-57">Standard options</h3>
+<p>To view your current quota you can use the
+<code>rclone about remote:</code> command which will display your
+current usage.</p>
+<h3 id="restricted-filename-characters-34">Restricted filename
+characters</h3>
+<p>Only control characters and invalid UTF-8 are replaced. In addition
+most Unicode full-width characters are not supported at all and will be
+removed from filenames during upload.</p>
+<h3 id="standard-options-58">Standard options</h3>
 <p>Here are the Standard options specific to zoho (Zoho).</p>
 <h4 id="zoho-client-id">--zoho-client-id</h4>
 <p>OAuth Client Id.</p>
@@ -36177,7 +51368,9 @@ y/e/d&gt; </code></pre>
 </ul>
 <h4 id="zoho-region">--zoho-region</h4>
 <p>Zoho region to connect to.</p>
-<p>You'll have to use the region your organization is registered in. If not sure use the same top level domain as you connect to in your browser.</p>
+<p>You'll have to use the region your organization is registered in. If
+not sure use the same top level domain as you connect to in your
+browser.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: region</li>
@@ -36212,7 +51405,7 @@ y/e/d&gt; </code></pre>
 </ul></li>
 </ul></li>
 </ul>
-<h3 id="advanced-options-58">Advanced options</h3>
+<h3 id="advanced-options-59">Advanced options</h3>
 <p>Here are the Advanced options specific to zoho (Zoho).</p>
 <h4 id="zoho-token">--zoho-token</h4>
 <p>OAuth Access Token as a JSON blob.</p>
@@ -36245,7 +51438,8 @@ y/e/d&gt; </code></pre>
 </ul>
 <h4 id="zoho-encoding">--zoho-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -36262,30 +51456,56 @@ y/e/d&gt; </code></pre>
 <li>Type: string</li>
 <li>Required: false</li>
 </ul>
-<h2 id="setting-up-your-own-client_id">Setting up your own client_id</h2>
-<p>For Zoho we advise you to set up your own client_id. To do so you have to complete the following steps.</p>
+<h2 id="setting-up-your-own-client_id">Setting up your own
+client_id</h2>
+<p>For Zoho we advise you to set up your own client_id. To do so you
+have to complete the following steps.</p>
 <ol type="1">
-<li><p>Log in to the <a href="https://api-console.zoho.com">Zoho API Console</a></p></li>
-<li><p>Create a new client of type "Server-based Application". The name and website don't matter, but you must add the redirect URL <code>http://localhost:53682/</code>.</p></li>
-<li><p>Once the client is created, you can go to the settings tab and enable it in other regions.</p></li>
+<li><p>Log in to the <a href="https://api-console.zoho.com">Zoho API
+Console</a></p></li>
+<li><p>Create a new client of type "Server-based Application". The name
+and website don't matter, but you must add the redirect URL
+<code>http://localhost:53682/</code>.</p></li>
+<li><p>Once the client is created, you can go to the settings tab and
+enable it in other regions.</p></li>
 </ol>
 <p>The client id and client secret can now be used with rclone.</p>
 <h1 id="local-filesystem">Local Filesystem</h1>
-<p>Local paths are specified as normal filesystem paths, e.g. <code>/path/to/wherever</code>, so</p>
+<p>Local paths are specified as normal filesystem paths, e.g.
+<code>/path/to/wherever</code>, so</p>
 <pre><code>rclone sync --interactive /home/source /tmp/destination</code></pre>
-<p>Will sync <code>/home/source</code> to <code>/tmp/destination</code>.</p>
-<h2 id="configuration-55">Configuration</h2>
-<p>For consistencies sake one can also configure a remote of type <code>local</code> in the config file, and access the local filesystem using rclone remote paths, e.g. <code>remote:path/to/wherever</code>, but it is probably easier not to.</p>
+<p>Will sync <code>/home/source</code> to
+<code>/tmp/destination</code>.</p>
+<h2 id="configuration-56">Configuration</h2>
+<p>For consistencies sake one can also configure a remote of type
+<code>local</code> in the config file, and access the local filesystem
+using rclone remote paths, e.g. <code>remote:path/to/wherever</code>,
+but it is probably easier not to.</p>
 <h3 id="modification-times-9">Modification times</h3>
-<p>Rclone reads and writes the modification times using an accuracy determined by the OS. Typically this is 1ns on Linux, 10 ns on Windows and 1 Second on OS X.</p>
+<p>Rclone reads and writes the modification times using an accuracy
+determined by the OS. Typically this is 1ns on Linux, 10 ns on Windows
+and 1 Second on OS X.</p>
 <h3 id="filenames">Filenames</h3>
-<p>Filenames should be encoded in UTF-8 on disk. This is the normal case for Windows and OS X.</p>
-<p>There is a bit more uncertainty in the Linux world, but new distributions will have UTF-8 encoded files names. If you are using an old Linux filesystem with non UTF-8 file names (e.g. latin1) then you can use the <code>convmv</code> tool to convert the filesystem to UTF-8. This tool is available in most distributions' package managers.</p>
-<p>If an invalid (non-UTF8) filename is read, the invalid characters will be replaced with a quoted representation of the invalid bytes. The name <code>gro\xdf</code> will be transferred as <code>gro‛DF</code>. <code>rclone</code> will emit a debug message in this case (use <code>-v</code> to see), e.g.</p>
+<p>Filenames should be encoded in UTF-8 on disk. This is the normal case
+for Windows and OS X.</p>
+<p>There is a bit more uncertainty in the Linux world, but new
+distributions will have UTF-8 encoded files names. If you are using an
+old Linux filesystem with non UTF-8 file names (e.g. latin1) then you
+can use the <code>convmv</code> tool to convert the filesystem to UTF-8.
+This tool is available in most distributions' package managers.</p>
+<p>If an invalid (non-UTF8) filename is read, the invalid characters
+will be replaced with a quoted representation of the invalid bytes. The
+name <code>gro\xdf</code> will be transferred as <code>gro‛DF</code>.
+<code>rclone</code> will emit a debug message in this case (use
+<code>-v</code> to see), e.g.</p>
 <pre><code>Local file system at .: Replacing invalid UTF-8 characters in &quot;gro\xdf&quot;</code></pre>
 <h4 id="restricted-characters-1">Restricted characters</h4>
-<p>With the local backend, restrictions on the characters that are usable in file or directory names depend on the operating system. To check what rclone will replace by default on your system, run <code>rclone help flags local-encoding</code>.</p>
-<p>On non Windows platforms the following characters are replaced when handling file names.</p>
+<p>With the local backend, restrictions on the characters that are
+usable in file or directory names depend on the operating system. To
+check what rclone will replace by default on your system, run
+<code>rclone help flags local-encoding</code>.</p>
+<p>On non Windows platforms the following characters are replaced when
+handling file names.</p>
 <table>
 <thead>
 <tr class="header">
@@ -36307,7 +51527,10 @@ y/e/d&gt; </code></pre>
 </tr>
 </tbody>
 </table>
-<p>When running on Windows the following characters are replaced. This list is based on the <a href="https://docs.microsoft.com/de-de/windows/desktop/FileIO/naming-a-file#naming-conventions">Windows file naming conventions</a>.</p>
+<p>When running on Windows the following characters are replaced. This
+list is based on the <a
+href="https://docs.microsoft.com/de-de/windows/desktop/FileIO/naming-a-file#naming-conventions">Windows
+file naming conventions</a>.</p>
 <table>
 <thead>
 <tr class="header">
@@ -36524,7 +51747,8 @@ y/e/d&gt; </code></pre>
 </tr>
 </tbody>
 </table>
-<p>File names on Windows can also not end with the following characters. These only get replaced if they are the last character in the name:</p>
+<p>File names on Windows can also not end with the following characters.
+These only get replaced if they are the last character in the name:</p>
 <table>
 <thead>
 <tr class="header">
@@ -36546,25 +51770,63 @@ y/e/d&gt; </code></pre>
 </tr>
 </tbody>
 </table>
-<p>Invalid UTF-8 bytes will also be <a href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they can't be converted to UTF-16.</p>
+<p>Invalid UTF-8 bytes will also be <a
+href="https://rclone.org/overview/#invalid-utf8">replaced</a>, as they
+can't be converted to UTF-16.</p>
 <h3 id="paths-on-windows">Paths on Windows</h3>
-<p>On Windows there are many ways of specifying a path to a file system resource. Local paths can be absolute, like <code>C:\path\to\wherever</code>, or relative, like <code>..\wherever</code>. Network paths in UNC format, <code>\\server\share</code>, are also supported. Path separator can be either <code>\</code> (as in <code>C:\path\to\wherever</code>) or <code>/</code> (as in <code>C:/path/to/wherever</code>). Length of these paths are limited to 259 characters for files and 247 characters for directories, but there is an alternative extended-length path format increasing the limit to (approximately) 32,767 characters. This format requires absolute paths and the use of prefix <code>\\?\</code>, e.g. <code>\\?\D:\some\very\long\path</code>. For convenience rclone will automatically convert regular paths into the corresponding extended-length paths, so in most cases you do not have to worry about this (read more <a href="#long-paths">below</a>). Using the same prefix <code>\\?\</code> it is also possible to specify path to volumes identified by their GUID, e.g. <code>\\?\Volume{b75e2c83-0000-0000-0000-602f00000000}\some\path</code>.</p>
+<p>On Windows there are many ways of specifying a path to a file system
+resource. Local paths can be absolute, like
+<code>C:\path\to\wherever</code>, or relative, like
+<code>..\wherever</code>. Network paths in UNC format,
+<code>\\server\share</code>, are also supported. Path separator can be
+either <code>\</code> (as in <code>C:\path\to\wherever</code>) or
+<code>/</code> (as in <code>C:/path/to/wherever</code>). Length of these
+paths are limited to 259 characters for files and 247 characters for
+directories, but there is an alternative extended-length path format
+increasing the limit to (approximately) 32,767 characters. This format
+requires absolute paths and the use of prefix <code>\\?\</code>, e.g.
+<code>\\?\D:\some\very\long\path</code>. For convenience rclone will
+automatically convert regular paths into the corresponding
+extended-length paths, so in most cases you do not have to worry about
+this (read more <a href="#long-paths">below</a>). Using the same prefix
+<code>\\?\</code> it is also possible to specify path to volumes
+identified by their GUID, e.g.
+<code>\\?\Volume{b75e2c83-0000-0000-0000-602f00000000}\some\path</code>.</p>
 <h4 id="long-paths">Long paths</h4>
-<p>Rclone handles long paths automatically, by converting all paths to <a href="https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation">extended-length path format</a>, which allows paths up to 32,767 characters.</p>
-<p>This conversion will ensure paths are absolute and prefix them with the <code>\\?\</code>. This is why you will see that your paths, for instance <code>.\files</code> is shown as path <code>\\?\C:\files</code> in the output, and <code>\\server\share</code> as <code>\\?\UNC\server\share</code>.</p>
-<p>However, in rare cases this may cause problems with buggy file system drivers like <a href="https://github.com/rclone/rclone/issues/261">EncFS</a>. To disable UNC conversion globally, add this to your <code>.rclone.conf</code> file:</p>
+<p>Rclone handles long paths automatically, by converting all paths to
+<a
+href="https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation">extended-length
+path format</a>, which allows paths up to 32,767 characters.</p>
+<p>This conversion will ensure paths are absolute and prefix them with
+the <code>\\?\</code>. This is why you will see that your paths, for
+instance <code>.\files</code> is shown as path <code>\\?\C:\files</code>
+in the output, and <code>\\server\share</code> as
+<code>\\?\UNC\server\share</code>.</p>
+<p>However, in rare cases this may cause problems with buggy file system
+drivers like <a
+href="https://github.com/rclone/rclone/issues/261">EncFS</a>. To disable
+UNC conversion globally, add this to your <code>.rclone.conf</code>
+file:</p>
 <pre><code>[local]
 nounc = true</code></pre>
-<p>If you want to selectively disable UNC, you can add it to a separate entry like this:</p>
+<p>If you want to selectively disable UNC, you can add it to a separate
+entry like this:</p>
 <pre><code>[nounc]
 type = local
 nounc = true</code></pre>
 <p>And use rclone like this:</p>
 <p><code>rclone copy c:\src nounc:z:\dst</code></p>
-<p>This will use UNC paths on <code>c:\src</code> but not on <code>z:\dst</code>. Of course this will cause problems if the absolute path length of a file exceeds 259 characters on z, so only use this option if you have to.</p>
+<p>This will use UNC paths on <code>c:\src</code> but not on
+<code>z:\dst</code>. Of course this will cause problems if the absolute
+path length of a file exceeds 259 characters on z, so only use this
+option if you have to.</p>
 <h3 id="symlinks-junction-points">Symlinks / Junction points</h3>
-<p>Normally rclone will ignore symlinks or junction points (which behave like symlinks under Windows).</p>
-<p>If you supply <code>--copy-links</code> or <code>-L</code> then rclone will follow the symlink and copy the pointed to file or directory. Note that this flag is incompatible with <code>--links</code> / <code>-l</code>.</p>
+<p>Normally rclone will ignore symlinks or junction points (which behave
+like symlinks under Windows).</p>
+<p>If you supply <code>--copy-links</code> or <code>-L</code> then
+rclone will follow the symlink and copy the pointed to file or
+directory. Note that this flag is incompatible with <code>--links</code>
+/ <code>-l</code>.</p>
 <p>This flag applies to all commands.</p>
 <p>For example, supposing you have a directory structure like this</p>
 <pre><code>$ tree /tmp/a
@@ -36574,7 +51836,8 @@ nounc = true</code></pre>
 ├── one
 └── two
     └── three</code></pre>
-<p>Then you can see the difference with and without the flag like this</p>
+<p>Then you can see the difference with and without the flag like
+this</p>
 <pre><code>$ rclone ls /tmp/a
         6 one
         6 two/three</code></pre>
@@ -36586,9 +51849,13 @@ nounc = true</code></pre>
         6 b/two
         6 b/one</code></pre>
 <h4 id="links--l">--links, -l</h4>
-<p>Normally rclone will ignore symlinks or junction points (which behave like symlinks under Windows).</p>
-<p>If you supply this flag then rclone will copy symbolic links from the local storage, and store them as text files, with a '.rclonelink' suffix in the remote storage.</p>
-<p>The text file will contain the target of the symbolic link (see example).</p>
+<p>Normally rclone will ignore symlinks or junction points (which behave
+like symlinks under Windows).</p>
+<p>If you supply this flag then rclone will copy symbolic links from the
+local storage, and store them as text files, with a '.rclonelink' suffix
+in the remote storage.</p>
+<p>The text file will contain the target of the symbolic link (see
+example).</p>
 <p>This flag applies to all commands.</p>
 <p>For example, supposing you have a directory structure like this</p>
 <pre><code>$ tree /tmp/a
@@ -36621,16 +51888,21 @@ $ tree /tmp/b
 /tmp/b
 ├── file1.rclonelink
 └── file2.rclonelink</code></pre>
-<p>If you want to copy a single file with <code>-l</code> then you must use the <code>.rclonelink</code> suffix.</p>
+<p>If you want to copy a single file with <code>-l</code> then you must
+use the <code>.rclonelink</code> suffix.</p>
 <pre><code>$ rclone copy -l remote:/tmp/a/file1.rclonelink /tmp/c
 
 $ tree /tmp/c
 /tmp/c
 └── file1 -&gt; ./file4</code></pre>
-<p>Note that this flag is incompatible with <code>-copy-links</code> / <code>-L</code>.</p>
-<h3 id="restricting-filesystems-with---one-file-system">Restricting filesystems with --one-file-system</h3>
+<p>Note that this flag is incompatible with <code>-copy-links</code> /
+<code>-L</code>.</p>
+<h3 id="restricting-filesystems-with---one-file-system">Restricting
+filesystems with --one-file-system</h3>
 <p>Normally rclone will recurse through filesystems as mounted.</p>
-<p>However if you set <code>--one-file-system</code> or <code>-x</code> this tells rclone to stay in the filesystem specified by the root and not to recurse into different file systems.</p>
+<p>However if you set <code>--one-file-system</code> or <code>-x</code>
+this tells rclone to stay in the filesystem specified by the root and
+not to recurse into different file systems.</p>
 <p>For example if you have a directory hierarchy like this</p>
 <pre><code>root
 ├── disk1     - disk1 mounted on the root
@@ -36639,7 +51911,8 @@ $ tree /tmp/c
 │   └── file4 - stored on disk12
 ├── file1     - stored on the root disk
 └── file2     - stored on the root disk</code></pre>
-<p>Using <code>rclone --one-file-system copy root remote:</code> will only copy <code>file1</code> and <code>file2</code>. Eg</p>
+<p>Using <code>rclone --one-file-system copy root remote:</code> will
+only copy <code>file1</code> and <code>file2</code>. Eg</p>
 <pre><code>$ rclone -q --one-file-system ls root
         0 file1
         0 file2</code></pre>
@@ -36648,9 +51921,13 @@ $ tree /tmp/c
         0 disk2/file4
         0 file1
         0 file2</code></pre>
-<p><strong>NB</strong> Rclone (like most unix tools such as <code>du</code>, <code>rsync</code> and <code>tar</code>) treats a bind mount to the same device as being on the same filesystem.</p>
-<p><strong>NB</strong> This flag is only available on Unix based systems. On systems where it isn't supported (e.g. Windows) it will be ignored.</p>
-<h3 id="advanced-options-59">Advanced options</h3>
+<p><strong>NB</strong> Rclone (like most unix tools such as
+<code>du</code>, <code>rsync</code> and <code>tar</code>) treats a bind
+mount to the same device as being on the same filesystem.</p>
+<p><strong>NB</strong> This flag is only available on Unix based
+systems. On systems where it isn't supported (e.g. Windows) it will be
+ignored.</p>
+<h3 id="advanced-options-60">Advanced options</h3>
 <p>Here are the Advanced options specific to local (Local Disk).</p>
 <h4 id="local-nounc">--local-nounc</h4>
 <p>Disable UNC (long path names) conversion on Windows.</p>
@@ -36678,7 +51955,8 @@ $ tree /tmp/c
 <li>Default: false</li>
 </ul>
 <h4 id="links--l-1">--links / -l</h4>
-<p>Translate symlinks to/from regular files with a '.rclonelink' extension.</p>
+<p>Translate symlinks to/from regular files with a '.rclonelink'
+extension.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: links</li>
@@ -36688,7 +51966,8 @@ $ tree /tmp/c
 </ul>
 <h4 id="skip-links">--skip-links</h4>
 <p>Don't warn about skipped symlinks.</p>
-<p>This flag disables warning messages on skipped symlinks or junction points, as you explicitly acknowledge that they should be skipped.</p>
+<p>This flag disables warning messages on skipped symlinks or junction
+points, as you explicitly acknowledge that they should be skipped.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: skip_links</li>
@@ -36697,8 +51976,10 @@ $ tree /tmp/c
 <li>Default: false</li>
 </ul>
 <h4 id="local-zero-size-links">--local-zero-size-links</h4>
-<p>Assume the Stat size of links is zero (and read them instead) (deprecated).</p>
-<p>Rclone used to use the Stat size of links as the link size, but this fails in quite a few places:</p>
+<p>Assume the Stat size of links is zero (and read them instead)
+(deprecated).</p>
+<p>Rclone used to use the Stat size of links as the link size, but this
+fails in quite a few places:</p>
 <ul>
 <li>Windows</li>
 <li>On some virtual filesystems (such ash LucidLink)</li>
@@ -36714,10 +51995,15 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-unicode-normalization">--local-unicode-normalization</h4>
 <p>Apply unicode NFC normalization to paths and filenames.</p>
-<p>This flag can be used to normalize file names into unicode NFC form that are read from the local filesystem.</p>
-<p>Rclone does not normally touch the encoding of file names it reads from the file system.</p>
-<p>This can be useful when using macOS as it normally provides decomposed (NFD) unicode which in some language (eg Korean) doesn't display properly on some OSes.</p>
-<p>Note that rclone compares filenames with unicode normalization in the sync routine so this flag shouldn't normally be used.</p>
+<p>This flag can be used to normalize file names into unicode NFC form
+that are read from the local filesystem.</p>
+<p>Rclone does not normally touch the encoding of file names it reads
+from the file system.</p>
+<p>This can be useful when using macOS as it normally provides
+decomposed (NFD) unicode which in some language (eg Korean) doesn't
+display properly on some OSes.</p>
+<p>Note that rclone compares filenames with unicode normalization in the
+sync routine so this flag shouldn't normally be used.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: unicode_normalization</li>
@@ -36727,17 +52013,32 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-no-check-updated">--local-no-check-updated</h4>
 <p>Don't check to see if the files change during upload.</p>
-<p>Normally rclone checks the size and modification time of files as they are being uploaded and aborts with a message which starts "can't copy - source file is being updated" if the file changes during upload.</p>
-<p>However on some file systems this modification time check may fail (e.g. <a href="https://github.com/rclone/rclone/issues/2206">Glusterfs #2206</a>) so this check can be disabled with this flag.</p>
-<p>If this flag is set, rclone will use its best efforts to transfer a file which is being updated. If the file is only having things appended to it (e.g. a log) then rclone will transfer the log file with the size it had the first time rclone saw it.</p>
-<p>If the file is being modified throughout (not just appended to) then the transfer may fail with a hash check failure.</p>
-<p>In detail, once the file has had stat() called on it for the first time we:</p>
+<p>Normally rclone checks the size and modification time of files as
+they are being uploaded and aborts with a message which starts "can't
+copy - source file is being updated" if the file changes during
+upload.</p>
+<p>However on some file systems this modification time check may fail
+(e.g. <a href="https://github.com/rclone/rclone/issues/2206">Glusterfs
+#2206</a>) so this check can be disabled with this flag.</p>
+<p>If this flag is set, rclone will use its best efforts to transfer a
+file which is being updated. If the file is only having things appended
+to it (e.g. a log) then rclone will transfer the log file with the size
+it had the first time rclone saw it.</p>
+<p>If the file is being modified throughout (not just appended to) then
+the transfer may fail with a hash check failure.</p>
+<p>In detail, once the file has had stat() called on it for the first
+time we:</p>
 <ul>
 <li>Only transfer the size that stat gave</li>
 <li>Only checksum the size that stat gave</li>
 <li>Don't update the stat info for the file</li>
 </ul>
-<p><strong>NB</strong> do not use this flag on a Windows Volume Shadow (VSS). For some unknown reason, files in a VSS sometimes show different sizes from the directory listing (where the initial stat value comes from on Windows) and when stat is called on them directly. Other copy tools always use the direct stat value and setting this flag will disable that.</p>
+<p><strong>NB</strong> do not use this flag on a Windows Volume Shadow
+(VSS). For some unknown reason, files in a VSS sometimes show different
+sizes from the directory listing (where the initial stat value comes
+from on Windows) and when stat is called on them directly. Other copy
+tools always use the direct stat value and setting this flag will
+disable that.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_check_updated</li>
@@ -36756,7 +52057,9 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-case-sensitive">--local-case-sensitive</h4>
 <p>Force the filesystem to report itself as case sensitive.</p>
-<p>Normally the local backend declares itself as case insensitive on Windows/macOS and case sensitive for everything else. Use this flag to override the default choice.</p>
+<p>Normally the local backend declares itself as case insensitive on
+Windows/macOS and case sensitive for everything else. Use this flag to
+override the default choice.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: case_sensitive</li>
@@ -36766,7 +52069,9 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-case-insensitive">--local-case-insensitive</h4>
 <p>Force the filesystem to report itself as case insensitive.</p>
-<p>Normally the local backend declares itself as case insensitive on Windows/macOS and case sensitive for everything else. Use this flag to override the default choice.</p>
+<p>Normally the local backend declares itself as case insensitive on
+Windows/macOS and case sensitive for everything else. Use this flag to
+override the default choice.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: case_insensitive</li>
@@ -36776,10 +52081,20 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-no-clone">--local-no-clone</h4>
 <p>Disable reflink cloning for server-side copies.</p>
-<p>Normally, for local-to-local transfers, rclone will "clone" the file when possible, and fall back to "copying" only when cloning is not supported.</p>
-<p>Cloning creates a shallow copy (or "reflink") which initially shares blocks with the original file. Unlike a "hardlink", the two files are independent and neither will affect the other if subsequently modified.</p>
-<p>Cloning is usually preferable to copying, as it is much faster and is deduplicated by default (i.e. having two identical files does not consume more storage than having just one.) However, for use cases where data redundancy is preferable, --local-no-clone can be used to disable cloning and force "deep" copies.</p>
-<p>Currently, cloning is only supported when using APFS on macOS (support for other platforms may be added in the future.)</p>
+<p>Normally, for local-to-local transfers, rclone will "clone" the file
+when possible, and fall back to "copying" only when cloning is not
+supported.</p>
+<p>Cloning creates a shallow copy (or "reflink") which initially shares
+blocks with the original file. Unlike a "hardlink", the two files are
+independent and neither will affect the other if subsequently
+modified.</p>
+<p>Cloning is usually preferable to copying, as it is much faster and is
+deduplicated by default (i.e. having two identical files does not
+consume more storage than having just one.) However, for use cases where
+data redundancy is preferable, --local-no-clone can be used to disable
+cloning and force "deep" copies.</p>
+<p>Currently, cloning is only supported when using APFS on macOS
+(support for other platforms may be added in the future.)</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_clone</li>
@@ -36789,7 +52104,11 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-no-preallocate">--local-no-preallocate</h4>
 <p>Disable preallocation of disk space for transferred files.</p>
-<p>Preallocation of disk space helps prevent filesystem fragmentation. However, some virtual filesystem layers (such as Google Drive File Stream) may incorrectly set the actual file size equal to the preallocated space, causing checksum and file size checks to fail. Use this flag to disable preallocation.</p>
+<p>Preallocation of disk space helps prevent filesystem fragmentation.
+However, some virtual filesystem layers (such as Google Drive File
+Stream) may incorrectly set the actual file size equal to the
+preallocated space, causing checksum and file size checks to fail. Use
+this flag to disable preallocation.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_preallocate</li>
@@ -36799,7 +52118,10 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-no-sparse">--local-no-sparse</h4>
 <p>Disable sparse files for multi-thread downloads.</p>
-<p>On Windows platforms rclone will make sparse files when doing multi-thread downloads. This avoids long pauses on large files where the OS zeros the file. However sparse files may be undesirable as they cause disk fragmentation and can be slow to work with.</p>
+<p>On Windows platforms rclone will make sparse files when doing
+multi-thread downloads. This avoids long pauses on large files where the
+OS zeros the file. However sparse files may be undesirable as they cause
+disk fragmentation and can be slow to work with.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_sparse</li>
@@ -36809,7 +52131,12 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-no-set-modtime">--local-no-set-modtime</h4>
 <p>Disable setting modtime.</p>
-<p>Normally rclone updates modification time of files after they are done uploading. This can cause permissions issues on Linux platforms when the user rclone is running as does not own the file uploaded, such as when copying to a CIFS mount owned by another user. If this option is enabled, rclone will no longer update the modtime after copying a file.</p>
+<p>Normally rclone updates modification time of files after they are
+done uploading. This can cause permissions issues on Linux platforms
+when the user rclone is running as does not own the file uploaded, such
+as when copying to a CIFS mount owned by another user. If this option is
+enabled, rclone will no longer update the modtime after copying a
+file.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: no_set_modtime</li>
@@ -36819,16 +52146,22 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-time-type">--local-time-type</h4>
 <p>Set what kind of time is returned.</p>
-<p>Normally rclone does all operations on the mtime or Modification time.</p>
-<p>If you set this flag then rclone will return the Modified time as whatever you set here. So if you use "rclone lsl --local-time-type ctime" then you will see ctimes in the listing.</p>
-<p>If the OS doesn't support returning the time_type specified then rclone will silently replace it with the modification time which all OSes support.</p>
+<p>Normally rclone does all operations on the mtime or Modification
+time.</p>
+<p>If you set this flag then rclone will return the Modified time as
+whatever you set here. So if you use "rclone lsl --local-time-type
+ctime" then you will see ctimes in the listing.</p>
+<p>If the OS doesn't support returning the time_type specified then
+rclone will silently replace it with the modification time which all
+OSes support.</p>
 <ul>
 <li>mtime is supported by all OSes</li>
 <li>atime is supported on all OSes except: plan9, js</li>
 <li>btime is only supported on: Windows, macOS, freebsd, netbsd</li>
 <li>ctime is supported on all Oses except: Windows, plan9, js</li>
 </ul>
-<p>Note that setting the time will still set the modified time so this is only useful for reading.</p>
+<p>Note that setting the time will still set the modified time so this
+is only useful for reading.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: time_type</li>
@@ -36857,7 +52190,8 @@ $ tree /tmp/c
 </ul>
 <h4 id="local-encoding">--local-encoding</h4>
 <p>The encoding for the backend.</p>
-<p>See the <a href="https://rclone.org/overview/#encoding">encoding section in the overview</a> for more info.</p>
+<p>See the <a href="https://rclone.org/overview/#encoding">encoding
+section in the overview</a> for more info.</p>
 <p>Properties:</p>
 <ul>
 <li>Config: encoding</li>
@@ -36875,10 +52209,17 @@ $ tree /tmp/c
 <li>Required: false</li>
 </ul>
 <h3 id="metadata-16">Metadata</h3>
-<p>Depending on which OS is in use the local backend may return only some of the system metadata. Setting system metadata is supported on all OSes but setting user metadata is only supported on linux, freebsd, netbsd, macOS and Solaris. It is <strong>not</strong> supported on Windows yet (<a href="https://github.com/pkg/xattr/issues/47">see pkg/attrs#47</a>).</p>
-<p>User metadata is stored as extended attributes (which may not be supported by all file systems) under the "user.*" prefix.</p>
+<p>Depending on which OS is in use the local backend may return only
+some of the system metadata. Setting system metadata is supported on all
+OSes but setting user metadata is only supported on linux, freebsd,
+netbsd, macOS and Solaris. It is <strong>not</strong> supported on
+Windows yet (<a href="https://github.com/pkg/xattr/issues/47">see
+pkg/attrs#47</a>).</p>
+<p>User metadata is stored as extended attributes (which may not be
+supported by all file systems) under the "user.*" prefix.</p>
 <p>Metadata is supported on files and directories.</p>
-<p>Here are the possible system metadata items for the local backend.</p>
+<p>Here are the possible system metadata items for the local
+backend.</p>
 <table>
 <colgroup>
 <col style="width: 15%" />
@@ -36948,18 +52289,23 @@ $ tree /tmp/c
 </tr>
 </tbody>
 </table>
-<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs for more info.</p>
+<p>See the <a href="https://rclone.org/docs/#metadata">metadata</a> docs
+for more info.</p>
 <h2 id="backend-commands-10">Backend commands</h2>
 <p>Here are the commands specific to the local backend.</p>
 <p>Run them with</p>
 <pre><code>rclone backend COMMAND remote:</code></pre>
 <p>The help below will explain what arguments each command takes.</p>
-<p>See the <a href="https://rclone.org/commands/rclone_backend/">backend</a> command for more info on how to pass options and arguments.</p>
-<p>These can be run on a running backend using the rc command <a href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
+<p>See the <a
+href="https://rclone.org/commands/rclone_backend/">backend</a> command
+for more info on how to pass options and arguments.</p>
+<p>These can be run on a running backend using the rc command <a
+href="https://rclone.org/rc/#backend-command">backend/command</a>.</p>
 <h3 id="noop">noop</h3>
 <p>A null operation for testing backend commands</p>
 <pre><code>rclone backend noop remote: [options] [&lt;arguments&gt;+]</code></pre>
-<p>This is a test command which has some options you can try to change the output.</p>
+<p>This is a test command which has some options you can try to change
+the output.</p>
 <p>Options:</p>
 <ul>
 <li>"echo": echo the input arguments</li>
@@ -36967,52 +52313,73 @@ $ tree /tmp/c
 </ul>
 <h1 id="changelog-1">Changelog</h1>
 <h2 id="v1.68.2---2024-11-15">v1.68.2 - 2024-11-15</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.68.1...v1.68.2">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.68.1...v1.68.2">See
+commits</a></p>
 <ul>
 <li>Security fixes
 <ul>
-<li>local backend: CVE-2024-52522: fix permission and ownership on symlinks with <code>--links</code> and <code>--metadata</code> (Nick Craig-Wood)
+<li>local backend: CVE-2024-52522: fix permission and ownership on
+symlinks with <code>--links</code> and <code>--metadata</code> (Nick
+Craig-Wood)
 <ul>
-<li>Only affects users using <code>--metadata</code> and <code>--links</code> and copying files to the local backend</li>
-<li>See https://github.com/rclone/rclone/security/advisories/GHSA-hrxh-9w67-g4cv</li>
+<li>Only affects users using <code>--metadata</code> and
+<code>--links</code> and copying files to the local backend</li>
+<li>See
+https://github.com/rclone/rclone/security/advisories/GHSA-hrxh-9w67-g4cv</li>
 </ul></li>
-<li>build: bump github.com/golang-jwt/jwt/v4 from 4.5.0 to 4.5.1 (dependabot)
+<li>build: bump github.com/golang-jwt/jwt/v4 from 4.5.0 to 4.5.1
+(dependabot)
 <ul>
-<li>This is an issue in a dependency which is used for JWT certificates</li>
-<li>See https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r</li>
+<li>This is an issue in a dependency which is used for JWT
+certificates</li>
+<li>See
+https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r</li>
 </ul></li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>accounting: Fix wrong message on SIGUSR2 to enable/disable bwlimit (Nick Craig-Wood)</li>
-<li>bisync: Fix output capture restoring the wrong output for logrus (Dimitrios Slamaris)</li>
-<li>dlna: Fix loggingResponseWriter disregarding log level (Simon Bos)</li>
-<li>serve s3: Fix excess locking which was making serve s3 single threaded (Nick Craig-Wood)</li>
-<li>doc fixes (Nick Craig-Wood, tgfisher, Alexandre Hamez, Randy Bush)</li>
+<li>accounting: Fix wrong message on SIGUSR2 to enable/disable bwlimit
+(Nick Craig-Wood)</li>
+<li>bisync: Fix output capture restoring the wrong output for logrus
+(Dimitrios Slamaris)</li>
+<li>dlna: Fix loggingResponseWriter disregarding log level (Simon
+Bos)</li>
+<li>serve s3: Fix excess locking which was making serve s3 single
+threaded (Nick Craig-Wood)</li>
+<li>doc fixes (Nick Craig-Wood, tgfisher, Alexandre Hamez, Randy
+Bush)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix permission and ownership on symlinks with <code>--links</code> and <code>--metadata</code> (Nick Craig-Wood)</li>
+<li>Fix permission and ownership on symlinks with <code>--links</code>
+and <code>--metadata</code> (Nick Craig-Wood)</li>
 <li>Fix <code>--copy-links</code> on macOS when cloning (nielash)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Fix Retry-After handling to look at 503 errors also (Nick Craig-Wood)</li>
+<li>Fix Retry-After handling to look at 503 errors also (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Pikpak
 <ul>
 <li>Fix cid/gcid calculations for fs.OverrideRemote (wiserain)</li>
-<li>Fix fatal crash on startup with token that can't be refreshed (Nick Craig-Wood)</li>
+<li>Fix fatal crash on startup with token that can't be refreshed (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Fix crash when using <code>--s3-download-url</code> after migration to SDKv2 (Nick Craig-Wood)</li>
-<li>Storj provider: fix server-side copy of files bigger than 5GB (Kaloyan Raev)</li>
+<li>Fix crash when using <code>--s3-download-url</code> after migration
+to SDKv2 (Nick Craig-Wood)</li>
+<li>Storj provider: fix server-side copy of files bigger than 5GB
+(Kaloyan Raev)</li>
 <li>Fix multitenant multipart uploads with CEPH (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.68.1---2024-09-24">v1.68.1 - 2024-09-24</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.68.0...v1.68.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.68.0...v1.68.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
@@ -37020,15 +52387,20 @@ $ tree /tmp/c
 <li>doc fixes (Nick Craig-Wood, Pawel Palucha)</li>
 <li>fs
 <ul>
-<li>Fix <code>--dump filters</code> not always appearing (Nick Craig-Wood)</li>
-<li>Fix setting <code>stringArray</code> config values from environment variables (Nick Craig-Wood)</li>
+<li>Fix <code>--dump filters</code> not always appearing (Nick
+Craig-Wood)</li>
+<li>Fix setting <code>stringArray</code> config values from environment
+variables (Nick Craig-Wood)</li>
 </ul></li>
-<li>rc: Fix default value of <code>--metrics-addr</code> (Nick Craig-Wood)</li>
-<li>serve docker: Add missing <code>vfs-read-chunk-streams</code> option in docker volume driver (Divyam)</li>
+<li>rc: Fix default value of <code>--metrics-addr</code> (Nick
+Craig-Wood)</li>
+<li>serve docker: Add missing <code>vfs-read-chunk-streams</code> option
+in docker volume driver (Divyam)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Fix spurious "Couldn't decode error response: EOF" DEBUG (Nick Craig-Wood)</li>
+<li>Fix spurious "Couldn't decode error response: EOF" DEBUG (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Pikpak
 <ul>
@@ -37036,74 +52408,113 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Fix rclone ignoring static credentials when <code>env_auth=true</code> (Nick Craig-Wood)</li>
+<li>Fix rclone ignoring static credentials when
+<code>env_auth=true</code> (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.68.0---2024-09-08">v1.68.0 - 2024-09-08</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.67.0...v1.68.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.67.0...v1.68.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
 <li><a href="/filescom">Files.com</a> (Sam Harrison)</li>
-<li><a href="https://rclone.org/gofile/">Gofile</a> (Nick Craig-Wood)</li>
-<li><a href="https://rclone.org/pixeldrain/">Pixeldrain</a> (Fornax)</li>
+<li><a href="https://rclone.org/gofile/">Gofile</a> (Nick
+Craig-Wood)</li>
+<li><a href="https://rclone.org/pixeldrain/">Pixeldrain</a>
+(Fornax)</li>
 </ul></li>
 <li>Changed backends
 <ul>
-<li><a href="https://rclone.org/s3/">S3</a> backend updated to use <a href="https://github.com/aws/aws-sdk-go-v2">AWS SDKv2</a> as v1 is now unsupported.
+<li><a href="https://rclone.org/s3/">S3</a> backend updated to use <a
+href="https://github.com/aws/aws-sdk-go-v2">AWS SDKv2</a> as v1 is now
+unsupported.
 <ul>
-<li>The matrix of providers and auth methods is huge and there could be problems with obscure combinations.</li>
-<li>Please report problems in a <a href="https://github.com/rclone/rclone/issues/new/choose">new issue</a> on Github.</li>
+<li>The matrix of providers and auth methods is huge and there could be
+problems with obscure combinations.</li>
+<li>Please report problems in a <a
+href="https://github.com/rclone/rclone/issues/new/choose">new issue</a>
+on Github.</li>
 </ul></li>
 </ul></li>
 <li>New commands
 <ul>
-<li><a href="https://rclone.org/commands/rclone_config_encryption/">config encryption</a>: set, remove and check to manage config file encryption (Nick Craig-Wood)</li>
+<li><a
+href="https://rclone.org/commands/rclone_config_encryption/">config
+encryption</a>: set, remove and check to manage config file encryption
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>New Features
 <ul>
 <li>build
 <ul>
-<li>Update to go1.23 and make go1.21 the minimum required version (Nick Craig-Wood)</li>
+<li>Update to go1.23 and make go1.21 the minimum required version (Nick
+Craig-Wood)</li>
 <li>Update all dependencies (Nick Craig-Wood)</li>
-<li>Disable wasm/js build due to <a href="https://github.com/golang/go/issues/64856">go bug #64856</a> (Nick Craig-Wood)</li>
-<li>Enable custom linting rules with ruleguard via gocritic (albertony)</li>
-<li>Update logging statements to make <code>--use-json-log</code> work always (albertony)</li>
-<li>Adding new code quality tests and fixing the fallout (albertony)</li>
+<li>Disable wasm/js build due to <a
+href="https://github.com/golang/go/issues/64856">go bug #64856</a> (Nick
+Craig-Wood)</li>
+<li>Enable custom linting rules with ruleguard via gocritic
+(albertony)</li>
+<li>Update logging statements to make <code>--use-json-log</code> work
+always (albertony)</li>
+<li>Adding new code quality tests and fixing the fallout
+(albertony)</li>
 </ul></li>
 <li>config
 <ul>
-<li>Internal config re-organised to be more consistent and make it available from the rc (Nick Craig-Wood)</li>
+<li>Internal config re-organised to be more consistent and make it
+available from the rc (Nick Craig-Wood)</li>
 <li>Avoid remotes with empty names from the environment (albertony)</li>
 <li>Make listing of remotes more consistent (albertony)</li>
 <li>Make getting config values more consistent (albertony)</li>
-<li>Use <code>--password-command</code> to set config file password if supplied (Nick Craig-Wood)</li>
+<li>Use <code>--password-command</code> to set config file password if
+supplied (Nick Craig-Wood)</li>
 </ul></li>
-<li>doc fixes (albertony, crystalstall, David Seifert, Eng Zer Jun, Ernie Hershey, Florian Klink, John Oxley, kapitainsky, Mathieu Moreau, Nick Craig-Wood, nipil, Pétr Bozsó, Russ Bubley, Sam Harrison, Thearas, URenko, Will Miles, yuval-cloudinary)</li>
-<li>fs: Allow semicolons as well as spaces in <code>--bwlimit</code> timetable parsing (Kyle Reynolds)</li>
+<li>doc fixes (albertony, crystalstall, David Seifert, Eng Zer Jun,
+Ernie Hershey, Florian Klink, John Oxley, kapitainsky, Mathieu Moreau,
+Nick Craig-Wood, nipil, Pétr Bozsó, Russ Bubley, Sam Harrison, Thearas,
+URenko, Will Miles, yuval-cloudinary)</li>
+<li>fs: Allow semicolons as well as spaces in <code>--bwlimit</code>
+timetable parsing (Kyle Reynolds)</li>
 <li>help
 <ul>
 <li>Global flags help command now takes glob filter (albertony)</li>
 <li>Make help command output less distracting (albertony)</li>
 </ul></li>
-<li>lib/encoder: Add Raw encoding for use where no encoding at all is required, eg <code>--local-encoding Raw</code> (URenko)</li>
-<li>listremotes: Added options for filtering, ordering and json output (albertony)</li>
+<li>lib/encoder: Add Raw encoding for use where no encoding at all is
+required, eg <code>--local-encoding Raw</code> (URenko)</li>
+<li>listremotes: Added options for filtering, ordering and json output
+(albertony)</li>
 <li>nfsmount
 <ul>
-<li>Make the <code>--sudo</code> flag work for umount as well as mount (Nick Craig-Wood)</li>
-<li>Add <code>-o tcp</code> option to NFS mount options to fix mounting under Linux (Nick Craig-Wood)</li>
+<li>Make the <code>--sudo</code> flag work for umount as well as mount
+(Nick Craig-Wood)</li>
+<li>Add <code>-o tcp</code> option to NFS mount options to fix mounting
+under Linux (Nick Craig-Wood)</li>
 </ul></li>
 <li>operations: copy: generate stable partial suffix (Georg Welzel)</li>
 <li>rc
 <ul>
-<li>Add <a href="https://rclone.org/rc/#options-info">options/info</a> call to enumerate options (Nick Craig-Wood)</li>
-<li>Add option blocks parameter to <a href="https://rclone.org/rc/#options-get">options/get</a> and <a href="/rc/#options-info">options/info</a> (Nick Craig-Wood)</li>
-<li>Add <a href="https://rclone.org/rc/#vfs-queue">vfs/queue</a> to show the status of the upload queue (Nick Craig-Wood)</li>
-<li>Add <a href="https://rclone.org/rc/#vfs-queue-set-expiry">vfs/queue-set-expiry</a> to adjust expiry of items in the VFS queue (Nick Craig-Wood)</li>
-<li>Add <code>--unix-socket</code> option to <code>rc</code> command (Florian Klink)</li>
-<li>Prevent unmount rc command from sending a <code>STOPPING=1</code> sd-notify message (AThePeanut4)</li>
+<li>Add <a href="https://rclone.org/rc/#options-info">options/info</a>
+call to enumerate options (Nick Craig-Wood)</li>
+<li>Add option blocks parameter to <a
+href="https://rclone.org/rc/#options-get">options/get</a> and <a
+href="/rc/#options-info">options/info</a> (Nick Craig-Wood)</li>
+<li>Add <a href="https://rclone.org/rc/#vfs-queue">vfs/queue</a> to show
+the status of the upload queue (Nick Craig-Wood)</li>
+<li>Add <a
+href="https://rclone.org/rc/#vfs-queue-set-expiry">vfs/queue-set-expiry</a>
+to adjust expiry of items in the VFS queue (Nick Craig-Wood)</li>
+<li>Add <code>--unix-socket</code> option to <code>rc</code> command
+(Florian Klink)</li>
+<li>Prevent unmount rc command from sending a <code>STOPPING=1</code>
+sd-notify message (AThePeanut4)</li>
 </ul></li>
-<li>rcserver: Implement <a href="https://rclone.org/docs/#metrics">prometheus metrics</a> on a dedicated port (Oleg Kunitsyn)</li>
+<li>rcserver: Implement <a
+href="https://rclone.org/docs/#metrics">prometheus metrics</a> on a
+dedicated port (Oleg Kunitsyn)</li>
 <li>serve dlna
 <ul>
 <li>Also look at "Subs" subdirectory (Florian Klink)</li>
@@ -37112,28 +52523,37 @@ $ tree /tmp/c
 </ul></li>
 <li>serve nfs
 <ul>
-<li>Implement on disk cache for file handles selected with <code>--nfs-cache-type</code> (Nick Craig-Wood)</li>
+<li>Implement on disk cache for file handles selected with
+<code>--nfs-cache-type</code> (Nick Craig-Wood)</li>
 <li>Add tracing to filesystem calls (Nick Craig-Wood)</li>
 <li>Mask unimplemented error from chmod (Nick Craig-Wood)</li>
-<li>Unify the nfs library logging with rclone's logging better (Nick Craig-Wood)</li>
-<li>Fix incorrect user id and group id exported to NFS (Nick Craig-Wood)</li>
+<li>Unify the nfs library logging with rclone's logging better (Nick
+Craig-Wood)</li>
+<li>Fix incorrect user id and group id exported to NFS (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>serve s3
 <ul>
 <li>Implement <code>--auth-proxy</code> (Sawjan Gurung)</li>
-<li>Update to AWS SDKv2 by updating <code>github.com/rclone/gofakes3</code> (Nick Craig-Wood)</li>
+<li>Update to AWS SDKv2 by updating
+<code>github.com/rclone/gofakes3</code> (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>bisync: Fix sync time problems with backends that round time (eg Dropbox) (nielash)</li>
-<li>serve dlna: Fix panic: invalid argument to Int63n (Nick Craig-Wood)</li>
+<li>bisync: Fix sync time problems with backends that round time (eg
+Dropbox) (nielash)</li>
+<li>serve dlna: Fix panic: invalid argument to Int63n (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Add <a href="https://rclone.org/commands/rclone_mount/#vfs-read-chunk-streams-0-1">--vfs-read-chunk-streams</a> to parallel read chunks from files (Nick Craig-Wood)
+<li>Add <a
+href="https://rclone.org/commands/rclone_mount/#vfs-read-chunk-streams-0-1">--vfs-read-chunk-streams</a>
+to parallel read chunks from files (Nick Craig-Wood)
 <ul>
-<li>This can increase mount performance on high bandwidth or large latency links</li>
+<li>This can increase mount performance on high bandwidth or large
+latency links</li>
 </ul></li>
 <li>Fix cache encoding with special characters (URenko)</li>
 </ul></li>
@@ -37142,9 +52562,11 @@ $ tree /tmp/c
 <li>Fix encoding of root path fix (URenko)</li>
 <li>Add server-side copy (using clone) with xattrs on macOS (nielash)
 <ul>
-<li><code>--local-no-clone</code> flag to disable cloning for server-side copies (nielash)</li>
+<li><code>--local-no-clone</code> flag to disable cloning for
+server-side copies (nielash)</li>
 </ul></li>
-<li>Support setting custom <code>--metadata</code> during server-side Copy (nielash)</li>
+<li>Support setting custom <code>--metadata</code> during server-side
+Copy (nielash)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
@@ -37152,11 +52574,13 @@ $ tree /tmp/c
 </ul></li>
 <li>B2
 <ul>
-<li>Include custom upload headers in large file info (Pat Patterson)</li>
+<li>Include custom upload headers in large file info (Pat
+Patterson)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Fix copying Google Docs to a backend which only supports SHA1 (Nick Craig-Wood)</li>
+<li>Fix copying Google Docs to a backend which only supports SHA1 (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Fichier
 <ul>
@@ -37174,19 +52598,23 @@ $ tree /tmp/c
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Fix nil pointer error when uploading small files (Nick Craig-Wood)</li>
+<li>Fix nil pointer error when uploading small files (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Pcloud
 <ul>
 <li>Implement <code>SetModTime</code> (Georg Welzel)</li>
-<li>Implement <code>OpenWriterAt</code> feature to enable multipart uploads (Georg Welzel)</li>
+<li>Implement <code>OpenWriterAt</code> feature to enable multipart
+uploads (Georg Welzel)</li>
 </ul></li>
 <li>Pikpak
 <ul>
-<li>Improve data consistency by ensuring async tasks complete (wiserain)</li>
+<li>Improve data consistency by ensuring async tasks complete
+(wiserain)</li>
 <li>Implement custom hash to replace wrong sha1 (wiserain)</li>
 <li>Fix error with <code>copyto</code> command (wiserain)</li>
-<li>Optimize file move by removing unnecessary <code>readMetaData()</code> call (wiserain)</li>
+<li>Optimize file move by removing unnecessary
+<code>readMetaData()</code> call (wiserain)</li>
 <li>Non-buffered hash calculation for local source files (wiserain)</li>
 <li>Optimize upload by pre-fetching gcid from API (wiserain)</li>
 <li>Correct file transfer progress for uploads by hash (wiserain)</li>
@@ -37196,97 +52624,137 @@ $ tree /tmp/c
 <ul>
 <li>Update to using AWS SDK v2 (Nick Craig-Wood)
 <ul>
-<li>Add <code>--s3-sdk-log-mode</code> to control SDKv2 debugging (Nick Craig-Wood)</li>
+<li>Add <code>--s3-sdk-log-mode</code> to control SDKv2 debugging (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Fix incorrect region for Magalu provider (Filipe Herculano)</li>
-<li>Allow restoring from intelligent-tiering storage class (Pawel Palucha)</li>
+<li>Allow restoring from intelligent-tiering storage class (Pawel
+Palucha)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Use <code>uint32</code> for mtime to save memory (Tomasz Melcer)</li>
-<li>Ignore useless errors when closing the connection pool (Nick Craig-Wood)</li>
+<li>Use <code>uint32</code> for mtime to save memory (Tomasz
+Melcer)</li>
+<li>Ignore useless errors when closing the connection pool (Nick
+Craig-Wood)</li>
 <li>Support listening on passed FDs (Florian Klink)</li>
 </ul></li>
 <li>Swift
 <ul>
 <li>Add workarounds for bad listings in Ceph RGW (Paul Collins)</li>
-<li>Add total/free space info in <code>about</code> command. (fsantagostinobietti)</li>
+<li>Add total/free space info in <code>about</code> command.
+(fsantagostinobietti)</li>
 </ul></li>
 <li>Ulozto
 <ul>
-<li>Fix upload of &gt; 2GB files on 32 bit platforms (Tobias Markus)</li>
+<li>Fix upload of &gt; 2GB files on 32 bit platforms (Tobias
+Markus)</li>
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Add <code>--webdav-unix-socket-path</code> to connect to a unix socket (Florian Klink)</li>
+<li>Add <code>--webdav-unix-socket-path</code> to connect to a unix
+socket (Florian Klink)</li>
 </ul></li>
 <li>Yandex
 <ul>
-<li>Implement custom user agent to help with upload speeds (Sebastian Bünger)</li>
+<li>Implement custom user agent to help with upload speeds (Sebastian
+Bünger)</li>
 </ul></li>
 <li>Zoho
 <ul>
-<li>Fix inefficiencies uploading with new API to avoid throttling (Nick Craig-Wood)</li>
+<li>Fix inefficiencies uploading with new API to avoid throttling (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.67.0---2024-06-14">v1.67.0 - 2024-06-14</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.66.0...v1.67.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.66.0...v1.67.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
 <li><a href="https://rclone.org/ulozto/">uloz.to</a> (iotmaestro)</li>
 <li>New S3 providers
 <ul>
-<li><a href="https://rclone.org/s3/#magalu">Magalu Object Storage</a> (Bruno Fernandes)</li>
+<li><a href="https://rclone.org/s3/#magalu">Magalu Object Storage</a>
+(Bruno Fernandes)</li>
 </ul></li>
 </ul></li>
 <li>New commands
 <ul>
-<li><a href="https://rclone.org/commands/rclone_gitannex/">gitannex</a>: Enables git-annex to store and retrieve content from an rclone remote (Dan McArdle)</li>
+<li><a href="https://rclone.org/commands/rclone_gitannex/">gitannex</a>:
+Enables git-annex to store and retrieve content from an rclone remote
+(Dan McArdle)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li>accounting: Add deleted files total size to status summary line (Kyle Reynolds)</li>
+<li>accounting: Add deleted files total size to status summary line
+(Kyle Reynolds)</li>
 <li>build
 <ul>
-<li>Fix <code>CVE-2023-45288</code> by upgrading <code>golang.org/x/net</code> (Nick Craig-Wood)</li>
-<li>Fix <code>CVE-2024-35255</code> by upgrading <code>github.com/Azure/azure-sdk-for-go/sdk/azidentity</code> to 1.6.0 (dependabot)</li>
+<li>Fix <code>CVE-2023-45288</code> by upgrading
+<code>golang.org/x/net</code> (Nick Craig-Wood)</li>
+<li>Fix <code>CVE-2024-35255</code> by upgrading
+<code>github.com/Azure/azure-sdk-for-go/sdk/azidentity</code> to 1.6.0
+(dependabot)</li>
 <li>Convert source files with CRLF to LF (albertony)</li>
 <li>Update all dependencies (Nick Craig-Wood)</li>
 </ul></li>
-<li>doc updates (albertony, Alex Garel, Dave Nicolson, Dominik Joe Pantůček, Eric Wolf, Erisa A, Evan Harris, Evan McBeth, Gachoud Philippe, hidewrong, jakzoe, jumbi77, kapitainsky, Kyle Reynolds, Lewis Hook, Nick Craig-Wood, overallteach, pawsey-kbuckley, Pieter van Oostrum, psychopatt, racerole, static-moonlight, Warrentheo, yudrywet, yumeiyin )</li>
+<li>doc updates (albertony, Alex Garel, Dave Nicolson, Dominik Joe
+Pantůček, Eric Wolf, Erisa A, Evan Harris, Evan McBeth, Gachoud
+Philippe, hidewrong, jakzoe, jumbi77, kapitainsky, Kyle Reynolds, Lewis
+Hook, Nick Craig-Wood, overallteach, pawsey-kbuckley, Pieter van
+Oostrum, psychopatt, racerole, static-moonlight, Warrentheo, yudrywet,
+yumeiyin )</li>
 <li>ncdu: Do not quit on Esc to aid usability (Katia Esposito)</li>
-<li>rcserver: Set <code>ModTime</code> for dirs and files served by <code>--rc-serve</code> (Nikita Shoshin)</li>
+<li>rcserver: Set <code>ModTime</code> for dirs and files served by
+<code>--rc-serve</code> (Nikita Shoshin)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>bisync: Add integration tests against all backends and fix many many problems (nielash)</li>
-<li>config: Fix default value for <code>description</code> (Nick Craig-Wood)</li>
-<li>copy: Fix <code>nil</code> pointer dereference when corrupted on transfer with <code>nil</code> dst (nielash)</li>
+<li>bisync: Add integration tests against all backends and fix many many
+problems (nielash)</li>
+<li>config: Fix default value for <code>description</code> (Nick
+Craig-Wood)</li>
+<li>copy: Fix <code>nil</code> pointer dereference when corrupted on
+transfer with <code>nil</code> dst (nielash)</li>
 <li>fs
 <ul>
-<li>Improve JSON Unmarshalling for <code>Duration</code> types (Kyle Reynolds)</li>
+<li>Improve JSON Unmarshalling for <code>Duration</code> types (Kyle
+Reynolds)</li>
 <li>Close the CPU profile on exit (guangwu)</li>
-<li>Replace <code>/bin/bash</code> with <code>/usr/bin/env bash</code> (Florian Klink)</li>
+<li>Replace <code>/bin/bash</code> with <code>/usr/bin/env bash</code>
+(Florian Klink)</li>
 </ul></li>
-<li>oauthutil: Clear client secret if client ID is set (Michael Terry)</li>
+<li>oauthutil: Clear client secret if client ID is set (Michael
+Terry)</li>
 <li>operations
 <ul>
-<li>Rework <code>rcat</code> so that it doesn't call the <code>--metadata-mapper</code> twice (Nick Craig-Wood)</li>
-<li>Ensure <code>SrcFsType</code> is set correctly when using <code>--metadata-mapper</code> (Nick Craig-Wood)</li>
-<li>Fix "optional feature not implemented" error with a crypted sftp bug (Nick Craig-Wood)</li>
-<li>Fix very long file names when using copy with <code>--partial</code> (Nick Craig-Wood)</li>
-<li>Fix retries downloading too much data with certain backends (Nick Craig-Wood)</li>
+<li>Rework <code>rcat</code> so that it doesn't call the
+<code>--metadata-mapper</code> twice (Nick Craig-Wood)</li>
+<li>Ensure <code>SrcFsType</code> is set correctly when using
+<code>--metadata-mapper</code> (Nick Craig-Wood)</li>
+<li>Fix "optional feature not implemented" error with a crypted sftp bug
+(Nick Craig-Wood)</li>
+<li>Fix very long file names when using copy with <code>--partial</code>
+(Nick Craig-Wood)</li>
+<li>Fix retries downloading too much data with certain backends (Nick
+Craig-Wood)</li>
 <li>Fix move when dst is nil and fdst is case-insensitive (nielash)</li>
-<li>Fix lsjson <code>--encrypted</code> when using <code>--crypt-XXX</code> parameters (Nick Craig-Wood)</li>
-<li>Fix missing metadata for multipart transfers to local disk (Nick Craig-Wood)</li>
-<li>Fix incorrect modtime on some multipart transfers (Nick Craig-Wood)</li>
+<li>Fix lsjson <code>--encrypted</code> when using
+<code>--crypt-XXX</code> parameters (Nick Craig-Wood)</li>
+<li>Fix missing metadata for multipart transfers to local disk (Nick
+Craig-Wood)</li>
+<li>Fix incorrect modtime on some multipart transfers (Nick
+Craig-Wood)</li>
 <li>Fix hashing problem in integration tests (Nick Craig-Wood)</li>
 </ul></li>
 <li>rc
 <ul>
-<li>Fix stats groups being ignored in <code>operations/check</code> (Nick Craig-Wood)</li>
-<li>Fix incorrect <code>Content-Type</code> in HTTP API (Kyle Reynolds)</li>
+<li>Fix stats groups being ignored in <code>operations/check</code>
+(Nick Craig-Wood)</li>
+<li>Fix incorrect <code>Content-Type</code> in HTTP API (Kyle
+Reynolds)</li>
 </ul></li>
 <li>serve s3
 <ul>
@@ -37294,26 +52762,38 @@ $ tree /tmp/c
 <li>Fix in-memory metadata storing wrong modtime (nielash)</li>
 <li>Fix XML of error message (Nick Craig-Wood)</li>
 </ul></li>
-<li>serve webdav: Fix webdav with <code>--baseurl</code> under Windows (Nick Craig-Wood)</li>
-<li>serve dlna: Make <code>BrowseMetadata</code> more compliant (albertony)</li>
-<li>serve http: Added <code>Content-Length</code> header when HTML directory is served (Sunny)</li>
+<li>serve webdav: Fix webdav with <code>--baseurl</code> under Windows
+(Nick Craig-Wood)</li>
+<li>serve dlna: Make <code>BrowseMetadata</code> more compliant
+(albertony)</li>
+<li>serve http: Added <code>Content-Length</code> header when HTML
+directory is served (Sunny)</li>
 <li>sync
 <ul>
-<li>Don't sync directories if they haven't been modified (Nick Craig-Wood)</li>
-<li>Don't test reading metadata if we can't write it (Nick Craig-Wood)</li>
+<li>Don't sync directories if they haven't been modified (Nick
+Craig-Wood)</li>
+<li>Don't test reading metadata if we can't write it (Nick
+Craig-Wood)</li>
 <li>Fix case normalisation (problem on on s3) (Nick Craig-Wood)</li>
-<li>Fix management of empty directories to make it more accurate (Nick Craig-Wood)</li>
-<li>Fix creation of empty directories when <code>--create-empty-src-dirs=false</code> (Nick Craig-Wood)</li>
-<li>Fix directory modification times not being set (Nick Craig-Wood)</li>
-<li>Fix "failed to update directory timestamp or metadata: directory not found" (Nick Craig-Wood)</li>
-<li>Fix expecting SFTP to have MkdirMetadata method: optional feature not implemented (Nick Craig-Wood)</li>
+<li>Fix management of empty directories to make it more accurate (Nick
+Craig-Wood)</li>
+<li>Fix creation of empty directories when
+<code>--create-empty-src-dirs=false</code> (Nick Craig-Wood)</li>
+<li>Fix directory modification times not being set (Nick
+Craig-Wood)</li>
+<li>Fix "failed to update directory timestamp or metadata: directory not
+found" (Nick Craig-Wood)</li>
+<li>Fix expecting SFTP to have MkdirMetadata method: optional feature
+not implemented (Nick Craig-Wood)</li>
 </ul></li>
 <li>test info: Improve cleanup of temp files (Kyle Reynolds)</li>
-<li>touch: Fix using <code>-R</code> on certain backends (Nick Craig-Wood)</li>
+<li>touch: Fix using <code>-R</code> on certain backends (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Add <code>--direct-io</code> flag to force uncached access (Nick Craig-Wood)</li>
+<li>Add <code>--direct-io</code> flag to force uncached access (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
@@ -37322,8 +52802,12 @@ $ tree /tmp/c
 </ul></li>
 <li>Local
 <ul>
-<li>Add <code>--local-time-type</code> to use <code>mtime</code>/<code>atime</code>/<code>btime</code>/<code>ctime</code> as the time (Nick Craig-Wood)</li>
-<li>Allow <code>SeBackupPrivilege</code> and/or <code>SeRestorePrivilege</code> to work on Windows (Charles Hamilton)</li>
+<li>Add <code>--local-time-type</code> to use
+<code>mtime</code>/<code>atime</code>/<code>btime</code>/<code>ctime</code>
+as the time (Nick Craig-Wood)</li>
+<li>Allow <code>SeBackupPrivilege</code> and/or
+<code>SeRestorePrivilege</code> to work on Windows (Charles
+Hamilton)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
@@ -37331,29 +52815,42 @@ $ tree /tmp/c
 </ul></li>
 <li>B2
 <ul>
-<li>Add new <a href="https://rclone.org/b2/#cleanup">cleanup</a> and <a href="/b2/#cleanup-hidden">cleanup-hidden</a> backend commands. (Pat Patterson)</li>
+<li>Add new <a href="https://rclone.org/b2/#cleanup">cleanup</a> and <a
+href="/b2/#cleanup-hidden">cleanup-hidden</a> backend commands. (Pat
+Patterson)</li>
 <li>Update B2 URLs to new home (Nick Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
-<li>Fix startup when root points to composite multi-chunk file without metadata (nielash)</li>
-<li>Fix case-insensitive comparison on local without metadata (nielash)</li>
+<li>Fix startup when root points to composite multi-chunk file without
+metadata (nielash)</li>
+<li>Fix case-insensitive comparison on local without metadata
+(nielash)</li>
 <li>Fix "finalizer already set" error (nielash)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Add <a href="https://rclone.org/drive/#query">backend query</a> command for general purpose querying of files (John-Paul Smith)</li>
-<li>Stop sending notification emails when setting permissions (Nick Craig-Wood)</li>
-<li>Fix server side copy with metadata from my drive to shared drive (Nick Craig-Wood)</li>
-<li>Set all metadata permissions and return error summary instead of stopping on the first error (Nick Craig-Wood)</li>
-<li>Make errors setting permissions into no retry errors (Nick Craig-Wood)</li>
-<li>Fix description being overwritten on server side moves (Nick Craig-Wood)</li>
-<li>Allow setting metadata to fail if <code>failok</code> flag is set (Nick Craig-Wood)</li>
-<li>Fix panic when using <code>--metadata-mapper</code> on large google doc files (Nick Craig-Wood)</li>
+<li>Add <a href="https://rclone.org/drive/#query">backend query</a>
+command for general purpose querying of files (John-Paul Smith)</li>
+<li>Stop sending notification emails when setting permissions (Nick
+Craig-Wood)</li>
+<li>Fix server side copy with metadata from my drive to shared drive
+(Nick Craig-Wood)</li>
+<li>Set all metadata permissions and return error summary instead of
+stopping on the first error (Nick Craig-Wood)</li>
+<li>Make errors setting permissions into no retry errors (Nick
+Craig-Wood)</li>
+<li>Fix description being overwritten on server side moves (Nick
+Craig-Wood)</li>
+<li>Allow setting metadata to fail if <code>failok</code> flag is set
+(Nick Craig-Wood)</li>
+<li>Fix panic when using <code>--metadata-mapper</code> on large google
+doc files (Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Add <code>--dropbox-root-namespace</code> to override the root namespace (Bill Fraser)</li>
+<li>Add <code>--dropbox-root-namespace</code> to override the root
+namespace (Bill Fraser)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
@@ -37365,7 +52862,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Http
 <ul>
-<li>Add <code>--http-no-escape</code> to not escape URL metacharacters in path names (Kyle Reynolds)</li>
+<li>Add <code>--http-no-escape</code> to not escape URL metacharacters
+in path names (Kyle Reynolds)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
@@ -37378,32 +52876,43 @@ $ tree /tmp/c
 </ul></li>
 <li>Mailru
 <ul>
-<li>Attempt to fix throttling by increasing min sleep to 100ms (Nick Craig-Wood)</li>
+<li>Attempt to fix throttling by increasing min sleep to 100ms (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Memory
 <ul>
 <li>Fix dst mutating src after server-side copy (nielash)</li>
 <li>Fix deadlock in operations.Purge (nielash)</li>
-<li>Fix incorrect list entries when rooted at subdirectory (nielash)</li>
+<li>Fix incorrect list entries when rooted at subdirectory
+(nielash)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Add <code>--onedrive-hard-delete</code> to permanently delete files (Nick Craig-Wood)</li>
+<li>Add <code>--onedrive-hard-delete</code> to permanently delete files
+(Nick Craig-Wood)</li>
 <li>Make server-side copy work in more scenarios (YukiUnHappy)</li>
-<li>Fix "unauthenticated: Unauthenticated" errors when downloading (Nick Craig-Wood)</li>
-<li>Fix <code>--metadata-mapper</code> being called twice if writing permissions (nielash)</li>
-<li>Set all metadata permissions and return error summary instead of stopping on the first error (nielash)</li>
-<li>Make errors setting permissions into no retry errors (Nick Craig-Wood)</li>
+<li>Fix "unauthenticated: Unauthenticated" errors when downloading (Nick
+Craig-Wood)</li>
+<li>Fix <code>--metadata-mapper</code> being called twice if writing
+permissions (nielash)</li>
+<li>Set all metadata permissions and return error summary instead of
+stopping on the first error (nielash)</li>
+<li>Make errors setting permissions into no retry errors (Nick
+Craig-Wood)</li>
 <li>Skip writing permissions with 'owner' role (nielash)</li>
 <li>Fix references to deprecated permissions properties (nielash)</li>
 <li>Add support for group permissions (nielash)</li>
-<li>Allow setting permissions to fail if <code>failok</code> flag is set (Nick Craig-Wood)</li>
+<li>Allow setting permissions to fail if <code>failok</code> flag is set
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Pikpak
 <ul>
-<li>Make getFile() usage more efficient to avoid the download limit (wiserain)</li>
-<li>Improve upload reliability and resolve potential file conflicts (wiserain)</li>
-<li>Implement configurable chunk size for multipart upload (wiserain)</li>
+<li>Make getFile() usage more efficient to avoid the download limit
+(wiserain)</li>
+<li>Improve upload reliability and resolve potential file conflicts
+(wiserain)</li>
+<li>Implement configurable chunk size for multipart upload
+(wiserain)</li>
 </ul></li>
 <li>Protondrive
 <ul>
@@ -37411,7 +52920,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Qingstor
 <ul>
-<li>Disable integration tests as test account suspended (Nick Craig-Wood)</li>
+<li>Disable integration tests as test account suspended (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Quatrix
 <ul>
@@ -37419,16 +52929,20 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Add new AWS region <code>il-central-1</code> Tel Aviv (yoelvini)</li>
+<li>Add new AWS region <code>il-central-1</code> Tel Aviv
+(yoelvini)</li>
 <li>Update Scaleway's configuration options (Alexandre Lavigne)</li>
-<li>Ceph: fix quirks when creating buckets to fix trying to create an existing bucket (Thomas Schneider)</li>
+<li>Ceph: fix quirks when creating buckets to fix trying to create an
+existing bucket (Thomas Schneider)</li>
 <li>Fix encoding issue with dir path comparison (nielash)</li>
-<li>Fix 405 error on HEAD for delete marker with versionId (nielash)</li>
+<li>Fix 405 error on HEAD for delete marker with versionId
+(nielash)</li>
 <li>Validate <code>--s3-copy-cutoff</code> size before copy (hoyho)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Add <code>--sftp-connections</code> to limit the maximum number of connections (Tomasz Melcer)</li>
+<li>Add <code>--sftp-connections</code> to limit the maximum number of
+connections (Tomasz Melcer)</li>
 </ul></li>
 <li>Storj
 <ul>
@@ -37437,45 +52951,64 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Implement <code>--swift-use-segments-container</code> to allow &gt;5G files on Blomp (Nick Craig-Wood)</li>
+<li>Implement <code>--swift-use-segments-container</code> to allow
+&gt;5G files on Blomp (Nick Craig-Wood)</li>
 </ul></li>
 <li>Union
 <ul>
-<li>Fix deleting dirs when all remotes can't have empty dirs (Nick Craig-Wood)</li>
+<li>Fix deleting dirs when all remotes can't have empty dirs (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Fix setting modification times erasing checksums on owncloud and nextcloud (nielash)</li>
-<li>owncloud: Add <code>--webdav-owncloud-exclude-mounts</code> which allows excluding mounted folders when listing remote resources (Thomas Müller)</li>
+<li>Fix setting modification times erasing checksums on owncloud and
+nextcloud (nielash)</li>
+<li>owncloud: Add <code>--webdav-owncloud-exclude-mounts</code> which
+allows excluding mounted folders when listing remote resources (Thomas
+Müller)</li>
 </ul></li>
 <li>Zoho
 <ul>
 <li>Fix throttling problem when uploading files (Nick Craig-Wood)</li>
 <li>Use cursor listing for improved performance (Nick Craig-Wood)</li>
-<li>Retry reading info after upload if size wasn't returned (Nick Craig-Wood)</li>
-<li>Remove simple file names complication which is no longer needed (Nick Craig-Wood)</li>
-<li>Sleep for 60 seconds if rate limit error received (Nick Craig-Wood)</li>
+<li>Retry reading info after upload if size wasn't returned (Nick
+Craig-Wood)</li>
+<li>Remove simple file names complication which is no longer needed
+(Nick Craig-Wood)</li>
+<li>Sleep for 60 seconds if rate limit error received (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.66.0---2024-03-10">v1.66.0 - 2024-03-10</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.65.0...v1.66.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.65.0...v1.66.0">See
+commits</a></p>
 <ul>
 <li>Major features
 <ul>
-<li>Rclone will now sync directory modification times if the backend supports it.
+<li>Rclone will now sync directory modification times if the backend
+supports it.
 <ul>
-<li>This can be disabled with <a href="https://rclone.org/docs/#no-update-dir-modtime">--no-update-dir-modtime</a></li>
-<li>See <a href="https://rclone.org/overview/#features">the overview</a> and look for the <code>D</code> flags in the <code>ModTime</code> column to see which backends support it.</li>
+<li>This can be disabled with <a
+href="https://rclone.org/docs/#no-update-dir-modtime">--no-update-dir-modtime</a></li>
+<li>See <a href="https://rclone.org/overview/#features">the overview</a>
+and look for the <code>D</code> flags in the <code>ModTime</code> column
+to see which backends support it.</li>
 </ul></li>
-<li>Rclone will now sync directory metadata if the backend supports it when <code>-M</code>/<code>--metadata</code> is in use.
+<li>Rclone will now sync directory metadata if the backend supports it
+when <code>-M</code>/<code>--metadata</code> is in use.
 <ul>
-<li>See <a href="https://rclone.org/overview/#features">the overview</a> and look for the <code>D</code> flags in the <code>Metadata</code> column to see which backends support it.</li>
+<li>See <a href="https://rclone.org/overview/#features">the overview</a>
+and look for the <code>D</code> flags in the <code>Metadata</code>
+column to see which backends support it.</li>
 </ul></li>
-<li>Bisync has received many updates see below for more details or <a href="https://rclone.org/bisync/#changelog">bisync's changelog</a></li>
+<li>Bisync has received many updates see below for more details or <a
+href="https://rclone.org/bisync/#changelog">bisync's changelog</a></li>
 </ul></li>
 <li>Removed backends
 <ul>
-<li>amazonclouddrive: Remove Amazon Drive backend code and docs (Nick Craig-Wood)</li>
+<li>amazonclouddrive: Remove Amazon Drive backend code and docs (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>New Features
 <ul>
@@ -37485,13 +53018,21 @@ $ tree /tmp/c
 </ul></li>
 <li>build
 <ul>
-<li>Update to go1.22 and make go1.20 the minimum required version (Nick Craig-Wood)</li>
-<li>Fix <code>CVE-2024-24786</code> by upgrading <code>google.golang.org/protobuf</code> (Nick Craig-Wood)</li>
+<li>Update to go1.22 and make go1.20 the minimum required version (Nick
+Craig-Wood)</li>
+<li>Fix <code>CVE-2024-24786</code> by upgrading
+<code>google.golang.org/protobuf</code> (Nick Craig-Wood)</li>
 </ul></li>
-<li>check: Respect <code>--no-unicode-normalization</code> and <code>--ignore-case-sync</code> for <code>--checkfile</code> (nielash)</li>
-<li>cmd: Much improved shell auto completion which reduces the size of the completion file and works faster (Nick Craig-Wood)</li>
-<li>doc updates (albertony, ben-ba, Eli, emyarod, huajin tong, Jack Provance, kapitainsky, keongalvin, Nick Craig-Wood, nielash, rarspace01, rzitzer, Tera, Vincent Murphy)</li>
-<li>fs: Add more detailed logging for file includes/excludes (Kyle Reynolds)</li>
+<li>check: Respect <code>--no-unicode-normalization</code> and
+<code>--ignore-case-sync</code> for <code>--checkfile</code>
+(nielash)</li>
+<li>cmd: Much improved shell auto completion which reduces the size of
+the completion file and works faster (Nick Craig-Wood)</li>
+<li>doc updates (albertony, ben-ba, Eli, emyarod, huajin tong, Jack
+Provance, kapitainsky, keongalvin, Nick Craig-Wood, nielash, rarspace01,
+rzitzer, Tera, Vincent Murphy)</li>
+<li>fs: Add more detailed logging for file includes/excludes (Kyle
+Reynolds)</li>
 <li>lsf
 <ul>
 <li>Add <code>--time-format</code> flag (nielash)</li>
@@ -37500,30 +53041,45 @@ $ tree /tmp/c
 <li>lsjson: Make metadata appear for directories (Nick Craig-Wood)</li>
 <li>rc
 <ul>
-<li>Add <code>srcFs</code> and <code>dstFs</code> to <code>core/stats</code> and <code>core/transferred</code> stats (Nick Craig-Wood)</li>
-<li>Add <code>operations/hashsum</code> to the rc as <code>rclone hashsum</code> equivalent (Nick Craig-Wood)</li>
-<li>Add <code>config/paths</code> to the rc as <code>rclone config paths</code> equivalent (Nick Craig-Wood)</li>
+<li>Add <code>srcFs</code> and <code>dstFs</code> to
+<code>core/stats</code> and <code>core/transferred</code> stats (Nick
+Craig-Wood)</li>
+<li>Add <code>operations/hashsum</code> to the rc as
+<code>rclone hashsum</code> equivalent (Nick Craig-Wood)</li>
+<li>Add <code>config/paths</code> to the rc as
+<code>rclone config paths</code> equivalent (Nick Craig-Wood)</li>
 </ul></li>
 <li>sync
 <ul>
 <li>Optionally report list of synced paths to file (nielash)</li>
-<li>Implement directory sync for mod times and metadata (Nick Craig-Wood)</li>
+<li>Implement directory sync for mod times and metadata (Nick
+Craig-Wood)</li>
 <li>Don't set directory modtimes if already set (nielash)</li>
-<li>Don't sync directory modtimes from backends which don't have directories (Nick Craig-Wood)</li>
+<li>Don't sync directory modtimes from backends which don't have
+directories (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>backend
 <ul>
-<li>Make backends which use oauth implement the <code>Shutdown</code> and shutdown the oauth properly (rkonfj)</li>
+<li>Make backends which use oauth implement the <code>Shutdown</code>
+and shutdown the oauth properly (rkonfj)</li>
 </ul></li>
 <li>bisync
 <ul>
 <li>Handle unicode and case normalization consistently (nielash)</li>
-<li>Partial uploads known issue on <code>local</code>/<code>ftp</code>/<code>sftp</code> has been resolved (unless using <code>--inplace</code>) (nielash)</li>
-<li>Fixed handling of unicode normalization and case insensitivity, support for <a href="https://rclone.org/docs/#fix-case"><code>--fix-case</code></a>, <a href="/docs/#ignore-case-sync"><code>--ignore-case-sync</code></a>, <a href="/docs/#no-unicode-normalization"><code>--no-unicode-normalization</code></a> (nielash)</li>
-<li>Bisync no longer fails to find the correct listing file when configs are overridden with backend-specific flags. (nielash)</li>
+<li>Partial uploads known issue on
+<code>local</code>/<code>ftp</code>/<code>sftp</code> has been resolved
+(unless using <code>--inplace</code>) (nielash)</li>
+<li>Fixed handling of unicode normalization and case insensitivity,
+support for <a
+href="https://rclone.org/docs/#fix-case"><code>--fix-case</code></a>, <a
+href="/docs/#ignore-case-sync"><code>--ignore-case-sync</code></a>, <a
+href="/docs/#no-unicode-normalization"><code>--no-unicode-normalization</code></a>
+(nielash)</li>
+<li>Bisync no longer fails to find the correct listing file when configs
+are overridden with backend-specific flags. (nielash)</li>
 </ul></li>
 <li>nfsmount
 <ul>
@@ -37534,25 +53090,33 @@ $ tree /tmp/c
 <ul>
 <li>Fix renaming a file on macOS (nielash)</li>
 <li>Fix case-insensitive moves in operations.Move (nielash)</li>
-<li>Fix TestCaseInsensitiveMoveFileDryRun on chunker integration tests (nielash)</li>
+<li>Fix TestCaseInsensitiveMoveFileDryRun on chunker integration tests
+(nielash)</li>
 <li>Fix TestMkdirModTime test (Nick Craig-Wood)</li>
-<li>Fix TestSetDirModTime for backends with SetDirModTime but not Metadata (Nick Craig-Wood)</li>
+<li>Fix TestSetDirModTime for backends with SetDirModTime but not
+Metadata (Nick Craig-Wood)</li>
 <li>Fix typo in log messages (nielash)</li>
 </ul></li>
 <li>serve nfs: Fix writing files via Finder on macOS (nielash)</li>
 <li>serve restic: Fix error handling (Michael Eischer)</li>
-<li>serve webdav: Fix <code>--baseurl</code> without leading / (Nick Craig-Wood)</li>
-<li>stats: Fix race between ResetCounters and stopAverageLoop called from time.AfterFunc (Nick Craig-Wood)</li>
+<li>serve webdav: Fix <code>--baseurl</code> without leading / (Nick
+Craig-Wood)</li>
+<li>stats: Fix race between ResetCounters and stopAverageLoop called
+from time.AfterFunc (Nick Craig-Wood)</li>
 <li>sync
 <ul>
-<li><code>--fix-case</code> flag to rename case insensitive dest (nielash)</li>
-<li>Use operations.DirMove instead of sync.MoveDir for <code>--fix-case</code> (nielash)</li>
+<li><code>--fix-case</code> flag to rename case insensitive dest
+(nielash)</li>
+<li>Use operations.DirMove instead of sync.MoveDir for
+<code>--fix-case</code> (nielash)</li>
 </ul></li>
-<li>systemd: Fix detection and switch to the coreos package everywhere rather than having 2 separate libraries (Anagh Kumar Baranwal)</li>
+<li>systemd: Fix detection and switch to the coreos package everywhere
+rather than having 2 separate libraries (Anagh Kumar Baranwal)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Fix macOS not noticing errors with <code>--daemon</code> (Nick Craig-Wood)</li>
+<li>Fix macOS not noticing errors with <code>--daemon</code> (Nick
+Craig-Wood)</li>
 <li>Notice daemon dying much quicker (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
@@ -37561,87 +53125,141 @@ $ tree /tmp/c
 </ul></li>
 <li>Bisync
 <ul>
-<li>Copies and deletes are now handled in one operation instead of two (nielash)</li>
-<li><code>--track-renames</code> and <code>--backup-dir</code> are now supported (nielash)</li>
-<li>Final listings are now generated from sync results, to avoid needing to re-list (nielash)</li>
-<li>Bisync is now much more resilient to changes that happen during a bisync run, and far less prone to critical errors / undetected changes (nielash)</li>
-<li>Bisync is now capable of rolling a file listing back in cases of uncertainty, essentially marking the file as needing to be rechecked next time. (nielash)</li>
-<li>A few basic terminal colors are now supported, controllable with <a href="https://rclone.org/docs/#color-when"><code>--color</code></a> (<code>AUTO</code>|<code>NEVER</code>|<code>ALWAYS</code>) (nielash)</li>
-<li>Initial listing snapshots of Path1 and Path2 are now generated concurrently, using the same "march" infrastructure as <code>check</code> and <code>sync</code>, for performance improvements and less risk of error. (nielash)</li>
-<li><code>--resync</code> is now much more efficient (especially for users of <code>--create-empty-src-dirs</code>) (nielash)</li>
-<li>Google Docs (and other files of unknown size) are now supported (with the same options as in <code>sync</code>) (nielash)</li>
-<li>Equality checks before a sync conflict rename now fall back to <code>cryptcheck</code> (when possible) or <code>--download</code>, (nielash) instead of of <code>--size-only</code>, when <code>check</code> is not available.</li>
-<li>Bisync now fully supports comparing based on any combination of size, modtime, and checksum, lifting the prior restriction on backends without modtime support. (nielash)</li>
-<li>Bisync now supports a "Graceful Shutdown" mode to cleanly cancel a run early without requiring <code>--resync</code>. (nielash)</li>
-<li>New <code>--recover</code> flag allows robust recovery in the event of interruptions, without requiring <code>--resync</code>. (nielash)</li>
-<li>A new <code>--max-lock</code> setting allows lock files to automatically renew and expire, for better automatic recovery when a run is interrupted. (nielash)</li>
-<li>Bisync now supports auto-resolving sync conflicts and customizing rename behavior with new <a href="#conflict-resolve"><code>--conflict-resolve</code></a>, <a href="#conflict-loser"><code>--conflict-loser</code></a>, and <a href="#conflict-suffix"><code>--conflict-suffix</code></a> flags. (nielash)</li>
-<li>A new <a href="#resync-mode"><code>--resync-mode</code></a> flag allows more control over which version of a file gets kept during a <code>--resync</code>. (nielash)</li>
-<li>Bisync now supports <a href="https://rclone.org/docs/#retries-int"><code>--retries</code></a> and <a href="/docs/#retries-sleep-time"><code>--retries-sleep</code></a> (when <a href="#resilient"><code>--resilient</code></a> is set.) (nielash)</li>
-<li>Clarify file operation directions in dry-run logs (Kyle Reynolds)</li>
+<li>Copies and deletes are now handled in one operation instead of two
+(nielash)</li>
+<li><code>--track-renames</code> and <code>--backup-dir</code> are now
+supported (nielash)</li>
+<li>Final listings are now generated from sync results, to avoid needing
+to re-list (nielash)</li>
+<li>Bisync is now much more resilient to changes that happen during a
+bisync run, and far less prone to critical errors / undetected changes
+(nielash)</li>
+<li>Bisync is now capable of rolling a file listing back in cases of
+uncertainty, essentially marking the file as needing to be rechecked
+next time. (nielash)</li>
+<li>A few basic terminal colors are now supported, controllable with <a
+href="https://rclone.org/docs/#color-when"><code>--color</code></a>
+(<code>AUTO</code>|<code>NEVER</code>|<code>ALWAYS</code>)
+(nielash)</li>
+<li>Initial listing snapshots of Path1 and Path2 are now generated
+concurrently, using the same "march" infrastructure as
+<code>check</code> and <code>sync</code>, for performance improvements
+and less risk of error. (nielash)</li>
+<li><code>--resync</code> is now much more efficient (especially for
+users of <code>--create-empty-src-dirs</code>) (nielash)</li>
+<li>Google Docs (and other files of unknown size) are now supported
+(with the same options as in <code>sync</code>) (nielash)</li>
+<li>Equality checks before a sync conflict rename now fall back to
+<code>cryptcheck</code> (when possible) or <code>--download</code>,
+(nielash) instead of of <code>--size-only</code>, when
+<code>check</code> is not available.</li>
+<li>Bisync now fully supports comparing based on any combination of
+size, modtime, and checksum, lifting the prior restriction on backends
+without modtime support. (nielash)</li>
+<li>Bisync now supports a "Graceful Shutdown" mode to cleanly cancel a
+run early without requiring <code>--resync</code>. (nielash)</li>
+<li>New <code>--recover</code> flag allows robust recovery in the event
+of interruptions, without requiring <code>--resync</code>.
+(nielash)</li>
+<li>A new <code>--max-lock</code> setting allows lock files to
+automatically renew and expire, for better automatic recovery when a run
+is interrupted. (nielash)</li>
+<li>Bisync now supports auto-resolving sync conflicts and customizing
+rename behavior with new <a
+href="#conflict-resolve"><code>--conflict-resolve</code></a>, <a
+href="#conflict-loser"><code>--conflict-loser</code></a>, and <a
+href="#conflict-suffix"><code>--conflict-suffix</code></a> flags.
+(nielash)</li>
+<li>A new <a href="#resync-mode"><code>--resync-mode</code></a> flag
+allows more control over which version of a file gets kept during a
+<code>--resync</code>. (nielash)</li>
+<li>Bisync now supports <a
+href="https://rclone.org/docs/#retries-int"><code>--retries</code></a>
+and <a href="/docs/#retries-sleep-time"><code>--retries-sleep</code></a>
+(when <a href="#resilient"><code>--resilient</code></a> is set.)
+(nielash)</li>
+<li>Clarify file operation directions in dry-run logs (Kyle
+Reynolds)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix cleanRootPath on Windows after go1.21.4 stdlib update (nielash)</li>
+<li>Fix cleanRootPath on Windows after go1.21.4 stdlib update
+(nielash)</li>
 <li>Implement setting modification time on directories (nielash)</li>
-<li>Implement modtime and metadata for directories (Nick Craig-Wood)</li>
-<li>Fix setting of btime on directories on Windows (Nick Craig-Wood)</li>
-<li>Delete backend implementation of Purge to speed up and make stats (Nick Craig-Wood)</li>
-<li>Support metadata setting and mapping on server side Move (Nick Craig-Wood)</li>
+<li>Implement modtime and metadata for directories (Nick
+Craig-Wood)</li>
+<li>Fix setting of btime on directories on Windows (Nick
+Craig-Wood)</li>
+<li>Delete backend implementation of Purge to speed up and make stats
+(Nick Craig-Wood)</li>
+<li>Support metadata setting and mapping on server side Move (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
-<li>Implement setting modification time on directories (if supported by wrapped remote) (nielash)</li>
+<li>Implement setting modification time on directories (if supported by
+wrapped remote) (nielash)</li>
 <li>Implement setting metadata on directories (Nick Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Implement setting modification time on directories (if supported by wrapped remote) (nielash)</li>
+<li>Implement setting modification time on directories (if supported by
+wrapped remote) (nielash)</li>
 <li>Implement setting metadata on directories (Nick Craig-Wood)</li>
 <li>Improve handling of undecryptable file names (nielash)</li>
 <li>Add missing error check spotted by linter (Nick Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Implement <code>--azureblob-delete-snapshots</code> (Nick Craig-Wood)</li>
+<li>Implement <code>--azureblob-delete-snapshots</code> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
-<li>Clarify exactly what <code>--b2-download-auth-duration</code> does in the docs (Nick Craig-Wood)</li>
+<li>Clarify exactly what <code>--b2-download-auth-duration</code> does
+in the docs (Nick Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
-<li>Implement setting modification time on directories (if supported by wrapped remote) (nielash)</li>
+<li>Implement setting modification time on directories (if supported by
+wrapped remote) (nielash)</li>
 <li>Implement setting metadata on directories (Nick Craig-Wood)</li>
 </ul></li>
 <li>Combine
 <ul>
-<li>Implement setting modification time on directories (if supported by wrapped remote) (nielash)</li>
+<li>Implement setting modification time on directories (if supported by
+wrapped remote) (nielash)</li>
 <li>Implement setting metadata on directories (Nick Craig-Wood)</li>
 <li>Fix directory metadata error on upstream root (nielash)</li>
 <li>Fix directory move across upstreams (nielash)</li>
 </ul></li>
 <li>Compress
 <ul>
-<li>Implement setting modification time on directories (if supported by wrapped remote) (nielash)</li>
+<li>Implement setting modification time on directories (if supported by
+wrapped remote) (nielash)</li>
 <li>Implement setting metadata on directories (Nick Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
 <li>Implement setting modification time on directories (nielash)</li>
-<li>Implement modtime and metadata setting for directories (Nick Craig-Wood)</li>
-<li>Support metadata setting and mapping on server side Move,Copy (Nick Craig-Wood)</li>
+<li>Implement modtime and metadata setting for directories (Nick
+Craig-Wood)</li>
+<li>Support metadata setting and mapping on server side Move,Copy (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Fix mkdir with rsftp which is returning the wrong code (Nick Craig-Wood)</li>
+<li>Fix mkdir with rsftp which is returning the wrong code (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Hasher
 <ul>
-<li>Implement setting modification time on directories (if supported by wrapped remote) (nielash)</li>
+<li>Implement setting modification time on directories (if supported by
+wrapped remote) (nielash)</li>
 <li>Implement setting metadata on directories (Nick Craig-Wood)</li>
 <li>Fix error from trying to stop an already-stopped db (nielash)</li>
-<li>Look for cached hash if passed hash unexpectedly blank (nielash)</li>
+<li>Look for cached hash if passed hash unexpectedly blank
+(nielash)</li>
 </ul></li>
 <li>Imagekit
 <ul>
@@ -37654,7 +53272,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Netstorage
 <ul>
-<li>Fix Root to return correct directory when pointing to a file (Nick Craig-Wood)</li>
+<li>Fix Root to return correct directory when pointing to a file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Onedrive
 <ul>
@@ -37667,7 +53286,8 @@ $ tree /tmp/c
 <li>Oracle Object Storage
 <ul>
 <li>Support <code>backend restore</code> command (Nikhil Ahuja)</li>
-<li>Support workload identity authentication for OKE (Anders Swanson)</li>
+<li>Support workload identity authentication for OKE (Anders
+Swanson)</li>
 </ul></li>
 <li>Protondrive
 <ul>
@@ -37677,26 +53297,35 @@ $ tree /tmp/c
 <ul>
 <li>Fix <code>Content-Range</code> header (Volodymyr)</li>
 <li>Add option to skip project folders (Oksana Zhykina)</li>
-<li>Fix Root to return correct directory when pointing to a file (Nick Craig-Wood)</li>
+<li>Fix Root to return correct directory when pointing to a file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Add <code>--s3-version-deleted</code> to show delete markers in listings when using versions. (Nick Craig-Wood)</li>
-<li>Add IPv6 support with option <code>--s3-use-dual-stack</code> (Anthony Metzidis)</li>
-<li>Copy parts in parallel when doing chunked server side copy (Nick Craig-Wood)</li>
-<li>GCS provider: fix server side copy of files bigger than 5G (Nick Craig-Wood)</li>
-<li>Support metadata setting and mapping on server side Copy (Nick Craig-Wood)</li>
+<li>Add <code>--s3-version-deleted</code> to show delete markers in
+listings when using versions. (Nick Craig-Wood)</li>
+<li>Add IPv6 support with option <code>--s3-use-dual-stack</code>
+(Anthony Metzidis)</li>
+<li>Copy parts in parallel when doing chunked server side copy (Nick
+Craig-Wood)</li>
+<li>GCS provider: fix server side copy of files bigger than 5G (Nick
+Craig-Wood)</li>
+<li>Support metadata setting and mapping on server side Copy (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Seafile
 <ul>
-<li>Fix download/upload error when <code>FILE_SERVER_ROOT</code> is relative (DanielEgbers)</li>
-<li>Fix Root to return correct directory when pointing to a file (Nick Craig-Wood)</li>
+<li>Fix download/upload error when <code>FILE_SERVER_ROOT</code> is
+relative (DanielEgbers)</li>
+<li>Fix Root to return correct directory when pointing to a file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
 <li>Implement setting modification time on directories (nielash)</li>
 <li>Set directory modtimes update on write flag (Nick Craig-Wood)</li>
-<li>Shorten wait delay for external ssh binaries now that we are using go1.20 (Nick Craig-Wood)</li>
+<li>Shorten wait delay for external ssh binaries now that we are using
+go1.20 (Nick Craig-Wood)</li>
 </ul></li>
 <li>Swift
 <ul>
@@ -37704,54 +53333,75 @@ $ tree /tmp/c
 </ul></li>
 <li>Union
 <ul>
-<li>Implement setting modification time on directories (if supported by wrapped remote) (nielash)</li>
+<li>Implement setting modification time on directories (if supported by
+wrapped remote) (nielash)</li>
 <li>Implement setting metadata on directories (Nick Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
 <li>Reduce priority of chunks upload log (Gabriel Ramos)</li>
-<li>owncloud: Add config <code>owncloud_exclude_shares</code> which allows to exclude shared files and folders when listing remote resources (Thomas Müller)</li>
+<li>owncloud: Add config <code>owncloud_exclude_shares</code> which
+allows to exclude shared files and folders when listing remote resources
+(Thomas Müller)</li>
 </ul></li>
 </ul>
 <h2 id="v1.65.2---2024-01-24">v1.65.2 - 2024-01-24</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.65.1...v1.65.2">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.65.1...v1.65.2">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>build: bump github.com/cloudflare/circl from 1.3.6 to 1.3.7 (dependabot)</li>
-<li>docs updates (Nick Craig-Wood, kapitainsky, nielash, Tera, Harshit Budhraja)</li>
+<li>build: bump github.com/cloudflare/circl from 1.3.6 to 1.3.7
+(dependabot)</li>
+<li>docs updates (Nick Craig-Wood, kapitainsky, nielash, Tera, Harshit
+Budhraja)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Fix stale data when using <code>--vfs-cache-mode</code> full (Nick Craig-Wood)</li>
+<li>Fix stale data when using <code>--vfs-cache-mode</code> full (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li><strong>IMPORTANT</strong> Fix data corruption bug - see <a href="https://github.com/rclone/rclone/issues/7590">#7590</a> (Nick Craig-Wood)</li>
+<li><strong>IMPORTANT</strong> Fix data corruption bug - see <a
+href="https://github.com/rclone/rclone/issues/7590">#7590</a> (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.65.1---2024-01-08">v1.65.1 - 2024-01-08</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.65.0...v1.65.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.65.0...v1.65.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
 <li>build
 <ul>
-<li>Bump golang.org/x/crypto to fix ssh terrapin CVE-2023-48795 (dependabot)</li>
-<li>Update to go1.21.5 to fix Windows path problems (Nick Craig-Wood)</li>
+<li>Bump golang.org/x/crypto to fix ssh terrapin CVE-2023-48795
+(dependabot)</li>
+<li>Update to go1.21.5 to fix Windows path problems (Nick
+Craig-Wood)</li>
 <li>Fix docker build on arm/v6 (Nick Craig-Wood)</li>
 </ul></li>
-<li>install.sh: fix harmless error message on install (Nick Craig-Wood)</li>
-<li>accounting: fix stats to show server side transfers (Nick Craig-Wood)</li>
-<li>doc fixes (albertony, ben-ba, Eli Orzitzer, emyarod, keongalvin, rarspace01)</li>
-<li>nfsmount: Compile for all unix oses, add <code>--sudo</code> and fix error/option handling (Nick Craig-Wood)</li>
-<li>operations: Fix files moved by rclone move not being counted as transfers (Nick Craig-Wood)</li>
-<li>oauthutil: Avoid panic when <code>*token</code> and <code>*ts.token</code> are the same (rkonfj)</li>
+<li>install.sh: fix harmless error message on install (Nick
+Craig-Wood)</li>
+<li>accounting: fix stats to show server side transfers (Nick
+Craig-Wood)</li>
+<li>doc fixes (albertony, ben-ba, Eli Orzitzer, emyarod, keongalvin,
+rarspace01)</li>
+<li>nfsmount: Compile for all unix oses, add <code>--sudo</code> and fix
+error/option handling (Nick Craig-Wood)</li>
+<li>operations: Fix files moved by rclone move not being counted as
+transfers (Nick Craig-Wood)</li>
+<li>oauthutil: Avoid panic when <code>*token</code> and
+<code>*ts.token</code> are the same (rkonfj)</li>
 <li>serve s3: Fix listing oddities (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Note that <code>--vfs-refresh</code> runs in the background (Nick Craig-Wood)</li>
+<li>Note that <code>--vfs-refresh</code> runs in the background (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Azurefiles
 <ul>
@@ -37759,15 +53409,18 @@ $ tree /tmp/c
 </ul></li>
 <li>Crypt
 <ul>
-<li>Fix rclone move a file over itself deleting the file (Nick Craig-Wood)</li>
+<li>Fix rclone move a file over itself deleting the file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
-<li>Fix rclone move a file over itself deleting the file (Nick Craig-Wood)</li>
+<li>Fix rclone move a file over itself deleting the file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Compress
 <ul>
-<li>Fix rclone move a file over itself deleting the file (Nick Craig-Wood)</li>
+<li>Fix rclone move a file over itself deleting the file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -37783,13 +53436,16 @@ $ tree /tmp/c
 </ul></li>
 <li>Hasher
 <ul>
-<li>Fix rclone move a file over itself deleting the file (Nick Craig-Wood)</li>
+<li>Fix rclone move a file over itself deleting the file (Nick
+Craig-Wood)</li>
 <li>Fix invalid memory address error when MaxAge == 0 (nielash)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Fix error listing: unknown object type <code>&lt;nil&gt;</code> (Nick Craig-Wood)</li>
-<li>Fix "unauthenticated: Unauthenticated" errors when uploading (Nick Craig-Wood)</li>
+<li>Fix error listing: unknown object type <code>&lt;nil&gt;</code>
+(Nick Craig-Wood)</li>
+<li>Fix "unauthenticated: Unauthenticated" errors when uploading (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Oracleobjectstorage
 <ul>
@@ -37810,11 +53466,14 @@ $ tree /tmp/c
 </ul></li>
 <li>Union
 <ul>
-<li>Fix rclone move a file over itself deleting the file (Nick Craig-Wood)</li>
+<li>Fix rclone move a file over itself deleting the file (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.65.0---2023-11-26">v1.65.0 - 2023-11-26</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.64.0...v1.65.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.64.0...v1.65.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
@@ -37824,9 +53483,12 @@ $ tree /tmp/c
 </ul></li>
 <li>New commands
 <ul>
-<li><code>serve s3</code>: Let rclone act as an S3 compatible server (Mikubill, Artur Neumann, Saw-jan, Nick Craig-Wood)</li>
-<li><code>nfsmount</code>: mount command to provide mount mechanism on macOS without FUSE (Saleh Dindar)</li>
-<li><code>serve nfs</code>: to serve a remote for use by <code>nfsmount</code> (Saleh Dindar)</li>
+<li><code>serve s3</code>: Let rclone act as an S3 compatible server
+(Mikubill, Artur Neumann, Saw-jan, Nick Craig-Wood)</li>
+<li><code>nfsmount</code>: mount command to provide mount mechanism on
+macOS without FUSE (Saleh Dindar)</li>
+<li><code>serve nfs</code>: to serve a remote for use by
+<code>nfsmount</code> (Saleh Dindar)</li>
 </ul></li>
 <li>New Features
 <ul>
@@ -37834,47 +53496,67 @@ $ tree /tmp/c
 <li>build
 <ul>
 <li>Update all dependencies (Nick Craig-Wood)</li>
-<li>Refactor version info and icon resource handling on windows (albertony)</li>
+<li>Refactor version info and icon resource handling on windows
+(albertony)</li>
 </ul></li>
-<li>doc updates (albertony, alfish2000, asdffdsazqqq, Dimitri Papadopoulos, Herby Gillot, Joda Stößer, Manoj Ghosh, Nick Craig-Wood)</li>
-<li>Implement <code>--metadata-mapper</code> to transform metatadata with a user supplied program (Nick Craig-Wood)</li>
-<li>Add <code>ChunkWriterDoesntSeek</code> feature flag and set it for b2 (Nick Craig-Wood)</li>
-<li>lib/http: Export basic go string functions for use in <code>--template</code> (Gabriel Espinoza)</li>
+<li>doc updates (albertony, alfish2000, asdffdsazqqq, Dimitri
+Papadopoulos, Herby Gillot, Joda Stößer, Manoj Ghosh, Nick
+Craig-Wood)</li>
+<li>Implement <code>--metadata-mapper</code> to transform metatadata
+with a user supplied program (Nick Craig-Wood)</li>
+<li>Add <code>ChunkWriterDoesntSeek</code> feature flag and set it for
+b2 (Nick Craig-Wood)</li>
+<li>lib/http: Export basic go string functions for use in
+<code>--template</code> (Gabriel Espinoza)</li>
 <li>makefile: Use POSIX compatible install arguments (Mina Galić)</li>
 <li>operations
 <ul>
-<li>Use less memory when doing multithread uploads (Nick Craig-Wood)</li>
-<li>Implement <code>--partial-suffix</code> to control extension of temporary file names (Volodymyr)</li>
+<li>Use less memory when doing multithread uploads (Nick
+Craig-Wood)</li>
+<li>Implement <code>--partial-suffix</code> to control extension of
+temporary file names (Volodymyr)</li>
 </ul></li>
 <li>rc
 <ul>
-<li>Add <code>operations/check</code> to the rc API (Nick Craig-Wood)</li>
+<li>Add <code>operations/check</code> to the rc API (Nick
+Craig-Wood)</li>
 <li>Always report an error as JSON (Nick Craig-Wood)</li>
-<li>Set <code>Last-Modified</code> header for files served by <code>--rc-serve</code> (Nikita Shoshin)</li>
+<li>Set <code>Last-Modified</code> header for files served by
+<code>--rc-serve</code> (Nikita Shoshin)</li>
 </ul></li>
-<li>size: Dont show duplicate object count when less than 1k (albertony)</li>
+<li>size: Dont show duplicate object count when less than 1k
+(albertony)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>fshttp: Fix <code>--contimeout</code> being ignored (你知道未来吗)</li>
-<li>march: Fix excessive parallelism when using <code>--no-traverse</code> (Nick Craig-Wood)</li>
-<li>ncdu: Fix crash when re-entering changed directory after rescan (Nick Craig-Wood)</li>
+<li>fshttp: Fix <code>--contimeout</code> being ignored
+(你知道未来吗)</li>
+<li>march: Fix excessive parallelism when using
+<code>--no-traverse</code> (Nick Craig-Wood)</li>
+<li>ncdu: Fix crash when re-entering changed directory after rescan
+(Nick Craig-Wood)</li>
 <li>operations
 <ul>
-<li>Fix overwrite of destination when multi-thread transfer fails (Nick Craig-Wood)</li>
-<li>Fix invalid UTF-8 when truncating file names when not using <code>--inplace</code> (Nick Craig-Wood)</li>
+<li>Fix overwrite of destination when multi-thread transfer fails (Nick
+Craig-Wood)</li>
+<li>Fix invalid UTF-8 when truncating file names when not using
+<code>--inplace</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>serve dnla: Fix crash on graceful exit (wuxingzhong)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Disable mount for freebsd and alias cmount as mount on that platform (Nick Craig-Wood)</li>
+<li>Disable mount for freebsd and alias cmount as mount on that platform
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Add <code>--vfs-refresh</code> flag to read all the directories on start (Beyond Meat)</li>
-<li>Implement Name() method in WriteFileHandle and ReadFileHandle (Saleh Dindar)</li>
-<li>Add go-billy dependency and make sure vfs.Handle implements billy.File (Saleh Dindar)</li>
+<li>Add <code>--vfs-refresh</code> flag to read all the directories on
+start (Beyond Meat)</li>
+<li>Implement Name() method in WriteFileHandle and ReadFileHandle (Saleh
+Dindar)</li>
+<li>Add go-billy dependency and make sure vfs.Handle implements
+billy.File (Saleh Dindar)</li>
 <li>Error out early if can't upload 0 length file (Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
@@ -37887,27 +53569,37 @@ $ tree /tmp/c
 </ul></li>
 <li>B2
 <ul>
-<li>Implement "rclone backend lifecycle" to read and set bucket lifecycles (Nick Craig-Wood)</li>
-<li>Implement <code>--b2-lifecycle</code> to control lifecycle when creating buckets (Nick Craig-Wood)</li>
+<li>Implement "rclone backend lifecycle" to read and set bucket
+lifecycles (Nick Craig-Wood)</li>
+<li>Implement <code>--b2-lifecycle</code> to control lifecycle when
+creating buckets (Nick Craig-Wood)</li>
 <li>Fix listing all buckets when not needed (Nick Craig-Wood)</li>
-<li>Fix multi-thread upload with copyto going to wrong name (Nick Craig-Wood)</li>
-<li>Fix server side chunked copy when file size was exactly <code>--b2-copy-cutoff</code> (Nick Craig-Wood)</li>
-<li>Fix streaming chunked files an exact multiple of chunk size (Nick Craig-Wood)</li>
+<li>Fix multi-thread upload with copyto going to wrong name (Nick
+Craig-Wood)</li>
+<li>Fix server side chunked copy when file size was exactly
+<code>--b2-copy-cutoff</code> (Nick Craig-Wood)</li>
+<li>Fix streaming chunked files an exact multiple of chunk size (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Box
 <ul>
 <li>Filter more EventIDs when polling (David Sze)</li>
 <li>Add more logging for polling (David Sze)</li>
-<li>Fix performance problem reading metadata for single files (Nick Craig-Wood)</li>
+<li>Fix performance problem reading metadata for single files (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
 <li>Add read/write metadata support (Nick Craig-Wood)</li>
 <li>Add support for SHA-1 and SHA-256 checksums (rinsuki)</li>
-<li>Add <code>--drive-show-all-gdocs</code> to allow unexportable gdocs to be server side copied (Nick Craig-Wood)</li>
-<li>Add a note that <code>--drive-scope</code> accepts comma-separated list of scopes (Keigo Imai)</li>
-<li>Fix error updating created time metadata on existing object (Nick Craig-Wood)</li>
-<li>Fix integration tests by enabling metadata support from the context (Nick Craig-Wood)</li>
+<li>Add <code>--drive-show-all-gdocs</code> to allow unexportable gdocs
+to be server side copied (Nick Craig-Wood)</li>
+<li>Add a note that <code>--drive-scope</code> accepts comma-separated
+list of scopes (Keigo Imai)</li>
+<li>Fix error updating created time metadata on existing object (Nick
+Craig-Wood)</li>
+<li>Fix integration tests by enabling metadata support from the context
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -37916,7 +53608,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Fix 400 Bad request errors when using multi-thread copy (Nick Craig-Wood)</li>
+<li>Fix 400 Bad request errors when using multi-thread copy (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Googlephotos
 <ul>
@@ -37924,11 +53617,13 @@ $ tree /tmp/c
 </ul></li>
 <li>Hdfs
 <ul>
-<li>Added support for list of namenodes in hdfs remote config (Tayo-pasedaRJ)</li>
+<li>Added support for list of namenodes in hdfs remote config
+(Tayo-pasedaRJ)</li>
 </ul></li>
 <li>HTTP
 <ul>
-<li>Implement set backend command to update running backend (Nick Craig-Wood)</li>
+<li>Implement set backend command to update running backend (Nick
+Craig-Wood)</li>
 <li>Enable methods used with WebDAV (Alen Šiljak)</li>
 </ul></li>
 <li>Jottacloud
@@ -37937,65 +53632,88 @@ $ tree /tmp/c
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Implement ListR method which gives <code>--fast-list</code> support (Nick Craig-Wood)
+<li>Implement ListR method which gives <code>--fast-list</code> support
+(Nick Craig-Wood)
 <ul>
-<li>This must be enabled with the <code>--onedrive-delta</code> flag</li>
+<li>This must be enabled with the <code>--onedrive-delta</code>
+flag</li>
 </ul></li>
 </ul></li>
 <li>Quatrix
 <ul>
 <li>Add partial upload support (Oksana Zhykina)</li>
-<li>Overwrite files on conflict during server-side move (Oksana Zhykina)</li>
+<li>Overwrite files on conflict during server-side move (Oksana
+Zhykina)</li>
 </ul></li>
 <li>S3
 <ul>
 <li>Add Linode provider (Nick Craig-Wood)</li>
 <li>Add docs on how to add a new provider (Nick Craig-Wood)</li>
-<li>Fix no error being returned when creating a bucket we don't own (Nick Craig-Wood)</li>
-<li>Emit a debug message if anonymous credentials are in use (Nick Craig-Wood)</li>
-<li>Add <code>--s3-disable-multipart-uploads</code> flag (Nick Craig-Wood)</li>
+<li>Fix no error being returned when creating a bucket we don't own
+(Nick Craig-Wood)</li>
+<li>Emit a debug message if anonymous credentials are in use (Nick
+Craig-Wood)</li>
+<li>Add <code>--s3-disable-multipart-uploads</code> flag (Nick
+Craig-Wood)</li>
 <li>Detect looping when using gcs and versions (Nick Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Implement <code>--sftp-copy-is-hardlink</code> to server side copy as hardlink (Nick Craig-Wood)</li>
+<li>Implement <code>--sftp-copy-is-hardlink</code> to server side copy
+as hardlink (Nick Craig-Wood)</li>
 </ul></li>
 <li>Smb
 <ul>
-<li>Fix incorrect <code>about</code> size by switching to <code>github.com/cloudsoda/go-smb2</code> fork (Nick Craig-Wood)</li>
-<li>Fix modtime of multithread uploads by setting PartialUploads (Nick Craig-Wood)</li>
+<li>Fix incorrect <code>about</code> size by switching to
+<code>github.com/cloudsoda/go-smb2</code> fork (Nick Craig-Wood)</li>
+<li>Fix modtime of multithread uploads by setting PartialUploads (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Added an rclone vendor to work with <code>rclone serve webdav</code> (Adithya Kumar)</li>
+<li>Added an rclone vendor to work with <code>rclone serve webdav</code>
+(Adithya Kumar)</li>
 </ul></li>
 </ul>
 <h2 id="v1.64.2---2023-10-19">v1.64.2 - 2023-10-19</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.64.1...v1.64.2">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.64.1...v1.64.2">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>selfupdate: Fix "invalid hashsum signature" error (Nick Craig-Wood)</li>
+<li>selfupdate: Fix "invalid hashsum signature" error (Nick
+Craig-Wood)</li>
 <li>build: Fix docker build running out of space (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.64.1---2023-10-17">v1.64.1 - 2023-10-17</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.64.0...v1.64.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.64.0...v1.64.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>cmd: Make <code>--progress</code> output logs in the same format as without (Nick Craig-Wood)</li>
-<li>docs fixes (Dimitri Papadopoulos Orfanos, Herby Gillot, Manoj Ghosh, Nick Craig-Wood)</li>
-<li>lsjson: Make sure we set the global metadata flag too (Nick Craig-Wood)</li>
+<li>cmd: Make <code>--progress</code> output logs in the same format as
+without (Nick Craig-Wood)</li>
+<li>docs fixes (Dimitri Papadopoulos Orfanos, Herby Gillot, Manoj Ghosh,
+Nick Craig-Wood)</li>
+<li>lsjson: Make sure we set the global metadata flag too (Nick
+Craig-Wood)</li>
 <li>operations
 <ul>
-<li>Ensure concurrency is no greater than the number of chunks (Pat Patterson)</li>
-<li>Fix OpenOptions ignored in copy if operation was a multiThreadCopy (Vitor Gomes)</li>
+<li>Ensure concurrency is no greater than the number of chunks (Pat
+Patterson)</li>
+<li>Fix OpenOptions ignored in copy if operation was a multiThreadCopy
+(Vitor Gomes)</li>
 <li>Fix error message on delete to have file name (Nick Craig-Wood)</li>
 </ul></li>
-<li>serve sftp: Return not supported error for not supported commands (Nick Craig-Wood)</li>
-<li>build: Upgrade golang.org/x/net to v0.17.0 to fix HTTP/2 rapid reset (Nick Craig-Wood)</li>
-<li>pacer: Fix b2 deadlock by defaulting max connections to unlimited (Nick Craig-Wood)</li>
+<li>serve sftp: Return not supported error for not supported commands
+(Nick Craig-Wood)</li>
+<li>build: Upgrade golang.org/x/net to v0.17.0 to fix HTTP/2 rapid reset
+(Nick Craig-Wood)</li>
+<li>pacer: Fix b2 deadlock by defaulting max connections to unlimited
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
@@ -38011,24 +53729,31 @@ $ tree /tmp/c
 </ul></li>
 <li>B2
 <ul>
-<li>Fix multipart upload: corrupted on transfer: sizes differ XXX vs 0 (Nick Craig-Wood)</li>
-<li>Fix locking window when getting mutipart upload URL (Nick Craig-Wood)</li>
+<li>Fix multipart upload: corrupted on transfer: sizes differ XXX vs 0
+(Nick Craig-Wood)</li>
+<li>Fix locking window when getting mutipart upload URL (Nick
+Craig-Wood)</li>
 <li>Fix server side copies greater than 4GB (Nick Craig-Wood)</li>
 <li>Fix chunked streaming uploads (Nick Craig-Wood)</li>
-<li>Reduce default <code>--b2-upload-concurrency</code> to 4 to reduce memory usage (Nick Craig-Wood)</li>
+<li>Reduce default <code>--b2-upload-concurrency</code> to 4 to reduce
+memory usage (Nick Craig-Wood)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Fix the configurator to allow <code>/teams/ID</code> in the config (Nick Craig-Wood)</li>
+<li>Fix the configurator to allow <code>/teams/ID</code> in the config
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Oracleobjectstorage
 <ul>
-<li>Fix OpenOptions being ignored in uploadMultipart with chunkWriter (Nick Craig-Wood)</li>
+<li>Fix OpenOptions being ignored in uploadMultipart with chunkWriter
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Fix slice bounds out of range error when listing (Nick Craig-Wood)</li>
-<li>Fix OpenOptions being ignored in uploadMultipart with chunkWriter (Vitor Gomes)</li>
+<li>Fix slice bounds out of range error when listing (Nick
+Craig-Wood)</li>
+<li>Fix OpenOptions being ignored in uploadMultipart with chunkWriter
+(Vitor Gomes)</li>
 </ul></li>
 <li>Storj
 <ul>
@@ -38036,96 +53761,138 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.64.0---2023-09-11">v1.64.0 - 2023-09-11</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.63.0...v1.64.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.63.0...v1.64.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
-<li><a href="https://rclone.org/protondrive/">Proton Drive</a> (Chun-Hung Tseng)</li>
-<li><a href="https://rclone.org/quatrix/">Quatrix</a> (Oksana, Volodymyr Kit)</li>
+<li><a href="https://rclone.org/protondrive/">Proton Drive</a>
+(Chun-Hung Tseng)</li>
+<li><a href="https://rclone.org/quatrix/">Quatrix</a> (Oksana, Volodymyr
+Kit)</li>
 <li>New S3 providers
 <ul>
-<li><a href="https://rclone.org/s3/#synology-c2">Synology C2</a> (BakaWang)</li>
+<li><a href="https://rclone.org/s3/#synology-c2">Synology C2</a>
+(BakaWang)</li>
 <li><a href="https://rclone.org/s3/#leviia">Leviia</a> (Benjamin)</li>
 </ul></li>
 <li>New Jottacloud providers
 <ul>
 <li><a href="https://rclone.org/jottacloud/">Onlime</a> (Fjodor42)</li>
-<li><a href="https://rclone.org/jottacloud/">Telia Sky</a> (NoLooseEnds)</li>
+<li><a href="https://rclone.org/jottacloud/">Telia Sky</a>
+(NoLooseEnds)</li>
 </ul></li>
 </ul></li>
 <li>Major changes
 <ul>
-<li>Multi-thread transfers (Vitor Gomes, Nick Craig-Wood, Manoj Ghosh, Edwin Mackenzie-Owen)
+<li>Multi-thread transfers (Vitor Gomes, Nick Craig-Wood, Manoj Ghosh,
+Edwin Mackenzie-Owen)
 <ul>
 <li>Multi-thread transfers are now available when transferring to:
 <ul>
-<li><code>local</code>, <code>s3</code>, <code>azureblob</code>, <code>b2</code>, <code>oracleobjectstorage</code> and <code>smb</code></li>
+<li><code>local</code>, <code>s3</code>, <code>azureblob</code>,
+<code>b2</code>, <code>oracleobjectstorage</code> and
+<code>smb</code></li>
 </ul></li>
-<li>This greatly improves transfer speed between two network sources.</li>
-<li>In memory buffering has been unified between all backends and should share memory better.</li>
-<li>See <a href="https://rclone.org/docs/#multi-thread-cutoff">--multi-thread docs</a> for more info</li>
+<li>This greatly improves transfer speed between two network
+sources.</li>
+<li>In memory buffering has been unified between all backends and should
+share memory better.</li>
+<li>See <a
+href="https://rclone.org/docs/#multi-thread-cutoff">--multi-thread
+docs</a> for more info</li>
 </ul></li>
 </ul></li>
 <li>New commands
 <ul>
-<li><code>rclone config redacted</code> support mechanism for showing redacted config (Nick Craig-Wood)</li>
+<li><code>rclone config redacted</code> support mechanism for showing
+redacted config (Nick Craig-Wood)</li>
 </ul></li>
 <li>New Features
 <ul>
 <li>accounting
 <ul>
-<li>Show server side stats in own lines and not as bytes transferred (Nick Craig-Wood)</li>
+<li>Show server side stats in own lines and not as bytes transferred
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>bisync
 <ul>
-<li>Add new <code>--ignore-listing-checksum</code> flag to distinguish from <code>--ignore-checksum</code> (nielash)</li>
-<li>Add experimental <code>--resilient</code> mode to allow recovery from self-correctable errors (nielash)</li>
+<li>Add new <code>--ignore-listing-checksum</code> flag to distinguish
+from <code>--ignore-checksum</code> (nielash)</li>
+<li>Add experimental <code>--resilient</code> mode to allow recovery
+from self-correctable errors (nielash)</li>
 <li>Add support for <code>--create-empty-src-dirs</code> (nielash)</li>
 <li>Dry runs no longer commit filter changes (nielash)</li>
-<li>Enforce <code>--check-access</code> during <code>--resync</code> (nielash)</li>
+<li>Enforce <code>--check-access</code> during <code>--resync</code>
+(nielash)</li>
 <li>Apply filters correctly during deletes (nielash)</li>
-<li>Equality check before renaming (leave identical files alone) (nielash)</li>
+<li>Equality check before renaming (leave identical files alone)
+(nielash)</li>
 <li>Fix <code>dryRun</code> rc parameter being ignored (nielash)</li>
 </ul></li>
 <li>build
 <ul>
-<li>Update to <code>go1.21</code> and make <code>go1.19</code> the minimum required version (Anagh Kumar Baranwal, Nick Craig-Wood)</li>
+<li>Update to <code>go1.21</code> and make <code>go1.19</code> the
+minimum required version (Anagh Kumar Baranwal, Nick Craig-Wood)</li>
 <li>Update dependencies (Nick Craig-Wood)</li>
 <li>Add snap installation (hideo aoyama)</li>
-<li>Change Winget Releaser job to <code>ubuntu-latest</code> (sitiom)</li>
+<li>Change Winget Releaser job to <code>ubuntu-latest</code>
+(sitiom)</li>
 </ul></li>
 <li>cmd: Refactor and use sysdnotify in more commands (eNV25)</li>
-<li>config: Add <code>--multi-thread-chunk-size</code> flag (Vitor Gomes)</li>
-<li>doc updates (antoinetran, Benjamin, Bjørn Smith, Dean Attali, gabriel-suela, James Braza, Justin Hellings, kapitainsky, Mahad, Masamune3210, Nick Craig-Wood, Nihaal Sangha, Niklas Hambüchen, Raymond Berger, r-ricci, Sawada Tsunayoshi, Tiago Boeing, Vladislav Vorobev)</li>
+<li>config: Add <code>--multi-thread-chunk-size</code> flag (Vitor
+Gomes)</li>
+<li>doc updates (antoinetran, Benjamin, Bjørn Smith, Dean Attali,
+gabriel-suela, James Braza, Justin Hellings, kapitainsky, Mahad,
+Masamune3210, Nick Craig-Wood, Nihaal Sangha, Niklas Hambüchen, Raymond
+Berger, r-ricci, Sawada Tsunayoshi, Tiago Boeing, Vladislav
+Vorobev)</li>
 <li>fs
 <ul>
 <li>Use atomic types everywhere (Roberto Ricci)</li>
-<li>When <code>--max-transfer</code> limit is reached exit with code (10) (kapitainsky)</li>
-<li>Add rclone completion powershell - basic implementation only (Nick Craig-Wood)</li>
+<li>When <code>--max-transfer</code> limit is reached exit with code
+(10) (kapitainsky)</li>
+<li>Add rclone completion powershell - basic implementation only (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>http servers: Allow CORS to be set with <code>--allow-origin</code> flag (yuudi)</li>
-<li>lib/rest: Remove unnecessary <code>nil</code> check (Eng Zer Jun)</li>
+<li>http servers: Allow CORS to be set with <code>--allow-origin</code>
+flag (yuudi)</li>
+<li>lib/rest: Remove unnecessary <code>nil</code> check (Eng Zer
+Jun)</li>
 <li>ncdu: Add keybinding to rescan filesystem (eNV25)</li>
 <li>rc
 <ul>
 <li>Add <code>executeId</code> to job listings (yuudi)</li>
-<li>Add <code>core/du</code> to measure local disk usage (Nick Craig-Wood)</li>
+<li>Add <code>core/du</code> to measure local disk usage (Nick
+Craig-Wood)</li>
 <li>Add <code>operations/settier</code> to API (Drew Stinnett)</li>
 </ul></li>
-<li>rclone test info: Add <code>--check-base32768</code> flag to check can store all base32768 characters (Nick Craig-Wood)</li>
-<li>rmdirs: Remove directories concurrently controlled by <code>--checkers</code> (Nick Craig-Wood)</li>
+<li>rclone test info: Add <code>--check-base32768</code> flag to check
+can store all base32768 characters (Nick Craig-Wood)</li>
+<li>rmdirs: Remove directories concurrently controlled by
+<code>--checkers</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>accounting: Don't stop calculating average transfer speed until the operation is complete (Jacob Hands)</li>
-<li>fs: Fix <code>transferTime</code> not being set in JSON logs (Jacob Hands)</li>
-<li>fshttp: Fix <code>--bind 0.0.0.0</code> allowing IPv6 and <code>--bind ::0</code> allowing IPv4 (Nick Craig-Wood)</li>
-<li>operations: Fix overlapping check on case insensitive file systems (Nick Craig-Wood)</li>
-<li>serve dlna: Fix MIME type if backend can't identify it (Nick Craig-Wood)</li>
-<li>serve ftp: Fix race condition when using the auth proxy (Nick Craig-Wood)</li>
-<li>serve sftp: Fix hash calculations with <code>--vfs-cache-mode full</code> (Nick Craig-Wood)</li>
-<li>serve webdav: Fix error: Expecting fs.Object or fs.Directory, got <code>nil</code> (Nick Craig-Wood)</li>
-<li>sync: Fix lockup with <code>--cutoff-mode=soft</code> and <code>--max-duration</code> (Nick Craig-Wood)</li>
+<li>accounting: Don't stop calculating average transfer speed until the
+operation is complete (Jacob Hands)</li>
+<li>fs: Fix <code>transferTime</code> not being set in JSON logs (Jacob
+Hands)</li>
+<li>fshttp: Fix <code>--bind 0.0.0.0</code> allowing IPv6 and
+<code>--bind ::0</code> allowing IPv4 (Nick Craig-Wood)</li>
+<li>operations: Fix overlapping check on case insensitive file systems
+(Nick Craig-Wood)</li>
+<li>serve dlna: Fix MIME type if backend can't identify it (Nick
+Craig-Wood)</li>
+<li>serve ftp: Fix race condition when using the auth proxy (Nick
+Craig-Wood)</li>
+<li>serve sftp: Fix hash calculations with
+<code>--vfs-cache-mode full</code> (Nick Craig-Wood)</li>
+<li>serve webdav: Fix error: Expecting fs.Object or fs.Directory, got
+<code>nil</code> (Nick Craig-Wood)</li>
+<li>sync: Fix lockup with <code>--cutoff-mode=soft</code> and
+<code>--max-duration</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
@@ -38133,11 +53900,16 @@ $ tree /tmp/c
 </ul></li>
 <li>VFS
 <ul>
-<li>Add <code>--vfs-cache-min-free-space</code> to control minimum free space on the disk containing the cache (Nick Craig-Wood)</li>
-<li>Added cache cleaner for directories to reduce memory usage (Anagh Kumar Baranwal)</li>
-<li>Update parent directory modtimes on vfs actions (David Pedersen)</li>
-<li>Keep virtual directory status accurate and reduce deadlock potential (Anagh Kumar Baranwal)</li>
-<li>Make sure struct field is aligned for atomic access (Roberto Ricci)</li>
+<li>Add <code>--vfs-cache-min-free-space</code> to control minimum free
+space on the disk containing the cache (Nick Craig-Wood)</li>
+<li>Added cache cleaner for directories to reduce memory usage (Anagh
+Kumar Baranwal)</li>
+<li>Update parent directory modtimes on vfs actions (David
+Pedersen)</li>
+<li>Keep virtual directory status accurate and reduce deadlock potential
+(Anagh Kumar Baranwal)</li>
+<li>Make sure struct field is aligned for atomic access (Roberto
+Ricci)</li>
 </ul></li>
 <li>Local
 <ul>
@@ -38145,24 +53917,30 @@ $ tree /tmp/c
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Implement <code>OpenChunkWriter</code> and multi-thread uploads (Nick Craig-Wood)</li>
+<li>Implement <code>OpenChunkWriter</code> and multi-thread uploads
+(Nick Craig-Wood)</li>
 <li>Fix creation of directory markers (Nick Craig-Wood)</li>
 <li>Fix purging with directory markers (Nick Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
-<li>Implement <code>OpenChunkWriter</code> and multi-thread uploads (Nick Craig-Wood)</li>
-<li>Fix rclone link when object path contains special characters (Alishan Ladhani)</li>
+<li>Implement <code>OpenChunkWriter</code> and multi-thread uploads
+(Nick Craig-Wood)</li>
+<li>Fix rclone link when object path contains special characters
+(Alishan Ladhani)</li>
 </ul></li>
 <li>Box
 <ul>
 <li>Add polling support (David Sze)</li>
-<li>Add <code>--box-impersonate</code> to impersonate a user ID (Nick Craig-Wood)</li>
-<li>Fix unhelpful decoding of error messages into decimal numbers (Nick Craig-Wood)</li>
+<li>Add <code>--box-impersonate</code> to impersonate a user ID (Nick
+Craig-Wood)</li>
+<li>Fix unhelpful decoding of error messages into decimal numbers (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
-<li>Update documentation to mention issue with small files (Ricardo D'O. Albanus)</li>
+<li>Update documentation to mention issue with small files (Ricardo D'O.
+Albanus)</li>
 </ul></li>
 <li>Compress
 <ul>
@@ -38170,7 +53948,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Add <code>--drive-fast-list-bug-fix</code> to control ListR bug workaround (Nick Craig-Wood)</li>
+<li>Add <code>--drive-fast-list-bug-fix</code> to control ListR bug
+workaround (Nick Craig-Wood)</li>
 </ul></li>
 <li>Fichier
 <ul>
@@ -38180,12 +53959,15 @@ $ tree /tmp/c
 <li>FTP
 <ul>
 <li>Add socks_proxy support for SOCKS5 proxies (Zach)</li>
-<li>Fix 425 "TLS session of data connection not resumed" errors (Nick Craig-Wood)</li>
+<li>Fix 425 "TLS session of data connection not resumed" errors (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Hdfs
 <ul>
-<li>Retry "replication in progress" errors when uploading (Nick Craig-Wood)</li>
-<li>Fix uploading to the wrong object on Update with overridden remote name (Nick Craig-Wood)</li>
+<li>Retry "replication in progress" errors when uploading (Nick
+Craig-Wood)</li>
+<li>Fix uploading to the wrong object on Update with overridden remote
+name (Nick Craig-Wood)</li>
 </ul></li>
 <li>HTTP
 <ul>
@@ -38194,32 +53976,43 @@ $ tree /tmp/c
 </ul></li>
 <li>Opendrive
 <ul>
-<li>Fix List on a just deleted and remade directory (Nick Craig-Wood)</li>
+<li>Fix List on a just deleted and remade directory (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Oracleobjectstorage
 <ul>
 <li>Use rclone's rate limiter in multipart transfers (Manoj Ghosh)</li>
-<li>Implement <code>OpenChunkWriter</code> and multi-thread uploads (Manoj Ghosh)</li>
+<li>Implement <code>OpenChunkWriter</code> and multi-thread uploads
+(Manoj Ghosh)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Refactor multipart upload to use <code>OpenChunkWriter</code> and <code>ChunkWriter</code> (Vitor Gomes)</li>
-<li>Factor generic multipart upload into <code>lib/multipart</code> (Nick Craig-Wood)</li>
-<li>Fix purging of root directory with <code>--s3-directory-markers</code> (Nick Craig-Wood)</li>
-<li>Add <code>rclone backend set</code> command to update the running config (Nick Craig-Wood)</li>
-<li>Add <code>rclone backend restore-status</code> command (Nick Craig-Wood)</li>
+<li>Refactor multipart upload to use <code>OpenChunkWriter</code> and
+<code>ChunkWriter</code> (Vitor Gomes)</li>
+<li>Factor generic multipart upload into <code>lib/multipart</code>
+(Nick Craig-Wood)</li>
+<li>Fix purging of root directory with
+<code>--s3-directory-markers</code> (Nick Craig-Wood)</li>
+<li>Add <code>rclone backend set</code> command to update the running
+config (Nick Craig-Wood)</li>
+<li>Add <code>rclone backend restore-status</code> command (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Stop uploads re-using the same ssh connection to improve performance (Nick Craig-Wood)</li>
-<li>Add <code>--sftp-ssh</code> to specify an external ssh binary to use (Nick Craig-Wood)</li>
+<li>Stop uploads re-using the same ssh connection to improve performance
+(Nick Craig-Wood)</li>
+<li>Add <code>--sftp-ssh</code> to specify an external ssh binary to use
+(Nick Craig-Wood)</li>
 <li>Add socks_proxy support for SOCKS5 proxies (Zach)</li>
 <li>Support dynamic <code>--sftp-path-override</code> (nielash)</li>
-<li>Fix spurious warning when using <code>--sftp-ssh</code> (Nick Craig-Wood)</li>
+<li>Fix spurious warning when using <code>--sftp-ssh</code> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Smb
 <ul>
-<li>Implement multi-threaded writes for copies to smb (Edwin Mackenzie-Owen)</li>
+<li>Implement multi-threaded writes for copies to smb (Edwin
+Mackenzie-Owen)</li>
 </ul></li>
 <li>Storj
 <ul>
@@ -38227,11 +54020,13 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Fix HEADing 0-length objects when <code>--swift-no-large-objects</code> set (Julian Lepinski)</li>
+<li>Fix HEADing 0-length objects when
+<code>--swift-no-large-objects</code> set (Julian Lepinski)</li>
 </ul></li>
 <li>Union
 <ul>
-<li>Add <code>:writback</code> to act as a simple cache (Nick Craig-Wood)</li>
+<li>Add <code>:writback</code> to act as a simple cache (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
@@ -38239,26 +54034,35 @@ $ tree /tmp/c
 </ul></li>
 <li>Zoho
 <ul>
-<li>Remove Range requests workarounds to fix integration tests (Nick Craig-Wood)</li>
+<li>Remove Range requests workarounds to fix integration tests (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.63.1---2023-07-17">v1.63.1 - 2023-07-17</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.63.0...v1.63.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.63.0...v1.63.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>build: Fix macos builds for versions &lt; 12 (Anagh Kumar Baranwal)</li>
-<li>dirtree: Fix performance with large directories of directories and <code>--fast-list</code> (Nick Craig-Wood)</li>
+<li>build: Fix macos builds for versions &lt; 12 (Anagh Kumar
+Baranwal)</li>
+<li>dirtree: Fix performance with large directories of directories and
+<code>--fast-list</code> (Nick Craig-Wood)</li>
 <li>operations
 <ul>
-<li>Fix deadlock when using <code>lsd</code>/<code>ls</code> with <code>--progress</code> (Nick Craig-Wood)</li>
-<li>Fix <code>.rclonelink</code> files not being converted back to symlinks (Nick Craig-Wood)</li>
+<li>Fix deadlock when using <code>lsd</code>/<code>ls</code> with
+<code>--progress</code> (Nick Craig-Wood)</li>
+<li>Fix <code>.rclonelink</code> files not being converted back to
+symlinks (Nick Craig-Wood)</li>
 </ul></li>
-<li>doc fixes (Dean Attali, Mahad, Nick Craig-Wood, Sawada Tsunayoshi, Vladislav Vorobev)</li>
+<li>doc fixes (Dean Attali, Mahad, Nick Craig-Wood, Sawada Tsunayoshi,
+Vladislav Vorobev)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix partial directory read for corrupted filesystem (Nick Craig-Wood)</li>
+<li>Fix partial directory read for corrupted filesystem (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Box
 <ul>
@@ -38266,111 +54070,167 @@ $ tree /tmp/c
 </ul></li>
 <li>Smb
 <ul>
-<li>Fix "Statfs failed: bucket or container name is needed" when mounting (Nick Craig-Wood)</li>
+<li>Fix "Statfs failed: bucket or container name is needed" when
+mounting (Nick Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Nextcloud: fix must use /dav/files/USER endpoint not /webdav error (Paul)</li>
-<li>Nextcloud chunking: add more guidance for the user to check the config (darix)</li>
+<li>Nextcloud: fix must use /dav/files/USER endpoint not /webdav error
+(Paul)</li>
+<li>Nextcloud chunking: add more guidance for the user to check the
+config (darix)</li>
 </ul></li>
 </ul>
 <h2 id="v1.63.0---2023-06-30">v1.63.0 - 2023-06-30</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.62.0...v1.63.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.62.0...v1.63.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
 <li><a href="https://rclone.org/pikpak/">Pikpak</a> (wiserain)</li>
 <li>New S3 providers
 <ul>
-<li><a href="https://rclone.org/s3/#petabox">petabox.io</a> (Andrei Smirnov)</li>
-<li><a href="https://rclone.org/s3/#google-cloud-storage">Google Cloud Storage</a> (Anthony Pessy)</li>
+<li><a href="https://rclone.org/s3/#petabox">petabox.io</a> (Andrei
+Smirnov)</li>
+<li><a href="https://rclone.org/s3/#google-cloud-storage">Google Cloud
+Storage</a> (Anthony Pessy)</li>
 </ul></li>
 <li>New WebDAV providers
 <ul>
-<li><a href="https://rclone.org/webdav/#fastmail-files">Fastmail</a> (Arnavion)</li>
+<li><a href="https://rclone.org/webdav/#fastmail-files">Fastmail</a>
+(Arnavion)</li>
 </ul></li>
 </ul></li>
 <li>Major changes
 <ul>
-<li>Files will be copied to a temporary name ending in <code>.partial</code> when copying to <code>local</code>,<code>ftp</code>,<code>sftp</code> then renamed at the end of the transfer. (Janne Hellsten, Nick Craig-Wood)
+<li>Files will be copied to a temporary name ending in
+<code>.partial</code> when copying to
+<code>local</code>,<code>ftp</code>,<code>sftp</code> then renamed at
+the end of the transfer. (Janne Hellsten, Nick Craig-Wood)
 <ul>
-<li>This helps with data integrity as we don't delete the existing file until the new one is complete.</li>
-<li>It can be disabled with the <a href="https://rclone.org/docs/#inplace">--inplace</a> flag.</li>
-<li>This behaviour will also happen if the backend is wrapped, for example <code>sftp</code> wrapped with <code>crypt</code>.</li>
+<li>This helps with data integrity as we don't delete the existing file
+until the new one is complete.</li>
+<li>It can be disabled with the <a
+href="https://rclone.org/docs/#inplace">--inplace</a> flag.</li>
+<li>This behaviour will also happen if the backend is wrapped, for
+example <code>sftp</code> wrapped with <code>crypt</code>.</li>
 </ul></li>
-<li>The <a href="https://rclone.org/s3/#s3-directory-markers">s3</a>, <a href="/azureblob/#azureblob-directory-markers">azureblob</a> and <a href="/googlecloudstorage/#gcs-directory-markers">gcs</a> backends now support directory markers so empty directories are supported (Jānis Bebrītis, Nick Craig-Wood)</li>
-<li>The <a href="https://rclone.org/docs/#default-time-time">--default-time</a> flag now controls the unknown modification time of files/dirs (Nick Craig-Wood)
+<li>The <a href="https://rclone.org/s3/#s3-directory-markers">s3</a>, <a
+href="/azureblob/#azureblob-directory-markers">azureblob</a> and <a
+href="/googlecloudstorage/#gcs-directory-markers">gcs</a> backends now
+support directory markers so empty directories are supported (Jānis
+Bebrītis, Nick Craig-Wood)</li>
+<li>The <a
+href="https://rclone.org/docs/#default-time-time">--default-time</a>
+flag now controls the unknown modification time of files/dirs (Nick
+Craig-Wood)
 <ul>
-<li>If a file or directory does not have a modification time rclone can read then rclone will display this fixed time instead.</li>
-<li>For the old behaviour use <code>--default-time 0s</code> which will set this time to the time rclone started up.</li>
+<li>If a file or directory does not have a modification time rclone can
+read then rclone will display this fixed time instead.</li>
+<li>For the old behaviour use <code>--default-time 0s</code> which will
+set this time to the time rclone started up.</li>
 </ul></li>
 </ul></li>
 <li>New Features
 <ul>
 <li>build
 <ul>
-<li>Modernise linters in use and fixup all affected code (albertony)</li>
-<li>Push docker beta to GHCR (GitHub container registry) (Richard Tweed)</li>
+<li>Modernise linters in use and fixup all affected code
+(albertony)</li>
+<li>Push docker beta to GHCR (GitHub container registry) (Richard
+Tweed)</li>
 </ul></li>
-<li>cat: Add <code>--separator</code> option to cat command (Loren Gordon)</li>
+<li>cat: Add <code>--separator</code> option to cat command (Loren
+Gordon)</li>
 <li>config
 <ul>
-<li>Do not remove/overwrite other files during config file save (albertony)</li>
+<li>Do not remove/overwrite other files during config file save
+(albertony)</li>
 <li>Do not overwrite config file symbolic link (albertony)</li>
-<li>Stop <code>config create</code> making invalid config files (Nick Craig-Wood)</li>
+<li>Stop <code>config create</code> making invalid config files (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>doc updates (Adam K, Aditya Basu, albertony, asdffdsazqqq, Damo, danielkrajnik, Dimitri Papadopoulos, dlitster, Drew Parsons, jumbi77, kapitainsky, mac-15, Mariusz Suchodolski, Nick Craig-Wood, NickIAm, Rintze Zelle, Stanislav Gromov, Tareq Sharafy, URenko, yuudi, Zach Kipp)</li>
+<li>doc updates (Adam K, Aditya Basu, albertony, asdffdsazqqq, Damo,
+danielkrajnik, Dimitri Papadopoulos, dlitster, Drew Parsons, jumbi77,
+kapitainsky, mac-15, Mariusz Suchodolski, Nick Craig-Wood, NickIAm,
+Rintze Zelle, Stanislav Gromov, Tareq Sharafy, URenko, yuudi, Zach
+Kipp)</li>
 <li>fs
 <ul>
-<li>Add <code>size</code> to JSON logs when moving or copying an object (Nick Craig-Wood)</li>
-<li>Allow boolean features to be enabled with <code>--disable !Feature</code> (Nick Craig-Wood)</li>
+<li>Add <code>size</code> to JSON logs when moving or copying an object
+(Nick Craig-Wood)</li>
+<li>Allow boolean features to be enabled with
+<code>--disable !Feature</code> (Nick Craig-Wood)</li>
 </ul></li>
-<li>genautocomplete: Rename to <code>completion</code> with alias to the old name (Nick Craig-Wood)</li>
-<li>librclone: Added example on using <code>librclone</code> with Go (alankrit)</li>
-<li>lsjson: Make <code>--stat</code> more efficient (Nick Craig-Wood)</li>
+<li>genautocomplete: Rename to <code>completion</code> with alias to the
+old name (Nick Craig-Wood)</li>
+<li>librclone: Added example on using <code>librclone</code> with Go
+(alankrit)</li>
+<li>lsjson: Make <code>--stat</code> more efficient (Nick
+Craig-Wood)</li>
 <li>operations
 <ul>
-<li>Implement <code>--multi-thread-write-buffer-size</code> for speed improvements on downloads (Paulo Schreiner)</li>
-<li>Reopen downloads on error when using <code>check --download</code> and <code>cat</code> (Nick Craig-Wood)</li>
+<li>Implement <code>--multi-thread-write-buffer-size</code> for speed
+improvements on downloads (Paulo Schreiner)</li>
+<li>Reopen downloads on error when using <code>check --download</code>
+and <code>cat</code> (Nick Craig-Wood)</li>
 </ul></li>
-<li>rc: <code>config/listremotes</code> includes remotes defined with environment variables (kapitainsky)</li>
-<li>selfupdate: Obey <code>--no-check-certificate</code> flag (Nick Craig-Wood)</li>
+<li>rc: <code>config/listremotes</code> includes remotes defined with
+environment variables (kapitainsky)</li>
+<li>selfupdate: Obey <code>--no-check-certificate</code> flag (Nick
+Craig-Wood)</li>
 <li>serve restic: Trigger systemd notify (Shyim)</li>
-<li>serve webdav: Implement owncloud checksum and modtime extensions (WeidiDeng)</li>
-<li>sync: <code>--suffix-keep-extension</code> preserve 2 part extensions like .tar.gz (Nick Craig-Wood)</li>
+<li>serve webdav: Implement owncloud checksum and modtime extensions
+(WeidiDeng)</li>
+<li>sync: <code>--suffix-keep-extension</code> preserve 2 part
+extensions like .tar.gz (Nick Craig-Wood)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>accounting
 <ul>
-<li>Fix Prometheus metrics to be the same as <code>core/stats</code> (Nick Craig-Wood)</li>
+<li>Fix Prometheus metrics to be the same as <code>core/stats</code>
+(Nick Craig-Wood)</li>
 <li>Bwlimit signal handler should always start (Sam Lai)</li>
 </ul></li>
-<li>bisync: Fix <code>maxDelete</code> parameter being ignored via the rc (Nick Craig-Wood)</li>
+<li>bisync: Fix <code>maxDelete</code> parameter being ignored via the
+rc (Nick Craig-Wood)</li>
 <li>cmd/ncdu: Fix screen corruption when logging (eNV25)</li>
-<li>filter: Fix deadlock with errors on <code>--files-from</code> (douchen)</li>
+<li>filter: Fix deadlock with errors on <code>--files-from</code>
+(douchen)</li>
 <li>fs
 <ul>
-<li>Fix interaction between <code>--progress</code> and <code>--interactive</code> (Nick Craig-Wood)</li>
-<li>Fix infinite recursive call in pacer ModifyCalculator (fixes issue reported by the staticcheck linter) (albertony)</li>
+<li>Fix interaction between <code>--progress</code> and
+<code>--interactive</code> (Nick Craig-Wood)</li>
+<li>Fix infinite recursive call in pacer ModifyCalculator (fixes issue
+reported by the staticcheck linter) (albertony)</li>
 </ul></li>
-<li>lib/atexit: Ensure OnError only calls cancel function once (Nick Craig-Wood)</li>
-<li>lib/rest: Fix problems re-using HTTP connections (Nick Craig-Wood)</li>
+<li>lib/atexit: Ensure OnError only calls cancel function once (Nick
+Craig-Wood)</li>
+<li>lib/rest: Fix problems re-using HTTP connections (Nick
+Craig-Wood)</li>
 <li>rc
 <ul>
-<li>Fix <code>operations/stat</code> with trailing <code>/</code> (Nick Craig-Wood)</li>
+<li>Fix <code>operations/stat</code> with trailing <code>/</code> (Nick
+Craig-Wood)</li>
 <li>Fix missing <code>--rc</code> flags (Nick Craig-Wood)</li>
-<li>Fix output of Time values in <code>options/get</code> (Nick Craig-Wood)</li>
+<li>Fix output of Time values in <code>options/get</code> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>serve dlna: Fix potential data race (Nick Craig-Wood)</li>
 <li>version: Fix reported os/kernel version for windows (albertony)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Add <code>--mount-case-insensitive</code> to force the mount to be case insensitive (Nick Craig-Wood)</li>
-<li>Removed unnecessary byte slice allocation for reads (Anagh Kumar Baranwal)</li>
-<li>Clarify rclone mount error when installed via homebrew (Nick Craig-Wood)</li>
-<li>Added _netdev to the example mount so it gets treated as a remote-fs rather than local-fs (Anagh Kumar Baranwal)</li>
+<li>Add <code>--mount-case-insensitive</code> to force the mount to be
+case insensitive (Nick Craig-Wood)</li>
+<li>Removed unnecessary byte slice allocation for reads (Anagh Kumar
+Baranwal)</li>
+<li>Clarify rclone mount error when installed via homebrew (Nick
+Craig-Wood)</li>
+<li>Added _netdev to the example mount so it gets treated as a remote-fs
+rather than local-fs (Anagh Kumar Baranwal)</li>
 </ul></li>
 <li>Mount2
 <ul>
@@ -38380,37 +54240,50 @@ $ tree /tmp/c
 </ul></li>
 <li>VFS
 <ul>
-<li>Add MkdirAll function to make a directory and all beneath (Nick Craig-Wood)</li>
-<li>Fix reload: failed to add virtual dir entry: file does not exist (Nick Craig-Wood)</li>
-<li>Fix writing to a read only directory creating spurious directory entries (WeidiDeng)</li>
+<li>Add MkdirAll function to make a directory and all beneath (Nick
+Craig-Wood)</li>
+<li>Fix reload: failed to add virtual dir entry: file does not exist
+(Nick Craig-Wood)</li>
+<li>Fix writing to a read only directory creating spurious directory
+entries (WeidiDeng)</li>
 <li>Fix potential data race (Nick Craig-Wood)</li>
-<li>Fix backends being Shutdown too early when startup takes a long time (Nick Craig-Wood)</li>
+<li>Fix backends being Shutdown too early when startup takes a long time
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix filtering of symlinks with <code>-l</code>/<code>--links</code> flag (Nick Craig-Wood)</li>
-<li>Fix /path/to/file.rclonelink when <code>-l</code>/<code>--links</code> is in use (Nick Craig-Wood)</li>
-<li>Fix crash with <code>--metadata</code> on Android (Nick Craig-Wood)</li>
+<li>Fix filtering of symlinks with <code>-l</code>/<code>--links</code>
+flag (Nick Craig-Wood)</li>
+<li>Fix /path/to/file.rclonelink when
+<code>-l</code>/<code>--links</code> is in use (Nick Craig-Wood)</li>
+<li>Fix crash with <code>--metadata</code> on Android (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
-<li>Fix backends shutting down when in use when used via the rc (Nick Craig-Wood)</li>
+<li>Fix backends shutting down when in use when used via the rc (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Add <code>--crypt-suffix</code> option to set a custom suffix for encrypted files (jladbrook)</li>
-<li>Add <code>--crypt-pass-bad-blocks</code> to allow corrupted file output (Nick Craig-Wood)</li>
+<li>Add <code>--crypt-suffix</code> option to set a custom suffix for
+encrypted files (jladbrook)</li>
+<li>Add <code>--crypt-pass-bad-blocks</code> to allow corrupted file
+output (Nick Craig-Wood)</li>
 <li>Fix reading 0 length files (Nick Craig-Wood)</li>
 <li>Try not to return "unexpected EOF" error (Nick Craig-Wood)</li>
 <li>Reduce allocations (albertony)</li>
-<li>Recommend Dropbox for <code>base32768</code> encoding (Nick Craig-Wood)</li>
+<li>Recommend Dropbox for <code>base32768</code> encoding (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
 <li>Empty directory markers (Nick Craig-Wood)</li>
 <li>Support azure workload identities (Tareq Sharafy)</li>
-<li>Fix azure blob uploads with multiple bits of metadata (Nick Craig-Wood)</li>
-<li>Fix azurite compatibility by sending nil tier if set to empty string (Roel Arents)</li>
+<li>Fix azure blob uploads with multiple bits of metadata (Nick
+Craig-Wood)</li>
+<li>Fix azurite compatibility by sending nil tier if set to empty string
+(Roel Arents)</li>
 </ul></li>
 <li>Combine
 <ul>
@@ -38419,83 +54292,109 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Add <code>--drive-env-auth</code> to get IAM credentials from runtime (Peter Brunner)</li>
+<li>Add <code>--drive-env-auth</code> to get IAM credentials from
+runtime (Peter Brunner)</li>
 <li>Update drive service account guide (Juang, Yi-Lin)</li>
-<li>Fix change notify picking up files outside the root (Nick Craig-Wood)</li>
-<li>Fix trailing slash mis-identificaton of folder as file (Nick Craig-Wood)</li>
+<li>Fix change notify picking up files outside the root (Nick
+Craig-Wood)</li>
+<li>Fix trailing slash mis-identificaton of folder as file (Nick
+Craig-Wood)</li>
 <li>Fix incorrect remote after Update on object (Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Implement <code>--dropbox-pacer-min-sleep</code> flag (Nick Craig-Wood)</li>
+<li>Implement <code>--dropbox-pacer-min-sleep</code> flag (Nick
+Craig-Wood)</li>
 <li>Fix the dropbox batcher stalling (Misty)</li>
 </ul></li>
 <li>Fichier
 <ul>
-<li>Add <code>--ficicher-cdn</code> option to use the CDN for download (Nick Craig-Wood)</li>
+<li>Add <code>--ficicher-cdn</code> option to use the CDN for download
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Lower log message priority when <code>SetModTime</code> is not supported to debug (Tobias Gion)</li>
+<li>Lower log message priority when <code>SetModTime</code> is not
+supported to debug (Tobias Gion)</li>
 <li>Fix "unsupported LIST line" errors on startup (Nick Craig-Wood)</li>
-<li>Fix "501 Not a valid pathname." errors when creating directories (Nick Craig-Wood)</li>
+<li>Fix "501 Not a valid pathname." errors when creating directories
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
 <li>Empty directory markers (Jānis Bebrītis, Nick Craig-Wood)</li>
-<li>Added <code>--gcs-user-project</code> needed for requester pays (Christopher Merry)</li>
+<li>Added <code>--gcs-user-project</code> needed for requester pays
+(Christopher Merry)</li>
 </ul></li>
 <li>HTTP
 <ul>
-<li>Add client certificate user auth middleware. This can auth <code>serve restic</code> from the username in the client cert. (Peter Fern)</li>
+<li>Add client certificate user auth middleware. This can auth
+<code>serve restic</code> from the username in the client cert. (Peter
+Fern)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
-<li>Fix vfs writeback stuck in a failed upload loop with file versioning disabled (albertony)</li>
+<li>Fix vfs writeback stuck in a failed upload loop with file versioning
+disabled (albertony)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Add <code>--onedrive-av-override</code> flag to download files flagged as virus (Nick Craig-Wood)</li>
+<li>Add <code>--onedrive-av-override</code> flag to download files
+flagged as virus (Nick Craig-Wood)</li>
 <li>Fix quickxorhash on 32 bit architectures (Nick Craig-Wood)</li>
-<li>Report any list errors during <code>rclone cleanup</code> (albertony)</li>
+<li>Report any list errors during <code>rclone cleanup</code>
+(albertony)</li>
 </ul></li>
 <li>Putio
 <ul>
-<li>Fix uploading to the wrong object on Update with overridden remote name (Nick Craig-Wood)</li>
-<li>Fix modification times not being preserved for server side copy and move (Nick Craig-Wood)</li>
+<li>Fix uploading to the wrong object on Update with overridden remote
+name (Nick Craig-Wood)</li>
+<li>Fix modification times not being preserved for server side copy and
+move (Nick Craig-Wood)</li>
 <li>Fix server side copy failures (400 errors) (Nick Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
 <li>Empty directory markers (Jānis Bebrītis, Nick Craig-Wood)</li>
 <li>Update Scaleway storage classes (Brian Starkey)</li>
-<li>Fix <code>--s3-versions</code> on individual objects (Nick Craig-Wood)</li>
-<li>Fix hang on aborting multipart upload with iDrive e2 (Nick Craig-Wood)</li>
+<li>Fix <code>--s3-versions</code> on individual objects (Nick
+Craig-Wood)</li>
+<li>Fix hang on aborting multipart upload with iDrive e2 (Nick
+Craig-Wood)</li>
 <li>Fix missing "tier" metadata (Nick Craig-Wood)</li>
 <li>Fix V3sign: add missing subresource delete (cc)</li>
-<li>Fix Arvancloud Domain and region changes and alphabetise the provider (Ehsan Tadayon)</li>
+<li>Fix Arvancloud Domain and region changes and alphabetise the
+provider (Ehsan Tadayon)</li>
 <li>Fix Qiniu KODO quirks virtualHostStyle is false (zzq)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Add <code>--sftp-host-key-algorithms</code> to allow specifying SSH host key algorithms (Joel)</li>
-<li>Fix using <code>--sftp-key-use-agent</code> and <code>--sftp-key-file</code> together needing private key file (Arnav Singh)</li>
+<li>Add <code>--sftp-host-key-algorithms</code> to allow specifying SSH
+host key algorithms (Joel)</li>
+<li>Fix using <code>--sftp-key-use-agent</code> and
+<code>--sftp-key-file</code> together needing private key file (Arnav
+Singh)</li>
 <li>Fix move to allow overwriting existing files (Nick Craig-Wood)</li>
 <li>Don't stat directories before listing them (Nick Craig-Wood)</li>
-<li>Don't check remote points to a file if it ends with / (Nick Craig-Wood)</li>
+<li>Don't check remote points to a file if it ends with / (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Sharefile
 <ul>
-<li>Disable streamed transfers as they no longer work (Nick Craig-Wood)</li>
+<li>Disable streamed transfers as they no longer work (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Smb
 <ul>
-<li>Code cleanup to avoid overwriting ctx before first use (fixes issue reported by the staticcheck linter) (albertony)</li>
+<li>Code cleanup to avoid overwriting ctx before first use (fixes issue
+reported by the staticcheck linter) (albertony)</li>
 </ul></li>
 <li>Storj
 <ul>
-<li>Fix "uplink: too many requests" errors when uploading to the same file (Nick Craig-Wood)</li>
-<li>Fix uploading to the wrong object on Update with overridden remote name (Nick Craig-Wood)</li>
+<li>Fix "uplink: too many requests" errors when uploading to the same
+file (Nick Craig-Wood)</li>
+<li>Fix uploading to the wrong object on Update with overridden remote
+name (Nick Craig-Wood)</li>
 </ul></li>
 <li>Swift
 <ul>
@@ -38508,18 +54407,23 @@ $ tree /tmp/c
 </ul></li>
 <li>Uptobox
 <ul>
-<li>Add <code>--uptobox-private</code> flag to make all uploaded files private (Nick Craig-Wood)</li>
+<li>Add <code>--uptobox-private</code> flag to make all uploaded files
+private (Nick Craig-Wood)</li>
 <li>Fix improper regex (Aaron Gokaslan)</li>
 <li>Fix Update returning the wrong object (Nick Craig-Wood)</li>
-<li>Fix rmdir declaring that directories weren't empty (Nick Craig-Wood)</li>
+<li>Fix rmdir declaring that directories weren't empty (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
 <li>nextcloud: Add support for chunked uploads (Paul)</li>
-<li>Set modtime using propset for owncloud and nextcloud (WeidiDeng)</li>
-<li>Make pacer minSleep configurable with <code>--webdav-pacer-min-sleep</code> (ed)</li>
+<li>Set modtime using propset for owncloud and nextcloud
+(WeidiDeng)</li>
+<li>Make pacer minSleep configurable with
+<code>--webdav-pacer-min-sleep</code> (ed)</li>
 <li>Fix server side copy/move not overwriting (WeidiDeng)</li>
-<li>Fix modtime on server side copy for owncloud and nextcloud (Nick Craig-Wood)</li>
+<li>Fix modtime on server side copy for owncloud and nextcloud (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Yandex
 <ul>
@@ -38527,15 +54431,19 @@ $ tree /tmp/c
 </ul></li>
 <li>Zoho
 <ul>
-<li>Fix downloads with <code>Range:</code> header returning the wrong data (Nick Craig-Wood)</li>
+<li>Fix downloads with <code>Range:</code> header returning the wrong
+data (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.62.2---2023-03-16">v1.62.2 - 2023-03-16</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.62.1...v1.62.2">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.62.1...v1.62.2">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>docker volume plugin: Add missing fuse3 dependency (Nick Craig-Wood)</li>
+<li>docker volume plugin: Add missing fuse3 dependency (Nick
+Craig-Wood)</li>
 <li>docs: Fix size documentation (asdffdsazqqq)</li>
 </ul></li>
 <li>FTP
@@ -38544,21 +54452,28 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.62.1---2023-03-15">v1.62.1 - 2023-03-15</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.62.0...v1.62.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.62.0...v1.62.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
 <li>docker: Add missing fuse3 dependency (cycneuramus)</li>
-<li>build: Update release docs to be more careful with the tag (Nick Craig-Wood)</li>
-<li>build: Set Github release to draft while uploading binaries (Nick Craig-Wood)</li>
+<li>build: Update release docs to be more careful with the tag (Nick
+Craig-Wood)</li>
+<li>build: Set Github release to draft while uploading binaries (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.62.0---2023-03-14">v1.62.0 - 2023-03-14</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.61.0...v1.62.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.61.0...v1.62.0">See
+commits</a></p>
 <ul>
 <li>New Features
 <ul>
-<li>accounting: Make checkers show what they are doing (Nick Craig-Wood)</li>
+<li>accounting: Make checkers show what they are doing (Nick
+Craig-Wood)</li>
 <li>authorize: Add support for custom templates (Hunter Wittenborn)</li>
 <li>build
 <ul>
@@ -38566,16 +54481,23 @@ $ tree /tmp/c
 <li>Add winget releaser workflow (Ryan Caezar Itang)</li>
 <li>Add dependabot (Ryan Caezar Itang)</li>
 </ul></li>
-<li>doc updates (albertony, Bryan Kaplan, Gerard Bosch, IMTheNachoMan, Justin Winokur, Manoj Ghosh, Nick Craig-Wood, Ole Frost, Peter Brunner, piyushgarg, Ryan Caezar Itang, Simmon Li, ToBeFree)</li>
-<li>filter: Emit INFO message when can't work out directory filters (Nick Craig-Wood)</li>
+<li>doc updates (albertony, Bryan Kaplan, Gerard Bosch, IMTheNachoMan,
+Justin Winokur, Manoj Ghosh, Nick Craig-Wood, Ole Frost, Peter Brunner,
+piyushgarg, Ryan Caezar Itang, Simmon Li, ToBeFree)</li>
+<li>filter: Emit INFO message when can't work out directory filters
+(Nick Craig-Wood)</li>
 <li>fs
 <ul>
 <li>Added multiple ca certificate support. (alankrit)</li>
-<li>Add <code>--max-delete-size</code> a delete size threshold (Leandro Sacchet)</li>
+<li>Add <code>--max-delete-size</code> a delete size threshold (Leandro
+Sacchet)</li>
 </ul></li>
-<li>fspath: Allow the symbols <code>@</code> and <code>+</code> in remote names (albertony)</li>
-<li>lib/terminal: Enable windows console virtual terminal sequences processing (ANSI/VT100 colors) (albertony)</li>
-<li>move: If <code>--check-first</code> and <code>--order-by</code> are set then delete with perfect ordering (Nick Craig-Wood)</li>
+<li>fspath: Allow the symbols <code>@</code> and <code>+</code> in
+remote names (albertony)</li>
+<li>lib/terminal: Enable windows console virtual terminal sequences
+processing (ANSI/VT100 colors) (albertony)</li>
+<li>move: If <code>--check-first</code> and <code>--order-by</code> are
+set then delete with perfect ordering (Nick Craig-Wood)</li>
 <li>serve http: Support <code>--auth-proxy</code> (Matthias Baur)</li>
 </ul></li>
 <li>Bug Fixes
@@ -38584,7 +54506,8 @@ $ tree /tmp/c
 <ul>
 <li>Avoid negative ETA values for very slow speeds (albertony)</li>
 <li>Limit length of ETA string (albertony)</li>
-<li>Show human readable elapsed time when longer than a day (albertony)</li>
+<li>Show human readable elapsed time when longer than a day
+(albertony)</li>
 </ul></li>
 <li>all: Apply codeql fixes (Aaron Gokaslan)</li>
 <li>build
@@ -38597,49 +54520,66 @@ $ tree /tmp/c
 <li>version: Report ARM version</li>
 </ul></li>
 </ul></li>
-<li>deletefile: Return error code 4 if file does not exist (Nick Craig-Wood)</li>
-<li>docker: Fix volume plugin does not remount volume on docker restart (logopk)</li>
-<li>fs: Fix race conditions in <code>--max-delete</code> and <code>--max-delete-size</code> (Nick Craig-Wood)</li>
+<li>deletefile: Return error code 4 if file does not exist (Nick
+Craig-Wood)</li>
+<li>docker: Fix volume plugin does not remount volume on docker restart
+(logopk)</li>
+<li>fs: Fix race conditions in <code>--max-delete</code> and
+<code>--max-delete-size</code> (Nick Craig-Wood)</li>
 <li>lib/oauthutil: Handle fatal errors better (Alex Chen)</li>
 <li>mount2: Fix <code>--allow-non-empty</code> (Nick Craig-Wood)</li>
-<li>operations: Fix concurrency: use <code>--checkers</code> unless transferring files (Nick Craig-Wood)</li>
-<li>serve ftp: Fix timestamps older than 1 year in listings (Nick Craig-Wood)</li>
-<li>sync: Fix concurrency: use <code>--checkers</code> unless transferring files (Nick Craig-Wood)</li>
+<li>operations: Fix concurrency: use <code>--checkers</code> unless
+transferring files (Nick Craig-Wood)</li>
+<li>serve ftp: Fix timestamps older than 1 year in listings (Nick
+Craig-Wood)</li>
+<li>sync: Fix concurrency: use <code>--checkers</code> unless
+transferring files (Nick Craig-Wood)</li>
 <li>tree
 <ul>
 <li>Fix nil pointer exception on stat failure (Nick Craig-Wood)</li>
 <li>Fix colored output on windows (albertony)</li>
-<li>Fix display of files with illegal Windows file system names (Nick Craig-Wood)</li>
+<li>Fix display of files with illegal Windows file system names (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Fix creating and renaming files on case insensitive backends (Nick Craig-Wood)</li>
-<li>Do not treat <code>\\?\</code> prefixed paths as network share paths on windows (albertony)</li>
+<li>Fix creating and renaming files on case insensitive backends (Nick
+Craig-Wood)</li>
+<li>Do not treat <code>\\?\</code> prefixed paths as network share paths
+on windows (albertony)</li>
 <li>Fix check for empty mount point on Linux (Nick Craig-Wood)</li>
 <li>Fix <code>--allow-non-empty</code> (Nick Craig-Wood)</li>
-<li>Avoid incorrect or premature overlap check on windows (albertony)</li>
+<li>Avoid incorrect or premature overlap check on windows
+(albertony)</li>
 <li>Update to fuse3 after bazil.org/fuse update (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Make uploaded files retain modtime with non-modtime backends (Nick Craig-Wood)</li>
-<li>Fix incorrect modtime on fs which don't support setting modtime (Nick Craig-Wood)</li>
-<li>Fix rename of directory containing files to be uploaded (Nick Craig-Wood)</li>
+<li>Make uploaded files retain modtime with non-modtime backends (Nick
+Craig-Wood)</li>
+<li>Fix incorrect modtime on fs which don't support setting modtime
+(Nick Craig-Wood)</li>
+<li>Fix rename of directory containing files to be uploaded (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix <code>%!w(&lt;nil&gt;)</code> in "failed to read directory" error (Marks Polakovs)</li>
-<li>Fix exclusion of dangling symlinks with -L/--copy-links (Nick Craig-Wood)</li>
+<li>Fix <code>%!w(&lt;nil&gt;)</code> in "failed to read directory"
+error (Marks Polakovs)</li>
+<li>Fix exclusion of dangling symlinks with -L/--copy-links (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
 <li>Obey <code>--ignore-checksum</code> (Nick Craig-Wood)</li>
-<li>Fix for unencrypted directory names on case insensitive remotes (Ole Frost)</li>
+<li>Fix for unencrypted directory names on case insensitive remotes (Ole
+Frost)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Remove workarounds for SDK bugs after v0.6.1 update (Nick Craig-Wood)</li>
+<li>Remove workarounds for SDK bugs after v0.6.1 update (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
@@ -38647,18 +54587,22 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Note that <code>--drive-acknowledge-abuse</code> needs SA Manager permission (Nick Craig-Wood)</li>
-<li>Make <code>--drive-stop-on-upload-limit</code> to respond to storageQuotaExceeded (Ninh Pham)</li>
+<li>Note that <code>--drive-acknowledge-abuse</code> needs SA Manager
+permission (Nick Craig-Wood)</li>
+<li>Make <code>--drive-stop-on-upload-limit</code> to respond to
+storageQuotaExceeded (Ninh Pham)</li>
 </ul></li>
 <li>FTP
 <ul>
 <li>Retry 426 errors (Nick Craig-Wood)</li>
 <li>Retry errors when initiating downloads (Nick Craig-Wood)</li>
-<li>Revert to upstream <code>github.com/jlaffaye/ftp</code> now fix is merged (Nick Craig-Wood)</li>
+<li>Revert to upstream <code>github.com/jlaffaye/ftp</code> now fix is
+merged (Nick Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Add <code>--gcs-env-auth</code> to pick up IAM credentials from env/instance (Peter Brunner)</li>
+<li>Add <code>--gcs-env-auth</code> to pick up IAM credentials from
+env/instance (Peter Brunner)</li>
 </ul></li>
 <li>Mega
 <ul>
@@ -38666,22 +54610,30 @@ $ tree /tmp/c
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Default onedrive personal to QuickXorHash as Microsoft is removing SHA1 (Nick Craig-Wood)</li>
-<li>Add <code>--onedrive-hash-type</code> to change the hash in use (Nick Craig-Wood)</li>
+<li>Default onedrive personal to QuickXorHash as Microsoft is removing
+SHA1 (Nick Craig-Wood)</li>
+<li>Add <code>--onedrive-hash-type</code> to change the hash in use
+(Nick Craig-Wood)</li>
 <li>Improve speed of QuickXorHash (LXY)</li>
 </ul></li>
 <li>Oracle Object Storage
 <ul>
-<li>Speed up operations by using S3 pacer and setting minsleep to 10ms (Manoj Ghosh)</li>
-<li>Expose the <code>storage_tier</code> option in config (Manoj Ghosh)</li>
+<li>Speed up operations by using S3 pacer and setting minsleep to 10ms
+(Manoj Ghosh)</li>
+<li>Expose the <code>storage_tier</code> option in config (Manoj
+Ghosh)</li>
 <li>Bring your own encryption keys (Manoj Ghosh)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Check multipart upload ETag when <code>--s3-no-head</code> is in use (Nick Craig-Wood)</li>
-<li>Add <code>--s3-sts-endpoint</code> to specify STS endpoint (Nick Craig-Wood)</li>
-<li>Fix incorrect tier support for StorJ and IDrive when pointing at a file (Ole Frost)</li>
-<li>Fix AWS STS failing if <code>--s3-endpoint</code> is set (Nick Craig-Wood)</li>
+<li>Check multipart upload ETag when <code>--s3-no-head</code> is in use
+(Nick Craig-Wood)</li>
+<li>Add <code>--s3-sts-endpoint</code> to specify STS endpoint (Nick
+Craig-Wood)</li>
+<li>Fix incorrect tier support for StorJ and IDrive when pointing at a
+file (Ole Frost)</li>
+<li>Fix AWS STS failing if <code>--s3-endpoint</code> is set (Nick
+Craig-Wood)</li>
 <li>Make purge remove directory markers too (Nick Craig-Wood)</li>
 </ul></li>
 <li>Seafile
@@ -38690,11 +54642,13 @@ $ tree /tmp/c
 </ul></li>
 <li>SFTP
 <ul>
-<li>Fix uploads being 65% slower than they should be with crypt (Nick Craig-Wood)</li>
+<li>Fix uploads being 65% slower than they should be with crypt (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Smb
 <ul>
-<li>Allow SPN (service principal name) to be configured (Nick Craig-Wood)</li>
+<li>Allow SPN (service principal name) to be configured (Nick
+Craig-Wood)</li>
 <li>Check smb connection is closed (happyxhw)</li>
 </ul></li>
 <li>Storj
@@ -38709,31 +54663,39 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.61.1---2022-12-23">v1.61.1 - 2022-12-23</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.61.0...v1.61.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.61.0...v1.61.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
 <li>docs:
 <ul>
-<li>Show only significant parts of version number in version introduced label (albertony)</li>
+<li>Show only significant parts of version number in version introduced
+label (albertony)</li>
 <li>Fix unescaped HTML (Nick Craig-Wood)</li>
 </ul></li>
-<li>lib/http: Shutdown all servers on exit to remove unix socket (Nick Craig-Wood)</li>
-<li>rc: Fix <code>--rc-addr</code> flag (which is an alternate for <code>--url</code>) (Anagh Kumar Baranwal)</li>
+<li>lib/http: Shutdown all servers on exit to remove unix socket (Nick
+Craig-Wood)</li>
+<li>rc: Fix <code>--rc-addr</code> flag (which is an alternate for
+<code>--url</code>) (Anagh Kumar Baranwal)</li>
 <li>serve restic
 <ul>
-<li>Don't serve via http if serving via <code>--stdio</code> (Nick Craig-Wood)</li>
+<li>Don't serve via http if serving via <code>--stdio</code> (Nick
+Craig-Wood)</li>
 <li>Fix immediate exit when not using stdio (Nick Craig-Wood)</li>
 </ul></li>
 <li>serve webdav
 <ul>
-<li>Fix <code>--baseurl</code> handling after <code>lib/http</code> refactor (Nick Craig-Wood)</li>
+<li>Fix <code>--baseurl</code> handling after <code>lib/http</code>
+refactor (Nick Craig-Wood)</li>
 <li>Fix running duplicate Serve call (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Fix "409 Public access is not permitted on this storage account" (Nick Craig-Wood)</li>
+<li>Fix "409 Public access is not permitted on this storage account"
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
@@ -38741,91 +54703,133 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.61.0---2022-12-20">v1.61.0 - 2022-12-20</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.60.0...v1.61.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.60.0...v1.61.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
 <li>New S3 providers
 <ul>
-<li><a href="https://rclone.org/s3/#liara-cloud">Liara LOS</a> (MohammadReza)</li>
+<li><a href="https://rclone.org/s3/#liara-cloud">Liara LOS</a>
+(MohammadReza)</li>
 </ul></li>
 </ul></li>
 <li>New Features
 <ul>
 <li>build: Add vulnerability testing using govulncheck (albertony)</li>
-<li>cmd: Enable <code>SIGINFO</code> (Ctrl-T) handler on FreeBSD, NetBSD, OpenBSD and Dragonfly BSD (x3-apptech)</li>
-<li>config: Add <a href="https://rclone.org/rc/#config-setpath">config/setpath</a> for setting config path via rc/librclone (Nick Craig-Wood)</li>
+<li>cmd: Enable <code>SIGINFO</code> (Ctrl-T) handler on FreeBSD,
+NetBSD, OpenBSD and Dragonfly BSD (x3-apptech)</li>
+<li>config: Add <a
+href="https://rclone.org/rc/#config-setpath">config/setpath</a> for
+setting config path via rc/librclone (Nick Craig-Wood)</li>
 <li>dedupe
 <ul>
-<li>Count Checks in the stats while scanning for duplicates (Nick Craig-Wood)</li>
+<li>Count Checks in the stats while scanning for duplicates (Nick
+Craig-Wood)</li>
 <li>Make dedupe obey the filters (Nick Craig-Wood)</li>
 </ul></li>
-<li>dlna: Properly attribute code used from https://github.com/anacrolix/dms (Nick Craig-Wood)</li>
+<li>dlna: Properly attribute code used from
+https://github.com/anacrolix/dms (Nick Craig-Wood)</li>
 <li>docs
 <ul>
-<li>Add minimum versions and status badges to backend and command docs (Nick Craig-Wood, albertony)</li>
+<li>Add minimum versions and status badges to backend and command docs
+(Nick Craig-Wood, albertony)</li>
 <li>Remote names may not start or end with space (albertony)</li>
 </ul></li>
-<li>filter: Add metadata filters <a href="https://rclone.org/filtering/#metadata">--metadata-include/exclude/filter</a> and friends (Nick Craig-Wood)</li>
+<li>filter: Add metadata filters <a
+href="https://rclone.org/filtering/#metadata">--metadata-include/exclude/filter</a>
+and friends (Nick Craig-Wood)</li>
 <li>fs
 <ul>
-<li>Make all duration flags take <code>y</code>, <code>M</code>, <code>w</code>, <code>d</code> etc suffixes (Nick Craig-Wood)</li>
-<li>Add global flag <code>--color</code> to control terminal colors (Kevin Verstaen)</li>
+<li>Make all duration flags take <code>y</code>, <code>M</code>,
+<code>w</code>, <code>d</code> etc suffixes (Nick Craig-Wood)</li>
+<li>Add global flag <code>--color</code> to control terminal colors
+(Kevin Verstaen)</li>
 </ul></li>
-<li>fspath: Allow unicode numbers and letters in remote names (albertony)</li>
-<li>lib/file: Improve error message for creating dir on non-existent network host on windows (albertony)</li>
-<li>lib/http: Finish port of rclone servers to <code>lib/http</code> (Tom Mombourquette, Nick Craig-Wood)</li>
-<li>lib/oauthutil: Improved usability of config flows needing web browser (Ole Frost)</li>
+<li>fspath: Allow unicode numbers and letters in remote names
+(albertony)</li>
+<li>lib/file: Improve error message for creating dir on non-existent
+network host on windows (albertony)</li>
+<li>lib/http: Finish port of rclone servers to <code>lib/http</code>
+(Tom Mombourquette, Nick Craig-Wood)</li>
+<li>lib/oauthutil: Improved usability of config flows needing web
+browser (Ole Frost)</li>
 <li>ncdu
 <ul>
 <li>Add support for modification time (albertony)</li>
-<li>Fallback to sort by name also for sort by average size (albertony)</li>
-<li>Rework to use tcell directly instead of the termbox wrapper (eNV25)</li>
+<li>Fallback to sort by name also for sort by average size
+(albertony)</li>
+<li>Rework to use tcell directly instead of the termbox wrapper
+(eNV25)</li>
 </ul></li>
-<li>rc: Add commands to set <a href="https://rclone.org/rc/#debug-set-gc-percent">GC Percent</a> &amp; <a href="/rc/#debug-set-soft-memory-limit">Memory Limit</a> (go 1.19+) (Anagh Kumar Baranwal)</li>
-<li>rcat: Preserve metadata when Copy falls back to Rcat (Nick Craig-Wood)</li>
-<li>rcd: Refactor rclone rc server to use <code>lib/http</code> (Nick Craig-Wood)</li>
-<li>rcserver: Avoid generating default credentials with htpasswd (Kamui)</li>
+<li>rc: Add commands to set <a
+href="https://rclone.org/rc/#debug-set-gc-percent">GC Percent</a> &amp;
+<a href="/rc/#debug-set-soft-memory-limit">Memory Limit</a> (go 1.19+)
+(Anagh Kumar Baranwal)</li>
+<li>rcat: Preserve metadata when Copy falls back to Rcat (Nick
+Craig-Wood)</li>
+<li>rcd: Refactor rclone rc server to use <code>lib/http</code> (Nick
+Craig-Wood)</li>
+<li>rcserver: Avoid generating default credentials with htpasswd
+(Kamui)</li>
 <li>restic: Refactor to use <code>lib/http</code> (Nolan Woods)</li>
-<li>serve http: Support unix sockets and multiple listeners (Tom Mombourquette)</li>
-<li>serve webdav: Refactor to use <code>lib/http</code> (Nick Craig-Wood)</li>
-<li>test: Replace defer cleanup with <code>t.Cleanup</code> (Eng Zer Jun)</li>
-<li>test memory: Read metadata if <code>-M</code> flag is specified (Nick Craig-Wood)</li>
-<li>wasm: Comply with <code>wasm_exec.js</code> licence terms (Matthew Vernon)</li>
+<li>serve http: Support unix sockets and multiple listeners (Tom
+Mombourquette)</li>
+<li>serve webdav: Refactor to use <code>lib/http</code> (Nick
+Craig-Wood)</li>
+<li>test: Replace defer cleanup with <code>t.Cleanup</code> (Eng Zer
+Jun)</li>
+<li>test memory: Read metadata if <code>-M</code> flag is specified
+(Nick Craig-Wood)</li>
+<li>wasm: Comply with <code>wasm_exec.js</code> licence terms (Matthew
+Vernon)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>build: Update <code>golang.org/x/net/http2</code> to fix GO-2022-1144 (Nick Craig-Wood)</li>
-<li>restic: Fix typo in docs 'remove' should be 'remote' (asdffdsazqqq)</li>
+<li>build: Update <code>golang.org/x/net/http2</code> to fix
+GO-2022-1144 (Nick Craig-Wood)</li>
+<li>restic: Fix typo in docs 'remove' should be 'remote'
+(asdffdsazqqq)</li>
 <li>serve dlna: Fix panic: Logger uninitialized. (Nick Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Update cgofuse for FUSE-T support for mounting volumes on Mac (Nick Craig-Wood)</li>
+<li>Update cgofuse for FUSE-T support for mounting volumes on Mac (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Windows: fix slow opening of exe files by not truncating files when not necessary (Nick Craig-Wood)</li>
-<li>Fix IO Error opening a file with <code>O_CREATE|O_RDONLY</code> in <code>--vfs-cache-mode</code> not full (Nick Craig-Wood)</li>
+<li>Windows: fix slow opening of exe files by not truncating files when
+not necessary (Nick Craig-Wood)</li>
+<li>Fix IO Error opening a file with <code>O_CREATE|O_RDONLY</code> in
+<code>--vfs-cache-mode</code> not full (Nick Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Fix compress wrapping crypt giving upload errors (Nick Craig-Wood)</li>
+<li>Fix compress wrapping crypt giving upload errors (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
 <li>Port to new SDK (Nick Craig-Wood)
 <ul>
-<li>Revamp authentication to include all methods and docs (Nick Craig-Wood)</li>
-<li>Port old authentication methods to new SDK (Nick Craig-Wood, Brad Ackerman)</li>
-<li>Thanks to <a href="https://www.stonebranch.com/">Stonebranch</a> for sponsoring this work.</li>
+<li>Revamp authentication to include all methods and docs (Nick
+Craig-Wood)</li>
+<li>Port old authentication methods to new SDK (Nick Craig-Wood, Brad
+Ackerman)</li>
+<li>Thanks to <a href="https://www.stonebranch.com/">Stonebranch</a> for
+sponsoring this work.</li>
 </ul></li>
-<li>Add <code>--azureblob-no-check-container</code> to assume container exists (Nick Craig-Wood)</li>
+<li>Add <code>--azureblob-no-check-container</code> to assume container
+exists (Nick Craig-Wood)</li>
 <li>Add <code>--use-server-modtime</code> support (Abdullah Saglam)</li>
 <li>Add support for custom upload headers (rkettelerij)</li>
 <li>Allow emulator account/key override (Roel Arents)</li>
-<li>Support simple "environment credentials" (Nathaniel Wesley Filardo)</li>
-<li>Ignore <code>AuthorizationFailure</code> when trying to create a create a container (Nick Craig-Wood)</li>
+<li>Support simple "environment credentials" (Nathaniel Wesley
+Filardo)</li>
+<li>Ignore <code>AuthorizationFailure</code> when trying to create a
+create a container (Nick Craig-Wood)</li>
 </ul></li>
 <li>Box
 <ul>
@@ -38833,17 +54837,21 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Handle shared drives with leading/trailing space in name (related to) (albertony)</li>
+<li>Handle shared drives with leading/trailing space in name (related
+to) (albertony)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Update help text of implicit/explicit TLS options to refer to FTPS instead of FTP (ycdtosa)</li>
-<li>Improve performance to speed up <code>--files-from</code> and <code>NewObject</code> (Anthony Pessy)</li>
+<li>Update help text of implicit/explicit TLS options to refer to FTPS
+instead of FTP (ycdtosa)</li>
+<li>Improve performance to speed up <code>--files-from</code> and
+<code>NewObject</code> (Anthony Pessy)</li>
 </ul></li>
 <li>HTTP
 <ul>
 <li>Parse GET responses when <code>no_head</code> is set (Arnie97)</li>
-<li>Do not update object size based on <code>Range</code> requests (Arnie97)</li>
+<li>Do not update object size based on <code>Range</code> requests
+(Arnie97)</li>
 <li>Support <code>Content-Range</code> response header (Arnie97)</li>
 </ul></li>
 <li>Onedrive
@@ -38853,19 +54861,27 @@ $ tree /tmp/c
 <li>S3
 <ul>
 <li>Add Liara LOS to provider list (MohammadReza)</li>
-<li>Add DigitalOcean Spaces regions <code>sfo3</code>, <code>fra1</code>, <code>syd1</code> (Jack)</li>
-<li>Avoid privileged <code>GetBucketLocation</code> to resolve s3 region (Anthony Pessy)</li>
-<li>Stop setting object and bucket ACL to <code>private</code> if it is an empty string (Philip Harvey)</li>
-<li>If bucket or object ACL is empty string then don't add <code>X-Amz-Acl:</code> header (Nick Craig-Wood)</li>
+<li>Add DigitalOcean Spaces regions <code>sfo3</code>,
+<code>fra1</code>, <code>syd1</code> (Jack)</li>
+<li>Avoid privileged <code>GetBucketLocation</code> to resolve s3 region
+(Anthony Pessy)</li>
+<li>Stop setting object and bucket ACL to <code>private</code> if it is
+an empty string (Philip Harvey)</li>
+<li>If bucket or object ACL is empty string then don't add
+<code>X-Amz-Acl:</code> header (Nick Craig-Wood)</li>
 <li>Reduce memory consumption for s3 objects (Erik Agterdenbos)</li>
-<li>Fix listing loop when using v2 listing on v1 server (Nick Craig-Wood)</li>
+<li>Fix listing loop when using v2 listing on v1 server (Nick
+Craig-Wood)</li>
 <li>Fix nil pointer exception when using Versions (Nick Craig-Wood)</li>
 <li>Fix excess memory usage when using versions (Nick Craig-Wood)</li>
-<li>Ignore versionIDs from uploads unless using <code>--s3-versions</code> or <code>--s3-versions-at</code> (Nick Craig-Wood)</li>
+<li>Ignore versionIDs from uploads unless using
+<code>--s3-versions</code> or <code>--s3-versions-at</code> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Add configuration options to set ssh Ciphers / MACs / KeyExchange (dgouju)</li>
+<li>Add configuration options to set ssh Ciphers / MACs / KeyExchange
+(dgouju)</li>
 <li>Auto-detect shell type for fish (albertony)</li>
 <li>Fix NewObject with leading / (Nick Craig-Wood)</li>
 </ul></li>
@@ -38879,136 +54895,184 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.60.1---2022-11-17">v1.60.1 - 2022-11-17</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.60.0...v1.60.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.60.0...v1.60.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>lib/cache: Fix alias backend shutting down too soon (Nick Craig-Wood)</li>
-<li>wasm: Fix walltime link error by adding up-to-date wasm_exec.js (João Henrique Franco)</li>
+<li>lib/cache: Fix alias backend shutting down too soon (Nick
+Craig-Wood)</li>
+<li>wasm: Fix walltime link error by adding up-to-date wasm_exec.js
+(João Henrique Franco)</li>
 <li>docs
 <ul>
 <li>Update faq.md with bisync (Samuel Johnson)</li>
 <li>Corrected download links in windows install docs (coultonluke)</li>
 <li>Add direct download link for windows arm64 (albertony)</li>
-<li>Remove link to rclone slack as it is no longer supported (Nick Craig-Wood)</li>
-<li>Faq: how to use a proxy server that requires a username and password (asdffdsazqqq)</li>
+<li>Remove link to rclone slack as it is no longer supported (Nick
+Craig-Wood)</li>
+<li>Faq: how to use a proxy server that requires a username and password
+(asdffdsazqqq)</li>
 <li>Oracle-object-storage: doc fix (Manoj Ghosh)</li>
-<li>Fix typo <code>remove</code> in rclone_serve_restic command (Joda Stößer)</li>
-<li>Fix character that was incorrectly interpreted as markdown (Clément Notin)</li>
+<li>Fix typo <code>remove</code> in rclone_serve_restic command (Joda
+Stößer)</li>
+<li>Fix character that was incorrectly interpreted as markdown (Clément
+Notin)</li>
 </ul></li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Fix deadlock caused by cache cleaner and upload finishing (Nick Craig-Wood)</li>
+<li>Fix deadlock caused by cache cleaner and upload finishing (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
 <li>Clean absolute paths (albertony)</li>
-<li>Fix -L/--copy-links with filters missing directories (Nick Craig-Wood)</li>
+<li>Fix -L/--copy-links with filters missing directories (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Mailru
 <ul>
 <li>Note that an app password is now needed (Nick Craig-Wood)</li>
-<li>Allow timestamps to be before the epoch 1970-01-01 (Nick Craig-Wood)</li>
+<li>Allow timestamps to be before the epoch 1970-01-01 (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Add provider quirk <code>--s3-might-gzip</code> to fix corrupted on transfer: sizes differ (Nick Craig-Wood)</li>
-<li>Allow Storj to server side copy since it seems to work now (Nick Craig-Wood)</li>
+<li>Add provider quirk <code>--s3-might-gzip</code> to fix corrupted on
+transfer: sizes differ (Nick Craig-Wood)</li>
+<li>Allow Storj to server side copy since it seems to work now (Nick
+Craig-Wood)</li>
 <li>Fix for unchecked err value in s3 listv2 (Aaron Gokaslan)</li>
 <li>Add additional Wasabi locations (techknowlogick)</li>
 </ul></li>
 <li>Smb
 <ul>
-<li>Fix <code>Failed to sync: context canceled</code> at the end of syncs (Nick Craig-Wood)</li>
+<li>Fix <code>Failed to sync: context canceled</code> at the end of
+syncs (Nick Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Fix Move/Copy/DirMove when using -server-side-across-configs (Nick Craig-Wood)</li>
+<li>Fix Move/Copy/DirMove when using -server-side-across-configs (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.60.0---2022-10-21">v1.60.0 - 2022-10-21</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.59.0...v1.60.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.59.0...v1.60.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
-<li><a href="https://rclone.org/oracleobjectstorage/">Oracle object storage</a> (Manoj Ghosh)</li>
-<li><a href="https://rclone.org/smb/">SMB</a> / CIFS (Windows file sharing) (Lesmiscore)</li>
+<li><a href="https://rclone.org/oracleobjectstorage/">Oracle object
+storage</a> (Manoj Ghosh)</li>
+<li><a href="https://rclone.org/smb/">SMB</a> / CIFS (Windows file
+sharing) (Lesmiscore)</li>
 <li>New S3 providers
 <ul>
-<li><a href="https://rclone.org/s3/#ionos">IONOS Cloud Storage</a> (Dmitry Deniskin)</li>
-<li><a href="https://rclone.org/s3/#qiniu">Qiniu KODO</a> (Bachue Zhou)</li>
+<li><a href="https://rclone.org/s3/#ionos">IONOS Cloud Storage</a>
+(Dmitry Deniskin)</li>
+<li><a href="https://rclone.org/s3/#qiniu">Qiniu KODO</a> (Bachue
+Zhou)</li>
 </ul></li>
 </ul></li>
 <li>New Features
 <ul>
 <li>build
 <ul>
-<li>Update to go1.19 and make go1.17 the minimum required version (Nick Craig-Wood)</li>
+<li>Update to go1.19 and make go1.17 the minimum required version (Nick
+Craig-Wood)</li>
 <li>Install.sh: fix arm-v7 download (Ole Frost)</li>
 </ul></li>
-<li>fs: Warn the user when using an existing remote name without a colon (Nick Craig-Wood)</li>
-<li>httplib: Add <code>--xxx-min-tls-version</code> option to select minimum TLS version for HTTP servers (Robert Newson)</li>
-<li>librclone: Add PHP bindings and test program (Jordi Gonzalez Muñoz)</li>
+<li>fs: Warn the user when using an existing remote name without a colon
+(Nick Craig-Wood)</li>
+<li>httplib: Add <code>--xxx-min-tls-version</code> option to select
+minimum TLS version for HTTP servers (Robert Newson)</li>
+<li>librclone: Add PHP bindings and test program (Jordi Gonzalez
+Muñoz)</li>
 <li>operations
 <ul>
-<li>Add <code>--server-side-across-configs</code> global flag for any backend (Nick Craig-Wood)</li>
-<li>Optimise <code>--copy-dest</code> and <code>--compare-dest</code> (Nick Craig-Wood)</li>
+<li>Add <code>--server-side-across-configs</code> global flag for any
+backend (Nick Craig-Wood)</li>
+<li>Optimise <code>--copy-dest</code> and <code>--compare-dest</code>
+(Nick Craig-Wood)</li>
 </ul></li>
-<li>rc: add <code>job/stopgroup</code> to stop group (Evan Spensley)</li>
+<li>rc: add <code>job/stopgroup</code> to stop group (Evan
+Spensley)</li>
 <li>serve dlna
 <ul>
-<li>Add <code>--announce-interval</code> to control SSDP Announce Interval (YanceyChiew)</li>
-<li>Add <code>--interface</code> to Specify SSDP interface names line (Simon Bos)</li>
+<li>Add <code>--announce-interval</code> to control SSDP Announce
+Interval (YanceyChiew)</li>
+<li>Add <code>--interface</code> to Specify SSDP interface names line
+(Simon Bos)</li>
 <li>Add support for more external subtitles (YanceyChiew)</li>
 <li>Add verification of addresses (YanceyChiew)</li>
 </ul></li>
-<li>sync: Optimise <code>--copy-dest</code> and <code>--compare-dest</code> (Nick Craig-Wood)</li>
-<li>doc updates (albertony, Alexander Knorr, anonion, João Henrique Franco, Josh Soref, Lorenzo Milesi, Marco Molteni, Mark Trolley, Ole Frost, partev, Ryan Morey, Tom Mombourquette, YFdyh000)</li>
+<li>sync: Optimise <code>--copy-dest</code> and
+<code>--compare-dest</code> (Nick Craig-Wood)</li>
+<li>doc updates (albertony, Alexander Knorr, anonion, João Henrique
+Franco, Josh Soref, Lorenzo Milesi, Marco Molteni, Mark Trolley, Ole
+Frost, partev, Ryan Morey, Tom Mombourquette, YFdyh000)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>filter
 <ul>
-<li>Fix incorrect filtering with <code>UseFilter</code> context flag and wrapping backends (Nick Craig-Wood)</li>
-<li>Make sure we check <code>--files-from</code> when looking for a single file (Nick Craig-Wood)</li>
+<li>Fix incorrect filtering with <code>UseFilter</code> context flag and
+wrapping backends (Nick Craig-Wood)</li>
+<li>Make sure we check <code>--files-from</code> when looking for a
+single file (Nick Craig-Wood)</li>
 </ul></li>
 <li>rc
 <ul>
-<li>Fix <code>mount/listmounts</code> not returning the full Fs entered in <code>mount/mount</code> (Tom Mombourquette)</li>
+<li>Fix <code>mount/listmounts</code> not returning the full Fs entered
+in <code>mount/mount</code> (Tom Mombourquette)</li>
 <li>Handle external unmount when mounting (Isaac Aymerich)</li>
-<li>Validate Daemon option is not set when mounting a volume via RC (Isaac Aymerich)</li>
+<li>Validate Daemon option is not set when mounting a volume via RC
+(Isaac Aymerich)</li>
 </ul></li>
-<li>sync: Update docs and error messages to reflect fixes to overlap checks (Nick Naumann)</li>
+<li>sync: Update docs and error messages to reflect fixes to overlap
+checks (Nick Naumann)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Reduce memory use by embedding <code>sync.Cond</code> (Nick Craig-Wood)</li>
-<li>Reduce memory usage by re-ordering commonly used structures (Nick Craig-Wood)</li>
-<li>Fix excess CPU used by VFS cache cleaner looping (Nick Craig-Wood)</li>
+<li>Reduce memory use by embedding <code>sync.Cond</code> (Nick
+Craig-Wood)</li>
+<li>Reduce memory usage by re-ordering commonly used structures (Nick
+Craig-Wood)</li>
+<li>Fix excess CPU used by VFS cache cleaner looping (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Obey file filters in listing to fix errors on excluded files (Nick Craig-Wood)</li>
-<li>Fix "Failed to read metadata: function not implemented" on old Linux kernels (Nick Craig-Wood)</li>
+<li>Obey file filters in listing to fix errors on excluded files (Nick
+Craig-Wood)</li>
+<li>Fix "Failed to read metadata: function not implemented" on old Linux
+kernels (Nick Craig-Wood)</li>
 </ul></li>
 <li>Compress
 <ul>
 <li>Fix crash due to nil metadata (Nick Craig-Wood)</li>
-<li>Fix error handling to not use or return nil objects (Nick Craig-Wood)</li>
+<li>Fix error handling to not use or return nil objects (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Make <code>--drive-stop-on-upload-limit</code> obey quota exceeded error (Steve Kowalik)</li>
+<li>Make <code>--drive-stop-on-upload-limit</code> obey quota exceeded
+error (Steve Kowalik)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Add <code>--ftp-force-list-hidden</code> option to show hidden items (Øyvind Heddeland Instefjord)</li>
-<li>Fix hang when using ExplicitTLS to certain servers. (Nick Craig-Wood)</li>
+<li>Add <code>--ftp-force-list-hidden</code> option to show hidden items
+(Øyvind Heddeland Instefjord)</li>
+<li>Fix hang when using ExplicitTLS to certain servers. (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Add <code>--gcs-endpoint</code> flag and config parameter (Nick Craig-Wood)</li>
+<li>Add <code>--gcs-endpoint</code> flag and config parameter (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Hubic
 <ul>
@@ -39017,19 +55081,29 @@ $ tree /tmp/c
 <li>Onedrive
 <ul>
 <li>Rename Onedrive(cn) 21Vianet to Vnet Group (Yen Hu)</li>
-<li>Disable change notify in China region since it is not supported (Nick Craig-Wood)</li>
+<li>Disable change notify in China region since it is not supported
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Implement <code>--s3-versions</code> flag to show old versions of objects if enabled (Nick Craig-Wood)</li>
-<li>Implement <code>--s3-version-at</code> flag to show versions of objects at a particular time (Nick Craig-Wood)</li>
-<li>Implement <code>backend versioning</code> command to get/set bucket versioning (Nick Craig-Wood)</li>
-<li>Implement <code>Purge</code> to purge versions and <code>backend cleanup-hidden</code> (Nick Craig-Wood)</li>
-<li>Add <code>--s3-decompress</code> flag to decompress gzip-encoded files (Nick Craig-Wood)</li>
-<li>Add <code>--s3-sse-customer-key-base64</code> to supply keys with binary data (Richard Bateman)</li>
-<li>Try to keep the maximum precision in ModTime with <code>--user-server-modtime</code> (Nick Craig-Wood)</li>
-<li>Drop binary metadata with an ERROR message as it can't be stored (Nick Craig-Wood)</li>
-<li>Add <code>--s3-no-system-metadata</code> to suppress read and write of system metadata (Nick Craig-Wood)</li>
+<li>Implement <code>--s3-versions</code> flag to show old versions of
+objects if enabled (Nick Craig-Wood)</li>
+<li>Implement <code>--s3-version-at</code> flag to show versions of
+objects at a particular time (Nick Craig-Wood)</li>
+<li>Implement <code>backend versioning</code> command to get/set bucket
+versioning (Nick Craig-Wood)</li>
+<li>Implement <code>Purge</code> to purge versions and
+<code>backend cleanup-hidden</code> (Nick Craig-Wood)</li>
+<li>Add <code>--s3-decompress</code> flag to decompress gzip-encoded
+files (Nick Craig-Wood)</li>
+<li>Add <code>--s3-sse-customer-key-base64</code> to supply keys with
+binary data (Richard Bateman)</li>
+<li>Try to keep the maximum precision in ModTime with
+<code>--user-server-modtime</code> (Nick Craig-Wood)</li>
+<li>Drop binary metadata with an ERROR message as it can't be stored
+(Nick Craig-Wood)</li>
+<li>Add <code>--s3-no-system-metadata</code> to suppress read and write
+of system metadata (Nick Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
@@ -39037,189 +55111,269 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Add <code>--swift-no-large-objects</code> to reduce HEAD requests (Nick Craig-Wood)</li>
+<li>Add <code>--swift-no-large-objects</code> to reduce HEAD requests
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Union
 <ul>
-<li>Propagate SlowHash feature to fix hasher interaction (Lesmiscore)</li>
+<li>Propagate SlowHash feature to fix hasher interaction
+(Lesmiscore)</li>
 </ul></li>
 </ul>
 <h2 id="v1.59.2---2022-09-15">v1.59.2 - 2022-09-15</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.59.1...v1.59.2">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.59.1...v1.59.2">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>config: Move locking to fix fatal error: concurrent map read and map write (Nick Craig-Wood)</li>
+<li>config: Move locking to fix fatal error: concurrent map read and map
+write (Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Disable xattr support if the filesystems indicates it is not supported (Nick Craig-Wood)</li>
+<li>Disable xattr support if the filesystems indicates it is not
+supported (Nick Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Fix chunksize calculations producing too many parts (Nick Craig-Wood)</li>
+<li>Fix chunksize calculations producing too many parts (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
-<li>Fix chunksize calculations producing too many parts (Nick Craig-Wood)</li>
+<li>Fix chunksize calculations producing too many parts (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Fix chunksize calculations producing too many parts (Nick Craig-Wood)</li>
+<li>Fix chunksize calculations producing too many parts (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.59.1---2022-08-08">v1.59.1 - 2022-08-08</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.59.0...v1.59.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.59.0...v1.59.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>accounting: Fix panic in core/stats-reset with unknown group (Nick Craig-Wood)</li>
-<li>build: Fix android build after GitHub actions change (Nick Craig-Wood)</li>
+<li>accounting: Fix panic in core/stats-reset with unknown group (Nick
+Craig-Wood)</li>
+<li>build: Fix android build after GitHub actions change (Nick
+Craig-Wood)</li>
 <li>dlna: Fix SOAP action header parsing (Joram Schrijver)</li>
 <li>docs: Fix links to mount command from install docs (albertony)</li>
-<li>dropbox: Fix ChangeNotify was unable to decrypt errors (Nick Craig-Wood)</li>
-<li>fs: Fix parsing of times and durations of the form "YYYY-MM-DD HH:MM:SS" (Nick Craig-Wood)</li>
+<li>dropbox: Fix ChangeNotify was unable to decrypt errors (Nick
+Craig-Wood)</li>
+<li>fs: Fix parsing of times and durations of the form "YYYY-MM-DD
+HH:MM:SS" (Nick Craig-Wood)</li>
 <li>serve sftp: Fix checksum detection (Nick Craig-Wood)</li>
-<li>sync: Add accidentally missed filter-sensitivity to --backup-dir option (Nick Naumann)</li>
+<li>sync: Add accidentally missed filter-sensitivity to --backup-dir
+option (Nick Naumann)</li>
 </ul></li>
 <li>Combine
 <ul>
-<li>Fix docs showing <code>remote=</code> instead of <code>upstreams=</code> (Nick Craig-Wood)</li>
-<li>Throw error if duplicate directory name is specified (Nick Craig-Wood)</li>
-<li>Fix errors with backends shutting down while in use (Nick Craig-Wood)</li>
+<li>Fix docs showing <code>remote=</code> instead of
+<code>upstreams=</code> (Nick Craig-Wood)</li>
+<li>Throw error if duplicate directory name is specified (Nick
+Craig-Wood)</li>
+<li>Fix errors with backends shutting down while in use (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Fix hang on quit with --dropbox-batch-mode off (Nick Craig-Wood)</li>
-<li>Fix infinite loop on uploading a corrupted file (Nick Craig-Wood)</li>
+<li>Fix hang on quit with --dropbox-batch-mode off (Nick
+Craig-Wood)</li>
+<li>Fix infinite loop on uploading a corrupted file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Internetarchive
 <ul>
-<li>Ignore checksums for files using the different method (Lesmiscore)</li>
+<li>Ignore checksums for files using the different method
+(Lesmiscore)</li>
 <li>Handle hash symbol in the middle of filename (Lesmiscore)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
 <li>Fix working with whitelabel Elgiganten Cloud</li>
-<li>Do not store username in config when using standard auth (albertony)</li>
+<li>Do not store username in config when using standard auth
+(albertony)</li>
 </ul></li>
 <li>Mega
 <ul>
-<li>Fix nil pointer exception when bad node received (Nick Craig-Wood)</li>
+<li>Fix nil pointer exception when bad node received (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Fix --s3-no-head panic: reflect: Elem of invalid type s3.PutObjectInput (Nick Craig-Wood)</li>
+<li>Fix --s3-no-head panic: reflect: Elem of invalid type
+s3.PutObjectInput (Nick Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Fix issue with WS_FTP by working around failing RealPath (albertony)</li>
+<li>Fix issue with WS_FTP by working around failing RealPath
+(albertony)</li>
 </ul></li>
 <li>Union
 <ul>
-<li>Fix duplicated files when using directories with leading / (Nick Craig-Wood)</li>
-<li>Fix multiple files being uploaded when roots don't exist (Nick Craig-Wood)</li>
-<li>Fix panic due to misalignment of struct field in 32 bit architectures (r-ricci)</li>
+<li>Fix duplicated files when using directories with leading / (Nick
+Craig-Wood)</li>
+<li>Fix multiple files being uploaded when roots don't exist (Nick
+Craig-Wood)</li>
+<li>Fix panic due to misalignment of struct field in 32 bit
+architectures (r-ricci)</li>
 </ul></li>
 </ul>
 <h2 id="v1.59.0---2022-07-09">v1.59.0 - 2022-07-09</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.58.0...v1.59.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.58.0...v1.59.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
-<li><a href="/combine">Combine</a> multiple remotes in one directory tree (Nick Craig-Wood)</li>
-<li><a href="https://rclone.org/hidrive/">Hidrive</a> (Ovidiu Victor Tatar)</li>
-<li><a href="https://rclone.org/internetarchive/">Internet Archive</a> (Lesmiscore (Naoya Ozaki))</li>
+<li><a href="/combine">Combine</a> multiple remotes in one directory
+tree (Nick Craig-Wood)</li>
+<li><a href="https://rclone.org/hidrive/">Hidrive</a> (Ovidiu Victor
+Tatar)</li>
+<li><a href="https://rclone.org/internetarchive/">Internet Archive</a>
+(Lesmiscore (Naoya Ozaki))</li>
 <li>New S3 providers
 <ul>
-<li><a href="https://rclone.org/s3/#arvan-cloud">ArvanCloud AOS</a> (ehsantdy)</li>
-<li><a href="https://rclone.org/s3/#cloudflare-r2">Cloudflare R2</a> (Nick Craig-Wood)</li>
-<li><a href="https://rclone.org/s3/#huawei-obs">Huawei OBS</a> (m00594701)</li>
-<li><a href="https://rclone.org/s3/#idrive-e2">IDrive e2</a> (vyloy)</li>
+<li><a href="https://rclone.org/s3/#arvan-cloud">ArvanCloud AOS</a>
+(ehsantdy)</li>
+<li><a href="https://rclone.org/s3/#cloudflare-r2">Cloudflare R2</a>
+(Nick Craig-Wood)</li>
+<li><a href="https://rclone.org/s3/#huawei-obs">Huawei OBS</a>
+(m00594701)</li>
+<li><a href="https://rclone.org/s3/#idrive-e2">IDrive e2</a>
+(vyloy)</li>
 </ul></li>
 </ul></li>
 <li>New commands
 <ul>
-<li><a href="https://rclone.org/commands/rclone_test_makefile/">test makefile</a>: Create a single file for testing (Nick Craig-Wood)</li>
+<li><a href="https://rclone.org/commands/rclone_test_makefile/">test
+makefile</a>: Create a single file for testing (Nick Craig-Wood)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li><a href="https://rclone.org/docs/#metadata">Metadata framework</a> to read and write system and user metadata on backends (Nick Craig-Wood)
+<li><a href="https://rclone.org/docs/#metadata">Metadata framework</a>
+to read and write system and user metadata on backends (Nick Craig-Wood)
 <ul>
-<li>Implemented initially for <code>local</code>, <code>s3</code> and <code>internetarchive</code> backends</li>
-<li><code>--metadata</code>/<code>-M</code> flag to control whether metadata is copied</li>
-<li><code>--metadata-set</code> flag to specify metadata for uploads</li>
-<li>Thanks to <a href="https://manz-solutions.at/">Manz Solutions</a> for sponsoring this work.</li>
+<li>Implemented initially for <code>local</code>, <code>s3</code> and
+<code>internetarchive</code> backends</li>
+<li><code>--metadata</code>/<code>-M</code> flag to control whether
+metadata is copied</li>
+<li><code>--metadata-set</code> flag to specify metadata for
+uploads</li>
+<li>Thanks to <a href="https://manz-solutions.at/">Manz Solutions</a>
+for sponsoring this work.</li>
 </ul></li>
 <li>build
 <ul>
-<li>Update to go1.18 and make go1.16 the minimum required version (Nick Craig-Wood)</li>
-<li>Update android go build to 1.18.x and NDK to 23.1.7779620 (Nick Craig-Wood)</li>
+<li>Update to go1.18 and make go1.16 the minimum required version (Nick
+Craig-Wood)</li>
+<li>Update android go build to 1.18.x and NDK to 23.1.7779620 (Nick
+Craig-Wood)</li>
 <li>All windows binaries now no longer CGO (Nick Craig-Wood)</li>
-<li>Add <code>linux/arm/v6</code> to docker images (Nick Craig-Wood)</li>
-<li>A huge number of fixes found with <a href="https://staticcheck.io/">staticcheck</a> (albertony)</li>
-<li>Configurable version suffix independent of version number (albertony)</li>
+<li>Add <code>linux/arm/v6</code> to docker images (Nick
+Craig-Wood)</li>
+<li>A huge number of fixes found with <a
+href="https://staticcheck.io/">staticcheck</a> (albertony)</li>
+<li>Configurable version suffix independent of version number
+(albertony)</li>
 </ul></li>
-<li>check: Implement <code>--no-traverse</code> and <code>--no-unicode-normalization</code> (Nick Craig-Wood)</li>
+<li>check: Implement <code>--no-traverse</code> and
+<code>--no-unicode-normalization</code> (Nick Craig-Wood)</li>
 <li>config: Readability improvements (albertony)</li>
-<li>copyurl: Add <code>--header-filename</code> to honor the HTTP header filename directive (J-P Treen)</li>
-<li>filter: Allow multiple <code>--exclude-if-present</code> flags (albertony)</li>
-<li>fshttp: Add <code>--disable-http-keep-alives</code> to disable HTTP Keep Alives (Nick Craig-Wood)</li>
+<li>copyurl: Add <code>--header-filename</code> to honor the HTTP header
+filename directive (J-P Treen)</li>
+<li>filter: Allow multiple <code>--exclude-if-present</code> flags
+(albertony)</li>
+<li>fshttp: Add <code>--disable-http-keep-alives</code> to disable HTTP
+Keep Alives (Nick Craig-Wood)</li>
 <li>install.sh
 <ul>
-<li>Set the modes on the files and/or directories on macOS (Michael C Tiernan - MIT-Research Computing Project)</li>
-<li>Pre verify sudo authorization <code>-v</code> before calling curl. (Michael C Tiernan - MIT-Research Computing Project)</li>
+<li>Set the modes on the files and/or directories on macOS (Michael C
+Tiernan - MIT-Research Computing Project)</li>
+<li>Pre verify sudo authorization <code>-v</code> before calling curl.
+(Michael C Tiernan - MIT-Research Computing Project)</li>
 </ul></li>
 <li>lib/encoder: Add Semicolon encoding (Nick Craig-Wood)</li>
-<li>lsf: Add metadata support with <code>M</code> flag (Nick Craig-Wood)</li>
-<li>lsjson: Add <code>--metadata</code>/<code>-M</code> flag (Nick Craig-Wood)</li>
+<li>lsf: Add metadata support with <code>M</code> flag (Nick
+Craig-Wood)</li>
+<li>lsjson: Add <code>--metadata</code>/<code>-M</code> flag (Nick
+Craig-Wood)</li>
 <li>ncdu
 <ul>
 <li>Implement multi selection (CrossR)</li>
 <li>Replace termbox with tcell's termbox wrapper (eNV25)</li>
-<li>Display correct path in delete confirmation dialog (Roberto Ricci)</li>
+<li>Display correct path in delete confirmation dialog (Roberto
+Ricci)</li>
 </ul></li>
 <li>operations
 <ul>
-<li>Speed up hash checking by aborting the other hash if first returns nothing (Nick Craig-Wood)</li>
+<li>Speed up hash checking by aborting the other hash if first returns
+nothing (Nick Craig-Wood)</li>
 <li>Use correct src/dst in some log messages (zzr93)</li>
 </ul></li>
-<li>rcat: Check checksums by default like copy does (Nick Craig-Wood)</li>
-<li>selfupdate: Replace deprecated <code>x/crypto/openpgp</code> package with <code>ProtonMail/go-crypto</code> (albertony)</li>
-<li>serve ftp: Check <code>--passive-port</code> arguments are correct (Nick Craig-Wood)</li>
-<li>size: Warn about inaccurate results when objects with unknown size (albertony)</li>
-<li>sync: Overlap check is now filter-sensitive so <code>--backup-dir</code> can be in the root provided it is filtered (Nick)</li>
-<li>test info: Check file name lengths using 1,2,3,4 byte unicode characters (Nick Craig-Wood)</li>
-<li>test makefile(s): <code>--sparse</code>, <code>--zero</code>, <code>--pattern</code>, <code>--ascii</code>, <code>--chargen</code> flags to control file contents (Nick Craig-Wood)</li>
-<li>Make sure we call the <code>Shutdown</code> method on backends (Martin Czygan)</li>
+<li>rcat: Check checksums by default like copy does (Nick
+Craig-Wood)</li>
+<li>selfupdate: Replace deprecated <code>x/crypto/openpgp</code> package
+with <code>ProtonMail/go-crypto</code> (albertony)</li>
+<li>serve ftp: Check <code>--passive-port</code> arguments are correct
+(Nick Craig-Wood)</li>
+<li>size: Warn about inaccurate results when objects with unknown size
+(albertony)</li>
+<li>sync: Overlap check is now filter-sensitive so
+<code>--backup-dir</code> can be in the root provided it is filtered
+(Nick)</li>
+<li>test info: Check file name lengths using 1,2,3,4 byte unicode
+characters (Nick Craig-Wood)</li>
+<li>test makefile(s): <code>--sparse</code>, <code>--zero</code>,
+<code>--pattern</code>, <code>--ascii</code>, <code>--chargen</code>
+flags to control file contents (Nick Craig-Wood)</li>
+<li>Make sure we call the <code>Shutdown</code> method on backends
+(Martin Czygan)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>accounting: Fix unknown length file transfers counting 3 transfers each (buda)</li>
-<li>ncdu: Fix issue where dir size is summed when file sizes are -1 (albertony)</li>
+<li>accounting: Fix unknown length file transfers counting 3 transfers
+each (buda)</li>
+<li>ncdu: Fix issue where dir size is summed when file sizes are -1
+(albertony)</li>
 <li>sync/copy/move
 <ul>
-<li>Fix <code>--fast-list</code> <code>--create-empty-src-dirs</code> and <code>--exclude</code> (Nick Craig-Wood)</li>
-<li>Fix <code>--max-duration</code> and <code>--cutoff-mode soft</code> (Nick Craig-Wood)</li>
+<li>Fix <code>--fast-list</code> <code>--create-empty-src-dirs</code>
+and <code>--exclude</code> (Nick Craig-Wood)</li>
+<li>Fix <code>--max-duration</code> and <code>--cutoff-mode soft</code>
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Fix fs cache unpin (Martin Czygan)</li>
-<li>Set proper exit code for errors that are not low-level retried (e.g. size/timestamp changing) (albertony)</li>
+<li>Set proper exit code for errors that are not low-level retried (e.g.
+size/timestamp changing) (albertony)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Support <code>windows/arm64</code> (may still be problems - see <a href="https://github.com/rclone/rclone/issues/5828">#5828</a>) (Nick Craig-Wood)</li>
+<li>Support <code>windows/arm64</code> (may still be problems - see <a
+href="https://github.com/rclone/rclone/issues/5828">#5828</a>) (Nick
+Craig-Wood)</li>
 <li>Log IO errors at ERROR level (Nick Craig-Wood)</li>
 <li>Ignore <code>_netdev</code> mount argument (Hugal31)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Add <code>--vfs-fast-fingerprint</code> for less accurate but faster fingerprints (Nick Craig-Wood)</li>
-<li>Add <code>--vfs-disk-space-total-size</code> option to manually set the total disk space (Claudio Maradonna)</li>
-<li>vfscache: Fix fatal error: sync: unlock of unlocked mutex error (Nick Craig-Wood)</li>
+<li>Add <code>--vfs-fast-fingerprint</code> for less accurate but faster
+fingerprints (Nick Craig-Wood)</li>
+<li>Add <code>--vfs-disk-space-total-size</code> option to manually set
+the total disk space (Claudio Maradonna)</li>
+<li>vfscache: Fix fatal error: sync: unlock of unlocked mutex error
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix parsing of <code>--local-nounc</code> flag (Nick Craig-Wood)</li>
+<li>Fix parsing of <code>--local-nounc</code> flag (Nick
+Craig-Wood)</li>
 <li>Add Metadata support (Nick Craig-Wood)</li>
 </ul></li>
 <li>Crypt
@@ -39228,15 +55382,19 @@ $ tree /tmp/c
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Calculate Chunksize/blocksize to stay below maxUploadParts (Leroy van Logchem)</li>
-<li>Use chunksize lib to determine chunksize dynamically (Derek Battams)</li>
+<li>Calculate Chunksize/blocksize to stay below maxUploadParts (Leroy
+van Logchem)</li>
+<li>Use chunksize lib to determine chunksize dynamically (Derek
+Battams)</li>
 <li>Case insensitive access tier (Rob Pickerill)</li>
 <li>Allow remote emulator (azurite) (Lorenzo Maiorfi)</li>
 </ul></li>
 <li>B2
 <ul>
-<li>Add <code>--b2-version-at</code> flag to show file versions at time specified (SwazRGB)</li>
-<li>Use chunksize lib to determine chunksize dynamically (Derek Battams)</li>
+<li>Add <code>--b2-version-at</code> flag to show file versions at time
+specified (SwazRGB)</li>
+<li>Use chunksize lib to determine chunksize dynamically (Derek
+Battams)</li>
 </ul></li>
 <li>Chunker
 <ul>
@@ -39248,19 +55406,26 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Make <code>backend config -o config</code> add a combined <code>AllDrives:</code> remote (Nick Craig-Wood)</li>
-<li>Make <code>--drive-shared-with-me</code> work with shared drives (Nick Craig-Wood)</li>
-<li>Add <code>--drive-resource-key</code> for accessing link-shared files (Nick Craig-Wood)</li>
-<li>Add backend commands <code>exportformats</code> and <code>importformats</code> for debugging (Nick Craig-Wood)</li>
-<li>Fix 404 errors on copy/server side copy objects from public folder (Nick Craig-Wood)</li>
+<li>Make <code>backend config -o config</code> add a combined
+<code>AllDrives:</code> remote (Nick Craig-Wood)</li>
+<li>Make <code>--drive-shared-with-me</code> work with shared drives
+(Nick Craig-Wood)</li>
+<li>Add <code>--drive-resource-key</code> for accessing link-shared
+files (Nick Craig-Wood)</li>
+<li>Add backend commands <code>exportformats</code> and
+<code>importformats</code> for debugging (Nick Craig-Wood)</li>
+<li>Fix 404 errors on copy/server side copy objects from public folder
+(Nick Craig-Wood)</li>
 <li>Update Internal OAuth consent screen docs (Phil Shackleton)</li>
 <li>Moved <code>root_folder_id</code> to advanced section (Abhiraj)</li>
 </ul></li>
 <li>Dropbox
 <ul>
 <li>Migrate from deprecated api (m8rge)</li>
-<li>Add logs to show when poll interval limits are exceeded (Nick Craig-Wood)</li>
-<li>Fix nil pointer exception on dropbox impersonate user not found (Nick Craig-Wood)</li>
+<li>Add logs to show when poll interval limits are exceeded (Nick
+Craig-Wood)</li>
+<li>Fix nil pointer exception on dropbox impersonate user not found
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Fichier
 <ul>
@@ -39269,14 +55434,18 @@ $ tree /tmp/c
 <li>FTP
 <ul>
 <li>Add support for <code>disable_utf8</code> option (Jason Zheng)</li>
-<li>Revert to upstream <code>github.com/jlaffaye/ftp</code> from our fork (Nick Craig-Wood)</li>
+<li>Revert to upstream <code>github.com/jlaffaye/ftp</code> from our
+fork (Nick Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Add <code>--gcs-no-check-bucket</code> to minimise transactions and perms (Nick Gooding)</li>
-<li>Add <code>--gcs-decompress</code> flag to decompress gzip-encoded files (Nick Craig-Wood)
+<li>Add <code>--gcs-no-check-bucket</code> to minimise transactions and
+perms (Nick Gooding)</li>
+<li>Add <code>--gcs-decompress</code> flag to decompress gzip-encoded
+files (Nick Craig-Wood)
 <ul>
-<li>by default these will be downloaded compressed (which previously failed)</li>
+<li>by default these will be downloaded compressed (which previously
+failed)</li>
 </ul></li>
 </ul></li>
 <li>Hasher
@@ -39289,22 +55458,29 @@ $ tree /tmp/c
 </ul></li>
 <li>Jottacloud
 <ul>
-<li>Add support for upload to custom device and mountpoint (albertony)</li>
-<li>Always store username in config and use it to avoid initial API request (albertony)</li>
-<li>Fix issue with server-side copy when destination is in trash (albertony)</li>
-<li>Fix listing output of remote with special characters (albertony)</li>
+<li>Add support for upload to custom device and mountpoint
+(albertony)</li>
+<li>Always store username in config and use it to avoid initial API
+request (albertony)</li>
+<li>Fix issue with server-side copy when destination is in trash
+(albertony)</li>
+<li>Fix listing output of remote with special characters
+(albertony)</li>
 </ul></li>
 <li>Mailru
 <ul>
-<li>Fix timeout by using int instead of time.Duration for keeping number of seconds (albertony)</li>
+<li>Fix timeout by using int instead of time.Duration for keeping number
+of seconds (albertony)</li>
 </ul></li>
 <li>Mega
 <ul>
-<li>Document using MEGAcmd to help with login failures (Art M. Gallagher)</li>
+<li>Document using MEGAcmd to help with login failures (Art M.
+Gallagher)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Implement <code>--poll-interval</code> for onedrive (Hugo Laloge)</li>
+<li>Implement <code>--poll-interval</code> for onedrive (Hugo
+Laloge)</li>
 <li>Add access scopes option (Sven Gerber)</li>
 </ul></li>
 <li>Opendrive
@@ -39318,31 +55494,43 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Use PUT Object instead of presigned URLs to upload single part objects (Nick Craig-Wood)</li>
-<li>Backend restore command to skip non-GLACIER objects (Vincent Murphy)</li>
-<li>Use chunksize lib to determine chunksize dynamically (Derek Battams)</li>
+<li>Use PUT Object instead of presigned URLs to upload single part
+objects (Nick Craig-Wood)</li>
+<li>Backend restore command to skip non-GLACIER objects (Vincent
+Murphy)</li>
+<li>Use chunksize lib to determine chunksize dynamically (Derek
+Battams)</li>
 <li>Retry RequestTimeout errors (Nick Craig-Wood)</li>
 <li>Implement reading and writing of metadata (Nick Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
 <li>Add support for about and hashsum on windows server (albertony)</li>
-<li>Use vendor-specific VFS statistics extension for about if available (albertony)</li>
-<li>Add <code>--sftp-chunk-size</code> to control packets sizes for high latency links (Nick Craig-Wood)</li>
-<li>Add <code>--sftp-concurrency</code> to improve high latency transfers (Nick Craig-Wood)</li>
-<li>Add <code>--sftp-set-env</code> option to set environment variables (Nick Craig-Wood)</li>
+<li>Use vendor-specific VFS statistics extension for about if available
+(albertony)</li>
+<li>Add <code>--sftp-chunk-size</code> to control packets sizes for high
+latency links (Nick Craig-Wood)</li>
+<li>Add <code>--sftp-concurrency</code> to improve high latency
+transfers (Nick Craig-Wood)</li>
+<li>Add <code>--sftp-set-env</code> option to set environment variables
+(Nick Craig-Wood)</li>
 <li>Add Hetzner Storage Boxes to supported sftp backends (Anthrazz)</li>
 </ul></li>
 <li>Storj
 <ul>
-<li>Fix put which lead to the file being unreadable when using mount (Erik van Velzen)</li>
+<li>Fix put which lead to the file being unreadable when using mount
+(Erik van Velzen)</li>
 </ul></li>
 <li>Union
 <ul>
-<li>Add <code>min_free_space</code> option for <code>lfs</code>/<code>eplfs</code> policies (Nick Craig-Wood)</li>
-<li>Fix uploading files to union of all bucket based remotes (Nick Craig-Wood)</li>
-<li>Fix get free space for remotes which don't support it (Nick Craig-Wood)</li>
-<li>Fix <code>eplus</code> policy to select correct entry for existing files (Nick Craig-Wood)</li>
+<li>Add <code>min_free_space</code> option for
+<code>lfs</code>/<code>eplfs</code> policies (Nick Craig-Wood)</li>
+<li>Fix uploading files to union of all bucket based remotes (Nick
+Craig-Wood)</li>
+<li>Fix get free space for remotes which don't support it (Nick
+Craig-Wood)</li>
+<li>Fix <code>eplus</code> policy to select correct entry for existing
+files (Nick Craig-Wood)</li>
 <li>Support metadata (Nick Craig-Wood)</li>
 </ul></li>
 <li>Uptobox
@@ -39363,35 +55551,44 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.58.1---2022-04-29">v1.58.1 - 2022-04-29</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.58.0...v1.58.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.58.0...v1.58.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>build: Update github.com/billziss-gh to github.com/winfsp (Nick Craig-Wood)</li>
-<li>filter: Fix timezone of <code>--min-age</code>/<code>-max-age</code> from UTC to local as documented (Nick Craig-Wood)</li>
+<li>build: Update github.com/billziss-gh to github.com/winfsp (Nick
+Craig-Wood)</li>
+<li>filter: Fix timezone of <code>--min-age</code>/<code>-max-age</code>
+from UTC to local as documented (Nick Craig-Wood)</li>
 <li>rc/js: Correct RC method names (Sơn Trần-Nguyễn)</li>
 <li>docs
 <ul>
 <li>Fix some links to command pages (albertony)</li>
-<li>Add <code>--multi-thread-streams</code> note to <code>--transfers</code>. (Zsolt Ero)</li>
+<li>Add <code>--multi-thread-streams</code> note to
+<code>--transfers</code>. (Zsolt Ero)</li>
 </ul></li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Fix <code>--devname</code> and fusermount: unknown option 'fsname' when mounting via rc (Nick Craig-Wood)</li>
+<li>Fix <code>--devname</code> and fusermount: unknown option 'fsname'
+when mounting via rc (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Remove wording which suggests VFS is only for mounting (Nick Craig-Wood)</li>
+<li>Remove wording which suggests VFS is only for mounting (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Fix retries of multipart uploads with incorrect_offset error (Nick Craig-Wood)</li>
+<li>Fix retries of multipart uploads with incorrect_offset error (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
 <li>Use the s3 pacer to speed up transactions (Nick Craig-Wood)</li>
-<li>pacer: Default the Google pacer to a burst of 100 to fix gcs pacing (Nick Craig-Wood)</li>
+<li>pacer: Default the Google pacer to a burst of 100 to fix gcs pacing
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
@@ -39415,12 +55612,14 @@ $ tree /tmp/c
 <li>S3
 <ul>
 <li>Add ChinaMobile EOS to provider list (GuoXingbin)</li>
-<li>Sync providers in config description with providers (Nick Craig-Wood)</li>
+<li>Sync providers in config description with providers (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
 <li>Fix OpenSSH 8.8+ RSA keys incompatibility (KARBOWSKI Piotr)</li>
-<li>Note that Scaleway C14 is deprecating SFTP in favor of S3 (Adrien Rey-Jarthon)</li>
+<li>Note that Scaleway C14 is deprecating SFTP in favor of S3 (Adrien
+Rey-Jarthon)</li>
 </ul></li>
 <li>Storj
 <ul>
@@ -39432,82 +55631,116 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.58.0---2022-03-18">v1.58.0 - 2022-03-18</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.57.0...v1.58.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.57.0...v1.58.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
 <li><a href="/netstorage">Akamai Netstorage</a> (Nil Alexandrov)</li>
-<li><a href="https://rclone.org/s3/#lyve">Seagate Lyve</a>, <a href="/s3/#seaweedfs">SeaweedFS</a>, <a href="/s3/#storj">Storj</a>, <a href="/s3/#RackCorp">RackCorp</a> via s3 backend</li>
-<li><a href="https://rclone.org/storj/">Storj</a> (renamed from Tardigrade - your old config files will continue working)</li>
+<li><a href="https://rclone.org/s3/#lyve">Seagate Lyve</a>, <a
+href="/s3/#seaweedfs">SeaweedFS</a>, <a href="/s3/#storj">Storj</a>, <a
+href="/s3/#RackCorp">RackCorp</a> via s3 backend</li>
+<li><a href="https://rclone.org/storj/">Storj</a> (renamed from
+Tardigrade - your old config files will continue working)</li>
 </ul></li>
 <li>New commands
 <ul>
-<li><a href="https://rclone.org/bisync/">bisync</a> - experimental bidirectional cloud sync (Ivan Andreev, Chris Nelson)</li>
+<li><a href="https://rclone.org/bisync/">bisync</a> - experimental
+bidirectional cloud sync (Ivan Andreev, Chris Nelson)</li>
 </ul></li>
 <li>New Features
 <ul>
 <li>build
 <ul>
-<li>Add <code>windows/arm64</code> build (<code>rclone mount</code> not supported yet) (Nick Craig-Wood)</li>
+<li>Add <code>windows/arm64</code> build (<code>rclone mount</code> not
+supported yet) (Nick Craig-Wood)</li>
 <li>Raise minimum go version to go1.15 (Nick Craig-Wood)</li>
 </ul></li>
-<li>config: Allow dot in remote names and improve config editing (albertony)</li>
+<li>config: Allow dot in remote names and improve config editing
+(albertony)</li>
 <li>dedupe: Add quit as a choice in interactive mode (albertony)</li>
 <li>dlna: Change icons to the newest ones. (Alain Nussbaumer)</li>
-<li>filter: Add <a href="https://rclone.org/filtering/#regexp"><code>{{ regexp }}</code> syntax</a> to pattern matches (Nick Craig-Wood)</li>
-<li>fshttp: Add prometheus metrics for HTTP status code (Michał Matczuk)</li>
-<li>hashsum: Support creating hash from data received on stdin (albertony)</li>
+<li>filter: Add <a
+href="https://rclone.org/filtering/#regexp"><code>{{ regexp }}</code>
+syntax</a> to pattern matches (Nick Craig-Wood)</li>
+<li>fshttp: Add prometheus metrics for HTTP status code (Michał
+Matczuk)</li>
+<li>hashsum: Support creating hash from data received on stdin
+(albertony)</li>
 <li>librclone
 <ul>
-<li>Allow empty string or null input instead of empty json object (albertony)</li>
+<li>Allow empty string or null input instead of empty json object
+(albertony)</li>
 <li>Add support for mount commands (albertony)</li>
 </ul></li>
 <li>operations: Add server-side moves to stats (Ole Frost)</li>
-<li>rc: Allow user to disable authentication for web gui (negative0)</li>
-<li>tree: Remove obsolete <code>--human</code> replaced by global <code>--human-readable</code> (albertony)</li>
-<li>version: Report correct friendly-name for newer Windows 10/11 versions (albertony)</li>
+<li>rc: Allow user to disable authentication for web gui
+(negative0)</li>
+<li>tree: Remove obsolete <code>--human</code> replaced by global
+<code>--human-readable</code> (albertony)</li>
+<li>version: Report correct friendly-name for newer Windows 10/11
+versions (albertony)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>build
 <ul>
-<li>Fix ARM architecture version in .deb packages after nfpm change (Nick Craig-Wood)</li>
-<li>Hard fork <code>github.com/jlaffaye/ftp</code> to fix <code>go get github.com/rclone/rclone</code> (Nick Craig-Wood)</li>
+<li>Fix ARM architecture version in .deb packages after nfpm change
+(Nick Craig-Wood)</li>
+<li>Hard fork <code>github.com/jlaffaye/ftp</code> to fix
+<code>go get github.com/rclone/rclone</code> (Nick Craig-Wood)</li>
 </ul></li>
-<li>oauthutil: Fix crash when webbrowser requests <code>/robots.txt</code> (Nick Craig-Wood)</li>
-<li>operations: Fix goroutine leak in case of copy retry (Ankur Gupta)</li>
+<li>oauthutil: Fix crash when webbrowser requests
+<code>/robots.txt</code> (Nick Craig-Wood)</li>
+<li>operations: Fix goroutine leak in case of copy retry (Ankur
+Gupta)</li>
 <li>rc:
 <ul>
-<li>Fix <code>operations/publiclink</code> default for <code>expires</code> parameter (Nick Craig-Wood)</li>
-<li>Fix missing computation of <code>transferQueueSize</code> when summing up statistics group (Carlo Mion)</li>
-<li>Fix missing <code>StatsInfo</code> fields in the computation of the group sum (Carlo Mion)</li>
+<li>Fix <code>operations/publiclink</code> default for
+<code>expires</code> parameter (Nick Craig-Wood)</li>
+<li>Fix missing computation of <code>transferQueueSize</code> when
+summing up statistics group (Carlo Mion)</li>
+<li>Fix missing <code>StatsInfo</code> fields in the computation of the
+group sum (Carlo Mion)</li>
 </ul></li>
-<li>sync: Fix <code>--max-duration</code> so it doesn't retry when the duration is exceeded (Nick Craig-Wood)</li>
-<li>touch: Fix issue where a directory is created instead of a file (albertony)</li>
+<li>sync: Fix <code>--max-duration</code> so it doesn't retry when the
+duration is exceeded (Nick Craig-Wood)</li>
+<li>touch: Fix issue where a directory is created instead of a file
+(albertony)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Add <code>--devname</code> to set the device name sent to FUSE for mount display (Nick Craig-Wood)</li>
+<li>Add <code>--devname</code> to set the device name sent to FUSE for
+mount display (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Add <code>vfs/stats</code> remote control to show statistics (Nick Craig-Wood)</li>
-<li>Fix <code>failed to _ensure cache internal error: downloaders is nil error</code> (Nick Craig-Wood)</li>
+<li>Add <code>vfs/stats</code> remote control to show statistics (Nick
+Craig-Wood)</li>
+<li>Fix
+<code>failed to _ensure cache internal error: downloaders is nil error</code>
+(Nick Craig-Wood)</li>
 <li>Fix handling of special characters in file names (Bumsu Hyeon)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix hash invalidation which caused errors with local crypt mount (Nick Craig-Wood)</li>
+<li>Fix hash invalidation which caused errors with local crypt mount
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Add <code>base64</code> and <code>base32768</code> filename encoding options (Max Sum, Sinan Tan)</li>
+<li>Add <code>base64</code> and <code>base32768</code> filename encoding
+options (Max Sum, Sinan Tan)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Implement <code>--azureblob-upload-concurrency</code> parameter to speed uploads (Nick Craig-Wood)</li>
-<li>Remove 100MB upper limit on <code>chunk_size</code> as it is no longer needed (Nick Craig-Wood)</li>
-<li>Raise <code>--azureblob-upload-concurrency</code> to 16 by default (Nick Craig-Wood)</li>
+<li>Implement <code>--azureblob-upload-concurrency</code> parameter to
+speed uploads (Nick Craig-Wood)</li>
+<li>Remove 100MB upper limit on <code>chunk_size</code> as it is no
+longer needed (Nick Craig-Wood)</li>
+<li>Raise <code>--azureblob-upload-concurrency</code> to 16 by default
+(Nick Craig-Wood)</li>
 <li>Fix crash with SAS URL and no container (Nick Craig-Wood)</li>
 </ul></li>
 <li>Compress
@@ -39518,16 +55751,22 @@ $ tree /tmp/c
 <li>Drive
 <ul>
 <li>Added <code>--drive-copy-shortcut-content</code> (Abhiraj)</li>
-<li>Disable OAuth OOB flow (copy a token) due to Google deprecation (Nick Craig-Wood)
+<li>Disable OAuth OOB flow (copy a token) due to Google deprecation
+(Nick Craig-Wood)
 <ul>
-<li>See <a href="https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob">the deprecation note</a>.</li>
+<li>See <a
+href="https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob">the
+deprecation note</a>.</li>
 </ul></li>
-<li>Add <code>--drive-skip-dangling-shortcuts</code> flag (Nick Craig-Wood)</li>
-<li>When using a link type <code>--drive-export-formats</code> shows all doc types (Nick Craig-Wood)</li>
+<li>Add <code>--drive-skip-dangling-shortcuts</code> flag (Nick
+Craig-Wood)</li>
+<li>When using a link type <code>--drive-export-formats</code> shows all
+doc types (Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Speed up directory listings by specifying 1000 items in a chunk (Nick Craig-Wood)</li>
+<li>Speed up directory listings by specifying 1000 items in a chunk
+(Nick Craig-Wood)</li>
 <li>Save an API request when at the root (Nick Craig-Wood)</li>
 </ul></li>
 <li>Fichier
@@ -39536,21 +55775,28 @@ $ tree /tmp/c
 </ul></li>
 <li>FTP
 <ul>
-<li>Add <code>--ftp-ask-password</code> to prompt for password when needed (Borna Butkovic)</li>
+<li>Add <code>--ftp-ask-password</code> to prompt for password when
+needed (Borna Butkovic)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
 <li>Add missing regions (Nick Craig-Wood)</li>
-<li>Disable OAuth OOB flow (copy a token) due to Google deprecation (Nick Craig-Wood)
+<li>Disable OAuth OOB flow (copy a token) due to Google deprecation
+(Nick Craig-Wood)
 <ul>
-<li>See <a href="https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob">the deprecation note</a>.</li>
+<li>See <a
+href="https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob">the
+deprecation note</a>.</li>
 </ul></li>
 </ul></li>
 <li>Googlephotos
 <ul>
-<li>Disable OAuth OOB flow (copy a token) due to Google deprecation (Nick Craig-Wood)
+<li>Disable OAuth OOB flow (copy a token) due to Google deprecation
+(Nick Craig-Wood)
 <ul>
-<li>See <a href="https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob">the deprecation note</a>.</li>
+<li>See <a
+href="https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob">the
+deprecation note</a>.</li>
 </ul></li>
 </ul></li>
 <li>Hasher
@@ -39559,11 +55805,13 @@ $ tree /tmp/c
 </ul></li>
 <li>Hdfs
 <ul>
-<li>Add file (Move) and directory move (DirMove) support (Andy Jackson)</li>
+<li>Add file (Move) and directory move (DirMove) support (Andy
+Jackson)</li>
 </ul></li>
 <li>HTTP
 <ul>
-<li>Improved recognition of URL pointing to a single file (albertony)</li>
+<li>Improved recognition of URL pointing to a single file
+(albertony)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
@@ -39580,9 +55828,11 @@ $ tree /tmp/c
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Add config option for oauth scope <code>Sites.Read.All</code> (Charlie Jiang)</li>
+<li>Add config option for oauth scope <code>Sites.Read.All</code>
+(Charlie Jiang)</li>
 <li>Minor optimization of quickxorhash (Isaac Levy)</li>
-<li>Add <code>--onedrive-root-folder-id</code> flag (Nick Craig-Wood)</li>
+<li>Add <code>--onedrive-root-folder-id</code> flag (Nick
+Craig-Wood)</li>
 <li>Do not retry on <code>400 pathIsTooLong</code> error (ctrl-q)</li>
 </ul></li>
 <li>Pcloud
@@ -39594,11 +55844,14 @@ $ tree /tmp/c
 <ul>
 <li>Use <code>ListObjectsV2</code> for faster listings (Felix Bünemann)
 <ul>
-<li>Fallback to <code>ListObject</code> v1 on unsupported providers (Nick Craig-Wood)</li>
+<li>Fallback to <code>ListObject</code> v1 on unsupported providers
+(Nick Craig-Wood)</li>
 </ul></li>
-<li>Use the <code>ETag</code> on multipart transfers to verify the transfer was OK (Nick Craig-Wood)
+<li>Use the <code>ETag</code> on multipart transfers to verify the
+transfer was OK (Nick Craig-Wood)
 <ul>
-<li>Add <code>--s3-use-multipart-etag</code> provider quirk to disable this on unsupported providers (Nick Craig-Wood)</li>
+<li>Add <code>--s3-use-multipart-etag</code> provider quirk to disable
+this on unsupported providers (Nick Craig-Wood)</li>
 </ul></li>
 <li>New Providers
 <ul>
@@ -39609,32 +55862,45 @@ $ tree /tmp/c
 </ul></li>
 <li>Add Wasabi AP Northeast 2 endpoint info (lindwurm)</li>
 <li>Add <code>GLACIER_IR</code> storage class (Yunhai Luo)</li>
-<li>Document <code>Content-MD5</code> workaround for object-lock enabled buckets (Paulo Martins)</li>
-<li>Fix multipart upload with <code>--no-head</code> flag (Nick Craig-Wood)</li>
-<li>Simplify content length processing in s3 with download url (Logeshwaran Murugesan)</li>
+<li>Document <code>Content-MD5</code> workaround for object-lock enabled
+buckets (Paulo Martins)</li>
+<li>Fix multipart upload with <code>--no-head</code> flag (Nick
+Craig-Wood)</li>
+<li>Simplify content length processing in s3 with download url
+(Logeshwaran Murugesan)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Add rclone to list of supported <code>md5sum</code>/<code>sha1sum</code> commands to look for (albertony)</li>
-<li>Refactor so we only have one way of running remote commands (Nick Craig-Wood)</li>
-<li>Fix timeout on hashing large files by sending keepalives (Nick Craig-Wood)</li>
-<li>Fix unnecessary seeking when uploading and downloading files (Nick Craig-Wood)</li>
-<li>Update docs on how to create <code>known_hosts</code> file (Nick Craig-Wood)</li>
+<li>Add rclone to list of supported
+<code>md5sum</code>/<code>sha1sum</code> commands to look for
+(albertony)</li>
+<li>Refactor so we only have one way of running remote commands (Nick
+Craig-Wood)</li>
+<li>Fix timeout on hashing large files by sending keepalives (Nick
+Craig-Wood)</li>
+<li>Fix unnecessary seeking when uploading and downloading files (Nick
+Craig-Wood)</li>
+<li>Update docs on how to create <code>known_hosts</code> file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Storj
 <ul>
 <li>Rename tardigrade backend to storj backend (Nick Craig-Wood)</li>
 <li>Implement server side Move for files (Nick Craig-Wood)</li>
-<li>Update docs to explain differences between s3 and this backend (Elek, Márton)</li>
+<li>Update docs to explain differences between s3 and this backend
+(Elek, Márton)</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Fix About so it shows info about the current container only (Nick Craig-Wood)</li>
+<li>Fix About so it shows info about the current container only (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Union
 <ul>
-<li>Fix treatment of remotes with <code>//</code> in (Nick Craig-Wood)</li>
-<li>Fix deadlock when one part of a multi-upload fails (Nick Craig-Wood)</li>
+<li>Fix treatment of remotes with <code>//</code> in (Nick
+Craig-Wood)</li>
+<li>Fix deadlock when one part of a multi-upload fails (Nick
+Craig-Wood)</li>
 <li>Fix eplus policy returned nil (Vitor Arruda)</li>
 </ul></li>
 <li>Yandex
@@ -39643,31 +55909,40 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.57.0---2021-11-01">v1.57.0 - 2021-11-01</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.56.0...v1.57.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.56.0...v1.57.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
-<li>Sia: for Sia decentralized cloud (Ian Levesque, Matthew Sevey, Ivan Andreev)</li>
-<li>Hasher: caches hashes and enable hashes for backends that don't support them (Ivan Andreev)</li>
+<li>Sia: for Sia decentralized cloud (Ian Levesque, Matthew Sevey, Ivan
+Andreev)</li>
+<li>Hasher: caches hashes and enable hashes for backends that don't
+support them (Ivan Andreev)</li>
 </ul></li>
 <li>New commands
 <ul>
-<li>lsjson --stat: to get info about a single file/dir and <code>operations/stat</code> api (Nick Craig-Wood)</li>
+<li>lsjson --stat: to get info about a single file/dir and
+<code>operations/stat</code> api (Nick Craig-Wood)</li>
 <li>config paths: show configured paths (albertony)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li>about: Make human-readable output more consistent with other commands (albertony)</li>
+<li>about: Make human-readable output more consistent with other
+commands (albertony)</li>
 <li>build
 <ul>
-<li>Use go1.17 for building and make go1.14 the minimum supported (Nick Craig-Wood)</li>
+<li>Use go1.17 for building and make go1.14 the minimum supported (Nick
+Craig-Wood)</li>
 <li>Update Go to 1.16 and NDK to 22b for Android builds (x0b)</li>
 </ul></li>
 <li>config
 <ul>
-<li>Support hyphen in remote name from environment variable (albertony)</li>
+<li>Support hyphen in remote name from environment variable
+(albertony)</li>
 <li>Make temporary directory user-configurable (albertony)</li>
-<li>Convert <code>--cache-dir</code> value to an absolute path (albertony)</li>
+<li>Convert <code>--cache-dir</code> value to an absolute path
+(albertony)</li>
 <li>Do not override MIME types from OS defaults (albertony)</li>
 </ul></li>
 <li>docs
@@ -39677,15 +55952,20 @@ $ tree /tmp/c
 <li>Mention make for building and cmount tag for macos (Alex Chen)</li>
 <li>...and many more contributions to numerous to mention!</li>
 </ul></li>
-<li>fs: Move with <code>--ignore-existing</code> will not delete skipped files (Nathan Collins)</li>
+<li>fs: Move with <code>--ignore-existing</code> will not delete skipped
+files (Nathan Collins)</li>
 <li>hashsum
 <ul>
-<li>Treat hash values in sum file as case insensitive (Ivan Andreev)</li>
-<li>Don't put <code>ERROR</code> or <code>UNSUPPORTED</code> in output (Ivan Andreev)</li>
+<li>Treat hash values in sum file as case insensitive (Ivan
+Andreev)</li>
+<li>Don't put <code>ERROR</code> or <code>UNSUPPORTED</code> in output
+(Ivan Andreev)</li>
 </ul></li>
 <li>lib/encoder: Add encoding of square brackets (Ivan Andreev)</li>
-<li>lib/file: Improve error message when attempting to create dir on nonexistent drive on windows (albertony)</li>
-<li>lib/http: Factor password hash salt into options with default (Nolan Woods)</li>
+<li>lib/file: Improve error message when attempting to create dir on
+nonexistent drive on windows (albertony)</li>
+<li>lib/http: Factor password hash salt into options with default (Nolan
+Woods)</li>
 <li>lib/kv: Add key-value database api (Ivan Andreev)</li>
 <li>librclone
 <ul>
@@ -39693,53 +55973,70 @@ $ tree /tmp/c
 <li>Free strings in python example (albertony)</li>
 </ul></li>
 <li>log: Optionally print pid in logs (Ivan Andreev)</li>
-<li>ls: Introduce <code>--human-readable</code> global option to print human-readable sizes (albertony)</li>
-<li>ncdu: Introduce key <code>u</code> to toggle human-readable (albertony)</li>
+<li>ls: Introduce <code>--human-readable</code> global option to print
+human-readable sizes (albertony)</li>
+<li>ncdu: Introduce key <code>u</code> to toggle human-readable
+(albertony)</li>
 <li>operations: Add <code>rmdirs -v</code> output (Justin Winokur)</li>
 <li>serve sftp
 <ul>
 <li>Generate an ECDSA server key as well as RSA (Nick Craig-Wood)</li>
-<li>Generate an Ed25519 server key as well as ECDSA and RSA (albertony)</li>
+<li>Generate an Ed25519 server key as well as ECDSA and RSA
+(albertony)</li>
 </ul></li>
 <li>serve docker
 <ul>
-<li>Allow to customize proxy settings of docker plugin (Ivan Andreev)</li>
+<li>Allow to customize proxy settings of docker plugin (Ivan
+Andreev)</li>
 <li>Build docker plugin for multiple platforms (Thomas Stachl)</li>
 </ul></li>
 <li>size: Include human-readable count (albertony)</li>
-<li>touch: Add support for touching files in directory, with recursive option, filtering and <code>--dry-run</code>/<code>-i</code> (albertony)</li>
-<li>tree: Option to print human-readable sizes removed in favor of global option (albertony)</li>
+<li>touch: Add support for touching files in directory, with recursive
+option, filtering and <code>--dry-run</code>/<code>-i</code>
+(albertony)</li>
+<li>tree: Option to print human-readable sizes removed in favor of
+global option (albertony)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>lib/http
 <ul>
-<li>Fix bad username check in single auth secret provider (Nolan Woods)</li>
+<li>Fix bad username check in single auth secret provider (Nolan
+Woods)</li>
 <li>Fix handling of SSL credentials (Nolan Woods)</li>
 </ul></li>
-<li>serve ftp: Ensure modtime is passed as UTC always to fix timezone oddities (Nick Craig-Wood)</li>
-<li>serve sftp: Fix generation of server keys on windows (albertony)</li>
+<li>serve ftp: Ensure modtime is passed as UTC always to fix timezone
+oddities (Nick Craig-Wood)</li>
+<li>serve sftp: Fix generation of server keys on windows
+(albertony)</li>
 <li>serve docker: Fix octal umask (Ivan Andreev)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Enable rclone to be run as mount helper direct from the fstab (Ivan Andreev)</li>
+<li>Enable rclone to be run as mount helper direct from the fstab (Ivan
+Andreev)</li>
 <li>Use procfs to validate mount on linux (Ivan Andreev)</li>
-<li>Correctly daemonize for compatibility with automount (Ivan Andreev)</li>
+<li>Correctly daemonize for compatibility with automount (Ivan
+Andreev)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Ensure names used in cache path are legal on current OS (albertony)</li>
-<li>Ignore <code>ECLOSED</code> when truncating file handles to fix intermittent bad file descriptor error (Nick Craig-Wood)</li>
+<li>Ensure names used in cache path are legal on current OS
+(albertony)</li>
+<li>Ignore <code>ECLOSED</code> when truncating file handles to fix
+intermittent bad file descriptor error (Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Refactor default OS encoding out from local backend into shared encoder lib (albertony)</li>
+<li>Refactor default OS encoding out from local backend into shared
+encoder lib (albertony)</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Return wrapped object even with <code>--crypt-no-data-encryption</code> (Ivan Andreev)</li>
-<li>Fix uploads with <code>--crypt-no-data-encryption</code> (Nick Craig-Wood)</li>
+<li>Return wrapped object even with
+<code>--crypt-no-data-encryption</code> (Ivan Andreev)</li>
+<li>Fix uploads with <code>--crypt-no-data-encryption</code> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
@@ -39747,12 +56044,17 @@ $ tree /tmp/c
 </ul></li>
 <li>Box
 <ul>
-<li>Make listings of heavily used directories more reliable (Nick Craig-Wood)</li>
+<li>Make listings of heavily used directories more reliable (Nick
+Craig-Wood)</li>
 <li>When doing cleanup delete as much as possible (Nick Craig-Wood)</li>
-<li>Add <code>--box-list-chunk</code> to control listing chunk size (Nick Craig-Wood)</li>
-<li>Delete items in parallel in cleanup using <code>--checkers</code> threads (Nick Craig-Wood)</li>
-<li>Add <code>--box-owned-by</code> to only show items owned by the login passed (Nick Craig-Wood)</li>
-<li>Retry <code>operation_blocked_temporary</code> errors (Nick Craig-Wood)</li>
+<li>Add <code>--box-list-chunk</code> to control listing chunk size
+(Nick Craig-Wood)</li>
+<li>Delete items in parallel in cleanup using <code>--checkers</code>
+threads (Nick Craig-Wood)</li>
+<li>Add <code>--box-owned-by</code> to only show items owned by the
+login passed (Nick Craig-Wood)</li>
+<li>Retry <code>operation_blocked_temporary</code> errors (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
@@ -39760,17 +56062,22 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Speed up directory listings by constraining the API listing using the current filters (fotile96, Ivan Andreev)</li>
-<li>Fix buffering for single request upload for files smaller than <code>--drive-upload-cutoff</code> (YenForYang)</li>
-<li>Add <code>-o config</code> option to <code>backend drives</code> to make config for all shared drives (Nick Craig-Wood)</li>
+<li>Speed up directory listings by constraining the API listing using
+the current filters (fotile96, Ivan Andreev)</li>
+<li>Fix buffering for single request upload for files smaller than
+<code>--drive-upload-cutoff</code> (YenForYang)</li>
+<li>Add <code>-o config</code> option to <code>backend drives</code> to
+make config for all shared drives (Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Add <code>--dropbox-batch-commit-timeout</code> to control batch timeout (Nick Craig-Wood)</li>
+<li>Add <code>--dropbox-batch-commit-timeout</code> to control batch
+timeout (Nick Craig-Wood)</li>
 </ul></li>
 <li>Filefabric
 <ul>
-<li>Make backoff exponential for error_background to fix errors (Nick Craig-Wood)</li>
+<li>Make backoff exponential for error_background to fix errors (Nick
+Craig-Wood)</li>
 <li>Fix directory move after API change (Nick Craig-Wood)</li>
 </ul></li>
 <li>FTP
@@ -39783,14 +56090,19 @@ $ tree /tmp/c
 </ul></li>
 <li>Googlephotos
 <ul>
-<li>Use encoder for album names to fix albums with control characters (Parth Shukla)</li>
+<li>Use encoder for album names to fix albums with control characters
+(Parth Shukla)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
-<li>Implement <code>SetModTime</code> to support modtime-only changes (albertony)</li>
-<li>Improved error handling with <code>SetModTime</code> and corrupt files in general (albertony)</li>
-<li>Add support for <code>UserInfo</code> (<code>rclone config userinfo</code>) feature (albertony)</li>
-<li>Return direct download link from <code>rclone link</code> command (albertony)</li>
+<li>Implement <code>SetModTime</code> to support modtime-only changes
+(albertony)</li>
+<li>Improved error handling with <code>SetModTime</code> and corrupt
+files in general (albertony)</li>
+<li>Add support for <code>UserInfo</code>
+(<code>rclone config userinfo</code>) feature (albertony)</li>
+<li>Return direct download link from <code>rclone link</code> command
+(albertony)</li>
 </ul></li>
 <li>Koofr
 <ul>
@@ -39804,16 +56116,21 @@ $ tree /tmp/c
 <ul>
 <li>Fix directory listing after API changes (Nick Craig-Wood)</li>
 <li>Fix server side move after API change (Nick Craig-Wood)</li>
-<li>Fix server side directory move after API changes (Nick Craig-Wood)</li>
+<li>Fix server side directory move after API changes (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
 <li>Add support to use CDN URL to download the file (Logeshwaran)</li>
 <li>Add AWS Snowball Edge to providers examples (r0kk3rz)</li>
-<li>Use a combination of SDK retries and rclone retries (Nick Craig-Wood)</li>
-<li>Fix IAM Role for Service Account not working and other auth problems (Nick Craig-Wood)</li>
-<li>Fix <code>shared_credentials_file</code> auth after reverting incorrect fix (Nick Craig-Wood)</li>
-<li>Fix corrupted on transfer: sizes differ 0 vs xxxx with Ceph (Nick Craig-Wood)</li>
+<li>Use a combination of SDK retries and rclone retries (Nick
+Craig-Wood)</li>
+<li>Fix IAM Role for Service Account not working and other auth problems
+(Nick Craig-Wood)</li>
+<li>Fix <code>shared_credentials_file</code> auth after reverting
+incorrect fix (Nick Craig-Wood)</li>
+<li>Fix corrupted on transfer: sizes differ 0 vs xxxx with Ceph (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Seafile
 <ul>
@@ -39830,31 +56147,41 @@ $ tree /tmp/c
 </ul></li>
 <li>Union
 <ul>
-<li>Fix rename not working with union of local disk and bucket based remote (Nick Craig-Wood)</li>
+<li>Fix rename not working with union of local disk and bucket based
+remote (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.56.2---2021-10-01">v1.56.2 - 2021-10-01</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.56.1...v1.56.2">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.56.1...v1.56.2">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
 <li>serve http: Re-add missing auth to http service (Nolan Woods)</li>
-<li>build: Update golang.org/x/sys to fix crash on macOS when compiled with go1.17 (Herby Gillot)</li>
+<li>build: Update golang.org/x/sys to fix crash on macOS when compiled
+with go1.17 (Herby Gillot)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Fix deadlock after failed update when concurrency=1 (Ivan Andreev)</li>
+<li>Fix deadlock after failed update when concurrency=1 (Ivan
+Andreev)</li>
 </ul></li>
 </ul>
 <h2 id="v1.56.1---2021-09-19">v1.56.1 - 2021-09-19</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.56.0...v1.56.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.56.0...v1.56.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>accounting: Fix maximum bwlimit by scaling scale max token bucket size (Nick Craig-Wood)</li>
+<li>accounting: Fix maximum bwlimit by scaling scale max token bucket
+size (Nick Craig-Wood)</li>
 <li>rc: Fix speed does not update in core/stats (negative0)</li>
-<li>selfupdate: Fix <code>--quiet</code> option, not quite quiet (yedamo)</li>
-<li>serve http: Fix <code>serve http</code> exiting directly after starting (Cnly)</li>
+<li>selfupdate: Fix <code>--quiet</code> option, not quite quiet
+(yedamo)</li>
+<li>serve http: Fix <code>serve http</code> exiting directly after
+starting (Cnly)</li>
 <li>build
 <ul>
 <li>Apply gofmt from golang 1.17 (Ivan Andreev)</li>
@@ -39868,8 +56195,10 @@ $ tree /tmp/c
 <li>VFS
 <ul>
 <li>Fix duplicates on rename (Nick Craig-Wood)</li>
-<li>Fix crash when truncating a just uploaded object (Nick Craig-Wood)</li>
-<li>Fix issue where empty dirs would build up in cache meta dir (albertony)</li>
+<li>Fix crash when truncating a just uploaded object (Nick
+Craig-Wood)</li>
+<li>Fix issue where empty dirs would build up in cache meta dir
+(albertony)</li>
 </ul></li>
 <li>Drive
 <ul>
@@ -39879,11 +56208,13 @@ $ tree /tmp/c
 <li>Onedrive
 <ul>
 <li>Handle HTTP 400 better in PublicLink (Alex Chen)</li>
-<li>Clarification of the process for creating custom client_id (Mariano Absatz)</li>
+<li>Clarification of the process for creating custom client_id (Mariano
+Absatz)</li>
 </ul></li>
 <li>Pcloud
 <ul>
-<li>Return an early error when Put is called with an unknown size (Nick Craig-Wood)</li>
+<li>Return an early error when Put is called with an unknown size (Nick
+Craig-Wood)</li>
 <li>Try harder to delete a failed upload (Nick Craig-Wood)</li>
 </ul></li>
 <li>S3
@@ -39897,15 +56228,19 @@ $ tree /tmp/c
 </ul></li>
 <li>SFTP
 <ul>
-<li>Remove spurious error message on <code>--sftp-disable-concurrent-reads</code> (Nick Craig-Wood)</li>
+<li>Remove spurious error message on
+<code>--sftp-disable-concurrent-reads</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>Sugarsync
 <ul>
-<li>Fix initial connection after config re-arrangement (Nick Craig-Wood)</li>
+<li>Fix initial connection after config re-arrangement (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.56.0---2021-07-20">v1.56.0 - 2021-07-20</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.55.0...v1.56.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.55.0...v1.56.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
@@ -39913,30 +56248,42 @@ $ tree /tmp/c
 </ul></li>
 <li>New commands
 <ul>
-<li><a href="https://rclone.org/commands/rclone_serve_docker/">serve docker</a> (Antoine GIRARD) (Ivan Andreev)
+<li><a href="https://rclone.org/commands/rclone_serve_docker/">serve
+docker</a> (Antoine GIRARD) (Ivan Andreev)
 <ul>
-<li>and accompanying <a href="https://rclone.org/docker/">docker volume plugin</a></li>
+<li>and accompanying <a href="https://rclone.org/docker/">docker volume
+plugin</a></li>
 </ul></li>
-<li><a href="https://rclone.org/commands/rclone_checksum/">checksum</a> to check files against a file of checksums (Ivan Andreev)
+<li><a href="https://rclone.org/commands/rclone_checksum/">checksum</a>
+to check files against a file of checksums (Ivan Andreev)
 <ul>
 <li>this is also available as <code>rclone md5sum -C</code> etc</li>
 </ul></li>
-<li><a href="https://rclone.org/commands/rclone_config_touch/">config touch</a>: ensure config exists at configured location (albertony)</li>
-<li><a href="https://rclone.org/commands/rclone_test_changenotify/">test changenotify</a>: command to help debugging changenotify (Nick Craig-Wood)</li>
+<li><a href="https://rclone.org/commands/rclone_config_touch/">config
+touch</a>: ensure config exists at configured location (albertony)</li>
+<li><a href="https://rclone.org/commands/rclone_test_changenotify/">test
+changenotify</a>: command to help debugging changenotify (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Deprecations
 <ul>
-<li><code>dbhashsum</code>: Remove command deprecated a year ago (Ivan Andreev)</li>
+<li><code>dbhashsum</code>: Remove command deprecated a year ago (Ivan
+Andreev)</li>
 <li><code>cache</code>: Deprecate cache backend (Ivan Andreev)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li>rework config system so it can be used non-interactively via cli and rc API.
+<li>rework config system so it can be used non-interactively via cli and
+rc API.
 <ul>
-<li>See docs in <a href="https://rclone.org/commands/rclone_config_create/">config create</a></li>
-<li>This is a very big change to all the backends so may cause breakages - please file bugs!</li>
+<li>See docs in <a
+href="https://rclone.org/commands/rclone_config_create/">config
+create</a></li>
+<li>This is a very big change to all the backends so may cause breakages
+- please file bugs!</li>
 </ul></li>
-<li>librclone - export the rclone RC as a C library (lewisxy) (Nick Craig-Wood)
+<li>librclone - export the rclone RC as a C library (lewisxy) (Nick
+Craig-Wood)
 <ul>
 <li>Link a C-API rclone shared object into your project</li>
 <li>Use the RC as an in memory interface</li>
@@ -39945,45 +56292,62 @@ $ tree /tmp/c
 </ul></li>
 <li>fs
 <ul>
-<li>Add <code>--disable-http2</code> for global http2 disable (Nick Craig-Wood)</li>
+<li>Add <code>--disable-http2</code> for global http2 disable (Nick
+Craig-Wood)</li>
 <li>Make <code>--dump</code> imply <code>-vv</code> (Alex Chen)</li>
 <li>Use binary prefixes for size and rate units (albertony)</li>
 <li>Use decimal prefixes for counts (albertony)</li>
 <li>Add google search widget to rclone.org (Ivan Andreev)</li>
 </ul></li>
 <li>accounting: Calculate rolling average speed (Haochen Tong)</li>
-<li>atexit: Terminate with non-zero status after receiving signal (Michael Hanselmann)</li>
+<li>atexit: Terminate with non-zero status after receiving signal
+(Michael Hanselmann)</li>
 <li>build
 <ul>
-<li>Only run event-based workflow scripts under rclone repo with manual override (Mathieu Carbou)</li>
+<li>Only run event-based workflow scripts under rclone repo with manual
+override (Mathieu Carbou)</li>
 <li>Add Android build with gomobile (x0b)</li>
 </ul></li>
-<li>check: Log the hash in use like cryptcheck does (Nick Craig-Wood)</li>
+<li>check: Log the hash in use like cryptcheck does (Nick
+Craig-Wood)</li>
 <li>version: Print os/version, kernel and bitness (Ivan Andreev)</li>
 <li>config
 <ul>
-<li>Prevent use of Windows reserved names in config file name (albertony)</li>
-<li>Create config file in windows appdata directory by default (albertony)</li>
-<li>Treat any config file paths with filename notfound as memory-only config (albertony)</li>
+<li>Prevent use of Windows reserved names in config file name
+(albertony)</li>
+<li>Create config file in windows appdata directory by default
+(albertony)</li>
+<li>Treat any config file paths with filename notfound as memory-only
+config (albertony)</li>
 <li>Delay load config file (albertony)</li>
-<li>Replace defaultConfig with a thread-safe in-memory implementation (Chris Macklin)</li>
-<li>Allow <code>config create</code> and friends to take <code>key=value</code> parameters (Nick Craig-Wood)</li>
-<li>Fixed issues with flags/options set by environment vars. (Ole Frost)</li>
+<li>Replace defaultConfig with a thread-safe in-memory implementation
+(Chris Macklin)</li>
+<li>Allow <code>config create</code> and friends to take
+<code>key=value</code> parameters (Nick Craig-Wood)</li>
+<li>Fixed issues with flags/options set by environment vars. (Ole
+Frost)</li>
 </ul></li>
 <li>fshttp: Implement graceful DSCP error handling (Tyson Moore)</li>
-<li>lib/http - provides an abstraction for a central http server that services can bind routes to (Nolan Woods)
+<li>lib/http - provides an abstraction for a central http server that
+services can bind routes to (Nolan Woods)
 <ul>
-<li>Add <code>--template</code> config and flags to serve/data (Nolan Woods)</li>
+<li>Add <code>--template</code> config and flags to serve/data (Nolan
+Woods)</li>
 <li>Add default 404 handler (Nolan Woods)</li>
 </ul></li>
 <li>link: Use "off" value for unset expiry (Nick Craig-Wood)</li>
-<li>oauthutil: Raise fatal error if token expired without refresh token (Alex Chen)</li>
-<li>rcat: Add <code>--size</code> flag for more efficient uploads of known size (Nazar Mishturak)</li>
-<li>serve sftp: Add <code>--stdio</code> flag to serve via stdio (Tom)</li>
-<li>sync: Don't warn about <code>--no-traverse</code> when <code>--files-from</code> is set (Nick Gaya)</li>
+<li>oauthutil: Raise fatal error if token expired without refresh token
+(Alex Chen)</li>
+<li>rcat: Add <code>--size</code> flag for more efficient uploads of
+known size (Nazar Mishturak)</li>
+<li>serve sftp: Add <code>--stdio</code> flag to serve via stdio
+(Tom)</li>
+<li>sync: Don't warn about <code>--no-traverse</code> when
+<code>--files-from</code> is set (Nick Gaya)</li>
 <li><code>test makefiles</code>
 <ul>
-<li>Add <code>--seed</code> flag and make data generated repeatable (Nick Craig-Wood)</li>
+<li>Add <code>--seed</code> flag and make data generated repeatable
+(Nick Craig-Wood)</li>
 <li>Add log levels and speed summary (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
@@ -39994,12 +56358,14 @@ $ tree /tmp/c
 <li>config
 <ul>
 <li>Fix issues with memory-only config file paths (albertony)</li>
-<li>Fix in memory config not saving on the fly backend config (Nick Craig-Wood)</li>
+<li>Fix in memory config not saving on the fly backend config (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>fshttp: Fix address parsing for DSCP (Tyson Moore)</li>
 <li>ncdu: Update termbox-go library to fix crash (Nick Craig-Wood)</li>
 <li>oauthutil: Fix old authorize result not recognised (Cnly)</li>
-<li>operations: Don't update timestamps of files in <code>--compare-dest</code> (Nick Gaya)</li>
+<li>operations: Don't update timestamps of files in
+<code>--compare-dest</code> (Nick Gaya)</li>
 <li>selfupdate: fix archive name on macos (Ivan Andreev)</li>
 </ul></li>
 <li>Mount
@@ -40008,59 +56374,77 @@ $ tree /tmp/c
 </ul></li>
 <li>VFS
 <ul>
-<li>Add cache reset for <code>--vfs-cache-max-size</code> handling at cache poll interval (Leo Luan)</li>
-<li>Fix modtime changing when reading file into cache (Nick Craig-Wood)</li>
+<li>Add cache reset for <code>--vfs-cache-max-size</code> handling at
+cache poll interval (Leo Luan)</li>
+<li>Fix modtime changing when reading file into cache (Nick
+Craig-Wood)</li>
 <li>Avoid unnecessary subdir in cache path (albertony)</li>
-<li>Fix that umask option cannot be set as environment variable (albertony)</li>
-<li>Do not print notice about missing poll-interval support when set to 0 (albertony)</li>
+<li>Fix that umask option cannot be set as environment variable
+(albertony)</li>
+<li>Do not print notice about missing poll-interval support when set to
+0 (albertony)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Always use readlink to read symlink size for better compatibility (Nick Craig-Wood)</li>
-<li>Add <code>--local-unicode-normalization</code> (and remove <code>--local-no-unicode-normalization</code>) (Nick Craig-Wood)</li>
+<li>Always use readlink to read symlink size for better compatibility
+(Nick Craig-Wood)</li>
+<li>Add <code>--local-unicode-normalization</code> (and remove
+<code>--local-no-unicode-normalization</code>) (Nick Craig-Wood)</li>
 <li>Skip entries removed concurrently with List() (Ivan Andreev)</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Support timestamped filenames from <code>--b2-versions</code> (Dominik Mydlil)</li>
+<li>Support timestamped filenames from <code>--b2-versions</code>
+(Dominik Mydlil)</li>
 </ul></li>
 <li>B2
 <ul>
-<li>Don't include the bucket name in public link file prefixes (Jeffrey Tolar)</li>
+<li>Don't include the bucket name in public link file prefixes (Jeffrey
+Tolar)</li>
 <li>Fix versions and .files with no extension (Nick Craig-Wood)</li>
 <li>Factor version handling into lib/version (Dominik Mydlil)</li>
 </ul></li>
 <li>Box
 <ul>
-<li>Use upload preflight check to avoid listings in file uploads (Nick Craig-Wood)</li>
-<li>Return errors instead of calling log.Fatal with them (Nick Craig-Wood)</li>
+<li>Use upload preflight check to avoid listings in file uploads (Nick
+Craig-Wood)</li>
+<li>Return errors instead of calling log.Fatal with them (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Switch to the Drives API for looking up shared drives (Nick Craig-Wood)</li>
+<li>Switch to the Drives API for looking up shared drives (Nick
+Craig-Wood)</li>
 <li>Fix some google docs being treated as files (Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Add <code>--dropbox-batch-mode</code> flag to speed up uploading (Nick Craig-Wood)
+<li>Add <code>--dropbox-batch-mode</code> flag to speed up uploading
+(Nick Craig-Wood)
 <ul>
-<li>Read the <a href="https://rclone.org/dropbox/#batch-mode">batch mode</a> docs for more info</li>
+<li>Read the <a href="https://rclone.org/dropbox/#batch-mode">batch
+mode</a> docs for more info</li>
 </ul></li>
-<li>Set visibility in link sharing when <code>--expire</code> is set (Nick Craig-Wood)</li>
+<li>Set visibility in link sharing when <code>--expire</code> is set
+(Nick Craig-Wood)</li>
 <li>Simplify chunked uploads (Alexey Ivanov)</li>
 <li>Improve "own App IP" instructions (Ivan Andreev)</li>
 </ul></li>
 <li>Fichier
 <ul>
-<li>Check if more than one upload link is returned (Nick Craig-Wood)</li>
-<li>Support downloading password protected files and folders (Florian Penzkofer)</li>
+<li>Check if more than one upload link is returned (Nick
+Craig-Wood)</li>
+<li>Support downloading password protected files and folders (Florian
+Penzkofer)</li>
 <li>Make error messages report text from the API (Nick Craig-Wood)</li>
 <li>Fix move of files in the same directory (Nick Craig-Wood)</li>
-<li>Check that we actually got a download token and retry if we didn't (buengese)</li>
+<li>Check that we actually got a download token and retry if we didn't
+(buengese)</li>
 </ul></li>
 <li>Filefabric
 <ul>
-<li>Fix listing after change of from field from "int" to int. (Nick Craig-Wood)</li>
+<li>Fix listing after change of from field from "int" to int. (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
@@ -40089,22 +56473,28 @@ $ tree /tmp/c
 <li>Onedrive
 <ul>
 <li>Add <code>list_chunk option</code> (Nick Gaya)</li>
-<li>Also report root error if unable to cancel multipart upload (Cnly)</li>
-<li>Fix failed to configure: empty token found error (Nick Craig-Wood)</li>
+<li>Also report root error if unable to cancel multipart upload
+(Cnly)</li>
+<li>Fix failed to configure: empty token found error (Nick
+Craig-Wood)</li>
 <li>Make link return direct download link (Xuanchen Wu)</li>
 </ul></li>
 <li>S3
 <ul>
 <li>Add <code>--s3-no-head-object</code> (Tatsuya Noyori)</li>
-<li>Remove WebIdentityRoleProvider to fix crash on auth (Nick Craig-Wood)</li>
-<li>Don't check to see if remote is object if it ends with / (Nick Craig-Wood)</li>
+<li>Remove WebIdentityRoleProvider to fix crash on auth (Nick
+Craig-Wood)</li>
+<li>Don't check to see if remote is object if it ends with / (Nick
+Craig-Wood)</li>
 <li>Add SeaweedFS (Chris Lu)</li>
 <li>Update Alibaba OSS endpoints (Chuan Zh)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Fix performance regression by re-enabling concurrent writes (Nick Craig-Wood)</li>
-<li>Expand tilde and environment variables in configured <code>known_hosts_file</code> (albertony)</li>
+<li>Fix performance regression by re-enabling concurrent writes (Nick
+Craig-Wood)</li>
+<li>Expand tilde and environment variables in configured
+<code>known_hosts_file</code> (albertony)</li>
 </ul></li>
 <li>Tardigrade
 <ul>
@@ -40119,7 +56509,9 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.55.1---2021-04-26">v1.55.1 - 2021-04-26</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.55.0...v1.55.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.55.0...v1.55.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
@@ -40128,12 +56520,15 @@ $ tree /tmp/c
 <li>Dont detect FUSE if build is static (Ivan Andreev)</li>
 <li>Add build tag noselfupdate (Ivan Andreev)</li>
 </ul></li>
-<li>sync: Fix incorrect error reported by graceful cutoff (Nick Craig-Wood)</li>
+<li>sync: Fix incorrect error reported by graceful cutoff (Nick
+Craig-Wood)</li>
 <li>install.sh: fix macOS arm64 download (Nick Craig-Wood)</li>
-<li>build: Fix version numbers in android branch builds (Nick Craig-Wood)</li>
+<li>build: Fix version numbers in android branch builds (Nick
+Craig-Wood)</li>
 <li>docs
 <ul>
-<li>Contributing.md: update setup instructions for go1.16 (Nick Gaya)</li>
+<li>Contributing.md: update setup instructions for go1.16 (Nick
+Gaya)</li>
 <li>WinFsp 2021 is out of beta (albertony)</li>
 <li>Minor cleanup of space around code section (albertony)</li>
 <li>Fixed some typos (albertony)</li>
@@ -40141,7 +56536,8 @@ $ tree /tmp/c
 </ul></li>
 <li>VFS
 <ul>
-<li>Fix a code path which allows dirty data to be removed causing data loss (Nick Craig-Wood)</li>
+<li>Fix a code path which allows dirty data to be removed causing data
+loss (Nick Craig-Wood)</li>
 </ul></li>
 <li>Compress
 <ul>
@@ -40154,9 +56550,12 @@ $ tree /tmp/c
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Add missing team_data.member scope for use with --impersonate (Nick Craig-Wood)</li>
-<li>Fix About after scopes changes - rclone config reconnect needed (Nick Craig-Wood)</li>
-<li>Fix Unable to decrypt returned paths from changeNotify (Nick Craig-Wood)</li>
+<li>Add missing team_data.member scope for use with --impersonate (Nick
+Craig-Wood)</li>
+<li>Fix About after scopes changes - rclone config reconnect needed
+(Nick Craig-Wood)</li>
+<li>Fix Unable to decrypt returned paths from changeNotify (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
@@ -40164,145 +56563,216 @@ $ tree /tmp/c
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Work around for random "Unable to initialize RPS" errors (OleFrost)</li>
+<li>Work around for random "Unable to initialize RPS" errors
+(OleFrost)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Revert sftp library to v1.12.0 from v1.13.0 to fix performance regression (Nick Craig-Wood)</li>
-<li>Fix Update ReadFrom failed: failed to send packet: EOF errors (Nick Craig-Wood)</li>
+<li>Revert sftp library to v1.12.0 from v1.13.0 to fix performance
+regression (Nick Craig-Wood)</li>
+<li>Fix Update ReadFrom failed: failed to send packet: EOF errors (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Zoho
 <ul>
 <li>Fix error when region isn't set (buengese)</li>
-<li>Do not ask for mountpoint twice when using headless setup (buengese)</li>
+<li>Do not ask for mountpoint twice when using headless setup
+(buengese)</li>
 </ul></li>
 </ul>
 <h2 id="v1.55.0---2021-03-31">v1.55.0 - 2021-03-31</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.54.0...v1.55.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.54.0...v1.55.0">See
+commits</a></p>
 <ul>
 <li>New commands
 <ul>
-<li><a href="https://rclone.org/commands/rclone_selfupdate/">selfupdate</a> (Ivan Andreev)
+<li><a
+href="https://rclone.org/commands/rclone_selfupdate/">selfupdate</a>
+(Ivan Andreev)
 <ul>
-<li>Allows rclone to update itself in-place or via a package (using <code>--package</code> flag)</li>
+<li>Allows rclone to update itself in-place or via a package (using
+<code>--package</code> flag)</li>
 <li>Reads cryptographically signed signatures for non beta releases</li>
 <li>Works on all OSes.</li>
 </ul></li>
-<li><a href="https://rclone.org/commands/rclone_test/">test</a> - these are test commands - use with care!
+<li><a href="https://rclone.org/commands/rclone_test/">test</a> - these
+are test commands - use with care!
 <ul>
-<li><code>histogram</code> - Makes a histogram of file name characters.</li>
-<li><code>info</code> - Discovers file name or other limitations for paths.</li>
-<li><code>makefiles</code> - Make a random file hierarchy for testing.</li>
-<li><code>memory</code> - Load all the objects at remote:path into memory and report memory stats.</li>
+<li><code>histogram</code> - Makes a histogram of file name
+characters.</li>
+<li><code>info</code> - Discovers file name or other limitations for
+paths.</li>
+<li><code>makefiles</code> - Make a random file hierarchy for
+testing.</li>
+<li><code>memory</code> - Load all the objects at remote:path into
+memory and report memory stats.</li>
 </ul></li>
 </ul></li>
 <li>New Features
 <ul>
-<li><a href="https://rclone.org/docs/#connection-strings">Connection strings</a>
+<li><a href="https://rclone.org/docs/#connection-strings">Connection
+strings</a>
 <ul>
-<li>Config parameters can now be passed as part of the remote name as a connection string.</li>
-<li>For example, to do the equivalent of <code>--drive-shared-with-me</code> use <code>drive,shared_with_me:</code></li>
-<li>Make sure we don't save on the fly remote config to the config file (Nick Craig-Wood)</li>
-<li>Make sure backends with additional config have a different name for caching (Nick Craig-Wood)</li>
-<li>This work was sponsored by CERN, through the <a href="https://cs3mesh4eosc.eu/">CS3MESH4EOSC Project</a>.
+<li>Config parameters can now be passed as part of the remote name as a
+connection string.</li>
+<li>For example, to do the equivalent of
+<code>--drive-shared-with-me</code> use
+<code>drive,shared_with_me:</code></li>
+<li>Make sure we don't save on the fly remote config to the config file
+(Nick Craig-Wood)</li>
+<li>Make sure backends with additional config have a different name for
+caching (Nick Craig-Wood)</li>
+<li>This work was sponsored by CERN, through the <a
+href="https://cs3mesh4eosc.eu/">CS3MESH4EOSC Project</a>.
 <ul>
-<li>CS3MESH4EOSC has received funding from the European Union’s Horizon 2020</li>
-<li>research and innovation programme under Grant Agreement no. 863353.</li>
+<li>CS3MESH4EOSC has received funding from the European Union’s Horizon
+2020</li>
+<li>research and innovation programme under Grant Agreement no.
+863353.</li>
 </ul></li>
 </ul></li>
 <li>build
 <ul>
-<li>Update go build version to go1.16 and raise minimum go version to go1.13 (Nick Craig-Wood)</li>
-<li>Make a macOS ARM64 build to support Apple Silicon (Nick Craig-Wood)</li>
+<li>Update go build version to go1.16 and raise minimum go version to
+go1.13 (Nick Craig-Wood)</li>
+<li>Make a macOS ARM64 build to support Apple Silicon (Nick
+Craig-Wood)</li>
 <li>Install macfuse 4.x instead of osxfuse 3.x (Nick Craig-Wood)</li>
-<li>Use <code>GO386=softfloat</code> instead of deprecated <code>GO386=387</code> for 386 builds (Nick Craig-Wood)</li>
+<li>Use <code>GO386=softfloat</code> instead of deprecated
+<code>GO386=387</code> for 386 builds (Nick Craig-Wood)</li>
 <li>Disable IOS builds for the time being (Nick Craig-Wood)</li>
 <li>Androids builds made with up to date NDK (x0b)</li>
-<li>Add an rclone user to the Docker image but don't use it by default (cynthia kwok)</li>
+<li>Add an rclone user to the Docker image but don't use it by default
+(cynthia kwok)</li>
 </ul></li>
-<li>dedupe: Make largest directory primary to minimize data moved (Saksham Khanna)</li>
+<li>dedupe: Make largest directory primary to minimize data moved
+(Saksham Khanna)</li>
 <li>config
 <ul>
 <li>Wrap config library in an interface (Fionera)</li>
 <li>Make config file system pluggable (Nick Craig-Wood)</li>
-<li><code>--config ""</code> or <code>"/notfound"</code> for in memory config only (Nick Craig-Wood)</li>
-<li>Clear fs cache of stale entries when altering config (Nick Craig-Wood)</li>
+<li><code>--config ""</code> or <code>"/notfound"</code> for in memory
+config only (Nick Craig-Wood)</li>
+<li>Clear fs cache of stale entries when altering config (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>copyurl: Add option to print resulting auto-filename (albertony)</li>
-<li>delete: Make <code>--rmdirs</code> obey the filters (Nick Craig-Wood)</li>
-<li>docs - many fixes and reworks from edwardxml, albertony, pvalls, Ivan Andreev, Evan Harris, buengese, Alexey Tabakman</li>
+<li>copyurl: Add option to print resulting auto-filename
+(albertony)</li>
+<li>delete: Make <code>--rmdirs</code> obey the filters (Nick
+Craig-Wood)</li>
+<li>docs - many fixes and reworks from edwardxml, albertony, pvalls,
+Ivan Andreev, Evan Harris, buengese, Alexey Tabakman</li>
 <li>encoder/filename - add SCSU as tables (Klaus Post)</li>
-<li>Add multiple paths support to <code>--compare-dest</code> and <code>--copy-dest</code> flag (K265)</li>
-<li>filter: Make <code>--exclude "dir/"</code> equivalent to <code>--exclude "dir/**"</code> (Nick Craig-Wood)</li>
-<li>fshttp: Add DSCP support with <code>--dscp</code> for QoS with differentiated services (Max Sum)</li>
-<li>lib/cache: Add Delete and DeletePrefix methods (Nick Craig-Wood)</li>
+<li>Add multiple paths support to <code>--compare-dest</code> and
+<code>--copy-dest</code> flag (K265)</li>
+<li>filter: Make <code>--exclude "dir/"</code> equivalent to
+<code>--exclude "dir/**"</code> (Nick Craig-Wood)</li>
+<li>fshttp: Add DSCP support with <code>--dscp</code> for QoS with
+differentiated services (Max Sum)</li>
+<li>lib/cache: Add Delete and DeletePrefix methods (Nick
+Craig-Wood)</li>
 <li>lib/file
 <ul>
-<li>Make pre-allocate detect disk full errors and return them (Nick Craig-Wood)</li>
+<li>Make pre-allocate detect disk full errors and return them (Nick
+Craig-Wood)</li>
 <li>Don't run preallocate concurrently (Nick Craig-Wood)</li>
 <li>Retry preallocate on EINTR (Nick Craig-Wood)</li>
 </ul></li>
-<li>operations: Made copy and sync operations obey a RetryAfterError (Ankur Gupta)</li>
+<li>operations: Made copy and sync operations obey a RetryAfterError
+(Ankur Gupta)</li>
 <li>rc
 <ul>
-<li>Add string alternatives for setting options over the rc (Nick Craig-Wood)</li>
-<li>Add <code>options/local</code> to see the options configured in the context (Nick Craig-Wood)</li>
-<li>Add <code>_config</code> parameter to set global config for just this rc call (Nick Craig-Wood)</li>
-<li>Implement passing filter config with <code>_filter</code> parameter (Nick Craig-Wood)</li>
-<li>Add <code>fscache/clear</code> and <code>fscache/entries</code> to control the fs cache (Nick Craig-Wood)</li>
-<li>Avoid +Inf value for speed in <code>core/stats</code> (albertony)</li>
-<li>Add a full set of stats to <code>core/stats</code> (Nick Craig-Wood)</li>
-<li>Allow <code>fs=</code> params to be a JSON blob (Nick Craig-Wood)</li>
+<li>Add string alternatives for setting options over the rc (Nick
+Craig-Wood)</li>
+<li>Add <code>options/local</code> to see the options configured in the
+context (Nick Craig-Wood)</li>
+<li>Add <code>_config</code> parameter to set global config for just
+this rc call (Nick Craig-Wood)</li>
+<li>Implement passing filter config with <code>_filter</code> parameter
+(Nick Craig-Wood)</li>
+<li>Add <code>fscache/clear</code> and <code>fscache/entries</code> to
+control the fs cache (Nick Craig-Wood)</li>
+<li>Avoid +Inf value for speed in <code>core/stats</code>
+(albertony)</li>
+<li>Add a full set of stats to <code>core/stats</code> (Nick
+Craig-Wood)</li>
+<li>Allow <code>fs=</code> params to be a JSON blob (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>rcd: Added systemd notification during the <code>rclone rcd</code> command. (Naveen Honest Raj)</li>
-<li>rmdirs: Make <code>--rmdirs</code> obey the filters (Nick Craig-Wood)</li>
+<li>rcd: Added systemd notification during the <code>rclone rcd</code>
+command. (Naveen Honest Raj)</li>
+<li>rmdirs: Make <code>--rmdirs</code> obey the filters (Nick
+Craig-Wood)</li>
 <li>version: Show build tags and type of executable (Ivan Andreev)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>install.sh: make it fail on download errors (Ivan Andreev)</li>
-<li>Fix excessive retries missing <code>--max-duration</code> timeout (Nick Craig-Wood)</li>
-<li>Fix crash when <code>--low-level-retries=0</code> (Nick Craig-Wood)</li>
-<li>Fix failed token refresh on mounts created via the rc (Nick Craig-Wood)</li>
-<li>fshttp: Fix bandwidth limiting after bad merge (Nick Craig-Wood)</li>
+<li>Fix excessive retries missing <code>--max-duration</code> timeout
+(Nick Craig-Wood)</li>
+<li>Fix crash when <code>--low-level-retries=0</code> (Nick
+Craig-Wood)</li>
+<li>Fix failed token refresh on mounts created via the rc (Nick
+Craig-Wood)</li>
+<li>fshttp: Fix bandwidth limiting after bad merge (Nick
+Craig-Wood)</li>
 <li>lib/atexit
 <ul>
-<li>Unregister interrupt handler once it has fired so users can interrupt again (Nick Craig-Wood)</li>
+<li>Unregister interrupt handler once it has fired so users can
+interrupt again (Nick Craig-Wood)</li>
 <li>Fix occasional failure to unmount with CTRL-C (Nick Craig-Wood)</li>
-<li>Fix deadlock calling Finalise while Run is running (Nick Craig-Wood)</li>
+<li>Fix deadlock calling Finalise while Run is running (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>lib/rest: Fix multipart uploads not stopping on context cancel (Nick Craig-Wood)</li>
+<li>lib/rest: Fix multipart uploads not stopping on context cancel (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
 <li>Allow mounting to root directory on windows (albertony)</li>
 <li>Improved handling of relative paths on windows (albertony)</li>
-<li>Fix unicode issues with accented characters on macOS (Nick Craig-Wood)</li>
-<li>Docs: document the new FileSecurity option in WinFsp 2021 (albertony)</li>
+<li>Fix unicode issues with accented characters on macOS (Nick
+Craig-Wood)</li>
+<li>Docs: document the new FileSecurity option in WinFsp 2021
+(albertony)</li>
 <li>Docs: add note about volume path syntax on windows (albertony)</li>
-<li>Fix caching of old directories after renaming them (Nick Craig-Wood)</li>
-<li>Update cgofuse to the latest version to bring in macfuse 4 fix (Nick Craig-Wood)</li>
+<li>Fix caching of old directories after renaming them (Nick
+Craig-Wood)</li>
+<li>Update cgofuse to the latest version to bring in macfuse 4 fix (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li><code>--vfs-used-is-size</code> to report used space using recursive scan (tYYGH)</li>
-<li>Don't set modification time if it was already correct (Nick Craig-Wood)</li>
-<li>Fix Create causing windows explorer to truncate files on CTRL-C CTRL-V (Nick Craig-Wood)</li>
-<li>Fix modtimes not updating when writing via cache (Nick Craig-Wood)</li>
-<li>Fix modtimes changing by fractional seconds after upload (Nick Craig-Wood)</li>
-<li>Fix modtime set if <code>--vfs-cache-mode writes</code>/<code>full</code> and no write (Nick Craig-Wood)</li>
-<li>Rename files in cache and cancel uploads on directory rename (Nick Craig-Wood)</li>
-<li>Fix directory renaming by renaming dirs cached in memory (Nick Craig-Wood)</li>
+<li><code>--vfs-used-is-size</code> to report used space using recursive
+scan (tYYGH)</li>
+<li>Don't set modification time if it was already correct (Nick
+Craig-Wood)</li>
+<li>Fix Create causing windows explorer to truncate files on CTRL-C
+CTRL-V (Nick Craig-Wood)</li>
+<li>Fix modtimes not updating when writing via cache (Nick
+Craig-Wood)</li>
+<li>Fix modtimes changing by fractional seconds after upload (Nick
+Craig-Wood)</li>
+<li>Fix modtime set if
+<code>--vfs-cache-mode writes</code>/<code>full</code> and no write
+(Nick Craig-Wood)</li>
+<li>Rename files in cache and cancel uploads on directory rename (Nick
+Craig-Wood)</li>
+<li>Fix directory renaming by renaming dirs cached in memory (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
 <li>Add flag <code>--local-no-preallocate</code> (David Sze)</li>
-<li>Make <code>nounc</code> an advanced option except on Windows (albertony)</li>
+<li>Make <code>nounc</code> an advanced option except on Windows
+(albertony)</li>
 <li>Don't ignore preallocate disk full errors (Nick Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
-<li>Add <code>--fs-cache-expire-duration</code> to control the fs cache (Nick Craig-Wood)</li>
+<li>Add <code>--fs-cache-expire-duration</code> to control the fs cache
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
@@ -40319,7 +56789,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Box
 <ul>
-<li>Fix transfers getting stuck on token expiry after API change (Nick Craig-Wood)</li>
+<li>Fix transfers getting stuck on token expiry after API change (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
@@ -40327,14 +56798,17 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Don't stop server side copy if couldn't read description (Nick Craig-Wood)</li>
-<li>Pass context on to drive SDK - to help with cancellation (Nick Craig-Wood)</li>
+<li>Don't stop server side copy if couldn't read description (Nick
+Craig-Wood)</li>
+<li>Pass context on to drive SDK - to help with cancellation (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
 <li>Add polling for changes support (Robert Thomas)</li>
 <li>Make <code>--timeout 0</code> work properly (Nick Craig-Wood)</li>
-<li>Raise priority of rate limited message to INFO to make it more noticeable (Nick Craig-Wood)</li>
+<li>Raise priority of rate limited message to INFO to make it more
+noticeable (Nick Craig-Wood)</li>
 </ul></li>
 <li>Fichier
 <ul>
@@ -40344,9 +56818,11 @@ $ tree /tmp/c
 <li>FTP
 <ul>
 <li>Implement Shutdown method (Nick Craig-Wood)</li>
-<li>Close idle connections after <code>--ftp-idle-timeout</code> (1m by default) (Nick Craig-Wood)</li>
+<li>Close idle connections after <code>--ftp-idle-timeout</code> (1m by
+default) (Nick Craig-Wood)</li>
 <li>Make <code>--timeout 0</code> work properly (Nick Craig-Wood)</li>
-<li>Add <code>--ftp-close-timeout</code> flag for use with awkward ftp servers (Nick Craig-Wood)</li>
+<li>Add <code>--ftp-close-timeout</code> flag for use with awkward ftp
+servers (Nick Craig-Wood)</li>
 <li>Retry connections and logins on 421 errors (Nick Craig-Wood)</li>
 </ul></li>
 <li>Hdfs
@@ -40359,13 +56835,17 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Fix <code>--s3-profile</code> which wasn't working (Nick Craig-Wood)</li>
+<li>Fix <code>--s3-profile</code> which wasn't working (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Close idle connections after <code>--sftp-idle-timeout</code> (1m by default) (Nick Craig-Wood)</li>
-<li>Fix "file not found" errors for read once servers (Nick Craig-Wood)</li>
-<li>Fix SetModTime stat failed: object not found with <code>--sftp-set-modtime=false</code> (Nick Craig-Wood)</li>
+<li>Close idle connections after <code>--sftp-idle-timeout</code> (1m by
+default) (Nick Craig-Wood)</li>
+<li>Fix "file not found" errors for read once servers (Nick
+Craig-Wood)</li>
+<li>Fix SetModTime stat failed: object not found with
+<code>--sftp-set-modtime=false</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>Swift
 <ul>
@@ -40375,8 +56855,10 @@ $ tree /tmp/c
 <li>Union
 <ul>
 <li>Fix crash when using epff policy (Nick Craig-Wood)</li>
-<li>Fix union attempting to update files on a read only file system (Nick Craig-Wood)</li>
-<li>Refactor to use fspath.SplitFs instead of fs.ParseRemote (Nick Craig-Wood)</li>
+<li>Fix union attempting to update files on a read only file system
+(Nick Craig-Wood)</li>
+<li>Refactor to use fspath.SplitFs instead of fs.ParseRemote (Nick
+Craig-Wood)</li>
 <li>Fix initialisation broken in refactor (Nick Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
@@ -40385,7 +56867,8 @@ $ tree /tmp/c
 <li>Make sharepoint-ntlm docs more consistent (Alex Chen)</li>
 <li>Improve terminology in sharepoint-ntlm docs (Ivan Andreev)</li>
 <li>Disable HTTP/2 for NTLM authentication (georne)</li>
-<li>Fix sharepoint-ntlm error 401 for parallel actions (Ivan Andreev)</li>
+<li>Fix sharepoint-ntlm error 401 for parallel actions (Ivan
+Andreev)</li>
 <li>Check that purged directory really exists (Ivan Andreev)</li>
 </ul></li>
 <li>Yandex
@@ -40394,16 +56877,21 @@ $ tree /tmp/c
 </ul></li>
 <li>Zoho
 <ul>
-<li>Replace client id - you will need to <code>rclone config reconnect</code> after this (buengese)</li>
-<li>Add forgotten setupRegion() to NewFs - this finally fixes regions other than EU (buengese)</li>
+<li>Replace client id - you will need to
+<code>rclone config reconnect</code> after this (buengese)</li>
+<li>Add forgotten setupRegion() to NewFs - this finally fixes regions
+other than EU (buengese)</li>
 </ul></li>
 </ul>
 <h2 id="v1.54.1---2021-03-08">v1.54.1 - 2021-03-08</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.54.0...v1.54.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.54.0...v1.54.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>accounting: Fix --bwlimit when up or down is off (Nick Craig-Wood)</li>
+<li>accounting: Fix --bwlimit when up or down is off (Nick
+Craig-Wood)</li>
 <li>docs
 <ul>
 <li>Fix nesting of brackets and backticks in ftp docs (edwardxml)</li>
@@ -40414,21 +56902,27 @@ $ tree /tmp/c
 <li>Convert bogus example link to code (edwardxml)</li>
 <li>Remove dead link from rc.md (edwardxml)</li>
 </ul></li>
-<li>rc: Sync,copy,move: document createEmptySrcDirs parameter (Nick Craig-Wood)</li>
-<li>lsjson: Fix unterminated JSON in the presence of errors (Nick Craig-Wood)</li>
+<li>rc: Sync,copy,move: document createEmptySrcDirs parameter (Nick
+Craig-Wood)</li>
+<li>lsjson: Fix unterminated JSON in the presence of errors (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Fix mount dropping on macOS by setting --daemon-timeout 10m (Nick Craig-Wood)</li>
+<li>Fix mount dropping on macOS by setting --daemon-timeout 10m (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Document simultaneous usage with the same cache shouldn't be used (Nick Craig-Wood)</li>
+<li>Document simultaneous usage with the same cache shouldn't be used
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
-<li>Automatically raise upload cutoff to avoid spurious error (Nick Craig-Wood)</li>
-<li>Fix failed to create file system with application key limited to a prefix (Nick Craig-Wood)</li>
+<li>Automatically raise upload cutoff to avoid spurious error (Nick
+Craig-Wood)</li>
+<li>Fix failed to create file system with application key limited to a
+prefix (Nick Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
@@ -40436,12 +56930,15 @@ $ tree /tmp/c
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Add scopes to oauth request and optionally "members.read" (Nick Craig-Wood)</li>
+<li>Add scopes to oauth request and optionally "members.read" (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Fix failed to create file system with folder level permissions policy (Nick Craig-Wood)</li>
-<li>Fix Wasabi HEAD requests returning stale data by using only 1 transport (Nick Craig-Wood)</li>
+<li>Fix failed to create file system with folder level permissions
+policy (Nick Craig-Wood)</li>
+<li>Fix Wasabi HEAD requests returning stale data by using only 1
+transport (Nick Craig-Wood)</li>
 <li>Fix shared_credentials_file auth (Dmitry Chepurovskiy)</li>
 <li>Add --s3-no-head to reducing costs docs (Nick Craig-Wood)</li>
 </ul></li>
@@ -40455,14 +56952,17 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.54.0---2021-02-02">v1.54.0 - 2021-02-02</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.53.0...v1.54.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.53.0...v1.54.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
 <li>Compression remote (experimental) (buengese)</li>
 <li>Enterprise File Fabric (Nick Craig-Wood)
 <ul>
-<li>This work was sponsored by <a href="https://storagemadeeasy.com/">Storage Made Easy</a></li>
+<li>This work was sponsored by <a
+href="https://storagemadeeasy.com/">Storage Made Easy</a></li>
 </ul></li>
 <li>HDFS (Hadoop Distributed File System) (Yury Stankevich)</li>
 <li>Zoho workdrive (buengese)</li>
@@ -40473,7 +56973,8 @@ $ tree /tmp/c
 <ul>
 <li>Global config now read from the context</li>
 <li>This will enable passing of global config via the rc</li>
-<li>This work was sponsored by <a href="https://digitalis.io/">Digitalis</a></li>
+<li>This work was sponsored by <a
+href="https://digitalis.io/">Digitalis</a></li>
 </ul></li>
 <li>Add <code>--bwlimit</code> for upload and download (Nick Craig-Wood)
 <ul>
@@ -40481,59 +56982,80 @@ $ tree /tmp/c
 </ul></li>
 <li>Enhance systemd integration (Hekmon)
 <ul>
-<li>log level identification, manual activation with flag, automatic systemd launch detection</li>
-<li>Don't compile systemd log integration for non unix systems (Benjamin Gustin)</li>
+<li>log level identification, manual activation with flag, automatic
+systemd launch detection</li>
+<li>Don't compile systemd log integration for non unix systems (Benjamin
+Gustin)</li>
 </ul></li>
-<li>Add a <code>--download</code> flag to md5sum/sha1sum/hashsum to force rclone to download and hash files locally (lostheli)</li>
-<li>Add <code>--progress-terminal-title</code> to print ETA to terminal title (LaSombra)</li>
-<li>Make backend env vars show in help as the defaults for backend flags (Nick Craig-Wood)</li>
+<li>Add a <code>--download</code> flag to md5sum/sha1sum/hashsum to
+force rclone to download and hash files locally (lostheli)</li>
+<li>Add <code>--progress-terminal-title</code> to print ETA to terminal
+title (LaSombra)</li>
+<li>Make backend env vars show in help as the defaults for backend flags
+(Nick Craig-Wood)</li>
 <li>build
 <ul>
 <li>Raise minimum go version to go1.12 (Nick Craig-Wood)</li>
 </ul></li>
 <li>dedupe
 <ul>
-<li>Add <code>--by-hash</code> to dedupe on content hash not file name (Nick Craig-Wood)</li>
-<li>Add <code>--dedupe-mode list</code> to just list dupes, changing nothing (Nick Craig-Wood)</li>
-<li>Add warning if used on a remote which can't have duplicate names (Nick Craig-Wood)</li>
+<li>Add <code>--by-hash</code> to dedupe on content hash not file name
+(Nick Craig-Wood)</li>
+<li>Add <code>--dedupe-mode list</code> to just list dupes, changing
+nothing (Nick Craig-Wood)</li>
+<li>Add warning if used on a remote which can't have duplicate names
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>fs
 <ul>
 <li>Add Shutdown optional method for backends (Nick Craig-Wood)</li>
-<li>When using <code>--files-from</code> check files concurrently (zhucan)</li>
+<li>When using <code>--files-from</code> check files concurrently
+(zhucan)</li>
 <li>Accumulate stats when using <code>--dry-run</code> (Ingo Weiss)</li>
-<li>Always show stats when using <code>--dry-run</code> or <code>--interactive</code> (Nick Craig-Wood)</li>
-<li>Add support for flag <code>--no-console</code> on windows to hide the console window (albertony)</li>
+<li>Always show stats when using <code>--dry-run</code> or
+<code>--interactive</code> (Nick Craig-Wood)</li>
+<li>Add support for flag <code>--no-console</code> on windows to hide
+the console window (albertony)</li>
 </ul></li>
 <li>genautocomplete: Add support to output to stdout (Ingo)</li>
 <li>ncdu
 <ul>
 <li>Highlight read errors instead of aborting (Claudio Bantaloukas)</li>
 <li>Add sort by average size in directory (Adam Plánský)</li>
-<li>Add toggle option for average s3ize in directory - key 'a' (Adam Plánský)</li>
+<li>Add toggle option for average s3ize in directory - key 'a' (Adam
+Plánský)</li>
 <li>Add empty folder flag into ncdu browser (Adam Plánský)</li>
-<li>Add <code>!</code> (error) and <code>.</code> (unreadable) file flags to go with <code>e</code> (empty) (Nick Craig-Wood)</li>
+<li>Add <code>!</code> (error) and <code>.</code> (unreadable) file
+flags to go with <code>e</code> (empty) (Nick Craig-Wood)</li>
 </ul></li>
-<li>obscure: Make <code>rclone obscure -</code> ignore newline at end of line (Nick Craig-Wood)</li>
+<li>obscure: Make <code>rclone obscure -</code> ignore newline at end of
+line (Nick Craig-Wood)</li>
 <li>operations
 <ul>
-<li>Add logs when need to upload files to set mod times (Nick Craig-Wood)</li>
-<li>Move and copy log name of the destination object in verbose (Adam Plánský)</li>
-<li>Add size if known to skipped items and JSON log (Nick Craig-Wood)</li>
+<li>Add logs when need to upload files to set mod times (Nick
+Craig-Wood)</li>
+<li>Move and copy log name of the destination object in verbose (Adam
+Plánský)</li>
+<li>Add size if known to skipped items and JSON log (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>rc
 <ul>
-<li>Prefer actual listener address if using ":port" or "addr:0" only (Nick Craig-Wood)</li>
+<li>Prefer actual listener address if using ":port" or "addr:0" only
+(Nick Craig-Wood)</li>
 <li>Add listener for finished jobs (Aleksandar Jankovic)</li>
 </ul></li>
 <li>serve ftp: Add options to enable TLS (Deepak Sah)</li>
-<li>serve http/webdav: Redirect requests to the base url without the / (Nick Craig-Wood)</li>
+<li>serve http/webdav: Redirect requests to the base url without the /
+(Nick Craig-Wood)</li>
 <li>serve restic: Implement object cache (Nick Craig-Wood)</li>
 <li>stats: Add counter for deleted directories (Nick Craig-Wood)</li>
-<li>sync: Only print "There was nothing to transfer" if no errors (Nick Craig-Wood)</li>
+<li>sync: Only print "There was nothing to transfer" if no errors (Nick
+Craig-Wood)</li>
 <li>webui
 <ul>
-<li>Prompt user for updating webui if an update is available (Chaitanya Bankanhal)</li>
+<li>Prompt user for updating webui if an update is available (Chaitanya
+Bankanhal)</li>
 <li>Fix plugins initialization (negative0)</li>
 </ul></li>
 </ul></li>
@@ -40541,35 +57063,44 @@ $ tree /tmp/c
 <ul>
 <li>fs
 <ul>
-<li>Fix nil pointer on copy &amp; move operations directly to remote (Anagh Kumar Baranwal)</li>
+<li>Fix nil pointer on copy &amp; move operations directly to remote
+(Anagh Kumar Baranwal)</li>
 <li>Fix parsing of .. when joining remotes (Nick Craig-Wood)</li>
 </ul></li>
-<li>log: Fix enabling systemd logging when using <code>--log-file</code> (Nick Craig-Wood)</li>
+<li>log: Fix enabling systemd logging when using <code>--log-file</code>
+(Nick Craig-Wood)</li>
 <li>check
 <ul>
-<li>Make the error count match up in the log message (Nick Craig-Wood)</li>
+<li>Make the error count match up in the log message (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>move: Fix data loss when source and destination are the same object (Nick Craig-Wood)</li>
+<li>move: Fix data loss when source and destination are the same object
+(Nick Craig-Wood)</li>
 <li>operations
 <ul>
-<li>Fix <code>--cutoff-mode</code> hard not cutting off immediately (Nick Craig-Wood)</li>
+<li>Fix <code>--cutoff-mode</code> hard not cutting off immediately
+(Nick Craig-Wood)</li>
 <li>Fix <code>--immutable</code> error message (Nick Craig-Wood)</li>
 </ul></li>
 <li>sync
 <ul>
-<li>Fix <code>--cutoff-mode</code> soft &amp; cautious so it doesn't end the transfer early (Nick Craig-Wood)</li>
-<li>Fix <code>--immutable</code> errors retrying many times (Nick Craig-Wood)</li>
+<li>Fix <code>--cutoff-mode</code> soft &amp; cautious so it doesn't end
+the transfer early (Nick Craig-Wood)</li>
+<li>Fix <code>--immutable</code> errors retrying many times (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Docs
 <ul>
 <li>Many fixes and a rewrite of the filtering docs (edwardxml)</li>
 <li>Many spelling and grammar fixes (Josh Soref)</li>
-<li>Doc fixes for commands delete, purge, rmdir, rmdirs and mount (albertony)</li>
+<li>Doc fixes for commands delete, purge, rmdir, rmdirs and mount
+(albertony)</li>
 <li>And thanks to these people for many doc fixes too numerous to list
 <ul>
 <li>Ameer Dawood, Antoine GIRARD, Bob Bagwill, Christopher Stewart</li>
-<li>CokeMine, David, Dov Murik, Durval Menezes, Evan Harris, gtorelly</li>
+<li>CokeMine, David, Dov Murik, Durval Menezes, Evan Harris,
+gtorelly</li>
 <li>Ilyess Bachiri, Janne Johansson, Kerry Su, Marcin Zelent,</li>
 <li>Martin Michlmayr, Milly, Sơn Trần-Nguyễn</li>
 </ul></li>
@@ -40579,98 +57110,134 @@ $ tree /tmp/c
 <li>Update systemd status with cache stats (Hekmon)</li>
 <li>Disable bazil/fuse based mount on macOS (Nick Craig-Wood)
 <ul>
-<li>Make <code>rclone mount</code> actually run <code>rclone cmount</code> under macOS (Nick Craig-Wood)</li>
+<li>Make <code>rclone mount</code> actually run
+<code>rclone cmount</code> under macOS (Nick Craig-Wood)</li>
 </ul></li>
-<li>Implement mknod to make NFS file creation work (Nick Craig-Wood)</li>
+<li>Implement mknod to make NFS file creation work (Nick
+Craig-Wood)</li>
 <li>Make sure we don't call umount more than once (Nick Craig-Wood)</li>
-<li>More user friendly mounting as network drive on windows (albertony)</li>
-<li>Detect if uid or gid are set in same option string: -o uid=123,gid=456 (albertony)</li>
-<li>Don't attempt to unmount if fs has been destroyed already (Nick Craig-Wood)</li>
+<li>More user friendly mounting as network drive on windows
+(albertony)</li>
+<li>Detect if uid or gid are set in same option string: -o
+uid=123,gid=456 (albertony)</li>
+<li>Don't attempt to unmount if fs has been destroyed already (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Fix virtual entries causing deleted files to still appear (Nick Craig-Wood)</li>
-<li>Fix "file already exists" error for stale cache files (Nick Craig-Wood)</li>
-<li>Fix file leaks with <code>--vfs-cache-mode</code> full and <code>--buffer-size 0</code> (Nick Craig-Wood)</li>
-<li>Fix invalid cache path on windows when using :backend: as remote (albertony)</li>
+<li>Fix virtual entries causing deleted files to still appear (Nick
+Craig-Wood)</li>
+<li>Fix "file already exists" error for stale cache files (Nick
+Craig-Wood)</li>
+<li>Fix file leaks with <code>--vfs-cache-mode</code> full and
+<code>--buffer-size 0</code> (Nick Craig-Wood)</li>
+<li>Fix invalid cache path on windows when using :backend: as remote
+(albertony)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Continue listing files/folders when a circular symlink is detected (Manish Gupta)</li>
-<li>New flag <code>--local-zero-size-links</code> to fix sync on some virtual filesystems (Riccardo Iaconelli)</li>
+<li>Continue listing files/folders when a circular symlink is detected
+(Manish Gupta)</li>
+<li>New flag <code>--local-zero-size-links</code> to fix sync on some
+virtual filesystems (Riccardo Iaconelli)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
 <li>Add support for service principals (James Lim)</li>
 <li>Add support for managed identities (Brad Ackerman)</li>
 <li>Add examples for access tier (Bob Pusateri)</li>
-<li>Utilize the streaming capabilities from the SDK for multipart uploads (Denis Neuling)</li>
+<li>Utilize the streaming capabilities from the SDK for multipart
+uploads (Denis Neuling)</li>
 <li>Fix setting of mime types (Nick Craig-Wood)</li>
-<li>Fix crash when listing outside a SAS URL's root (Nick Craig-Wood)</li>
-<li>Delete archive tier blobs before update if <code>--azureblob-archive-tier-delete</code> (Nick Craig-Wood)</li>
+<li>Fix crash when listing outside a SAS URL's root (Nick
+Craig-Wood)</li>
+<li>Delete archive tier blobs before update if
+<code>--azureblob-archive-tier-delete</code> (Nick Craig-Wood)</li>
 <li>Fix crash on startup (Nick Craig-Wood)</li>
-<li>Fix memory usage by upgrading the SDK to v0.13.0 and implementing a TransferManager (Nick Craig-Wood)</li>
+<li>Fix memory usage by upgrading the SDK to v0.13.0 and implementing a
+TransferManager (Nick Craig-Wood)</li>
 <li>Require go1.14+ to compile due to SDK changes (Nick Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
 <li>Make NewObject use less expensive API calls (Nick Craig-Wood)
 <ul>
-<li>This will improve <code>--files-from</code> and <code>restic serve</code> in particular</li>
+<li>This will improve <code>--files-from</code> and
+<code>restic serve</code> in particular</li>
 </ul></li>
 <li>Fixed crash on an empty file name (lluuaapp)</li>
 </ul></li>
 <li>Box
 <ul>
 <li>Fix NewObject for files that differ in case (Nick Craig-Wood)</li>
-<li>Fix finding directories in a case insensitive way (Nick Craig-Wood)</li>
+<li>Fix finding directories in a case insensitive way (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
 <li>Skip long local hashing, hash in-transit (fixes) (Ivan Andreev)</li>
-<li>Set Features ReadMimeType to false as Object.MimeType not supported (Nick Craig-Wood)</li>
-<li>Fix case-insensitive NewObject, test metadata detection (Ivan Andreev)</li>
+<li>Set Features ReadMimeType to false as Object.MimeType not supported
+(Nick Craig-Wood)</li>
+<li>Fix case-insensitive NewObject, test metadata detection (Ivan
+Andreev)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Implement <code>rclone backend copyid</code> command for copying files by ID (Nick Craig-Wood)</li>
-<li>Added flag <code>--drive-stop-on-download-limit</code> to stop transfers when the download limit is exceeded (Anagh Kumar Baranwal)</li>
+<li>Implement <code>rclone backend copyid</code> command for copying
+files by ID (Nick Craig-Wood)</li>
+<li>Added flag <code>--drive-stop-on-download-limit</code> to stop
+transfers when the download limit is exceeded (Anagh Kumar
+Baranwal)</li>
 <li>Implement CleanUp workaround for team drives (buengese)</li>
-<li>Allow shortcut resolution and creation to be retried (Nick Craig-Wood)</li>
-<li>Log that emptying the trash can take some time (Nick Craig-Wood)</li>
-<li>Add xdg office icons to xdg desktop files (Pau Rodriguez-Estivill)</li>
+<li>Allow shortcut resolution and creation to be retried (Nick
+Craig-Wood)</li>
+<li>Log that emptying the trash can take some time (Nick
+Craig-Wood)</li>
+<li>Add xdg office icons to xdg desktop files (Pau
+Rodriguez-Estivill)</li>
 </ul></li>
 <li>Dropbox
 <ul>
 <li>Add support for viewing shared files and folders (buengese)</li>
 <li>Enable short lived access tokens (Nick Craig-Wood)</li>
-<li>Implement IDer on Objects so <code>rclone lsf</code> etc can read the IDs (buengese)</li>
-<li>Set Features ReadMimeType to false as Object.MimeType not supported (Nick Craig-Wood)</li>
-<li>Make malformed_path errors from too long files not retriable (Nick Craig-Wood)</li>
-<li>Test file name length before upload to fix upload loop (Nick Craig-Wood)</li>
+<li>Implement IDer on Objects so <code>rclone lsf</code> etc can read
+the IDs (buengese)</li>
+<li>Set Features ReadMimeType to false as Object.MimeType not supported
+(Nick Craig-Wood)</li>
+<li>Make malformed_path errors from too long files not retriable (Nick
+Craig-Wood)</li>
+<li>Test file name length before upload to fix upload loop (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Fichier
 <ul>
-<li>Set Features ReadMimeType to true as Object.MimeType is supported (Nick Craig-Wood)</li>
+<li>Set Features ReadMimeType to true as Object.MimeType is supported
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Add <code>--ftp-disable-msld</code> option to ignore MLSD for really old servers (Nick Craig-Wood)</li>
+<li>Add <code>--ftp-disable-msld</code> option to ignore MLSD for really
+old servers (Nick Craig-Wood)</li>
 <li>Make <code>--tpslimit apply</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
 <li>Storage class object header support (Laurens Janssen)</li>
-<li>Fix anonymous client to use rclone's HTTP client (Nick Craig-Wood)</li>
-<li>Fix <code>Entry doesn't belong in directory "" (same as directory) - ignoring</code> (Nick Craig-Wood)</li>
+<li>Fix anonymous client to use rclone's HTTP client (Nick
+Craig-Wood)</li>
+<li>Fix
+<code>Entry doesn't belong in directory "" (same as directory) - ignoring</code>
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Googlephotos
 <ul>
-<li>New flag <code>--gphotos-include-archived</code> to show archived photos as well (Nicolas Rueff)</li>
+<li>New flag <code>--gphotos-include-archived</code> to show archived
+photos as well (Nicolas Rueff)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
-<li>Don't erroneously report support for writing mime types (buengese)</li>
+<li>Don't erroneously report support for writing mime types
+(buengese)</li>
 <li>Add support for Telia Cloud (Patrik Nordlén)</li>
 </ul></li>
 <li>Mailru
@@ -40678,7 +57245,8 @@ $ tree /tmp/c
 <li>Accept special folders eg camera-upload (Ivan Andreev)</li>
 <li>Avoid prehashing of large local files (Ivan Andreev)</li>
 <li>Fix uploads after recent changes on server (Ivan Andreev)</li>
-<li>Fix range requests after June 2020 changes on server (Ivan Andreev)</li>
+<li>Fix range requests after June 2020 changes on server (Ivan
+Andreev)</li>
 <li>Fix invalid timestamp on corrupted files (fixes) (Ivan Andreev)</li>
 <li>Remove deprecated protocol quirks (Ivan Andreev)</li>
 </ul></li>
@@ -40688,18 +57256,24 @@ $ tree /tmp/c
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Add support for China region operated by 21vianet and other regional suppliers (NyaMisty)</li>
+<li>Add support for China region operated by 21vianet and other regional
+suppliers (NyaMisty)</li>
 <li>Warn on gateway timeout errors (Nick Craig-Wood)</li>
-<li>Fall back to normal copy if server-side copy unavailable (Alex Chen)</li>
-<li>Fix server-side copy completely disabled on OneDrive for Business (Cnly)</li>
-<li>(business only) workaround to replace existing file on server-side copy (Alex Chen)</li>
-<li>Enhance link creation with expiry, scope, type and password (Nick Craig-Wood)</li>
+<li>Fall back to normal copy if server-side copy unavailable (Alex
+Chen)</li>
+<li>Fix server-side copy completely disabled on OneDrive for Business
+(Cnly)</li>
+<li>(business only) workaround to replace existing file on server-side
+copy (Alex Chen)</li>
+<li>Enhance link creation with expiry, scope, type and password (Nick
+Craig-Wood)</li>
 <li>Remove % and # from the set of encoded characters (Alex Chen)</li>
 <li>Support addressing site by server-relative URL (kice)</li>
 </ul></li>
 <li>Opendrive
 <ul>
-<li>Fix finding directories in a case insensitive way (Nick Craig-Wood)</li>
+<li>Fix finding directories in a case insensitive way (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Pcloud
 <ul>
@@ -40707,7 +57281,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Premiumizeme
 <ul>
-<li>Fix finding directories in a case insensitive way (Nick Craig-Wood)</li>
+<li>Fix finding directories in a case insensitive way (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Qingstor
 <ul>
@@ -40716,38 +57291,50 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Added <code>--s3-disable-http2</code> to disable http/2 (Anagh Kumar Baranwal)</li>
+<li>Added <code>--s3-disable-http2</code> to disable http/2 (Anagh Kumar
+Baranwal)</li>
 <li>Complete SSE-C implementation (Nick Craig-Wood)
 <ul>
-<li>Fix hashes on small files with AWS:KMS and SSE-C (Nick Craig-Wood)</li>
-<li>Add MD5 metadata to objects uploaded with SSE-AWS/SSE-C (Nick Craig-Wood)</li>
+<li>Fix hashes on small files with AWS:KMS and SSE-C (Nick
+Craig-Wood)</li>
+<li>Add MD5 metadata to objects uploaded with SSE-AWS/SSE-C (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>Add <code>--s3-no-head parameter</code> to minimise transactions on upload (Nick Craig-Wood)</li>
+<li>Add <code>--s3-no-head parameter</code> to minimise transactions on
+upload (Nick Craig-Wood)</li>
 <li>Update docs with a Reducing Costs section (Nick Craig-Wood)</li>
-<li>Added error handling for error code 429 indicating too many requests (Anagh Kumar Baranwal)</li>
+<li>Added error handling for error code 429 indicating too many requests
+(Anagh Kumar Baranwal)</li>
 <li>Add requester pays option (kelv)</li>
-<li>Fix copy multipart with v2 auth failing with 'SignatureDoesNotMatch' (Louis Koo)</li>
+<li>Fix copy multipart with v2 auth failing with 'SignatureDoesNotMatch'
+(Louis Koo)</li>
 </ul></li>
 <li>SFTP
 <ul>
 <li>Allow cert based auth via optional pubkey (Stephen Harris)</li>
-<li>Allow user to optionally check server hosts key to add security (Stephen Harris)</li>
-<li>Defer asking for user passwords until the SSH connection succeeds (Stephen Harris)</li>
+<li>Allow user to optionally check server hosts key to add security
+(Stephen Harris)</li>
+<li>Defer asking for user passwords until the SSH connection succeeds
+(Stephen Harris)</li>
 <li>Remember entered password in AskPass mode (Stephen Harris)</li>
 <li>Implement Shutdown method (Nick Craig-Wood)</li>
 <li>Implement keyboard interactive authentication (Nick Craig-Wood)</li>
 <li>Make <code>--tpslimit</code> apply (Nick Craig-Wood)</li>
-<li>Implement <code>--sftp-use-fstat</code> for unusual SFTP servers (Nick Craig-Wood)</li>
+<li>Implement <code>--sftp-use-fstat</code> for unusual SFTP servers
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Sugarsync
 <ul>
 <li>Fix NewObject for files that differ in case (Nick Craig-Wood)</li>
-<li>Fix finding directories in a case insensitive way (Nick Craig-Wood)</li>
+<li>Fix finding directories in a case insensitive way (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Fix deletion of parts of Static Large Object (SLO) (Nguyễn Hữu Luân)</li>
-<li>Ensure partially uploaded large files are uploaded unless <code>--swift-leave-parts-on-error</code> (Nguyễn Hữu Luân)</li>
+<li>Fix deletion of parts of Static Large Object (SLO) (Nguyễn Hữu
+Luân)</li>
+<li>Ensure partially uploaded large files are uploaded unless
+<code>--swift-leave-parts-on-error</code> (Nguyễn Hữu Luân)</li>
 </ul></li>
 <li>Tardigrade
 <ul>
@@ -40755,15 +57342,19 @@ $ tree /tmp/c
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Updated docs to show streaming to nextcloud is working (Durval Menezes)</li>
+<li>Updated docs to show streaming to nextcloud is working (Durval
+Menezes)</li>
 </ul></li>
 <li>Yandex
 <ul>
-<li>Set Features WriteMimeType to false as Yandex ignores mime types (Nick Craig-Wood)</li>
+<li>Set Features WriteMimeType to false as Yandex ignores mime types
+(Nick Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.53.4---2021-01-20">v1.53.4 - 2021-01-20</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.53.3...v1.53.4">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.53.3...v1.53.4">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
@@ -40773,32 +57364,44 @@ $ tree /tmp/c
 <li>Stop tagged releases making a current beta (Nick Craig-Wood)</li>
 <li>Upgrade docker buildx action (Matteo Pietro Dazzi)</li>
 <li>Add -buildmode to cross-compile.go (Nick Craig-Wood)</li>
-<li>Fix docker build by upgrading ilteoood/docker_buildx (Nick Craig-Wood)</li>
-<li>Revert GitHub actions brew fix since this is now fixed (Nick Craig-Wood)</li>
-<li>Fix brew install --cask syntax for macOS build (Nick Craig-Wood)</li>
-<li>Update nfpm syntax to fix build of .deb/.rpm packages (Nick Craig-Wood)</li>
+<li>Fix docker build by upgrading ilteoood/docker_buildx (Nick
+Craig-Wood)</li>
+<li>Revert GitHub actions brew fix since this is now fixed (Nick
+Craig-Wood)</li>
+<li>Fix brew install --cask syntax for macOS build (Nick
+Craig-Wood)</li>
+<li>Update nfpm syntax to fix build of .deb/.rpm packages (Nick
+Craig-Wood)</li>
 <li>Fix for Windows build errors (Ivan Andreev)</li>
 </ul></li>
 <li>fs: Parseduration: fixed tests to use UTC time (Ankur Gupta)</li>
-<li>fshttp: Prevent overlap of HTTP headers in logs (Nathan Collins)</li>
+<li>fshttp: Prevent overlap of HTTP headers in logs (Nathan
+Collins)</li>
 <li>rc
 <ul>
 <li>Fix core/command giving 500 internal error (Nick Craig-Wood)</li>
 <li>Add Copy method to rc.Params (Nick Craig-Wood)</li>
-<li>Fix 500 error when marshalling errors from core/command (Nick Craig-Wood)</li>
-<li>plugins: Create plugins files only if webui is enabled. (negative0)</li>
+<li>Fix 500 error when marshalling errors from core/command (Nick
+Craig-Wood)</li>
+<li>plugins: Create plugins files only if webui is enabled.
+(negative0)</li>
 </ul></li>
-<li>serve http: Fix serving files of unknown length (Nick Craig-Wood)</li>
-<li>serve sftp: Fix authentication on one connection blocking others (Nick Craig-Wood)</li>
+<li>serve http: Fix serving files of unknown length (Nick
+Craig-Wood)</li>
+<li>serve sftp: Fix authentication on one connection blocking others
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Add optional <code>brew</code> tag to throw an error when using mount in the binaries installed via Homebrew (Anagh Kumar Baranwal)</li>
-<li>Add "." and ".." to directories to match cmount and expectations (Nick Craig-Wood)</li>
+<li>Add optional <code>brew</code> tag to throw an error when using
+mount in the binaries installed via Homebrew (Anagh Kumar Baranwal)</li>
+<li>Add "." and ".." to directories to match cmount and expectations
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Make cache dir absolute before using it to fix path too long errors (Nick Craig-Wood)</li>
+<li>Make cache dir absolute before using it to fix path too long errors
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
@@ -40811,7 +57414,8 @@ $ tree /tmp/c
 <li>Jottacloud
 <ul>
 <li>Fix token renewer to fix long uploads (Nick Craig-Wood)</li>
-<li>Fix token refresh failed: is not a regular file error (Nick Craig-Wood)</li>
+<li>Fix token refresh failed: is not a regular file error (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Pcloud
 <ul>
@@ -40819,7 +57423,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Sharefile
 <ul>
-<li>Undo Fix backend due to API swapping integers for strings (Nick Craig-Wood)</li>
+<li>Undo Fix backend due to API swapping integers for strings (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
@@ -40828,16 +57433,22 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.53.3---2020-11-19">v1.53.3 - 2020-11-19</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.53.2...v1.53.3">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.53.2...v1.53.3">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>random: Fix incorrect use of math/rand instead of crypto/rand CVE-2020-28924 (Nick Craig-Wood)
+<li>random: Fix incorrect use of math/rand instead of crypto/rand
+CVE-2020-28924 (Nick Craig-Wood)
 <ul>
-<li>Passwords you have generated with <code>rclone config</code> may be insecure</li>
-<li>See <a href="https://github.com/rclone/rclone/issues/4783">issue #4783</a> for more details and a checking tool</li>
+<li>Passwords you have generated with <code>rclone config</code> may be
+insecure</li>
+<li>See <a href="https://github.com/rclone/rclone/issues/4783">issue
+#4783</a> for more details and a checking tool</li>
 </ul></li>
-<li>random: Seed math/rand in one place with crypto strong seed (Nick Craig-Wood)</li>
+<li>random: Seed math/rand in one place with crypto strong seed (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
@@ -40845,28 +57456,35 @@ $ tree /tmp/c
 </ul></li>
 <li>Sharefile
 <ul>
-<li>Fix backend due to API swapping integers for strings (Nick Craig-Wood)</li>
+<li>Fix backend due to API swapping integers for strings (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.53.2---2020-10-26">v1.53.2 - 2020-10-26</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.53.1...v1.53.2">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.53.1...v1.53.2">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
 <li>accounting
 <ul>
-<li>Fix incorrect speed and transferTime in core/stats (Nick Craig-Wood)</li>
-<li>Stabilize display order of transfers on Windows (Nick Craig-Wood)</li>
+<li>Fix incorrect speed and transferTime in core/stats (Nick
+Craig-Wood)</li>
+<li>Stabilize display order of transfers on Windows (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>operations
 <ul>
 <li>Fix use of --suffix without --backup-dir (Nick Craig-Wood)</li>
-<li>Fix spurious "--checksum is in use but the source and destination have no hashes in common" (Nick Craig-Wood)</li>
+<li>Fix spurious "--checksum is in use but the source and destination
+have no hashes in common" (Nick Craig-Wood)</li>
 </ul></li>
 <li>build
 <ul>
 <li>Work around GitHub actions brew problem (Nick Craig-Wood)</li>
-<li>Stop using set-env and set-path in the GitHub actions (Nick Craig-Wood)</li>
+<li>Stop using set-env and set-path in the GitHub actions (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Mount
@@ -40875,21 +57493,26 @@ $ tree /tmp/c
 </ul></li>
 <li>VFS
 <ul>
-<li>Detect and recover from a file being removed externally from the cache (Nick Craig-Wood)</li>
+<li>Detect and recover from a file being removed externally from the
+cache (Nick Craig-Wood)</li>
 <li>Fix a deadlock vulnerability in downloaders.Close (Leo Luan)</li>
 <li>Fix a race condition in retryFailedResets (Leo Luan)</li>
-<li>Fix missed concurrency control between some item operations and reset (Leo Luan)</li>
+<li>Fix missed concurrency control between some item operations and
+reset (Leo Luan)</li>
 <li>Add exponential backoff during ENOSPC retries (Leo Luan)</li>
 <li>Add a missed update of used cache space (Leo Luan)</li>
-<li>Fix --no-modtime to not attempt to set modtimes (as documented) (Nick Craig-Wood)</li>
+<li>Fix --no-modtime to not attempt to set modtimes (as documented)
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix sizes and syncing with --links option on Windows (Nick Craig-Wood)</li>
+<li>Fix sizes and syncing with --links option on Windows (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Chunker
 <ul>
-<li>Disable ListR to fix missing files on GDrive (workaround) (Ivan Andreev)</li>
+<li>Disable ListR to fix missing files on GDrive (workaround) (Ivan
+Andreev)</li>
 <li>Fix upload over crypt (Ivan Andreev)</li>
 </ul></li>
 <li>Fichier
@@ -40898,9 +57521,11 @@ $ tree /tmp/c
 </ul></li>
 <li>Jottacloud
 <ul>
-<li>Remove clientSecret from config when upgrading to token based authentication (buengese)</li>
+<li>Remove clientSecret from config when upgrading to token based
+authentication (buengese)</li>
 <li>Avoid double url escaping of device/mountpoint (albertony)</li>
-<li>Remove DirMove workaround as it's not required anymore - also (buengese)</li>
+<li>Remove DirMove workaround as it's not required anymore - also
+(buengese)</li>
 </ul></li>
 <li>Mailru
 <ul>
@@ -40918,7 +57543,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Seafile
 <ul>
-<li>Fix accessing libraries &gt; 2GB on 32 bit systems (Muffin King)</li>
+<li>Fix accessing libraries &gt; 2GB on 32 bit systems (Muffin
+King)</li>
 </ul></li>
 <li>SFTP
 <ul>
@@ -40930,11 +57556,14 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.53.1---2020-09-13">v1.53.1 - 2020-09-13</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.53.0...v1.53.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.53.0...v1.53.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>accounting: Remove new line from end of --stats-one-line display (Nick Craig-Wood)</li>
+<li>accounting: Remove new line from end of --stats-one-line display
+(Nick Craig-Wood)</li>
 <li>check
 <ul>
 <li>Add back missing --download flag (Nick Craig-Wood)</li>
@@ -40945,25 +57574,32 @@ $ tree /tmp/c
 <li>Note --log-file does append (Nick Craig-Wood)</li>
 <li>Add full stops for consistency in rclone --help (edwardxml)</li>
 <li>Add Tencent COS to s3 provider list (wjielai)</li>
-<li>Updated mount command to reflect that it requires Go 1.13 or newer (Evan Harris)</li>
-<li>jottacloud: Mention that uploads from local disk will not need to cache files to disk for md5 calculation (albertony)</li>
+<li>Updated mount command to reflect that it requires Go 1.13 or newer
+(Evan Harris)</li>
+<li>jottacloud: Mention that uploads from local disk will not need to
+cache files to disk for md5 calculation (albertony)</li>
 <li>Fix formatting of rc docs page (Nick Craig-Wood)</li>
 </ul></li>
 <li>build
 <ul>
-<li>Include vendor tar ball in release and fix startdev (Nick Craig-Wood)</li>
-<li>Fix "Illegal instruction" error for ARMv6 builds (Nick Craig-Wood)</li>
+<li>Include vendor tar ball in release and fix startdev (Nick
+Craig-Wood)</li>
+<li>Fix "Illegal instruction" error for ARMv6 builds (Nick
+Craig-Wood)</li>
 <li>Fix architecture name in ARMv7 build (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Fix spurious error "vfs cache: failed to _ensure cache EOF" (Nick Craig-Wood)</li>
-<li>Log an ERROR if we fail to set the file to be sparse (Nick Craig-Wood)</li>
+<li>Fix spurious error "vfs cache: failed to _ensure cache EOF" (Nick
+Craig-Wood)</li>
+<li>Log an ERROR if we fail to set the file to be sparse (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Log an ERROR if we fail to set the file to be sparse (Nick Craig-Wood)</li>
+<li>Log an ERROR if we fail to set the file to be sparse (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
@@ -40975,186 +57611,274 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.53.0---2020-09-02">v1.53.0 - 2020-09-02</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.52.0...v1.53.0">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.52.0...v1.53.0">See
+commits</a></p>
 <ul>
 <li>New Features
 <ul>
-<li>The <a href="https://rclone.org/commands/rclone_mount/#vfs-virtual-file-system">VFS layer</a> was heavily reworked for this release - see below for more details</li>
-<li>Interactive mode <a href="https://rclone.org/docs/#interactive">-i/--interactive</a> for destructive operations (fishbullet)</li>
-<li>Add <a href="https://rclone.org/docs/#bwlimit-file-bandwidth-spec">--bwlimit-file</a> flag to limit speeds of individual file transfers (Nick Craig-Wood)</li>
-<li>Transfers are sorted by start time in the stats and progress output (Max Sum)</li>
-<li>Make sure backends expand <code>~</code> and environment vars in file names they use (Nick Craig-Wood)</li>
-<li>Add <a href="https://rclone.org/docs/#refresh-times">--refresh-times</a> flag to set modtimes on hashless backends (Nick Craig-Wood)</li>
+<li>The <a
+href="https://rclone.org/commands/rclone_mount/#vfs-virtual-file-system">VFS
+layer</a> was heavily reworked for this release - see below for more
+details</li>
+<li>Interactive mode <a
+href="https://rclone.org/docs/#interactive">-i/--interactive</a> for
+destructive operations (fishbullet)</li>
+<li>Add <a
+href="https://rclone.org/docs/#bwlimit-file-bandwidth-spec">--bwlimit-file</a>
+flag to limit speeds of individual file transfers (Nick Craig-Wood)</li>
+<li>Transfers are sorted by start time in the stats and progress output
+(Max Sum)</li>
+<li>Make sure backends expand <code>~</code> and environment vars in
+file names they use (Nick Craig-Wood)</li>
+<li>Add <a
+href="https://rclone.org/docs/#refresh-times">--refresh-times</a> flag
+to set modtimes on hashless backends (Nick Craig-Wood)</li>
 <li>build
 <ul>
-<li>Remove vendor directory in favour of Go modules (Nick Craig-Wood)</li>
+<li>Remove vendor directory in favour of Go modules (Nick
+Craig-Wood)</li>
 <li>Build with go1.15.x by default (Nick Craig-Wood)</li>
-<li>Drop macOS 386 build as it is no longer supported by go1.15 (Nick Craig-Wood)</li>
+<li>Drop macOS 386 build as it is no longer supported by go1.15 (Nick
+Craig-Wood)</li>
 <li>Add ARMv7 to the supported builds (Nick Craig-Wood)</li>
 <li>Enable <code>rclone cmount</code> on macOS (Nick Craig-Wood)</li>
 <li>Make rclone build with gccgo (Nick Craig-Wood)</li>
 <li>Make rclone build with wasm (Nick Craig-Wood)</li>
 <li>Change beta numbering to be semver compatible (Nick Craig-Wood)</li>
 <li>Add file properties and icon to Windows executable (albertony)</li>
-<li>Add experimental interface for integrating rclone into browsers (Nick Craig-Wood)</li>
+<li>Add experimental interface for integrating rclone into browsers
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>lib: Add file name compression (Klaus Post)</li>
 <li>rc
 <ul>
-<li>Allow installation and use of plugins and test plugins with rclone-webui (Chaitanya Bankanhal)</li>
-<li>Add reverse proxy pluginsHandler for serving plugins (Chaitanya Bankanhal)</li>
-<li>Add <code>mount/listmounts</code> option for listing current mounts (Chaitanya Bankanhal)</li>
-<li>Add <code>operations/uploadfile</code> to upload a file through rc using encoding multipart/form-data (Chaitanya Bankanhal)</li>
-<li>Add <code>core/command</code> to execute rclone terminal commands. (Chaitanya Bankanhal)</li>
+<li>Allow installation and use of plugins and test plugins with
+rclone-webui (Chaitanya Bankanhal)</li>
+<li>Add reverse proxy pluginsHandler for serving plugins (Chaitanya
+Bankanhal)</li>
+<li>Add <code>mount/listmounts</code> option for listing current mounts
+(Chaitanya Bankanhal)</li>
+<li>Add <code>operations/uploadfile</code> to upload a file through rc
+using encoding multipart/form-data (Chaitanya Bankanhal)</li>
+<li>Add <code>core/command</code> to execute rclone terminal commands.
+(Chaitanya Bankanhal)</li>
 </ul></li>
 <li><code>rclone check</code>
 <ul>
-<li>Add reporting of filenames for same/missing/changed (Nick Craig-Wood)</li>
-<li>Make check command obey <code>--dry-run</code>/<code>-i</code>/<code>--interactive</code> (Nick Craig-Wood)</li>
-<li>Make check do <code>--checkers</code> files concurrently (Nick Craig-Wood)</li>
-<li>Retry downloads if they fail when using the <code>--download</code> flag (Nick Craig-Wood)</li>
+<li>Add reporting of filenames for same/missing/changed (Nick
+Craig-Wood)</li>
+<li>Make check command obey
+<code>--dry-run</code>/<code>-i</code>/<code>--interactive</code> (Nick
+Craig-Wood)</li>
+<li>Make check do <code>--checkers</code> files concurrently (Nick
+Craig-Wood)</li>
+<li>Retry downloads if they fail when using the <code>--download</code>
+flag (Nick Craig-Wood)</li>
 <li>Make it show stats by default (Nick Craig-Wood)</li>
 </ul></li>
-<li><code>rclone obscure</code>: Allow obscure command to accept password on STDIN (David Ibarra)</li>
+<li><code>rclone obscure</code>: Allow obscure command to accept
+password on STDIN (David Ibarra)</li>
 <li><code>rclone config</code>
 <ul>
-<li>Set RCLONE_CONFIG_DIR for use in config files and subprocesses (Nick Craig-Wood)</li>
+<li>Set RCLONE_CONFIG_DIR for use in config files and subprocesses (Nick
+Craig-Wood)</li>
 <li>Reject remote names starting with a dash. (jtagcat)</li>
 </ul></li>
-<li><code>rclone cryptcheck</code>: Add reporting of filenames for same/missing/changed (Nick Craig-Wood)</li>
-<li><code>rclone dedupe</code>: Make it obey the <code>--size-only</code> flag for duplicate detection (Nick Craig-Wood)</li>
-<li><code>rclone link</code>: Add <code>--expire</code> and <code>--unlink</code> flags (Roman Kredentser)</li>
-<li><code>rclone mkdir</code>: Warn when using mkdir on remotes which can't have empty directories (Nick Craig-Wood)</li>
-<li><code>rclone rc</code>: Allow JSON parameters to simplify command line usage (Nick Craig-Wood)</li>
+<li><code>rclone cryptcheck</code>: Add reporting of filenames for
+same/missing/changed (Nick Craig-Wood)</li>
+<li><code>rclone dedupe</code>: Make it obey the
+<code>--size-only</code> flag for duplicate detection (Nick
+Craig-Wood)</li>
+<li><code>rclone link</code>: Add <code>--expire</code> and
+<code>--unlink</code> flags (Roman Kredentser)</li>
+<li><code>rclone mkdir</code>: Warn when using mkdir on remotes which
+can't have empty directories (Nick Craig-Wood)</li>
+<li><code>rclone rc</code>: Allow JSON parameters to simplify command
+line usage (Nick Craig-Wood)</li>
 <li><code>rclone serve ftp</code>
 <ul>
-<li>Don't compile on &lt; go1.13 after dependency update (Nick Craig-Wood)</li>
+<li>Don't compile on &lt; go1.13 after dependency update (Nick
+Craig-Wood)</li>
 <li>Add error message if auth proxy fails (Nick Craig-Wood)</li>
-<li>Use refactored goftp.io/server library for binary shrink (Nick Craig-Wood)</li>
+<li>Use refactored goftp.io/server library for binary shrink (Nick
+Craig-Wood)</li>
 </ul></li>
-<li><code>rclone serve restic</code>: Expose interfaces so that rclone can be used as a library from within restic (Jack)</li>
-<li><code>rclone sync</code>: Add <code>--track-renames-strategy leaf</code> (Nick Craig-Wood)</li>
-<li><code>rclone touch</code>: Add ability to set nanosecond resolution times (Nick Craig-Wood)</li>
-<li><code>rclone tree</code>: Remove <code>-i</code> shorthand for <code>--noindent</code> as it conflicts with <code>-i</code>/<code>--interactive</code> (Nick Craig-Wood)</li>
+<li><code>rclone serve restic</code>: Expose interfaces so that rclone
+can be used as a library from within restic (Jack)</li>
+<li><code>rclone sync</code>: Add
+<code>--track-renames-strategy leaf</code> (Nick Craig-Wood)</li>
+<li><code>rclone touch</code>: Add ability to set nanosecond resolution
+times (Nick Craig-Wood)</li>
+<li><code>rclone tree</code>: Remove <code>-i</code> shorthand for
+<code>--noindent</code> as it conflicts with
+<code>-i</code>/<code>--interactive</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>accounting
 <ul>
-<li>Fix documentation for <code>speed</code>/<code>speedAvg</code> (Nick Craig-Wood)</li>
-<li>Fix elapsed time not show actual time since beginning (Chaitanya Bankanhal)</li>
+<li>Fix documentation for <code>speed</code>/<code>speedAvg</code> (Nick
+Craig-Wood)</li>
+<li>Fix elapsed time not show actual time since beginning (Chaitanya
+Bankanhal)</li>
 <li>Fix deadlock in stats printing (Nick Craig-Wood)</li>
 </ul></li>
 <li>build
 <ul>
 <li>Fix file handle leak in GitHub release tool (Garrett Squire)</li>
 </ul></li>
-<li><code>rclone check</code>: Fix successful retries with <code>--download</code> counting errors (Nick Craig-Wood)</li>
-<li><code>rclone dedupe</code>: Fix logging to be easier to understand (Nick Craig-Wood)</li>
+<li><code>rclone check</code>: Fix successful retries with
+<code>--download</code> counting errors (Nick Craig-Wood)</li>
+<li><code>rclone dedupe</code>: Fix logging to be easier to understand
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Warn macOS users that mount implementation is changing (Nick Craig-Wood)
+<li>Warn macOS users that mount implementation is changing (Nick
+Craig-Wood)
 <ul>
-<li>to test the new implementation use <code>rclone cmount</code> instead of <code>rclone mount</code></li>
-<li>this is because the library rclone uses has dropped macOS support</li>
+<li>to test the new implementation use <code>rclone cmount</code>
+instead of <code>rclone mount</code></li>
+<li>this is because the library rclone uses has dropped macOS
+support</li>
 </ul></li>
 <li>rc interface
 <ul>
 <li>Add call for unmount all (Chaitanya Bankanhal)</li>
-<li>Make <code>mount/mount</code> remote control take vfsOpt option (Nick Craig-Wood)</li>
+<li>Make <code>mount/mount</code> remote control take vfsOpt option
+(Nick Craig-Wood)</li>
 <li>Add mountOpt to <code>mount/mount</code> (Nick Craig-Wood)</li>
-<li>Add VFS and Mount options to <code>mount/listmounts</code> (Nick Craig-Wood)</li>
+<li>Add VFS and Mount options to <code>mount/listmounts</code> (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>Catch panics in cgofuse initialization and turn into error messages (Nick Craig-Wood)</li>
+<li>Catch panics in cgofuse initialization and turn into error messages
+(Nick Craig-Wood)</li>
 <li>Always supply stat information in Readdir (Nick Craig-Wood)</li>
-<li>Add support for reading unknown length files using direct IO (Windows) (Nick Craig-Wood)</li>
-<li>Fix On Windows don't add <code>-o uid/gid=-1</code> if user supplies <code>-o uid/gid</code>. (Nick Craig-Wood)</li>
+<li>Add support for reading unknown length files using direct IO
+(Windows) (Nick Craig-Wood)</li>
+<li>Fix On Windows don't add <code>-o uid/gid=-1</code> if user supplies
+<code>-o uid/gid</code>. (Nick Craig-Wood)</li>
 <li>Fix macOS losing directory contents in cmount (Nick Craig-Wood)</li>
 <li>Fix volume name broken in recent refactor (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Implement partial reads for <code>--vfs-cache-mode full</code> (Nick Craig-Wood)</li>
-<li>Add <code>--vfs-writeback</code> option to delay writes back to cloud storage (Nick Craig-Wood)</li>
-<li>Add <code>--vfs-read-ahead</code> parameter for use with <code>--vfs-cache-mode full</code> (Nick Craig-Wood)</li>
-<li>Restart pending uploads on restart of the cache (Nick Craig-Wood)</li>
+<li>Implement partial reads for <code>--vfs-cache-mode full</code> (Nick
+Craig-Wood)</li>
+<li>Add <code>--vfs-writeback</code> option to delay writes back to
+cloud storage (Nick Craig-Wood)</li>
+<li>Add <code>--vfs-read-ahead</code> parameter for use with
+<code>--vfs-cache-mode full</code> (Nick Craig-Wood)</li>
+<li>Restart pending uploads on restart of the cache (Nick
+Craig-Wood)</li>
 <li>Support synchronous cache space recovery upon ENOSPC (Leo Luan)</li>
-<li>Allow ReadAt and WriteAt to run concurrently with themselves (Nick Craig-Wood)</li>
+<li>Allow ReadAt and WriteAt to run concurrently with themselves (Nick
+Craig-Wood)</li>
 <li>Change modtime of file before upload to current (Rob Calistri)</li>
-<li>Recommend <code>--vfs-cache-modes writes</code> on backends which can't stream (Nick Craig-Wood)</li>
-<li>Add an optional <code>fs</code> parameter to vfs rc methods (Nick Craig-Wood)</li>
-<li>Fix errors when using &gt; 260 char files in the cache in Windows (Nick Craig-Wood)</li>
-<li>Fix renaming of items while they are being uploaded (Nick Craig-Wood)</li>
-<li>Fix very high load caused by slow directory listings (Nick Craig-Wood)</li>
-<li>Fix renamed files not being uploaded with <code>--vfs-cache-mode minimal</code> (Nick Craig-Wood)</li>
-<li>Fix directory locking caused by slow directory listings (Nick Craig-Wood)</li>
-<li>Fix saving from chrome without <code>--vfs-cache-mode writes</code> (Nick Craig-Wood)</li>
+<li>Recommend <code>--vfs-cache-modes writes</code> on backends which
+can't stream (Nick Craig-Wood)</li>
+<li>Add an optional <code>fs</code> parameter to vfs rc methods (Nick
+Craig-Wood)</li>
+<li>Fix errors when using &gt; 260 char files in the cache in Windows
+(Nick Craig-Wood)</li>
+<li>Fix renaming of items while they are being uploaded (Nick
+Craig-Wood)</li>
+<li>Fix very high load caused by slow directory listings (Nick
+Craig-Wood)</li>
+<li>Fix renamed files not being uploaded with
+<code>--vfs-cache-mode minimal</code> (Nick Craig-Wood)</li>
+<li>Fix directory locking caused by slow directory listings (Nick
+Craig-Wood)</li>
+<li>Fix saving from chrome without <code>--vfs-cache-mode writes</code>
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Add <code>--local-no-updated</code> to provide a consistent view of changing objects (Nick Craig-Wood)</li>
-<li>Add <code>--local-no-set-modtime</code> option to prevent modtime changes (tyhuber1)</li>
-<li>Fix race conditions updating and reading Object metadata (Nick Craig-Wood)</li>
+<li>Add <code>--local-no-updated</code> to provide a consistent view of
+changing objects (Nick Craig-Wood)</li>
+<li>Add <code>--local-no-set-modtime</code> option to prevent modtime
+changes (tyhuber1)</li>
+<li>Fix race conditions updating and reading Object metadata (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
-<li>Make any created backends be cached to fix rc problems (Nick Craig-Wood)</li>
+<li>Make any created backends be cached to fix rc problems (Nick
+Craig-Wood)</li>
 <li>Fix dedupe on caches wrapping drives (Nick Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Add <code>--crypt-server-side-across-configs</code> flag (Nick Craig-Wood)</li>
-<li>Make any created backends be cached to fix rc problems (Nick Craig-Wood)</li>
+<li>Add <code>--crypt-server-side-across-configs</code> flag (Nick
+Craig-Wood)</li>
+<li>Make any created backends be cached to fix rc problems (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Alias
 <ul>
-<li>Make any created backends be cached to fix rc problems (Nick Craig-Wood)</li>
+<li>Make any created backends be cached to fix rc problems (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Don't compile on &lt; go1.13 after dependency update (Nick Craig-Wood)</li>
+<li>Don't compile on &lt; go1.13 after dependency update (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
 <li>Implement server-side copy for files &gt; 5GB (Nick Craig-Wood)</li>
-<li>Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)</li>
-<li>Note that b2's encoding now allows  but rclone's hasn't changed (Nick Craig-Wood)</li>
+<li>Cancel in progress multipart uploads and copies on rclone exit (Nick
+Craig-Wood)</li>
+<li>Note that b2's encoding now allows  but rclone's hasn't changed
+(Nick Craig-Wood)</li>
 <li>Fix transfers when using download_url (Nick Craig-Wood)</li>
 </ul></li>
 <li>Box
 <ul>
 <li>Implement rclone cleanup (buengese)</li>
-<li>Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)</li>
+<li>Cancel in progress multipart uploads and copies on rclone exit (Nick
+Craig-Wood)</li>
 <li>Allow authentication with access token (David)</li>
 </ul></li>
 <li>Chunker
 <ul>
-<li>Make any created backends be cached to fix rc problems (Nick Craig-Wood)</li>
+<li>Make any created backends be cached to fix rc problems (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Add <code>rclone backend drives</code> to list shared drives (teamdrives) (Nick Craig-Wood)</li>
+<li>Add <code>rclone backend drives</code> to list shared drives
+(teamdrives) (Nick Craig-Wood)</li>
 <li>Implement <code>rclone backend untrash</code> (Nick Craig-Wood)</li>
-<li>Work around drive bug which didn't set modtime of copied docs (Nick Craig-Wood)</li>
-<li>Added <code>--drive-starred-only</code> to only show starred files (Jay McEntire)</li>
-<li>Deprecate <code>--drive-alternate-export</code> as it is no longer needed (themylogin)</li>
-<li>Fix duplication of Google docs on server-side copy (Nick Craig-Wood)</li>
-<li>Fix "panic: send on closed channel" when recycling dir entries (Nick Craig-Wood)</li>
+<li>Work around drive bug which didn't set modtime of copied docs (Nick
+Craig-Wood)</li>
+<li>Added <code>--drive-starred-only</code> to only show starred files
+(Jay McEntire)</li>
+<li>Deprecate <code>--drive-alternate-export</code> as it is no longer
+needed (themylogin)</li>
+<li>Fix duplication of Google docs on server-side copy (Nick
+Craig-Wood)</li>
+<li>Fix "panic: send on closed channel" when recycling dir entries (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Add copyright detector info in limitations section in the docs (Alex Guerrero)</li>
-<li>Fix <code>rclone link</code> by removing expires parameter (Nick Craig-Wood)</li>
+<li>Add copyright detector info in limitations section in the docs (Alex
+Guerrero)</li>
+<li>Fix <code>rclone link</code> by removing expires parameter (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Fichier
 <ul>
-<li>Detect Flood detected: IP Locked error and sleep for 30s (Nick Craig-Wood)</li>
+<li>Detect Flood detected: IP Locked error and sleep for 30s (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
 <li>Add explicit TLS support (Heiko Bornholdt)</li>
-<li>Add support for <code>--dump bodies</code> and <code>--dump auth</code> for debugging (Nick Craig-Wood)</li>
+<li>Add support for <code>--dump bodies</code> and
+<code>--dump auth</code> for debugging (Nick Craig-Wood)</li>
 <li>Fix interoperation with pure-ftpd (Nick Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
@@ -41163,51 +57887,72 @@ $ tree /tmp/c
 </ul></li>
 <li>Jottacloud
 <ul>
-<li>Bring back legacy authentication for use with whitelabel versions (buengese)</li>
-<li>Switch to new api root - also implement a very ugly workaround for the DirMove failures (buengese)</li>
+<li>Bring back legacy authentication for use with whitelabel versions
+(buengese)</li>
+<li>Switch to new api root - also implement a very ugly workaround for
+the DirMove failures (buengese)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Rework cancel of multipart uploads on rclone exit (Nick Craig-Wood)</li>
+<li>Rework cancel of multipart uploads on rclone exit (Nick
+Craig-Wood)</li>
 <li>Implement rclone cleanup (Nick Craig-Wood)</li>
-<li>Add <code>--onedrive-no-versions</code> flag to remove old versions (Nick Craig-Wood)</li>
+<li>Add <code>--onedrive-no-versions</code> flag to remove old versions
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Pcloud
 <ul>
-<li>Implement <code>rclone link</code> for public link creation (buengese)</li>
+<li>Implement <code>rclone link</code> for public link creation
+(buengese)</li>
 </ul></li>
 <li>Qingstor
 <ul>
-<li>Cancel in progress multipart uploads on rclone exit (Nick Craig-Wood)</li>
+<li>Cancel in progress multipart uploads on rclone exit (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
 <li>Preserve metadata when doing multipart copy (Nick Craig-Wood)</li>
-<li>Cancel in progress multipart uploads and copies on rclone exit (Nick Craig-Wood)</li>
-<li>Add <code>rclone link</code> for public link sharing (Roman Kredentser)</li>
-<li>Add <code>rclone backend restore</code> command to restore objects from GLACIER (Nick Craig-Wood)</li>
-<li>Add <code>rclone cleanup</code> and <code>rclone backend cleanup</code> to clean unfinished multipart uploads (Nick Craig-Wood)</li>
-<li>Add <code>rclone backend list-multipart-uploads</code> to list unfinished multipart uploads (Nick Craig-Wood)</li>
-<li>Add <code>--s3-max-upload-parts</code> support (Kamil Trzciński)</li>
-<li>Add <code>--s3-no-check-bucket</code> for minimising rclone transactions and perms (Nick Craig-Wood)</li>
-<li>Add <code>--s3-profile</code> and <code>--s3-shared-credentials-file</code> options (Nick Craig-Wood)</li>
+<li>Cancel in progress multipart uploads and copies on rclone exit (Nick
+Craig-Wood)</li>
+<li>Add <code>rclone link</code> for public link sharing (Roman
+Kredentser)</li>
+<li>Add <code>rclone backend restore</code> command to restore objects
+from GLACIER (Nick Craig-Wood)</li>
+<li>Add <code>rclone cleanup</code> and
+<code>rclone backend cleanup</code> to clean unfinished multipart
+uploads (Nick Craig-Wood)</li>
+<li>Add <code>rclone backend list-multipart-uploads</code> to list
+unfinished multipart uploads (Nick Craig-Wood)</li>
+<li>Add <code>--s3-max-upload-parts</code> support (Kamil
+Trzciński)</li>
+<li>Add <code>--s3-no-check-bucket</code> for minimising rclone
+transactions and perms (Nick Craig-Wood)</li>
+<li>Add <code>--s3-profile</code> and
+<code>--s3-shared-credentials-file</code> options (Nick Craig-Wood)</li>
 <li>Use regional s3 us-east-1 endpoint (David)</li>
 <li>Add Scaleway provider (Vincent Feltz)</li>
 <li>Update IBM COS endpoints (Egor Margineanu)</li>
-<li>Reduce the default <code>--s3-copy-cutoff</code> to &lt; 5GB for Backblaze S3 compatibility (Nick Craig-Wood)</li>
+<li>Reduce the default <code>--s3-copy-cutoff</code> to &lt; 5GB for
+Backblaze S3 compatibility (Nick Craig-Wood)</li>
 <li>Fix detection of bucket existing (Nick Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Use the absolute path instead of the relative path for listing for improved compatibility (Nick Craig-Wood)</li>
-<li>Add <code>--sftp-subsystem</code> and <code>--sftp-server-command</code> options (aus)</li>
+<li>Use the absolute path instead of the relative path for listing for
+improved compatibility (Nick Craig-Wood)</li>
+<li>Add <code>--sftp-subsystem</code> and
+<code>--sftp-server-command</code> options (aus)</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Fix dangling large objects breaking the listing (Nick Craig-Wood)</li>
+<li>Fix dangling large objects breaking the listing (Nick
+Craig-Wood)</li>
 <li>Fix purge not deleting directory markers (Nick Craig-Wood)</li>
-<li>Fix update multipart object removing all of its own parts (Nick Craig-Wood)</li>
-<li>Fix missing hash from object returned from upload (Nick Craig-Wood)</li>
+<li>Fix update multipart object removing all of its own parts (Nick
+Craig-Wood)</li>
+<li>Fix missing hash from object returned from upload (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Tardigrade
 <ul>
@@ -41223,20 +57968,26 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.52.3---2020-08-07">v1.52.3 - 2020-08-07</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.52.2...v1.52.3">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.52.2...v1.52.3">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
 <li>docs
 <ul>
-<li>Disable smart typography (e.g. en-dash) in MANUAL.* and man page (Nick Craig-Wood)</li>
+<li>Disable smart typography (e.g. en-dash) in MANUAL.* and man page
+(Nick Craig-Wood)</li>
 <li>Update install.md to reflect minimum Go version (Evan Harris)</li>
 <li>Update install from source instructions (Nick Craig-Wood)</li>
 <li>make_manual: Support SOURCE_DATE_EPOCH (Morten Linderud)</li>
 </ul></li>
-<li>log: Fix --use-json-log going to stderr not --log-file on Windows (Nick Craig-Wood)</li>
-<li>serve dlna: Fix file list on Samsung Series 6+ TVs (Matteo Pietro Dazzi)</li>
-<li>sync: Fix deadlock with --track-renames-strategy modtime (Nick Craig-Wood)</li>
+<li>log: Fix --use-json-log going to stderr not --log-file on Windows
+(Nick Craig-Wood)</li>
+<li>serve dlna: Fix file list on Samsung Series 6+ TVs (Matteo Pietro
+Dazzi)</li>
+<li>sync: Fix deadlock with --track-renames-strategy modtime (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
@@ -41251,24 +58002,30 @@ $ tree /tmp/c
 </ul></li>
 <li>FTP
 <ul>
-<li>Add note to docs about home vs root directory selection (Nick Craig-Wood)</li>
+<li>Add note to docs about home vs root directory selection (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Fix reverting to Copy when Move would have worked (Nick Craig-Wood)</li>
+<li>Fix reverting to Copy when Move would have worked (Nick
+Craig-Wood)</li>
 <li>Avoid comma rendered in URL in onedrive.md (Kevin)</li>
 </ul></li>
 <li>Pcloud
 <ul>
-<li>Fix oauth on European region "eapi.pcloud.com" (Nick Craig-Wood)</li>
+<li>Fix oauth on European region "eapi.pcloud.com" (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Fix bucket Region auto detection when Region unset in config (Nick Craig-Wood)</li>
+<li>Fix bucket Region auto detection when Region unset in config (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.52.2---2020-06-24">v1.52.2 - 2020-06-24</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.52.1...v1.52.2">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.52.1...v1.52.2">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
@@ -41277,18 +58034,24 @@ $ tree /tmp/c
 <li>Fix docker release build action (Nick Craig-Wood)</li>
 <li>Fix custom timezone in Docker image (NoLooseEnds)</li>
 </ul></li>
-<li>check: Fix misleading message which printed errors instead of differences (Nick Craig-Wood)</li>
-<li>errors: Add WSAECONNREFUSED and more to the list of retriable Windows errors (Nick Craig-Wood)</li>
+<li>check: Fix misleading message which printed errors instead of
+differences (Nick Craig-Wood)</li>
+<li>errors: Add WSAECONNREFUSED and more to the list of retriable
+Windows errors (Nick Craig-Wood)</li>
 <li>rcd: Fix incorrect prometheus metrics (Gary Kim)</li>
-<li>serve restic: Fix flags so they use environment variables (Nick Craig-Wood)</li>
-<li>serve webdav: Fix flags so they use environment variables (Nick Craig-Wood)</li>
+<li>serve restic: Fix flags so they use environment variables (Nick
+Craig-Wood)</li>
+<li>serve webdav: Fix flags so they use environment variables (Nick
+Craig-Wood)</li>
 <li>sync: Fix --track-renames-strategy modtime (Nick Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Fix not being able to delete a directory with a trashed shortcut (Nick Craig-Wood)</li>
+<li>Fix not being able to delete a directory with a trashed shortcut
+(Nick Craig-Wood)</li>
 <li>Fix creating a directory inside a shortcut (Nick Craig-Wood)</li>
-<li>Fix --drive-impersonate with cached root_folder_id (Nick Craig-Wood)</li>
+<li>Fix --drive-impersonate with cached root_folder_id (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
@@ -41296,7 +58059,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Speed up deletes by not retrying segment container deletes (Nick Craig-Wood)</li>
+<li>Speed up deletes by not retrying segment container deletes (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Tardigrade
 <ul>
@@ -41304,41 +58068,55 @@ $ tree /tmp/c
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Fix free/used display for rclone about/df for certain backends (Nick Craig-Wood)</li>
+<li>Fix free/used display for rclone about/df for certain backends (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.52.1---2020-06-10">v1.52.1 - 2020-06-10</h2>
-<p><a href="https://github.com/rclone/rclone/compare/v1.52.0...v1.52.1">See commits</a></p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.52.0...v1.52.1">See
+commits</a></p>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>lib/file: Fix SetSparse on Windows 7 which fixes downloads of files &gt; 250MB (Nick Craig-Wood)</li>
+<li>lib/file: Fix SetSparse on Windows 7 which fixes downloads of files
+&gt; 250MB (Nick Craig-Wood)</li>
 <li>build
 <ul>
-<li>Update go.mod to go1.14 to enable -mod=vendor build (Nick Craig-Wood)</li>
+<li>Update go.mod to go1.14 to enable -mod=vendor build (Nick
+Craig-Wood)</li>
 <li>Remove quicktest from Dockerfile (Nick Craig-Wood)</li>
 <li>Build Docker images with GitHub actions (Matteo Pietro Dazzi)</li>
 <li>Update Docker build workflows (Nick Craig-Wood)</li>
-<li>Set user_allow_other in /etc/fuse.conf in the Docker image (Nick Craig-Wood)</li>
+<li>Set user_allow_other in /etc/fuse.conf in the Docker image (Nick
+Craig-Wood)</li>
 <li>Fix xgo build after go1.14 go.mod update (Nick Craig-Wood)</li>
 </ul></li>
 <li>docs
 <ul>
-<li>Add link to source and modified time to footer of every page (Nick Craig-Wood)</li>
-<li>Remove manually set dates and use git dates instead (Nick Craig-Wood)</li>
-<li>Minor tense, punctuation, brevity and positivity changes for the home page (edwardxml)</li>
-<li>Remove leading slash in page reference in footer when present (Nick Craig-Wood)</li>
-<li>Note commands which need obscured input in the docs (Nick Craig-Wood)</li>
-<li>obscure: Write more help as we are referencing it elsewhere (Nick Craig-Wood)</li>
+<li>Add link to source and modified time to footer of every page (Nick
+Craig-Wood)</li>
+<li>Remove manually set dates and use git dates instead (Nick
+Craig-Wood)</li>
+<li>Minor tense, punctuation, brevity and positivity changes for the
+home page (edwardxml)</li>
+<li>Remove leading slash in page reference in footer when present (Nick
+Craig-Wood)</li>
+<li>Note commands which need obscured input in the docs (Nick
+Craig-Wood)</li>
+<li>obscure: Write more help as we are referencing it elsewhere (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Fix OS vs Unix path confusion - fixes ChangeNotify on Windows (Nick Craig-Wood)</li>
+<li>Fix OS vs Unix path confusion - fixes ChangeNotify on Windows (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Fix missing items when listing using --fast-list / ListR (Nick Craig-Wood)</li>
+<li>Fix missing items when listing using --fast-list / ListR (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Putio
 <ul>
@@ -41346,7 +58124,8 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Fix upload of single files into buckets without create permission (Nick Craig-Wood)</li>
+<li>Fix upload of single files into buckets without create permission
+(Nick Craig-Wood)</li>
 <li>Fix --header-upload (Nick Craig-Wood)</li>
 </ul></li>
 <li>Tardigrade
@@ -41356,94 +58135,139 @@ $ tree /tmp/c
 </ul></li>
 </ul>
 <h2 id="v1.52.0---2020-05-27">v1.52.0 - 2020-05-27</h2>
-<p>Special thanks to Martin Michlmayr for proof reading and correcting all the docs and Edward Barker for helping re-write the front page.</p>
-<p><a href="https://github.com/rclone/rclone/compare/v1.51.0...v1.52.0">See commits</a></p>
+<p>Special thanks to Martin Michlmayr for proof reading and correcting
+all the docs and Edward Barker for helping re-write the front page.</p>
+<p><a
+href="https://github.com/rclone/rclone/compare/v1.51.0...v1.52.0">See
+commits</a></p>
 <ul>
 <li>New backends
 <ul>
-<li><a href="https://rclone.org/tardigrade/">Tardigrade</a> backend for use with storj.io (Caleb Case)</li>
-<li><a href="https://rclone.org/union/">Union</a> re-write to have multiple writable remotes (Max Sum)</li>
-<li><a href="/seafile">Seafile</a> for Seafile server (Fred <span class="citation" data-cites="creativeprojects">@creativeprojects</span>)</li>
+<li><a href="https://rclone.org/tardigrade/">Tardigrade</a> backend for
+use with storj.io (Caleb Case)</li>
+<li><a href="https://rclone.org/union/">Union</a> re-write to have
+multiple writable remotes (Max Sum)</li>
+<li><a href="/seafile">Seafile</a> for Seafile server (Fred <span
+class="citation"
+data-cites="creativeprojects">@creativeprojects</span>)</li>
 </ul></li>
 <li>New commands
 <ul>
-<li>backend: command for backend-specific commands (see backends) (Nick Craig-Wood)</li>
-<li>cachestats: Deprecate in favour of <code>rclone backend stats cache:</code> (Nick Craig-Wood)</li>
-<li>dbhashsum: Deprecate in favour of <code>rclone hashsum DropboxHash</code> (Nick Craig-Wood)</li>
+<li>backend: command for backend-specific commands (see backends) (Nick
+Craig-Wood)</li>
+<li>cachestats: Deprecate in favour of
+<code>rclone backend stats cache:</code> (Nick Craig-Wood)</li>
+<li>dbhashsum: Deprecate in favour of
+<code>rclone hashsum DropboxHash</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li>Add <code>--header-download</code> and <code>--header-upload</code> flags for setting HTTP headers when uploading/downloading (Tim Gallant)</li>
-<li>Add <code>--header</code> flag to add HTTP headers to every HTTP transaction (Nick Craig-Wood)</li>
-<li>Add <code>--check-first</code> to do all checking before starting transfers (Nick Craig-Wood)</li>
-<li>Add <code>--track-renames-strategy</code> for configurable matching criteria for <code>--track-renames</code> (Bernd Schoolmann)</li>
-<li>Add <code>--cutoff-mode</code> hard,soft,cautious (Shing Kit Chan &amp; Franklyn Tackitt)</li>
-<li>Filter flags (e.g. <code>--files-from -</code>) can read from stdin (fishbullet)</li>
+<li>Add <code>--header-download</code> and <code>--header-upload</code>
+flags for setting HTTP headers when uploading/downloading (Tim
+Gallant)</li>
+<li>Add <code>--header</code> flag to add HTTP headers to every HTTP
+transaction (Nick Craig-Wood)</li>
+<li>Add <code>--check-first</code> to do all checking before starting
+transfers (Nick Craig-Wood)</li>
+<li>Add <code>--track-renames-strategy</code> for configurable matching
+criteria for <code>--track-renames</code> (Bernd Schoolmann)</li>
+<li>Add <code>--cutoff-mode</code> hard,soft,cautious (Shing Kit Chan
+&amp; Franklyn Tackitt)</li>
+<li>Filter flags (e.g. <code>--files-from -</code>) can read from stdin
+(fishbullet)</li>
 <li>Add <code>--error-on-no-transfer</code> option (Jon Fautley)</li>
-<li>Implement <code>--order-by xxx,mixed</code> for copying some small and some big files (Nick Craig-Wood)</li>
-<li>Allow <code>--max-backlog</code> to be negative meaning as large as possible (Nick Craig-Wood)</li>
-<li>Added <code>--no-unicode-normalization</code> flag to allow Unicode filenames to remain unique (Ben Zenker)</li>
-<li>Allow <code>--min-age</code>/<code>--max-age</code> to take a date as well as a duration (Nick Craig-Wood)</li>
-<li>Add rename statistics for file and directory renames (Nick Craig-Wood)</li>
+<li>Implement <code>--order-by xxx,mixed</code> for copying some small
+and some big files (Nick Craig-Wood)</li>
+<li>Allow <code>--max-backlog</code> to be negative meaning as large as
+possible (Nick Craig-Wood)</li>
+<li>Added <code>--no-unicode-normalization</code> flag to allow Unicode
+filenames to remain unique (Ben Zenker)</li>
+<li>Allow <code>--min-age</code>/<code>--max-age</code> to take a date
+as well as a duration (Nick Craig-Wood)</li>
+<li>Add rename statistics for file and directory renames (Nick
+Craig-Wood)</li>
 <li>Add statistics output to JSON log (reddi)</li>
 <li>Make stats be printed on non-zero exit code (Nick Craig-Wood)</li>
-<li>When running <code>--password-command</code> allow use of stdin (Sébastien Gross)</li>
+<li>When running <code>--password-command</code> allow use of stdin
+(Sébastien Gross)</li>
 <li>Stop empty strings being a valid remote path (Nick Craig-Wood)</li>
-<li>accounting: support WriterTo for less memory copying (Nick Craig-Wood)</li>
+<li>accounting: support WriterTo for less memory copying (Nick
+Craig-Wood)</li>
 <li>build
 <ul>
 <li>Update to use go1.14 for the build (Nick Craig-Wood)</li>
-<li>Add <code>-trimpath</code> to release build for reproduceable builds (Nick Craig-Wood)</li>
+<li>Add <code>-trimpath</code> to release build for reproduceable builds
+(Nick Craig-Wood)</li>
 <li>Remove GOOS and GOARCH from Dockerfile (Brandon Philips)</li>
 </ul></li>
 <li>config
 <ul>
-<li>Fsync the config file after writing to save more reliably (Nick Craig-Wood)</li>
-<li>Add <code>--obscure</code> and <code>--no-obscure</code> flags to <code>config create</code>/<code>update</code> (Nick Craig-Wood)</li>
-<li>Make <code>config show</code> take <code>remote:</code> as well as <code>remote</code> (Nick Craig-Wood)</li>
+<li>Fsync the config file after writing to save more reliably (Nick
+Craig-Wood)</li>
+<li>Add <code>--obscure</code> and <code>--no-obscure</code> flags to
+<code>config create</code>/<code>update</code> (Nick Craig-Wood)</li>
+<li>Make <code>config show</code> take <code>remote:</code> as well as
+<code>remote</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>copyurl: Add <code>--no-clobber</code> flag (Denis)</li>
-<li>delete: Added <code>--rmdirs</code> flag to delete directories as well (Kush)</li>
+<li>delete: Added <code>--rmdirs</code> flag to delete directories as
+well (Kush)</li>
 <li>filter: Added <code>--files-from-raw</code> flag (Ankur Gupta)</li>
 <li>genautocomplete: Add support for fish shell (Matan Rosenberg)</li>
 <li>log: Add support for syslog LOCAL facilities (Patryk Jakuszew)</li>
-<li>lsjson: Add <code>--hash-type</code> parameter and use it in lsf to speed up hashing (Nick Craig-Wood)</li>
+<li>lsjson: Add <code>--hash-type</code> parameter and use it in lsf to
+speed up hashing (Nick Craig-Wood)</li>
 <li>rc
 <ul>
-<li>Add <code>-o</code>/<code>--opt</code> and <code>-a</code>/<code>--arg</code> for more structured input (Nick Craig-Wood)</li>
-<li>Implement <code>backend/command</code> for running backend-specific commands remotely (Nick Craig-Wood)</li>
-<li>Add <code>mount/mount</code> command for starting <code>rclone mount</code> via the API (Chaitanya)</li>
+<li>Add <code>-o</code>/<code>--opt</code> and
+<code>-a</code>/<code>--arg</code> for more structured input (Nick
+Craig-Wood)</li>
+<li>Implement <code>backend/command</code> for running backend-specific
+commands remotely (Nick Craig-Wood)</li>
+<li>Add <code>mount/mount</code> command for starting
+<code>rclone mount</code> via the API (Chaitanya)</li>
 </ul></li>
 <li>rcd: Add Prometheus metrics support (Gary Kim)</li>
 <li>serve http
 <ul>
-<li>Added a <code>--template</code> flag for user defined markup (calistri)</li>
-<li>Add Last-Modified headers to files and directories (Nick Craig-Wood)</li>
+<li>Added a <code>--template</code> flag for user defined markup
+(calistri)</li>
+<li>Add Last-Modified headers to files and directories (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>serve sftp: Add support for multiple host keys by repeating <code>--key</code> flag (Maxime Suret)</li>
-<li>touch: Add <code>--localtime</code> flag to make <code>--timestamp</code> localtime not UTC (Nick Craig-Wood)</li>
+<li>serve sftp: Add support for multiple host keys by repeating
+<code>--key</code> flag (Maxime Suret)</li>
+<li>touch: Add <code>--localtime</code> flag to make
+<code>--timestamp</code> localtime not UTC (Nick Craig-Wood)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>accounting
 <ul>
-<li>Restore "Max number of stats groups reached" log line (Michał Matczuk)</li>
-<li>Correct exitcode on Transfer Limit Exceeded flag. (Anuar Serdaliyev)</li>
+<li>Restore "Max number of stats groups reached" log line (Michał
+Matczuk)</li>
+<li>Correct exitcode on Transfer Limit Exceeded flag. (Anuar
+Serdaliyev)</li>
 <li>Reset bytes read during copy retry (Ankur Gupta)</li>
 <li>Fix race clearing stats (Nick Craig-Wood)</li>
 </ul></li>
-<li>copy: Only create empty directories when they don't exist on the remote (Ishuah Kariuki)</li>
-<li>dedupe: Stop dedupe deleting files with identical IDs (Nick Craig-Wood)</li>
+<li>copy: Only create empty directories when they don't exist on the
+remote (Ishuah Kariuki)</li>
+<li>dedupe: Stop dedupe deleting files with identical IDs (Nick
+Craig-Wood)</li>
 <li>oauth
 <ul>
-<li>Use custom http client so that <code>--no-check-certificate</code> is honored by oauth token fetch (Mark Spieth)</li>
+<li>Use custom http client so that <code>--no-check-certificate</code>
+is honored by oauth token fetch (Mark Spieth)</li>
 <li>Replace deprecated oauth2.NoContext (Lars Lehtonen)</li>
 </ul></li>
 <li>operations
 <ul>
-<li>Fix setting the timestamp on Windows for multithread copy (Nick Craig-Wood)</li>
+<li>Fix setting the timestamp on Windows for multithread copy (Nick
+Craig-Wood)</li>
 <li>Make rcat obey <code>--ignore-checksum</code> (Nick Craig-Wood)</li>
-<li>Make <code>--max-transfer</code> more accurate (Nick Craig-Wood)</li>
+<li>Make <code>--max-transfer</code> more accurate (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>rc
 <ul>
@@ -41454,55 +58278,80 @@ $ tree /tmp/c
 <li>serve dlna
 <ul>
 <li>Cds: don't specify childCount at all when unknown (Dan Walters)</li>
-<li>Cds: use modification time as date in dlna metadata (Dan Walters)</li>
+<li>Cds: use modification time as date in dlna metadata (Dan
+Walters)</li>
 </ul></li>
-<li>serve restic: Fix tests after restic project removed vendoring (Nick Craig-Wood)</li>
+<li>serve restic: Fix tests after restic project removed vendoring (Nick
+Craig-Wood)</li>
 <li>sync
 <ul>
-<li>Fix incorrect "nothing to transfer" message using <code>--delete-before</code> (Nick Craig-Wood)</li>
-<li>Only create empty directories when they don't exist on the remote (Ishuah Kariuki)</li>
+<li>Fix incorrect "nothing to transfer" message using
+<code>--delete-before</code> (Nick Craig-Wood)</li>
+<li>Only create empty directories when they don't exist on the remote
+(Ishuah Kariuki)</li>
 </ul></li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Add <code>--async-read</code> flag to disable asynchronous reads (Nick Craig-Wood)</li>
-<li>Ignore <code>--allow-root</code> flag with a warning as it has been removed upstream (Nick Craig-Wood)</li>
-<li>Warn if <code>--allow-non-empty</code> used on Windows and clarify docs (Nick Craig-Wood)</li>
-<li>Constrain to go1.13 or above otherwise bazil.org/fuse fails to compile (Nick Craig-Wood)</li>
+<li>Add <code>--async-read</code> flag to disable asynchronous reads
+(Nick Craig-Wood)</li>
+<li>Ignore <code>--allow-root</code> flag with a warning as it has been
+removed upstream (Nick Craig-Wood)</li>
+<li>Warn if <code>--allow-non-empty</code> used on Windows and clarify
+docs (Nick Craig-Wood)</li>
+<li>Constrain to go1.13 or above otherwise bazil.org/fuse fails to
+compile (Nick Craig-Wood)</li>
 <li>Fix fail because of too long volume name (evileye)</li>
 <li>Report 1PB free for unknown disk sizes (Nick Craig-Wood)</li>
-<li>Map more rclone errors into file systems errors (Nick Craig-Wood)</li>
+<li>Map more rclone errors into file systems errors (Nick
+Craig-Wood)</li>
 <li>Fix disappearing cwd problem (Nick Craig-Wood)</li>
-<li>Use ReaddirPlus on Windows to improve directory listing performance (Nick Craig-Wood)</li>
-<li>Send a hint as to whether the filesystem is case insensitive or not (Nick Craig-Wood)</li>
+<li>Use ReaddirPlus on Windows to improve directory listing performance
+(Nick Craig-Wood)</li>
+<li>Send a hint as to whether the filesystem is case insensitive or not
+(Nick Craig-Wood)</li>
 <li>Add rc command <code>mount/types</code> (Nick Craig-Wood)</li>
 <li>Change maximum leaf name length to 1024 bytes (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Add <code>--vfs-read-wait</code> and <code>--vfs-write-wait</code> flags to control time waiting for a sequential read/write (Nick Craig-Wood)</li>
-<li>Change default <code>--vfs-read-wait</code> to 20ms (it was 5ms and not configurable) (Nick Craig-Wood)</li>
-<li>Make <code>df</code> output more consistent on a rclone mount. (Yves G)</li>
+<li>Add <code>--vfs-read-wait</code> and <code>--vfs-write-wait</code>
+flags to control time waiting for a sequential read/write (Nick
+Craig-Wood)</li>
+<li>Change default <code>--vfs-read-wait</code> to 20ms (it was 5ms and
+not configurable) (Nick Craig-Wood)</li>
+<li>Make <code>df</code> output more consistent on a rclone mount. (Yves
+G)</li>
 <li>Report 1PB free for unknown disk sizes (Nick Craig-Wood)</li>
-<li>Fix race condition caused by unlocked reading of Dir.path (Nick Craig-Wood)</li>
-<li>Make File lock and Dir lock not overlap to avoid deadlock (Nick Craig-Wood)</li>
-<li>Implement lock ordering between File and Dir to eliminate deadlocks (Nick Craig-Wood)</li>
+<li>Fix race condition caused by unlocked reading of Dir.path (Nick
+Craig-Wood)</li>
+<li>Make File lock and Dir lock not overlap to avoid deadlock (Nick
+Craig-Wood)</li>
+<li>Implement lock ordering between File and Dir to eliminate deadlocks
+(Nick Craig-Wood)</li>
 <li>Factor the vfs cache into its own package (Nick Craig-Wood)</li>
 <li>Pin the Fs in use in the Fs cache (Nick Craig-Wood)</li>
-<li>Add SetSys() methods to Node to allow caching stuff on a node (Nick Craig-Wood)</li>
-<li>Ignore file not found errors from Hash in Read.Release (Nick Craig-Wood)</li>
+<li>Add SetSys() methods to Node to allow caching stuff on a node (Nick
+Craig-Wood)</li>
+<li>Ignore file not found errors from Hash in Read.Release (Nick
+Craig-Wood)</li>
 <li>Fix hang in read wait code (Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Speed up multi thread downloads by using sparse files on Windows (Nick Craig-Wood)</li>
-<li>Implement <code>--local-no-sparse</code> flag for disabling sparse files (Nick Craig-Wood)</li>
-<li>Implement <code>rclone backend noop</code> for testing purposes (Nick Craig-Wood)</li>
-<li>Fix "file not found" errors on post transfer Hash calculation (Nick Craig-Wood)</li>
+<li>Speed up multi thread downloads by using sparse files on Windows
+(Nick Craig-Wood)</li>
+<li>Implement <code>--local-no-sparse</code> flag for disabling sparse
+files (Nick Craig-Wood)</li>
+<li>Implement <code>rclone backend noop</code> for testing purposes
+(Nick Craig-Wood)</li>
+<li>Fix "file not found" errors on post transfer Hash calculation (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
-<li>Implement <code>rclone backend stats</code> command (Nick Craig-Wood)</li>
+<li>Implement <code>rclone backend stats</code> command (Nick
+Craig-Wood)</li>
 <li>Fix Server Side Copy with Temp Upload (Brandon McNama)</li>
 <li>Remove Unused Functions (Lars Lehtonen)</li>
 <li>Disable race tests until bbolt is fixed (Nick Craig-Wood)</li>
@@ -41514,46 +58363,69 @@ $ tree /tmp/c
 <ul>
 <li>Calculate hashes for uploads from local disk (Nick Craig-Wood)
 <ul>
-<li>This allows encrypted Jottacloud uploads without using local disk</li>
+<li>This allows encrypted Jottacloud uploads without using local
+disk</li>
 <li>This means encrypted s3/b2 uploads will now have hashes</li>
 </ul></li>
-<li>Added <code>rclone backend decode</code>/<code>encode</code> commands to replicate functionality of <code>cryptdecode</code> (Anagh Kumar Baranwal)</li>
-<li>Get rid of the unused Cipher interface as it obfuscated the code (Nick Craig-Wood)</li>
+<li>Added <code>rclone backend decode</code>/<code>encode</code>
+commands to replicate functionality of <code>cryptdecode</code> (Anagh
+Kumar Baranwal)</li>
+<li>Get rid of the unused Cipher interface as it obfuscated the code
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Implement streaming of unknown sized files so <code>rcat</code> is now supported (Nick Craig-Wood)</li>
-<li>Implement memory pooling to control memory use (Nick Craig-Wood)</li>
-<li>Add <code>--azureblob-disable-checksum</code> flag (Nick Craig-Wood)</li>
-<li>Retry <code>InvalidBlobOrBlock</code> error as it may indicate block concurrency problems (Nick Craig-Wood)</li>
-<li>Remove unused <code>Object.parseTimeString()</code> (Lars Lehtonen)</li>
-<li>Fix permission error on SAS URL limited to container (Nick Craig-Wood)</li>
+<li>Implement streaming of unknown sized files so <code>rcat</code> is
+now supported (Nick Craig-Wood)</li>
+<li>Implement memory pooling to control memory use (Nick
+Craig-Wood)</li>
+<li>Add <code>--azureblob-disable-checksum</code> flag (Nick
+Craig-Wood)</li>
+<li>Retry <code>InvalidBlobOrBlock</code> error as it may indicate block
+concurrency problems (Nick Craig-Wood)</li>
+<li>Remove unused <code>Object.parseTimeString()</code> (Lars
+Lehtonen)</li>
+<li>Fix permission error on SAS URL limited to container (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 <li>Ignore directory markers at the root also (Nick Craig-Wood)</li>
 <li>Force the case of the SHA1 to lowercase (Nick Craig-Wood)</li>
-<li>Remove unused <code>largeUpload.clearUploadURL()</code> (Lars Lehtonen)</li>
+<li>Remove unused <code>largeUpload.clearUploadURL()</code> (Lars
+Lehtonen)</li>
 </ul></li>
 <li>Box
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 <li>Implement About to read size used (Nick Craig-Wood)</li>
 <li>Add token renew function for jwt auth (David Bramwell)</li>
-<li>Added support for interchangeable root folder for Box backend (Sunil Patra)</li>
+<li>Added support for interchangeable root folder for Box backend (Sunil
+Patra)</li>
 <li>Remove unnecessary iat from jws claims (David)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Follow shortcuts by default, skip with <code>--drive-skip-shortcuts</code> (Nick Craig-Wood)</li>
-<li>Implement <code>rclone backend shortcut</code> command for creating shortcuts (Nick Craig-Wood)</li>
-<li>Added <code>rclone backend</code> command to change <code>service_account_file</code> and <code>chunk_size</code> (Anagh Kumar Baranwal)</li>
-<li>Fix missing files when using <code>--fast-list</code> and <code>--drive-shared-with-me</code> (Nick Craig-Wood)</li>
-<li>Fix duplicate items when using <code>--drive-shared-with-me</code> (Nick Craig-Wood)</li>
-<li>Extend <code>--drive-stop-on-upload-limit</code> to respond to <code>teamDriveFileLimitExceeded</code>. (harry)</li>
-<li>Don't delete files with multiple parents to avoid data loss (Nick Craig-Wood)</li>
-<li>Server side copy docs use default description if empty (Nick Craig-Wood)</li>
+<li>Follow shortcuts by default, skip with
+<code>--drive-skip-shortcuts</code> (Nick Craig-Wood)</li>
+<li>Implement <code>rclone backend shortcut</code> command for creating
+shortcuts (Nick Craig-Wood)</li>
+<li>Added <code>rclone backend</code> command to change
+<code>service_account_file</code> and <code>chunk_size</code> (Anagh
+Kumar Baranwal)</li>
+<li>Fix missing files when using <code>--fast-list</code> and
+<code>--drive-shared-with-me</code> (Nick Craig-Wood)</li>
+<li>Fix duplicate items when using <code>--drive-shared-with-me</code>
+(Nick Craig-Wood)</li>
+<li>Extend <code>--drive-stop-on-upload-limit</code> to respond to
+<code>teamDriveFileLimitExceeded</code>. (harry)</li>
+<li>Don't delete files with multiple parents to avoid data loss (Nick
+Craig-Wood)</li>
+<li>Server side copy docs use default description if empty (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -41562,41 +58434,53 @@ $ tree /tmp/c
 </ul></li>
 <li>Fichier
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
-<li>Implement custom pacer to deal with the new rate limiting (buengese)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
+<li>Implement custom pacer to deal with the new rate limiting
+(buengese)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Fix lockup when using concurrency limit on failed connections (Nick Craig-Wood)</li>
-<li>Fix lockup on failed upload when using concurrency limit (Nick Craig-Wood)</li>
-<li>Fix lockup on Close failures when using concurrency limit (Nick Craig-Wood)</li>
-<li>Work around pureftp sending spurious 150 messages (Nick Craig-Wood)</li>
+<li>Fix lockup when using concurrency limit on failed connections (Nick
+Craig-Wood)</li>
+<li>Fix lockup on failed upload when using concurrency limit (Nick
+Craig-Wood)</li>
+<li>Fix lockup on Close failures when using concurrency limit (Nick
+Craig-Wood)</li>
+<li>Work around pureftp sending spurious 150 messages (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Nick Craig-Wood)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Nick Craig-Wood)</li>
 <li>Add <code>ARCHIVE</code> storage class to help (Adam Stroud)</li>
 <li>Ignore directory markers at the root (Nick Craig-Wood)</li>
 </ul></li>
 <li>Googlephotos
 <ul>
 <li>Make the start year configurable (Daven)</li>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 <li>Create feature/favorites directory (Brandon Philips)</li>
 <li>Fix "concurrent map write" error (Nick Craig-Wood)</li>
 <li>Don't put an image in error message (Nick Craig-Wood)</li>
 </ul></li>
 <li>HTTP
 <ul>
-<li>Improved directory listing with new template from Caddy project (calisro)</li>
+<li>Improved directory listing with new template from Caddy project
+(calisro)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
 <li>Implement <code>--jottacloud-trashed-only</code> (buengese)</li>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
-<li>Use <code>RawURLEncoding</code> when decoding base64 encoded login token (buengese)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
+<li>Use <code>RawURLEncoding</code> when decoding base64 encoded login
+token (buengese)</li>
 <li>Implement cleanup (buengese)</li>
-<li>Update docs regarding cleanup, removed remains from old auth, and added warning about special mountpoints. (albertony)</li>
+<li>Update docs regarding cleanup, removed remains from old auth, and
+added warning about special mountpoints. (albertony)</li>
 </ul></li>
 <li>Mailru
 <ul>
@@ -41604,60 +58488,81 @@ $ tree /tmp/c
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Implement <code>--onedrive-server-side-across-configs</code> (Nick Craig-Wood)</li>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
-<li>Fix occasional 416 errors on multipart uploads (Nick Craig-Wood)</li>
+<li>Implement <code>--onedrive-server-side-across-configs</code> (Nick
+Craig-Wood)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
+<li>Fix occasional 416 errors on multipart uploads (Nick
+Craig-Wood)</li>
 <li>Added maximum chunk size limit warning in the docs (Harry)</li>
 <li>Fix missing drive on config (Nick Craig-Wood)</li>
 <li>Make error <code>quotaLimitReached</code> to be fatal (harry)</li>
 </ul></li>
 <li>Opendrive
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 </ul></li>
 <li>Pcloud
 <ul>
-<li>Added support for interchangeable root folder for pCloud backend (Sunil Patra)</li>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
-<li>Fix initial config "Auth state doesn't match" message (Nick Craig-Wood)</li>
+<li>Added support for interchangeable root folder for pCloud backend
+(Sunil Patra)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
+<li>Fix initial config "Auth state doesn't match" message (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Premiumizeme
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 <li>Prune unused functions (Lars Lehtonen)</li>
 </ul></li>
 <li>Putio
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Nick Craig-Wood)</li>
-<li>Make downloading files use the rclone http Client (Nick Craig-Wood)</li>
-<li>Fix parsing of remotes with leading and trailing / (Nick Craig-Wood)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Nick Craig-Wood)</li>
+<li>Make downloading files use the rclone http Client (Nick
+Craig-Wood)</li>
+<li>Fix parsing of remotes with leading and trailing / (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Qingstor
 <ul>
-<li>Make <code>rclone cleanup</code> remove pending multipart uploads older than 24h (Nick Craig-Wood)</li>
+<li>Make <code>rclone cleanup</code> remove pending multipart uploads
+older than 24h (Nick Craig-Wood)</li>
 <li>Try harder to cancel failed multipart uploads (Nick Craig-Wood)</li>
 <li>Prune <code>multiUploader.list()</code> (Lars Lehtonen)</li>
 <li>Lint fix (Lars Lehtonen)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 <li>Use memory pool for buffer allocations (Maciej Zimnoch)</li>
 <li>Add SSE-C support for AWS, Ceph, and MinIO (Jack Anderson)</li>
 <li>Fail fast multipart upload (Michał Matczuk)</li>
-<li>Report errors on bucket creation (mkdir) correctly (Nick Craig-Wood)</li>
-<li>Specify that Minio supports URL encoding in listings (Nick Craig-Wood)</li>
+<li>Report errors on bucket creation (mkdir) correctly (Nick
+Craig-Wood)</li>
+<li>Specify that Minio supports URL encoding in listings (Nick
+Craig-Wood)</li>
 <li>Added 500 as retryErrorCode (Michał Matczuk)</li>
-<li>Use <code>--low-level-retries</code> as the number of SDK retries (Aleksandar Janković)</li>
+<li>Use <code>--low-level-retries</code> as the number of SDK retries
+(Aleksandar Janković)</li>
 <li>Fix multipart abort context (Aleksandar Jankovic)</li>
-<li>Replace deprecated <code>session.New()</code> with <code>session.NewSession()</code> (Lars Lehtonen)</li>
-<li>Use the provided size parameter when allocating a new memory pool (Joachim Brandon LeBlanc)</li>
-<li>Use rclone's low level retries instead of AWS SDK to fix listing retries (Nick Craig-Wood)</li>
+<li>Replace deprecated <code>session.New()</code> with
+<code>session.NewSession()</code> (Lars Lehtonen)</li>
+<li>Use the provided size parameter when allocating a new memory pool
+(Joachim Brandon LeBlanc)</li>
+<li>Use rclone's low level retries instead of AWS SDK to fix listing
+retries (Nick Craig-Wood)</li>
 <li>Ignore directory markers at the root also (Nick Craig-Wood)</li>
 <li>Use single memory pool (Michał Matczuk)</li>
 <li>Do not resize buf on put to memBuf (Michał Matczuk)</li>
-<li>Improve docs for <code>--s3-disable-checksum</code> (Nick Craig-Wood)</li>
-<li>Don't leak memory or tokens in edge cases for multipart upload (Nick Craig-Wood)</li>
+<li>Improve docs for <code>--s3-disable-checksum</code> (Nick
+Craig-Wood)</li>
+<li>Don't leak memory or tokens in edge cases for multipart upload (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Seafile
 <ul>
@@ -41665,20 +58570,25 @@ $ tree /tmp/c
 </ul></li>
 <li>SFTP
 <ul>
-<li>Added <code>--sftp-pem-key</code> to support inline key files (calisro)</li>
-<li>Fix post transfer copies failing with 0 size when using <code>set_modtime=false</code> (Nick Craig-Wood)</li>
+<li>Added <code>--sftp-pem-key</code> to support inline key files
+(calisro)</li>
+<li>Fix post transfer copies failing with 0 size when using
+<code>set_modtime=false</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>Sharefile
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 </ul></li>
 <li>Sugarsync
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Nick Craig-Wood)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Nick Craig-Wood)</li>
 <li>Fix cosmetic issue in error message (Martin Michlmayr)</li>
 </ul></li>
 <li>Union
@@ -41690,61 +58600,81 @@ $ tree /tmp/c
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
-<li>Fix <code>X-OC-Mtime</code> header for Transip compatibility (Nick Craig-Wood)</li>
-<li>Report full and consistent usage with <code>about</code> (Yves G)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
+<li>Fix <code>X-OC-Mtime</code> header for Transip compatibility (Nick
+Craig-Wood)</li>
+<li>Report full and consistent usage with <code>about</code> (Yves
+G)</li>
 </ul></li>
 <li>Yandex
 <ul>
-<li>Add support for <code>--header-upload</code> and <code>--header-download</code> (Tim Gallant)</li>
+<li>Add support for <code>--header-upload</code> and
+<code>--header-download</code> (Tim Gallant)</li>
 </ul></li>
 </ul>
 <h2 id="v1.51.0---2020-02-01">v1.51.0 - 2020-02-01</h2>
 <ul>
 <li>New backends
 <ul>
-<li><a href="https://rclone.org/memory/">Memory</a> (Nick Craig-Wood)</li>
-<li><a href="https://rclone.org/sugarsync/">Sugarsync</a> (Nick Craig-Wood)</li>
+<li><a href="https://rclone.org/memory/">Memory</a> (Nick
+Craig-Wood)</li>
+<li><a href="https://rclone.org/sugarsync/">Sugarsync</a> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li>Adjust all backends to have <code>--backend-encoding</code> parameter (Nick Craig-Wood)
+<li>Adjust all backends to have <code>--backend-encoding</code>
+parameter (Nick Craig-Wood)
 <ul>
-<li>this enables the encoding for special characters to be adjusted or disabled</li>
+<li>this enables the encoding for special characters to be adjusted or
+disabled</li>
 </ul></li>
-<li>Add <code>--max-duration</code> flag to control the maximum duration of a transfer session (boosh)</li>
-<li>Add <code>--expect-continue-timeout</code> flag, default 1s (Nick Craig-Wood)</li>
-<li>Add <code>--no-check-dest</code> flag for copying without testing the destination (Nick Craig-Wood)</li>
-<li>Implement <code>--order-by</code> flag to order transfers (Nick Craig-Wood)</li>
+<li>Add <code>--max-duration</code> flag to control the maximum duration
+of a transfer session (boosh)</li>
+<li>Add <code>--expect-continue-timeout</code> flag, default 1s (Nick
+Craig-Wood)</li>
+<li>Add <code>--no-check-dest</code> flag for copying without testing
+the destination (Nick Craig-Wood)</li>
+<li>Implement <code>--order-by</code> flag to order transfers (Nick
+Craig-Wood)</li>
 <li>accounting
 <ul>
-<li>Don't show entries in both transferring and checking (Nick Craig-Wood)</li>
+<li>Don't show entries in both transferring and checking (Nick
+Craig-Wood)</li>
 <li>Add option to delete stats (Aleksandar Jankovic)</li>
 </ul></li>
 <li>build
 <ul>
 <li>Compress the test builds with gzip (Nick Craig-Wood)</li>
-<li>Implement a framework for starting test servers during tests (Nick Craig-Wood)</li>
+<li>Implement a framework for starting test servers during tests (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>cmd: Always print elapsed time to tenth place seconds in progress (Gary Kim)</li>
+<li>cmd: Always print elapsed time to tenth place seconds in progress
+(Gary Kim)</li>
 <li>config
 <ul>
-<li>Add <code>--password-command</code> to allow dynamic config password (Damon Permezel)</li>
+<li>Add <code>--password-command</code> to allow dynamic config password
+(Damon Permezel)</li>
 <li>Give config questions default values (Nick Craig-Wood)</li>
 <li>Check a remote exists when creating a new one (Nick Craig-Wood)</li>
 </ul></li>
-<li>copyurl: Add <code>--stdout</code> flag to write to stdout (Nick Craig-Wood)</li>
+<li>copyurl: Add <code>--stdout</code> flag to write to stdout (Nick
+Craig-Wood)</li>
 <li>dedupe: Implement keep smallest too (Nick Craig-Wood)</li>
 <li>hashsum: Add flag <code>--base64</code> flag (landall)</li>
-<li>lsf: Speed up on s3/swift/etc by not reading mimetype by default (Nick Craig-Wood)</li>
+<li>lsf: Speed up on s3/swift/etc by not reading mimetype by default
+(Nick Craig-Wood)</li>
 <li>lsjson: Add <code>--no-mimetype</code> flag (Nick Craig-Wood)</li>
-<li>rc: Add methods to turn on blocking and mutex profiling (Nick Craig-Wood)</li>
+<li>rc: Add methods to turn on blocking and mutex profiling (Nick
+Craig-Wood)</li>
 <li>rcd
 <ul>
 <li>Adding group parameter to stats (Chaitanya)</li>
 <li>Move webgui apart; option to disable browser (Xiaoxing Ye)</li>
 </ul></li>
-<li>serve sftp: Add support for public key with auth proxy (Paul Tinsley)</li>
+<li>serve sftp: Add support for public key with auth proxy (Paul
+Tinsley)</li>
 <li>stats: Show deletes in stats and hide zero stats (anuar45)</li>
 </ul></li>
 <li>Bug Fixes
@@ -41754,67 +58684,94 @@ $ tree /tmp/c
 <li>Fix error counter counting multiple times (Ankur Gupta)</li>
 <li>Fix error count shown as checks (Cnly)</li>
 <li>Clear finished transfer in stats-reset (Maciej Zimnoch)</li>
-<li>Added StatsInfo locking in statsGroups sum function (Michał Matczuk)</li>
+<li>Added StatsInfo locking in statsGroups sum function (Michał
+Matczuk)</li>
 </ul></li>
 <li>asyncreader: Fix EOF error (buengese)</li>
-<li>check: Fix <code>--one-way</code> recursing more directories than it needs to (Nick Craig-Wood)</li>
-<li>chunkedreader: Disable hash calculation for first segment (Nick Craig-Wood)</li>
+<li>check: Fix <code>--one-way</code> recursing more directories than it
+needs to (Nick Craig-Wood)</li>
+<li>chunkedreader: Disable hash calculation for first segment (Nick
+Craig-Wood)</li>
 <li>config
 <ul>
-<li>Do not open browser on headless on drive/gcs/google photos (Xiaoxing Ye)</li>
-<li>SetValueAndSave ignore error if config section does not exist yet (buengese)</li>
+<li>Do not open browser on headless on drive/gcs/google photos (Xiaoxing
+Ye)</li>
+<li>SetValueAndSave ignore error if config section does not exist yet
+(buengese)</li>
 </ul></li>
 <li>cmd: Fix completion with an encrypted config (Danil Semelenov)</li>
-<li>dbhashsum: Stop it returning UNSUPPORTED on dropbox (Nick Craig-Wood)</li>
+<li>dbhashsum: Stop it returning UNSUPPORTED on dropbox (Nick
+Craig-Wood)</li>
 <li>dedupe: Add missing modes to help string (Nick Craig-Wood)</li>
 <li>operations
 <ul>
-<li>Fix dedupe continuing on errors like insufficientFilePersimmon (SezalAgrawal)</li>
+<li>Fix dedupe continuing on errors like insufficientFilePersimmon
+(SezalAgrawal)</li>
 <li>Clear accounting before low level retry (Maciej Zimnoch)</li>
-<li>Write debug message when hashes could not be checked (Ole Schütt)</li>
-<li>Move interface assertion to tests to remove pflag dependency (Nick Craig-Wood)</li>
-<li>Make NewOverrideObjectInfo public and factor uses (Nick Craig-Wood)</li>
+<li>Write debug message when hashes could not be checked (Ole
+Schütt)</li>
+<li>Move interface assertion to tests to remove pflag dependency (Nick
+Craig-Wood)</li>
+<li>Make NewOverrideObjectInfo public and factor uses (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>proxy: Replace use of bcrypt with sha256 (Nick Craig-Wood)</li>
 <li>vendor
 <ul>
 <li>Update bazil.org/fuse to fix FreeBSD 12.1 (Nick Craig-Wood)</li>
-<li>Update github.com/t3rm1n4l/go-mega to fix mega "illegal base64 data at input byte 22" (Nick Craig-Wood)</li>
+<li>Update github.com/t3rm1n4l/go-mega to fix mega "illegal base64 data
+at input byte 22" (Nick Craig-Wood)</li>
 <li>Update termbox-go to fix ncdu command on FreeBSD (Kuang-che Wu)</li>
-<li>Update t3rm1n4l/go-mega - fixes mega: couldn't login: crypto/aes: invalid key size 0 (Nick Craig-Wood)</li>
+<li>Update t3rm1n4l/go-mega - fixes mega: couldn't login: crypto/aes:
+invalid key size 0 (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Mount
 <ul>
 <li>Enable async reads for a 20% speedup (Nick Craig-Wood)</li>
-<li>Replace use of WriteAt with Write for cache mode &gt;= writes and O_APPEND (Brett Dutro)</li>
+<li>Replace use of WriteAt with Write for cache mode &gt;= writes and
+O_APPEND (Brett Dutro)</li>
 <li>Make sure we call unmount when exiting (Nick Craig-Wood)</li>
-<li>Don't build on go1.10 as bazil/fuse no longer supports it (Nick Craig-Wood)</li>
+<li>Don't build on go1.10 as bazil/fuse no longer supports it (Nick
+Craig-Wood)</li>
 <li>When setting dates discard out of range dates (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Add a newly created file straight into the directory (Nick Craig-Wood)</li>
-<li>Only calculate one hash for reads for a speedup (Nick Craig-Wood)</li>
-<li>Make ReadAt for non cached files work better with non-sequential reads (Nick Craig-Wood)</li>
+<li>Add a newly created file straight into the directory (Nick
+Craig-Wood)</li>
+<li>Only calculate one hash for reads for a speedup (Nick
+Craig-Wood)</li>
+<li>Make ReadAt for non cached files work better with non-sequential
+reads (Nick Craig-Wood)</li>
 <li>Fix edge cases when reading ModTime from file (Nick Craig-Wood)</li>
-<li>Make sure existing files opened for write show correct size (Nick Craig-Wood)</li>
-<li>Don't cache the path in RW file objects to fix renaming (Nick Craig-Wood)</li>
-<li>Fix rename of open files when using the VFS cache (Nick Craig-Wood)</li>
-<li>When renaming files in the cache, rename the cache item in memory too (Nick Craig-Wood)</li>
-<li>Fix open file renaming on drive when using <code>--vfs-cache-mode writes</code> (Nick Craig-Wood)</li>
-<li>Fix incorrect modtime for mv into mount with <code>--vfs-cache-modes writes</code> (Nick Craig-Wood)</li>
-<li>On rename, rename in cache too if the file exists (Anagh Kumar Baranwal)</li>
+<li>Make sure existing files opened for write show correct size (Nick
+Craig-Wood)</li>
+<li>Don't cache the path in RW file objects to fix renaming (Nick
+Craig-Wood)</li>
+<li>Fix rename of open files when using the VFS cache (Nick
+Craig-Wood)</li>
+<li>When renaming files in the cache, rename the cache item in memory
+too (Nick Craig-Wood)</li>
+<li>Fix open file renaming on drive when using
+<code>--vfs-cache-mode writes</code> (Nick Craig-Wood)</li>
+<li>Fix incorrect modtime for mv into mount with
+<code>--vfs-cache-modes writes</code> (Nick Craig-Wood)</li>
+<li>On rename, rename in cache too if the file exists (Anagh Kumar
+Baranwal)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Make source file being updated errors be NoLowLevelRetry errors (Nick Craig-Wood)</li>
+<li>Make source file being updated errors be NoLowLevelRetry errors
+(Nick Craig-Wood)</li>
 <li>Fix update of hidden files on Windows (Nick Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
-<li>Follow move of upstream library github.com/coreos/bbolt github.com/etcd-io/bbolt (Nick Craig-Wood)</li>
-<li>Fix <code>fatal error: concurrent map writes</code> (Nick Craig-Wood)</li>
+<li>Follow move of upstream library github.com/coreos/bbolt
+github.com/etcd-io/bbolt (Nick Craig-Wood)</li>
+<li>Fix <code>fatal error: concurrent map writes</code> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
@@ -41827,22 +58784,30 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Add <code>--drive-stop-on-upload-limit</code> flag to stop syncs when upload limit reached (Nick Craig-Wood)</li>
-<li>Add <code>--drive-use-shared-date</code> to use date file was shared instead of modified date (Garry McNulty)</li>
-<li>Make sure invalid auth for teamdrives always reports an error (Nick Craig-Wood)</li>
-<li>Fix <code>--fast-list</code> when using appDataFolder (Nick Craig-Wood)</li>
-<li>Use multipart resumable uploads for streaming and uploads in mount (Nick Craig-Wood)</li>
-<li>Log an ERROR if an incomplete search is returned (Nick Craig-Wood)</li>
+<li>Add <code>--drive-stop-on-upload-limit</code> flag to stop syncs
+when upload limit reached (Nick Craig-Wood)</li>
+<li>Add <code>--drive-use-shared-date</code> to use date file was shared
+instead of modified date (Garry McNulty)</li>
+<li>Make sure invalid auth for teamdrives always reports an error (Nick
+Craig-Wood)</li>
+<li>Fix <code>--fast-list</code> when using appDataFolder (Nick
+Craig-Wood)</li>
+<li>Use multipart resumable uploads for streaming and uploads in mount
+(Nick Craig-Wood)</li>
+<li>Log an ERROR if an incomplete search is returned (Nick
+Craig-Wood)</li>
 <li>Hide dangerous config from the configurator (Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Treat <code>insufficient_space</code> errors as non retriable errors (Nick Craig-Wood)</li>
+<li>Treat <code>insufficient_space</code> errors as non retriable errors
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
 <li>Use new auth method used by official client (buengese)</li>
-<li>Add URL to generate Login Token to config wizard (Nick Craig-Wood)</li>
+<li>Add URL to generate Login Token to config wizard (Nick
+Craig-Wood)</li>
 <li>Add support whitelabel versions (buengese)</li>
 </ul></li>
 <li>Koofr
@@ -41860,12 +58825,17 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Re-implement multipart upload to fix memory issues (Nick Craig-Wood)</li>
-<li>Add <code>--s3-copy-cutoff</code> for size to switch to multipart copy (Nick Craig-Wood)</li>
+<li>Re-implement multipart upload to fix memory issues (Nick
+Craig-Wood)</li>
+<li>Add <code>--s3-copy-cutoff</code> for size to switch to multipart
+copy (Nick Craig-Wood)</li>
 <li>Add new region Asia Pacific (Hong Kong) (Outvi V)</li>
-<li>Reduce memory usage streaming files by reducing max stream upload size (Nick Craig-Wood)</li>
-<li>Add <code>--s3-list-chunk</code> option for bucket listing (Thomas Kriechbaumer)</li>
-<li>Force path style bucket access to off for AWS deprecation (Nick Craig-Wood)</li>
+<li>Reduce memory usage streaming files by reducing max stream upload
+size (Nick Craig-Wood)</li>
+<li>Add <code>--s3-list-chunk</code> option for bucket listing (Thomas
+Kriechbaumer)</li>
+<li>Force path style bucket access to off for AWS deprecation (Nick
+Craig-Wood)</li>
 <li>Use AWS web identity role provider if available (Tennix)</li>
 <li>Add StackPath Object Storage Support (Dave Koston)</li>
 <li>Fix ExpiryWindow value (Aleksandar Jankovic)</li>
@@ -41874,21 +58844,26 @@ $ tree /tmp/c
 </ul></li>
 <li>SFTP
 <ul>
-<li>Add <code>--sftp-skip-links</code> to skip symlinks and non regular files (Nick Craig-Wood)</li>
+<li>Add <code>--sftp-skip-links</code> to skip symlinks and non regular
+files (Nick Craig-Wood)</li>
 <li>Retry Creation of Connection (Sebastian Brandt)</li>
-<li>Fix "failed to parse private key file: ssh: not an encrypted key" error (Nick Craig-Wood)</li>
-<li>Open files for update write only to fix AWS SFTP interop (Nick Craig-Wood)</li>
+<li>Fix "failed to parse private key file: ssh: not an encrypted key"
+error (Nick Craig-Wood)</li>
+<li>Open files for update write only to fix AWS SFTP interop (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Reserve segments of dynamic large object when delete objects in container what was enabled versioning. (Nguyễn Hữu Luân)</li>
+<li>Reserve segments of dynamic large object when delete objects in
+container what was enabled versioning. (Nguyễn Hữu Luân)</li>
 <li>Fix parsing of X-Object-Manifest (Nick Craig-Wood)</li>
 <li>Update OVH API endpoint (unbelauscht)</li>
 </ul></li>
 <li>WebDAV
 <ul>
 <li>Make nextcloud only upload SHA1 checksums (Nick Craig-Wood)</li>
-<li>Fix case of "Bearer" in Authorization: header to agree with RFC (Nick Craig-Wood)</li>
+<li>Fix case of "Bearer" in Authorization: header to agree with RFC
+(Nick Craig-Wood)</li>
 <li>Add Referer header to fix problems with WAFs (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
@@ -41896,21 +58871,27 @@ $ tree /tmp/c
 <ul>
 <li>Bug Fixes
 <ul>
-<li>accounting: Fix memory leak on retries operations (Nick Craig-Wood)</li>
+<li>accounting: Fix memory leak on retries operations (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Fix listing of the root directory with drive.files scope (Nick Craig-Wood)</li>
-<li>Fix --drive-root-folder-id with team/shared drives (Nick Craig-Wood)</li>
+<li>Fix listing of the root directory with drive.files scope (Nick
+Craig-Wood)</li>
+<li>Fix --drive-root-folder-id with team/shared drives (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.50.1---2019-11-02">v1.50.1 - 2019-11-02</h2>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>hash: Fix accidentally changed hash names for <code>DropboxHash</code> and <code>CRC-32</code> (Nick Craig-Wood)</li>
-<li>fshttp: Fix error reporting on tpslimit token bucket errors (Nick Craig-Wood)</li>
-<li>fshttp: Don't print token bucket errors on context cancelled (Nick Craig-Wood)</li>
+<li>hash: Fix accidentally changed hash names for
+<code>DropboxHash</code> and <code>CRC-32</code> (Nick Craig-Wood)</li>
+<li>fshttp: Fix error reporting on tpslimit token bucket errors (Nick
+Craig-Wood)</li>
+<li>fshttp: Don't print token bucket errors on context cancelled (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
@@ -41925,17 +58906,27 @@ $ tree /tmp/c
 <ul>
 <li>New backends
 <ul>
-<li><a href="https://rclone.org/sharefile/">Citrix Sharefile</a> (Nick Craig-Wood)</li>
-<li><a href="https://rclone.org/chunker/">Chunker</a> - an overlay backend to split files into smaller parts (Ivan Andreev)</li>
-<li><a href="https://rclone.org/mailru/">Mail.ru Cloud</a> (Ivan Andreev)</li>
+<li><a href="https://rclone.org/sharefile/">Citrix Sharefile</a> (Nick
+Craig-Wood)</li>
+<li><a href="https://rclone.org/chunker/">Chunker</a> - an overlay
+backend to split files into smaller parts (Ivan Andreev)</li>
+<li><a href="https://rclone.org/mailru/">Mail.ru Cloud</a> (Ivan
+Andreev)</li>
 </ul></li>
 <li>New Features
 <ul>
 <li>encodings (Fabian Möller &amp; Nick Craig-Wood)
 <ul>
-<li>All backends now use file name encoding to ensure any file name can be written to any backend.</li>
-<li>See the <a href="https://rclone.org/overview/#restricted-filenames">restricted file name docs</a> for more info and the <a href="/local/#filenames">local backend docs</a>.</li>
-<li>Some file names may look different in rclone if you are using any control characters in names or <a href="https://en.wikipedia.org/wiki/Halfwidth_and_Fullwidth_Forms_(Unicode_block)">unicode FULLWIDTH symbols</a>.</li>
+<li>All backends now use file name encoding to ensure any file name can
+be written to any backend.</li>
+<li>See the <a
+href="https://rclone.org/overview/#restricted-filenames">restricted file
+name docs</a> for more info and the <a href="/local/#filenames">local
+backend docs</a>.</li>
+<li>Some file names may look different in rclone if you are using any
+control characters in names or <a
+href="https://en.wikipedia.org/wiki/Halfwidth_and_Fullwidth_Forms_(Unicode_block)">unicode
+FULLWIDTH symbols</a>.</li>
 </ul></li>
 <li>build
 <ul>
@@ -41945,11 +58936,14 @@ $ tree /tmp/c
 <li>Convert python scripts to python3 (Nick Craig-Wood)</li>
 <li>Swap Azure/go-ansiterm for mattn/go-colorable (Nick Craig-Wood)</li>
 <li>Dockerfile fixes (Matei David)</li>
-<li>Add <a href="https://github.com/rclone/rclone/blob/master/CONTRIBUTING.md#writing-a-plugin">plugin support</a> for backends and commands (Richard Patel)</li>
+<li>Add <a
+href="https://github.com/rclone/rclone/blob/master/CONTRIBUTING.md#writing-a-plugin">plugin
+support</a> for backends and commands (Richard Patel)</li>
 </ul></li>
 <li>config
 <ul>
-<li>Use alternating Red/Green in config to make more obvious (Nick Craig-Wood)</li>
+<li>Use alternating Red/Green in config to make more obvious (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>contrib
 <ul>
@@ -41958,7 +58952,8 @@ $ tree /tmp/c
 </ul></li>
 <li>copyurl
 <ul>
-<li>Add <code>--auto-filename</code> flag for using file name from URL in destination path (Denis)</li>
+<li>Add <code>--auto-filename</code> flag for using file name from URL
+in destination path (Denis)</li>
 </ul></li>
 <li>serve dlna:
 <ul>
@@ -41974,55 +58969,81 @@ $ tree /tmp/c
 <ul>
 <li>sync
 <ul>
-<li>Make <code>--update</code>/<code>-u</code> not transfer files that haven't changed (Nick Craig-Wood)</li>
-<li>Free objects after they come out of the transfer pipe to save memory (Nick Craig-Wood)</li>
-<li>Fix <code>--files-from without --no-traverse</code> doing a recursive scan (Nick Craig-Wood)</li>
+<li>Make <code>--update</code>/<code>-u</code> not transfer files that
+haven't changed (Nick Craig-Wood)</li>
+<li>Free objects after they come out of the transfer pipe to save memory
+(Nick Craig-Wood)</li>
+<li>Fix <code>--files-from without --no-traverse</code> doing a
+recursive scan (Nick Craig-Wood)</li>
 </ul></li>
 <li>operations
 <ul>
 <li>Fix accounting for server-side copies (Nick Craig-Wood)</li>
-<li>Display 'All duplicates removed' only if dedupe successful (Sezal Agrawal)</li>
-<li>Display 'Deleted X extra copies' only if dedupe successful (Sezal Agrawal)</li>
+<li>Display 'All duplicates removed' only if dedupe successful (Sezal
+Agrawal)</li>
+<li>Display 'Deleted X extra copies' only if dedupe successful (Sezal
+Agrawal)</li>
 </ul></li>
 <li>accounting
 <ul>
-<li>Only allow up to 100 completed transfers in the accounting list to save memory (Nick Craig-Wood)</li>
-<li>Cull the old time ranges when possible to save memory (Nick Craig-Wood)</li>
+<li>Only allow up to 100 completed transfers in the accounting list to
+save memory (Nick Craig-Wood)</li>
+<li>Cull the old time ranges when possible to save memory (Nick
+Craig-Wood)</li>
 <li>Fix panic due to server-side copy fallback (Ivan Andreev)</li>
-<li>Fix memory leak noticeable for transfers of large numbers of objects (Nick Craig-Wood)</li>
+<li>Fix memory leak noticeable for transfers of large numbers of objects
+(Nick Craig-Wood)</li>
 <li>Fix total duration calculation (Nick Craig-Wood)</li>
 </ul></li>
 <li>cmd
 <ul>
-<li>Fix environment variables not setting command line flags (Nick Craig-Wood)</li>
-<li>Make autocomplete compatible with bash's posix mode for macOS (Danil Semelenov)</li>
-<li>Make <code>--progress</code> work in git bash on Windows (Nick Craig-Wood)</li>
-<li>Fix 'compopt: command not found' on autocomplete on macOS (Danil Semelenov)</li>
+<li>Fix environment variables not setting command line flags (Nick
+Craig-Wood)</li>
+<li>Make autocomplete compatible with bash's posix mode for macOS (Danil
+Semelenov)</li>
+<li>Make <code>--progress</code> work in git bash on Windows (Nick
+Craig-Wood)</li>
+<li>Fix 'compopt: command not found' on autocomplete on macOS (Danil
+Semelenov)</li>
 </ul></li>
 <li>config
 <ul>
-<li>Fix setting of non top level flags from environment variables (Nick Craig-Wood)</li>
-<li>Check config names more carefully and report errors (Nick Craig-Wood)</li>
-<li>Remove error: can't use <code>--size-only</code> and <code>--ignore-size</code> together. (Nick Craig-Wood)</li>
+<li>Fix setting of non top level flags from environment variables (Nick
+Craig-Wood)</li>
+<li>Check config names more carefully and report errors (Nick
+Craig-Wood)</li>
+<li>Remove error: can't use <code>--size-only</code> and
+<code>--ignore-size</code> together. (Nick Craig-Wood)</li>
 </ul></li>
-<li>filter: Prevent mixing options when <code>--files-from</code> is in use (Michele Caci)</li>
-<li>serve sftp: Fix crash on unsupported operations (e.g. Readlink) (Nick Craig-Wood)</li>
+<li>filter: Prevent mixing options when <code>--files-from</code> is in
+use (Michele Caci)</li>
+<li>serve sftp: Fix crash on unsupported operations (e.g. Readlink)
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Allow files of unknown size to be read properly (Nick Craig-Wood)</li>
+<li>Allow files of unknown size to be read properly (Nick
+Craig-Wood)</li>
 <li>Skip tests on &lt;= 2 CPUs to avoid lockup (Nick Craig-Wood)</li>
 <li>Fix panic on File.Open (Nick Craig-Wood)</li>
-<li>Fix "mount_fusefs: -o timeout=: option not supported" on FreeBSD (Nick Craig-Wood)</li>
-<li>Don't pass huge filenames (&gt;4k) to FUSE as it can't cope (Nick Craig-Wood)</li>
+<li>Fix "mount_fusefs: -o timeout=: option not supported" on FreeBSD
+(Nick Craig-Wood)</li>
+<li>Don't pass huge filenames (&gt;4k) to FUSE as it can't cope (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Add flag <code>--vfs-case-insensitive</code> for windows/macOS mounts (Ivan Andreev)</li>
-<li>Make objects of unknown size readable through the VFS (Nick Craig-Wood)</li>
-<li>Move writeback of dirty data out of close() method into its own method (FlushWrites) and remove close() call from Flush() (Brett Dutro)</li>
-<li>Stop empty dirs disappearing when renamed on bucket-based remotes (Nick Craig-Wood)</li>
-<li>Stop change notify polling clearing so much of the directory cache (Nick Craig-Wood)</li>
+<li>Add flag <code>--vfs-case-insensitive</code> for windows/macOS
+mounts (Ivan Andreev)</li>
+<li>Make objects of unknown size readable through the VFS (Nick
+Craig-Wood)</li>
+<li>Move writeback of dirty data out of close() method into its own
+method (FlushWrites) and remove close() call from Flush() (Brett
+Dutro)</li>
+<li>Stop empty dirs disappearing when renamed on bucket-based remotes
+(Nick Craig-Wood)</li>
+<li>Stop change notify polling clearing so much of the directory cache
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
@@ -42030,7 +59051,8 @@ $ tree /tmp/c
 </ul></li>
 <li>B2
 <ul>
-<li>Remove <code>unverified:</code> prefix on sha1 to improve interop (e.g. with CyberDuck) (Nick Craig-Wood)</li>
+<li>Remove <code>unverified:</code> prefix on sha1 to improve interop
+(e.g. with CyberDuck) (Nick Craig-Wood)</li>
 </ul></li>
 <li>Box
 <ul>
@@ -42038,11 +59060,15 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Disable HTTP/2 by default to work around INTERNAL_ERROR problems (Nick Craig-Wood)</li>
-<li>Make sure that drive root ID is always canonical (Nick Craig-Wood)</li>
-<li>Fix <code>--drive-shared-with-me</code> from the root with lsand <code>--fast-list</code> (Nick Craig-Wood)</li>
+<li>Disable HTTP/2 by default to work around INTERNAL_ERROR problems
+(Nick Craig-Wood)</li>
+<li>Make sure that drive root ID is always canonical (Nick
+Craig-Wood)</li>
+<li>Fix <code>--drive-shared-with-me</code> from the root with lsand
+<code>--fast-list</code> (Nick Craig-Wood)</li>
 <li>Fix ChangeNotify polling for shared drives (Nick Craig-Wood)</li>
-<li>Fix change notify polling when using appDataFolder (Nick Craig-Wood)</li>
+<li>Fix change notify polling when using appDataFolder (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -42051,7 +59077,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Fichier
 <ul>
-<li>Fix accessing files &gt; 2GB on 32 bit systems (Nick Craig-Wood)</li>
+<li>Fix accessing files &gt; 2GB on 32 bit systems (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
@@ -42060,7 +59087,8 @@ $ tree /tmp/c
 <li>HTTP
 <ul>
 <li>HEAD directory entries in parallel to speedup (Nick Craig-Wood)</li>
-<li>Add <code>--http-no-head</code> to stop rclone doing HEAD in listings (Nick Craig-Wood)</li>
+<li>Add <code>--http-no-head</code> to stop rclone doing HEAD in
+listings (Nick Craig-Wood)</li>
 </ul></li>
 <li>Putio
 <ul>
@@ -42070,16 +59098,21 @@ $ tree /tmp/c
 <ul>
 <li>Fix signature v2_auth headers (Anthony Rusdi)</li>
 <li>Fix encoding for control characters (Nick Craig-Wood)</li>
-<li>Only ask for URL encoded directory listings if we need them on Ceph (Nick Craig-Wood)</li>
-<li>Add option for multipart failure behaviour (Aleksandar Jankovic)</li>
+<li>Only ask for URL encoded directory listings if we need them on Ceph
+(Nick Craig-Wood)</li>
+<li>Add option for multipart failure behaviour (Aleksandar
+Jankovic)</li>
 <li>Support for multipart copy (庄天翼)</li>
-<li>Fix nil pointer reference if no metadata returned for object (Nick Craig-Wood)</li>
+<li>Fix nil pointer reference if no metadata returned for object (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>SFTP
 <ul>
-<li>Fix <code>--sftp-ask-password</code> trying to contact the ssh agent (Nick Craig-Wood)</li>
+<li>Fix <code>--sftp-ask-password</code> trying to contact the ssh agent
+(Nick Craig-Wood)</li>
 <li>Fix hashes of files with backslashes (Nick Craig-Wood)</li>
-<li>Include more ciphers with <code>--sftp-use-insecure-cipher</code> (Carlos Ferreyra)</li>
+<li>Include more ciphers with <code>--sftp-use-insecure-cipher</code>
+(Carlos Ferreyra)</li>
 </ul></li>
 <li>WebDAV
 <ul>
@@ -42090,8 +59123,10 @@ $ tree /tmp/c
 <ul>
 <li>Bug Fixes
 <ul>
-<li>Revert back to go1.12.x for the v1.49.x builds as go1.13.x was causing issues (Nick Craig-Wood)</li>
-<li>Fix rpm packages by using master builds of nfpm (Nick Craig-Wood)</li>
+<li>Revert back to go1.12.x for the v1.49.x builds as go1.13.x was
+causing issues (Nick Craig-Wood)</li>
+<li>Fix rpm packages by using master builds of nfpm (Nick
+Craig-Wood)</li>
 <li>Fix macOS build after brew changes (Nick Craig-Wood)</li>
 </ul></li>
 </ul>
@@ -42101,15 +59136,18 @@ $ tree /tmp/c
 <ul>
 <li>cmd/rcd: Address ZipSlip vulnerability (Richard Patel)</li>
 <li>accounting: Fix file handle leak on errors (Nick Craig-Wood)</li>
-<li>oauthutil: Fix security problem when running with two users on the same machine (Nick Craig-Wood)</li>
+<li>oauthutil: Fix security problem when running with two users on the
+same machine (Nick Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Fix listing of an empty root returning: error dir not found (Nick Craig-Wood)</li>
+<li>Fix listing of an empty root returning: error dir not found (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Fix SetModTime on GLACIER/ARCHIVE objects and implement set/get tier (Nick Craig-Wood)</li>
+<li>Fix SetModTime on GLACIER/ARCHIVE objects and implement set/get tier
+(Nick Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.49.3---2019-09-15">v1.49.3 - 2019-09-15</h2>
@@ -42131,21 +59169,26 @@ $ tree /tmp/c
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>accounting: Fix locking in Transfer to avoid deadlock with <code>--progress</code> (Nick Craig-Wood)</li>
+<li>accounting: Fix locking in Transfer to avoid deadlock with
+<code>--progress</code> (Nick Craig-Wood)</li>
 <li>docs: Fix template argument for mktemp in install.sh (Cnly)</li>
-<li>operations: Fix <code>-u</code>/<code>--update</code> with google photos / files of unknown size (Nick Craig-Wood)</li>
-<li>rc: Fix docs for config/create /update /password (Nick Craig-Wood)</li>
+<li>operations: Fix <code>-u</code>/<code>--update</code> with google
+photos / files of unknown size (Nick Craig-Wood)</li>
+<li>rc: Fix docs for config/create /update /password (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Fix need for elevated permissions on SetModTime (Nick Craig-Wood)</li>
+<li>Fix need for elevated permissions on SetModTime (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.49.1---2019-08-28">v1.49.1 - 2019-08-28</h2>
 <ul>
 <li>Bug Fixes
 <ul>
-<li>config: Fix generated passwords being stored as empty password (Nick Craig-Wood)</li>
+<li>config: Fix generated passwords being stored as empty password (Nick
+Craig-Wood)</li>
 <li>rcd: Added missing parameter for web-gui info logs. (Chaitanya)</li>
 </ul></li>
 <li>Googlephotos
@@ -42161,63 +59204,88 @@ $ tree /tmp/c
 <ul>
 <li>New backends
 <ul>
-<li><a href="https://rclone.org/fichier/">1fichier</a> (Laura Hausmann)</li>
-<li><a href="https://rclone.org/googlephotos/">Google Photos</a> (Nick Craig-Wood)</li>
+<li><a href="https://rclone.org/fichier/">1fichier</a> (Laura
+Hausmann)</li>
+<li><a href="https://rclone.org/googlephotos/">Google Photos</a> (Nick
+Craig-Wood)</li>
 <li><a href="https://rclone.org/putio/">Putio</a> (Cenk Alti)</li>
-<li><a href="https://rclone.org/premiumizeme/">premiumize.me</a> (Nick Craig-Wood)</li>
+<li><a href="https://rclone.org/premiumizeme/">premiumize.me</a> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li>Experimental <a href="https://rclone.org/gui/">web GUI</a> (Chaitanya Bankanhal)</li>
-<li>Implement <code>--compare-dest</code> &amp; <code>--copy-dest</code> (yparitcher)</li>
-<li>Implement <code>--suffix</code> without <code>--backup-dir</code> for backup to current dir (yparitcher)</li>
-<li><code>config reconnect</code> to re-login (re-run the oauth login) for the backend. (Nick Craig-Wood)</li>
-<li><code>config userinfo</code> to discover which user you are logged in as. (Nick Craig-Wood)</li>
-<li><code>config disconnect</code> to disconnect you (log out) from the backend. (Nick Craig-Wood)</li>
+<li>Experimental <a href="https://rclone.org/gui/">web GUI</a>
+(Chaitanya Bankanhal)</li>
+<li>Implement <code>--compare-dest</code> &amp; <code>--copy-dest</code>
+(yparitcher)</li>
+<li>Implement <code>--suffix</code> without <code>--backup-dir</code>
+for backup to current dir (yparitcher)</li>
+<li><code>config reconnect</code> to re-login (re-run the oauth login)
+for the backend. (Nick Craig-Wood)</li>
+<li><code>config userinfo</code> to discover which user you are logged
+in as. (Nick Craig-Wood)</li>
+<li><code>config disconnect</code> to disconnect you (log out) from the
+backend. (Nick Craig-Wood)</li>
 <li>Add <code>--use-json-log</code> for JSON logging (justinalin)</li>
 <li>Add context propagation to rclone (Aleksandar Jankovic)</li>
-<li>Reworking internal statistics interfaces so they work with rc jobs (Aleksandar Jankovic)</li>
+<li>Reworking internal statistics interfaces so they work with rc jobs
+(Aleksandar Jankovic)</li>
 <li>Add Higher units for ETA (AbelThar)</li>
 <li>Update rclone logos to new design (Andreas Chlupka)</li>
 <li>hash: Add CRC-32 support (Cenk Alti)</li>
-<li>help showbackend: Fixed advanced option category when there are no standard options (buengese)</li>
+<li>help showbackend: Fixed advanced option category when there are no
+standard options (buengese)</li>
 <li>ncdu: Display/Copy to Clipboard Current Path (Gary Kim)</li>
 <li>operations:
 <ul>
 <li>Run hashing operations in parallel (Nick Craig-Wood)</li>
-<li>Don't calculate checksums when using <code>--ignore-checksum</code> (Nick Craig-Wood)</li>
-<li>Check transfer hashes when using <code>--size-only</code> mode (Nick Craig-Wood)</li>
-<li>Disable multi thread copy for local to local copies (Nick Craig-Wood)</li>
+<li>Don't calculate checksums when using <code>--ignore-checksum</code>
+(Nick Craig-Wood)</li>
+<li>Check transfer hashes when using <code>--size-only</code> mode (Nick
+Craig-Wood)</li>
+<li>Disable multi thread copy for local to local copies (Nick
+Craig-Wood)</li>
 <li>Debug successful hashes as well as failures (Nick Craig-Wood)</li>
 </ul></li>
 <li>rc
 <ul>
 <li>Add ability to stop async jobs (Aleksandar Jankovic)</li>
-<li>Return current settings if core/bwlimit called without parameters (Nick Craig-Wood)</li>
+<li>Return current settings if core/bwlimit called without parameters
+(Nick Craig-Wood)</li>
 <li>Rclone-WebUI integration with rclone (Chaitanya Bankanhal)</li>
-<li>Added command line parameter to control the cross origin resource sharing (CORS) in the rcd. (Security Improvement) (Chaitanya Bankanhal)</li>
-<li>Add anchor tags to the docs so links are consistent (Nick Craig-Wood)</li>
-<li>Remove _async key from input parameters after parsing so later operations won't get confused (buengese)</li>
+<li>Added command line parameter to control the cross origin resource
+sharing (CORS) in the rcd. (Security Improvement) (Chaitanya
+Bankanhal)</li>
+<li>Add anchor tags to the docs so links are consistent (Nick
+Craig-Wood)</li>
+<li>Remove _async key from input parameters after parsing so later
+operations won't get confused (buengese)</li>
 <li>Add call to clear stats (Aleksandar Jankovic)</li>
 </ul></li>
 <li>rcd
 <ul>
 <li>Auto-login for web-gui (Chaitanya Bankanhal)</li>
-<li>Implement <code>--baseurl</code> for rcd and web-gui (Chaitanya Bankanhal)</li>
+<li>Implement <code>--baseurl</code> for rcd and web-gui (Chaitanya
+Bankanhal)</li>
 </ul></li>
 <li>serve dlna
 <ul>
-<li>Only select interfaces which can multicast for SSDP (Nick Craig-Wood)</li>
-<li>Add more builtin mime types to cover standard audio/video (Nick Craig-Wood)</li>
-<li>Fix missing mime types on Android causing missing videos (Nick Craig-Wood)</li>
+<li>Only select interfaces which can multicast for SSDP (Nick
+Craig-Wood)</li>
+<li>Add more builtin mime types to cover standard audio/video (Nick
+Craig-Wood)</li>
+<li>Fix missing mime types on Android causing missing videos (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>serve ftp
 <ul>
-<li>Refactor to bring into line with other serve commands (Nick Craig-Wood)</li>
+<li>Refactor to bring into line with other serve commands (Nick
+Craig-Wood)</li>
 <li>Implement <code>--auth-proxy</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>serve http: Implement <code>--baseurl</code> (Nick Craig-Wood)</li>
-<li>serve restic: Implement <code>--baseurl</code> (Nick Craig-Wood)</li>
+<li>serve restic: Implement <code>--baseurl</code> (Nick
+Craig-Wood)</li>
 <li>serve sftp
 <ul>
 <li>Implement auth proxy (Nick Craig-Wood)</li>
@@ -42232,52 +59300,67 @@ $ tree /tmp/c
 <li>Bug Fixes
 <ul>
 <li>Make "bad record MAC" a retriable error (Nick Craig-Wood)</li>
-<li>copyurl: Fix copying files that return HTTP errors (Nick Craig-Wood)</li>
-<li>march: Fix checking sub-directories when using <code>--no-traverse</code> (buengese)</li>
+<li>copyurl: Fix copying files that return HTTP errors (Nick
+Craig-Wood)</li>
+<li>march: Fix checking sub-directories when using
+<code>--no-traverse</code> (buengese)</li>
 <li>rc
 <ul>
-<li>Fix unmarshalable http.AuthFn in options and put in test for marshalability (Nick Craig-Wood)</li>
-<li>Move job expire flags to rc to fix initialization problem (Nick Craig-Wood)</li>
-<li>Fix <code>--loopback</code> with rc/list and others (Nick Craig-Wood)</li>
+<li>Fix unmarshalable http.AuthFn in options and put in test for
+marshalability (Nick Craig-Wood)</li>
+<li>Move job expire flags to rc to fix initialization problem (Nick
+Craig-Wood)</li>
+<li>Fix <code>--loopback</code> with rc/list and others (Nick
+Craig-Wood)</li>
 </ul></li>
-<li>rcat: Fix slowdown on systems with multiple hashes (Nick Craig-Wood)</li>
-<li>rcd: Fix permissions problems on cache directory with web gui download (Nick Craig-Wood)</li>
+<li>rcat: Fix slowdown on systems with multiple hashes (Nick
+Craig-Wood)</li>
+<li>rcd: Fix permissions problems on cache directory with web gui
+download (Nick Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Default <code>--daemon-timeout</code> to 15 minutes on macOS and FreeBSD (Nick Craig-Wood)</li>
-<li>Update docs to show mounting from root OK for bucket-based (Nick Craig-Wood)</li>
+<li>Default <code>--daemon-timeout</code> to 15 minutes on macOS and
+FreeBSD (Nick Craig-Wood)</li>
+<li>Update docs to show mounting from root OK for bucket-based (Nick
+Craig-Wood)</li>
 <li>Remove nonseekable flag from write files (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
 <li>Make write without cache more efficient (Nick Craig-Wood)</li>
-<li>Fix <code>--vfs-cache-mode minimal</code> and <code>writes</code> ignoring cached files (Nick Craig-Wood)</li>
+<li>Fix <code>--vfs-cache-mode minimal</code> and <code>writes</code>
+ignoring cached files (Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Add <code>--local-case-sensitive</code> and <code>--local-case-insensitive</code> (Nick Craig-Wood)</li>
-<li>Avoid polluting page cache when uploading local files to remote backends (Michał Matczuk)</li>
+<li>Add <code>--local-case-sensitive</code> and
+<code>--local-case-insensitive</code> (Nick Craig-Wood)</li>
+<li>Avoid polluting page cache when uploading local files to remote
+backends (Michał Matczuk)</li>
 <li>Don't calculate any hashes by default (Nick Craig-Wood)</li>
 <li>Fadvise run syscall on a dedicated go routine (Michał Matczuk)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
 <li>Azure Storage Emulator support (Sandeep)</li>
-<li>Updated config help details to remove connection string references (Sandeep)</li>
+<li>Updated config help details to remove connection string references
+(Sandeep)</li>
 <li>Make all operations work from the root (Nick Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
 <li>Implement link sharing (yparitcher)</li>
-<li>Enable server-side copy to copy between buckets (Nick Craig-Wood)</li>
+<li>Enable server-side copy to copy between buckets (Nick
+Craig-Wood)</li>
 <li>Make all operations work from the root (Nick Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
 <li>Fix server-side copy of big files (Nick Craig-Wood)</li>
 <li>Update API for teamdrive use (Nick Craig-Wood)</li>
-<li>Add error for purge with <code>--drive-trashed-only</code> (ginvine)</li>
+<li>Add error for purge with <code>--drive-trashed-only</code>
+(ginvine)</li>
 </ul></li>
 <li>Fichier
 <ul>
@@ -42285,12 +59368,14 @@ $ tree /tmp/c
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Reduce oauth scope requested as suggested by Google (Nick Craig-Wood)</li>
+<li>Reduce oauth scope requested as suggested by Google (Nick
+Craig-Wood)</li>
 <li>Make all operations work from the root (Nick Craig-Wood)</li>
 </ul></li>
 <li>HTTP
 <ul>
-<li>Add <code>--http-headers</code> flag for setting arbitrary headers (Nick Craig-Wood)</li>
+<li>Add <code>--http-headers</code> flag for setting arbitrary headers
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
@@ -42303,7 +59388,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Opendrive
 <ul>
-<li>Refactor to use existing lib/rest facilities for uploads (Nick Craig-Wood)</li>
+<li>Refactor to use existing lib/rest facilities for uploads (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Qingstor
 <ul>
@@ -42318,23 +59404,32 @@ $ tree /tmp/c
 <li>SFTP
 <ul>
 <li>Add missing interface check and fix About (Nick Craig-Wood)</li>
-<li>Completely ignore all modtime checks if SetModTime=false (Jon Fautley)</li>
+<li>Completely ignore all modtime checks if SetModTime=false (Jon
+Fautley)</li>
 <li>Support md5/sha1 with rsync.net (Nick Craig-Wood)</li>
-<li>Save the md5/sha1 command in use to the config file for efficiency (Nick Craig-Wood)</li>
-<li>Opt-in support for diffie-hellman-group-exchange-sha256 diffie-hellman-group-exchange-sha1 (Yi FU)</li>
+<li>Save the md5/sha1 command in use to the config file for efficiency
+(Nick Craig-Wood)</li>
+<li>Opt-in support for diffie-hellman-group-exchange-sha256
+diffie-hellman-group-exchange-sha1 (Yi FU)</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Use FixRangeOption to fix 0 length files via the VFS (Nick Craig-Wood)</li>
-<li>Fix upload when using no_chunk to return the correct size (Nick Craig-Wood)</li>
+<li>Use FixRangeOption to fix 0 length files via the VFS (Nick
+Craig-Wood)</li>
+<li>Fix upload when using no_chunk to return the correct size (Nick
+Craig-Wood)</li>
 <li>Make all operations work from the root (Nick Craig-Wood)</li>
-<li>Fix segments leak during failed large file uploads. (nguyenhuuluan434)</li>
+<li>Fix segments leak during failed large file uploads.
+(nguyenhuuluan434)</li>
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Add <code>--webdav-bearer-token-command</code> (Nick Craig-Wood)</li>
-<li>Refresh token when it expires with <code>--webdav-bearer-token-command</code> (Nick Craig-Wood)</li>
-<li>Add docs for using bearer_token_command with oidc-agent (Paul Millar)</li>
+<li>Add <code>--webdav-bearer-token-command</code> (Nick
+Craig-Wood)</li>
+<li>Refresh token when it expires with
+<code>--webdav-bearer-token-command</code> (Nick Craig-Wood)</li>
+<li>Add docs for using bearer_token_command with oidc-agent (Paul
+Millar)</li>
 </ul></li>
 </ul>
 <h2 id="v1.48.0---2019-06-15">v1.48.0 - 2019-06-15</h2>
@@ -42347,50 +59442,71 @@ $ tree /tmp/c
 <ul>
 <li>Multi threaded downloads to local storage (Nick Craig-Wood)
 <ul>
-<li>controlled with <code>--multi-thread-cutoff</code> and <code>--multi-thread-streams</code></li>
+<li>controlled with <code>--multi-thread-cutoff</code> and
+<code>--multi-thread-streams</code></li>
 </ul></li>
-<li>Use rclone.conf from rclone executable directory to enable portable use (albertony)</li>
+<li>Use rclone.conf from rclone executable directory to enable portable
+use (albertony)</li>
 <li>Allow sync of a file and a directory with the same name (forgems)
 <ul>
 <li>this is common on bucket-based remotes, e.g. s3, gcs</li>
 </ul></li>
-<li>Add <code>--ignore-case-sync</code> for forced case insensitivity (garry415)</li>
-<li>Implement <code>--stats-one-line-date</code> and <code>--stats-one-line-date-format</code> (Peter Berbec)</li>
-<li>Log an ERROR for all commands which exit with non-zero status (Nick Craig-Wood)</li>
-<li>Use go-homedir to read the home directory more reliably (Nick Craig-Wood)</li>
-<li>Enable creating encrypted config through external script invocation (Wojciech Smigielski)</li>
+<li>Add <code>--ignore-case-sync</code> for forced case insensitivity
+(garry415)</li>
+<li>Implement <code>--stats-one-line-date</code> and
+<code>--stats-one-line-date-format</code> (Peter Berbec)</li>
+<li>Log an ERROR for all commands which exit with non-zero status (Nick
+Craig-Wood)</li>
+<li>Use go-homedir to read the home directory more reliably (Nick
+Craig-Wood)</li>
+<li>Enable creating encrypted config through external script invocation
+(Wojciech Smigielski)</li>
 <li>build: Drop support for go1.8 (Nick Craig-Wood)</li>
-<li>config: Make config create/update encrypt passwords where necessary (Nick Craig-Wood)</li>
-<li>copyurl: Honor <code>--no-check-certificate</code> (Stefan Breunig)</li>
+<li>config: Make config create/update encrypt passwords where necessary
+(Nick Craig-Wood)</li>
+<li>copyurl: Honor <code>--no-check-certificate</code> (Stefan
+Breunig)</li>
 <li>install: Linux skip man pages if no mandb (didil)</li>
 <li>lsf: Support showing the Tier of the object (Nick Craig-Wood)</li>
 <li>lsjson
 <ul>
 <li>Added EncryptedPath to output (calisro)</li>
 <li>Support showing the Tier of the object (Nick Craig-Wood)</li>
-<li>Add IsBucket field for bucket-based remote listing of the root (Nick Craig-Wood)</li>
+<li>Add IsBucket field for bucket-based remote listing of the root (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>rc
 <ul>
-<li>Add <code>--loopback</code> flag to run commands directly without a server (Nick Craig-Wood)</li>
-<li>Add operations/fsinfo: Return information about the remote (Nick Craig-Wood)</li>
+<li>Add <code>--loopback</code> flag to run commands directly without a
+server (Nick Craig-Wood)</li>
+<li>Add operations/fsinfo: Return information about the remote (Nick
+Craig-Wood)</li>
 <li>Skip auth for OPTIONS request (Nick Craig-Wood)</li>
-<li>cmd/providers: Add DefaultStr, ValueStr and Type fields (Nick Craig-Wood)</li>
-<li>jobs: Make job expiry timeouts configurable (Aleksandar Jankovic)</li>
+<li>cmd/providers: Add DefaultStr, ValueStr and Type fields (Nick
+Craig-Wood)</li>
+<li>jobs: Make job expiry timeouts configurable (Aleksandar
+Jankovic)</li>
 </ul></li>
 <li>serve dlna reworked and improved (Dan Walters)</li>
-<li>serve ftp: add <code>--ftp-public-ip</code> flag to specify public IP (calistri)</li>
-<li>serve restic: Add support for <code>--private-repos</code> in <code>serve restic</code> (Florian Apolloner)</li>
+<li>serve ftp: add <code>--ftp-public-ip</code> flag to specify public
+IP (calistri)</li>
+<li>serve restic: Add support for <code>--private-repos</code> in
+<code>serve restic</code> (Florian Apolloner)</li>
 <li>serve webdav: Combine serve webdav and serve http (Gary Kim)</li>
-<li>size: Ignore negative sizes when calculating total (Garry McNulty)</li>
+<li>size: Ignore negative sizes when calculating total (Garry
+McNulty)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>Make move and copy individual files obey <code>--backup-dir</code> (Nick Craig-Wood)</li>
-<li>If <code>--ignore-checksum</code> is in effect, don't calculate checksum (Nick Craig-Wood)</li>
+<li>Make move and copy individual files obey <code>--backup-dir</code>
+(Nick Craig-Wood)</li>
+<li>If <code>--ignore-checksum</code> is in effect, don't calculate
+checksum (Nick Craig-Wood)</li>
 <li>moveto: Fix case-insensitive same remote move (Gary Kim)</li>
-<li>rc: Fix serving bucket-based objects with <code>--rc-serve</code> (Nick Craig-Wood)</li>
-<li>serve webdav: Fix serveDir not being updated with changes from webdav (Gary Kim)</li>
+<li>rc: Fix serving bucket-based objects with <code>--rc-serve</code>
+(Nick Craig-Wood)</li>
+<li>serve webdav: Fix serveDir not being updated with changes from
+webdav (Gary Kim)</li>
 </ul></li>
 <li>Mount
 <ul>
@@ -42398,19 +59514,24 @@ $ tree /tmp/c
 </ul></li>
 <li>VFS
 <ul>
-<li>Make WriteAt for non cached files work with non-sequential writes (Nick Craig-Wood)</li>
+<li>Make WriteAt for non cached files work with non-sequential writes
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Only calculate the required hashes for big speedup (Nick Craig-Wood)</li>
-<li>Log errors when listing instead of returning an error (Nick Craig-Wood)</li>
+<li>Only calculate the required hashes for big speedup (Nick
+Craig-Wood)</li>
+<li>Log errors when listing instead of returning an error (Nick
+Craig-Wood)</li>
 <li>Fix preallocate warning on Linux with ZFS (Nick Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
 <li>Make rclone dedupe work through crypt (Nick Craig-Wood)</li>
-<li>Fix wrapping of ChangeNotify to decrypt directories properly (Nick Craig-Wood)</li>
-<li>Support PublicLink (rclone link) of underlying backend (Nick Craig-Wood)</li>
+<li>Fix wrapping of ChangeNotify to decrypt directories properly (Nick
+Craig-Wood)</li>
+<li>Support PublicLink (rclone link) of underlying backend (Nick
+Craig-Wood)</li>
 <li>Implement Optional methods SetTier, GetTier (Nick Craig-Wood)</li>
 </ul></li>
 <li>B2
@@ -42421,19 +59542,24 @@ $ tree /tmp/c
 <li>Drive
 <ul>
 <li>Fix move and copy from TeamDrive to GDrive (Fionera)</li>
-<li>Add notes that cleanup works in the background on drive (Nick Craig-Wood)</li>
-<li>Add <code>--drive-server-side-across-configs</code> to default back to old server-side copy semantics by default (Nick Craig-Wood)</li>
-<li>Add <code>--drive-size-as-quota</code> to show storage quota usage for file size (Garry McNulty)</li>
+<li>Add notes that cleanup works in the background on drive (Nick
+Craig-Wood)</li>
+<li>Add <code>--drive-server-side-across-configs</code> to default back
+to old server-side copy semantics by default (Nick Craig-Wood)</li>
+<li>Add <code>--drive-size-as-quota</code> to show storage quota usage
+for file size (Garry McNulty)</li>
 </ul></li>
 <li>FTP
 <ul>
 <li>Add FTP List timeout (Jeff Quinn)</li>
 <li>Add FTP over TLS support (Gary Kim)</li>
-<li>Add <code>--ftp-no-check-certificate</code> option for FTPS (Gary Kim)</li>
+<li>Add <code>--ftp-no-check-certificate</code> option for FTPS (Gary
+Kim)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Fix upload errors when uploading pre 1970 files (Nick Craig-Wood)</li>
+<li>Fix upload errors when uploading pre 1970 files (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
@@ -42449,15 +59575,18 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Support S3 Accelerated endpoints with <code>--s3-use-accelerate-endpoint</code> (Nick Craig-Wood)</li>
+<li>Support S3 Accelerated endpoints with
+<code>--s3-use-accelerate-endpoint</code> (Nick Craig-Wood)</li>
 <li>Add config info for Wasabi's EU Central endpoint (Robert Marko)</li>
 <li>Make SetModTime work for GLACIER while syncing (Philip Harvey)</li>
 </ul></li>
 <li>SFTP
 <ul>
 <li>Add About support (Gary Kim)</li>
-<li>Fix about parsing of <code>df</code> results so it can cope with -ve results (Nick Craig-Wood)</li>
-<li>Send custom client version and debug server version (Nick Craig-Wood)</li>
+<li>Fix about parsing of <code>df</code> results so it can cope with -ve
+results (Nick Craig-Wood)</li>
+<li>Send custom client version and debug server version (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
@@ -42474,73 +59603,107 @@ $ tree /tmp/c
 <ul>
 <li>Resume downloads if the reader fails in copy (Nick Craig-Wood)
 <ul>
-<li>this means rclone will restart transfers if the source has an error</li>
+<li>this means rclone will restart transfers if the source has an
+error</li>
 <li>this is most useful for downloads or cloud to cloud copies</li>
 </ul></li>
-<li>Use <code>--fast-list</code> for listing operations where it won't use more memory (Nick Craig-Wood)
+<li>Use <code>--fast-list</code> for listing operations where it won't
+use more memory (Nick Craig-Wood)
 <ul>
-<li>this should speed up the following operations on remotes which support <code>ListR</code></li>
-<li><code>dedupe</code>, <code>serve restic</code> <code>lsf</code>, <code>ls</code>, <code>lsl</code>, <code>lsjson</code>, <code>lsd</code>, <code>md5sum</code>, <code>sha1sum</code>, <code>hashsum</code>, <code>size</code>, <code>delete</code>, <code>cat</code>, <code>settier</code></li>
-<li>use <code>--disable ListR</code> to get old behaviour if required</li>
+<li>this should speed up the following operations on remotes which
+support <code>ListR</code></li>
+<li><code>dedupe</code>, <code>serve restic</code> <code>lsf</code>,
+<code>ls</code>, <code>lsl</code>, <code>lsjson</code>,
+<code>lsd</code>, <code>md5sum</code>, <code>sha1sum</code>,
+<code>hashsum</code>, <code>size</code>, <code>delete</code>,
+<code>cat</code>, <code>settier</code></li>
+<li>use <code>--disable ListR</code> to get old behaviour if
+required</li>
 </ul></li>
-<li>Make <code>--files-from</code> traverse the destination unless <code>--no-traverse</code> is set (Nick Craig-Wood)
+<li>Make <code>--files-from</code> traverse the destination unless
+<code>--no-traverse</code> is set (Nick Craig-Wood)
 <ul>
-<li>this fixes <code>--files-from</code> with Google drive and excessive API use in general.</li>
+<li>this fixes <code>--files-from</code> with Google drive and excessive
+API use in general.</li>
 </ul></li>
-<li>Make server-side copy account bytes and obey <code>--max-transfer</code> (Nick Craig-Wood)</li>
-<li>Add <code>--create-empty-src-dirs</code> flag and default to not creating empty dirs (ishuah)</li>
-<li>Add client side TLS/SSL flags <code>--ca-cert</code>/<code>--client-cert</code>/<code>--client-key</code> (Nick Craig-Wood)</li>
-<li>Implement <code>--suffix-keep-extension</code> for use with <code>--suffix</code> (Nick Craig-Wood)</li>
+<li>Make server-side copy account bytes and obey
+<code>--max-transfer</code> (Nick Craig-Wood)</li>
+<li>Add <code>--create-empty-src-dirs</code> flag and default to not
+creating empty dirs (ishuah)</li>
+<li>Add client side TLS/SSL flags
+<code>--ca-cert</code>/<code>--client-cert</code>/<code>--client-key</code>
+(Nick Craig-Wood)</li>
+<li>Implement <code>--suffix-keep-extension</code> for use with
+<code>--suffix</code> (Nick Craig-Wood)</li>
 <li>build:
 <ul>
-<li>Switch to semver compliant version tags to be go modules compliant (Nick Craig-Wood)</li>
+<li>Switch to semver compliant version tags to be go modules compliant
+(Nick Craig-Wood)</li>
 <li>Update to use go1.12.x for the build (Nick Craig-Wood)</li>
 </ul></li>
-<li>serve dlna: Add connection manager service description to improve compatibility (Dan Walters)</li>
-<li>lsf: Add 'e' format to show encrypted names and 'o' for original IDs (Nick Craig-Wood)</li>
-<li>lsjson: Added <code>--files-only</code> and <code>--dirs-only</code> flags (calistri)</li>
-<li>rc: Implement operations/publiclink the equivalent of <code>rclone link</code> (Nick Craig-Wood)</li>
+<li>serve dlna: Add connection manager service description to improve
+compatibility (Dan Walters)</li>
+<li>lsf: Add 'e' format to show encrypted names and 'o' for original IDs
+(Nick Craig-Wood)</li>
+<li>lsjson: Added <code>--files-only</code> and <code>--dirs-only</code>
+flags (calistri)</li>
+<li>rc: Implement operations/publiclink the equivalent of
+<code>rclone link</code> (Nick Craig-Wood)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>accounting: Fix total ETA when <code>--stats-unit bits</code> is in effect (Nick Craig-Wood)</li>
+<li>accounting: Fix total ETA when <code>--stats-unit bits</code> is in
+effect (Nick Craig-Wood)</li>
 <li>Bash TAB completion
 <ul>
-<li>Use private custom func to fix clash between rclone and kubectl (Nick Craig-Wood)</li>
+<li>Use private custom func to fix clash between rclone and kubectl
+(Nick Craig-Wood)</li>
 <li>Fix for remotes with underscores in their names (Six)</li>
 <li>Fix completion of remotes (Florian Gamböck)</li>
-<li>Fix autocompletion of remote paths with spaces (Danil Semelenov)</li>
+<li>Fix autocompletion of remote paths with spaces (Danil
+Semelenov)</li>
 </ul></li>
 <li>serve dlna: Fix root XML service descriptor (Dan Walters)</li>
-<li>ncdu: Fix display corruption with Chinese characters (Nick Craig-Wood)</li>
-<li>Add SIGTERM to signals which run the exit handlers on unix (Nick Craig-Wood)</li>
-<li>rc: Reload filter when the options are set via the rc (Nick Craig-Wood)</li>
+<li>ncdu: Fix display corruption with Chinese characters (Nick
+Craig-Wood)</li>
+<li>Add SIGTERM to signals which run the exit handlers on unix (Nick
+Craig-Wood)</li>
+<li>rc: Reload filter when the options are set via the rc (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>VFS / Mount
 <ul>
-<li>Fix FreeBSD: Ignore Truncate if called with no readers and already the correct size (Nick Craig-Wood)</li>
-<li>Read directory and check for a file before mkdir (Nick Craig-Wood)</li>
+<li>Fix FreeBSD: Ignore Truncate if called with no readers and already
+the correct size (Nick Craig-Wood)</li>
+<li>Read directory and check for a file before mkdir (Nick
+Craig-Wood)</li>
 <li>Shorten the locking window for vfs/refresh (Nick Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Enable MD5 checksums when uploading files bigger than the "Cutoff" (Dr.Rx)</li>
+<li>Enable MD5 checksums when uploading files bigger than the "Cutoff"
+(Dr.Rx)</li>
 <li>Fix SAS URL support (Nick Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
 <li>Allow manual configuration of backblaze downloadUrl (Vince)</li>
 <li>Ignore already_hidden error on remove (Nick Craig-Wood)</li>
-<li>Ignore malformed <code>src_last_modified_millis</code> (Nick Craig-Wood)</li>
+<li>Ignore malformed <code>src_last_modified_millis</code> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
-<li>Add <code>--skip-checksum-gphotos</code> to ignore incorrect checksums on Google Photos (Nick Craig-Wood)</li>
-<li>Allow server-side move/copy between different remotes. (Fionera)</li>
-<li>Add docs on team drives and <code>--fast-list</code> eventual consistency (Nestar47)</li>
+<li>Add <code>--skip-checksum-gphotos</code> to ignore incorrect
+checksums on Google Photos (Nick Craig-Wood)</li>
+<li>Allow server-side move/copy between different remotes.
+(Fionera)</li>
+<li>Add docs on team drives and <code>--fast-list</code> eventual
+consistency (Nestar47)</li>
 <li>Fix imports of text files (Nick Craig-Wood)</li>
 <li>Fix range requests on 0 length files (Nick Craig-Wood)</li>
-<li>Fix creation of duplicates with server-side copy (Nick Craig-Wood)</li>
+<li>Fix creation of duplicates with server-side copy (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -42548,7 +59711,8 @@ $ tree /tmp/c
 </ul></li>
 <li>FTP
 <ul>
-<li>Add <code>--ftp-concurrency</code> to limit maximum number of connections (Nick Craig-Wood)</li>
+<li>Add <code>--ftp-concurrency</code> to limit maximum number of
+connections (Nick Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
@@ -42557,7 +59721,8 @@ $ tree /tmp/c
 </ul></li>
 <li>HTTP
 <ul>
-<li>Add <code>--http-no-slash</code> for websites with directories with no slashes (Nick Craig-Wood)</li>
+<li>Add <code>--http-no-slash</code> for websites with directories with
+no slashes (Nick Craig-Wood)</li>
 <li>Remove duplicates from listings (Nick Craig-Wood)</li>
 <li>Fix socket leak on 404 errors (Nick Craig-Wood)</li>
 </ul></li>
@@ -42568,9 +59733,11 @@ $ tree /tmp/c
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Implement graceful cancel of multipart uploads if rclone is interrupted (Cnly)</li>
+<li>Implement graceful cancel of multipart uploads if rclone is
+interrupted (Cnly)</li>
 <li>Always add trailing colon to path when addressing items, (Cnly)</li>
-<li>Return errors instead of panic for invalid uploads (Fabian Möller)</li>
+<li>Return errors instead of panic for invalid uploads (Fabian
+Möller)</li>
 </ul></li>
 <li>S3
 <ul>
@@ -42584,120 +59751,166 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Obey Retry-After to enable OVH restore from cold storage (Nick Craig-Wood)</li>
+<li>Obey Retry-After to enable OVH restore from cold storage (Nick
+Craig-Wood)</li>
 <li>Work around token expiry on CEPH (Nick Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Allow IsCollection property to be integer or boolean (Nick Craig-Wood)</li>
+<li>Allow IsCollection property to be integer or boolean (Nick
+Craig-Wood)</li>
 <li>Fix race when creating directories (Nick Craig-Wood)</li>
-<li>Fix About/df when reading the available/total returns 0 (Nick Craig-Wood)</li>
+<li>Fix About/df when reading the available/total returns 0 (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.46---2019-02-09">v1.46 - 2019-02-09</h2>
 <ul>
 <li>New backends
 <ul>
-<li>Support Alibaba Cloud (Aliyun) OSS via the s3 backend (Nick Craig-Wood)</li>
+<li>Support Alibaba Cloud (Aliyun) OSS via the s3 backend (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>New commands
 <ul>
-<li>serve dlna: serves a remove via DLNA for the local network (nicolov)</li>
+<li>serve dlna: serves a remove via DLNA for the local network
+(nicolov)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li>copy, move: Restore deprecated <code>--no-traverse</code> flag (Nick Craig-Wood)
+<li>copy, move: Restore deprecated <code>--no-traverse</code> flag (Nick
+Craig-Wood)
 <ul>
-<li>This is useful for when transferring a small number of files into a large destination</li>
+<li>This is useful for when transferring a small number of files into a
+large destination</li>
 </ul></li>
-<li>genautocomplete: Add remote path completion for bash completion (Christopher Peterson &amp; Danil Semelenov)</li>
-<li>Buffer memory handling reworked to return memory to the OS better (Nick Craig-Wood)
+<li>genautocomplete: Add remote path completion for bash completion
+(Christopher Peterson &amp; Danil Semelenov)</li>
+<li>Buffer memory handling reworked to return memory to the OS better
+(Nick Craig-Wood)
 <ul>
 <li>Buffer recycling library to replace sync.Pool</li>
 <li>Optionally use memory mapped memory for better memory shrinking</li>
-<li>Enable with <code>--use-mmap</code> if having memory problems - not default yet</li>
+<li>Enable with <code>--use-mmap</code> if having memory problems - not
+default yet</li>
 </ul></li>
-<li>Parallelise reading of files specified by <code>--files-from</code> (Nick Craig-Wood)</li>
+<li>Parallelise reading of files specified by <code>--files-from</code>
+(Nick Craig-Wood)</li>
 <li>check: Add stats showing total files matched. (Dario Guzik)</li>
 <li>Allow rename/delete open files under Windows (Nick Craig-Wood)</li>
-<li>lsjson: Use exactly the correct number of decimal places in the seconds (Nick Craig-Wood)</li>
-<li>Add cookie support with cmdline switch <code>--use-cookies</code> for all HTTP based remotes (qip)</li>
-<li>Warn if <code>--checksum</code> is set but there are no hashes available (Nick Craig-Wood)</li>
-<li>Rework rate limiting (pacer) to be more accurate and allow bursting (Nick Craig-Wood)</li>
-<li>Improve error reporting for too many/few arguments in commands (Nick Craig-Wood)</li>
-<li>listremotes: Remove <code>-l</code> short flag as it conflicts with the new global flag (weetmuts)</li>
-<li>Make http serving with auth generate INFO messages on auth fail (Nick Craig-Wood)</li>
+<li>lsjson: Use exactly the correct number of decimal places in the
+seconds (Nick Craig-Wood)</li>
+<li>Add cookie support with cmdline switch <code>--use-cookies</code>
+for all HTTP based remotes (qip)</li>
+<li>Warn if <code>--checksum</code> is set but there are no hashes
+available (Nick Craig-Wood)</li>
+<li>Rework rate limiting (pacer) to be more accurate and allow bursting
+(Nick Craig-Wood)</li>
+<li>Improve error reporting for too many/few arguments in commands (Nick
+Craig-Wood)</li>
+<li>listremotes: Remove <code>-l</code> short flag as it conflicts with
+the new global flag (weetmuts)</li>
+<li>Make http serving with auth generate INFO messages on auth fail
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>Fix layout of stats (Nick Craig-Wood)</li>
-<li>Fix <code>--progress</code> crash under Windows Jenkins (Nick Craig-Wood)</li>
-<li>Fix transfer of google/onedrive docs by calling Rcat in Copy when size is -1 (Cnly)</li>
+<li>Fix <code>--progress</code> crash under Windows Jenkins (Nick
+Craig-Wood)</li>
+<li>Fix transfer of google/onedrive docs by calling Rcat in Copy when
+size is -1 (Cnly)</li>
 <li>copyurl: Fix checking of <code>--dry-run</code> (Denis Skovpen)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Check that mountpoint and local directory to mount don't overlap (Nick Craig-Wood)</li>
+<li>Check that mountpoint and local directory to mount don't overlap
+(Nick Craig-Wood)</li>
 <li>Fix mount size under 32 bit Windows (Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Implement renaming of directories for backends without DirMove (Nick Craig-Wood)
+<li>Implement renaming of directories for backends without DirMove (Nick
+Craig-Wood)
 <ul>
 <li>now all backends except b2 support renaming directories</li>
 </ul></li>
-<li>Implement <code>--vfs-cache-max-size</code> to limit the total size of the cache (Nick Craig-Wood)</li>
-<li>Add <code>--dir-perms</code> and <code>--file-perms</code> flags to set default permissions (Nick Craig-Wood)</li>
-<li>Fix deadlock on concurrent operations on a directory (Nick Craig-Wood)</li>
-<li>Fix deadlock between RWFileHandle.close and File.Remove (Nick Craig-Wood)</li>
-<li>Fix renaming/deleting open files with cache mode "writes" under Windows (Nick Craig-Wood)</li>
-<li>Fix panic on rename with <code>--dry-run</code> set (Nick Craig-Wood)</li>
-<li>Fix vfs/refresh with recurse=true needing the <code>--fast-list</code> flag</li>
+<li>Implement <code>--vfs-cache-max-size</code> to limit the total size
+of the cache (Nick Craig-Wood)</li>
+<li>Add <code>--dir-perms</code> and <code>--file-perms</code> flags to
+set default permissions (Nick Craig-Wood)</li>
+<li>Fix deadlock on concurrent operations on a directory (Nick
+Craig-Wood)</li>
+<li>Fix deadlock between RWFileHandle.close and File.Remove (Nick
+Craig-Wood)</li>
+<li>Fix renaming/deleting open files with cache mode "writes" under
+Windows (Nick Craig-Wood)</li>
+<li>Fix panic on rename with <code>--dry-run</code> set (Nick
+Craig-Wood)</li>
+<li>Fix vfs/refresh with recurse=true needing the
+<code>--fast-list</code> flag</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Add support for <code>-l</code>/<code>--links</code> (symbolic link translation) (yair@unicorn)
+<li>Add support for <code>-l</code>/<code>--links</code> (symbolic link
+translation) (yair@unicorn)
 <ul>
-<li>this works by showing links as <code>link.rclonelink</code> - see local backend docs for more info</li>
-<li>this errors if used with <code>-L</code>/<code>--copy-links</code></li>
+<li>this works by showing links as <code>link.rclonelink</code> - see
+local backend docs for more info</li>
+<li>this errors if used with
+<code>-L</code>/<code>--copy-links</code></li>
 </ul></li>
 <li>Fix renaming/deleting open files on Windows (Nick Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
-<li>Check for maximum length before decrypting filename to fix panic (Garry McNulty)</li>
+<li>Check for maximum length before decrypting filename to fix panic
+(Garry McNulty)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
 <li>Allow building azureblob backend on *BSD (themylogin)</li>
-<li>Use the rclone HTTP client to support <code>--dump headers</code>, <code>--tpslimit</code>, etc. (Nick Craig-Wood)</li>
-<li>Use the s3 pacer for 0 delay in non error conditions (Nick Craig-Wood)</li>
+<li>Use the rclone HTTP client to support <code>--dump headers</code>,
+<code>--tpslimit</code>, etc. (Nick Craig-Wood)</li>
+<li>Use the s3 pacer for 0 delay in non error conditions (Nick
+Craig-Wood)</li>
 <li>Ignore directory markers (Nick Craig-Wood)</li>
-<li>Stop Mkdir attempting to create existing containers (Nick Craig-Wood)</li>
+<li>Stop Mkdir attempting to create existing containers (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>B2
 <ul>
-<li>cleanup: will remove unfinished large files &gt;24hrs old (Garry McNulty)</li>
-<li>For a bucket limited application key check the bucket name (Nick Craig-Wood)
+<li>cleanup: will remove unfinished large files &gt;24hrs old (Garry
+McNulty)</li>
+<li>For a bucket limited application key check the bucket name (Nick
+Craig-Wood)
 <ul>
-<li>before this, rclone would use the authorised bucket regardless of what you put on the command line</li>
+<li>before this, rclone would use the authorised bucket regardless of
+what you put on the command line</li>
 </ul></li>
 <li>Added <code>--b2-disable-checksum</code> flag (Wojciech Smigielski)
 <ul>
-<li>this enables large files to be uploaded without a SHA-1 hash for speed reasons</li>
+<li>this enables large files to be uploaded without a SHA-1 hash for
+speed reasons</li>
 </ul></li>
 </ul></li>
 <li>Drive
 <ul>
 <li>Set default pacer to 100ms for 10 tps (Nick Craig-Wood)
 <ul>
-<li>This fits the Google defaults much better and reduces the 403 errors massively</li>
-<li>Add <code>--drive-pacer-min-sleep</code> and <code>--drive-pacer-burst</code> to control the pacer</li>
+<li>This fits the Google defaults much better and reduces the 403 errors
+massively</li>
+<li>Add <code>--drive-pacer-min-sleep</code> and
+<code>--drive-pacer-burst</code> to control the pacer</li>
 </ul></li>
-<li>Improve ChangeNotify support for items with multiple parents (Fabian Möller)</li>
-<li>Fix ListR for items with multiple parents - this fixes oddities with <code>vfs/refresh</code> (Fabian Möller)</li>
-<li>Fix using <code>--drive-impersonate</code> and appfolders (Nick Craig-Wood)</li>
-<li>Fix google docs in rclone mount for some (not all) applications (Nick Craig-Wood)</li>
+<li>Improve ChangeNotify support for items with multiple parents (Fabian
+Möller)</li>
+<li>Fix ListR for items with multiple parents - this fixes oddities with
+<code>vfs/refresh</code> (Fabian Möller)</li>
+<li>Fix using <code>--drive-impersonate</code> and appfolders (Nick
+Craig-Wood)</li>
+<li>Fix google docs in rclone mount for some (not all) applications
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -42705,7 +59918,8 @@ $ tree /tmp/c
 </ul></li>
 <li>FTP
 <ul>
-<li>Wait for 60 seconds for a connection to Close then declare it dead (Nick Craig-Wood)
+<li>Wait for 60 seconds for a connection to Close then declare it dead
+(Nick Craig-Wood)
 <ul>
 <li>helps with indefinite hangs on some FTP servers</li>
 </ul></li>
@@ -42716,24 +59930,31 @@ $ tree /tmp/c
 </ul></li>
 <li>HTTP
 <ul>
-<li>Add an example with username and password which is supported but wasn't documented (Nick Craig-Wood)</li>
-<li>Fix backend with <code>--files-from</code> and nonexistent files (Nick Craig-Wood)</li>
+<li>Add an example with username and password which is supported but
+wasn't documented (Nick Craig-Wood)</li>
+<li>Fix backend with <code>--files-from</code> and nonexistent files
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Hubic
 <ul>
-<li>Make error message more informative if authentication fails (Nick Craig-Wood)</li>
+<li>Make error message more informative if authentication fails (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
 <li>Resume and deduplication support (Oliver Heyme)</li>
-<li>Use token auth for all API requests Don't store password anymore (Sebastian Bünger)</li>
+<li>Use token auth for all API requests Don't store password anymore
+(Sebastian Bünger)</li>
 <li>Add support for 2-factor authentication (Sebastian Bünger)</li>
 </ul></li>
 <li>Mega
 <ul>
-<li>Implement v2 account login which fixes logins for newer Mega accounts (Nick Craig-Wood)</li>
-<li>Return error if an unknown length file is attempted to be uploaded (Nick Craig-Wood)</li>
-<li>Add new error codes for better error reporting (Nick Craig-Wood)</li>
+<li>Implement v2 account login which fixes logins for newer Mega
+accounts (Nick Craig-Wood)</li>
+<li>Return error if an unknown length file is attempted to be uploaded
+(Nick Craig-Wood)</li>
+<li>Add new error codes for better error reporting (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Onedrive
 <ul>
@@ -42743,16 +59964,23 @@ $ tree /tmp/c
 </ul></li>
 <li>Qingstor
 <ul>
-<li>Fix go routine leak on multipart upload errors (Nick Craig-Wood)</li>
-<li>Add upload chunk size/concurrency/cutoff control (Nick Craig-Wood)</li>
-<li>Default <code>--qingstor-upload-concurrency</code> to 1 to work around bug (Nick Craig-Wood)</li>
+<li>Fix go routine leak on multipart upload errors (Nick
+Craig-Wood)</li>
+<li>Add upload chunk size/concurrency/cutoff control (Nick
+Craig-Wood)</li>
+<li>Default <code>--qingstor-upload-concurrency</code> to 1 to work
+around bug (Nick Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Implement <code>--s3-upload-cutoff</code> for single part uploads below this (Nick Craig-Wood)</li>
-<li>Change <code>--s3-upload-concurrency</code> default to 4 to increase performance (Nick Craig-Wood)</li>
-<li>Add <code>--s3-bucket-acl</code> to control bucket ACL (Nick Craig-Wood)</li>
-<li>Auto detect region for buckets on operation failure (Nick Craig-Wood)</li>
+<li>Implement <code>--s3-upload-cutoff</code> for single part uploads
+below this (Nick Craig-Wood)</li>
+<li>Change <code>--s3-upload-concurrency</code> default to 4 to increase
+performance (Nick Craig-Wood)</li>
+<li>Add <code>--s3-bucket-acl</code> to control bucket ACL (Nick
+Craig-Wood)</li>
+<li>Auto detect region for buckets on operation failure (Nick
+Craig-Wood)</li>
 <li>Add GLACIER storage class (William Cocker)</li>
 <li>Add Scaleway to s3 documentation (Rémy Léone)</li>
 <li>Add AWS endpoint eu-north-1 (weetmuts)</li>
@@ -42761,14 +59989,18 @@ $ tree /tmp/c
 <ul>
 <li>Add support for PEM encrypted private keys (Fabian Möller)</li>
 <li>Add option to force the usage of an ssh-agent (Fabian Möller)</li>
-<li>Perform environment variable expansion on key-file (Fabian Möller)</li>
-<li>Fix rmdir on Windows based servers (e.g. CrushFTP) (Nick Craig-Wood)</li>
-<li>Fix rmdir deleting directory contents on some SFTP servers (Nick Craig-Wood)</li>
+<li>Perform environment variable expansion on key-file (Fabian
+Möller)</li>
+<li>Fix rmdir on Windows based servers (e.g. CrushFTP) (Nick
+Craig-Wood)</li>
+<li>Fix rmdir deleting directory contents on some SFTP servers (Nick
+Craig-Wood)</li>
 <li>Fix error on dangling symlinks (Nick Craig-Wood)</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Add <code>--swift-no-chunk</code> to disable segmented uploads in rcat/mount (Nick Craig-Wood)</li>
+<li>Add <code>--swift-no-chunk</code> to disable segmented uploads in
+rcat/mount (Nick Craig-Wood)</li>
 <li>Introduce application credential auth support (kayrus)</li>
 <li>Fix memory usage by slimming Object (Nick Craig-Wood)</li>
 <li>Fix extra requests on upload (Nick Craig-Wood)</li>
@@ -42780,81 +60012,109 @@ $ tree /tmp/c
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Support About which means rclone mount will show the correct disk size (Nick Craig-Wood)</li>
-<li>Support MD5 and SHA1 hashes with Owncloud and Nextcloud (Nick Craig-Wood)</li>
+<li>Support About which means rclone mount will show the correct disk
+size (Nick Craig-Wood)</li>
+<li>Support MD5 and SHA1 hashes with Owncloud and Nextcloud (Nick
+Craig-Wood)</li>
 <li>Fail soft on time parsing errors (Nick Craig-Wood)</li>
-<li>Fix infinite loop on failed directory creation (Nick Craig-Wood)</li>
-<li>Fix identification of directories for Bitrix Site Manager (Nick Craig-Wood)</li>
+<li>Fix infinite loop on failed directory creation (Nick
+Craig-Wood)</li>
+<li>Fix identification of directories for Bitrix Site Manager (Nick
+Craig-Wood)</li>
 <li>Fix upload of 0 length files on some servers (Nick Craig-Wood)</li>
-<li>Fix if MKCOL fails with 423 Locked assume the directory exists (Nick Craig-Wood)</li>
+<li>Fix if MKCOL fails with 423 Locked assume the directory exists (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.45---2018-11-24">v1.45 - 2018-11-24</h2>
 <ul>
 <li>New backends
 <ul>
-<li>The Yandex backend was re-written - see below for details (Sebastian Bünger)</li>
+<li>The Yandex backend was re-written - see below for details (Sebastian
+Bünger)</li>
 </ul></li>
 <li>New commands
 <ul>
-<li>rcd: New command just to serve the remote control API (Nick Craig-Wood)</li>
+<li>rcd: New command just to serve the remote control API (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>New Features
 <ul>
-<li>The remote control API (rc) was greatly expanded to allow full control over rclone (Nick Craig-Wood)
+<li>The remote control API (rc) was greatly expanded to allow full
+control over rclone (Nick Craig-Wood)
 <ul>
-<li>sensitive operations require authorization or the <code>--rc-no-auth</code> flag</li>
+<li>sensitive operations require authorization or the
+<code>--rc-no-auth</code> flag</li>
 <li>config/* operations to configure rclone</li>
 <li>options/* for reading/setting command line flags</li>
-<li>operations/* for all low level operations, e.g. copy file, list directory</li>
+<li>operations/* for all low level operations, e.g. copy file, list
+directory</li>
 <li>sync/* for sync, copy and move</li>
 <li><code>--rc-files</code> flag to serve files on the rc http server
 <ul>
 <li>this is for building web native GUIs for rclone</li>
 </ul></li>
 <li>Optionally serving objects on the rc http server</li>
-<li>Ensure rclone fails to start up if the <code>--rc</code> port is in use already</li>
-<li>See <a href="https://rclone.org/rc/">the rc docs</a> for more info</li>
+<li>Ensure rclone fails to start up if the <code>--rc</code> port is in
+use already</li>
+<li>See <a href="https://rclone.org/rc/">the rc docs</a> for more
+info</li>
 </ul></li>
 <li>sync/copy/move
 <ul>
-<li>Make <code>--files-from</code> only read the objects specified and don't scan directories (Nick Craig-Wood)
+<li>Make <code>--files-from</code> only read the objects specified and
+don't scan directories (Nick Craig-Wood)
 <ul>
-<li>This is a huge speed improvement for destinations with lots of files</li>
+<li>This is a huge speed improvement for destinations with lots of
+files</li>
 </ul></li>
 </ul></li>
 <li>filter: Add <code>--ignore-case</code> flag (Nick Craig-Wood)</li>
 <li>ncdu: Add remove function ('d' key) (Henning Surmeier)</li>
 <li>rc command
 <ul>
-<li>Add <code>--json</code> flag for structured JSON input (Nick Craig-Wood)</li>
-<li>Add <code>--user</code> and <code>--pass</code> flags and interpret <code>--rc-user</code>, <code>--rc-pass</code>, <code>--rc-addr</code> (Nick Craig-Wood)</li>
+<li>Add <code>--json</code> flag for structured JSON input (Nick
+Craig-Wood)</li>
+<li>Add <code>--user</code> and <code>--pass</code> flags and interpret
+<code>--rc-user</code>, <code>--rc-pass</code>, <code>--rc-addr</code>
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>build
 <ul>
 <li>Require go1.8 or later for compilation (Nick Craig-Wood)</li>
 <li>Enable softfloat on MIPS arch (Scott Edlund)</li>
-<li>Integration test framework revamped with a better report and better retries (Nick Craig-Wood)</li>
+<li>Integration test framework revamped with a better report and better
+retries (Nick Craig-Wood)</li>
 </ul></li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>cmd: Make <code>--progress</code> update the stats correctly at the end (Nick Craig-Wood)</li>
-<li>config: Create config directory on save if it is missing (Nick Craig-Wood)</li>
-<li>dedupe: Check for existing filename before renaming a dupe file (ssaqua)</li>
-<li>move: Don't create directories with <code>--dry-run</code> (Nick Craig-Wood)</li>
-<li>operations: Fix Purge and Rmdirs when dir is not the root (Nick Craig-Wood)</li>
-<li>serve http/webdav/restic: Ensure rclone exits if the port is in use (Nick Craig-Wood)</li>
+<li>cmd: Make <code>--progress</code> update the stats correctly at the
+end (Nick Craig-Wood)</li>
+<li>config: Create config directory on save if it is missing (Nick
+Craig-Wood)</li>
+<li>dedupe: Check for existing filename before renaming a dupe file
+(ssaqua)</li>
+<li>move: Don't create directories with <code>--dry-run</code> (Nick
+Craig-Wood)</li>
+<li>operations: Fix Purge and Rmdirs when dir is not the root (Nick
+Craig-Wood)</li>
+<li>serve http/webdav/restic: Ensure rclone exits if the port is in use
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Make <code>--volname</code> work for Windows and macOS (Nick Craig-Wood)</li>
+<li>Make <code>--volname</code> work for Windows and macOS (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Avoid context deadline exceeded error by setting a large TryTimeout value (brused27)</li>
-<li>Fix erroneous Rmdir error "directory not empty" (Nick Craig-Wood)</li>
-<li>Wait for up to 60s to create a just deleted container (Nick Craig-Wood)</li>
+<li>Avoid context deadline exceeded error by setting a large TryTimeout
+value (brused27)</li>
+<li>Fix erroneous Rmdir error "directory not empty" (Nick
+Craig-Wood)</li>
+<li>Wait for up to 60s to create a just deleted container (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -42862,16 +60122,19 @@ $ tree /tmp/c
 </ul></li>
 <li>Jottacloud
 <ul>
-<li>Fix bug in <code>--fast-list</code> handing of empty folders (albertony)</li>
+<li>Fix bug in <code>--fast-list</code> handing of empty folders
+(albertony)</li>
 </ul></li>
 <li>Opendrive
 <ul>
-<li>Fix transfer of files with <code>+</code> and <code>&amp;</code> in (Nick Craig-Wood)</li>
+<li>Fix transfer of files with <code>+</code> and <code>&amp;</code> in
+(Nick Craig-Wood)</li>
 <li>Fix retries of upload chunks (Nick Craig-Wood)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Set ACL for server-side copies to that provided by the user (Nick Craig-Wood)</li>
+<li>Set ACL for server-side copies to that provided by the user (Nick
+Craig-Wood)</li>
 <li>Fix role_arn, credential_source, ... (Erik Swanson)</li>
 <li>Add config info for Wasabi's US-West endpoint (Henry Ptasinski)</li>
 </ul></li>
@@ -42881,12 +60144,14 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Add pacer for retries to make swift more reliable (Nick Craig-Wood)</li>
+<li>Add pacer for retries to make swift more reliable (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
 <li>Add Content-Type to PUT requests (Nick Craig-Wood)</li>
-<li>Fix config parsing so <code>--webdav-user</code> and <code>--webdav-pass</code> flags work (Nick Craig-Wood)</li>
+<li>Fix config parsing so <code>--webdav-user</code> and
+<code>--webdav-pass</code> flags work (Nick Craig-Wood)</li>
 <li>Add RFC3339 date format (Ralf Hemberger)</li>
 </ul></li>
 <li>Yandex
@@ -42894,9 +60159,11 @@ $ tree /tmp/c
 <li>The yandex backend was re-written (Sebastian Bünger)
 <ul>
 <li>This implements low level retries (Sebastian Bünger)</li>
-<li>Copy, Move, DirMove, PublicLink and About optional interfaces (Sebastian Bünger)</li>
+<li>Copy, Move, DirMove, PublicLink and About optional interfaces
+(Sebastian Bünger)</li>
 <li>Improved general error handling (Sebastian Bünger)</li>
-<li>Removed ListR for now due to inconsistent behaviour (Sebastian Bünger)</li>
+<li>Removed ListR for now due to inconsistent behaviour (Sebastian
+Bünger)</li>
 </ul></li>
 </ul></li>
 </ul>
@@ -42905,7 +60172,8 @@ $ tree /tmp/c
 <li>New commands
 <ul>
 <li>serve ftp: Add ftp server (Antoine GIRARD)</li>
-<li>settier: perform storage tier changes on supported remotes (sandeepkru)</li>
+<li>settier: perform storage tier changes on supported remotes
+(sandeepkru)</li>
 </ul></li>
 <li>New Features
 <ul>
@@ -42913,19 +60181,25 @@ $ tree /tmp/c
 <ul>
 <li>Make default help less verbose (Nick Craig-Wood)</li>
 <li>Split flags up into global and backend flags (Nick Craig-Wood)</li>
-<li>Implement specialised help for flags and backends (Nick Craig-Wood)</li>
-<li>Show URL of backend help page when starting config (Nick Craig-Wood)</li>
+<li>Implement specialised help for flags and backends (Nick
+Craig-Wood)</li>
+<li>Show URL of backend help page when starting config (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>stats: Long names now split in center (Joanna Marek)</li>
-<li>Add <code>--log-format</code> flag for more control over log output (dcpu)</li>
+<li>Add <code>--log-format</code> flag for more control over log output
+(dcpu)</li>
 <li>rc: Add support for OPTIONS and basic CORS (frenos)</li>
-<li>stats: show FatalErrors and NoRetryErrors in stats (Cédric Connes)</li>
+<li>stats: show FatalErrors and NoRetryErrors in stats (Cédric
+Connes)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
 <li>Fix -P not ending with a new line (Nick Craig-Wood)</li>
-<li>config: don't create default config dir when user supplies <code>--config</code> (albertony)</li>
-<li>Don't print non-ASCII characters with <code>--progress</code> on windows (Nick Craig-Wood)</li>
+<li>config: don't create default config dir when user supplies
+<code>--config</code> (albertony)</li>
+<li>Don't print non-ASCII characters with <code>--progress</code> on
+windows (Nick Craig-Wood)</li>
 <li>Correct logs for excluded items (ssaqua)</li>
 </ul></li>
 <li>Mount
@@ -42934,27 +60208,34 @@ $ tree /tmp/c
 </ul></li>
 <li>VFS
 <ul>
-<li>Fix race condition detected by serve ftp tests (Nick Craig-Wood)</li>
+<li>Fix race condition detected by serve ftp tests (Nick
+Craig-Wood)</li>
 <li>Add vfs/poll-interval rc command (Fabian Möller)</li>
-<li>Enable rename for nearly all remotes using server-side Move or Copy (Nick Craig-Wood)</li>
+<li>Enable rename for nearly all remotes using server-side Move or Copy
+(Nick Craig-Wood)</li>
 <li>Reduce directory cache cleared by poll-interval (Fabian Möller)</li>
 <li>Remove EXPERIMENTAL tags (Nick Craig-Wood)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Skip bad symlinks in dir listing with -L enabled (Cédric Connes)</li>
-<li>Preallocate files on Windows to reduce fragmentation (Nick Craig-Wood)</li>
+<li>Skip bad symlinks in dir listing with -L enabled (Cédric
+Connes)</li>
+<li>Preallocate files on Windows to reduce fragmentation (Nick
+Craig-Wood)</li>
 <li>Preallocate files on linux with fallocate(2) (Nick Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
 <li>Add cache/fetch rc function (Fabian Möller)</li>
 <li>Fix worker scale down (Fabian Möller)</li>
-<li>Improve performance by not sending info requests for cached chunks (dcpu)</li>
+<li>Improve performance by not sending info requests for cached chunks
+(dcpu)</li>
 <li>Fix error return value of cache/fetch rc method (Fabian Möller)</li>
-<li>Documentation fix for cache-chunk-total-size (Anagh Kumar Baranwal)</li>
+<li>Documentation fix for cache-chunk-total-size (Anagh Kumar
+Baranwal)</li>
 <li>Preserve leading / in wrapped remote path (Fabian Möller)</li>
-<li>Add plex_insecure option to skip certificate validation (Fabian Möller)</li>
+<li>Add plex_insecure option to skip certificate validation (Fabian
+Möller)</li>
 <li>Remove entries that no longer exist in the source (dcpu)</li>
 </ul></li>
 <li>Crypt
@@ -42967,9 +60248,12 @@ $ tree /tmp/c
 </ul></li>
 <li>Azure Blob
 <ul>
-<li>Add <code>--azureblob-list-chunk</code> parameter (Santiago Rodríguez)</li>
-<li>Implemented settier command support on azureblob remote. (sandeepkru)</li>
-<li>Work around SDK bug which causes errors for chunk-sized files (Nick Craig-Wood)</li>
+<li>Add <code>--azureblob-list-chunk</code> parameter (Santiago
+Rodríguez)</li>
+<li>Implemented settier command support on azureblob remote.
+(sandeepkru)</li>
+<li>Work around SDK bug which causes errors for chunk-sized files (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Box
 <ul>
@@ -42977,7 +60261,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Add <code>--drive-import-formats</code> - google docs can now be imported (Fabian Möller)
+<li>Add <code>--drive-import-formats</code> - google docs can now be
+imported (Fabian Möller)
 <ul>
 <li>Rewrite mime type and extension handling (Fabian Möller)</li>
 <li>Add document links (Fabian Möller)</li>
@@ -42985,13 +60270,16 @@ $ tree /tmp/c
 <li>Add support for apps-script to json export (Fabian Möller)</li>
 <li>Fix escaped chars in documents during list (Fabian Möller)</li>
 </ul></li>
-<li>Add <code>--drive-v2-download-min-size</code> a workaround for slow downloads (Fabian Möller)</li>
+<li>Add <code>--drive-v2-download-min-size</code> a workaround for slow
+downloads (Fabian Möller)</li>
 <li>Improve directory notifications in ChangeNotify (Fabian Möller)</li>
-<li>When listing team drives in config, continue on failure (Nick Craig-Wood)</li>
+<li>When listing team drives in config, continue on failure (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>FTP
 <ul>
-<li>Add a small pause after failed upload before deleting file (Nick Craig-Wood)</li>
+<li>Add a small pause after failed upload before deleting file (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
@@ -43001,7 +60289,8 @@ $ tree /tmp/c
 <ul>
 <li>Minor improvement in quota info (omit if unlimited) (albertony)</li>
 <li>Add <code>--fast-list</code> support (albertony)</li>
-<li>Add permanent delete support: <code>--jottacloud-hard-delete</code> (albertony)</li>
+<li>Add permanent delete support: <code>--jottacloud-hard-delete</code>
+(albertony)</li>
 <li>Add link sharing support (albertony)</li>
 <li>Fix handling of reserved characters. (Sebastian Bünger)</li>
 <li>Fix socket leak on Object.Remove (Nick Craig-Wood)</li>
@@ -43010,33 +60299,42 @@ $ tree /tmp/c
 <ul>
 <li>Rework to support Microsoft Graph (Cnly)
 <ul>
-<li><strong>NB</strong> this will require re-authenticating the remote</li>
+<li><strong>NB</strong> this will require re-authenticating the
+remote</li>
 </ul></li>
-<li>Removed upload cutoff and always do session uploads (Oliver Heyme)</li>
+<li>Removed upload cutoff and always do session uploads (Oliver
+Heyme)</li>
 <li>Use single-part upload for empty files (Cnly)</li>
 <li>Fix new fields not saved when editing old config (Alex Chen)</li>
-<li>Fix sometimes special chars in filenames not replaced (Alex Chen)</li>
+<li>Fix sometimes special chars in filenames not replaced (Alex
+Chen)</li>
 <li>Ignore OneNote files by default (Alex Chen)</li>
 <li>Add link sharing support (jackyzy823)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Use custom pacer, to retry operations when reasonable (Craig Miskell)</li>
-<li>Use configured server-side-encryption and storage class options when calling CopyObject() (Paul Kohout)</li>
+<li>Use custom pacer, to retry operations when reasonable (Craig
+Miskell)</li>
+<li>Use configured server-side-encryption and storage class options when
+calling CopyObject() (Paul Kohout)</li>
 <li>Make <code>--s3-v2-auth</code> flag (Nick Craig-Wood)</li>
 <li>Fix v2 auth on files with spaces (Nick Craig-Wood)</li>
 </ul></li>
 <li>Union
 <ul>
-<li>Implement union backend which reads from multiple backends (Felix Brucker)</li>
-<li>Implement optional interfaces (Move, DirMove, Copy, etc.) (Nick Craig-Wood)</li>
+<li>Implement union backend which reads from multiple backends (Felix
+Brucker)</li>
+<li>Implement optional interfaces (Move, DirMove, Copy, etc.) (Nick
+Craig-Wood)</li>
 <li>Fix ChangeNotify to support multiple remotes (Fabian Möller)</li>
-<li>Fix <code>--backup-dir</code> on union backend (Nick Craig-Wood)</li>
+<li>Fix <code>--backup-dir</code> on union backend (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
 <li>Add another time format (Nick Craig-Wood)</li>
-<li>Add a small pause after failed upload before deleting file (Nick Craig-Wood)</li>
+<li>Add a small pause after failed upload before deleting file (Nick
+Craig-Wood)</li>
 <li>Add workaround for missing mtime (buergi)</li>
 <li>Sharepoint: Renew cookies after 12hrs (Henning Surmeier)</li>
 </ul></li>
@@ -43051,7 +60349,8 @@ $ tree /tmp/c
 <li>Bug Fixes
 <ul>
 <li>ncdu: Return error instead of log.Fatal in Show (Fabian Möller)</li>
-<li>cmd: Fix crash with <code>--progress</code> and <code>--stats 0</code> (Nick Craig-Wood)</li>
+<li>cmd: Fix crash with <code>--progress</code> and
+<code>--stats 0</code> (Nick Craig-Wood)</li>
 <li>docs: Tidy website display (Anagh Kumar Baranwal)</li>
 </ul></li>
 <li>Azure Blob:
@@ -43061,7 +60360,8 @@ $ tree /tmp/c
 <li>Hubic
 <ul>
 <li>Fix uploads (Nick Craig-Wood)</li>
-<li>Retry auth fetching if it fails to make hubic more reliable (Nick Craig-Wood)</li>
+<li>Retry auth fetching if it fails to make hubic more reliable (Nick
+Craig-Wood)</li>
 </ul></li>
 </ul>
 <h2 id="v1.43---2018-09-01">v1.43 - 2018-09-01</h2>
@@ -43078,20 +60378,27 @@ $ tree /tmp/c
 <ul>
 <li>Reworked config for backends (Nick Craig-Wood)
 <ul>
-<li>All backend config can now be supplied by command line, env var or config file</li>
+<li>All backend config can now be supplied by command line, env var or
+config file</li>
 <li>Advanced section in the config wizard for the optional items</li>
-<li>A large step towards rclone backends being usable in other go software</li>
+<li>A large step towards rclone backends being usable in other go
+software</li>
 <li>Allow on the fly remotes with :backend: syntax</li>
 </ul></li>
 <li>Stats revamp
 <ul>
-<li>Add <code>--progress</code>/<code>-P</code> flag to show interactive progress (Nick Craig-Wood)</li>
-<li>Show the total progress of the sync in the stats (Nick Craig-Wood)</li>
-<li>Add <code>--stats-one-line</code> flag for single line stats (Nick Craig-Wood)</li>
+<li>Add <code>--progress</code>/<code>-P</code> flag to show interactive
+progress (Nick Craig-Wood)</li>
+<li>Show the total progress of the sync in the stats (Nick
+Craig-Wood)</li>
+<li>Add <code>--stats-one-line</code> flag for single line stats (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Added weekday schedule into <code>--bwlimit</code> (Mateusz)</li>
-<li>lsjson: Add option to show the original object IDs (Fabian Möller)</li>
-<li>serve webdav: Make Content-Type without reading the file and add <code>--etag-hash</code> (Nick Craig-Wood)</li>
+<li>lsjson: Add option to show the original object IDs (Fabian
+Möller)</li>
+<li>serve webdav: Make Content-Type without reading the file and add
+<code>--etag-hash</code> (Nick Craig-Wood)</li>
 <li>build
 <ul>
 <li>Build macOS with native compiler (Nick Craig-Wood)</li>
@@ -43101,7 +60408,8 @@ $ tree /tmp/c
 <ul>
 <li>Added core/stats to return the stats (reddi1)</li>
 </ul></li>
-<li><code>version --check</code>: Prints the current release and beta versions (Nick Craig-Wood)</li>
+<li><code>version --check</code>: Prints the current release and beta
+versions (Nick Craig-Wood)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
@@ -43110,31 +60418,42 @@ $ tree /tmp/c
 <li>Fix time to completion estimates (Nick Craig-Wood)</li>
 <li>Fix moving average speed for file stats (Nick Craig-Wood)</li>
 </ul></li>
-<li>config: Fix error reading password from piped input (Nick Craig-Wood)</li>
-<li>move: Fix <code>--delete-empty-src-dirs</code> flag to delete all empty dirs on move (ishuah)</li>
+<li>config: Fix error reading password from piped input (Nick
+Craig-Wood)</li>
+<li>move: Fix <code>--delete-empty-src-dirs</code> flag to delete all
+empty dirs on move (ishuah)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Implement <code>--daemon-timeout</code> flag for OSXFUSE (Nick Craig-Wood)</li>
-<li>Fix mount <code>--daemon</code> not working with encrypted config (Alex Chen)</li>
-<li>Clip the number of blocks to 2^32-1 on macOS - fixes borg backup (Nick Craig-Wood)</li>
+<li>Implement <code>--daemon-timeout</code> flag for OSXFUSE (Nick
+Craig-Wood)</li>
+<li>Fix mount <code>--daemon</code> not working with encrypted config
+(Alex Chen)</li>
+<li>Clip the number of blocks to 2^32-1 on macOS - fixes borg backup
+(Nick Craig-Wood)</li>
 </ul></li>
 <li>VFS
 <ul>
 <li>Enable vfs-read-chunk-size by default (Fabian Möller)</li>
 <li>Add the vfs/refresh rc command (Fabian Möller)</li>
-<li>Add non recursive mode to vfs/refresh rc command (Fabian Möller)</li>
+<li>Add non recursive mode to vfs/refresh rc command (Fabian
+Möller)</li>
 <li>Try to seek buffer on read only files (Fabian Möller)</li>
 </ul></li>
 <li>Local
 <ul>
-<li>Fix crash when deprecated <code>--local-no-unicode-normalization</code> is supplied (Nick Craig-Wood)</li>
-<li>Fix mkdir error when trying to copy files to the root of a drive on windows (Nick Craig-Wood)</li>
+<li>Fix crash when deprecated
+<code>--local-no-unicode-normalization</code> is supplied (Nick
+Craig-Wood)</li>
+<li>Fix mkdir error when trying to copy files to the root of a drive on
+windows (Nick Craig-Wood)</li>
 </ul></li>
 <li>Cache
 <ul>
-<li>Fix nil pointer deref when using lsjson on cached directory (Nick Craig-Wood)</li>
-<li>Fix nil pointer deref for occasional crash on playback (Nick Craig-Wood)</li>
+<li>Fix nil pointer deref when using lsjson on cached directory (Nick
+Craig-Wood)</li>
+<li>Fix nil pointer deref for occasional crash on playback (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Crypt
 <ul>
@@ -43142,14 +60461,16 @@ $ tree /tmp/c
 </ul></li>
 <li>Amazon Cloud Drive
 <ul>
-<li>Make very clear in the docs that rclone has no ACD keys (Nick Craig-Wood)</li>
+<li>Make very clear in the docs that rclone has no ACD keys (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Azure Blob
 <ul>
 <li>Add connection string and SAS URL auth (Nick Craig-Wood)</li>
 <li>List the container to see if it exists (Nick Craig-Wood)</li>
 <li>Port new Azure Blob Storage SDK (sandeepkru)</li>
-<li>Added blob tier, tier between Hot, Cool and Archive. (sandeepkru)</li>
+<li>Added blob tier, tier between Hot, Cool and Archive.
+(sandeepkru)</li>
 <li>Remove leading / from paths (Nick Craig-Wood)</li>
 </ul></li>
 <li>B2
@@ -43159,14 +60480,17 @@ $ tree /tmp/c
 </ul></li>
 <li>Box
 <ul>
-<li>Fix upload of &gt; 2GB files on 32 bit platforms (Nick Craig-Wood)</li>
-<li>Make <code>--box-commit-retries</code> flag defaulting to 100 to fix large uploads (Nick Craig-Wood)</li>
+<li>Fix upload of &gt; 2GB files on 32 bit platforms (Nick
+Craig-Wood)</li>
+<li>Make <code>--box-commit-retries</code> flag defaulting to 100 to fix
+large uploads (Nick Craig-Wood)</li>
 </ul></li>
 <li>Drive
 <ul>
 <li>Add <code>--drive-keep-revision-forever</code> flag (lewapm)</li>
 <li>Handle gdocs when filtering file names in list (Fabian Möller)</li>
-<li>Support using <code>--fast-list</code> for large speedups (Fabian Möller)</li>
+<li>Support using <code>--fast-list</code> for large speedups (Fabian
+Möller)</li>
 </ul></li>
 <li>FTP
 <ul>
@@ -43174,7 +60498,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Fix index out of range error with <code>--fast-list</code> (Nick Craig-Wood)</li>
+<li>Fix index out of range error with <code>--fast-list</code> (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Jottacloud
 <ul>
@@ -43183,19 +60508,22 @@ $ tree /tmp/c
 <li>Calculate missing MD5s (Oliver Heyme)</li>
 <li>Docs, fixes and tests for MD5 calculation (Nick Craig-Wood)</li>
 <li>Add optional MimeTyper interface. (Sebastian Bünger)</li>
-<li>Implement optional About interface (for <code>df</code> support). (Sebastian Bünger)</li>
+<li>Implement optional About interface (for <code>df</code> support).
+(Sebastian Bünger)</li>
 </ul></li>
 <li>Mega
 <ul>
 <li>Wait for events instead of arbitrary sleeping (Nick Craig-Wood)</li>
 <li>Add <code>--mega-hard-delete</code> flag (Nick Craig-Wood)</li>
-<li>Fix failed logins with upper case chars in email (Nick Craig-Wood)</li>
+<li>Fix failed logins with upper case chars in email (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Onedrive
 <ul>
 <li>Shared folder support (Yoni Jah)</li>
 <li>Implement DirMove (Cnly)</li>
-<li>Fix rmdir sometimes deleting directories with contents (Nick Craig-Wood)</li>
+<li>Fix rmdir sometimes deleting directories with contents (Nick
+Craig-Wood)</li>
 </ul></li>
 <li>Pcloud
 <ul>
@@ -43207,7 +60535,8 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Fix index out of range error with <code>--fast-list</code> (Nick Craig-Wood)</li>
+<li>Fix index out of range error with <code>--fast-list</code> (Nick
+Craig-Wood)</li>
 <li>Add <code>--s3-force-path-style</code> (Nick Craig-Wood)</li>
 <li>Add support for KMS Key ID (bsteiss)</li>
 <li>Remove leading / from paths (Nick Craig-Wood)</li>
@@ -43215,16 +60544,21 @@ $ tree /tmp/c
 <li>Swift
 <ul>
 <li>Add <code>storage_policy</code> (Ruben Vandamme)</li>
-<li>Make it so just <code>storage_url</code> or <code>auth_token</code> can be overridden (Nick Craig-Wood)</li>
-<li>Fix server-side copy bug for unusual file names (Nick Craig-Wood)</li>
+<li>Make it so just <code>storage_url</code> or <code>auth_token</code>
+can be overridden (Nick Craig-Wood)</li>
+<li>Fix server-side copy bug for unusual file names (Nick
+Craig-Wood)</li>
 <li>Remove leading / from paths (Nick Craig-Wood)</li>
 </ul></li>
 <li>WebDAV
 <ul>
-<li>Ensure we call MKCOL with a URL with a trailing / for QNAP interop (Nick Craig-Wood)</li>
-<li>If root ends with / then don't check if it is a file (Nick Craig-Wood)</li>
+<li>Ensure we call MKCOL with a URL with a trailing / for QNAP interop
+(Nick Craig-Wood)</li>
+<li>If root ends with / then don't check if it is a file (Nick
+Craig-Wood)</li>
 <li>Don't accept redirects when reading metadata (Nick Craig-Wood)</li>
-<li>Add bearer token (Macaroon) support for dCache (Nick Craig-Wood)</li>
+<li>Add bearer token (Macaroon) support for dCache (Nick
+Craig-Wood)</li>
 <li>Document dCache and Macaroons (Onno Zweers)</li>
 <li>Sharepoint recursion with different depth (Henning)</li>
 <li>Attempt to remove failed uploads (Nick Craig-Wood)</li>
@@ -43246,15 +60580,18 @@ $ tree /tmp/c
 </ul></li>
 <li>New Features
 <ul>
-<li>copy, move: Copy single files directly, don't use <code>--files-from</code> work-around
+<li>copy, move: Copy single files directly, don't use
+<code>--files-from</code> work-around
 <ul>
 <li>this makes them much more efficient</li>
 </ul></li>
-<li>Implement <code>--max-transfer</code> flag to quit transferring at a limit
+<li>Implement <code>--max-transfer</code> flag to quit transferring at a
+limit
 <ul>
 <li>make exit code 8 for <code>--max-transfer</code> exceeded</li>
 </ul></li>
-<li>copy: copy empty source directories to destination (Ishuah Kariuki)</li>
+<li>copy: copy empty source directories to destination (Ishuah
+Kariuki)</li>
 <li>check: Add <code>--one-way</code> flag (Kasper Byrdal Nielsen)</li>
 <li>Add siginfo handler for macOS for ctrl-T stats (kubatasiemski)</li>
 <li>rc
@@ -43265,7 +60602,8 @@ $ tree /tmp/c
 </ul></li>
 <li>lsf
 <ul>
-<li>Add <code>--absolute</code> flag to add a leading / onto path names</li>
+<li>Add <code>--absolute</code> flag to add a leading / onto path
+names</li>
 <li>Add <code>--csv</code> flag for compliant CSV output</li>
 <li>Add 'm' format specifier to show the MimeType</li>
 <li>Implement 'i' format for showing object ID</li>
@@ -43280,39 +60618,47 @@ $ tree /tmp/c
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>Password prompt output with <code>--log-file</code> fixed for unix (Filip Bartodziej)</li>
-<li>Calculate ModifyWindow each time on the fly to fix various problems (Stefan Breunig)</li>
+<li>Password prompt output with <code>--log-file</code> fixed for unix
+(Filip Bartodziej)</li>
+<li>Calculate ModifyWindow each time on the fly to fix various problems
+(Stefan Breunig)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Only print "File.rename error" if there actually is an error (Stefan Breunig)</li>
-<li>Delay rename if file has open writers instead of failing outright (Stefan Breunig)</li>
+<li>Only print "File.rename error" if there actually is an error (Stefan
+Breunig)</li>
+<li>Delay rename if file has open writers instead of failing outright
+(Stefan Breunig)</li>
 <li>Ensure atexit gets run on interrupt</li>
 <li>macOS enhancements
 <ul>
 <li>Make <code>--noappledouble</code> <code>--noapplexattr</code></li>
-<li>Add <code>--volname</code> flag and remove special chars from it</li>
+<li>Add <code>--volname</code> flag and remove special chars from
+it</li>
 <li>Make Get/List/Set/Remove xattr return ENOSYS for efficiency</li>
 <li>Make <code>--daemon</code> work for macOS without CGO</li>
 </ul></li>
 </ul></li>
 <li>VFS
 <ul>
-<li>Add <code>--vfs-read-chunk-size</code> and <code>--vfs-read-chunk-size-limit</code> (Fabian Möller)</li>
+<li>Add <code>--vfs-read-chunk-size</code> and
+<code>--vfs-read-chunk-size-limit</code> (Fabian Möller)</li>
 <li>Fix ChangeNotify for new or changed folders (Fabian Möller)</li>
 </ul></li>
 <li>Local
 <ul>
 <li>Fix symlink/junction point directory handling under Windows
 <ul>
-<li><strong>NB</strong> you will need to add <code>-L</code> to your command line to copy files with reparse points</li>
+<li><strong>NB</strong> you will need to add <code>-L</code> to your
+command line to copy files with reparse points</li>
 </ul></li>
 </ul></li>
 <li>Cache
 <ul>
 <li>Add non cached dirs on notifications (Remus Bunduc)</li>
 <li>Allow root to be expired from rc (Remus Bunduc)</li>
-<li>Clean remaining empty folders from temp upload path (Remus Bunduc)</li>
+<li>Clean remaining empty folders from temp upload path (Remus
+Bunduc)</li>
 <li>Cache lists using batch writes (Remus Bunduc)</li>
 <li>Use secure websockets for HTTPS Plex addresses (John Clayton)</li>
 <li>Reconnect plex websocket on failures (Remus Bunduc)</li>
@@ -43321,11 +60667,13 @@ $ tree /tmp/c
 </ul></li>
 <li>Crypt
 <ul>
-<li>Check the encrypted hash of files when uploading for extra data security</li>
+<li>Check the encrypted hash of files when uploading for extra data
+security</li>
 </ul></li>
 <li>Dropbox
 <ul>
-<li>Make Dropbox for business folders accessible using an initial <code>/</code> in the path</li>
+<li>Make Dropbox for business folders accessible using an initial
+<code>/</code> in the path</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
@@ -43333,21 +60681,27 @@ $ tree /tmp/c
 </ul></li>
 <li>Google Drive
 <ul>
-<li>Add <code>--drive-acknowledge-abuse</code> to download flagged files</li>
-<li>Add <code>--drive-alternate-export</code> to fix large doc export</li>
-<li>Don't attempt to choose Team Drives when using rclone config create</li>
+<li>Add <code>--drive-acknowledge-abuse</code> to download flagged
+files</li>
+<li>Add <code>--drive-alternate-export</code> to fix large doc
+export</li>
+<li>Don't attempt to choose Team Drives when using rclone config
+create</li>
 <li>Fix change list polling with team drives</li>
 <li>Fix ChangeNotify for folders (Fabian Möller)</li>
 <li>Fix about (and df on a mount) for team drives</li>
 </ul></li>
 <li>Onedrive
 <ul>
-<li>Errorhandler for onedrive for business requests (Henning Surmeier)</li>
+<li>Errorhandler for onedrive for business requests (Henning
+Surmeier)</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Adjust upload concurrency with <code>--s3-upload-concurrency</code> (themylogin)</li>
-<li>Fix <code>--s3-chunk-size</code> which was always using the minimum</li>
+<li>Adjust upload concurrency with <code>--s3-upload-concurrency</code>
+(themylogin)</li>
+<li>Fix <code>--s3-chunk-size</code> which was always using the
+minimum</li>
 </ul></li>
 <li>SFTP
 <ul>
@@ -43372,14 +60726,16 @@ $ tree /tmp/c
 <ul>
 <li>link: create public link to files and folders (Stefan Breunig)</li>
 <li>about: gets quota info from a remote (a-roussos, ncw)</li>
-<li>hashsum: a generic tool for any hash to produce md5sum like output</li>
+<li>hashsum: a generic tool for any hash to produce md5sum like
+output</li>
 </ul></li>
 <li>New Features
 <ul>
 <li>lsd: Add -R flag and fix and update docs for all ls commands</li>
 <li>ncdu: added a "refresh" key - CTRL-L (Keith Goldfarb)</li>
 <li>serve restic: Add append-only mode (Steve Kriss)</li>
-<li>serve restic: Disallow overwriting files in append-only mode (Alexander Neumann)</li>
+<li>serve restic: Disallow overwriting files in append-only mode
+(Alexander Neumann)</li>
 <li>serve restic: Print actual listener address (Matt Holt)</li>
 <li>size: Add --json flag (Matthew Holt)</li>
 <li>sync: implement --ignore-errors (Mateusz Pabian)</li>
@@ -43407,7 +60763,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Mount
 <ul>
-<li>Use About to return the correct disk total/used/free (e.g. in <code>df</code>)</li>
+<li>Use About to return the correct disk total/used/free (e.g. in
+<code>df</code>)</li>
 <li>Set <code>--attr-timeout default</code> to <code>1s</code> - fixes:
 <ul>
 <li>rclone using too much memory</li>
@@ -43418,7 +60775,8 @@ $ tree /tmp/c
 </ul></li>
 <li>VFS
 <ul>
-<li>Filter files <code>.</code> and <code>..</code> from directory listing</li>
+<li>Filter files <code>.</code> and <code>..</code> from directory
+listing</li>
 <li>Only make the VFS cache if --vfs-cache-mode &gt; Off</li>
 </ul></li>
 <li>Local
@@ -43437,7 +60795,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Box
 <ul>
-<li>Fix failure reading large directories - parse file/directory size as float</li>
+<li>Fix failure reading large directories - parse file/directory size as
+float</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -43453,7 +60812,8 @@ $ tree /tmp/c
 <li>Google Cloud Storage
 <ul>
 <li>Add service_account_credentials (Matt Holt)</li>
-<li>Detect bucket presence by listing it - minimises permissions needed</li>
+<li>Detect bucket presence by listing it - minimises permissions
+needed</li>
 <li>Ignore zero length directory markers</li>
 </ul></li>
 <li>Google Drive
@@ -43461,7 +60821,8 @@ $ tree /tmp/c
 <li>Add service_account_credentials (Matt Holt)</li>
 <li>Fix directory move leaving a hardlinked directory behind</li>
 <li>Return proper google errors when Opening files</li>
-<li>When initialized with a filepath, optional features used incorrect root path (Stefan Breunig)</li>
+<li>When initialized with a filepath, optional features used incorrect
+root path (Stefan Breunig)</li>
 </ul></li>
 <li>HTTP
 <ul>
@@ -43475,7 +60836,8 @@ $ tree /tmp/c
 <li>S3
 <ul>
 <li>Look in S3 named profile files for credentials</li>
-<li>Add <code>--s3-disable-checksum</code> to disable checksum uploading (Chris Redekop)</li>
+<li>Add <code>--s3-disable-checksum</code> to disable checksum uploading
+(Chris Redekop)</li>
 <li>Hierarchical configuration support (Giri Badanahatti)</li>
 <li>Add in config for all the supported S3 providers</li>
 <li>Add One Zone Infrequent Access storage class (Craig Rachel)</li>
@@ -43485,7 +60847,8 @@ $ tree /tmp/c
 </ul></li>
 <li>SFTP
 <ul>
-<li>Update docs to match code, fix typos and clarify disable_hashcheck prompt (Michael G. Noll)</li>
+<li>Update docs to match code, fix typos and clarify disable_hashcheck
+prompt (Michael G. Noll)</li>
 <li>Update docs with Synology quirks</li>
 <li>Fail soft with a debug on hash failure</li>
 </ul></li>
@@ -43503,16 +60866,19 @@ $ tree /tmp/c
 <ul>
 <li>New backends
 <ul>
-<li>Alias backend to create aliases for existing remote names (Fabian Möller)</li>
+<li>Alias backend to create aliases for existing remote names (Fabian
+Möller)</li>
 </ul></li>
 <li>New commands
 <ul>
 <li><code>lsf</code>: list for parsing purposes (Jakub Tasiemski)
 <ul>
-<li>by default this is a simple non recursive list of files and directories</li>
+<li>by default this is a simple non recursive list of files and
+directories</li>
 <li>it can be configured to add more info in an easy to parse way</li>
 </ul></li>
-<li><code>serve restic</code>: for serving a remote as a Restic REST endpoint
+<li><code>serve restic</code>: for serving a remote as a Restic REST
+endpoint
 <ul>
 <li>This enables restic to use any backends that rclone can access</li>
 <li>Thanks Alexander Neumann for help, patches and review</li>
@@ -43520,26 +60886,35 @@ $ tree /tmp/c
 <li><code>rc</code>: enable the remote control of a running rclone
 <ul>
 <li>The running rclone must be started with --rc and related flags.</li>
-<li>Currently there is support for bwlimit, and flushing for mount and cache.</li>
+<li>Currently there is support for bwlimit, and flushing for mount and
+cache.</li>
 </ul></li>
 </ul></li>
 <li>New Features
 <ul>
-<li><code>--max-delete</code> flag to add a delete threshold (Bjørn Erik Pedersen)</li>
+<li><code>--max-delete</code> flag to add a delete threshold (Bjørn Erik
+Pedersen)</li>
 <li>All backends now support RangeOption for ranged Open
 <ul>
-<li><code>cat</code>: Use RangeOption for limited fetches to make more efficient</li>
-<li><code>cryptcheck</code>: make reading of nonce more efficient with RangeOption</li>
+<li><code>cat</code>: Use RangeOption for limited fetches to make more
+efficient</li>
+<li><code>cryptcheck</code>: make reading of nonce more efficient with
+RangeOption</li>
 </ul></li>
 <li>serve http/webdav/restic
 <ul>
 <li>support SSL/TLS</li>
-<li>add <code>--user</code> <code>--pass</code> and <code>--htpasswd</code> for authentication</li>
+<li>add <code>--user</code> <code>--pass</code> and
+<code>--htpasswd</code> for authentication</li>
 </ul></li>
-<li><code>copy</code>/<code>move</code>: detect file size change during copy/move and abort transfer (ishuah)</li>
-<li><code>cryptdecode</code>: added option to return encrypted file names. (ishuah)</li>
-<li><code>lsjson</code>: add <code>--encrypted</code> to show encrypted name (Jakub Tasiemski)</li>
-<li>Add <code>--stats-file-name-length</code> to specify the printed file name length for stats (Will Gunn)</li>
+<li><code>copy</code>/<code>move</code>: detect file size change during
+copy/move and abort transfer (ishuah)</li>
+<li><code>cryptdecode</code>: added option to return encrypted file
+names. (ishuah)</li>
+<li><code>lsjson</code>: add <code>--encrypted</code> to show encrypted
+name (Jakub Tasiemski)</li>
+<li>Add <code>--stats-file-name-length</code> to specify the printed
+file name length for stats (Will Gunn)</li>
 </ul></li>
 <li>Compile
 <ul>
@@ -43550,43 +60925,56 @@ $ tree /tmp/c
 <li>See the CONTRIBUTING.md doc for info as to what lives where now</li>
 </ul></li>
 <li>Update to using go1.10 as the default go version</li>
-<li>Implement daily <a href="https://pub.rclone.org/integration-tests/">full integration tests</a></li>
+<li>Implement daily <a
+href="https://pub.rclone.org/integration-tests/">full integration
+tests</a></li>
 </ul></li>
 <li>Release
 <ul>
 <li>Include a source tarball and sign it and the binaries</li>
 <li>Sign the git tags as part of the release process</li>
 <li>Add .deb and .rpm packages as part of the build</li>
-<li>Make a beta release for all branches on the main repo (but not pull requests)</li>
+<li>Make a beta release for all branches on the main repo (but not pull
+requests)</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>config: fixes errors on nonexistent config by loading config file only on first access</li>
+<li>config: fixes errors on nonexistent config by loading config file
+only on first access</li>
 <li>config: retry saving the config after failure (Mateusz)</li>
-<li>sync: when using <code>--backup-dir</code> don't delete files if we can't set their modtime
+<li>sync: when using <code>--backup-dir</code> don't delete files if we
+can't set their modtime
 <ul>
-<li>this fixes odd behaviour with Dropbox and <code>--backup-dir</code></li>
+<li>this fixes odd behaviour with Dropbox and
+<code>--backup-dir</code></li>
 </ul></li>
 <li>fshttp: fix idle timeouts for HTTP connections</li>
 <li><code>serve http</code>: fix serving files with : in - fixes</li>
-<li>Fix <code>--exclude-if-present</code> to ignore directories which it doesn't have permission for (Iakov Davydov)</li>
+<li>Fix <code>--exclude-if-present</code> to ignore directories which it
+doesn't have permission for (Iakov Davydov)</li>
 <li>Make accounting work properly with crypt and b2</li>
 <li>remove <code>--no-traverse</code> flag because it is obsolete</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Add <code>--attr-timeout</code> flag to control attribute caching in kernel
+<li>Add <code>--attr-timeout</code> flag to control attribute caching in
+kernel
 <ul>
 <li>this now defaults to 0 which is correct but less efficient</li>
-<li>see <a href="https://rclone.org/commands/rclone_mount/#attribute-caching">the mount docs</a> for more info</li>
+<li>see <a
+href="https://rclone.org/commands/rclone_mount/#attribute-caching">the
+mount docs</a> for more info</li>
 </ul></li>
-<li>Add <code>--daemon</code> flag to allow mount to run in the background (ishuah)</li>
+<li>Add <code>--daemon</code> flag to allow mount to run in the
+background (ishuah)</li>
 <li>Fix: Return ENOSYS rather than EIO on attempted link
 <ul>
-<li>This fixes FileZilla accessing an rclone mount served over sftp.</li>
+<li>This fixes FileZilla accessing an rclone mount served over
+sftp.</li>
 </ul></li>
 <li>Fix setting modtime twice</li>
-<li>Mount tests now run on CI for Linux (mount &amp; cmount)/Mac/Windows</li>
+<li>Mount tests now run on CI for Linux (mount &amp;
+cmount)/Mac/Windows</li>
 <li>Many bugs fixed in the VFS layer - see below</li>
 </ul></li>
 <li>VFS
@@ -43595,25 +60983,29 @@ $ tree /tmp/c
 <ul>
 <li>Update cached copy if we know it has changed (fixes stale data)</li>
 <li>Clean path names before using them in the cache</li>
-<li>Disable cache cleaner if <code>--vfs-cache-poll-interval=0</code></li>
+<li>Disable cache cleaner if
+<code>--vfs-cache-poll-interval=0</code></li>
 <li>Fill and clean the cache immediately on startup</li>
 </ul></li>
 <li>Fix Windows opening every file when it stats the file</li>
 <li>Fix applying modtime for an open Write Handle</li>
 <li>Fix creation of files when truncating</li>
-<li>Write 0 bytes when flushing unwritten handles to avoid race conditions in FUSE</li>
+<li>Write 0 bytes when flushing unwritten handles to avoid race
+conditions in FUSE</li>
 <li>Downgrade "poll-interval is not supported" message to Info</li>
 <li>Make OpenFile and friends return EINVAL if O_RDONLY and O_TRUNC</li>
 </ul></li>
 <li>Local
 <ul>
 <li>Downgrade "invalid cross-device link: trying copy" to debug</li>
-<li>Make DirMove return fs.ErrorCantDirMove to allow fallback to Copy for cross device</li>
+<li>Make DirMove return fs.ErrorCantDirMove to allow fallback to Copy
+for cross device</li>
 <li>Fix race conditions updating the hashes</li>
 </ul></li>
 <li>Cache
 <ul>
-<li>Add support for polling - cache will update when remote changes on supported backends</li>
+<li>Add support for polling - cache will update when remote changes on
+supported backends</li>
 <li>Reduce log level for Plex api</li>
 <li>Fix dir cache issue</li>
 <li>Implement <code>--cache-db-wait-time</code> flag</li>
@@ -43625,7 +61017,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Amazon cloud drive
 <ul>
-<li>Rclone no longer has any working keys - disable integration tests</li>
+<li>Rclone no longer has any working keys - disable integration
+tests</li>
 <li>Implement DirChangeNotify to notify cache/vfs/mount of changes</li>
 </ul></li>
 <li>Azureblob
@@ -43666,14 +61059,17 @@ $ tree /tmp/c
 <ul>
 <li>thanks to everyone who tested, explored and contributed docs</li>
 </ul></li>
-<li>Add <code>--drive-use-created-date</code> to use created date as modified date (nbuchanan)</li>
+<li>Add <code>--drive-use-created-date</code> to use created date as
+modified date (nbuchanan)</li>
 <li>Request the export formats only when required
 <ul>
 <li>This makes rclone quicker when there are no google docs</li>
 </ul></li>
-<li>Fix finding paths with latin1 chars (a workaround for a drive bug)</li>
+<li>Fix finding paths with latin1 chars (a workaround for a drive
+bug)</li>
 <li>Fix copying of a single Google doc file</li>
-<li>Fix <code>--drive-auth-owner-only</code> to look in all directories</li>
+<li>Fix <code>--drive-auth-owner-only</code> to look in all
+directories</li>
 </ul></li>
 <li>HTTP
 <ul>
@@ -43683,9 +61079,11 @@ $ tree /tmp/c
 <ul>
 <li>Removed upload cutoff and always do session uploads
 <ul>
-<li>this stops the creation of multiple versions on business onedrive</li>
+<li>this stops the creation of multiple versions on business
+onedrive</li>
 </ul></li>
-<li>Overwrite object size value with real size when reading file. (Victor)
+<li>Overwrite object size value with real size when reading file.
+(Victor)
 <ul>
 <li>this fixes oddities when onedrive misreports the size of images</li>
 </ul></li>
@@ -43714,19 +61112,23 @@ $ tree /tmp/c
 </ul></li>
 <li>SFTP
 <ul>
-<li>Add option to disable remote hash check command execution (Jon Fautley)</li>
-<li>Add <code>--sftp-ask-password</code> flag to prompt for password when needed (Leo R. Lundgren)</li>
+<li>Add option to disable remote hash check command execution (Jon
+Fautley)</li>
+<li>Add <code>--sftp-ask-password</code> flag to prompt for password
+when needed (Leo R. Lundgren)</li>
 <li>Add <code>set_modtime</code> configuration option</li>
 <li>Fix following of symlinks</li>
 <li>Fix reading config file outside of Fs setup</li>
 <li>Fix reading $USER in username fallback not $HOME</li>
-<li>Fix running under crontab - Use correct OS way of reading username</li>
+<li>Fix running under crontab - Use correct OS way of reading
+username</li>
 </ul></li>
 <li>Swift
 <ul>
 <li>Fix refresh of authentication token
 <ul>
-<li>in v1.39 a bug was introduced which ignored new tokens - this fixes it</li>
+<li>in v1.39 a bug was introduced which ignored new tokens - this fixes
+it</li>
 </ul></li>
 <li>Fix extra HEAD transaction when uploading a new file</li>
 <li>Don't check for bucket/container presence if listing was OK
@@ -43758,36 +61160,48 @@ $ tree /tmp/c
 <ul>
 <li>serve command with subcommands:
 <ul>
-<li>serve webdav: this implements a webdav server for any rclone remote.</li>
+<li>serve webdav: this implements a webdav server for any rclone
+remote.</li>
 <li>serve http: command to serve a remote over HTTP</li>
 </ul></li>
 <li>config: add sub commands for full config file management
 <ul>
 <li>create/delete/dump/edit/file/password/providers/show/update</li>
 </ul></li>
-<li>touch: to create or update the timestamp of a file (Jakub Tasiemski)</li>
+<li>touch: to create or update the timestamp of a file (Jakub
+Tasiemski)</li>
 </ul></li>
 <li>New Features
 <ul>
 <li>curl install for rclone (Filip Bartodziej)</li>
-<li>--stats now shows percentage, size, rate and ETA in condensed form (Ishuah Kariuki)</li>
-<li>--exclude-if-present to exclude a directory if a file is present (Iakov Davydov)</li>
+<li>--stats now shows percentage, size, rate and ETA in condensed form
+(Ishuah Kariuki)</li>
+<li>--exclude-if-present to exclude a directory if a file is present
+(Iakov Davydov)</li>
 <li>rmdirs: add --leave-root flag (lewapm)</li>
-<li>move: add --delete-empty-src-dirs flag to remove dirs after move (Ishuah Kariuki)</li>
-<li>Add --dump flag, introduce --dump requests, responses and remove --dump-auth, --dump-filters
+<li>move: add --delete-empty-src-dirs flag to remove dirs after move
+(Ishuah Kariuki)</li>
+<li>Add --dump flag, introduce --dump requests, responses and remove
+--dump-auth, --dump-filters
 <ul>
 <li>Obscure X-Auth-Token: from headers when dumping too</li>
 </ul></li>
-<li>Document and implement exit codes for different failure modes (Ishuah Kariuki)</li>
+<li>Document and implement exit codes for different failure modes
+(Ishuah Kariuki)</li>
 </ul></li>
 <li>Compile</li>
 <li>Bug Fixes
 <ul>
-<li>Retry lots more different types of errors to make multipart transfers more reliable</li>
-<li>Save the config before asking for a token, fixes disappearing oauth config</li>
-<li>Warn the user if --include and --exclude are used together (Ernest Borowski)</li>
-<li>Fix duplicate files (e.g. on Google drive) causing spurious copies</li>
-<li>Allow trailing and leading whitespace for passwords (Jason Rose)</li>
+<li>Retry lots more different types of errors to make multipart
+transfers more reliable</li>
+<li>Save the config before asking for a token, fixes disappearing oauth
+config</li>
+<li>Warn the user if --include and --exclude are used together (Ernest
+Borowski)</li>
+<li>Fix duplicate files (e.g. on Google drive) causing spurious
+copies</li>
+<li>Allow trailing and leading whitespace for passwords (Jason
+Rose)</li>
 <li>ncdu: fix crashes on empty directories</li>
 <li>rcat: fix goroutine leak</li>
 <li>moveto/copyto: Fix to allow copying to the same name</li>
@@ -43799,8 +61213,10 @@ $ tree /tmp/c
 <li>this requires caching files on the disk (see --cache-dir)</li>
 <li>As this is a new feature, use with care</li>
 </ul></li>
-<li>Use sdnotify to signal systemd the mount is ready (Fabian Möller)</li>
-<li>Check if directory is not empty before mounting (Ernest Borowski)</li>
+<li>Use sdnotify to signal systemd the mount is ready (Fabian
+Möller)</li>
+<li>Check if directory is not empty before mounting (Ernest
+Borowski)</li>
 </ul></li>
 <li>Local
 <ul>
@@ -43811,8 +61227,10 @@ $ tree /tmp/c
 <ul>
 <li>Rework multipart upload
 <ul>
-<li>buffer the chunks when uploading large files so they can be retried</li>
-<li>change default chunk size to 48MB now we are buffering them in memory</li>
+<li>buffer the chunks when uploading large files so they can be
+retried</li>
+<li>change default chunk size to 48MB now we are buffering them in
+memory</li>
 <li>retry every error after the first chunk is done successfully</li>
 </ul></li>
 <li>Fix error when renaming directories</li>
@@ -43827,7 +61245,8 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Make it work properly with Digital Ocean Spaces (Andrew Starr-Bochicchio)</li>
+<li>Make it work properly with Digital Ocean Spaces (Andrew
+Starr-Bochicchio)</li>
 <li>Fix crash if a bad listing is received</li>
 <li>Add support for ECS task IAM roles (David Minor)</li>
 </ul></li>
@@ -43838,11 +61257,14 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Allow authentication with storage URL and auth key (Giovanni Pizzi)</li>
-<li>Add new fields for swift configuration to support IBM Bluemix Swift (Pierre Carlson)</li>
+<li>Allow authentication with storage URL and auth key (Giovanni
+Pizzi)</li>
+<li>Add new fields for swift configuration to support IBM Bluemix Swift
+(Pierre Carlson)</li>
 <li>Add OS_TENANT_ID and OS_USER_ID to config</li>
 <li>Allow configs with user id instead of user name</li>
-<li>Check if swift segments container exists before creating (John Leach)</li>
+<li>Check if swift segments container exists before creating (John
+Leach)</li>
 <li>Fix memory leak in swift transfers (upstream fix)</li>
 </ul></li>
 <li>SFTP
@@ -43851,7 +61273,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Amazon cloud drive
 <ul>
-<li>Fix download of large files failing with "Only one auth mechanism allowed"</li>
+<li>Fix download of large files failing with "Only one auth mechanism
+allowed"</li>
 </ul></li>
 <li>crypt
 <ul>
@@ -43860,7 +61283,8 @@ $ tree /tmp/c
 </ul></li>
 <li>onedrive
 <ul>
-<li>Add option to choose resourceURL during setup of OneDrive Business account if more than one is available for user</li>
+<li>Add option to choose resourceURL during setup of OneDrive Business
+account if more than one is available for user</li>
 </ul></li>
 </ul>
 <h2 id="v1.38---2017-09-30">v1.38 - 2017-09-30</h2>
@@ -43876,22 +61300,28 @@ $ tree /tmp/c
 <ul>
 <li><code>rcat</code> - read from standard input and stream upload</li>
 <li><code>tree</code> - shows a nicely formatted recursive listing</li>
-<li><code>cryptdecode</code> - decode encrypted file names (thanks ishuah)</li>
+<li><code>cryptdecode</code> - decode encrypted file names (thanks
+ishuah)</li>
 <li><code>config show</code> - print the config file</li>
 <li><code>config file</code> - print the config file location</li>
 </ul></li>
 <li>New Features
 <ul>
 <li>Empty directories are deleted on <code>sync</code></li>
-<li><code>dedupe</code> - implement merging of duplicate directories</li>
-<li><code>check</code> and <code>cryptcheck</code> made more consistent and use less memory</li>
+<li><code>dedupe</code> - implement merging of duplicate
+directories</li>
+<li><code>check</code> and <code>cryptcheck</code> made more consistent
+and use less memory</li>
 <li><code>cleanup</code> for remaining remotes (thanks ishuah)</li>
-<li><code>--immutable</code> for ensuring that files don't change (thanks Jacob McNamee)</li>
+<li><code>--immutable</code> for ensuring that files don't change
+(thanks Jacob McNamee)</li>
 <li><code>--user-agent</code> option (thanks Alex McGrath Kraak)</li>
 <li><code>--disable</code> flag to disable optional features</li>
-<li><code>--bind</code> flag for choosing the local addr on outgoing connections</li>
+<li><code>--bind</code> flag for choosing the local addr on outgoing
+connections</li>
 <li>Support for zsh auto-completion (thanks bpicode)</li>
-<li>Stop normalizing file names but do a normalized compare in <code>sync</code></li>
+<li>Stop normalizing file names but do a normalized compare in
+<code>sync</code></li>
 </ul></li>
 <li>Compile
 <ul>
@@ -43900,19 +61330,24 @@ $ tree /tmp/c
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>Improve retriable error detection which makes multipart uploads better</li>
+<li>Improve retriable error detection which makes multipart uploads
+better</li>
 <li>Make <code>check</code> obey <code>--ignore-size</code></li>
-<li>Fix bwlimit toggle in conjunction with schedules (thanks cbruegg)</li>
-<li><code>config</code> ensures newly written config is on the same mount</li>
+<li>Fix bwlimit toggle in conjunction with schedules (thanks
+cbruegg)</li>
+<li><code>config</code> ensures newly written config is on the same
+mount</li>
 </ul></li>
 <li>Local
 <ul>
 <li>Revert to copy when moving file across file system boundaries</li>
-<li><code>--skip-links</code> to suppress symlink warnings (thanks Zhiming Wang)</li>
+<li><code>--skip-links</code> to suppress symlink warnings (thanks
+Zhiming Wang)</li>
 </ul></li>
 <li>Mount
 <ul>
-<li>Reuse <code>rcat</code> internals to support uploads from all remotes</li>
+<li>Reuse <code>rcat</code> internals to support uploads from all
+remotes</li>
 </ul></li>
 <li>Dropbox
 <ul>
@@ -43921,11 +61356,13 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Fix server-side copy to empty container with <code>--fast-list</code></li>
+<li>Fix server-side copy to empty container with
+<code>--fast-list</code></li>
 </ul></li>
 <li>Google Drive
 <ul>
-<li>Change the default for <code>--drive-use-trash</code> to <code>true</code></li>
+<li>Change the default for <code>--drive-use-trash</code> to
+<code>true</code></li>
 </ul></li>
 <li>S3
 <ul>
@@ -43937,15 +61374,18 @@ $ tree /tmp/c
 <ul>
 <li>Fix SHA1 mismatch when downloading files with no SHA1</li>
 <li>Calculate missing hashes on the fly instead of spooling</li>
-<li><code>--b2-hard-delete</code> to permanently delete (not hide) files (thanks John Papandriopoulos)</li>
+<li><code>--b2-hard-delete</code> to permanently delete (not hide) files
+(thanks John Papandriopoulos)</li>
 </ul></li>
 <li>Hubic
 <ul>
-<li>Fix creating containers - no longer have to use the <code>default</code> container</li>
+<li>Fix creating containers - no longer have to use the
+<code>default</code> container</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Optionally configure from a standard set of OpenStack environment vars</li>
+<li>Optionally configure from a standard set of OpenStack environment
+vars</li>
 <li>Add <code>endpoint_type</code> config</li>
 </ul></li>
 <li>Google Cloud Storage
@@ -43956,7 +61396,8 @@ $ tree /tmp/c
 <ul>
 <li>Implement connection pooling for multiple ssh connections</li>
 <li>Limit new connections per second</li>
-<li>Add support for MD5 and SHA1 hashes where available (thanks Christian Brüggemann)</li>
+<li>Add support for MD5 and SHA1 hashes where available (thanks
+Christian Brüggemann)</li>
 </ul></li>
 <li>HTTP
 <ul>
@@ -43974,9 +61415,11 @@ $ tree /tmp/c
 </ul></li>
 <li>New commands
 <ul>
-<li>rclone ncdu - for exploring a remote with a text based user interface.</li>
+<li>rclone ncdu - for exploring a remote with a text based user
+interface.</li>
 <li>rclone lsjson - for listing with a machine-readable output</li>
-<li>rclone dbhashsum - to show Dropbox style hashes of files (local or Dropbox)</li>
+<li>rclone dbhashsum - to show Dropbox style hashes of files (local or
+Dropbox)</li>
 </ul></li>
 <li>New Features
 <ul>
@@ -43985,13 +61428,16 @@ $ tree /tmp/c
 <li>This allows remotes to list recursively if they can</li>
 <li>This uses less transactions (important if you pay for them)</li>
 <li>This may or may not be quicker</li>
-<li>This will use more memory as it has to hold the listing in memory</li>
-<li>--old-sync-method deprecated - the remaining uses are covered by --fast-list</li>
+<li>This will use more memory as it has to hold the listing in
+memory</li>
+<li>--old-sync-method deprecated - the remaining uses are covered by
+--fast-list</li>
 <li>This involved a major re-write of all the listing code</li>
 </ul></li>
 <li>Add --tpslimit and --tpslimit-burst to limit transactions per second
 <ul>
-<li>this is useful in conjunction with <code>rclone mount</code> to limit external apps</li>
+<li>this is useful in conjunction with <code>rclone mount</code> to
+limit external apps</li>
 </ul></li>
 <li>Add --stats-log-level so can see --stats without -v</li>
 <li>Print password prompts to stderr - Hraban Luyat</li>
@@ -44014,7 +61460,8 @@ $ tree /tmp/c
 <li>Fix menu selection when no remotes</li>
 <li>Config saving reworked to not kill the file if disk gets full</li>
 <li>Don't delete remote if name does not change while renaming</li>
-<li>moveto, copyto: report transfers and checks as per move and copy</li>
+<li>moveto, copyto: report transfers and checks as per move and
+copy</li>
 </ul></li>
 <li>Local
 <ul>
@@ -44022,9 +61469,11 @@ $ tree /tmp/c
 </ul></li>
 <li>Mount
 <ul>
-<li>Now supported on Windows using cgofuse and WinFsp - thanks to Bill Zissimopoulos for much help</li>
+<li>Now supported on Windows using cgofuse and WinFsp - thanks to Bill
+Zissimopoulos for much help</li>
 <li>Compare checksums on upload/download via FUSE</li>
-<li>Unmount when program ends with SIGINT (Ctrl+C) or SIGTERM - Jérôme Vizcaino</li>
+<li>Unmount when program ends with SIGINT (Ctrl+C) or SIGTERM - Jérôme
+Vizcaino</li>
 <li>On read only open of file, make open pending until first read</li>
 <li>Make --read-only reject modify operations</li>
 <li>Implement ModTime via FUSE for remotes that support it</li>
@@ -44035,12 +61484,14 @@ $ tree /tmp/c
 <li>Crypt
 <ul>
 <li>Report the name:root as specified by the user</li>
-<li>Add an "obfuscate" option for filename encryption - Stephen Harris</li>
+<li>Add an "obfuscate" option for filename encryption - Stephen
+Harris</li>
 </ul></li>
 <li>Amazon Drive
 <ul>
 <li>Fix initialization order for token renewer</li>
-<li>Remove revoked credentials, allow oauth proxy config and update docs</li>
+<li>Remove revoked credentials, allow oauth proxy config and update
+docs</li>
 </ul></li>
 <li>B2
 <ul>
@@ -44049,8 +61500,10 @@ $ tree /tmp/c
 <li>Drive
 <ul>
 <li>Add team drive support</li>
-<li>Reduce bandwidth by adding fields for partial responses - Martin Kristensen</li>
-<li>Implement --drive-shared-with-me flag to view shared with me files - Danny Tsai</li>
+<li>Reduce bandwidth by adding fields for partial responses - Martin
+Kristensen</li>
+<li>Implement --drive-shared-with-me flag to view shared with me files -
+Danny Tsai</li>
 <li>Add --drive-trashed-only to read only the files in the trash</li>
 <li>Remove obsolete --drive-full-list</li>
 <li>Add missing seek to start on retries of chunked uploads</li>
@@ -44063,14 +61516,18 @@ $ tree /tmp/c
 <li>Fix the uploading of files with spaces</li>
 <li>Fix initialization order for token renewer</li>
 <li>Display speeds accurately when uploading - Yoni Jah</li>
-<li>Swap to using http://localhost:53682/ as redirect URL - Michael Ledin</li>
-<li>Retry on token expired error, reset upload body on retry - Yoni Jah</li>
+<li>Swap to using http://localhost:53682/ as redirect URL - Michael
+Ledin</li>
+<li>Retry on token expired error, reset upload body on retry - Yoni
+Jah</li>
 </ul></li>
 <li>Google Cloud Storage
 <ul>
-<li>Add ability to specify location and storage class via config and command line - thanks gdm85</li>
+<li>Add ability to specify location and storage class via config and
+command line - thanks gdm85</li>
 <li>Create container if necessary on server-side copy</li>
-<li>Increase directory listing chunk to 1000 to increase performance</li>
+<li>Increase directory listing chunk to 1000 to increase
+performance</li>
 <li>Obtain a refresh token for GCS - Steven Lu</li>
 </ul></li>
 <li>Yandex
@@ -44085,8 +61542,10 @@ $ tree /tmp/c
 <li>Now supports ModTime
 <ul>
 <li>Can only set by uploading the file again</li>
-<li>If you uploaded with an old rclone, rclone may upload everything again</li>
-<li>Use <code>--size-only</code> or <code>--checksum</code> to avoid this</li>
+<li>If you uploaded with an old rclone, rclone may upload everything
+again</li>
+<li>Use <code>--size-only</code> or <code>--checksum</code> to avoid
+this</li>
 </ul></li>
 <li>Now supports the Dropbox content hashing scheme</li>
 <li>Now supports low level retries</li>
@@ -44096,11 +61555,13 @@ $ tree /tmp/c
 <ul>
 <li>Work around eventual consistency in bucket creation</li>
 <li>Create container if necessary on server-side copy</li>
-<li>Add us-east-2 (Ohio) and eu-west-2 (London) S3 regions - Zahiar Ahmed</li>
+<li>Add us-east-2 (Ohio) and eu-west-2 (London) S3 regions - Zahiar
+Ahmed</li>
 </ul></li>
 <li>Swift, Hubic
 <ul>
-<li>Fix zero length directory markers showing in the subdirectory listing
+<li>Fix zero length directory markers showing in the subdirectory
+listing
 <ul>
 <li>this caused lots of duplicate transfers</li>
 </ul></li>
@@ -44109,7 +61570,8 @@ $ tree /tmp/c
 <li>this caused duplicate directory errors</li>
 </ul></li>
 <li>Create container if necessary on server-side copy</li>
-<li>Increase directory listing chunk to 1000 to increase performance</li>
+<li>Increase directory listing chunk to 1000 to increase
+performance</li>
 <li>Make sensible error if the user forgets the container</li>
 </ul></li>
 <li>SFTP
@@ -44125,24 +61587,33 @@ $ tree /tmp/c
 <li>New Features
 <ul>
 <li>SFTP remote (Jack Schmidt)</li>
-<li>Re-implement sync routine to work a directory at a time reducing memory usage</li>
-<li>Logging revamped to be more inline with rsync - now much quieter * -v only shows transfers * -vv is for full debug * --syslog to log to syslog on capable platforms</li>
+<li>Re-implement sync routine to work a directory at a time reducing
+memory usage</li>
+<li>Logging revamped to be more inline with rsync - now much quieter *
+-v only shows transfers * -vv is for full debug * --syslog to log to
+syslog on capable platforms</li>
 <li>Implement --backup-dir and --suffix</li>
-<li>Implement --track-renames (initial implementation by Bjørn Erik Pedersen)</li>
+<li>Implement --track-renames (initial implementation by Bjørn Erik
+Pedersen)</li>
 <li>Add time-based bandwidth limits (Lukas Loesche)</li>
 <li>rclone cryptcheck: checks integrity of crypt remotes</li>
-<li>Allow all config file variables and options to be set from environment variables</li>
+<li>Allow all config file variables and options to be set from
+environment variables</li>
 <li>Add --buffer-size parameter to control buffer size for copy</li>
 <li>Make --delete-after the default</li>
 <li>Add --ignore-checksum flag (fixed by Hisham Zarka)</li>
-<li>rclone check: Add --download flag to check all the data, not just hashes</li>
+<li>rclone check: Add --download flag to check all the data, not just
+hashes</li>
 <li>rclone cat: add --head, --tail, --offset, --count and --discard</li>
-<li>rclone config: when choosing from a list, allow the value to be entered too</li>
+<li>rclone config: when choosing from a list, allow the value to be
+entered too</li>
 <li>rclone config: allow rename and copy of remotes</li>
-<li>rclone obscure: for generating encrypted passwords for rclone's config (T.C. Ferguson)</li>
+<li>rclone obscure: for generating encrypted passwords for rclone's
+config (T.C. Ferguson)</li>
 <li>Comply with XDG Base Directory specification (Dario Giovannetti)
 <ul>
-<li>this moves the default location of the config file in a backwards compatible way</li>
+<li>this moves the default location of the config file in a backwards
+compatible way</li>
 </ul></li>
 <li>Release changes
 <ul>
@@ -44153,7 +61624,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>Fix copyto copying things to the wrong place if the destination dir didn't exist</li>
+<li>Fix copyto copying things to the wrong place if the destination dir
+didn't exist</li>
 <li>Fix parsing of remotes in moveto and copyto</li>
 <li>Fix --delete-before deleting files on copy</li>
 <li>Fix --files-from with an empty file copying everything</li>
@@ -44163,8 +61635,10 @@ $ tree /tmp/c
 </ul></li>
 <li>Local
 <ul>
-<li>Implement -L, --copy-links flag to allow rclone to follow symlinks</li>
-<li>Open files in write only mode so rclone can write to an rclone mount</li>
+<li>Implement -L, --copy-links flag to allow rclone to follow
+symlinks</li>
+<li>Open files in write only mode so rclone can write to an rclone
+mount</li>
 <li>Fix unnormalised unicode causing problems reading directories</li>
 <li>Fix interaction between -x flag and --max-depth</li>
 </ul></li>
@@ -44172,7 +61646,8 @@ $ tree /tmp/c
 <ul>
 <li>Implement proper directory handling (mkdir, rmdir, renaming)</li>
 <li>Make include and exclude filters apply to mount</li>
-<li>Implement read and write async buffers - control with --buffer-size</li>
+<li>Implement read and write async buffers - control with
+--buffer-size</li>
 <li>Fix fsync on for directories</li>
 <li>Fix retry on network failure when reading off crypt</li>
 </ul></li>
@@ -44181,12 +61656,14 @@ $ tree /tmp/c
 <li>Add --crypt-show-mapping to show encrypted file mapping</li>
 <li>Fix crypt writer getting stuck in a loop
 <ul>
-<li><strong>IMPORTANT</strong> this bug had the potential to cause data corruption when
+<li><strong>IMPORTANT</strong> this bug had the potential to cause data
+corruption when
 <ul>
 <li>reading data from a network based remote and</li>
 <li>writing to a crypt on Google Drive</li>
 </ul></li>
-<li>Use the cryptcheck command to validate your data if you are concerned</li>
+<li>Use the cryptcheck command to validate your data if you are
+concerned</li>
 <li>If syncing two crypt remotes, sync the unencrypted remote</li>
 </ul></li>
 </ul></li>
@@ -44242,19 +61719,22 @@ $ tree /tmp/c
 <ul>
 <li>New Features
 <ul>
-<li>moveto and copyto commands for choosing a destination name on copy/move</li>
+<li>moveto and copyto commands for choosing a destination name on
+copy/move</li>
 <li>rmdirs command to recursively delete empty directories</li>
 <li>Allow repeated --include/--exclude/--filter options</li>
 <li>Only show transfer stats on commands which transfer stuff
 <ul>
 <li>show stats on any command using the <code>--stats</code> flag</li>
 </ul></li>
-<li>Allow overlapping directories in move when server-side dir move is supported</li>
+<li>Allow overlapping directories in move when server-side dir move is
+supported</li>
 <li>Add --stats-unit option - thanks Scott McGillivray</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>Fix the config file being overwritten when two rclone instances are running</li>
+<li>Fix the config file being overwritten when two rclone instances are
+running</li>
 <li>Make rclone lsd obey the filters properly</li>
 <li>Fix compilation on mips</li>
 <li>Fix not transferring files that don't differ in size</li>
@@ -44265,7 +61745,8 @@ $ tree /tmp/c
 <li>Retry reads on error - should help with reliability a lot</li>
 <li>Report the modification times for directories from the remote</li>
 <li>Add bandwidth accounting and limiting (fixes --bwlimit)</li>
-<li>If --stats provided will show stats and which files are transferring</li>
+<li>If --stats provided will show stats and which files are
+transferring</li>
 <li>Support R/W files if truncate is set.</li>
 <li>Implement statfs interface so df works</li>
 <li>Note that write is now supported on Amazon Drive</li>
@@ -44281,16 +61762,19 @@ $ tree /tmp/c
 </ul></li>
 <li>Amazon Drive
 <ul>
-<li>Add support for server-side move and directory move - thanks Stefan Breunig</li>
+<li>Add support for server-side move and directory move - thanks Stefan
+Breunig</li>
 <li>Fix nil pointer deref on size attribute</li>
 </ul></li>
 <li>B2
 <ul>
 <li>Use new prefix and delimiter parameters in directory listings
 <ul>
-<li>This makes --max-depth 1 dir listings as used in mount much faster</li>
+<li>This makes --max-depth 1 dir listings as used in mount much
+faster</li>
 </ul></li>
-<li>Reauth the account while doing uploads too - should help with token expiry</li>
+<li>Reauth the account while doing uploads too - should help with token
+expiry</li>
 </ul></li>
 <li>Drive
 <ul>
@@ -44302,14 +61786,18 @@ $ tree /tmp/c
 <ul>
 <li>New Features
 <ul>
-<li>Stop single file and <code>--files-from</code> operations iterating through the source bucket.</li>
+<li>Stop single file and <code>--files-from</code> operations iterating
+through the source bucket.</li>
 <li>Stop removing failed upload to cloud storage remotes</li>
 <li>Make ContentType be preserved for cloud to cloud copies</li>
-<li>Add support to toggle bandwidth limits via SIGUSR2 - thanks Marco Paganini</li>
-<li><code>rclone check</code> shows count of hashes that couldn't be checked</li>
+<li>Add support to toggle bandwidth limits via SIGUSR2 - thanks Marco
+Paganini</li>
+<li><code>rclone check</code> shows count of hashes that couldn't be
+checked</li>
 <li><code>rclone listremotes</code> command</li>
 <li>Support linux/arm64 build - thanks Fredrik Fornwall</li>
-<li>Remove <code>Authorization:</code> lines from <code>--dump-headers</code> output</li>
+<li>Remove <code>Authorization:</code> lines from
+<code>--dump-headers</code> output</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
@@ -44328,10 +61816,15 @@ $ tree /tmp/c
 <ul>
 <li>Implement FUSE mount options
 <ul>
-<li><code>--no-modtime</code>, <code>--debug-fuse</code>, <code>--read-only</code>, <code>--allow-non-empty</code>, <code>--allow-root</code>, <code>--allow-other</code></li>
-<li><code>--default-permissions</code>, <code>--write-back-cache</code>, <code>--max-read-ahead</code>, <code>--umask</code>, <code>--uid</code>, <code>--gid</code></li>
+<li><code>--no-modtime</code>, <code>--debug-fuse</code>,
+<code>--read-only</code>, <code>--allow-non-empty</code>,
+<code>--allow-root</code>, <code>--allow-other</code></li>
+<li><code>--default-permissions</code>, <code>--write-back-cache</code>,
+<code>--max-read-ahead</code>, <code>--umask</code>, <code>--uid</code>,
+<code>--gid</code></li>
 </ul></li>
-<li>Add <code>--dir-cache-time</code> to control caching of directory entries</li>
+<li>Add <code>--dir-cache-time</code> to control caching of directory
+entries</li>
 <li>Implement seek for files opened for read (useful for video players)
 <ul>
 <li>with <code>-no-seek</code> flag to disable</li>
@@ -44355,7 +61848,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Local
 <ul>
-<li>Unix: implement <code>-x</code>/<code>--one-file-system</code> to stay on a single file system
+<li>Unix: implement <code>-x</code>/<code>--one-file-system</code> to
+stay on a single file system
 <ul>
 <li>thanks Durval Menezes and Luiz Carlos Rumbelsperger Viana</li>
 </ul></li>
@@ -44364,11 +61858,14 @@ $ tree /tmp/c
 </ul></li>
 <li>B2
 <ul>
-<li>Make sure each upload has at least one upload slot - fixes strange upload stats</li>
+<li>Make sure each upload has at least one upload slot - fixes strange
+upload stats</li>
 <li>Fix uploads when using crypt</li>
 <li>Fix download of large files (sha1 mismatch)</li>
-<li>Return error when we try to create a bucket which someone else owns</li>
-<li>Update B2 docs with Data usage, and Crypt section - thanks Tomasz Mazur</li>
+<li>Return error when we try to create a bucket which someone else
+owns</li>
+<li>Update B2 docs with Data usage, and Crypt section - thanks Tomasz
+Mazur</li>
 </ul></li>
 <li>S3
 <ul>
@@ -44380,8 +61877,10 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Make exponential backoff work exactly as per Google specification</li>
-<li>add <code>.epub</code>, <code>.odp</code> and <code>.tsv</code> as export formats.</li>
+<li>Make exponential backoff work exactly as per Google
+specification</li>
+<li>add <code>.epub</code>, <code>.odp</code> and <code>.tsv</code> as
+export formats.</li>
 </ul></li>
 <li>Swift
 <ul>
@@ -44404,10 +61903,13 @@ $ tree /tmp/c
 <li>works on Linux, FreeBSD and OS X (need testers for the last 2!)</li>
 </ul></li>
 <li>rclone cat - outputs remote file or files to the terminal</li>
-<li>rclone genautocomplete - command to make a bash completion script for rclone</li>
+<li>rclone genautocomplete - command to make a bash completion script
+for rclone</li>
 </ul></li>
-<li>Editing a remote using <code>rclone config</code> now goes through the wizard</li>
-<li>Compile with go 1.7 - this fixes rclone on macOS Sierra and on 386 processors</li>
+<li>Editing a remote using <code>rclone config</code> now goes through
+the wizard</li>
+<li>Compile with go 1.7 - this fixes rclone on macOS Sierra and on 386
+processors</li>
 <li>Use cobra for sub commands and docs generation</li>
 </ul></li>
 <li>drive
@@ -44427,7 +61929,8 @@ $ tree /tmp/c
 </ul></li>
 <li>onedrive
 <ul>
-<li>Fix URL escaping in file names - e.g. uploading files with <code>+</code> in them.</li>
+<li>Fix URL escaping in file names - e.g. uploading files with
+<code>+</code> in them.</li>
 </ul></li>
 <li>amazon cloud drive
 <ul>
@@ -44452,12 +61955,16 @@ $ tree /tmp/c
 <li>New Features
 <ul>
 <li>Reduce memory on sync by about 50%</li>
-<li>Implement --no-traverse flag to stop copy traversing the destination remote.
+<li>Implement --no-traverse flag to stop copy traversing the destination
+remote.
 <ul>
-<li>This can be used to reduce memory usage down to the smallest possible.</li>
-<li>Useful to copy a small number of files into a large destination folder.</li>
+<li>This can be used to reduce memory usage down to the smallest
+possible.</li>
+<li>Useful to copy a small number of files into a large destination
+folder.</li>
 </ul></li>
-<li>Implement cleanup command for emptying trash / removing old versions of files
+<li>Implement cleanup command for emptying trash / removing old versions
+of files
 <ul>
 <li>Currently B2 only</li>
 </ul></li>
@@ -44466,12 +61973,15 @@ $ tree /tmp/c
 <li>Now copied with --files-from</li>
 <li>Automatically sets --no-traverse when copying a single file</li>
 </ul></li>
-<li>Info on using installing with ansible - thanks Stefan Weichinger</li>
-<li>Implement --no-update-modtime flag to stop rclone fixing the remote modified times.</li>
+<li>Info on using installing with ansible - thanks Stefan
+Weichinger</li>
+<li>Implement --no-update-modtime flag to stop rclone fixing the remote
+modified times.</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
-<li>Fix move command - stop it running for overlapping Fses - this was causing data loss.</li>
+<li>Fix move command - stop it running for overlapping Fses - this was
+causing data loss.</li>
 </ul></li>
 <li>Local
 <ul>
@@ -44479,26 +61989,31 @@ $ tree /tmp/c
 </ul></li>
 <li>Amazon Drive
 <ul>
-<li>Rename Amazon Cloud Drive to Amazon Drive - no changes to config file needed.</li>
+<li>Rename Amazon Cloud Drive to Amazon Drive - no changes to config
+file needed.</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Add support for non-default project domain - thanks Antonio Messina.</li>
+<li>Add support for non-default project domain - thanks Antonio
+Messina.</li>
 </ul></li>
 <li>S3
 <ul>
 <li>Add instructions on how to use rclone with minio.</li>
 <li>Add ap-northeast-2 (Seoul) and ap-south-1 (Mumbai) regions.</li>
-<li>Skip setting the modified time for objects &gt; 5GB as it isn't possible.</li>
+<li>Skip setting the modified time for objects &gt; 5GB as it isn't
+possible.</li>
 </ul></li>
 <li>Backblaze B2
 <ul>
-<li>Add --b2-versions flag so old versions can be listed and retrieved.</li>
+<li>Add --b2-versions flag so old versions can be listed and
+retrieved.</li>
 <li>Treat 403 errors (e.g. cap exceeded) as fatal.</li>
 <li>Implement cleanup command for deleting old file versions.</li>
 <li>Make error handling compliant with B2 integrations notes.</li>
 <li>Fix handling of token expiry.</li>
-<li>Implement --b2-test-mode to set <code>X-Bz-Test-Mode</code> header.</li>
+<li>Implement --b2-test-mode to set <code>X-Bz-Test-Mode</code>
+header.</li>
 <li>Set cutoff for chunked upload to 200MB as per B2 guidelines.</li>
 <li>Make upload multi-threaded.</li>
 </ul></li>
@@ -44511,7 +62026,8 @@ $ tree /tmp/c
 <ul>
 <li>New Features
 <ul>
-<li>Directory listing code reworked for more features and better error reporting (thanks to Klaus Post for help). This enables
+<li>Directory listing code reworked for more features and better error
+reporting (thanks to Klaus Post for help). This enables
 <ul>
 <li>Directory include filtering for efficiency</li>
 <li>--max-depth parameter</li>
@@ -44523,8 +62039,10 @@ $ tree /tmp/c
 <li>Log -v output to stdout by default</li>
 <li>Display the transfer stats in more human-readable form</li>
 <li>Make 0 size files specifiable with <code>--max-size 0b</code></li>
-<li>Add <code>b</code> suffix so we can specify bytes in --bwlimit, --min-size, etc.</li>
-<li>Use "password:" instead of "password&gt;" prompt - thanks Klaus Post and Leigh Klotz</li>
+<li>Add <code>b</code> suffix so we can specify bytes in --bwlimit,
+--min-size, etc.</li>
+<li>Use "password:" instead of "password&gt;" prompt - thanks Klaus Post
+and Leigh Klotz</li>
 </ul></li>
 <li>Bug Fixes
 <ul>
@@ -44536,7 +62054,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Amazon Drive
 <ul>
-<li>Check a file exists before uploading to help with 408 Conflict errors</li>
+<li>Check a file exists before uploading to help with 408 Conflict
+errors</li>
 <li>Reauth on 401 errors - this has been causing a lot of problems</li>
 <li>Work around spurious 403 errors</li>
 <li>Restart directory listings on error</li>
@@ -44569,33 +62088,43 @@ $ tree /tmp/c
 <ul>
 <li>New Features
 <ul>
-<li>Implement <code>-I, --ignore-times</code> for unconditional upload</li>
+<li>Implement <code>-I, --ignore-times</code> for unconditional
+upload</li>
 <li>Improve <code>dedupe</code>command
 <ul>
 <li>Now removes identical copies without asking</li>
 <li>Now obeys <code>--dry-run</code></li>
 <li>Implement <code>--dedupe-mode</code> for non interactive running
 <ul>
-<li><code>--dedupe-mode interactive</code> - interactive the default.</li>
-<li><code>--dedupe-mode skip</code> - removes identical files then skips anything left.</li>
-<li><code>--dedupe-mode first</code> - removes identical files then keeps the first one.</li>
-<li><code>--dedupe-mode newest</code> - removes identical files then keeps the newest one.</li>
-<li><code>--dedupe-mode oldest</code> - removes identical files then keeps the oldest one.</li>
-<li><code>--dedupe-mode rename</code> - removes identical files then renames the rest to be different.</li>
+<li><code>--dedupe-mode interactive</code> - interactive the
+default.</li>
+<li><code>--dedupe-mode skip</code> - removes identical files then skips
+anything left.</li>
+<li><code>--dedupe-mode first</code> - removes identical files then
+keeps the first one.</li>
+<li><code>--dedupe-mode newest</code> - removes identical files then
+keeps the newest one.</li>
+<li><code>--dedupe-mode oldest</code> - removes identical files then
+keeps the oldest one.</li>
+<li><code>--dedupe-mode rename</code> - removes identical files then
+renames the rest to be different.</li>
 </ul></li>
 </ul></li>
 </ul></li>
 <li>Bug fixes
 <ul>
 <li>Make rclone check obey the <code>--size-only</code> flag.</li>
-<li>Use "application/octet-stream" if discovered mime type is invalid.</li>
+<li>Use "application/octet-stream" if discovered mime type is
+invalid.</li>
 <li>Fix missing "quit" option when there are no remotes.</li>
 </ul></li>
 <li>Google Drive
 <ul>
-<li>Increase default chunk size to 8 MB - increases upload speed of big files</li>
+<li>Increase default chunk size to 8 MB - increases upload speed of big
+files</li>
 <li>Speed up directory listings and make more reliable</li>
-<li>Add missing retries for Move and DirMove - increases reliability</li>
+<li>Add missing retries for Move and DirMove - increases
+reliability</li>
 <li>Preserve mime type on file update</li>
 </ul></li>
 <li>Backblaze B2
@@ -44624,23 +62153,31 @@ $ tree /tmp/c
 <li>New Features
 <ul>
 <li>Configuration file encryption - thanks Klaus Post</li>
-<li>Improve <code>rclone config</code> adding more help and making it easier to understand</li>
-<li>Implement <code>-u</code>/<code>--update</code> so creation times can be used on all remotes</li>
+<li>Improve <code>rclone config</code> adding more help and making it
+easier to understand</li>
+<li>Implement <code>-u</code>/<code>--update</code> so creation times
+can be used on all remotes</li>
 <li>Implement <code>--low-level-retries</code> flag</li>
-<li>Optionally disable gzip compression on downloads with <code>--no-gzip-encoding</code></li>
+<li>Optionally disable gzip compression on downloads with
+<code>--no-gzip-encoding</code></li>
 </ul></li>
 <li>Bug fixes
 <ul>
 <li>Don't make directories if <code>--dry-run</code> set</li>
 <li>Fix and document the <code>move</code> command</li>
-<li>Fix redirecting stderr on unix-like OSes when using <code>--log-file</code></li>
-<li>Fix <code>delete</code> command to wait until all finished - fixes missing deletes.</li>
+<li>Fix redirecting stderr on unix-like OSes when using
+<code>--log-file</code></li>
+<li>Fix <code>delete</code> command to wait until all finished - fixes
+missing deletes.</li>
 </ul></li>
 <li>Backblaze B2
 <ul>
-<li>Use one upload URL per go routine fixes <code>more than one upload using auth token</code></li>
-<li>Add pacing, retries and reauthentication - fixes token expiry problems</li>
-<li>Upload without using a temporary file from local (and remotes which support SHA1)</li>
+<li>Use one upload URL per go routine fixes
+<code>more than one upload using auth token</code></li>
+<li>Add pacing, retries and reauthentication - fixes token expiry
+problems</li>
+<li>Upload without using a temporary file from local (and remotes which
+support SHA1)</li>
 <li>Fix reading metadata for all files when it shouldn't have been</li>
 </ul></li>
 <li>Drive
@@ -44651,12 +62188,15 @@ $ tree /tmp/c
 <li>Swift
 <ul>
 <li>Fix uploading of chunked files with non ASCII characters</li>
-<li>Allow setting of <code>storage_url</code> in the config - thanks Xavier Lucas</li>
+<li>Allow setting of <code>storage_url</code> in the config - thanks
+Xavier Lucas</li>
 </ul></li>
 <li>S3
 <ul>
-<li>Allow IAM role and credentials from environment variables - thanks Brian Stengaard</li>
-<li>Allow low privilege users to use S3 (check if directory exists during Mkdir) - thanks Jakub Gedeon</li>
+<li>Allow IAM role and credentials from environment variables - thanks
+Brian Stengaard</li>
+<li>Allow low privilege users to use S3 (check if directory exists
+during Mkdir) - thanks Jakub Gedeon</li>
 </ul></li>
 <li>Amazon Drive
 <ul>
@@ -44667,22 +62207,31 @@ $ tree /tmp/c
 <ul>
 <li>New Features
 <ul>
-<li>Easier headless configuration with <code>rclone authorize</code></li>
-<li>Add support for multiple hash types - we now check SHA1 as well as MD5 hashes.</li>
-<li><code>delete</code> command which does obey the filters (unlike <code>purge</code>)</li>
-<li><code>dedupe</code> command to deduplicate a remote. Useful with Google Drive.</li>
-<li>Add <code>--ignore-existing</code> flag to skip all files that exist on destination.</li>
-<li>Add <code>--delete-before</code>, <code>--delete-during</code>, <code>--delete-after</code> flags.</li>
+<li>Easier headless configuration with
+<code>rclone authorize</code></li>
+<li>Add support for multiple hash types - we now check SHA1 as well as
+MD5 hashes.</li>
+<li><code>delete</code> command which does obey the filters (unlike
+<code>purge</code>)</li>
+<li><code>dedupe</code> command to deduplicate a remote. Useful with
+Google Drive.</li>
+<li>Add <code>--ignore-existing</code> flag to skip all files that exist
+on destination.</li>
+<li>Add <code>--delete-before</code>, <code>--delete-during</code>,
+<code>--delete-after</code> flags.</li>
 <li>Add <code>--memprofile</code> flag to debug memory use.</li>
 <li>Warn the user about files with same name but different case</li>
-<li>Make <code>--include</code> rules add their implicit exclude * at the end of the filter list</li>
+<li>Make <code>--include</code> rules add their implicit exclude * at
+the end of the filter list</li>
 <li>Deprecate compiling with go1.3</li>
 </ul></li>
 <li>Amazon Drive
 <ul>
 <li>Fix download of files &gt; 10 GB</li>
-<li>Fix directory traversal ("Next token is expired") for large directory listings</li>
-<li>Remove 409 conflict from error codes we will retry - stops very long pauses</li>
+<li>Fix directory traversal ("Next token is expired") for large
+directory listings</li>
+<li>Remove 409 conflict from error codes we will retry - stops very long
+pauses</li>
 </ul></li>
 <li>Backblaze B2
 <ul>
@@ -44690,7 +62239,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Drive
 <ul>
-<li>Add <code>--drive-auth-owner-only</code> to only consider files owned by the user - thanks Björn Harrtell</li>
+<li>Add <code>--drive-auth-owner-only</code> to only consider files
+owned by the user - thanks Björn Harrtell</li>
 <li>Export Google documents</li>
 </ul></li>
 <li>Dropbox
@@ -44716,7 +62266,8 @@ $ tree /tmp/c
 <ul>
 <li>Yandex storage backend - thank you Dmitry Burdeev ("dibu")</li>
 <li>Implement Backblaze B2 storage backend</li>
-<li>Add --min-age and --max-age flags - thank you Adriano Aurélio Meirelles</li>
+<li>Add --min-age and --max-age flags - thank you Adriano Aurélio
+Meirelles</li>
 <li>Make ls/lsl/md5sum/size/check obey includes and excludes</li>
 </ul></li>
 <li>Fixes
@@ -44735,7 +62286,8 @@ $ tree /tmp/c
 </ul></li>
 <li>S3
 <ul>
-<li>Fix corrupting Content-Type on mod time update (thanks Joseph Spurrier)</li>
+<li>Fix corrupting Content-Type on mod time update (thanks Joseph
+Spurrier)</li>
 </ul></li>
 </ul>
 <h2 id="v1.25---2015-11-14">v1.25 - 2015-11-14</h2>
@@ -44770,17 +62322,20 @@ $ tree /tmp/c
 <li>New features
 <ul>
 <li>Add support for Microsoft OneDrive</li>
-<li>Add <code>--no-check-certificate</code> option to disable server certificate verification</li>
+<li>Add <code>--no-check-certificate</code> option to disable server
+certificate verification</li>
 <li>Add async readahead buffer for faster transfer of big files</li>
 </ul></li>
 <li>Fixes
 <ul>
-<li>Allow spaces in remotes and check remote names for validity at creation time</li>
+<li>Allow spaces in remotes and check remote names for validity at
+creation time</li>
 <li>Allow '&amp;' and disallow ':' in Windows filenames.</li>
 </ul></li>
 <li>Swift
 <ul>
-<li>Ignore directory marker objects where appropriate - allows working with Hubic</li>
+<li>Ignore directory marker objects where appropriate - allows working
+with Hubic</li>
 <li>Don't delete the container if fs wasn't at root</li>
 </ul></li>
 <li>S3
@@ -44801,7 +62356,8 @@ $ tree /tmp/c
 <li>Fixes
 <ul>
 <li>Fix headless config for drive and gcs</li>
-<li>Tell the user they should try again if the webserver method failed</li>
+<li>Tell the user they should try again if the webserver method
+failed</li>
 <li>Improve output of <code>--dump-headers</code></li>
 </ul></li>
 <li>S3
@@ -44810,7 +62366,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Swift
 <ul>
-<li>Stop chunked operations logging "Failed to read info: Object Not Found"</li>
+<li>Stop chunked operations logging "Failed to read info: Object Not
+Found"</li>
 <li>Use Content-Length on uploads for extra reliability</li>
 </ul></li>
 </ul>
@@ -44831,7 +62388,8 @@ $ tree /tmp/c
 </ul></li>
 <li>Fixes
 <ul>
-<li>Fix allowing user to override credentials again in Drive, GCS and ACD</li>
+<li>Fix allowing user to override credentials again in Drive, GCS and
+ACD</li>
 </ul></li>
 <li>Amazon Drive
 <ul>
@@ -44851,7 +62409,8 @@ $ tree /tmp/c
 <ul>
 <li>Use "golang.org/x/oauth2" as oauth library of choice</li>
 <li>Improve oauth usability for smoother initial signup</li>
-<li>drive, googlecloudstorage: optionally use auto config for the oauth token</li>
+<li>drive, googlecloudstorage: optionally use auto config for the oauth
+token</li>
 </ul></li>
 <li>Implement --dump-headers and --dump-bodies debug flags</li>
 <li>Show multiple matched commands if abbreviation too short</li>
@@ -44859,7 +62418,8 @@ $ tree /tmp/c
 </ul></li>
 <li>local
 <ul>
-<li>Always use UNC paths internally on Windows - fixes a lot of bugs</li>
+<li>Always use UNC paths internally on Windows - fixes a lot of
+bugs</li>
 </ul></li>
 <li>dropbox
 <ul>
@@ -44891,8 +62451,10 @@ $ tree /tmp/c
 <ul>
 <li>drive
 <ul>
-<li>Add <code>--drive-use-trash</code> flag so rclone trashes instead of deletes</li>
-<li>Add "Forbidden to download" message for files with no downloadURL</li>
+<li>Add <code>--drive-use-trash</code> flag so rclone trashes instead of
+deletes</li>
+<li>Add "Forbidden to download" message for files with no
+downloadURL</li>
 </ul></li>
 <li>dropbox
 <ul>
@@ -44906,10 +62468,13 @@ $ tree /tmp/c
 <li>s3
 <ul>
 <li>use official AWS SDK from github.com/aws/aws-sdk-go</li>
-<li><strong>NB</strong> will most likely require you to delete and recreate remote</li>
+<li><strong>NB</strong> will most likely require you to delete and
+recreate remote</li>
 <li>enable multipart upload which enables files &gt; 5GB</li>
 <li>tested with Ceph / RadosGW / S3 emulation</li>
-<li>many thanks to Sam Liston and Brian Haymore at the <a href="https://www.chpc.utah.edu/">Utah Center for High Performance Computing</a> for a Ceph test account</li>
+<li>many thanks to Sam Liston and Brian Haymore at the <a
+href="https://www.chpc.utah.edu/">Utah Center for High Performance
+Computing</a> for a Ceph test account</li>
 </ul></li>
 <li>misc
 <ul>
@@ -44931,17 +62496,21 @@ $ tree /tmp/c
 </ul>
 <h2 id="v1.15---2015-06-06">v1.15 - 2015-06-06</h2>
 <ul>
-<li>Add --checksum flag to only discard transfers by MD5SUM - thanks Alex Couper</li>
-<li>Implement --size-only flag to sync on size not checksum &amp; modtime</li>
+<li>Add --checksum flag to only discard transfers by MD5SUM - thanks
+Alex Couper</li>
+<li>Implement --size-only flag to sync on size not checksum &amp;
+modtime</li>
 <li>Expand docs and remove duplicated information</li>
 <li>Document rclone's limitations with directories</li>
 <li>dropbox: update docs about case insensitivity</li>
 </ul>
 <h2 id="v1.14---2015-05-21">v1.14 - 2015-05-21</h2>
 <ul>
-<li>local: fix encoding of non utf-8 file names - fixes a duplicate file problem</li>
+<li>local: fix encoding of non utf-8 file names - fixes a duplicate file
+problem</li>
 <li>drive: docs about rate limiting</li>
-<li>google cloud storage: Fix compile after API change in "google.golang.org/api/storage/v1"</li>
+<li>google cloud storage: Fix compile after API change in
+"google.golang.org/api/storage/v1"</li>
 </ul>
 <h2 id="v1.13---2015-05-10">v1.13 - 2015-05-10</h2>
 <ul>
@@ -44952,8 +62521,10 @@ $ tree /tmp/c
 <h2 id="v1.12---2015-03-15">v1.12 - 2015-03-15</h2>
 <ul>
 <li>drive: Use chunked upload for files above a certain size</li>
-<li>drive: add --drive-chunk-size and --drive-upload-cutoff parameters</li>
-<li>drive: switch to insert from update when a failed copy deletes the upload</li>
+<li>drive: add --drive-chunk-size and --drive-upload-cutoff
+parameters</li>
+<li>drive: switch to insert from update when a failed copy deletes the
+upload</li>
 <li>core: Log duplicate files if they are detected</li>
 </ul>
 <h2 id="v1.11---2015-03-04">v1.11 - 2015-03-04</h2>
@@ -44963,7 +62534,8 @@ $ tree /tmp/c
 <li>In remote paths, change native directory separators to /</li>
 <li>Add synchronization to ls/lsl/lsd output to stop corruptions</li>
 <li>Ensure all stats/log messages to go stderr</li>
-<li>Add --log-file flag to log everything (including panics) to file</li>
+<li>Add --log-file flag to log everything (including panics) to
+file</li>
 <li>Make it possible to disable stats printing with --stats=0</li>
 <li>Implement --bwlimit to limit data transfer bandwidth</li>
 </ul>
@@ -44974,7 +62546,8 @@ $ tree /tmp/c
 </ul>
 <h2 id="v1.09---2015-02-07">v1.09 - 2015-02-07</h2>
 <ul>
-<li>windows: Stop drive letters (e.g. C:) getting mixed up with remotes (e.g. drive:)</li>
+<li>windows: Stop drive letters (e.g. C:) getting mixed up with remotes
+(e.g. drive:)</li>
 <li>local: Fix directory separators on Windows</li>
 <li>drive: fix rate limit exceeded errors</li>
 </ul>
@@ -45000,10 +62573,12 @@ $ tree /tmp/c
 <li>core: Fix race detected by go race detector</li>
 <li>core: Fixes after running errcheck</li>
 <li>drive: reset root directory on Rmdir and Purge</li>
-<li>fs: Document that Purger returns error on empty directory, test and fix</li>
+<li>fs: Document that Purger returns error on empty directory, test and
+fix</li>
 <li>google cloud storage: fix ListDir on subdirectory</li>
 <li>google cloud storage: re-read metadata in SetModTime</li>
-<li>s3: make reading metadata more reliable to work around eventual consistency problems</li>
+<li>s3: make reading metadata more reliable to work around eventual
+consistency problems</li>
 <li>s3: strip trailing / from ListDir()</li>
 <li>swift: return directories without / in ListDir</li>
 </ul>
@@ -45040,7 +62615,8 @@ $ tree /tmp/c
 </ul>
 <h2 id="v0.98---2014-05-30">v0.98 - 2014-05-30</h2>
 <ul>
-<li>s3: Treat missing Content-Length as 0 for some ceph installations</li>
+<li>s3: Treat missing Content-Length as 0 for some ceph
+installations</li>
 <li>rclonetest: add file with a space in</li>
 </ul>
 <h2 id="v0.97---2014-05-05">v0.97 - 2014-05-05</h2>
@@ -45088,112 +62664,257 @@ $ tree /tmp/c
 </ul>
 <h1 id="bugs-and-limitations">Bugs and Limitations</h1>
 <h2 id="limitations-42">Limitations</h2>
-<h3 id="directory-timestamps-arent-preserved-on-some-backends">Directory timestamps aren't preserved on some backends</h3>
-<p>As of <code>v1.66</code>, rclone supports syncing directory modtimes, if the backend supports it. Some backends do not support it -- see <a href="https://rclone.org/overview/">overview</a> for a complete list. Additionally, note that empty directories are not synced by default (this can be enabled with <code>--create-empty-src-dirs</code>.)</p>
-<h3 id="rclone-struggles-with-millions-of-files-in-a-directorybucket">Rclone struggles with millions of files in a directory/bucket</h3>
-<p>Currently rclone loads each directory/bucket entirely into memory before using it. Since each rclone object takes 0.5k-1k of memory this can take a very long time and use a large amount of memory.</p>
-<p>Millions of files in a directory tends to occur on bucket-based remotes (e.g. S3 buckets) since those remotes do not segregate subdirectories within the bucket.</p>
-<h3 id="bucket-based-remotes-and-folders">Bucket-based remotes and folders</h3>
-<p>Bucket-based remotes (e.g. S3/GCS/Swift/B2) do not have a concept of directories. Rclone therefore cannot create directories in them which means that empty directories on a bucket-based remote will tend to disappear.</p>
-<p>Some software creates empty keys ending in <code>/</code> as directory markers. Rclone doesn't do this as it potentially creates more objects and costs more. This ability may be added in the future (probably via a flag/option).</p>
+<h3 id="directory-timestamps-arent-preserved-on-some-backends">Directory
+timestamps aren't preserved on some backends</h3>
+<p>As of <code>v1.66</code>, rclone supports syncing directory modtimes,
+if the backend supports it. Some backends do not support it -- see <a
+href="https://rclone.org/overview/">overview</a> for a complete list.
+Additionally, note that empty directories are not synced by default
+(this can be enabled with <code>--create-empty-src-dirs</code>.)</p>
+<h3
+id="rclone-struggles-with-millions-of-files-in-a-directorybucket">Rclone
+struggles with millions of files in a directory/bucket</h3>
+<p>Currently rclone loads each directory/bucket entirely into memory
+before using it. Since each rclone object takes 0.5k-1k of memory this
+can take a very long time and use a large amount of memory.</p>
+<p>Millions of files in a directory tends to occur on bucket-based
+remotes (e.g. S3 buckets) since those remotes do not segregate
+subdirectories within the bucket.</p>
+<h3 id="bucket-based-remotes-and-folders">Bucket-based remotes and
+folders</h3>
+<p>Bucket-based remotes (e.g. S3/GCS/Swift/B2) do not have a concept of
+directories. Rclone therefore cannot create directories in them which
+means that empty directories on a bucket-based remote will tend to
+disappear.</p>
+<p>Some software creates empty keys ending in <code>/</code> as
+directory markers. Rclone doesn't do this as it potentially creates more
+objects and costs more. This ability may be added in the future
+(probably via a flag/option).</p>
 <h2 id="bugs-1">Bugs</h2>
 <p>Bugs are stored in rclone's GitHub project:</p>
 <ul>
-<li><a href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug">Reported bugs</a></li>
-<li><a href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Known+Problem%22">Known issues</a></li>
+<li><a
+href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+label%3Abug">Reported
+bugs</a></li>
+<li><a
+href="https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Known+Problem%22">Known
+issues</a></li>
 </ul>
 <h1 id="frequently-asked-questions">Frequently Asked Questions</h1>
-<h3 id="do-all-cloud-storage-systems-support-all-rclone-commands">Do all cloud storage systems support all rclone commands</h3>
-<p>Yes they do. All the rclone commands (e.g. <code>sync</code>, <code>copy</code>, etc.) will work on all the remote storage systems.</p>
-<h3 id="can-i-copy-the-config-from-one-machine-to-another">Can I copy the config from one machine to another</h3>
-<p>Sure! Rclone stores all of its config in a single file. If you want to find this file, run <code>rclone config file</code> which will tell you where it is.</p>
-<p>See the <a href="https://rclone.org/remote_setup/">remote setup docs</a> for more info.</p>
-<h3 id="how-do-i-configure-rclone-on-a-remote-headless-box-with-no-browser">How do I configure rclone on a remote / headless box with no browser?</h3>
-<p>This has now been documented in its own <a href="https://rclone.org/remote_setup/">remote setup page</a>.</p>
-<h3 id="can-rclone-sync-directly-from-drive-to-s3">Can rclone sync directly from drive to s3</h3>
-<p>Rclone can sync between two remote cloud storage systems just fine.</p>
-<p>Note that it effectively downloads the file and uploads it again, so the node running rclone would need to have lots of bandwidth.</p>
+<h3 id="do-all-cloud-storage-systems-support-all-rclone-commands">Do all
+cloud storage systems support all rclone commands</h3>
+<p>Yes they do. All the rclone commands (e.g. <code>sync</code>,
+<code>copy</code>, etc.) will work on all the remote storage
+systems.</p>
+<h3 id="can-i-copy-the-config-from-one-machine-to-another">Can I copy
+the config from one machine to another</h3>
+<p>Sure! Rclone stores all of its config in a single file. If you want
+to find this file, run <code>rclone config file</code> which will tell
+you where it is.</p>
+<p>See the <a href="https://rclone.org/remote_setup/">remote setup
+docs</a> for more info.</p>
+<h3
+id="how-do-i-configure-rclone-on-a-remote-headless-box-with-no-browser">How
+do I configure rclone on a remote / headless box with no browser?</h3>
+<p>This has now been documented in its own <a
+href="https://rclone.org/remote_setup/">remote setup page</a>.</p>
+<h3 id="can-rclone-sync-directly-from-drive-to-s3">Can rclone sync
+directly from drive to s3</h3>
+<p>Rclone can sync between two remote cloud storage systems just
+fine.</p>
+<p>Note that it effectively downloads the file and uploads it again, so
+the node running rclone would need to have lots of bandwidth.</p>
 <p>The syncs would be incremental (on a file by file basis).</p>
 <p>e.g.</p>
 <pre><code>rclone sync --interactive drive:Folder s3:bucket</code></pre>
-<h3 id="using-rclone-from-multiple-locations-at-the-same-time">Using rclone from multiple locations at the same time</h3>
-<p>You can use rclone from multiple places at the same time if you choose different subdirectory for the output, e.g.</p>
+<h3 id="using-rclone-from-multiple-locations-at-the-same-time">Using
+rclone from multiple locations at the same time</h3>
+<p>You can use rclone from multiple places at the same time if you
+choose different subdirectory for the output, e.g.</p>
 <pre><code>Server A&gt; rclone sync --interactive /tmp/whatever remote:ServerA
 Server B&gt; rclone sync --interactive /tmp/whatever remote:ServerB</code></pre>
-<p>If you sync to the same directory then you should use rclone copy otherwise the two instances of rclone may delete each other's files, e.g.</p>
+<p>If you sync to the same directory then you should use rclone copy
+otherwise the two instances of rclone may delete each other's files,
+e.g.</p>
 <pre><code>Server A&gt; rclone copy /tmp/whatever remote:Backup
 Server B&gt; rclone copy /tmp/whatever remote:Backup</code></pre>
-<p>The file names you upload from Server A and Server B should be different in this case, otherwise some file systems (e.g. Drive) may make duplicates.</p>
-<h3 id="why-doesnt-rclone-support-partial-transfers-binary-diffs-like-rsync">Why doesn't rclone support partial transfers / binary diffs like rsync?</h3>
-<p>Rclone stores each file you transfer as a native object on the remote cloud storage system. This means that you can see the files you upload as expected using alternative access methods (e.g. using the Google Drive web interface). There is a 1:1 mapping between files on your hard disk and objects created in the cloud storage system.</p>
-<p>Cloud storage systems (at least none I've come across yet) don't support partially uploading an object. You can't take an existing object, and change some bytes in the middle of it.</p>
-<p>It would be possible to make a sync system which stored binary diffs like rsync does, instead of whole objects, but that would break the 1:1 mapping of files on your hard disk to objects in the remote cloud storage system.</p>
-<p>All the cloud storage systems support partial downloads of content, so it would be possible to make partial downloads work. However to make this work efficiently this would require storing a significant amount of metadata, which breaks the desired 1:1 mapping of files to objects.</p>
-<h3 id="can-rclone-do-bi-directional-sync">Can rclone do bi-directional sync?</h3>
-<p>Yes, since rclone v1.58.0, <a href="https://rclone.org/bisync/">bidirectional cloud sync</a> is available.</p>
-<h3 id="can-i-use-rclone-with-an-http-proxy">Can I use rclone with an HTTP proxy?</h3>
-<p>Yes. rclone will follow the standard environment variables for proxies, similar to cURL and other programs.</p>
-<p>In general the variables are called <code>http_proxy</code> (for services reached over <code>http</code>) and <code>https_proxy</code> (for services reached over <code>https</code>). Most public services will be using <code>https</code>, but you may wish to set both.</p>
-<p>The content of the variable is <code>protocol://server:port</code>. The protocol value is the one used to talk to the proxy server, itself, and is commonly either <code>http</code> or <code>socks5</code>.</p>
-<p>Slightly annoyingly, there is no <em>standard</em> for the name; some applications may use <code>http_proxy</code> but another one <code>HTTP_PROXY</code>. The <code>Go</code> libraries used by <code>rclone</code> will try both variations, but you may wish to set all possibilities. So, on Linux, you may end up with code similar to</p>
+<p>The file names you upload from Server A and Server B should be
+different in this case, otherwise some file systems (e.g. Drive) may
+make duplicates.</p>
+<h3
+id="why-doesnt-rclone-support-partial-transfers-binary-diffs-like-rsync">Why
+doesn't rclone support partial transfers / binary diffs like rsync?</h3>
+<p>Rclone stores each file you transfer as a native object on the remote
+cloud storage system. This means that you can see the files you upload
+as expected using alternative access methods (e.g. using the Google
+Drive web interface). There is a 1:1 mapping between files on your hard
+disk and objects created in the cloud storage system.</p>
+<p>Cloud storage systems (at least none I've come across yet) don't
+support partially uploading an object. You can't take an existing
+object, and change some bytes in the middle of it.</p>
+<p>It would be possible to make a sync system which stored binary diffs
+like rsync does, instead of whole objects, but that would break the 1:1
+mapping of files on your hard disk to objects in the remote cloud
+storage system.</p>
+<p>All the cloud storage systems support partial downloads of content,
+so it would be possible to make partial downloads work. However to make
+this work efficiently this would require storing a significant amount of
+metadata, which breaks the desired 1:1 mapping of files to objects.</p>
+<h3 id="can-rclone-do-bi-directional-sync">Can rclone do bi-directional
+sync?</h3>
+<p>Yes, since rclone v1.58.0, <a
+href="https://rclone.org/bisync/">bidirectional cloud sync</a> is
+available.</p>
+<h3 id="can-i-use-rclone-with-an-http-proxy">Can I use rclone with an
+HTTP proxy?</h3>
+<p>Yes. rclone will follow the standard environment variables for
+proxies, similar to cURL and other programs.</p>
+<p>In general the variables are called <code>http_proxy</code> (for
+services reached over <code>http</code>) and <code>https_proxy</code>
+(for services reached over <code>https</code>). Most public services
+will be using <code>https</code>, but you may wish to set both.</p>
+<p>The content of the variable is <code>protocol://server:port</code>.
+The protocol value is the one used to talk to the proxy server, itself,
+and is commonly either <code>http</code> or <code>socks5</code>.</p>
+<p>Slightly annoyingly, there is no <em>standard</em> for the name; some
+applications may use <code>http_proxy</code> but another one
+<code>HTTP_PROXY</code>. The <code>Go</code> libraries used by
+<code>rclone</code> will try both variations, but you may wish to set
+all possibilities. So, on Linux, you may end up with code similar to</p>
 <pre><code>export http_proxy=http://proxyserver:12345
 export https_proxy=$http_proxy
 export HTTP_PROXY=$http_proxy
 export HTTPS_PROXY=$http_proxy</code></pre>
-<p>Note: If the proxy server requires a username and password, then use</p>
+<p>Note: If the proxy server requires a username and password, then
+use</p>
 <pre><code>export http_proxy=http://username:password@proxyserver:12345
 export https_proxy=$http_proxy
 export HTTP_PROXY=$http_proxy
 export HTTPS_PROXY=$http_proxy</code></pre>
-<p>The <code>NO_PROXY</code> allows you to disable the proxy for specific hosts. Hosts must be comma separated, and can contain domains or parts. For instance "foo.com" also matches "bar.foo.com".</p>
+<p>The <code>NO_PROXY</code> allows you to disable the proxy for
+specific hosts. Hosts must be comma separated, and can contain domains
+or parts. For instance "foo.com" also matches "bar.foo.com".</p>
 <p>e.g.</p>
 <pre><code>export no_proxy=localhost,127.0.0.0/8,my.host.name
 export NO_PROXY=$no_proxy</code></pre>
-<p>Note that the FTP backend does not support <code>ftp_proxy</code> yet.</p>
-<h3 id="rclone-gives-x509-failed-to-load-system-roots-and-no-roots-provided-error">Rclone gives x509: failed to load system roots and no roots provided error</h3>
-<p>This means that <code>rclone</code> can't find the SSL root certificates. Likely you are running <code>rclone</code> on a NAS with a cut-down Linux OS, or possibly on Solaris.</p>
-<p>Rclone (via the Go runtime) tries to load the root certificates from these places on Linux.</p>
+<p>Note that the FTP backend does not support <code>ftp_proxy</code>
+yet.</p>
+<h3
+id="rclone-gives-x509-failed-to-load-system-roots-and-no-roots-provided-error">Rclone
+gives x509: failed to load system roots and no roots provided error</h3>
+<p>This means that <code>rclone</code> can't find the SSL root
+certificates. Likely you are running <code>rclone</code> on a NAS with a
+cut-down Linux OS, or possibly on Solaris.</p>
+<p>Rclone (via the Go runtime) tries to load the root certificates from
+these places on Linux.</p>
 <pre><code>&quot;/etc/ssl/certs/ca-certificates.crt&quot;, // Debian/Ubuntu/Gentoo etc.
 &quot;/etc/pki/tls/certs/ca-bundle.crt&quot;,   // Fedora/RHEL
 &quot;/etc/ssl/ca-bundle.pem&quot;,             // OpenSUSE
 &quot;/etc/pki/tls/cacert.pem&quot;,            // OpenELEC</code></pre>
-<p>So doing something like this should fix the problem. It also sets the time which is important for SSL to work properly.</p>
+<p>So doing something like this should fix the problem. It also sets the
+time which is important for SSL to work properly.</p>
 <pre><code>mkdir -p /etc/ssl/certs/
 curl -o /etc/ssl/certs/ca-certificates.crt https://raw.githubusercontent.com/bagder/ca-bundle/master/ca-bundle.crt
 ntpclient -s -h pool.ntp.org</code></pre>
-<p>The two environment variables <code>SSL_CERT_FILE</code> and <code>SSL_CERT_DIR</code>, mentioned in the <a href="https://godoc.org/crypto/x509">x509 package</a>, provide an additional way to provide the SSL root certificates.</p>
-<p>Note that you may need to add the <code>--insecure</code> option to the <code>curl</code> command line if it doesn't work without.</p>
+<p>The two environment variables <code>SSL_CERT_FILE</code> and
+<code>SSL_CERT_DIR</code>, mentioned in the <a
+href="https://godoc.org/crypto/x509">x509 package</a>, provide an
+additional way to provide the SSL root certificates.</p>
+<p>Note that you may need to add the <code>--insecure</code> option to
+the <code>curl</code> command line if it doesn't work without.</p>
 <pre><code>curl --insecure -o /etc/ssl/certs/ca-certificates.crt https://raw.githubusercontent.com/bagder/ca-bundle/master/ca-bundle.crt</code></pre>
-<h3 id="rclone-gives-failed-to-load-config-file-function-not-implemented-error">Rclone gives Failed to load config file: function not implemented error</h3>
-<p>Likely this means that you are running rclone on Linux version not supported by the go runtime, ie earlier than version 2.6.23.</p>
-<p>See the <a href="https://golang.org/doc/install">system requirements section in the go install docs</a> for full details.</p>
-<h3 id="all-my-uploaded-docxxlsxpptx-files-appear-as-archivezip">All my uploaded docx/xlsx/pptx files appear as archive/zip</h3>
-<p>This is caused by uploading these files from a Windows computer which hasn't got the Microsoft Office suite installed. The easiest way to fix is to install the Word viewer and the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 and later versions' file formats</p>
-<h3 id="tcp-lookup-some.domain.com-no-such-host">tcp lookup some.domain.com no such host</h3>
-<p>This happens when rclone cannot resolve a domain. Please check that your DNS setup is generally working, e.g.</p>
+<h3
+id="rclone-gives-failed-to-load-config-file-function-not-implemented-error">Rclone
+gives Failed to load config file: function not implemented error</h3>
+<p>Likely this means that you are running rclone on Linux version not
+supported by the go runtime, ie earlier than version 2.6.23.</p>
+<p>See the <a href="https://golang.org/doc/install">system requirements
+section in the go install docs</a> for full details.</p>
+<h3 id="all-my-uploaded-docxxlsxpptx-files-appear-as-archivezip">All my
+uploaded docx/xlsx/pptx files appear as archive/zip</h3>
+<p>This is caused by uploading these files from a Windows computer which
+hasn't got the Microsoft Office suite installed. The easiest way to fix
+is to install the Word viewer and the Microsoft Office Compatibility
+Pack for Word, Excel, and PowerPoint 2007 and later versions' file
+formats</p>
+<h3 id="tcp-lookup-some.domain.com-no-such-host">tcp lookup
+some.domain.com no such host</h3>
+<p>This happens when rclone cannot resolve a domain. Please check that
+your DNS setup is generally working, e.g.</p>
 <pre><code># both should print a long list of possible IP addresses
 dig www.googleapis.com          # resolve using your default DNS
 dig www.googleapis.com @8.8.8.8 # resolve with Google&#39;s DNS server</code></pre>
-<p>If you are using <code>systemd-resolved</code> (default on Arch Linux), ensure it is at version 233 or higher. Previous releases contain a bug which causes not all domains to be resolved properly.</p>
-<p>The Go resolver decision can be influenced with the <code>GODEBUG=netdns=...</code> environment variable. This also allows to resolve certain issues with DNS resolution. On Windows or MacOS systems, try forcing use of the internal Go resolver by setting <code>GODEBUG=netdns=go</code> at runtime. On other systems (Linux, *BSD, etc) try forcing use of the system name resolver by setting <code>GODEBUG=netdns=cgo</code> (and recompile rclone from source with CGO enabled if necessary). See the <a href="https://golang.org/pkg/net/#hdr-Name_Resolution">name resolution section in the go docs</a>.</p>
-<h3 id="failed-to-start-auth-webserver-on-windows">Failed to start auth webserver on Windows</h3>
+<p>If you are using <code>systemd-resolved</code> (default on Arch
+Linux), ensure it is at version 233 or higher. Previous releases contain
+a bug which causes not all domains to be resolved properly.</p>
+<p>The Go resolver decision can be influenced with the
+<code>GODEBUG=netdns=...</code> environment variable. This also allows
+to resolve certain issues with DNS resolution. On Windows or MacOS
+systems, try forcing use of the internal Go resolver by setting
+<code>GODEBUG=netdns=go</code> at runtime. On other systems (Linux,
+*BSD, etc) try forcing use of the system name resolver by setting
+<code>GODEBUG=netdns=cgo</code> (and recompile rclone from source with
+CGO enabled if necessary). See the <a
+href="https://golang.org/pkg/net/#hdr-Name_Resolution">name resolution
+section in the go docs</a>.</p>
+<h3 id="failed-to-start-auth-webserver-on-windows">Failed to start auth
+webserver on Windows</h3>
 <pre><code>Error: config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
 ...
 yyyy/mm/dd hh:mm:ss Fatal error: config failed to refresh token: failed to start auth webserver: listen tcp 127.0.0.1:53682: bind: An attempt was made to access a socket in a way forbidden by its access permissions.</code></pre>
-<p>This is sometimes caused by the Host Network Service causing issues with opening the port on the host.</p>
-<p>A simple solution may be restarting the Host Network Service with eg. Powershell</p>
+<p>This is sometimes caused by the Host Network Service causing issues
+with opening the port on the host.</p>
+<p>A simple solution may be restarting the Host Network Service with eg.
+Powershell</p>
 <pre><code>Restart-Service hns</code></pre>
-<h3 id="the-total-size-reported-in-the-stats-for-a-sync-is-wrong-and-keeps-changing">The total size reported in the stats for a sync is wrong and keeps changing</h3>
-<p>It is likely you have more than 10,000 files that need to be synced. By default, rclone only gets 10,000 files ahead in a sync so as not to use up too much memory. You can change this default with the <a href="https://rclone.org/docs/#max-backlog-n">--max-backlog</a> flag.</p>
-<h3 id="rclone-is-using-too-much-memory-or-appears-to-have-a-memory-leak">Rclone is using too much memory or appears to have a memory leak</h3>
-<p>Rclone is written in Go which uses a garbage collector. The default settings for the garbage collector mean that it runs when the heap size has doubled.</p>
-<p>However it is possible to tune the garbage collector to use less memory by <a href="https://dave.cheney.net/tag/gogc">setting GOGC</a> to a lower value, say <code>export GOGC=20</code>. This will make the garbage collector work harder, reducing memory size at the expense of CPU usage.</p>
-<p>The most common cause of rclone using lots of memory is a single directory with millions of files in. Rclone has to load this entirely into memory as rclone objects. Each rclone object takes 0.5k-1k of memory. There is <a href="https://github.com/rclone/rclone/wiki/Big-syncs-with-millions-of-files">a workaround for this</a> which involves a bit of scripting.</p>
-<h3 id="rclone-changes-fullwidth-unicode-punctuation-marks-in-file-names">Rclone changes fullwidth Unicode punctuation marks in file names</h3>
-<p>For example: On a Windows system, you have a file with name <code>Test：1.jpg</code>, where <code>：</code> is the Unicode fullwidth colon symbol. When using rclone to copy this to your Google Drive, you will notice that the file gets renamed to <code>Test:1.jpg</code>, where <code>:</code> is the regular (halfwidth) colon.</p>
-<p>The reason for such renames is the way rclone handles different <a href="https://rclone.org/overview/#restricted-filenames">restricted filenames</a> on different cloud storage systems. It tries to avoid ambiguous file names as much and allow moving files between many cloud storage systems transparently, by replacing invalid characters with similar looking Unicode characters when transferring to one storage system, and replacing back again when transferring to a different storage system where the original characters are supported. When the same Unicode characters are intentionally used in file names, this replacement strategy leads to unwanted renames. Read more <a href="https://rclone.org/overview/#restricted-filenames-caveats">here</a>.</p>
+<h3
+id="the-total-size-reported-in-the-stats-for-a-sync-is-wrong-and-keeps-changing">The
+total size reported in the stats for a sync is wrong and keeps
+changing</h3>
+<p>It is likely you have more than 10,000 files that need to be synced.
+By default, rclone only gets 10,000 files ahead in a sync so as not to
+use up too much memory. You can change this default with the <a
+href="https://rclone.org/docs/#max-backlog-n">--max-backlog</a>
+flag.</p>
+<h3
+id="rclone-is-using-too-much-memory-or-appears-to-have-a-memory-leak">Rclone
+is using too much memory or appears to have a memory leak</h3>
+<p>Rclone is written in Go which uses a garbage collector. The default
+settings for the garbage collector mean that it runs when the heap size
+has doubled.</p>
+<p>However it is possible to tune the garbage collector to use less
+memory by <a href="https://dave.cheney.net/tag/gogc">setting GOGC</a> to
+a lower value, say <code>export GOGC=20</code>. This will make the
+garbage collector work harder, reducing memory size at the expense of
+CPU usage.</p>
+<p>The most common cause of rclone using lots of memory is a single
+directory with millions of files in. Rclone has to load this entirely
+into memory as rclone objects. Each rclone object takes 0.5k-1k of
+memory. There is <a
+href="https://github.com/rclone/rclone/wiki/Big-syncs-with-millions-of-files">a
+workaround for this</a> which involves a bit of scripting.</p>
+<h3
+id="rclone-changes-fullwidth-unicode-punctuation-marks-in-file-names">Rclone
+changes fullwidth Unicode punctuation marks in file names</h3>
+<p>For example: On a Windows system, you have a file with name
+<code>Test：1.jpg</code>, where <code>：</code> is the Unicode fullwidth
+colon symbol. When using rclone to copy this to your Google Drive, you
+will notice that the file gets renamed to <code>Test:1.jpg</code>, where
+<code>:</code> is the regular (halfwidth) colon.</p>
+<p>The reason for such renames is the way rclone handles different <a
+href="https://rclone.org/overview/#restricted-filenames">restricted
+filenames</a> on different cloud storage systems. It tries to avoid
+ambiguous file names as much and allow moving files between many cloud
+storage systems transparently, by replacing invalid characters with
+similar looking Unicode characters when transferring to one storage
+system, and replacing back again when transferring to a different
+storage system where the original characters are supported. When the
+same Unicode characters are intentionally used in file names, this
+replacement strategy leads to unwanted renames. Read more <a
+href="https://rclone.org/overview/#restricted-filenames-caveats">here</a>.</p>
 <h1 id="license">License</h1>
-<p>This is free software under the terms of the MIT license (check the COPYING file included with the source code).</p>
+<p>This is free software under the terms of the MIT license (check the
+COPYING file included with the source code).</p>
 <pre><code>Copyright (C) 2019 by Nick Craig-Wood https://www.craig-wood.com/nick/
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
@@ -45216,883 +62937,1878 @@ THE SOFTWARE.</code></pre>
 <h1 id="authors-and-contributors">Authors and contributors</h1>
 <h2 id="authors">Authors</h2>
 <ul>
-<li>Nick Craig-Wood <a href="mailto:nick@craig-wood.com" class="email">nick@craig-wood.com</a></li>
+<li>Nick Craig-Wood <a href="mailto:nick@craig-wood.com"
+class="email">nick@craig-wood.com</a></li>
 </ul>
 <h2 id="contributors">Contributors</h2>
-<p>{{&lt; rem <code>email addresses removed from here need to be added to bin/.ignore-emails to make sure update-authors.py doesn't immediately put them back in again.</code> &gt;}}</p>
+<p>{{&lt; rem
+<code>email addresses removed from here need to be added to bin/.ignore-emails to make sure update-authors.py doesn't immediately put them back in again.</code>
+&gt;}}</p>
 <ul>
-<li>Alex Couper <a href="mailto:amcouper@gmail.com" class="email">amcouper@gmail.com</a></li>
-<li>Leonid Shalupov <a href="mailto:leonid@shalupov.com" class="email">leonid@shalupov.com</a> <a href="mailto:shalupov@diverse.org.ru" class="email">shalupov@diverse.org.ru</a></li>
-<li>Shimon Doodkin <a href="mailto:helpmepro1@gmail.com" class="email">helpmepro1@gmail.com</a></li>
-<li>Colin Nicholson <a href="mailto:colin@colinn.com" class="email">colin@colinn.com</a></li>
-<li>Klaus Post <a href="mailto:klauspost@gmail.com" class="email">klauspost@gmail.com</a></li>
-<li>Sergey Tolmachev <a href="mailto:tolsi.ru@gmail.com" class="email">tolsi.ru@gmail.com</a></li>
-<li>Adriano Aurélio Meirelles <a href="mailto:adriano@atinge.com" class="email">adriano@atinge.com</a></li>
-<li>C. Bess <a href="mailto:cbess@users.noreply.github.com" class="email">cbess@users.noreply.github.com</a></li>
-<li>Dmitry Burdeev <a href="mailto:dibu28@gmail.com" class="email">dibu28@gmail.com</a></li>
-<li>Joseph Spurrier <a href="mailto:github@josephspurrier.com" class="email">github@josephspurrier.com</a></li>
-<li>Björn Harrtell <a href="mailto:bjorn@wololo.org" class="email">bjorn@wololo.org</a></li>
-<li>Xavier Lucas <a href="mailto:xavier.lucas@corp.ovh.com" class="email">xavier.lucas@corp.ovh.com</a></li>
-<li>Werner Beroux <a href="mailto:werner@beroux.com" class="email">werner@beroux.com</a></li>
-<li>Brian Stengaard <a href="mailto:brian@stengaard.eu" class="email">brian@stengaard.eu</a></li>
-<li>Jakub Gedeon <a href="mailto:jgedeon@sofi.com" class="email">jgedeon@sofi.com</a></li>
-<li>Jim Tittsler <a href="mailto:jwt@onjapan.net" class="email">jwt@onjapan.net</a></li>
-<li>Michal Witkowski <a href="mailto:michal@improbable.io" class="email">michal@improbable.io</a></li>
-<li>Fabian Ruff <a href="mailto:fabian.ruff@sap.com" class="email">fabian.ruff@sap.com</a></li>
-<li>Leigh Klotz <a href="mailto:klotz@quixey.com" class="email">klotz@quixey.com</a></li>
-<li>Romain Lapray <a href="mailto:lapray.romain@gmail.com" class="email">lapray.romain@gmail.com</a></li>
-<li>Justin R. Wilson <a href="mailto:jrw972@gmail.com" class="email">jrw972@gmail.com</a></li>
-<li>Antonio Messina <a href="mailto:antonio.s.messina@gmail.com" class="email">antonio.s.messina@gmail.com</a></li>
-<li>Stefan G. Weichinger <a href="mailto:office@oops.co.at" class="email">office@oops.co.at</a></li>
-<li>Per Cederberg <a href="mailto:cederberg@gmail.com" class="email">cederberg@gmail.com</a></li>
-<li>Radek Šenfeld <a href="mailto:rush@logic.cz" class="email">rush@logic.cz</a></li>
-<li>Fredrik Fornwall <a href="mailto:fredrik@fornwall.net" class="email">fredrik@fornwall.net</a></li>
-<li>Asko Tamm <a href="mailto:asko@deekit.net" class="email">asko@deekit.net</a></li>
-<li>xor-zz <a href="mailto:xor@gstocco.com" class="email">xor@gstocco.com</a></li>
-<li>Tomasz Mazur <a href="mailto:tmazur90@gmail.com" class="email">tmazur90@gmail.com</a></li>
-<li>Marco Paganini <a href="mailto:paganini@paganini.net" class="email">paganini@paganini.net</a></li>
-<li>Felix Bünemann <a href="mailto:buenemann@louis.info" class="email">buenemann@louis.info</a></li>
-<li>Durval Menezes <a href="mailto:jmrclone@durval.com" class="email">jmrclone@durval.com</a></li>
-<li>Luiz Carlos Rumbelsperger Viana <a href="mailto:maxd13_luiz_carlos@hotmail.com" class="email">maxd13_luiz_carlos@hotmail.com</a></li>
-<li>Stefan Breunig <a href="mailto:stefan-github@yrden.de" class="email">stefan-github@yrden.de</a></li>
-<li>Alishan Ladhani <a href="mailto:ali-l@users.noreply.github.com" class="email">ali-l@users.noreply.github.com</a></li>
-<li>0xJAKE <a href="mailto:0xJAKE@users.noreply.github.com" class="email">0xJAKE@users.noreply.github.com</a></li>
-<li>Thibault Molleman <a href="mailto:thibaultmol@users.noreply.github.com" class="email">thibaultmol@users.noreply.github.com</a></li>
-<li>Scott McGillivray <a href="mailto:scott.mcgillivray@gmail.com" class="email">scott.mcgillivray@gmail.com</a></li>
-<li>Bjørn Erik Pedersen <a href="mailto:bjorn.erik.pedersen@gmail.com" class="email">bjorn.erik.pedersen@gmail.com</a></li>
-<li>Lukas Loesche <a href="mailto:lukas@mesosphere.io" class="email">lukas@mesosphere.io</a></li>
-<li>emyarod <a href="mailto:emyarod@users.noreply.github.com" class="email">emyarod@users.noreply.github.com</a></li>
-<li>T.C. Ferguson <a href="mailto:tcf909@gmail.com" class="email">tcf909@gmail.com</a></li>
-<li>Brandur <a href="mailto:brandur@mutelight.org" class="email">brandur@mutelight.org</a></li>
-<li>Dario Giovannetti <a href="mailto:dev@dariogiovannetti.net" class="email">dev@dariogiovannetti.net</a></li>
-<li>Károly Oláh <a href="mailto:okaresz@aol.com" class="email">okaresz@aol.com</a></li>
-<li>Jon Yergatian <a href="mailto:jon@macfanatic.ca" class="email">jon@macfanatic.ca</a></li>
-<li>Jack Schmidt <a href="mailto:github@mowsey.org" class="email">github@mowsey.org</a></li>
-<li>Dedsec1 <a href="mailto:Dedsec1@users.noreply.github.com" class="email">Dedsec1@users.noreply.github.com</a></li>
-<li>Hisham Zarka <a href="mailto:hzarka@gmail.com" class="email">hzarka@gmail.com</a></li>
-<li>Jérôme Vizcaino <a href="mailto:jerome.vizcaino@gmail.com" class="email">jerome.vizcaino@gmail.com</a></li>
-<li>Mike Tesch <a href="mailto:mjt6129@rit.edu" class="email">mjt6129@rit.edu</a></li>
-<li>Marvin Watson <a href="mailto:marvwatson@users.noreply.github.com" class="email">marvwatson@users.noreply.github.com</a></li>
-<li>Danny Tsai <a href="mailto:danny8376@gmail.com" class="email">danny8376@gmail.com</a></li>
-<li>Yoni Jah <a href="mailto:yonjah+git@gmail.com" class="email">yonjah+git@gmail.com</a> <a href="mailto:yonjah+github@gmail.com" class="email">yonjah+github@gmail.com</a></li>
-<li>Stephen Harris <a href="mailto:github@spuddy.org" class="email">github@spuddy.org</a> <a href="mailto:sweharris@users.noreply.github.com" class="email">sweharris@users.noreply.github.com</a></li>
-<li>Ihor Dvoretskyi <a href="mailto:ihor.dvoretskyi@gmail.com" class="email">ihor.dvoretskyi@gmail.com</a></li>
-<li>Jon Craton <a href="mailto:jncraton@gmail.com" class="email">jncraton@gmail.com</a></li>
-<li>Hraban Luyat <a href="mailto:hraban@0brg.net" class="email">hraban@0brg.net</a></li>
-<li>Michael Ledin <a href="mailto:mledin89@gmail.com" class="email">mledin89@gmail.com</a></li>
-<li>Martin Kristensen <a href="mailto:me@azgul.com" class="email">me@azgul.com</a></li>
-<li>Too Much IO <a href="mailto:toomuchio@users.noreply.github.com" class="email">toomuchio@users.noreply.github.com</a></li>
-<li>Anisse Astier <a href="mailto:anisse@astier.eu" class="email">anisse@astier.eu</a></li>
-<li>Zahiar Ahmed <a href="mailto:zahiar@live.com" class="email">zahiar@live.com</a></li>
-<li>Igor Kharin <a href="mailto:igorkharin@gmail.com" class="email">igorkharin@gmail.com</a></li>
-<li>Bill Zissimopoulos <a href="mailto:billziss@navimatics.com" class="email">billziss@navimatics.com</a></li>
-<li>Bob Potter <a href="mailto:bobby.potter@gmail.com" class="email">bobby.potter@gmail.com</a></li>
-<li>Steven Lu <a href="mailto:tacticalazn@gmail.com" class="email">tacticalazn@gmail.com</a></li>
-<li>Sjur Fredriksen <a href="mailto:sjurtf@ifi.uio.no" class="email">sjurtf@ifi.uio.no</a></li>
-<li>Ruwbin <a href="mailto:hubus12345@gmail.com" class="email">hubus12345@gmail.com</a></li>
-<li>Fabian Möller <a href="mailto:fabianm88@gmail.com" class="email">fabianm88@gmail.com</a> <a href="mailto:f.moeller@nynex.de" class="email">f.moeller@nynex.de</a></li>
-<li>Edward Q. Bridges <a href="mailto:github@eqbridges.com" class="email">github@eqbridges.com</a></li>
-<li>Vasiliy Tolstov <a href="mailto:v.tolstov@selfip.ru" class="email">v.tolstov@selfip.ru</a></li>
-<li>Harshavardhana <a href="mailto:harsha@minio.io" class="email">harsha@minio.io</a></li>
-<li>sainaen <a href="mailto:sainaen@gmail.com" class="email">sainaen@gmail.com</a></li>
-<li>gdm85 <a href="mailto:gdm85@users.noreply.github.com" class="email">gdm85@users.noreply.github.com</a></li>
-<li>Yaroslav Halchenko <a href="mailto:debian@onerussian.com" class="email">debian@onerussian.com</a></li>
-<li>John Papandriopoulos <a href="mailto:jpap@users.noreply.github.com" class="email">jpap@users.noreply.github.com</a></li>
-<li>Zhiming Wang <a href="mailto:zmwangx@gmail.com" class="email">zmwangx@gmail.com</a></li>
-<li>Andy Pilate <a href="mailto:cubox@cubox.me" class="email">cubox@cubox.me</a></li>
-<li>Oliver Heyme <a href="mailto:olihey@googlemail.com" class="email">olihey@googlemail.com</a> <a href="mailto:olihey@users.noreply.github.com" class="email">olihey@users.noreply.github.com</a> <a href="mailto:de8olihe@lego.com" class="email">de8olihe@lego.com</a></li>
-<li>wuyu <a href="mailto:wuyu@yunify.com" class="email">wuyu@yunify.com</a></li>
-<li>Andrei Dragomir <a href="mailto:adragomi@adobe.com" class="email">adragomi@adobe.com</a></li>
-<li>Christian Brüggemann <a href="mailto:mail@cbruegg.com" class="email">mail@cbruegg.com</a></li>
-<li>Alex McGrath Kraak <a href="mailto:amkdude@gmail.com" class="email">amkdude@gmail.com</a></li>
-<li>bpicode <a href="mailto:bjoern.pirnay@googlemail.com" class="email">bjoern.pirnay@googlemail.com</a></li>
-<li>Daniel Jagszent <a href="mailto:daniel@jagszent.de" class="email">daniel@jagszent.de</a></li>
-<li>Josiah White <a href="mailto:thegenius2009@gmail.com" class="email">thegenius2009@gmail.com</a></li>
-<li>Ishuah Kariuki <a href="mailto:kariuki@ishuah.com" class="email">kariuki@ishuah.com</a> <a href="mailto:ishuah91@gmail.com" class="email">ishuah91@gmail.com</a></li>
-<li>Jan Varho <a href="mailto:jan@varho.org" class="email">jan@varho.org</a></li>
-<li>Girish Ramakrishnan <a href="mailto:girish@cloudron.io" class="email">girish@cloudron.io</a></li>
-<li>LingMan <a href="mailto:LingMan@users.noreply.github.com" class="email">LingMan@users.noreply.github.com</a></li>
-<li>Jacob McNamee <a href="mailto:jacobmcnamee@gmail.com" class="email">jacobmcnamee@gmail.com</a></li>
-<li>jersou <a href="mailto:jertux@gmail.com" class="email">jertux@gmail.com</a></li>
-<li>thierry <a href="mailto:thierry@substantiel.fr" class="email">thierry@substantiel.fr</a></li>
-<li>Simon Leinen <a href="mailto:simon.leinen@gmail.com" class="email">simon.leinen@gmail.com</a> <a href="mailto:ubuntu@s3-test.novalocal" class="email">ubuntu@s3-test.novalocal</a></li>
-<li>Dan Dascalescu <a href="mailto:ddascalescu+github@gmail.com" class="email">ddascalescu+github@gmail.com</a></li>
-<li>Jason Rose <a href="mailto:jason@jro.io" class="email">jason@jro.io</a></li>
-<li>Andrew Starr-Bochicchio <a href="mailto:a.starr.b@gmail.com" class="email">a.starr.b@gmail.com</a></li>
-<li>John Leach <a href="mailto:john@johnleach.co.uk" class="email">john@johnleach.co.uk</a></li>
-<li>Corban Raun <a href="mailto:craun@instructure.com" class="email">craun@instructure.com</a></li>
-<li>Pierre Carlson <a href="mailto:mpcarl@us.ibm.com" class="email">mpcarl@us.ibm.com</a></li>
-<li>Ernest Borowski <a href="mailto:er.borowski@gmail.com" class="email">er.borowski@gmail.com</a></li>
-<li>Remus Bunduc <a href="mailto:remus.bunduc@gmail.com" class="email">remus.bunduc@gmail.com</a></li>
-<li>Iakov Davydov <a href="mailto:iakov.davydov@unil.ch" class="email">iakov.davydov@unil.ch</a> <a href="mailto:dav05.gith@myths.ru" class="email">dav05.gith@myths.ru</a></li>
-<li>Jakub Tasiemski <a href="mailto:tasiemski@gmail.com" class="email">tasiemski@gmail.com</a></li>
-<li>David Minor <a href="mailto:dminor@saymedia.com" class="email">dminor@saymedia.com</a></li>
-<li>Tim Cooijmans <a href="mailto:cooijmans.tim@gmail.com" class="email">cooijmans.tim@gmail.com</a></li>
-<li>Laurence <a href="mailto:liuxy6@gmail.com" class="email">liuxy6@gmail.com</a></li>
-<li>Giovanni Pizzi <a href="mailto:gio.piz@gmail.com" class="email">gio.piz@gmail.com</a></li>
-<li>Filip Bartodziej <a href="mailto:filipbartodziej@gmail.com" class="email">filipbartodziej@gmail.com</a></li>
-<li>Jon Fautley <a href="mailto:jon@dead.li" class="email">jon@dead.li</a></li>
-<li>lewapm <a href="mailto:32110057+lewapm@users.noreply.github.com" class="email">32110057+lewapm@users.noreply.github.com</a></li>
-<li>Yassine Imounachen <a href="mailto:yassine256@gmail.com" class="email">yassine256@gmail.com</a></li>
-<li>Chris Redekop <a href="mailto:chris-redekop@users.noreply.github.com" class="email">chris-redekop@users.noreply.github.com</a> <a href="mailto:chris.redekop@gmail.com" class="email">chris.redekop@gmail.com</a></li>
-<li>Jon Fautley <a href="mailto:jon@adenoid.appstal.co.uk" class="email">jon@adenoid.appstal.co.uk</a></li>
-<li>Will Gunn <a href="mailto:WillGunn@users.noreply.github.com" class="email">WillGunn@users.noreply.github.com</a></li>
-<li>Lucas Bremgartner <a href="mailto:lucas@bremis.ch" class="email">lucas@bremis.ch</a></li>
-<li>Jody Frankowski <a href="mailto:jody.frankowski@gmail.com" class="email">jody.frankowski@gmail.com</a></li>
-<li>Andreas Roussos <a href="mailto:arouss1980@gmail.com" class="email">arouss1980@gmail.com</a></li>
-<li>nbuchanan <a href="mailto:nbuchanan@utah.gov" class="email">nbuchanan@utah.gov</a></li>
-<li>Durval Menezes <a href="mailto:rclone@durval.com" class="email">rclone@durval.com</a></li>
-<li>Victor <a href="mailto:vb-github@viblo.se" class="email">vb-github@viblo.se</a></li>
-<li>Mateusz <a href="mailto:pabian.mateusz@gmail.com" class="email">pabian.mateusz@gmail.com</a></li>
-<li>Daniel Loader <a href="mailto:spicypixel@gmail.com" class="email">spicypixel@gmail.com</a></li>
-<li>David0rk <a href="mailto:davidork@gmail.com" class="email">davidork@gmail.com</a></li>
-<li>Alexander Neumann <a href="mailto:alexander@bumpern.de" class="email">alexander@bumpern.de</a></li>
-<li>Giri Badanahatti <a href="mailto:gbadanahatti@us.ibm.com@Giris-MacBook-Pro.local" class="email">gbadanahatti@us.ibm.com@Giris-MacBook-Pro.local</a></li>
-<li>Leo R. Lundgren <a href="mailto:leo@finalresort.org" class="email">leo@finalresort.org</a></li>
-<li>wolfv <a href="mailto:wolfv6@users.noreply.github.com" class="email">wolfv6@users.noreply.github.com</a></li>
-<li>Dave Pedu <a href="mailto:dave@davepedu.com" class="email">dave@davepedu.com</a></li>
-<li>Stefan Lindblom <a href="mailto:lindblom@spotify.com" class="email">lindblom@spotify.com</a></li>
-<li>seuffert <a href="mailto:oliver@seuffert.biz" class="email">oliver@seuffert.biz</a></li>
-<li>gbadanahatti <a href="mailto:37121690+gbadanahatti@users.noreply.github.com" class="email">37121690+gbadanahatti@users.noreply.github.com</a></li>
-<li>Keith Goldfarb <a href="mailto:barkofdelight@gmail.com" class="email">barkofdelight@gmail.com</a></li>
-<li>Steve Kriss <a href="mailto:steve@heptio.com" class="email">steve@heptio.com</a></li>
-<li>Chih-Hsuan Yen <a href="mailto:yan12125@gmail.com" class="email">yan12125@gmail.com</a></li>
-<li>Alexander Neumann <a href="mailto:fd0@users.noreply.github.com" class="email">fd0@users.noreply.github.com</a></li>
-<li>Matt Holt <a href="mailto:mholt@users.noreply.github.com" class="email">mholt@users.noreply.github.com</a></li>
-<li>Eri Bastos <a href="mailto:bastos.eri@gmail.com" class="email">bastos.eri@gmail.com</a></li>
-<li>Michael P. Dubner <a href="mailto:pywebmail@list.ru" class="email">pywebmail@list.ru</a></li>
-<li>Antoine GIRARD <a href="mailto:sapk@users.noreply.github.com" class="email">sapk@users.noreply.github.com</a></li>
-<li>Mateusz Piotrowski <a href="mailto:mpp302@gmail.com" class="email">mpp302@gmail.com</a></li>
-<li>Animosity022 <a href="mailto:animosity22@users.noreply.github.com" class="email">animosity22@users.noreply.github.com</a> <a href="mailto:earl.texter@gmail.com" class="email">earl.texter@gmail.com</a></li>
-<li>Peter Baumgartner <a href="mailto:pete@lincolnloop.com" class="email">pete@lincolnloop.com</a></li>
-<li>Craig Rachel <a href="mailto:craig@craigrachel.com" class="email">craig@craigrachel.com</a></li>
-<li>Michael G. Noll <a href="mailto:miguno@users.noreply.github.com" class="email">miguno@users.noreply.github.com</a></li>
-<li>hensur <a href="mailto:me@hensur.de" class="email">me@hensur.de</a></li>
-<li>Oliver Heyme <a href="mailto:de8olihe@lego.com" class="email">de8olihe@lego.com</a></li>
-<li>Richard Yang <a href="mailto:richard@yenforyang.com" class="email">richard@yenforyang.com</a></li>
-<li>Piotr Oleszczyk <a href="mailto:piotr.oleszczyk@gmail.com" class="email">piotr.oleszczyk@gmail.com</a></li>
-<li>Rodrigo <a href="mailto:rodarima@gmail.com" class="email">rodarima@gmail.com</a></li>
-<li>NoLooseEnds <a href="mailto:NoLooseEnds@users.noreply.github.com" class="email">NoLooseEnds@users.noreply.github.com</a></li>
-<li>Jakub Karlicek <a href="mailto:jakub@karlicek.me" class="email">jakub@karlicek.me</a></li>
-<li>John Clayton <a href="mailto:john@codemonkeylabs.com" class="email">john@codemonkeylabs.com</a></li>
-<li>Kasper Byrdal Nielsen <a href="mailto:byrdal76@gmail.com" class="email">byrdal76@gmail.com</a></li>
-<li>Benjamin Joseph Dag <a href="mailto:bjdag1234@users.noreply.github.com" class="email">bjdag1234@users.noreply.github.com</a></li>
-<li>themylogin <a href="mailto:themylogin@gmail.com" class="email">themylogin@gmail.com</a></li>
-<li>Onno Zweers <a href="mailto:onno.zweers@surfsara.nl" class="email">onno.zweers@surfsara.nl</a></li>
-<li>Jasper Lievisse Adriaanse <a href="mailto:jasper@humppa.nl" class="email">jasper@humppa.nl</a></li>
-<li>sandeepkru <a href="mailto:sandeep.ummadi@gmail.com" class="email">sandeep.ummadi@gmail.com</a> <a href="mailto:sandeepkru@users.noreply.github.com" class="email">sandeepkru@users.noreply.github.com</a></li>
-<li>HerrH <a href="mailto:atomtigerzoo@users.noreply.github.com" class="email">atomtigerzoo@users.noreply.github.com</a></li>
-<li>Andrew <a href="mailto:4030760+sparkyman215@users.noreply.github.com" class="email">4030760+sparkyman215@users.noreply.github.com</a></li>
-<li>dan smith <a href="mailto:XX1011@gmail.com" class="email">XX1011@gmail.com</a></li>
-<li>Oleg Kovalov <a href="mailto:iamolegkovalov@gmail.com" class="email">iamolegkovalov@gmail.com</a></li>
-<li>Ruben Vandamme <a href="mailto:github-com-00ff86@vandamme.email" class="email">github-com-00ff86@vandamme.email</a></li>
-<li>Cnly <a href="mailto:minecnly@gmail.com" class="email">minecnly@gmail.com</a></li>
-<li>Andres Alvarez <a href="mailto:1671935+kir4h@users.noreply.github.com" class="email">1671935+kir4h@users.noreply.github.com</a></li>
-<li>reddi1 <a href="mailto:xreddi@gmail.com" class="email">xreddi@gmail.com</a></li>
-<li>Matt Tucker <a href="mailto:matthewtckr@gmail.com" class="email">matthewtckr@gmail.com</a></li>
-<li>Sebastian Bünger <a href="mailto:buengese@gmail.com" class="email">buengese@gmail.com</a> <a href="mailto:buengese@protonmail.com" class="email">buengese@protonmail.com</a></li>
-<li>Martin Polden <a href="mailto:mpolden@mpolden.no" class="email">mpolden@mpolden.no</a></li>
-<li>Alex Chen <a href="mailto:Cnly@users.noreply.github.com" class="email">Cnly@users.noreply.github.com</a></li>
-<li>Denis <a href="mailto:deniskovpen@gmail.com" class="email">deniskovpen@gmail.com</a></li>
-<li>bsteiss <a href="mailto:35940619+bsteiss@users.noreply.github.com" class="email">35940619+bsteiss@users.noreply.github.com</a></li>
-<li>Cédric Connes <a href="mailto:cedric.connes@gmail.com" class="email">cedric.connes@gmail.com</a></li>
-<li>Dr. Tobias Quathamer <a href="mailto:toddy15@users.noreply.github.com" class="email">toddy15@users.noreply.github.com</a></li>
-<li>dcpu <a href="mailto:42736967+dcpu@users.noreply.github.com" class="email">42736967+dcpu@users.noreply.github.com</a></li>
-<li>Sheldon Rupp <a href="mailto:me@shel.io" class="email">me@shel.io</a></li>
-<li>albertony <a href="mailto:12441419+albertony@users.noreply.github.com" class="email">12441419+albertony@users.noreply.github.com</a></li>
-<li>cron410 <a href="mailto:cron410@gmail.com" class="email">cron410@gmail.com</a></li>
-<li>Anagh Kumar Baranwal <a href="mailto:6824881+darthShadow@users.noreply.github.com" class="email">6824881+darthShadow@users.noreply.github.com</a></li>
-<li>Felix Brucker <a href="mailto:felix@felixbrucker.com" class="email">felix@felixbrucker.com</a></li>
-<li>Santiago Rodríguez <a href="mailto:scollazo@users.noreply.github.com" class="email">scollazo@users.noreply.github.com</a></li>
-<li>Craig Miskell <a href="mailto:craig.miskell@fluxfederation.com" class="email">craig.miskell@fluxfederation.com</a></li>
-<li>Antoine GIRARD <a href="mailto:sapk@sapk.fr" class="email">sapk@sapk.fr</a></li>
-<li>Joanna Marek <a href="mailto:joanna.marek@u2i.com" class="email">joanna.marek@u2i.com</a></li>
-<li>frenos <a href="mailto:frenos@users.noreply.github.com" class="email">frenos@users.noreply.github.com</a></li>
-<li>ssaqua <a href="mailto:ssaqua@users.noreply.github.com" class="email">ssaqua@users.noreply.github.com</a></li>
-<li>xnaas <a href="mailto:me@xnaas.info" class="email">me@xnaas.info</a></li>
-<li>Frantisek Fuka <a href="mailto:fuka@fuxoft.cz" class="email">fuka@fuxoft.cz</a></li>
-<li>Paul Kohout <a href="mailto:pauljkohout@yahoo.com" class="email">pauljkohout@yahoo.com</a></li>
-<li>dcpu <a href="mailto:43330287+dcpu@users.noreply.github.com" class="email">43330287+dcpu@users.noreply.github.com</a></li>
-<li>jackyzy823 <a href="mailto:jackyzy823@gmail.com" class="email">jackyzy823@gmail.com</a></li>
-<li>David Haguenauer <a href="mailto:ml@kurokatta.org" class="email">ml@kurokatta.org</a></li>
-<li>teresy <a href="mailto:hi.teresy@gmail.com" class="email">hi.teresy@gmail.com</a></li>
-<li>buergi <a href="mailto:patbuergi@gmx.de" class="email">patbuergi@gmx.de</a></li>
-<li>Florian Gamboeck <a href="mailto:mail@floga.de" class="email">mail@floga.de</a></li>
-<li>Ralf Hemberger <a href="mailto:10364191+rhemberger@users.noreply.github.com" class="email">10364191+rhemberger@users.noreply.github.com</a></li>
-<li>Scott Edlund <a href="mailto:sedlund@users.noreply.github.com" class="email">sedlund@users.noreply.github.com</a></li>
-<li>Erik Swanson <a href="mailto:erik@retailnext.net" class="email">erik@retailnext.net</a></li>
-<li>Jake Coggiano <a href="mailto:jake@stripe.com" class="email">jake@stripe.com</a></li>
-<li>brused27 <a href="mailto:brused27@noemailaddress" class="email">brused27@noemailaddress</a></li>
-<li>Peter Kaminski <a href="mailto:kaminski@istori.com" class="email">kaminski@istori.com</a></li>
-<li>Henry Ptasinski <a href="mailto:henry@logout.com" class="email">henry@logout.com</a></li>
-<li>Alexander <a href="mailto:kharkovalexander@gmail.com" class="email">kharkovalexander@gmail.com</a></li>
-<li>Garry McNulty <a href="mailto:garrmcnu@gmail.com" class="email">garrmcnu@gmail.com</a></li>
-<li>Mathieu Carbou <a href="mailto:mathieu.carbou@gmail.com" class="email">mathieu.carbou@gmail.com</a></li>
-<li>Mark Otway <a href="mailto:mark@otway.com" class="email">mark@otway.com</a></li>
-<li>William Cocker <a href="mailto:37018962+WilliamCocker@users.noreply.github.com" class="email">37018962+WilliamCocker@users.noreply.github.com</a></li>
-<li>François Leurent <a href="mailto:131.js@cloudyks.org" class="email">131.js@cloudyks.org</a></li>
-<li>Arkadius Stefanski <a href="mailto:arkste@gmail.com" class="email">arkste@gmail.com</a></li>
-<li>Jay <a href="mailto:dev@jaygoel.com" class="email">dev@jaygoel.com</a></li>
-<li>andrea rota <a href="mailto:a@xelera.eu" class="email">a@xelera.eu</a></li>
-<li>nicolov <a href="mailto:nicolov@users.noreply.github.com" class="email">nicolov@users.noreply.github.com</a></li>
-<li>Matt Joiner <a href="mailto:anacrolix@gmail.com" class="email">anacrolix@gmail.com</a></li>
-<li>Dario Guzik <a href="mailto:dario@guzik.com.ar" class="email">dario@guzik.com.ar</a></li>
-<li>qip <a href="mailto:qip@users.noreply.github.com" class="email">qip@users.noreply.github.com</a></li>
-<li>yair@unicorn <a href="mailto:yair@unicorn" class="email">yair@unicorn</a></li>
-<li>Matt Robinson <a href="mailto:brimstone@the.narro.ws" class="email">brimstone@the.narro.ws</a></li>
-<li>kayrus <a href="mailto:kay.diam@gmail.com" class="email">kay.diam@gmail.com</a></li>
-<li>Rémy Léone <a href="mailto:remy.leone@gmail.com" class="email">remy.leone@gmail.com</a></li>
-<li>Wojciech Smigielski <a href="mailto:wojciech.hieronim.smigielski@gmail.com" class="email">wojciech.hieronim.smigielski@gmail.com</a></li>
-<li>weetmuts <a href="mailto:oehrstroem@gmail.com" class="email">oehrstroem@gmail.com</a></li>
-<li>Jonathan <a href="mailto:vanillajonathan@users.noreply.github.com" class="email">vanillajonathan@users.noreply.github.com</a></li>
-<li>James Carpenter <a href="mailto:orbsmiv@users.noreply.github.com" class="email">orbsmiv@users.noreply.github.com</a></li>
-<li>Vince <a href="mailto:vince0villamora@gmail.com" class="email">vince0villamora@gmail.com</a></li>
-<li>Nestar47 <a href="mailto:47841759+Nestar47@users.noreply.github.com" class="email">47841759+Nestar47@users.noreply.github.com</a></li>
-<li>Six <a href="mailto:brbsix@gmail.com" class="email">brbsix@gmail.com</a></li>
-<li>Alexandru Bumbacea <a href="mailto:alexandru.bumbacea@booking.com" class="email">alexandru.bumbacea@booking.com</a></li>
-<li>calisro <a href="mailto:robert.calistri@gmail.com" class="email">robert.calistri@gmail.com</a></li>
-<li>Dr.Rx <a href="mailto:david.rey@nventive.com" class="email">david.rey@nventive.com</a></li>
-<li>marcintustin <a href="mailto:marcintustin@users.noreply.github.com" class="email">marcintustin@users.noreply.github.com</a></li>
-<li>jaKa Močnik <a href="mailto:jaka@koofr.net" class="email">jaka@koofr.net</a></li>
-<li>Fionera <a href="mailto:fionera@fionera.de" class="email">fionera@fionera.de</a></li>
-<li>Dan Walters <a href="mailto:dan@walters.io" class="email">dan@walters.io</a></li>
-<li>Danil Semelenov <a href="mailto:sgtpep@users.noreply.github.com" class="email">sgtpep@users.noreply.github.com</a></li>
-<li>xopez <a href="mailto:28950736+xopez@users.noreply.github.com" class="email">28950736+xopez@users.noreply.github.com</a></li>
-<li>Ben Boeckel <a href="mailto:mathstuf@gmail.com" class="email">mathstuf@gmail.com</a></li>
-<li>Manu <a href="mailto:manu@snapdragon.cc" class="email">manu@snapdragon.cc</a></li>
-<li>Kyle E. Mitchell <a href="mailto:kyle@kemitchell.com" class="email">kyle@kemitchell.com</a></li>
-<li>Gary Kim <a href="mailto:gary@garykim.dev" class="email">gary@garykim.dev</a></li>
-<li>Jon <a href="mailto:jonathn@github.com" class="email">jonathn@github.com</a></li>
-<li>Jeff Quinn <a href="mailto:jeffrey.quinn@bluevoyant.com" class="email">jeffrey.quinn@bluevoyant.com</a></li>
-<li>Peter Berbec <a href="mailto:peter@berbec.com" class="email">peter@berbec.com</a></li>
-<li>didil <a href="mailto:1284255+didil@users.noreply.github.com" class="email">1284255+didil@users.noreply.github.com</a></li>
-<li>id01 <a href="mailto:gaviniboom@gmail.com" class="email">gaviniboom@gmail.com</a></li>
-<li>Robert Marko <a href="mailto:robimarko@gmail.com" class="email">robimarko@gmail.com</a></li>
-<li>Philip Harvey <a href="mailto:32467456+pharveybattelle@users.noreply.github.com" class="email">32467456+pharveybattelle@users.noreply.github.com</a></li>
-<li>JorisE <a href="mailto:JorisE@users.noreply.github.com" class="email">JorisE@users.noreply.github.com</a></li>
-<li>garry415 <a href="mailto:garry.415@gmail.com" class="email">garry.415@gmail.com</a></li>
-<li>forgems <a href="mailto:forgems@gmail.com" class="email">forgems@gmail.com</a></li>
-<li>Florian Apolloner <a href="mailto:florian@apolloner.eu" class="email">florian@apolloner.eu</a></li>
-<li>Aleksandar Janković <a href="mailto:office@ajankovic.com" class="email">office@ajankovic.com</a> <a href="mailto:ajankovic@users.noreply.github.com" class="email">ajankovic@users.noreply.github.com</a></li>
-<li>Maran <a href="mailto:maran@protonmail.com" class="email">maran@protonmail.com</a></li>
-<li>nguyenhuuluan434 <a href="mailto:nguyenhuuluan434@gmail.com" class="email">nguyenhuuluan434@gmail.com</a></li>
-<li>Laura Hausmann <a href="mailto:zotan@zotan.pw" class="email">zotan@zotan.pw</a> <a href="mailto:laura@hausmann.dev" class="email">laura@hausmann.dev</a></li>
-<li>yparitcher <a href="mailto:y@paritcher.com" class="email">y@paritcher.com</a></li>
-<li>AbelThar <a href="mailto:abela.tharen@gmail.com" class="email">abela.tharen@gmail.com</a></li>
-<li>Matti Niemenmaa <a href="mailto:matti.niemenmaa+git@iki.fi" class="email">matti.niemenmaa+git@iki.fi</a></li>
-<li>Russell Davis <a href="mailto:russelldavis@users.noreply.github.com" class="email">russelldavis@users.noreply.github.com</a></li>
-<li>Yi FU <a href="mailto:yi.fu@tink.se" class="email">yi.fu@tink.se</a></li>
-<li>Paul Millar <a href="mailto:paul.millar@desy.de" class="email">paul.millar@desy.de</a></li>
-<li>justinalin <a href="mailto:justinalin@qnap.com" class="email">justinalin@qnap.com</a></li>
-<li>EliEron <a href="mailto:subanimehd@gmail.com" class="email">subanimehd@gmail.com</a></li>
-<li>justina777 <a href="mailto:chiahuei.lin@gmail.com" class="email">chiahuei.lin@gmail.com</a></li>
-<li>Chaitanya Bankanhal <a href="mailto:bchaitanya15@gmail.com" class="email">bchaitanya15@gmail.com</a></li>
-<li>Michał Matczuk <a href="mailto:michal@scylladb.com" class="email">michal@scylladb.com</a></li>
-<li>Macavirus <a href="mailto:macavirus@zoho.com" class="email">macavirus@zoho.com</a></li>
-<li>Abhinav Sharma <a href="mailto:abhi18av@outlook.com" class="email">abhi18av@outlook.com</a></li>
-<li>ginvine <a href="mailto:34869051+ginvine@users.noreply.github.com" class="email">34869051+ginvine@users.noreply.github.com</a></li>
-<li>Patrick Wang <a href="mailto:mail6543210@yahoo.com.tw" class="email">mail6543210@yahoo.com.tw</a></li>
-<li>Cenk Alti <a href="mailto:cenkalti@gmail.com" class="email">cenkalti@gmail.com</a></li>
-<li>Andreas Chlupka <a href="mailto:andy@chlupka.com" class="email">andy@chlupka.com</a></li>
-<li>Alfonso Montero <a href="mailto:amontero@tinet.org" class="email">amontero@tinet.org</a></li>
-<li>Ivan Andreev <a href="mailto:ivandeex@gmail.com" class="email">ivandeex@gmail.com</a></li>
-<li>David Baumgold <a href="mailto:david@davidbaumgold.com" class="email">david@davidbaumgold.com</a></li>
-<li>Lars Lehtonen <a href="mailto:lars.lehtonen@gmail.com" class="email">lars.lehtonen@gmail.com</a></li>
-<li>Matei David <a href="mailto:matei.david@gmail.com" class="email">matei.david@gmail.com</a></li>
-<li>David <a href="mailto:david.bramwell@endemolshine.com" class="email">david.bramwell@endemolshine.com</a></li>
-<li>Anthony Rusdi <a href="mailto:33247310+antrusd@users.noreply.github.com" class="email">33247310+antrusd@users.noreply.github.com</a></li>
-<li>Richard Patel <a href="mailto:me@terorie.dev" class="email">me@terorie.dev</a></li>
-<li>庄天翼 <a href="mailto:zty0826@gmail.com" class="email">zty0826@gmail.com</a></li>
-<li>SwitchJS <a href="mailto:dev@switchjs.com" class="email">dev@switchjs.com</a></li>
-<li>Raphael <a href="mailto:PowershellNinja@users.noreply.github.com" class="email">PowershellNinja@users.noreply.github.com</a></li>
-<li>Sezal Agrawal <a href="mailto:sezalagrawal@gmail.com" class="email">sezalagrawal@gmail.com</a></li>
-<li>Tyler <a href="mailto:TylerNakamura@users.noreply.github.com" class="email">TylerNakamura@users.noreply.github.com</a></li>
-<li>Brett Dutro <a href="mailto:brett.dutro@gmail.com" class="email">brett.dutro@gmail.com</a></li>
-<li>Vighnesh SK <a href="mailto:booterror99@gmail.com" class="email">booterror99@gmail.com</a></li>
-<li>Arijit Biswas <a href="mailto:dibbyo456@gmail.com" class="email">dibbyo456@gmail.com</a></li>
-<li>Michele Caci <a href="mailto:michele.caci@gmail.com" class="email">michele.caci@gmail.com</a></li>
-<li>AlexandrBoltris <a href="mailto:ua2fgb@gmail.com" class="email">ua2fgb@gmail.com</a></li>
-<li>Bryce Larson <a href="mailto:blarson@saltstack.com" class="email">blarson@saltstack.com</a></li>
-<li>Carlos Ferreyra <a href="mailto:crypticmind@gmail.com" class="email">crypticmind@gmail.com</a></li>
-<li>Saksham Khanna <a href="mailto:sakshamkhanna@outlook.com" class="email">sakshamkhanna@outlook.com</a></li>
-<li>dausruddin <a href="mailto:5763466+dausruddin@users.noreply.github.com" class="email">5763466+dausruddin@users.noreply.github.com</a></li>
-<li>zero-24 <a href="mailto:zero-24@users.noreply.github.com" class="email">zero-24@users.noreply.github.com</a></li>
-<li>Xiaoxing Ye <a href="mailto:ye@xiaoxing.us" class="email">ye@xiaoxing.us</a></li>
-<li>Barry Muldrey <a href="mailto:barry@muldrey.net" class="email">barry@muldrey.net</a></li>
-<li>Sebastian Brandt <a href="mailto:sebastian.brandt@friday.de" class="email">sebastian.brandt@friday.de</a></li>
-<li>Marco Molteni <a href="mailto:marco.molteni@mailbox.org" class="email">marco.molteni@mailbox.org</a></li>
-<li>Ankur Gupta <a href="mailto:7876747+ankur0493@users.noreply.github.com" class="email">7876747+ankur0493@users.noreply.github.com</a></li>
-<li>Maciej Zimnoch <a href="mailto:maciej@scylladb.com" class="email">maciej@scylladb.com</a></li>
-<li>anuar45 <a href="mailto:serdaliyev.anuar@gmail.com" class="email">serdaliyev.anuar@gmail.com</a></li>
-<li>Fernando <a href="mailto:ferferga@users.noreply.github.com" class="email">ferferga@users.noreply.github.com</a></li>
-<li>David Cole <a href="mailto:david.cole@sohonet.com" class="email">david.cole@sohonet.com</a></li>
-<li>Wei He <a href="mailto:git@weispot.com" class="email">git@weispot.com</a></li>
-<li>Outvi V <a href="mailto:19144373+outloudvi@users.noreply.github.com" class="email">19144373+outloudvi@users.noreply.github.com</a></li>
-<li>Thomas Kriechbaumer <a href="mailto:thomas@kriechbaumer.name" class="email">thomas@kriechbaumer.name</a></li>
-<li>Tennix <a href="mailto:tennix@users.noreply.github.com" class="email">tennix@users.noreply.github.com</a></li>
-<li>Ole Schütt <a href="mailto:ole@schuett.name" class="email">ole@schuett.name</a></li>
-<li>Kuang-che Wu <a href="mailto:kcwu@csie.org" class="email">kcwu@csie.org</a></li>
-<li>Thomas Eales <a href="mailto:wingsuit@users.noreply.github.com" class="email">wingsuit@users.noreply.github.com</a></li>
-<li>Paul Tinsley <a href="mailto:paul.tinsley@vitalsource.com" class="email">paul.tinsley@vitalsource.com</a></li>
-<li>Felix Hungenberg <a href="mailto:git@shiftgeist.com" class="email">git@shiftgeist.com</a></li>
-<li>Benjamin Richter <a href="mailto:github@dev.telepath.de" class="email">github@dev.telepath.de</a></li>
-<li>landall <a href="mailto:cst_zf@qq.com" class="email">cst_zf@qq.com</a></li>
-<li>thestigma <a href="mailto:thestigma@gmail.com" class="email">thestigma@gmail.com</a></li>
-<li>jtagcat <a href="mailto:38327267+jtagcat@users.noreply.github.com" class="email">38327267+jtagcat@users.noreply.github.com</a></li>
-<li>Damon Permezel <a href="mailto:permezel@me.com" class="email">permezel@me.com</a></li>
-<li>boosh <a href="mailto:boosh@users.noreply.github.com" class="email">boosh@users.noreply.github.com</a></li>
-<li>unbelauscht <a href="mailto:58393353+unbelauscht@users.noreply.github.com" class="email">58393353+unbelauscht@users.noreply.github.com</a></li>
-<li>Motonori IWAMURO <a href="mailto:vmi@nifty.com" class="email">vmi@nifty.com</a></li>
-<li>Benjapol Worakan <a href="mailto:benwrk@live.com" class="email">benwrk@live.com</a></li>
-<li>Dave Koston <a href="mailto:dave.koston@stackpath.com" class="email">dave.koston@stackpath.com</a></li>
-<li>Durval Menezes <a href="mailto:DurvalMenezes@users.noreply.github.com" class="email">DurvalMenezes@users.noreply.github.com</a></li>
-<li>Tim Gallant <a href="mailto:me@timgallant.us" class="email">me@timgallant.us</a></li>
-<li>Frederick Zhang <a href="mailto:frederick888@tsundere.moe" class="email">frederick888@tsundere.moe</a></li>
-<li>valery1707 <a href="mailto:valery1707@gmail.com" class="email">valery1707@gmail.com</a></li>
-<li>Yves G <a href="mailto:theYinYeti@yalis.fr" class="email">theYinYeti@yalis.fr</a></li>
-<li>Shing Kit Chan <a href="mailto:chanshingkit@gmail.com" class="email">chanshingkit@gmail.com</a></li>
-<li>Franklyn Tackitt <a href="mailto:franklyn@tackitt.net" class="email">franklyn@tackitt.net</a></li>
-<li>Robert-André Mauchin <a href="mailto:zebob.m@gmail.com" class="email">zebob.m@gmail.com</a></li>
-<li>evileye <a href="mailto:48332831+ibiruai@users.noreply.github.com" class="email">48332831+ibiruai@users.noreply.github.com</a></li>
-<li>Joachim Brandon LeBlanc <a href="mailto:brandon@leblanc.codes" class="email">brandon@leblanc.codes</a></li>
-<li>Patryk Jakuszew <a href="mailto:patryk.jakuszew@gmail.com" class="email">patryk.jakuszew@gmail.com</a></li>
-<li>fishbullet <a href="mailto:shindu666@gmail.com" class="email">shindu666@gmail.com</a></li>
+<li>Alex Couper <a href="mailto:amcouper@gmail.com"
+class="email">amcouper@gmail.com</a></li>
+<li>Leonid Shalupov <a href="mailto:leonid@shalupov.com"
+class="email">leonid@shalupov.com</a> <a
+href="mailto:shalupov@diverse.org.ru"
+class="email">shalupov@diverse.org.ru</a></li>
+<li>Shimon Doodkin <a href="mailto:helpmepro1@gmail.com"
+class="email">helpmepro1@gmail.com</a></li>
+<li>Colin Nicholson <a href="mailto:colin@colinn.com"
+class="email">colin@colinn.com</a></li>
+<li>Klaus Post <a href="mailto:klauspost@gmail.com"
+class="email">klauspost@gmail.com</a></li>
+<li>Sergey Tolmachev <a href="mailto:tolsi.ru@gmail.com"
+class="email">tolsi.ru@gmail.com</a></li>
+<li>Adriano Aurélio Meirelles <a href="mailto:adriano@atinge.com"
+class="email">adriano@atinge.com</a></li>
+<li>C. Bess <a href="mailto:cbess@users.noreply.github.com"
+class="email">cbess@users.noreply.github.com</a></li>
+<li>Dmitry Burdeev <a href="mailto:dibu28@gmail.com"
+class="email">dibu28@gmail.com</a></li>
+<li>Joseph Spurrier <a href="mailto:github@josephspurrier.com"
+class="email">github@josephspurrier.com</a></li>
+<li>Björn Harrtell <a href="mailto:bjorn@wololo.org"
+class="email">bjorn@wololo.org</a></li>
+<li>Xavier Lucas <a href="mailto:xavier.lucas@corp.ovh.com"
+class="email">xavier.lucas@corp.ovh.com</a></li>
+<li>Werner Beroux <a href="mailto:werner@beroux.com"
+class="email">werner@beroux.com</a></li>
+<li>Brian Stengaard <a href="mailto:brian@stengaard.eu"
+class="email">brian@stengaard.eu</a></li>
+<li>Jakub Gedeon <a href="mailto:jgedeon@sofi.com"
+class="email">jgedeon@sofi.com</a></li>
+<li>Jim Tittsler <a href="mailto:jwt@onjapan.net"
+class="email">jwt@onjapan.net</a></li>
+<li>Michal Witkowski <a href="mailto:michal@improbable.io"
+class="email">michal@improbable.io</a></li>
+<li>Fabian Ruff <a href="mailto:fabian.ruff@sap.com"
+class="email">fabian.ruff@sap.com</a></li>
+<li>Leigh Klotz <a href="mailto:klotz@quixey.com"
+class="email">klotz@quixey.com</a></li>
+<li>Romain Lapray <a href="mailto:lapray.romain@gmail.com"
+class="email">lapray.romain@gmail.com</a></li>
+<li>Justin R. Wilson <a href="mailto:jrw972@gmail.com"
+class="email">jrw972@gmail.com</a></li>
+<li>Antonio Messina <a href="mailto:antonio.s.messina@gmail.com"
+class="email">antonio.s.messina@gmail.com</a></li>
+<li>Stefan G. Weichinger <a href="mailto:office@oops.co.at"
+class="email">office@oops.co.at</a></li>
+<li>Per Cederberg <a href="mailto:cederberg@gmail.com"
+class="email">cederberg@gmail.com</a></li>
+<li>Radek Šenfeld <a href="mailto:rush@logic.cz"
+class="email">rush@logic.cz</a></li>
+<li>Fredrik Fornwall <a href="mailto:fredrik@fornwall.net"
+class="email">fredrik@fornwall.net</a></li>
+<li>Asko Tamm <a href="mailto:asko@deekit.net"
+class="email">asko@deekit.net</a></li>
+<li>xor-zz <a href="mailto:xor@gstocco.com"
+class="email">xor@gstocco.com</a></li>
+<li>Tomasz Mazur <a href="mailto:tmazur90@gmail.com"
+class="email">tmazur90@gmail.com</a></li>
+<li>Marco Paganini <a href="mailto:paganini@paganini.net"
+class="email">paganini@paganini.net</a></li>
+<li>Felix Bünemann <a href="mailto:buenemann@louis.info"
+class="email">buenemann@louis.info</a></li>
+<li>Durval Menezes <a href="mailto:jmrclone@durval.com"
+class="email">jmrclone@durval.com</a></li>
+<li>Luiz Carlos Rumbelsperger Viana <a
+href="mailto:maxd13_luiz_carlos@hotmail.com"
+class="email">maxd13_luiz_carlos@hotmail.com</a></li>
+<li>Stefan Breunig <a href="mailto:stefan-github@yrden.de"
+class="email">stefan-github@yrden.de</a></li>
+<li>Alishan Ladhani <a href="mailto:ali-l@users.noreply.github.com"
+class="email">ali-l@users.noreply.github.com</a></li>
+<li>0xJAKE <a href="mailto:0xJAKE@users.noreply.github.com"
+class="email">0xJAKE@users.noreply.github.com</a></li>
+<li>Thibault Molleman <a
+href="mailto:thibaultmol@users.noreply.github.com"
+class="email">thibaultmol@users.noreply.github.com</a></li>
+<li>Scott McGillivray <a href="mailto:scott.mcgillivray@gmail.com"
+class="email">scott.mcgillivray@gmail.com</a></li>
+<li>Bjørn Erik Pedersen <a href="mailto:bjorn.erik.pedersen@gmail.com"
+class="email">bjorn.erik.pedersen@gmail.com</a></li>
+<li>Lukas Loesche <a href="mailto:lukas@mesosphere.io"
+class="email">lukas@mesosphere.io</a></li>
+<li>emyarod <a href="mailto:emyarod@users.noreply.github.com"
+class="email">emyarod@users.noreply.github.com</a></li>
+<li>T.C. Ferguson <a href="mailto:tcf909@gmail.com"
+class="email">tcf909@gmail.com</a></li>
+<li>Brandur <a href="mailto:brandur@mutelight.org"
+class="email">brandur@mutelight.org</a></li>
+<li>Dario Giovannetti <a href="mailto:dev@dariogiovannetti.net"
+class="email">dev@dariogiovannetti.net</a></li>
+<li>Károly Oláh <a href="mailto:okaresz@aol.com"
+class="email">okaresz@aol.com</a></li>
+<li>Jon Yergatian <a href="mailto:jon@macfanatic.ca"
+class="email">jon@macfanatic.ca</a></li>
+<li>Jack Schmidt <a href="mailto:github@mowsey.org"
+class="email">github@mowsey.org</a></li>
+<li>Dedsec1 <a href="mailto:Dedsec1@users.noreply.github.com"
+class="email">Dedsec1@users.noreply.github.com</a></li>
+<li>Hisham Zarka <a href="mailto:hzarka@gmail.com"
+class="email">hzarka@gmail.com</a></li>
+<li>Jérôme Vizcaino <a href="mailto:jerome.vizcaino@gmail.com"
+class="email">jerome.vizcaino@gmail.com</a></li>
+<li>Mike Tesch <a href="mailto:mjt6129@rit.edu"
+class="email">mjt6129@rit.edu</a></li>
+<li>Marvin Watson <a href="mailto:marvwatson@users.noreply.github.com"
+class="email">marvwatson@users.noreply.github.com</a></li>
+<li>Danny Tsai <a href="mailto:danny8376@gmail.com"
+class="email">danny8376@gmail.com</a></li>
+<li>Yoni Jah <a href="mailto:yonjah+git@gmail.com"
+class="email">yonjah+git@gmail.com</a> <a
+href="mailto:yonjah+github@gmail.com"
+class="email">yonjah+github@gmail.com</a></li>
+<li>Stephen Harris <a href="mailto:github@spuddy.org"
+class="email">github@spuddy.org</a> <a
+href="mailto:sweharris@users.noreply.github.com"
+class="email">sweharris@users.noreply.github.com</a></li>
+<li>Ihor Dvoretskyi <a href="mailto:ihor.dvoretskyi@gmail.com"
+class="email">ihor.dvoretskyi@gmail.com</a></li>
+<li>Jon Craton <a href="mailto:jncraton@gmail.com"
+class="email">jncraton@gmail.com</a></li>
+<li>Hraban Luyat <a href="mailto:hraban@0brg.net"
+class="email">hraban@0brg.net</a></li>
+<li>Michael Ledin <a href="mailto:mledin89@gmail.com"
+class="email">mledin89@gmail.com</a></li>
+<li>Martin Kristensen <a href="mailto:me@azgul.com"
+class="email">me@azgul.com</a></li>
+<li>Too Much IO <a href="mailto:toomuchio@users.noreply.github.com"
+class="email">toomuchio@users.noreply.github.com</a></li>
+<li>Anisse Astier <a href="mailto:anisse@astier.eu"
+class="email">anisse@astier.eu</a></li>
+<li>Zahiar Ahmed <a href="mailto:zahiar@live.com"
+class="email">zahiar@live.com</a></li>
+<li>Igor Kharin <a href="mailto:igorkharin@gmail.com"
+class="email">igorkharin@gmail.com</a></li>
+<li>Bill Zissimopoulos <a href="mailto:billziss@navimatics.com"
+class="email">billziss@navimatics.com</a></li>
+<li>Bob Potter <a href="mailto:bobby.potter@gmail.com"
+class="email">bobby.potter@gmail.com</a></li>
+<li>Steven Lu <a href="mailto:tacticalazn@gmail.com"
+class="email">tacticalazn@gmail.com</a></li>
+<li>Sjur Fredriksen <a href="mailto:sjurtf@ifi.uio.no"
+class="email">sjurtf@ifi.uio.no</a></li>
+<li>Ruwbin <a href="mailto:hubus12345@gmail.com"
+class="email">hubus12345@gmail.com</a></li>
+<li>Fabian Möller <a href="mailto:fabianm88@gmail.com"
+class="email">fabianm88@gmail.com</a> <a
+href="mailto:f.moeller@nynex.de"
+class="email">f.moeller@nynex.de</a></li>
+<li>Edward Q. Bridges <a href="mailto:github@eqbridges.com"
+class="email">github@eqbridges.com</a></li>
+<li>Vasiliy Tolstov <a href="mailto:v.tolstov@selfip.ru"
+class="email">v.tolstov@selfip.ru</a></li>
+<li>Harshavardhana <a href="mailto:harsha@minio.io"
+class="email">harsha@minio.io</a></li>
+<li>sainaen <a href="mailto:sainaen@gmail.com"
+class="email">sainaen@gmail.com</a></li>
+<li>gdm85 <a href="mailto:gdm85@users.noreply.github.com"
+class="email">gdm85@users.noreply.github.com</a></li>
+<li>Yaroslav Halchenko <a href="mailto:debian@onerussian.com"
+class="email">debian@onerussian.com</a></li>
+<li>John Papandriopoulos <a href="mailto:jpap@users.noreply.github.com"
+class="email">jpap@users.noreply.github.com</a></li>
+<li>Zhiming Wang <a href="mailto:zmwangx@gmail.com"
+class="email">zmwangx@gmail.com</a></li>
+<li>Andy Pilate <a href="mailto:cubox@cubox.me"
+class="email">cubox@cubox.me</a></li>
+<li>Oliver Heyme <a href="mailto:olihey@googlemail.com"
+class="email">olihey@googlemail.com</a> <a
+href="mailto:olihey@users.noreply.github.com"
+class="email">olihey@users.noreply.github.com</a> <a
+href="mailto:de8olihe@lego.com" class="email">de8olihe@lego.com</a></li>
+<li>wuyu <a href="mailto:wuyu@yunify.com"
+class="email">wuyu@yunify.com</a></li>
+<li>Andrei Dragomir <a href="mailto:adragomi@adobe.com"
+class="email">adragomi@adobe.com</a></li>
+<li>Christian Brüggemann <a href="mailto:mail@cbruegg.com"
+class="email">mail@cbruegg.com</a></li>
+<li>Alex McGrath Kraak <a href="mailto:amkdude@gmail.com"
+class="email">amkdude@gmail.com</a></li>
+<li>bpicode <a href="mailto:bjoern.pirnay@googlemail.com"
+class="email">bjoern.pirnay@googlemail.com</a></li>
+<li>Daniel Jagszent <a href="mailto:daniel@jagszent.de"
+class="email">daniel@jagszent.de</a></li>
+<li>Josiah White <a href="mailto:thegenius2009@gmail.com"
+class="email">thegenius2009@gmail.com</a></li>
+<li>Ishuah Kariuki <a href="mailto:kariuki@ishuah.com"
+class="email">kariuki@ishuah.com</a> <a href="mailto:ishuah91@gmail.com"
+class="email">ishuah91@gmail.com</a></li>
+<li>Jan Varho <a href="mailto:jan@varho.org"
+class="email">jan@varho.org</a></li>
+<li>Girish Ramakrishnan <a href="mailto:girish@cloudron.io"
+class="email">girish@cloudron.io</a></li>
+<li>LingMan <a href="mailto:LingMan@users.noreply.github.com"
+class="email">LingMan@users.noreply.github.com</a></li>
+<li>Jacob McNamee <a href="mailto:jacobmcnamee@gmail.com"
+class="email">jacobmcnamee@gmail.com</a></li>
+<li>jersou <a href="mailto:jertux@gmail.com"
+class="email">jertux@gmail.com</a></li>
+<li>thierry <a href="mailto:thierry@substantiel.fr"
+class="email">thierry@substantiel.fr</a></li>
+<li>Simon Leinen <a href="mailto:simon.leinen@gmail.com"
+class="email">simon.leinen@gmail.com</a> <a
+href="mailto:ubuntu@s3-test.novalocal"
+class="email">ubuntu@s3-test.novalocal</a></li>
+<li>Dan Dascalescu <a href="mailto:ddascalescu+github@gmail.com"
+class="email">ddascalescu+github@gmail.com</a></li>
+<li>Jason Rose <a href="mailto:jason@jro.io"
+class="email">jason@jro.io</a></li>
+<li>Andrew Starr-Bochicchio <a href="mailto:a.starr.b@gmail.com"
+class="email">a.starr.b@gmail.com</a></li>
+<li>John Leach <a href="mailto:john@johnleach.co.uk"
+class="email">john@johnleach.co.uk</a></li>
+<li>Corban Raun <a href="mailto:craun@instructure.com"
+class="email">craun@instructure.com</a></li>
+<li>Pierre Carlson <a href="mailto:mpcarl@us.ibm.com"
+class="email">mpcarl@us.ibm.com</a></li>
+<li>Ernest Borowski <a href="mailto:er.borowski@gmail.com"
+class="email">er.borowski@gmail.com</a></li>
+<li>Remus Bunduc <a href="mailto:remus.bunduc@gmail.com"
+class="email">remus.bunduc@gmail.com</a></li>
+<li>Iakov Davydov <a href="mailto:iakov.davydov@unil.ch"
+class="email">iakov.davydov@unil.ch</a> <a
+href="mailto:dav05.gith@myths.ru"
+class="email">dav05.gith@myths.ru</a></li>
+<li>Jakub Tasiemski <a href="mailto:tasiemski@gmail.com"
+class="email">tasiemski@gmail.com</a></li>
+<li>David Minor <a href="mailto:dminor@saymedia.com"
+class="email">dminor@saymedia.com</a></li>
+<li>Tim Cooijmans <a href="mailto:cooijmans.tim@gmail.com"
+class="email">cooijmans.tim@gmail.com</a></li>
+<li>Laurence <a href="mailto:liuxy6@gmail.com"
+class="email">liuxy6@gmail.com</a></li>
+<li>Giovanni Pizzi <a href="mailto:gio.piz@gmail.com"
+class="email">gio.piz@gmail.com</a></li>
+<li>Filip Bartodziej <a href="mailto:filipbartodziej@gmail.com"
+class="email">filipbartodziej@gmail.com</a></li>
+<li>Jon Fautley <a href="mailto:jon@dead.li"
+class="email">jon@dead.li</a></li>
+<li>lewapm <a href="mailto:32110057+lewapm@users.noreply.github.com"
+class="email">32110057+lewapm@users.noreply.github.com</a></li>
+<li>Yassine Imounachen <a href="mailto:yassine256@gmail.com"
+class="email">yassine256@gmail.com</a></li>
+<li>Chris Redekop <a
+href="mailto:chris-redekop@users.noreply.github.com"
+class="email">chris-redekop@users.noreply.github.com</a> <a
+href="mailto:chris.redekop@gmail.com"
+class="email">chris.redekop@gmail.com</a></li>
+<li>Jon Fautley <a href="mailto:jon@adenoid.appstal.co.uk"
+class="email">jon@adenoid.appstal.co.uk</a></li>
+<li>Will Gunn <a href="mailto:WillGunn@users.noreply.github.com"
+class="email">WillGunn@users.noreply.github.com</a></li>
+<li>Lucas Bremgartner <a href="mailto:lucas@bremis.ch"
+class="email">lucas@bremis.ch</a></li>
+<li>Jody Frankowski <a href="mailto:jody.frankowski@gmail.com"
+class="email">jody.frankowski@gmail.com</a></li>
+<li>Andreas Roussos <a href="mailto:arouss1980@gmail.com"
+class="email">arouss1980@gmail.com</a></li>
+<li>nbuchanan <a href="mailto:nbuchanan@utah.gov"
+class="email">nbuchanan@utah.gov</a></li>
+<li>Durval Menezes <a href="mailto:rclone@durval.com"
+class="email">rclone@durval.com</a></li>
+<li>Victor <a href="mailto:vb-github@viblo.se"
+class="email">vb-github@viblo.se</a></li>
+<li>Mateusz <a href="mailto:pabian.mateusz@gmail.com"
+class="email">pabian.mateusz@gmail.com</a></li>
+<li>Daniel Loader <a href="mailto:spicypixel@gmail.com"
+class="email">spicypixel@gmail.com</a></li>
+<li>David0rk <a href="mailto:davidork@gmail.com"
+class="email">davidork@gmail.com</a></li>
+<li>Alexander Neumann <a href="mailto:alexander@bumpern.de"
+class="email">alexander@bumpern.de</a></li>
+<li>Giri Badanahatti <a
+href="mailto:gbadanahatti@us.ibm.com@Giris-MacBook-Pro.local"
+class="email">gbadanahatti@us.ibm.com@Giris-MacBook-Pro.local</a></li>
+<li>Leo R. Lundgren <a href="mailto:leo@finalresort.org"
+class="email">leo@finalresort.org</a></li>
+<li>wolfv <a href="mailto:wolfv6@users.noreply.github.com"
+class="email">wolfv6@users.noreply.github.com</a></li>
+<li>Dave Pedu <a href="mailto:dave@davepedu.com"
+class="email">dave@davepedu.com</a></li>
+<li>Stefan Lindblom <a href="mailto:lindblom@spotify.com"
+class="email">lindblom@spotify.com</a></li>
+<li>seuffert <a href="mailto:oliver@seuffert.biz"
+class="email">oliver@seuffert.biz</a></li>
+<li>gbadanahatti <a
+href="mailto:37121690+gbadanahatti@users.noreply.github.com"
+class="email">37121690+gbadanahatti@users.noreply.github.com</a></li>
+<li>Keith Goldfarb <a href="mailto:barkofdelight@gmail.com"
+class="email">barkofdelight@gmail.com</a></li>
+<li>Steve Kriss <a href="mailto:steve@heptio.com"
+class="email">steve@heptio.com</a></li>
+<li>Chih-Hsuan Yen <a href="mailto:yan12125@gmail.com"
+class="email">yan12125@gmail.com</a></li>
+<li>Alexander Neumann <a href="mailto:fd0@users.noreply.github.com"
+class="email">fd0@users.noreply.github.com</a></li>
+<li>Matt Holt <a href="mailto:mholt@users.noreply.github.com"
+class="email">mholt@users.noreply.github.com</a></li>
+<li>Eri Bastos <a href="mailto:bastos.eri@gmail.com"
+class="email">bastos.eri@gmail.com</a></li>
+<li>Michael P. Dubner <a href="mailto:pywebmail@list.ru"
+class="email">pywebmail@list.ru</a></li>
+<li>Antoine GIRARD <a href="mailto:sapk@users.noreply.github.com"
+class="email">sapk@users.noreply.github.com</a></li>
+<li>Mateusz Piotrowski <a href="mailto:mpp302@gmail.com"
+class="email">mpp302@gmail.com</a></li>
+<li>Animosity022 <a href="mailto:animosity22@users.noreply.github.com"
+class="email">animosity22@users.noreply.github.com</a> <a
+href="mailto:earl.texter@gmail.com"
+class="email">earl.texter@gmail.com</a></li>
+<li>Peter Baumgartner <a href="mailto:pete@lincolnloop.com"
+class="email">pete@lincolnloop.com</a></li>
+<li>Craig Rachel <a href="mailto:craig@craigrachel.com"
+class="email">craig@craigrachel.com</a></li>
+<li>Michael G. Noll <a href="mailto:miguno@users.noreply.github.com"
+class="email">miguno@users.noreply.github.com</a></li>
+<li>hensur <a href="mailto:me@hensur.de"
+class="email">me@hensur.de</a></li>
+<li>Oliver Heyme <a href="mailto:de8olihe@lego.com"
+class="email">de8olihe@lego.com</a></li>
+<li>Richard Yang <a href="mailto:richard@yenforyang.com"
+class="email">richard@yenforyang.com</a></li>
+<li>Piotr Oleszczyk <a href="mailto:piotr.oleszczyk@gmail.com"
+class="email">piotr.oleszczyk@gmail.com</a></li>
+<li>Rodrigo <a href="mailto:rodarima@gmail.com"
+class="email">rodarima@gmail.com</a></li>
+<li>NoLooseEnds <a href="mailto:NoLooseEnds@users.noreply.github.com"
+class="email">NoLooseEnds@users.noreply.github.com</a></li>
+<li>Jakub Karlicek <a href="mailto:jakub@karlicek.me"
+class="email">jakub@karlicek.me</a></li>
+<li>John Clayton <a href="mailto:john@codemonkeylabs.com"
+class="email">john@codemonkeylabs.com</a></li>
+<li>Kasper Byrdal Nielsen <a href="mailto:byrdal76@gmail.com"
+class="email">byrdal76@gmail.com</a></li>
+<li>Benjamin Joseph Dag <a
+href="mailto:bjdag1234@users.noreply.github.com"
+class="email">bjdag1234@users.noreply.github.com</a></li>
+<li>themylogin <a href="mailto:themylogin@gmail.com"
+class="email">themylogin@gmail.com</a></li>
+<li>Onno Zweers <a href="mailto:onno.zweers@surfsara.nl"
+class="email">onno.zweers@surfsara.nl</a></li>
+<li>Jasper Lievisse Adriaanse <a href="mailto:jasper@humppa.nl"
+class="email">jasper@humppa.nl</a></li>
+<li>sandeepkru <a href="mailto:sandeep.ummadi@gmail.com"
+class="email">sandeep.ummadi@gmail.com</a> <a
+href="mailto:sandeepkru@users.noreply.github.com"
+class="email">sandeepkru@users.noreply.github.com</a></li>
+<li>HerrH <a href="mailto:atomtigerzoo@users.noreply.github.com"
+class="email">atomtigerzoo@users.noreply.github.com</a></li>
+<li>Andrew <a
+href="mailto:4030760+sparkyman215@users.noreply.github.com"
+class="email">4030760+sparkyman215@users.noreply.github.com</a></li>
+<li>dan smith <a href="mailto:XX1011@gmail.com"
+class="email">XX1011@gmail.com</a></li>
+<li>Oleg Kovalov <a href="mailto:iamolegkovalov@gmail.com"
+class="email">iamolegkovalov@gmail.com</a></li>
+<li>Ruben Vandamme <a href="mailto:github-com-00ff86@vandamme.email"
+class="email">github-com-00ff86@vandamme.email</a></li>
+<li>Cnly <a href="mailto:minecnly@gmail.com"
+class="email">minecnly@gmail.com</a></li>
+<li>Andres Alvarez <a
+href="mailto:1671935+kir4h@users.noreply.github.com"
+class="email">1671935+kir4h@users.noreply.github.com</a></li>
+<li>reddi1 <a href="mailto:xreddi@gmail.com"
+class="email">xreddi@gmail.com</a></li>
+<li>Matt Tucker <a href="mailto:matthewtckr@gmail.com"
+class="email">matthewtckr@gmail.com</a></li>
+<li>Sebastian Bünger <a href="mailto:buengese@gmail.com"
+class="email">buengese@gmail.com</a> <a
+href="mailto:buengese@protonmail.com"
+class="email">buengese@protonmail.com</a></li>
+<li>Martin Polden <a href="mailto:mpolden@mpolden.no"
+class="email">mpolden@mpolden.no</a></li>
+<li>Alex Chen <a href="mailto:Cnly@users.noreply.github.com"
+class="email">Cnly@users.noreply.github.com</a></li>
+<li>Denis <a href="mailto:deniskovpen@gmail.com"
+class="email">deniskovpen@gmail.com</a></li>
+<li>bsteiss <a href="mailto:35940619+bsteiss@users.noreply.github.com"
+class="email">35940619+bsteiss@users.noreply.github.com</a></li>
+<li>Cédric Connes <a href="mailto:cedric.connes@gmail.com"
+class="email">cedric.connes@gmail.com</a></li>
+<li>Dr. Tobias Quathamer <a
+href="mailto:toddy15@users.noreply.github.com"
+class="email">toddy15@users.noreply.github.com</a></li>
+<li>dcpu <a href="mailto:42736967+dcpu@users.noreply.github.com"
+class="email">42736967+dcpu@users.noreply.github.com</a></li>
+<li>Sheldon Rupp <a href="mailto:me@shel.io"
+class="email">me@shel.io</a></li>
+<li>albertony <a
+href="mailto:12441419+albertony@users.noreply.github.com"
+class="email">12441419+albertony@users.noreply.github.com</a></li>
+<li>cron410 <a href="mailto:cron410@gmail.com"
+class="email">cron410@gmail.com</a></li>
+<li>Anagh Kumar Baranwal <a
+href="mailto:6824881+darthShadow@users.noreply.github.com"
+class="email">6824881+darthShadow@users.noreply.github.com</a></li>
+<li>Felix Brucker <a href="mailto:felix@felixbrucker.com"
+class="email">felix@felixbrucker.com</a></li>
+<li>Santiago Rodríguez <a
+href="mailto:scollazo@users.noreply.github.com"
+class="email">scollazo@users.noreply.github.com</a></li>
+<li>Craig Miskell <a href="mailto:craig.miskell@fluxfederation.com"
+class="email">craig.miskell@fluxfederation.com</a></li>
+<li>Antoine GIRARD <a href="mailto:sapk@sapk.fr"
+class="email">sapk@sapk.fr</a></li>
+<li>Joanna Marek <a href="mailto:joanna.marek@u2i.com"
+class="email">joanna.marek@u2i.com</a></li>
+<li>frenos <a href="mailto:frenos@users.noreply.github.com"
+class="email">frenos@users.noreply.github.com</a></li>
+<li>ssaqua <a href="mailto:ssaqua@users.noreply.github.com"
+class="email">ssaqua@users.noreply.github.com</a></li>
+<li>xnaas <a href="mailto:me@xnaas.info"
+class="email">me@xnaas.info</a></li>
+<li>Frantisek Fuka <a href="mailto:fuka@fuxoft.cz"
+class="email">fuka@fuxoft.cz</a></li>
+<li>Paul Kohout <a href="mailto:pauljkohout@yahoo.com"
+class="email">pauljkohout@yahoo.com</a></li>
+<li>dcpu <a href="mailto:43330287+dcpu@users.noreply.github.com"
+class="email">43330287+dcpu@users.noreply.github.com</a></li>
+<li>jackyzy823 <a href="mailto:jackyzy823@gmail.com"
+class="email">jackyzy823@gmail.com</a></li>
+<li>David Haguenauer <a href="mailto:ml@kurokatta.org"
+class="email">ml@kurokatta.org</a></li>
+<li>teresy <a href="mailto:hi.teresy@gmail.com"
+class="email">hi.teresy@gmail.com</a></li>
+<li>buergi <a href="mailto:patbuergi@gmx.de"
+class="email">patbuergi@gmx.de</a></li>
+<li>Florian Gamboeck <a href="mailto:mail@floga.de"
+class="email">mail@floga.de</a></li>
+<li>Ralf Hemberger <a
+href="mailto:10364191+rhemberger@users.noreply.github.com"
+class="email">10364191+rhemberger@users.noreply.github.com</a></li>
+<li>Scott Edlund <a href="mailto:sedlund@users.noreply.github.com"
+class="email">sedlund@users.noreply.github.com</a></li>
+<li>Erik Swanson <a href="mailto:erik@retailnext.net"
+class="email">erik@retailnext.net</a></li>
+<li>Jake Coggiano <a href="mailto:jake@stripe.com"
+class="email">jake@stripe.com</a></li>
+<li>brused27 <a href="mailto:brused27@noemailaddress"
+class="email">brused27@noemailaddress</a></li>
+<li>Peter Kaminski <a href="mailto:kaminski@istori.com"
+class="email">kaminski@istori.com</a></li>
+<li>Henry Ptasinski <a href="mailto:henry@logout.com"
+class="email">henry@logout.com</a></li>
+<li>Alexander <a href="mailto:kharkovalexander@gmail.com"
+class="email">kharkovalexander@gmail.com</a></li>
+<li>Garry McNulty <a href="mailto:garrmcnu@gmail.com"
+class="email">garrmcnu@gmail.com</a></li>
+<li>Mathieu Carbou <a href="mailto:mathieu.carbou@gmail.com"
+class="email">mathieu.carbou@gmail.com</a></li>
+<li>Mark Otway <a href="mailto:mark@otway.com"
+class="email">mark@otway.com</a></li>
+<li>William Cocker <a
+href="mailto:37018962+WilliamCocker@users.noreply.github.com"
+class="email">37018962+WilliamCocker@users.noreply.github.com</a></li>
+<li>François Leurent <a href="mailto:131.js@cloudyks.org"
+class="email">131.js@cloudyks.org</a></li>
+<li>Arkadius Stefanski <a href="mailto:arkste@gmail.com"
+class="email">arkste@gmail.com</a></li>
+<li>Jay <a href="mailto:dev@jaygoel.com"
+class="email">dev@jaygoel.com</a></li>
+<li>andrea rota <a href="mailto:a@xelera.eu"
+class="email">a@xelera.eu</a></li>
+<li>nicolov <a href="mailto:nicolov@users.noreply.github.com"
+class="email">nicolov@users.noreply.github.com</a></li>
+<li>Matt Joiner <a href="mailto:anacrolix@gmail.com"
+class="email">anacrolix@gmail.com</a></li>
+<li>Dario Guzik <a href="mailto:dario@guzik.com.ar"
+class="email">dario@guzik.com.ar</a></li>
+<li>qip <a href="mailto:qip@users.noreply.github.com"
+class="email">qip@users.noreply.github.com</a></li>
+<li>yair@unicorn <a href="mailto:yair@unicorn"
+class="email">yair@unicorn</a></li>
+<li>Matt Robinson <a href="mailto:brimstone@the.narro.ws"
+class="email">brimstone@the.narro.ws</a></li>
+<li>kayrus <a href="mailto:kay.diam@gmail.com"
+class="email">kay.diam@gmail.com</a></li>
+<li>Rémy Léone <a href="mailto:remy.leone@gmail.com"
+class="email">remy.leone@gmail.com</a></li>
+<li>Wojciech Smigielski <a
+href="mailto:wojciech.hieronim.smigielski@gmail.com"
+class="email">wojciech.hieronim.smigielski@gmail.com</a></li>
+<li>weetmuts <a href="mailto:oehrstroem@gmail.com"
+class="email">oehrstroem@gmail.com</a></li>
+<li>Jonathan <a href="mailto:vanillajonathan@users.noreply.github.com"
+class="email">vanillajonathan@users.noreply.github.com</a></li>
+<li>James Carpenter <a href="mailto:orbsmiv@users.noreply.github.com"
+class="email">orbsmiv@users.noreply.github.com</a></li>
+<li>Vince <a href="mailto:vince0villamora@gmail.com"
+class="email">vince0villamora@gmail.com</a></li>
+<li>Nestar47 <a href="mailto:47841759+Nestar47@users.noreply.github.com"
+class="email">47841759+Nestar47@users.noreply.github.com</a></li>
+<li>Six <a href="mailto:brbsix@gmail.com"
+class="email">brbsix@gmail.com</a></li>
+<li>Alexandru Bumbacea <a href="mailto:alexandru.bumbacea@booking.com"
+class="email">alexandru.bumbacea@booking.com</a></li>
+<li>calisro <a href="mailto:robert.calistri@gmail.com"
+class="email">robert.calistri@gmail.com</a></li>
+<li>Dr.Rx <a href="mailto:david.rey@nventive.com"
+class="email">david.rey@nventive.com</a></li>
+<li>marcintustin <a href="mailto:marcintustin@users.noreply.github.com"
+class="email">marcintustin@users.noreply.github.com</a></li>
+<li>jaKa Močnik <a href="mailto:jaka@koofr.net"
+class="email">jaka@koofr.net</a></li>
+<li>Fionera <a href="mailto:fionera@fionera.de"
+class="email">fionera@fionera.de</a></li>
+<li>Dan Walters <a href="mailto:dan@walters.io"
+class="email">dan@walters.io</a></li>
+<li>Danil Semelenov <a href="mailto:sgtpep@users.noreply.github.com"
+class="email">sgtpep@users.noreply.github.com</a></li>
+<li>xopez <a href="mailto:28950736+xopez@users.noreply.github.com"
+class="email">28950736+xopez@users.noreply.github.com</a></li>
+<li>Ben Boeckel <a href="mailto:mathstuf@gmail.com"
+class="email">mathstuf@gmail.com</a></li>
+<li>Manu <a href="mailto:manu@snapdragon.cc"
+class="email">manu@snapdragon.cc</a></li>
+<li>Kyle E. Mitchell <a href="mailto:kyle@kemitchell.com"
+class="email">kyle@kemitchell.com</a></li>
+<li>Gary Kim <a href="mailto:gary@garykim.dev"
+class="email">gary@garykim.dev</a></li>
+<li>Jon <a href="mailto:jonathn@github.com"
+class="email">jonathn@github.com</a></li>
+<li>Jeff Quinn <a href="mailto:jeffrey.quinn@bluevoyant.com"
+class="email">jeffrey.quinn@bluevoyant.com</a></li>
+<li>Peter Berbec <a href="mailto:peter@berbec.com"
+class="email">peter@berbec.com</a></li>
+<li>didil <a href="mailto:1284255+didil@users.noreply.github.com"
+class="email">1284255+didil@users.noreply.github.com</a></li>
+<li>id01 <a href="mailto:gaviniboom@gmail.com"
+class="email">gaviniboom@gmail.com</a></li>
+<li>Robert Marko <a href="mailto:robimarko@gmail.com"
+class="email">robimarko@gmail.com</a></li>
+<li>Philip Harvey <a
+href="mailto:32467456+pharveybattelle@users.noreply.github.com"
+class="email">32467456+pharveybattelle@users.noreply.github.com</a></li>
+<li>JorisE <a href="mailto:JorisE@users.noreply.github.com"
+class="email">JorisE@users.noreply.github.com</a></li>
+<li>garry415 <a href="mailto:garry.415@gmail.com"
+class="email">garry.415@gmail.com</a></li>
+<li>forgems <a href="mailto:forgems@gmail.com"
+class="email">forgems@gmail.com</a></li>
+<li>Florian Apolloner <a href="mailto:florian@apolloner.eu"
+class="email">florian@apolloner.eu</a></li>
+<li>Aleksandar Janković <a href="mailto:office@ajankovic.com"
+class="email">office@ajankovic.com</a> <a
+href="mailto:ajankovic@users.noreply.github.com"
+class="email">ajankovic@users.noreply.github.com</a></li>
+<li>Maran <a href="mailto:maran@protonmail.com"
+class="email">maran@protonmail.com</a></li>
+<li>nguyenhuuluan434 <a href="mailto:nguyenhuuluan434@gmail.com"
+class="email">nguyenhuuluan434@gmail.com</a></li>
+<li>Laura Hausmann <a href="mailto:zotan@zotan.pw"
+class="email">zotan@zotan.pw</a> <a href="mailto:laura@hausmann.dev"
+class="email">laura@hausmann.dev</a></li>
+<li>yparitcher <a href="mailto:y@paritcher.com"
+class="email">y@paritcher.com</a></li>
+<li>AbelThar <a href="mailto:abela.tharen@gmail.com"
+class="email">abela.tharen@gmail.com</a></li>
+<li>Matti Niemenmaa <a href="mailto:matti.niemenmaa+git@iki.fi"
+class="email">matti.niemenmaa+git@iki.fi</a></li>
+<li>Russell Davis <a href="mailto:russelldavis@users.noreply.github.com"
+class="email">russelldavis@users.noreply.github.com</a></li>
+<li>Yi FU <a href="mailto:yi.fu@tink.se"
+class="email">yi.fu@tink.se</a></li>
+<li>Paul Millar <a href="mailto:paul.millar@desy.de"
+class="email">paul.millar@desy.de</a></li>
+<li>justinalin <a href="mailto:justinalin@qnap.com"
+class="email">justinalin@qnap.com</a></li>
+<li>EliEron <a href="mailto:subanimehd@gmail.com"
+class="email">subanimehd@gmail.com</a></li>
+<li>justina777 <a href="mailto:chiahuei.lin@gmail.com"
+class="email">chiahuei.lin@gmail.com</a></li>
+<li>Chaitanya Bankanhal <a href="mailto:bchaitanya15@gmail.com"
+class="email">bchaitanya15@gmail.com</a></li>
+<li>Michał Matczuk <a href="mailto:michal@scylladb.com"
+class="email">michal@scylladb.com</a></li>
+<li>Macavirus <a href="mailto:macavirus@zoho.com"
+class="email">macavirus@zoho.com</a></li>
+<li>Abhinav Sharma <a href="mailto:abhi18av@outlook.com"
+class="email">abhi18av@outlook.com</a></li>
+<li>ginvine <a href="mailto:34869051+ginvine@users.noreply.github.com"
+class="email">34869051+ginvine@users.noreply.github.com</a></li>
+<li>Patrick Wang <a href="mailto:mail6543210@yahoo.com.tw"
+class="email">mail6543210@yahoo.com.tw</a></li>
+<li>Cenk Alti <a href="mailto:cenkalti@gmail.com"
+class="email">cenkalti@gmail.com</a></li>
+<li>Andreas Chlupka <a href="mailto:andy@chlupka.com"
+class="email">andy@chlupka.com</a></li>
+<li>Alfonso Montero <a href="mailto:amontero@tinet.org"
+class="email">amontero@tinet.org</a></li>
+<li>Ivan Andreev <a href="mailto:ivandeex@gmail.com"
+class="email">ivandeex@gmail.com</a></li>
+<li>David Baumgold <a href="mailto:david@davidbaumgold.com"
+class="email">david@davidbaumgold.com</a></li>
+<li>Lars Lehtonen <a href="mailto:lars.lehtonen@gmail.com"
+class="email">lars.lehtonen@gmail.com</a></li>
+<li>Matei David <a href="mailto:matei.david@gmail.com"
+class="email">matei.david@gmail.com</a></li>
+<li>David <a href="mailto:david.bramwell@endemolshine.com"
+class="email">david.bramwell@endemolshine.com</a></li>
+<li>Anthony Rusdi <a
+href="mailto:33247310+antrusd@users.noreply.github.com"
+class="email">33247310+antrusd@users.noreply.github.com</a></li>
+<li>Richard Patel <a href="mailto:me@terorie.dev"
+class="email">me@terorie.dev</a></li>
+<li>庄天翼 <a href="mailto:zty0826@gmail.com"
+class="email">zty0826@gmail.com</a></li>
+<li>SwitchJS <a href="mailto:dev@switchjs.com"
+class="email">dev@switchjs.com</a></li>
+<li>Raphael <a href="mailto:PowershellNinja@users.noreply.github.com"
+class="email">PowershellNinja@users.noreply.github.com</a></li>
+<li>Sezal Agrawal <a href="mailto:sezalagrawal@gmail.com"
+class="email">sezalagrawal@gmail.com</a></li>
+<li>Tyler <a href="mailto:TylerNakamura@users.noreply.github.com"
+class="email">TylerNakamura@users.noreply.github.com</a></li>
+<li>Brett Dutro <a href="mailto:brett.dutro@gmail.com"
+class="email">brett.dutro@gmail.com</a></li>
+<li>Vighnesh SK <a href="mailto:booterror99@gmail.com"
+class="email">booterror99@gmail.com</a></li>
+<li>Arijit Biswas <a href="mailto:dibbyo456@gmail.com"
+class="email">dibbyo456@gmail.com</a></li>
+<li>Michele Caci <a href="mailto:michele.caci@gmail.com"
+class="email">michele.caci@gmail.com</a></li>
+<li>AlexandrBoltris <a href="mailto:ua2fgb@gmail.com"
+class="email">ua2fgb@gmail.com</a></li>
+<li>Bryce Larson <a href="mailto:blarson@saltstack.com"
+class="email">blarson@saltstack.com</a></li>
+<li>Carlos Ferreyra <a href="mailto:crypticmind@gmail.com"
+class="email">crypticmind@gmail.com</a></li>
+<li>Saksham Khanna <a href="mailto:sakshamkhanna@outlook.com"
+class="email">sakshamkhanna@outlook.com</a></li>
+<li>dausruddin <a
+href="mailto:5763466+dausruddin@users.noreply.github.com"
+class="email">5763466+dausruddin@users.noreply.github.com</a></li>
+<li>zero-24 <a href="mailto:zero-24@users.noreply.github.com"
+class="email">zero-24@users.noreply.github.com</a></li>
+<li>Xiaoxing Ye <a href="mailto:ye@xiaoxing.us"
+class="email">ye@xiaoxing.us</a></li>
+<li>Barry Muldrey <a href="mailto:barry@muldrey.net"
+class="email">barry@muldrey.net</a></li>
+<li>Sebastian Brandt <a href="mailto:sebastian.brandt@friday.de"
+class="email">sebastian.brandt@friday.de</a></li>
+<li>Marco Molteni <a href="mailto:marco.molteni@mailbox.org"
+class="email">marco.molteni@mailbox.org</a></li>
+<li>Ankur Gupta <a
+href="mailto:7876747+ankur0493@users.noreply.github.com"
+class="email">7876747+ankur0493@users.noreply.github.com</a></li>
+<li>Maciej Zimnoch <a href="mailto:maciej@scylladb.com"
+class="email">maciej@scylladb.com</a></li>
+<li>anuar45 <a href="mailto:serdaliyev.anuar@gmail.com"
+class="email">serdaliyev.anuar@gmail.com</a></li>
+<li>Fernando <a href="mailto:ferferga@users.noreply.github.com"
+class="email">ferferga@users.noreply.github.com</a></li>
+<li>David Cole <a href="mailto:david.cole@sohonet.com"
+class="email">david.cole@sohonet.com</a></li>
+<li>Wei He <a href="mailto:git@weispot.com"
+class="email">git@weispot.com</a></li>
+<li>Outvi V <a href="mailto:19144373+outloudvi@users.noreply.github.com"
+class="email">19144373+outloudvi@users.noreply.github.com</a></li>
+<li>Thomas Kriechbaumer <a href="mailto:thomas@kriechbaumer.name"
+class="email">thomas@kriechbaumer.name</a></li>
+<li>Tennix <a href="mailto:tennix@users.noreply.github.com"
+class="email">tennix@users.noreply.github.com</a></li>
+<li>Ole Schütt <a href="mailto:ole@schuett.name"
+class="email">ole@schuett.name</a></li>
+<li>Kuang-che Wu <a href="mailto:kcwu@csie.org"
+class="email">kcwu@csie.org</a></li>
+<li>Thomas Eales <a href="mailto:wingsuit@users.noreply.github.com"
+class="email">wingsuit@users.noreply.github.com</a></li>
+<li>Paul Tinsley <a href="mailto:paul.tinsley@vitalsource.com"
+class="email">paul.tinsley@vitalsource.com</a></li>
+<li>Felix Hungenberg <a href="mailto:git@shiftgeist.com"
+class="email">git@shiftgeist.com</a></li>
+<li>Benjamin Richter <a href="mailto:github@dev.telepath.de"
+class="email">github@dev.telepath.de</a></li>
+<li>landall <a href="mailto:cst_zf@qq.com"
+class="email">cst_zf@qq.com</a></li>
+<li>thestigma <a href="mailto:thestigma@gmail.com"
+class="email">thestigma@gmail.com</a></li>
+<li>jtagcat <a href="mailto:38327267+jtagcat@users.noreply.github.com"
+class="email">38327267+jtagcat@users.noreply.github.com</a></li>
+<li>Damon Permezel <a href="mailto:permezel@me.com"
+class="email">permezel@me.com</a></li>
+<li>boosh <a href="mailto:boosh@users.noreply.github.com"
+class="email">boosh@users.noreply.github.com</a></li>
+<li>unbelauscht <a
+href="mailto:58393353+unbelauscht@users.noreply.github.com"
+class="email">58393353+unbelauscht@users.noreply.github.com</a></li>
+<li>Motonori IWAMURO <a href="mailto:vmi@nifty.com"
+class="email">vmi@nifty.com</a></li>
+<li>Benjapol Worakan <a href="mailto:benwrk@live.com"
+class="email">benwrk@live.com</a></li>
+<li>Dave Koston <a href="mailto:dave.koston@stackpath.com"
+class="email">dave.koston@stackpath.com</a></li>
+<li>Durval Menezes <a
+href="mailto:DurvalMenezes@users.noreply.github.com"
+class="email">DurvalMenezes@users.noreply.github.com</a></li>
+<li>Tim Gallant <a href="mailto:me@timgallant.us"
+class="email">me@timgallant.us</a></li>
+<li>Frederick Zhang <a href="mailto:frederick888@tsundere.moe"
+class="email">frederick888@tsundere.moe</a></li>
+<li>valery1707 <a href="mailto:valery1707@gmail.com"
+class="email">valery1707@gmail.com</a></li>
+<li>Yves G <a href="mailto:theYinYeti@yalis.fr"
+class="email">theYinYeti@yalis.fr</a></li>
+<li>Shing Kit Chan <a href="mailto:chanshingkit@gmail.com"
+class="email">chanshingkit@gmail.com</a></li>
+<li>Franklyn Tackitt <a href="mailto:franklyn@tackitt.net"
+class="email">franklyn@tackitt.net</a></li>
+<li>Robert-André Mauchin <a href="mailto:zebob.m@gmail.com"
+class="email">zebob.m@gmail.com</a></li>
+<li>evileye <a href="mailto:48332831+ibiruai@users.noreply.github.com"
+class="email">48332831+ibiruai@users.noreply.github.com</a></li>
+<li>Joachim Brandon LeBlanc <a href="mailto:brandon@leblanc.codes"
+class="email">brandon@leblanc.codes</a></li>
+<li>Patryk Jakuszew <a href="mailto:patryk.jakuszew@gmail.com"
+class="email">patryk.jakuszew@gmail.com</a></li>
+<li>fishbullet <a href="mailto:shindu666@gmail.com"
+class="email">shindu666@gmail.com</a></li>
 <li>greatroar &lt;@&gt;</li>
-<li>Bernd Schoolmann <a href="mailto:mail@quexten.com" class="email">mail@quexten.com</a></li>
-<li>Elan Ruusamäe <a href="mailto:glen@pld-linux.org" class="email">glen@pld-linux.org</a></li>
-<li>Max Sum <a href="mailto:max@lolyculture.com" class="email">max@lolyculture.com</a></li>
-<li>Mark Spieth <a href="mailto:mspieth@users.noreply.github.com" class="email">mspieth@users.noreply.github.com</a></li>
-<li>harry <a href="mailto:me@harry.plus" class="email">me@harry.plus</a></li>
-<li>Samantha McVey <a href="mailto:samantham@posteo.net" class="email">samantham@posteo.net</a></li>
-<li>Jack Anderson <a href="mailto:jack.anderson@metaswitch.com" class="email">jack.anderson@metaswitch.com</a></li>
-<li>Michael G <a href="mailto:draget@speciesm.net" class="email">draget@speciesm.net</a></li>
-<li>Brandon Philips <a href="mailto:brandon@ifup.org" class="email">brandon@ifup.org</a></li>
-<li>Daven <a href="mailto:dooven@users.noreply.github.com" class="email">dooven@users.noreply.github.com</a></li>
-<li>Martin Stone <a href="mailto:martin@d7415.co.uk" class="email">martin@d7415.co.uk</a></li>
-<li>David Bramwell <a href="mailto:13053834+dbramwell@users.noreply.github.com" class="email">13053834+dbramwell@users.noreply.github.com</a></li>
-<li>Sunil Patra <a href="mailto:snl_su@live.com" class="email">snl_su@live.com</a></li>
-<li>Adam Stroud <a href="mailto:adam.stroud@gmail.com" class="email">adam.stroud@gmail.com</a></li>
-<li>Kush <a href="mailto:kushsharma@users.noreply.github.com" class="email">kushsharma@users.noreply.github.com</a></li>
-<li>Matan Rosenberg <a href="mailto:matan129@gmail.com" class="email">matan129@gmail.com</a></li>
-<li>gitch1 <a href="mailto:63495046+gitch1@users.noreply.github.com" class="email">63495046+gitch1@users.noreply.github.com</a></li>
-<li>ElonH <a href="mailto:elonhhuang@gmail.com" class="email">elonhhuang@gmail.com</a></li>
-<li>Fred <a href="mailto:fred@creativeprojects.tech" class="email">fred@creativeprojects.tech</a></li>
-<li>Sébastien Gross <a href="mailto:renard@users.noreply.github.com" class="email">renard@users.noreply.github.com</a></li>
-<li>Maxime Suret <a href="mailto:11944422+msuret@users.noreply.github.com" class="email">11944422+msuret@users.noreply.github.com</a></li>
-<li>Caleb Case <a href="mailto:caleb@storj.io" class="email">caleb@storj.io</a> <a href="mailto:calebcase@gmail.com" class="email">calebcase@gmail.com</a></li>
-<li>Ben Zenker <a href="mailto:imbenzenker@gmail.com" class="email">imbenzenker@gmail.com</a></li>
-<li>Martin Michlmayr <a href="mailto:tbm@cyrius.com" class="email">tbm@cyrius.com</a></li>
-<li>Brandon McNama <a href="mailto:bmcnama@pagerduty.com" class="email">bmcnama@pagerduty.com</a></li>
-<li>Daniel Slyman <a href="mailto:github@skylayer.eu" class="email">github@skylayer.eu</a></li>
-<li>Alex Guerrero <a href="mailto:guerrero@users.noreply.github.com" class="email">guerrero@users.noreply.github.com</a></li>
-<li>Matteo Pietro Dazzi <a href="mailto:matteopietro.dazzi@gft.com" class="email">matteopietro.dazzi@gft.com</a></li>
-<li>edwardxml <a href="mailto:56691903+edwardxml@users.noreply.github.com" class="email">56691903+edwardxml@users.noreply.github.com</a></li>
-<li>Roman Kredentser <a href="mailto:shareed2k@gmail.com" class="email">shareed2k@gmail.com</a></li>
-<li>Kamil Trzciński <a href="mailto:ayufan@ayufan.eu" class="email">ayufan@ayufan.eu</a></li>
-<li>Zac Rubin <a href="mailto:z-0@users.noreply.github.com" class="email">z-0@users.noreply.github.com</a></li>
+<li>Bernd Schoolmann <a href="mailto:mail@quexten.com"
+class="email">mail@quexten.com</a></li>
+<li>Elan Ruusamäe <a href="mailto:glen@pld-linux.org"
+class="email">glen@pld-linux.org</a></li>
+<li>Max Sum <a href="mailto:max@lolyculture.com"
+class="email">max@lolyculture.com</a></li>
+<li>Mark Spieth <a href="mailto:mspieth@users.noreply.github.com"
+class="email">mspieth@users.noreply.github.com</a></li>
+<li>harry <a href="mailto:me@harry.plus"
+class="email">me@harry.plus</a></li>
+<li>Samantha McVey <a href="mailto:samantham@posteo.net"
+class="email">samantham@posteo.net</a></li>
+<li>Jack Anderson <a href="mailto:jack.anderson@metaswitch.com"
+class="email">jack.anderson@metaswitch.com</a></li>
+<li>Michael G <a href="mailto:draget@speciesm.net"
+class="email">draget@speciesm.net</a></li>
+<li>Brandon Philips <a href="mailto:brandon@ifup.org"
+class="email">brandon@ifup.org</a></li>
+<li>Daven <a href="mailto:dooven@users.noreply.github.com"
+class="email">dooven@users.noreply.github.com</a></li>
+<li>Martin Stone <a href="mailto:martin@d7415.co.uk"
+class="email">martin@d7415.co.uk</a></li>
+<li>David Bramwell <a
+href="mailto:13053834+dbramwell@users.noreply.github.com"
+class="email">13053834+dbramwell@users.noreply.github.com</a></li>
+<li>Sunil Patra <a href="mailto:snl_su@live.com"
+class="email">snl_su@live.com</a></li>
+<li>Adam Stroud <a href="mailto:adam.stroud@gmail.com"
+class="email">adam.stroud@gmail.com</a></li>
+<li>Kush <a href="mailto:kushsharma@users.noreply.github.com"
+class="email">kushsharma@users.noreply.github.com</a></li>
+<li>Matan Rosenberg <a href="mailto:matan129@gmail.com"
+class="email">matan129@gmail.com</a></li>
+<li>gitch1 <a href="mailto:63495046+gitch1@users.noreply.github.com"
+class="email">63495046+gitch1@users.noreply.github.com</a></li>
+<li>ElonH <a href="mailto:elonhhuang@gmail.com"
+class="email">elonhhuang@gmail.com</a></li>
+<li>Fred <a href="mailto:fred@creativeprojects.tech"
+class="email">fred@creativeprojects.tech</a></li>
+<li>Sébastien Gross <a href="mailto:renard@users.noreply.github.com"
+class="email">renard@users.noreply.github.com</a></li>
+<li>Maxime Suret <a
+href="mailto:11944422+msuret@users.noreply.github.com"
+class="email">11944422+msuret@users.noreply.github.com</a></li>
+<li>Caleb Case <a href="mailto:caleb@storj.io"
+class="email">caleb@storj.io</a> <a href="mailto:calebcase@gmail.com"
+class="email">calebcase@gmail.com</a></li>
+<li>Ben Zenker <a href="mailto:imbenzenker@gmail.com"
+class="email">imbenzenker@gmail.com</a></li>
+<li>Martin Michlmayr <a href="mailto:tbm@cyrius.com"
+class="email">tbm@cyrius.com</a></li>
+<li>Brandon McNama <a href="mailto:bmcnama@pagerduty.com"
+class="email">bmcnama@pagerduty.com</a></li>
+<li>Daniel Slyman <a href="mailto:github@skylayer.eu"
+class="email">github@skylayer.eu</a></li>
+<li>Alex Guerrero <a href="mailto:guerrero@users.noreply.github.com"
+class="email">guerrero@users.noreply.github.com</a></li>
+<li>Matteo Pietro Dazzi <a href="mailto:matteopietro.dazzi@gft.com"
+class="email">matteopietro.dazzi@gft.com</a></li>
+<li>edwardxml <a
+href="mailto:56691903+edwardxml@users.noreply.github.com"
+class="email">56691903+edwardxml@users.noreply.github.com</a></li>
+<li>Roman Kredentser <a href="mailto:shareed2k@gmail.com"
+class="email">shareed2k@gmail.com</a></li>
+<li>Kamil Trzciński <a href="mailto:ayufan@ayufan.eu"
+class="email">ayufan@ayufan.eu</a></li>
+<li>Zac Rubin <a href="mailto:z-0@users.noreply.github.com"
+class="email">z-0@users.noreply.github.com</a></li>
 <li>Vincent Feltz</li>
-<li>Heiko Bornholdt <a href="mailto:bornholdt@informatik.uni-hamburg.de" class="email">bornholdt@informatik.uni-hamburg.de</a></li>
-<li>Matteo Pietro Dazzi <a href="mailto:matteopietro.dazzi@gmail.com" class="email">matteopietro.dazzi@gmail.com</a></li>
-<li>jtagcat <a href="mailto:gitlab@c7.ee" class="email">gitlab@c7.ee</a></li>
-<li>Petri Salminen <a href="mailto:petri@salminen.dev" class="email">petri@salminen.dev</a></li>
-<li>Tim Burke <a href="mailto:tim.burke@gmail.com" class="email">tim.burke@gmail.com</a></li>
-<li>Kai Lüke <a href="mailto:kai@kinvolk.io" class="email">kai@kinvolk.io</a></li>
-<li>Garrett Squire <a href="mailto:github@garrettsquire.com" class="email">github@garrettsquire.com</a></li>
-<li>Evan Harris <a href="mailto:eharris@puremagic.com" class="email">eharris@puremagic.com</a></li>
-<li>Kevin <a href="mailto:keyam@microsoft.com" class="email">keyam@microsoft.com</a></li>
-<li>Morten Linderud <a href="mailto:morten@linderud.pw" class="email">morten@linderud.pw</a></li>
-<li>Dmitry Ustalov <a href="mailto:dmitry.ustalov@gmail.com" class="email">dmitry.ustalov@gmail.com</a></li>
-<li>Jack <a href="mailto:196648+jdeng@users.noreply.github.com" class="email">196648+jdeng@users.noreply.github.com</a></li>
-<li>kcris <a href="mailto:cristian.tarsoaga@gmail.com" class="email">cristian.tarsoaga@gmail.com</a></li>
-<li>tyhuber1 <a href="mailto:68970760+tyhuber1@users.noreply.github.com" class="email">68970760+tyhuber1@users.noreply.github.com</a></li>
-<li>David Ibarra <a href="mailto:david.ibarra@realty.com" class="email">david.ibarra@realty.com</a></li>
-<li>Tim Gallant <a href="mailto:tim@lilt.com" class="email">tim@lilt.com</a></li>
-<li>Kaloyan Raev <a href="mailto:kaloyan@storj.io" class="email">kaloyan@storj.io</a></li>
-<li>Jay McEntire <a href="mailto:jay.mcentire@gmail.com" class="email">jay.mcentire@gmail.com</a></li>
-<li>Leo Luan <a href="mailto:leoluan@us.ibm.com" class="email">leoluan@us.ibm.com</a></li>
-<li>aus <a href="mailto:549081+aus@users.noreply.github.com" class="email">549081+aus@users.noreply.github.com</a></li>
-<li>Aaron Gokaslan <a href="mailto:agokaslan@fb.com" class="email">agokaslan@fb.com</a></li>
-<li>Egor Margineanu <a href="mailto:egmar@users.noreply.github.com" class="email">egmar@users.noreply.github.com</a></li>
-<li>Lucas Kanashiro <a href="mailto:lucas.kanashiro@canonical.com" class="email">lucas.kanashiro@canonical.com</a></li>
-<li>WarpedPixel <a href="mailto:WarpedPixel@users.noreply.github.com" class="email">WarpedPixel@users.noreply.github.com</a></li>
-<li>Sam Edwards <a href="mailto:sam@samedwards.ca" class="email">sam@samedwards.ca</a></li>
-<li>wjielai <a href="mailto:gouki0123@gmail.com" class="email">gouki0123@gmail.com</a></li>
-<li>Muffin King <a href="mailto:jinxz_k@live.com" class="email">jinxz_k@live.com</a></li>
-<li>Christopher Stewart <a href="mailto:6573710+1f47a@users.noreply.github.com" class="email">6573710+1f47a@users.noreply.github.com</a></li>
-<li>Russell Cattelan <a href="mailto:cattelan@digitalelves.com" class="email">cattelan@digitalelves.com</a></li>
-<li>gyutw <a href="mailto:30371241+gyutw@users.noreply.github.com" class="email">30371241+gyutw@users.noreply.github.com</a></li>
-<li>Hekmon <a href="mailto:edouardhur@gmail.com" class="email">edouardhur@gmail.com</a></li>
-<li>LaSombra <a href="mailto:lasombra@users.noreply.github.com" class="email">lasombra@users.noreply.github.com</a></li>
-<li>Dov Murik <a href="mailto:dov.murik@gmail.com" class="email">dov.murik@gmail.com</a></li>
-<li>Ameer Dawood <a href="mailto:ameer1234567890@gmail.com" class="email">ameer1234567890@gmail.com</a></li>
-<li>Dan Hipschman <a href="mailto:dan.hipschman@opendoor.com" class="email">dan.hipschman@opendoor.com</a></li>
-<li>Josh Soref <a href="mailto:jsoref@users.noreply.github.com" class="email">jsoref@users.noreply.github.com</a></li>
-<li>David <a href="mailto:david@staron.nl" class="email">david@staron.nl</a></li>
-<li>Ingo <a href="mailto:ingo@hoffmann.cx" class="email">ingo@hoffmann.cx</a></li>
-<li>Adam Plánský <a href="mailto:adamplansky@users.noreply.github.com" class="email">adamplansky@users.noreply.github.com</a> <a href="mailto:adamplansky@gmail.com" class="email">adamplansky@gmail.com</a></li>
-<li>Manish Gupta <a href="mailto:manishgupta.ait@gmail.com" class="email">manishgupta.ait@gmail.com</a></li>
-<li>Deepak Sah <a href="mailto:sah.sslpu@gmail.com" class="email">sah.sslpu@gmail.com</a></li>
-<li>Marcin Zelent <a href="mailto:marcin@zelent.net" class="email">marcin@zelent.net</a></li>
-<li>zhucan <a href="mailto:zhucan.k8s@gmail.com" class="email">zhucan.k8s@gmail.com</a></li>
-<li>James Lim <a href="mailto:james.lim@samsara.com" class="email">james.lim@samsara.com</a></li>
-<li>Laurens Janssen <a href="mailto:BD69BM@insim.biz" class="email">BD69BM@insim.biz</a></li>
-<li>Bob Bagwill <a href="mailto:bobbagwill@gmail.com" class="email">bobbagwill@gmail.com</a></li>
-<li>Nathan Collins <a href="mailto:colli372@msu.edu" class="email">colli372@msu.edu</a></li>
+<li>Heiko Bornholdt <a href="mailto:bornholdt@informatik.uni-hamburg.de"
+class="email">bornholdt@informatik.uni-hamburg.de</a></li>
+<li>Matteo Pietro Dazzi <a href="mailto:matteopietro.dazzi@gmail.com"
+class="email">matteopietro.dazzi@gmail.com</a></li>
+<li>jtagcat <a href="mailto:gitlab@c7.ee"
+class="email">gitlab@c7.ee</a></li>
+<li>Petri Salminen <a href="mailto:petri@salminen.dev"
+class="email">petri@salminen.dev</a></li>
+<li>Tim Burke <a href="mailto:tim.burke@gmail.com"
+class="email">tim.burke@gmail.com</a></li>
+<li>Kai Lüke <a href="mailto:kai@kinvolk.io"
+class="email">kai@kinvolk.io</a></li>
+<li>Garrett Squire <a href="mailto:github@garrettsquire.com"
+class="email">github@garrettsquire.com</a></li>
+<li>Evan Harris <a href="mailto:eharris@puremagic.com"
+class="email">eharris@puremagic.com</a></li>
+<li>Kevin <a href="mailto:keyam@microsoft.com"
+class="email">keyam@microsoft.com</a></li>
+<li>Morten Linderud <a href="mailto:morten@linderud.pw"
+class="email">morten@linderud.pw</a></li>
+<li>Dmitry Ustalov <a href="mailto:dmitry.ustalov@gmail.com"
+class="email">dmitry.ustalov@gmail.com</a></li>
+<li>Jack <a href="mailto:196648+jdeng@users.noreply.github.com"
+class="email">196648+jdeng@users.noreply.github.com</a></li>
+<li>kcris <a href="mailto:cristian.tarsoaga@gmail.com"
+class="email">cristian.tarsoaga@gmail.com</a></li>
+<li>tyhuber1 <a href="mailto:68970760+tyhuber1@users.noreply.github.com"
+class="email">68970760+tyhuber1@users.noreply.github.com</a></li>
+<li>David Ibarra <a href="mailto:david.ibarra@realty.com"
+class="email">david.ibarra@realty.com</a></li>
+<li>Tim Gallant <a href="mailto:tim@lilt.com"
+class="email">tim@lilt.com</a></li>
+<li>Kaloyan Raev <a href="mailto:kaloyan@storj.io"
+class="email">kaloyan@storj.io</a></li>
+<li>Jay McEntire <a href="mailto:jay.mcentire@gmail.com"
+class="email">jay.mcentire@gmail.com</a></li>
+<li>Leo Luan <a href="mailto:leoluan@us.ibm.com"
+class="email">leoluan@us.ibm.com</a></li>
+<li>aus <a href="mailto:549081+aus@users.noreply.github.com"
+class="email">549081+aus@users.noreply.github.com</a></li>
+<li>Aaron Gokaslan <a href="mailto:agokaslan@fb.com"
+class="email">agokaslan@fb.com</a></li>
+<li>Egor Margineanu <a href="mailto:egmar@users.noreply.github.com"
+class="email">egmar@users.noreply.github.com</a></li>
+<li>Lucas Kanashiro <a href="mailto:lucas.kanashiro@canonical.com"
+class="email">lucas.kanashiro@canonical.com</a></li>
+<li>WarpedPixel <a href="mailto:WarpedPixel@users.noreply.github.com"
+class="email">WarpedPixel@users.noreply.github.com</a></li>
+<li>Sam Edwards <a href="mailto:sam@samedwards.ca"
+class="email">sam@samedwards.ca</a></li>
+<li>wjielai <a href="mailto:gouki0123@gmail.com"
+class="email">gouki0123@gmail.com</a></li>
+<li>Muffin King <a href="mailto:jinxz_k@live.com"
+class="email">jinxz_k@live.com</a></li>
+<li>Christopher Stewart <a
+href="mailto:6573710+1f47a@users.noreply.github.com"
+class="email">6573710+1f47a@users.noreply.github.com</a></li>
+<li>Russell Cattelan <a href="mailto:cattelan@digitalelves.com"
+class="email">cattelan@digitalelves.com</a></li>
+<li>gyutw <a href="mailto:30371241+gyutw@users.noreply.github.com"
+class="email">30371241+gyutw@users.noreply.github.com</a></li>
+<li>Hekmon <a href="mailto:edouardhur@gmail.com"
+class="email">edouardhur@gmail.com</a></li>
+<li>LaSombra <a href="mailto:lasombra@users.noreply.github.com"
+class="email">lasombra@users.noreply.github.com</a></li>
+<li>Dov Murik <a href="mailto:dov.murik@gmail.com"
+class="email">dov.murik@gmail.com</a></li>
+<li>Ameer Dawood <a href="mailto:ameer1234567890@gmail.com"
+class="email">ameer1234567890@gmail.com</a></li>
+<li>Dan Hipschman <a href="mailto:dan.hipschman@opendoor.com"
+class="email">dan.hipschman@opendoor.com</a></li>
+<li>Josh Soref <a href="mailto:jsoref@users.noreply.github.com"
+class="email">jsoref@users.noreply.github.com</a></li>
+<li>David <a href="mailto:david@staron.nl"
+class="email">david@staron.nl</a></li>
+<li>Ingo <a href="mailto:ingo@hoffmann.cx"
+class="email">ingo@hoffmann.cx</a></li>
+<li>Adam Plánský <a href="mailto:adamplansky@users.noreply.github.com"
+class="email">adamplansky@users.noreply.github.com</a> <a
+href="mailto:adamplansky@gmail.com"
+class="email">adamplansky@gmail.com</a></li>
+<li>Manish Gupta <a href="mailto:manishgupta.ait@gmail.com"
+class="email">manishgupta.ait@gmail.com</a></li>
+<li>Deepak Sah <a href="mailto:sah.sslpu@gmail.com"
+class="email">sah.sslpu@gmail.com</a></li>
+<li>Marcin Zelent <a href="mailto:marcin@zelent.net"
+class="email">marcin@zelent.net</a></li>
+<li>zhucan <a href="mailto:zhucan.k8s@gmail.com"
+class="email">zhucan.k8s@gmail.com</a></li>
+<li>James Lim <a href="mailto:james.lim@samsara.com"
+class="email">james.lim@samsara.com</a></li>
+<li>Laurens Janssen <a href="mailto:BD69BM@insim.biz"
+class="email">BD69BM@insim.biz</a></li>
+<li>Bob Bagwill <a href="mailto:bobbagwill@gmail.com"
+class="email">bobbagwill@gmail.com</a></li>
+<li>Nathan Collins <a href="mailto:colli372@msu.edu"
+class="email">colli372@msu.edu</a></li>
 <li>lostheli</li>
-<li>kelv <a href="mailto:kelvin@acks.org" class="email">kelvin@acks.org</a></li>
-<li>Milly <a href="mailto:milly.ca@gmail.com" class="email">milly.ca@gmail.com</a></li>
-<li>gtorelly <a href="mailto:gtorelly@gmail.com" class="email">gtorelly@gmail.com</a></li>
-<li>Brad Ackerman <a href="mailto:brad@facefault.org" class="email">brad@facefault.org</a></li>
-<li>Mitsuo Heijo <a href="mailto:mitsuo.heijo@gmail.com" class="email">mitsuo.heijo@gmail.com</a></li>
-<li>Claudio Bantaloukas <a href="mailto:rockdreamer@gmail.com" class="email">rockdreamer@gmail.com</a></li>
-<li>Benjamin Gustin <a href="mailto:gustin.ben@gmail.com" class="email">gustin.ben@gmail.com</a></li>
-<li>Ingo Weiss <a href="mailto:ingo@redhat.com" class="email">ingo@redhat.com</a></li>
-<li>Kerry Su <a href="mailto:me@sshockwave.net" class="email">me@sshockwave.net</a></li>
-<li>Ilyess Bachiri <a href="mailto:ilyess.bachiri@sonder.com" class="email">ilyess.bachiri@sonder.com</a></li>
-<li>Yury Stankevich <a href="mailto:urykhy@gmail.com" class="email">urykhy@gmail.com</a></li>
-<li>kice <a href="mailto:wslikerqs@gmail.com" class="email">wslikerqs@gmail.com</a></li>
-<li>Denis Neuling <a href="mailto:denisneuling@gmail.com" class="email">denisneuling@gmail.com</a></li>
-<li>Janne Johansson <a href="mailto:icepic.dz@gmail.com" class="email">icepic.dz@gmail.com</a></li>
-<li>Patrik Nordlén <a href="mailto:patriki@gmail.com" class="email">patriki@gmail.com</a></li>
-<li>CokeMine <a href="mailto:aptx4561@gmail.com" class="email">aptx4561@gmail.com</a></li>
-<li>Sơn Trần-Nguyễn <a href="mailto:github@sntran.com" class="email">github@sntran.com</a></li>
-<li>lluuaapp <a href="mailto:266615+lluuaapp@users.noreply.github.com" class="email">266615+lluuaapp@users.noreply.github.com</a></li>
-<li>Zach Kipp <a href="mailto:kipp.zach@gmail.com" class="email">kipp.zach@gmail.com</a></li>
-<li>Riccardo Iaconelli <a href="mailto:riccardo@kde.org" class="email">riccardo@kde.org</a></li>
-<li>Sakuragawa Misty <a href="mailto:gyc990326@gmail.com" class="email">gyc990326@gmail.com</a></li>
-<li>Nicolas Rueff <a href="mailto:nicolas@rueff.fr" class="email">nicolas@rueff.fr</a></li>
-<li>Pau Rodriguez-Estivill <a href="mailto:prodrigestivill@gmail.com" class="email">prodrigestivill@gmail.com</a></li>
-<li>Bob Pusateri <a href="mailto:BobPusateri@users.noreply.github.com" class="email">BobPusateri@users.noreply.github.com</a></li>
-<li>Alex JOST <a href="mailto:25005220+dimejo@users.noreply.github.com" class="email">25005220+dimejo@users.noreply.github.com</a></li>
-<li>Alexey Tabakman <a href="mailto:samosad.ru@gmail.com" class="email">samosad.ru@gmail.com</a></li>
-<li>David Sze <a href="mailto:sze.david@gmail.com" class="email">sze.david@gmail.com</a></li>
-<li>cynthia kwok <a href="mailto:cynthia.m.kwok@gmail.com" class="email">cynthia.m.kwok@gmail.com</a></li>
-<li>Miron Veryanskiy <a href="mailto:MironVeryanskiy@gmail.com" class="email">MironVeryanskiy@gmail.com</a></li>
-<li>K265 <a href="mailto:k.265@qq.com" class="email">k.265@qq.com</a></li>
-<li>Vesnyx <a href="mailto:Vesnyx@users.noreply.github.com" class="email">Vesnyx@users.noreply.github.com</a></li>
-<li>Dmitry Chepurovskiy <a href="mailto:me@dm3ch.net" class="email">me@dm3ch.net</a></li>
-<li>Rauno Ots <a href="mailto:rauno.ots@cgi.com" class="email">rauno.ots@cgi.com</a></li>
-<li>Georg Neugschwandtner <a href="mailto:georg.neugschwandtner@gmx.net" class="email">georg.neugschwandtner@gmx.net</a></li>
-<li>pvalls <a href="mailto:polvallsrue@gmail.com" class="email">polvallsrue@gmail.com</a></li>
-<li>Robert Thomas <a href="mailto:31854736+wolveix@users.noreply.github.com" class="email">31854736+wolveix@users.noreply.github.com</a></li>
-<li>Romeo Kienzler <a href="mailto:romeo.kienzler@gmail.com" class="email">romeo.kienzler@gmail.com</a></li>
-<li>tYYGH <a href="mailto:tYYGH@users.noreply.github.com" class="email">tYYGH@users.noreply.github.com</a></li>
-<li>georne <a href="mailto:77802995+georne@users.noreply.github.com" class="email">77802995+georne@users.noreply.github.com</a></li>
-<li>Maxwell Calman <a href="mailto:mcalman@MacBook-Pro.local" class="email">mcalman@MacBook-Pro.local</a></li>
-<li>Naveen Honest Raj <a href="mailto:naveendurai19@gmail.com" class="email">naveendurai19@gmail.com</a></li>
-<li>Lucas Messenger <a href="mailto:lmesseng@cisco.com" class="email">lmesseng@cisco.com</a></li>
-<li>Manish Kumar <a href="mailto:krmanish260@gmail.com" class="email">krmanish260@gmail.com</a></li>
-<li>x0b <a href="mailto:x0bdev@gmail.com" class="email">x0bdev@gmail.com</a></li>
+<li>kelv <a href="mailto:kelvin@acks.org"
+class="email">kelvin@acks.org</a></li>
+<li>Milly <a href="mailto:milly.ca@gmail.com"
+class="email">milly.ca@gmail.com</a></li>
+<li>gtorelly <a href="mailto:gtorelly@gmail.com"
+class="email">gtorelly@gmail.com</a></li>
+<li>Brad Ackerman <a href="mailto:brad@facefault.org"
+class="email">brad@facefault.org</a></li>
+<li>Mitsuo Heijo <a href="mailto:mitsuo.heijo@gmail.com"
+class="email">mitsuo.heijo@gmail.com</a></li>
+<li>Claudio Bantaloukas <a href="mailto:rockdreamer@gmail.com"
+class="email">rockdreamer@gmail.com</a></li>
+<li>Benjamin Gustin <a href="mailto:gustin.ben@gmail.com"
+class="email">gustin.ben@gmail.com</a></li>
+<li>Ingo Weiss <a href="mailto:ingo@redhat.com"
+class="email">ingo@redhat.com</a></li>
+<li>Kerry Su <a href="mailto:me@sshockwave.net"
+class="email">me@sshockwave.net</a></li>
+<li>Ilyess Bachiri <a href="mailto:ilyess.bachiri@sonder.com"
+class="email">ilyess.bachiri@sonder.com</a></li>
+<li>Yury Stankevich <a href="mailto:urykhy@gmail.com"
+class="email">urykhy@gmail.com</a></li>
+<li>kice <a href="mailto:wslikerqs@gmail.com"
+class="email">wslikerqs@gmail.com</a></li>
+<li>Denis Neuling <a href="mailto:denisneuling@gmail.com"
+class="email">denisneuling@gmail.com</a></li>
+<li>Janne Johansson <a href="mailto:icepic.dz@gmail.com"
+class="email">icepic.dz@gmail.com</a></li>
+<li>Patrik Nordlén <a href="mailto:patriki@gmail.com"
+class="email">patriki@gmail.com</a></li>
+<li>CokeMine <a href="mailto:aptx4561@gmail.com"
+class="email">aptx4561@gmail.com</a></li>
+<li>Sơn Trần-Nguyễn <a href="mailto:github@sntran.com"
+class="email">github@sntran.com</a></li>
+<li>lluuaapp <a href="mailto:266615+lluuaapp@users.noreply.github.com"
+class="email">266615+lluuaapp@users.noreply.github.com</a></li>
+<li>Zach Kipp <a href="mailto:kipp.zach@gmail.com"
+class="email">kipp.zach@gmail.com</a></li>
+<li>Riccardo Iaconelli <a href="mailto:riccardo@kde.org"
+class="email">riccardo@kde.org</a></li>
+<li>Sakuragawa Misty <a href="mailto:gyc990326@gmail.com"
+class="email">gyc990326@gmail.com</a></li>
+<li>Nicolas Rueff <a href="mailto:nicolas@rueff.fr"
+class="email">nicolas@rueff.fr</a></li>
+<li>Pau Rodriguez-Estivill <a href="mailto:prodrigestivill@gmail.com"
+class="email">prodrigestivill@gmail.com</a></li>
+<li>Bob Pusateri <a href="mailto:BobPusateri@users.noreply.github.com"
+class="email">BobPusateri@users.noreply.github.com</a></li>
+<li>Alex JOST <a href="mailto:25005220+dimejo@users.noreply.github.com"
+class="email">25005220+dimejo@users.noreply.github.com</a></li>
+<li>Alexey Tabakman <a href="mailto:samosad.ru@gmail.com"
+class="email">samosad.ru@gmail.com</a></li>
+<li>David Sze <a href="mailto:sze.david@gmail.com"
+class="email">sze.david@gmail.com</a></li>
+<li>cynthia kwok <a href="mailto:cynthia.m.kwok@gmail.com"
+class="email">cynthia.m.kwok@gmail.com</a></li>
+<li>Miron Veryanskiy <a href="mailto:MironVeryanskiy@gmail.com"
+class="email">MironVeryanskiy@gmail.com</a></li>
+<li>K265 <a href="mailto:k.265@qq.com"
+class="email">k.265@qq.com</a></li>
+<li>Vesnyx <a href="mailto:Vesnyx@users.noreply.github.com"
+class="email">Vesnyx@users.noreply.github.com</a></li>
+<li>Dmitry Chepurovskiy <a href="mailto:me@dm3ch.net"
+class="email">me@dm3ch.net</a></li>
+<li>Rauno Ots <a href="mailto:rauno.ots@cgi.com"
+class="email">rauno.ots@cgi.com</a></li>
+<li>Georg Neugschwandtner <a href="mailto:georg.neugschwandtner@gmx.net"
+class="email">georg.neugschwandtner@gmx.net</a></li>
+<li>pvalls <a href="mailto:polvallsrue@gmail.com"
+class="email">polvallsrue@gmail.com</a></li>
+<li>Robert Thomas <a
+href="mailto:31854736+wolveix@users.noreply.github.com"
+class="email">31854736+wolveix@users.noreply.github.com</a></li>
+<li>Romeo Kienzler <a href="mailto:romeo.kienzler@gmail.com"
+class="email">romeo.kienzler@gmail.com</a></li>
+<li>tYYGH <a href="mailto:tYYGH@users.noreply.github.com"
+class="email">tYYGH@users.noreply.github.com</a></li>
+<li>georne <a href="mailto:77802995+georne@users.noreply.github.com"
+class="email">77802995+georne@users.noreply.github.com</a></li>
+<li>Maxwell Calman <a href="mailto:mcalman@MacBook-Pro.local"
+class="email">mcalman@MacBook-Pro.local</a></li>
+<li>Naveen Honest Raj <a href="mailto:naveendurai19@gmail.com"
+class="email">naveendurai19@gmail.com</a></li>
+<li>Lucas Messenger <a href="mailto:lmesseng@cisco.com"
+class="email">lmesseng@cisco.com</a></li>
+<li>Manish Kumar <a href="mailto:krmanish260@gmail.com"
+class="email">krmanish260@gmail.com</a></li>
+<li>x0b <a href="mailto:x0bdev@gmail.com"
+class="email">x0bdev@gmail.com</a></li>
 <li>CERN through the CS3MESH4EOSC Project</li>
-<li>Nick Gaya <a href="mailto:nicholasgaya+github@gmail.com" class="email">nicholasgaya+github@gmail.com</a></li>
-<li>Ashok Gelal <a href="mailto:401055+ashokgelal@users.noreply.github.com" class="email">401055+ashokgelal@users.noreply.github.com</a></li>
-<li>Dominik Mydlil <a href="mailto:dominik.mydlil@outlook.com" class="email">dominik.mydlil@outlook.com</a></li>
-<li>Nazar Mishturak <a href="mailto:nazarmx@gmail.com" class="email">nazarmx@gmail.com</a></li>
-<li>Ansh Mittal <a href="mailto:iamAnshMittal@gmail.com" class="email">iamAnshMittal@gmail.com</a></li>
-<li>noabody <a href="mailto:noabody@yahoo.com" class="email">noabody@yahoo.com</a></li>
-<li>OleFrost <a href="mailto:82263101+olefrost@users.noreply.github.com" class="email">82263101+olefrost@users.noreply.github.com</a></li>
-<li>Kenny Parsons <a href="mailto:kennyparsons93@gmail.com" class="email">kennyparsons93@gmail.com</a></li>
-<li>Jeffrey Tolar <a href="mailto:tolar.jeffrey@gmail.com" class="email">tolar.jeffrey@gmail.com</a></li>
-<li>jtagcat <a href="mailto:git-514635f7@jtag.cat" class="email">git-514635f7@jtag.cat</a></li>
-<li>Tatsuya Noyori <a href="mailto:63089076+public-tatsuya-noyori@users.noreply.github.com" class="email">63089076+public-tatsuya-noyori@users.noreply.github.com</a></li>
-<li>lewisxy <a href="mailto:lewisxy@users.noreply.github.com" class="email">lewisxy@users.noreply.github.com</a></li>
-<li>Nolan Woods <a href="mailto:nolan_w@sfu.ca" class="email">nolan_w@sfu.ca</a></li>
-<li>Gautam Kumar <a href="mailto:25435568+gautamajay52@users.noreply.github.com" class="email">25435568+gautamajay52@users.noreply.github.com</a></li>
-<li>Chris Macklin <a href="mailto:chris.macklin@10xgenomics.com" class="email">chris.macklin@10xgenomics.com</a></li>
-<li>Antoon Prins <a href="mailto:antoon.prins@surfsara.nl" class="email">antoon.prins@surfsara.nl</a></li>
-<li>Alexey Ivanov <a href="mailto:rbtz@dropbox.com" class="email">rbtz@dropbox.com</a></li>
-<li>Serge Pouliquen <a href="mailto:sp31415@free.fr" class="email">sp31415@free.fr</a></li>
-<li>acsfer <a href="mailto:carlos@reendex.com" class="email">carlos@reendex.com</a></li>
-<li>Tom <a href="mailto:tom@tom-fitzhenry.me.uk" class="email">tom@tom-fitzhenry.me.uk</a></li>
-<li>Tyson Moore <a href="mailto:tyson@tyson.me" class="email">tyson@tyson.me</a></li>
-<li>database64128 <a href="mailto:free122448@hotmail.com" class="email">free122448@hotmail.com</a></li>
-<li>Chris Lu <a href="mailto:chrislusf@users.noreply.github.com" class="email">chrislusf@users.noreply.github.com</a></li>
-<li>Reid Buzby <a href="mailto:reid@rethink.software" class="email">reid@rethink.software</a></li>
-<li>darrenrhs <a href="mailto:darrenrhs@gmail.com" class="email">darrenrhs@gmail.com</a></li>
-<li>Florian Penzkofer <a href="mailto:fp@nullptr.de" class="email">fp@nullptr.de</a></li>
-<li>Xuanchen Wu <a href="mailto:117010292@link.cuhk.edu.cn" class="email">117010292@link.cuhk.edu.cn</a></li>
-<li>partev <a href="mailto:petrosyan@gmail.com" class="email">petrosyan@gmail.com</a></li>
-<li>Dmitry Sitnikov <a href="mailto:fo2@inbox.ru" class="email">fo2@inbox.ru</a></li>
-<li>Haochen Tong <a href="mailto:i@hexchain.org" class="email">i@hexchain.org</a></li>
-<li>Michael Hanselmann <a href="mailto:public@hansmi.ch" class="email">public@hansmi.ch</a></li>
-<li>Chuan Zh <a href="mailto:zhchuan7@gmail.com" class="email">zhchuan7@gmail.com</a></li>
-<li>Antoine GIRARD <a href="mailto:antoine.girard@sapk.fr" class="email">antoine.girard@sapk.fr</a></li>
-<li>Justin Winokur (Jwink3101) <a href="mailto:Jwink3101@users.noreply.github.com" class="email">Jwink3101@users.noreply.github.com</a></li>
-<li>Mariano Absatz (git) <a href="mailto:scm@baby.com.ar" class="email">scm@baby.com.ar</a></li>
-<li>Greg Sadetsky <a href="mailto:lepetitg@gmail.com" class="email">lepetitg@gmail.com</a></li>
-<li>yedamo <a href="mailto:logindaveye@gmail.com" class="email">logindaveye@gmail.com</a></li>
-<li>hota <a href="mailto:lindwurm.q@gmail.com" class="email">lindwurm.q@gmail.com</a></li>
-<li>vinibali <a href="mailto:vinibali1@gmail.com" class="email">vinibali1@gmail.com</a></li>
-<li>Ken Enrique Morel <a href="mailto:ken.morel.santana@gmail.com" class="email">ken.morel.santana@gmail.com</a></li>
-<li>Justin Hellings <a href="mailto:justin.hellings@gmail.com" class="email">justin.hellings@gmail.com</a></li>
-<li>Parth Shukla <a href="mailto:pparth@pparth.net" class="email">pparth@pparth.net</a></li>
-<li>wzl <a href="mailto:wangzl31@outlook.com" class="email">wangzl31@outlook.com</a></li>
-<li>HNGamingUK <a href="mailto:connor@earnshawhome.co.uk" class="email">connor@earnshawhome.co.uk</a></li>
-<li>Jonta <a href="mailto:359397+Jonta@users.noreply.github.com" class="email">359397+Jonta@users.noreply.github.com</a></li>
-<li>YenForYang <a href="mailto:YenForYang@users.noreply.github.com" class="email">YenForYang@users.noreply.github.com</a></li>
-<li>SimJoSt / Joda Stößer <a href="mailto:git@simjo.st" class="email">git@simjo.st</a></li>
-<li>Logeshwaran <a href="mailto:waranlogesh@gmail.com" class="email">waranlogesh@gmail.com</a></li>
-<li>Rajat Goel <a href="mailto:rajat@dropbox.com" class="email">rajat@dropbox.com</a></li>
-<li>r0kk3rz <a href="mailto:r0kk3rz@gmail.com" class="email">r0kk3rz@gmail.com</a></li>
-<li>Matthew Sevey <a href="mailto:mjsevey@gmail.com" class="email">mjsevey@gmail.com</a></li>
-<li>Filip Rysavy <a href="mailto:fil@siasky.net" class="email">fil@siasky.net</a></li>
-<li>Ian Levesque <a href="mailto:ian@ianlevesque.org" class="email">ian@ianlevesque.org</a></li>
-<li>Thomas Stachl <a href="mailto:thomas@stachl.me" class="email">thomas@stachl.me</a></li>
-<li>Dmitry Bogatov <a href="mailto:git#v1@kaction.cc" class="email">git#v1@kaction.cc</a></li>
-<li>thomae <a href="mailto:4493560+thomae@users.noreply.github.com" class="email">4493560+thomae@users.noreply.github.com</a></li>
-<li>trevyn <a href="mailto:trevyn-git@protonmail.com" class="email">trevyn-git@protonmail.com</a></li>
-<li>David Liu <a href="mailto:david.yx.liu@oracle.com" class="email">david.yx.liu@oracle.com</a></li>
-<li>Chris Nelson <a href="mailto:stuff@cjnaz.com" class="email">stuff@cjnaz.com</a></li>
-<li>Felix Bünemann <a href="mailto:felix.buenemann@gmail.com" class="email">felix.buenemann@gmail.com</a></li>
-<li>Atílio Antônio <a href="mailto:atiliodadalto@hotmail.com" class="email">atiliodadalto@hotmail.com</a></li>
-<li>Carlo Mion <a href="mailto:mion00@gmail.com" class="email">mion00@gmail.com</a></li>
-<li>Chris Lu <a href="mailto:chris.lu@gmail.com" class="email">chris.lu@gmail.com</a></li>
-<li>Vitor Arruda <a href="mailto:vitor.pimenta.arruda@gmail.com" class="email">vitor.pimenta.arruda@gmail.com</a></li>
-<li>bbabich <a href="mailto:bbabich@datamossa.com" class="email">bbabich@datamossa.com</a></li>
-<li>David <a href="mailto:dp.davide.palma@gmail.com" class="email">dp.davide.palma@gmail.com</a></li>
-<li>Borna Butkovic <a href="mailto:borna@favicode.net" class="email">borna@favicode.net</a></li>
-<li>Fredric Arklid <a href="mailto:fredric.arklid@consid.se" class="email">fredric.arklid@consid.se</a></li>
-<li>Andy Jackson <a href="mailto:Andrew.Jackson@bl.uk" class="email">Andrew.Jackson@bl.uk</a></li>
-<li>Sinan Tan <a href="mailto:i@tinytangent.com" class="email">i@tinytangent.com</a></li>
-<li>deinferno <a href="mailto:14363193+deinferno@users.noreply.github.com" class="email">14363193+deinferno@users.noreply.github.com</a></li>
-<li>rsapkf <a href="mailto:rsapkfff@pm.me" class="email">rsapkfff@pm.me</a></li>
-<li>Will Holtz <a href="mailto:wholtz@gmail.com" class="email">wholtz@gmail.com</a></li>
-<li>GGG KILLER <a href="mailto:gggkiller2@gmail.com" class="email">gggkiller2@gmail.com</a></li>
-<li>Logeshwaran Murugesan <a href="mailto:logeshwaran@testpress.in" class="email">logeshwaran@testpress.in</a></li>
-<li>Lu Wang <a href="mailto:coolwanglu@gmail.com" class="email">coolwanglu@gmail.com</a></li>
-<li>Bumsu Hyeon <a href="mailto:ksitht@gmail.com" class="email">ksitht@gmail.com</a></li>
-<li>Shmz Ozggrn <a href="mailto:98463324+ShmzOzggrn@users.noreply.github.com" class="email">98463324+ShmzOzggrn@users.noreply.github.com</a></li>
-<li>Kim <a href="mailto:kim@jotta.no" class="email">kim@jotta.no</a></li>
-<li>Niels van de Weem <a href="mailto:n.van.de.weem@smile.nl" class="email">n.van.de.weem@smile.nl</a></li>
-<li>Koopa <a href="mailto:codingkoopa@gmail.com" class="email">codingkoopa@gmail.com</a></li>
-<li>Yunhai Luo <a href="mailto:yunhai-luo@hotmail.com" class="email">yunhai-luo@hotmail.com</a></li>
-<li>Charlie Jiang <a href="mailto:w@chariri.moe" class="email">w@chariri.moe</a></li>
-<li>Alain Nussbaumer <a href="mailto:alain.nussbaumer@alleluia.ch" class="email">alain.nussbaumer@alleluia.ch</a></li>
-<li>Vanessasaurus <a href="mailto:814322+vsoch@users.noreply.github.com" class="email">814322+vsoch@users.noreply.github.com</a></li>
-<li>Isaac Levy <a href="mailto:isaac.r.levy@gmail.com" class="email">isaac.r.levy@gmail.com</a></li>
-<li>Gourav T <a href="mailto:workflowautomation@protonmail.com" class="email">workflowautomation@protonmail.com</a></li>
-<li>Paulo Martins <a href="mailto:paulo.pontes.m@gmail.com" class="email">paulo.pontes.m@gmail.com</a></li>
-<li>viveknathani <a href="mailto:viveknathani2402@gmail.com" class="email">viveknathani2402@gmail.com</a></li>
-<li>Eng Zer Jun <a href="mailto:engzerjun@gmail.com" class="email">engzerjun@gmail.com</a></li>
-<li>Abhiraj <a href="mailto:abhiraj.official15@gmail.com" class="email">abhiraj.official15@gmail.com</a></li>
-<li>Márton Elek <a href="mailto:elek@apache.org" class="email">elek@apache.org</a> <a href="mailto:elek@users.noreply.github.com" class="email">elek@users.noreply.github.com</a></li>
-<li>Vincent Murphy <a href="mailto:vdm@vdm.ie" class="email">vdm@vdm.ie</a></li>
-<li>ctrl-q <a href="mailto:34975747+ctrl-q@users.noreply.github.com" class="email">34975747+ctrl-q@users.noreply.github.com</a></li>
-<li>Nil Alexandrov <a href="mailto:nalexand@akamai.com" class="email">nalexand@akamai.com</a></li>
-<li>GuoXingbin <a href="mailto:101376330+guoxingbin@users.noreply.github.com" class="email">101376330+guoxingbin@users.noreply.github.com</a></li>
-<li>Berkan Teber <a href="mailto:berkan@berkanteber.com" class="email">berkan@berkanteber.com</a></li>
-<li>Tobias Klauser <a href="mailto:tklauser@distanz.ch" class="email">tklauser@distanz.ch</a></li>
-<li>KARBOWSKI Piotr <a href="mailto:piotr.karbowski@gmail.com" class="email">piotr.karbowski@gmail.com</a></li>
-<li>GH <a href="mailto:geeklihui@foxmail.com" class="email">geeklihui@foxmail.com</a></li>
-<li>rafma0 <a href="mailto:int.main@gmail.com" class="email">int.main@gmail.com</a></li>
-<li>Adrien Rey-Jarthon <a href="mailto:jobs@adrienjarthon.com" class="email">jobs@adrienjarthon.com</a></li>
-<li>Nick Gooding <a href="mailto:73336146+nickgooding@users.noreply.github.com" class="email">73336146+nickgooding@users.noreply.github.com</a></li>
-<li>Leroy van Logchem <a href="mailto:lr.vanlogchem@gmail.com" class="email">lr.vanlogchem@gmail.com</a></li>
-<li>Zsolt Ero <a href="mailto:zsolt.ero@gmail.com" class="email">zsolt.ero@gmail.com</a></li>
-<li>Lesmiscore <a href="mailto:nao20010128@gmail.com" class="email">nao20010128@gmail.com</a></li>
-<li>ehsantdy <a href="mailto:ehsan.tadayon@arvancloud.com" class="email">ehsan.tadayon@arvancloud.com</a> <a href="mailto:ehsantadayon85@gmail.com" class="email">ehsantadayon85@gmail.com</a></li>
-<li>SwazRGB <a href="mailto:65694696+swazrgb@users.noreply.github.com" class="email">65694696+swazrgb@users.noreply.github.com</a></li>
-<li>Mateusz Puczyński <a href="mailto:mati6095@gmail.com" class="email">mati6095@gmail.com</a></li>
-<li>Michael C Tiernan - MIT-Research Computing Project <a href="mailto:mtiernan@mit.edu" class="email">mtiernan@mit.edu</a></li>
-<li>Kaspian <a href="mailto:34658474+KaspianDev@users.noreply.github.com" class="email">34658474+KaspianDev@users.noreply.github.com</a></li>
-<li>Werner <a href="mailto:EvilOlaf@users.noreply.github.com" class="email">EvilOlaf@users.noreply.github.com</a></li>
-<li>Hugal31 <a href="mailto:hugo.laloge@gmail.com" class="email">hugo.laloge@gmail.com</a></li>
-<li>Christian Galo <a href="mailto:36752715+cgalo5758@users.noreply.github.com" class="email">36752715+cgalo5758@users.noreply.github.com</a></li>
-<li>Erik van Velzen <a href="mailto:erik@evanv.nl" class="email">erik@evanv.nl</a></li>
-<li>Derek Battams <a href="mailto:derek@battams.ca" class="email">derek@battams.ca</a></li>
-<li>Paul <a href="mailto:devnoname120@gmail.com" class="email">devnoname120@gmail.com</a></li>
-<li>SimonLiu <a href="mailto:simonliu009@users.noreply.github.com" class="email">simonliu009@users.noreply.github.com</a></li>
-<li>Hugo Laloge <a href="mailto:hla@lescompanions.com" class="email">hla@lescompanions.com</a></li>
-<li>Mr-Kanister <a href="mailto:68117355+Mr-Kanister@users.noreply.github.com" class="email">68117355+Mr-Kanister@users.noreply.github.com</a></li>
-<li>Rob Pickerill <a href="mailto:r.pickerill@gmail.com" class="email">r.pickerill@gmail.com</a></li>
-<li>Andrey <a href="mailto:to.merge@gmail.com" class="email">to.merge@gmail.com</a></li>
-<li>Eric Wolf <a href="mailto:19wolf@gmail.com" class="email">19wolf@gmail.com</a></li>
-<li>Nick <a href="mailto:nick.naumann@mailbox.tu-dresden.de" class="email">nick.naumann@mailbox.tu-dresden.de</a></li>
-<li>Jason Zheng <a href="mailto:jszheng17@gmail.com" class="email">jszheng17@gmail.com</a></li>
-<li>Matthew Vernon <a href="mailto:mvernon@wikimedia.org" class="email">mvernon@wikimedia.org</a></li>
+<li>Nick Gaya <a href="mailto:nicholasgaya+github@gmail.com"
+class="email">nicholasgaya+github@gmail.com</a></li>
+<li>Ashok Gelal <a
+href="mailto:401055+ashokgelal@users.noreply.github.com"
+class="email">401055+ashokgelal@users.noreply.github.com</a></li>
+<li>Dominik Mydlil <a href="mailto:dominik.mydlil@outlook.com"
+class="email">dominik.mydlil@outlook.com</a></li>
+<li>Nazar Mishturak <a href="mailto:nazarmx@gmail.com"
+class="email">nazarmx@gmail.com</a></li>
+<li>Ansh Mittal <a href="mailto:iamAnshMittal@gmail.com"
+class="email">iamAnshMittal@gmail.com</a></li>
+<li>noabody <a href="mailto:noabody@yahoo.com"
+class="email">noabody@yahoo.com</a></li>
+<li>OleFrost <a href="mailto:82263101+olefrost@users.noreply.github.com"
+class="email">82263101+olefrost@users.noreply.github.com</a></li>
+<li>Kenny Parsons <a href="mailto:kennyparsons93@gmail.com"
+class="email">kennyparsons93@gmail.com</a></li>
+<li>Jeffrey Tolar <a href="mailto:tolar.jeffrey@gmail.com"
+class="email">tolar.jeffrey@gmail.com</a></li>
+<li>jtagcat <a href="mailto:git-514635f7@jtag.cat"
+class="email">git-514635f7@jtag.cat</a></li>
+<li>Tatsuya Noyori <a
+href="mailto:63089076+public-tatsuya-noyori@users.noreply.github.com"
+class="email">63089076+public-tatsuya-noyori@users.noreply.github.com</a></li>
+<li>lewisxy <a href="mailto:lewisxy@users.noreply.github.com"
+class="email">lewisxy@users.noreply.github.com</a></li>
+<li>Nolan Woods <a href="mailto:nolan_w@sfu.ca"
+class="email">nolan_w@sfu.ca</a></li>
+<li>Gautam Kumar <a
+href="mailto:25435568+gautamajay52@users.noreply.github.com"
+class="email">25435568+gautamajay52@users.noreply.github.com</a></li>
+<li>Chris Macklin <a href="mailto:chris.macklin@10xgenomics.com"
+class="email">chris.macklin@10xgenomics.com</a></li>
+<li>Antoon Prins <a href="mailto:antoon.prins@surfsara.nl"
+class="email">antoon.prins@surfsara.nl</a></li>
+<li>Alexey Ivanov <a href="mailto:rbtz@dropbox.com"
+class="email">rbtz@dropbox.com</a></li>
+<li>Serge Pouliquen <a href="mailto:sp31415@free.fr"
+class="email">sp31415@free.fr</a></li>
+<li>acsfer <a href="mailto:carlos@reendex.com"
+class="email">carlos@reendex.com</a></li>
+<li>Tom <a href="mailto:tom@tom-fitzhenry.me.uk"
+class="email">tom@tom-fitzhenry.me.uk</a></li>
+<li>Tyson Moore <a href="mailto:tyson@tyson.me"
+class="email">tyson@tyson.me</a></li>
+<li>database64128 <a href="mailto:free122448@hotmail.com"
+class="email">free122448@hotmail.com</a></li>
+<li>Chris Lu <a href="mailto:chrislusf@users.noreply.github.com"
+class="email">chrislusf@users.noreply.github.com</a></li>
+<li>Reid Buzby <a href="mailto:reid@rethink.software"
+class="email">reid@rethink.software</a></li>
+<li>darrenrhs <a href="mailto:darrenrhs@gmail.com"
+class="email">darrenrhs@gmail.com</a></li>
+<li>Florian Penzkofer <a href="mailto:fp@nullptr.de"
+class="email">fp@nullptr.de</a></li>
+<li>Xuanchen Wu <a href="mailto:117010292@link.cuhk.edu.cn"
+class="email">117010292@link.cuhk.edu.cn</a></li>
+<li>partev <a href="mailto:petrosyan@gmail.com"
+class="email">petrosyan@gmail.com</a></li>
+<li>Dmitry Sitnikov <a href="mailto:fo2@inbox.ru"
+class="email">fo2@inbox.ru</a></li>
+<li>Haochen Tong <a href="mailto:i@hexchain.org"
+class="email">i@hexchain.org</a></li>
+<li>Michael Hanselmann <a href="mailto:public@hansmi.ch"
+class="email">public@hansmi.ch</a></li>
+<li>Chuan Zh <a href="mailto:zhchuan7@gmail.com"
+class="email">zhchuan7@gmail.com</a></li>
+<li>Antoine GIRARD <a href="mailto:antoine.girard@sapk.fr"
+class="email">antoine.girard@sapk.fr</a></li>
+<li>Justin Winokur (Jwink3101) <a
+href="mailto:Jwink3101@users.noreply.github.com"
+class="email">Jwink3101@users.noreply.github.com</a></li>
+<li>Mariano Absatz (git) <a href="mailto:scm@baby.com.ar"
+class="email">scm@baby.com.ar</a></li>
+<li>Greg Sadetsky <a href="mailto:lepetitg@gmail.com"
+class="email">lepetitg@gmail.com</a></li>
+<li>yedamo <a href="mailto:logindaveye@gmail.com"
+class="email">logindaveye@gmail.com</a></li>
+<li>hota <a href="mailto:lindwurm.q@gmail.com"
+class="email">lindwurm.q@gmail.com</a></li>
+<li>vinibali <a href="mailto:vinibali1@gmail.com"
+class="email">vinibali1@gmail.com</a></li>
+<li>Ken Enrique Morel <a href="mailto:ken.morel.santana@gmail.com"
+class="email">ken.morel.santana@gmail.com</a></li>
+<li>Justin Hellings <a href="mailto:justin.hellings@gmail.com"
+class="email">justin.hellings@gmail.com</a></li>
+<li>Parth Shukla <a href="mailto:pparth@pparth.net"
+class="email">pparth@pparth.net</a></li>
+<li>wzl <a href="mailto:wangzl31@outlook.com"
+class="email">wangzl31@outlook.com</a></li>
+<li>HNGamingUK <a href="mailto:connor@earnshawhome.co.uk"
+class="email">connor@earnshawhome.co.uk</a></li>
+<li>Jonta <a href="mailto:359397+Jonta@users.noreply.github.com"
+class="email">359397+Jonta@users.noreply.github.com</a></li>
+<li>YenForYang <a href="mailto:YenForYang@users.noreply.github.com"
+class="email">YenForYang@users.noreply.github.com</a></li>
+<li>SimJoSt / Joda Stößer <a href="mailto:git@simjo.st"
+class="email">git@simjo.st</a></li>
+<li>Logeshwaran <a href="mailto:waranlogesh@gmail.com"
+class="email">waranlogesh@gmail.com</a></li>
+<li>Rajat Goel <a href="mailto:rajat@dropbox.com"
+class="email">rajat@dropbox.com</a></li>
+<li>r0kk3rz <a href="mailto:r0kk3rz@gmail.com"
+class="email">r0kk3rz@gmail.com</a></li>
+<li>Matthew Sevey <a href="mailto:mjsevey@gmail.com"
+class="email">mjsevey@gmail.com</a></li>
+<li>Filip Rysavy <a href="mailto:fil@siasky.net"
+class="email">fil@siasky.net</a></li>
+<li>Ian Levesque <a href="mailto:ian@ianlevesque.org"
+class="email">ian@ianlevesque.org</a></li>
+<li>Thomas Stachl <a href="mailto:thomas@stachl.me"
+class="email">thomas@stachl.me</a></li>
+<li>Dmitry Bogatov <a href="mailto:git#v1@kaction.cc"
+class="email">git#v1@kaction.cc</a></li>
+<li>thomae <a href="mailto:4493560+thomae@users.noreply.github.com"
+class="email">4493560+thomae@users.noreply.github.com</a></li>
+<li>trevyn <a href="mailto:trevyn-git@protonmail.com"
+class="email">trevyn-git@protonmail.com</a></li>
+<li>David Liu <a href="mailto:david.yx.liu@oracle.com"
+class="email">david.yx.liu@oracle.com</a></li>
+<li>Chris Nelson <a href="mailto:stuff@cjnaz.com"
+class="email">stuff@cjnaz.com</a></li>
+<li>Felix Bünemann <a href="mailto:felix.buenemann@gmail.com"
+class="email">felix.buenemann@gmail.com</a></li>
+<li>Atílio Antônio <a href="mailto:atiliodadalto@hotmail.com"
+class="email">atiliodadalto@hotmail.com</a></li>
+<li>Carlo Mion <a href="mailto:mion00@gmail.com"
+class="email">mion00@gmail.com</a></li>
+<li>Chris Lu <a href="mailto:chris.lu@gmail.com"
+class="email">chris.lu@gmail.com</a></li>
+<li>Vitor Arruda <a href="mailto:vitor.pimenta.arruda@gmail.com"
+class="email">vitor.pimenta.arruda@gmail.com</a></li>
+<li>bbabich <a href="mailto:bbabich@datamossa.com"
+class="email">bbabich@datamossa.com</a></li>
+<li>David <a href="mailto:dp.davide.palma@gmail.com"
+class="email">dp.davide.palma@gmail.com</a></li>
+<li>Borna Butkovic <a href="mailto:borna@favicode.net"
+class="email">borna@favicode.net</a></li>
+<li>Fredric Arklid <a href="mailto:fredric.arklid@consid.se"
+class="email">fredric.arklid@consid.se</a></li>
+<li>Andy Jackson <a href="mailto:Andrew.Jackson@bl.uk"
+class="email">Andrew.Jackson@bl.uk</a></li>
+<li>Sinan Tan <a href="mailto:i@tinytangent.com"
+class="email">i@tinytangent.com</a></li>
+<li>deinferno <a
+href="mailto:14363193+deinferno@users.noreply.github.com"
+class="email">14363193+deinferno@users.noreply.github.com</a></li>
+<li>rsapkf <a href="mailto:rsapkfff@pm.me"
+class="email">rsapkfff@pm.me</a></li>
+<li>Will Holtz <a href="mailto:wholtz@gmail.com"
+class="email">wholtz@gmail.com</a></li>
+<li>GGG KILLER <a href="mailto:gggkiller2@gmail.com"
+class="email">gggkiller2@gmail.com</a></li>
+<li>Logeshwaran Murugesan <a href="mailto:logeshwaran@testpress.in"
+class="email">logeshwaran@testpress.in</a></li>
+<li>Lu Wang <a href="mailto:coolwanglu@gmail.com"
+class="email">coolwanglu@gmail.com</a></li>
+<li>Bumsu Hyeon <a href="mailto:ksitht@gmail.com"
+class="email">ksitht@gmail.com</a></li>
+<li>Shmz Ozggrn <a
+href="mailto:98463324+ShmzOzggrn@users.noreply.github.com"
+class="email">98463324+ShmzOzggrn@users.noreply.github.com</a></li>
+<li>Kim <a href="mailto:kim@jotta.no"
+class="email">kim@jotta.no</a></li>
+<li>Niels van de Weem <a href="mailto:n.van.de.weem@smile.nl"
+class="email">n.van.de.weem@smile.nl</a></li>
+<li>Koopa <a href="mailto:codingkoopa@gmail.com"
+class="email">codingkoopa@gmail.com</a></li>
+<li>Yunhai Luo <a href="mailto:yunhai-luo@hotmail.com"
+class="email">yunhai-luo@hotmail.com</a></li>
+<li>Charlie Jiang <a href="mailto:w@chariri.moe"
+class="email">w@chariri.moe</a></li>
+<li>Alain Nussbaumer <a href="mailto:alain.nussbaumer@alleluia.ch"
+class="email">alain.nussbaumer@alleluia.ch</a></li>
+<li>Vanessasaurus <a href="mailto:814322+vsoch@users.noreply.github.com"
+class="email">814322+vsoch@users.noreply.github.com</a></li>
+<li>Isaac Levy <a href="mailto:isaac.r.levy@gmail.com"
+class="email">isaac.r.levy@gmail.com</a></li>
+<li>Gourav T <a href="mailto:workflowautomation@protonmail.com"
+class="email">workflowautomation@protonmail.com</a></li>
+<li>Paulo Martins <a href="mailto:paulo.pontes.m@gmail.com"
+class="email">paulo.pontes.m@gmail.com</a></li>
+<li>viveknathani <a href="mailto:viveknathani2402@gmail.com"
+class="email">viveknathani2402@gmail.com</a></li>
+<li>Eng Zer Jun <a href="mailto:engzerjun@gmail.com"
+class="email">engzerjun@gmail.com</a></li>
+<li>Abhiraj <a href="mailto:abhiraj.official15@gmail.com"
+class="email">abhiraj.official15@gmail.com</a></li>
+<li>Márton Elek <a href="mailto:elek@apache.org"
+class="email">elek@apache.org</a> <a
+href="mailto:elek@users.noreply.github.com"
+class="email">elek@users.noreply.github.com</a></li>
+<li>Vincent Murphy <a href="mailto:vdm@vdm.ie"
+class="email">vdm@vdm.ie</a></li>
+<li>ctrl-q <a href="mailto:34975747+ctrl-q@users.noreply.github.com"
+class="email">34975747+ctrl-q@users.noreply.github.com</a></li>
+<li>Nil Alexandrov <a href="mailto:nalexand@akamai.com"
+class="email">nalexand@akamai.com</a></li>
+<li>GuoXingbin <a
+href="mailto:101376330+guoxingbin@users.noreply.github.com"
+class="email">101376330+guoxingbin@users.noreply.github.com</a></li>
+<li>Berkan Teber <a href="mailto:berkan@berkanteber.com"
+class="email">berkan@berkanteber.com</a></li>
+<li>Tobias Klauser <a href="mailto:tklauser@distanz.ch"
+class="email">tklauser@distanz.ch</a></li>
+<li>KARBOWSKI Piotr <a href="mailto:piotr.karbowski@gmail.com"
+class="email">piotr.karbowski@gmail.com</a></li>
+<li>GH <a href="mailto:geeklihui@foxmail.com"
+class="email">geeklihui@foxmail.com</a></li>
+<li>rafma0 <a href="mailto:int.main@gmail.com"
+class="email">int.main@gmail.com</a></li>
+<li>Adrien Rey-Jarthon <a href="mailto:jobs@adrienjarthon.com"
+class="email">jobs@adrienjarthon.com</a></li>
+<li>Nick Gooding <a
+href="mailto:73336146+nickgooding@users.noreply.github.com"
+class="email">73336146+nickgooding@users.noreply.github.com</a></li>
+<li>Leroy van Logchem <a href="mailto:lr.vanlogchem@gmail.com"
+class="email">lr.vanlogchem@gmail.com</a></li>
+<li>Zsolt Ero <a href="mailto:zsolt.ero@gmail.com"
+class="email">zsolt.ero@gmail.com</a></li>
+<li>Lesmiscore <a href="mailto:nao20010128@gmail.com"
+class="email">nao20010128@gmail.com</a></li>
+<li>ehsantdy <a href="mailto:ehsan.tadayon@arvancloud.com"
+class="email">ehsan.tadayon@arvancloud.com</a> <a
+href="mailto:ehsantadayon85@gmail.com"
+class="email">ehsantadayon85@gmail.com</a></li>
+<li>SwazRGB <a href="mailto:65694696+swazrgb@users.noreply.github.com"
+class="email">65694696+swazrgb@users.noreply.github.com</a></li>
+<li>Mateusz Puczyński <a href="mailto:mati6095@gmail.com"
+class="email">mati6095@gmail.com</a></li>
+<li>Michael C Tiernan - MIT-Research Computing Project <a
+href="mailto:mtiernan@mit.edu" class="email">mtiernan@mit.edu</a></li>
+<li>Kaspian <a
+href="mailto:34658474+KaspianDev@users.noreply.github.com"
+class="email">34658474+KaspianDev@users.noreply.github.com</a></li>
+<li>Werner <a href="mailto:EvilOlaf@users.noreply.github.com"
+class="email">EvilOlaf@users.noreply.github.com</a></li>
+<li>Hugal31 <a href="mailto:hugo.laloge@gmail.com"
+class="email">hugo.laloge@gmail.com</a></li>
+<li>Christian Galo <a
+href="mailto:36752715+cgalo5758@users.noreply.github.com"
+class="email">36752715+cgalo5758@users.noreply.github.com</a></li>
+<li>Erik van Velzen <a href="mailto:erik@evanv.nl"
+class="email">erik@evanv.nl</a></li>
+<li>Derek Battams <a href="mailto:derek@battams.ca"
+class="email">derek@battams.ca</a></li>
+<li>Paul <a href="mailto:devnoname120@gmail.com"
+class="email">devnoname120@gmail.com</a></li>
+<li>SimonLiu <a href="mailto:simonliu009@users.noreply.github.com"
+class="email">simonliu009@users.noreply.github.com</a></li>
+<li>Hugo Laloge <a href="mailto:hla@lescompanions.com"
+class="email">hla@lescompanions.com</a></li>
+<li>Mr-Kanister <a
+href="mailto:68117355+Mr-Kanister@users.noreply.github.com"
+class="email">68117355+Mr-Kanister@users.noreply.github.com</a></li>
+<li>Rob Pickerill <a href="mailto:r.pickerill@gmail.com"
+class="email">r.pickerill@gmail.com</a></li>
+<li>Andrey <a href="mailto:to.merge@gmail.com"
+class="email">to.merge@gmail.com</a></li>
+<li>Eric Wolf <a href="mailto:19wolf@gmail.com"
+class="email">19wolf@gmail.com</a></li>
+<li>Nick <a href="mailto:nick.naumann@mailbox.tu-dresden.de"
+class="email">nick.naumann@mailbox.tu-dresden.de</a></li>
+<li>Jason Zheng <a href="mailto:jszheng17@gmail.com"
+class="email">jszheng17@gmail.com</a></li>
+<li>Matthew Vernon <a href="mailto:mvernon@wikimedia.org"
+class="email">mvernon@wikimedia.org</a></li>
 <li>Noah Hsu <a href="mailto:i@nn.ci" class="email">i@nn.ci</a></li>
-<li>m00594701 <a href="mailto:mengpengbo@huawei.com" class="email">mengpengbo@huawei.com</a></li>
-<li>Art M. Gallagher <a href="mailto:artmg50@gmail.com" class="email">artmg50@gmail.com</a></li>
-<li>Sven Gerber <a href="mailto:49589423+svengerber@users.noreply.github.com" class="email">49589423+svengerber@users.noreply.github.com</a></li>
-<li>CrossR <a href="mailto:r.cross@lancaster.ac.uk" class="email">r.cross@lancaster.ac.uk</a></li>
-<li>Maciej Radzikowski <a href="mailto:maciej@radzikowski.com.pl" class="email">maciej@radzikowski.com.pl</a></li>
-<li>Scott Grimes <a href="mailto:scott.grimes@spaciq.com" class="email">scott.grimes@spaciq.com</a></li>
-<li>Phil Shackleton <a href="mailto:71221528+philshacks@users.noreply.github.com" class="email">71221528+philshacks@users.noreply.github.com</a></li>
-<li>eNV25 <a href="mailto:env252525@gmail.com" class="email">env252525@gmail.com</a></li>
-<li>Caleb <a href="mailto:inventor96@users.noreply.github.com" class="email">inventor96@users.noreply.github.com</a></li>
-<li>J-P Treen <a href="mailto:jp@wraptious.com" class="email">jp@wraptious.com</a></li>
-<li>Martin Czygan <a href="mailto:53705+miku@users.noreply.github.com" class="email">53705+miku@users.noreply.github.com</a></li>
-<li>buda <a href="mailto:sandrojijavadze@protonmail.com" class="email">sandrojijavadze@protonmail.com</a></li>
-<li>mirekphd <a href="mailto:36706320+mirekphd@users.noreply.github.com" class="email">36706320+mirekphd@users.noreply.github.com</a></li>
-<li>vyloy <a href="mailto:vyloy@qq.com" class="email">vyloy@qq.com</a></li>
-<li>Anthrazz <a href="mailto:25553648+Anthrazz@users.noreply.github.com" class="email">25553648+Anthrazz@users.noreply.github.com</a></li>
-<li>zzr93 <a href="mailto:34027824+zzr93@users.noreply.github.com" class="email">34027824+zzr93@users.noreply.github.com</a></li>
-<li>Paul Norman <a href="mailto:penorman@mac.com" class="email">penorman@mac.com</a></li>
-<li>Lorenzo Maiorfi <a href="mailto:maiorfi@gmail.com" class="email">maiorfi@gmail.com</a></li>
-<li>Claudio Maradonna <a href="mailto:penguyman@stronzi.org" class="email">penguyman@stronzi.org</a></li>
-<li>Ovidiu Victor Tatar <a href="mailto:ovi.tatar@googlemail.com" class="email">ovi.tatar@googlemail.com</a></li>
-<li>Evan Spensley <a href="mailto:epspensley@gmail.com" class="email">epspensley@gmail.com</a></li>
-<li>Yen Hu <a href="mailto:61753151+0x59656e@users.noreply.github.com" class="email">61753151+0x59656e@users.noreply.github.com</a></li>
-<li>Steve Kowalik <a href="mailto:steven@wedontsleep.org" class="email">steven@wedontsleep.org</a></li>
-<li>Jordi Gonzalez Muñoz <a href="mailto:jordigonzm@gmail.com" class="email">jordigonzm@gmail.com</a></li>
-<li>Joram Schrijver <a href="mailto:i@joram.io" class="email">i@joram.io</a></li>
-<li>Mark Trolley <a href="mailto:marktrolley@gmail.com" class="email">marktrolley@gmail.com</a></li>
-<li>João Henrique Franco <a href="mailto:joaohenrique.franco@gmail.com" class="email">joaohenrique.franco@gmail.com</a></li>
-<li>anonion <a href="mailto:aman207@users.noreply.github.com" class="email">aman207@users.noreply.github.com</a></li>
-<li>Ryan Morey <a href="mailto:4590343+rmorey@users.noreply.github.com" class="email">4590343+rmorey@users.noreply.github.com</a></li>
-<li>Simon Bos <a href="mailto:simonbos9@gmail.com" class="email">simonbos9@gmail.com</a></li>
-<li>YFdyh000 <a href="mailto:yfdyh000@gmail.com" class="email">yfdyh000@gmail.com</a> * Josh Soref <a href="mailto:2119212+jsoref@users.noreply.github.com" class="email">2119212+jsoref@users.noreply.github.com</a></li>
-<li>Øyvind Heddeland Instefjord <a href="mailto:instefjord@outlook.com" class="email">instefjord@outlook.com</a></li>
-<li>Dmitry Deniskin <a href="mailto:110819396+ddeniskin@users.noreply.github.com" class="email">110819396+ddeniskin@users.noreply.github.com</a></li>
-<li>Alexander Knorr <a href="mailto:106825+opexxx@users.noreply.github.com" class="email">106825+opexxx@users.noreply.github.com</a></li>
-<li>Richard Bateman <a href="mailto:richard@batemansr.us" class="email">richard@batemansr.us</a></li>
-<li>Dimitri Papadopoulos Orfanos <a href="mailto:3234522+DimitriPapadopoulos@users.noreply.github.com" class="email">3234522+DimitriPapadopoulos@users.noreply.github.com</a></li>
-<li>Lorenzo Milesi <a href="mailto:lorenzo.milesi@yetopen.com" class="email">lorenzo.milesi@yetopen.com</a></li>
-<li>Isaac Aymerich <a href="mailto:isaac.aymerich@gmail.com" class="email">isaac.aymerich@gmail.com</a></li>
-<li>YanceyChiew <a href="mailto:35898533+YanceyChiew@users.noreply.github.com" class="email">35898533+YanceyChiew@users.noreply.github.com</a></li>
-<li>Manoj Ghosh <a href="mailto:msays2000@gmail.com" class="email">msays2000@gmail.com</a></li>
-<li>Bachue Zhou <a href="mailto:bachue.shu@gmail.com" class="email">bachue.shu@gmail.com</a></li>
-<li>Manoj Ghosh <a href="mailto:manoj.ghosh@oracle.com" class="email">manoj.ghosh@oracle.com</a></li>
-<li>Tom Mombourquette <a href="mailto:tom@devnode.com" class="email">tom@devnode.com</a></li>
-<li>Robert Newson <a href="mailto:rnewson@apache.org" class="email">rnewson@apache.org</a></li>
-<li>Samuel Johnson <a href="mailto:esamueljohnson@gmail.com" class="email">esamueljohnson@gmail.com</a></li>
-<li>coultonluke <a href="mailto:luke@luke.org.uk" class="email">luke@luke.org.uk</a></li>
-<li>Anthony Pessy <a href="mailto:anthony@cogniteev.com" class="email">anthony@cogniteev.com</a></li>
-<li>Philip Harvey <a href="mailto:pharvey@battelleecology.org" class="email">pharvey@battelleecology.org</a></li>
-<li>dgouju <a href="mailto:dgouju@users.noreply.github.com" class="email">dgouju@users.noreply.github.com</a></li>
-<li>Clément Notin <a href="mailto:clement.notin@gmail.com" class="email">clement.notin@gmail.com</a></li>
-<li>x3-apptech <a href="mailto:66947598+x3-apptech@users.noreply.github.com" class="email">66947598+x3-apptech@users.noreply.github.com</a></li>
-<li>Arnie97 <a href="mailto:arnie97@gmail.com" class="email">arnie97@gmail.com</a></li>
-<li>Roel Arents <a href="mailto:2691308+roelarents@users.noreply.github.com" class="email">2691308+roelarents@users.noreply.github.com</a></li>
-<li>Aaron Gokaslan <a href="mailto:aaronGokaslan@gmail.com" class="email">aaronGokaslan@gmail.com</a></li>
-<li>techknowlogick <a href="mailto:matti@mdranta.net" class="email">matti@mdranta.net</a></li>
-<li>rkettelerij <a href="mailto:richard@mindloops.nl" class="email">richard@mindloops.nl</a></li>
-<li>Kamui <a href="mailto:fin-kamui@pm.me" class="email">fin-kamui@pm.me</a></li>
-<li>asdffdsazqqq <a href="mailto:90116442+asdffdsazqqq@users.noreply.github.com" class="email">90116442+asdffdsazqqq@users.noreply.github.com</a></li>
-<li>Nathaniel Wesley Filardo <a href="mailto:nfilardo@microsoft.com" class="email">nfilardo@microsoft.com</a></li>
-<li>ycdtosa <a href="mailto:ycdtosa@users.noreply.github.com" class="email">ycdtosa@users.noreply.github.com</a></li>
-<li>Erik Agterdenbos <a href="mailto:agterdenbos@users.noreply.github.com" class="email">agterdenbos@users.noreply.github.com</a></li>
-<li>Kevin Verstaen <a href="mailto:48050031+kverstae@users.noreply.github.com" class="email">48050031+kverstae@users.noreply.github.com</a></li>
-<li>MohammadReza <a href="mailto:mrvashian@gmail.com" class="email">mrvashian@gmail.com</a></li>
-<li>vanplus <a href="mailto:60313789+vanplus@users.noreply.github.com" class="email">60313789+vanplus@users.noreply.github.com</a></li>
-<li>Jack <a href="mailto:16779171+jkpe@users.noreply.github.com" class="email">16779171+jkpe@users.noreply.github.com</a></li>
-<li>Abdullah Saglam <a href="mailto:abdullah.saglam@stonebranch.com" class="email">abdullah.saglam@stonebranch.com</a></li>
-<li>Marks Polakovs <a href="mailto:github@markspolakovs.me" class="email">github@markspolakovs.me</a></li>
-<li>piyushgarg <a href="mailto:piyushgarg80@gmail.com" class="email">piyushgarg80@gmail.com</a></li>
-<li>Kaloyan Raev <a href="mailto:kaloyan-raev@users.noreply.github.com" class="email">kaloyan-raev@users.noreply.github.com</a></li>
-<li>IMTheNachoMan <a href="mailto:imthenachoman@gmail.com" class="email">imthenachoman@gmail.com</a></li>
-<li>alankrit <a href="mailto:alankrit@google.com" class="email">alankrit@google.com</a></li>
-<li>Bryan Kaplan &lt;#<span class="citation" data-cites="bryankaplan.com">@bryankaplan.com</span>&gt;</li>
-<li>LXY <a href="mailto:767763591@qq.com" class="email">767763591@qq.com</a></li>
-<li>Simmon Li (he/him) <a href="mailto:li.simmon@gmail.com" class="email">li.simmon@gmail.com</a></li>
-<li>happyxhw <a href="mailto:44490504+happyxhw@users.noreply.github.com" class="email">44490504+happyxhw@users.noreply.github.com</a></li>
-<li>Simmon Li (he/him) <a href="mailto:hello@crespire.dev" class="email">hello@crespire.dev</a></li>
-<li>Matthias Baur <a href="mailto:baurmatt@users.noreply.github.com" class="email">baurmatt@users.noreply.github.com</a></li>
-<li>Hunter Wittenborn <a href="mailto:hunter@hunterwittenborn.com" class="email">hunter@hunterwittenborn.com</a></li>
-<li>logopk <a href="mailto:peter@kreuser.name" class="email">peter@kreuser.name</a></li>
-<li>Gerard Bosch <a href="mailto:30733556+gerardbosch@users.noreply.github.com" class="email">30733556+gerardbosch@users.noreply.github.com</a></li>
-<li>ToBeFree <a href="mailto:github@tfrei.de" class="email">github@tfrei.de</a></li>
-<li>NodudeWasTaken <a href="mailto:75137537+NodudeWasTaken@users.noreply.github.com" class="email">75137537+NodudeWasTaken@users.noreply.github.com</a></li>
-<li>Peter Brunner <a href="mailto:peter@lugoues.net" class="email">peter@lugoues.net</a></li>
-<li>Ninh Pham <a href="mailto:dongian.rapclubkhtn@gmail.com" class="email">dongian.rapclubkhtn@gmail.com</a></li>
-<li>Ryan Caezar Itang <a href="mailto:sitiom@proton.me" class="email">sitiom@proton.me</a></li>
-<li>Peter Brunner <a href="mailto:peter@psykhe.com" class="email">peter@psykhe.com</a></li>
-<li>Leandro Sacchet <a href="mailto:leandro.sacchet@animati.com.br" class="email">leandro.sacchet@animati.com.br</a></li>
-<li>dependabot[bot] &lt;49699333+dependabot[bot]<span class="citation" data-cites="users.noreply.github.com">@users.noreply.github.com</span>&gt;</li>
-<li>cycneuramus <a href="mailto:56681631+cycneuramus@users.noreply.github.com" class="email">56681631+cycneuramus@users.noreply.github.com</a></li>
-<li>Arnavion <a href="mailto:me@arnavion.dev" class="email">me@arnavion.dev</a></li>
-<li>Christopher Merry <a href="mailto:christopher.merry@mlb.com" class="email">christopher.merry@mlb.com</a></li>
-<li>Thibault Coupin <a href="mailto:thibault.coupin@gmail.com" class="email">thibault.coupin@gmail.com</a></li>
-<li>Richard Tweed <a href="mailto:RichardoC@users.noreply.github.com" class="email">RichardoC@users.noreply.github.com</a></li>
-<li>Zach Kipp <a href="mailto:Zacho2@users.noreply.github.com" class="email">Zacho2@users.noreply.github.com</a></li>
-<li>yuudi <a href="mailto:26199752+yuudi@users.noreply.github.com" class="email">26199752+yuudi@users.noreply.github.com</a></li>
-<li>NickIAm <a href="mailto:NickIAm@users.noreply.github.com" class="email">NickIAm@users.noreply.github.com</a></li>
-<li>Juang, Yi-Lin <a href="mailto:frankyjuang@gmail.com" class="email">frankyjuang@gmail.com</a></li>
-<li>jumbi77 <a href="mailto:jumbi77@users.noreply.github.com" class="email">jumbi77@users.noreply.github.com</a></li>
-<li>Aditya Basu <a href="mailto:ab.aditya.basu@gmail.com" class="email">ab.aditya.basu@gmail.com</a></li>
+<li>m00594701 <a href="mailto:mengpengbo@huawei.com"
+class="email">mengpengbo@huawei.com</a></li>
+<li>Art M. Gallagher <a href="mailto:artmg50@gmail.com"
+class="email">artmg50@gmail.com</a></li>
+<li>Sven Gerber <a
+href="mailto:49589423+svengerber@users.noreply.github.com"
+class="email">49589423+svengerber@users.noreply.github.com</a></li>
+<li>CrossR <a href="mailto:r.cross@lancaster.ac.uk"
+class="email">r.cross@lancaster.ac.uk</a></li>
+<li>Maciej Radzikowski <a href="mailto:maciej@radzikowski.com.pl"
+class="email">maciej@radzikowski.com.pl</a></li>
+<li>Scott Grimes <a href="mailto:scott.grimes@spaciq.com"
+class="email">scott.grimes@spaciq.com</a></li>
+<li>Phil Shackleton <a
+href="mailto:71221528+philshacks@users.noreply.github.com"
+class="email">71221528+philshacks@users.noreply.github.com</a></li>
+<li>eNV25 <a href="mailto:env252525@gmail.com"
+class="email">env252525@gmail.com</a></li>
+<li>Caleb <a href="mailto:inventor96@users.noreply.github.com"
+class="email">inventor96@users.noreply.github.com</a></li>
+<li>J-P Treen <a href="mailto:jp@wraptious.com"
+class="email">jp@wraptious.com</a></li>
+<li>Martin Czygan <a href="mailto:53705+miku@users.noreply.github.com"
+class="email">53705+miku@users.noreply.github.com</a></li>
+<li>buda <a href="mailto:sandrojijavadze@protonmail.com"
+class="email">sandrojijavadze@protonmail.com</a></li>
+<li>mirekphd <a href="mailto:36706320+mirekphd@users.noreply.github.com"
+class="email">36706320+mirekphd@users.noreply.github.com</a></li>
+<li>vyloy <a href="mailto:vyloy@qq.com"
+class="email">vyloy@qq.com</a></li>
+<li>Anthrazz <a href="mailto:25553648+Anthrazz@users.noreply.github.com"
+class="email">25553648+Anthrazz@users.noreply.github.com</a></li>
+<li>zzr93 <a href="mailto:34027824+zzr93@users.noreply.github.com"
+class="email">34027824+zzr93@users.noreply.github.com</a></li>
+<li>Paul Norman <a href="mailto:penorman@mac.com"
+class="email">penorman@mac.com</a></li>
+<li>Lorenzo Maiorfi <a href="mailto:maiorfi@gmail.com"
+class="email">maiorfi@gmail.com</a></li>
+<li>Claudio Maradonna <a href="mailto:penguyman@stronzi.org"
+class="email">penguyman@stronzi.org</a></li>
+<li>Ovidiu Victor Tatar <a href="mailto:ovi.tatar@googlemail.com"
+class="email">ovi.tatar@googlemail.com</a></li>
+<li>Evan Spensley <a href="mailto:epspensley@gmail.com"
+class="email">epspensley@gmail.com</a></li>
+<li>Yen Hu <a href="mailto:61753151+0x59656e@users.noreply.github.com"
+class="email">61753151+0x59656e@users.noreply.github.com</a></li>
+<li>Steve Kowalik <a href="mailto:steven@wedontsleep.org"
+class="email">steven@wedontsleep.org</a></li>
+<li>Jordi Gonzalez Muñoz <a href="mailto:jordigonzm@gmail.com"
+class="email">jordigonzm@gmail.com</a></li>
+<li>Joram Schrijver <a href="mailto:i@joram.io"
+class="email">i@joram.io</a></li>
+<li>Mark Trolley <a href="mailto:marktrolley@gmail.com"
+class="email">marktrolley@gmail.com</a></li>
+<li>João Henrique Franco <a href="mailto:joaohenrique.franco@gmail.com"
+class="email">joaohenrique.franco@gmail.com</a></li>
+<li>anonion <a href="mailto:aman207@users.noreply.github.com"
+class="email">aman207@users.noreply.github.com</a></li>
+<li>Ryan Morey <a href="mailto:4590343+rmorey@users.noreply.github.com"
+class="email">4590343+rmorey@users.noreply.github.com</a></li>
+<li>Simon Bos <a href="mailto:simonbos9@gmail.com"
+class="email">simonbos9@gmail.com</a></li>
+<li>YFdyh000 <a href="mailto:yfdyh000@gmail.com"
+class="email">yfdyh000@gmail.com</a> * Josh Soref <a
+href="mailto:2119212+jsoref@users.noreply.github.com"
+class="email">2119212+jsoref@users.noreply.github.com</a></li>
+<li>Øyvind Heddeland Instefjord <a href="mailto:instefjord@outlook.com"
+class="email">instefjord@outlook.com</a></li>
+<li>Dmitry Deniskin <a
+href="mailto:110819396+ddeniskin@users.noreply.github.com"
+class="email">110819396+ddeniskin@users.noreply.github.com</a></li>
+<li>Alexander Knorr <a
+href="mailto:106825+opexxx@users.noreply.github.com"
+class="email">106825+opexxx@users.noreply.github.com</a></li>
+<li>Richard Bateman <a href="mailto:richard@batemansr.us"
+class="email">richard@batemansr.us</a></li>
+<li>Dimitri Papadopoulos Orfanos <a
+href="mailto:3234522+DimitriPapadopoulos@users.noreply.github.com"
+class="email">3234522+DimitriPapadopoulos@users.noreply.github.com</a></li>
+<li>Lorenzo Milesi <a href="mailto:lorenzo.milesi@yetopen.com"
+class="email">lorenzo.milesi@yetopen.com</a></li>
+<li>Isaac Aymerich <a href="mailto:isaac.aymerich@gmail.com"
+class="email">isaac.aymerich@gmail.com</a></li>
+<li>YanceyChiew <a
+href="mailto:35898533+YanceyChiew@users.noreply.github.com"
+class="email">35898533+YanceyChiew@users.noreply.github.com</a></li>
+<li>Manoj Ghosh <a href="mailto:msays2000@gmail.com"
+class="email">msays2000@gmail.com</a></li>
+<li>Bachue Zhou <a href="mailto:bachue.shu@gmail.com"
+class="email">bachue.shu@gmail.com</a></li>
+<li>Manoj Ghosh <a href="mailto:manoj.ghosh@oracle.com"
+class="email">manoj.ghosh@oracle.com</a></li>
+<li>Tom Mombourquette <a href="mailto:tom@devnode.com"
+class="email">tom@devnode.com</a></li>
+<li>Robert Newson <a href="mailto:rnewson@apache.org"
+class="email">rnewson@apache.org</a></li>
+<li>Samuel Johnson <a href="mailto:esamueljohnson@gmail.com"
+class="email">esamueljohnson@gmail.com</a></li>
+<li>coultonluke <a href="mailto:luke@luke.org.uk"
+class="email">luke@luke.org.uk</a></li>
+<li>Anthony Pessy <a href="mailto:anthony@cogniteev.com"
+class="email">anthony@cogniteev.com</a></li>
+<li>Philip Harvey <a href="mailto:pharvey@battelleecology.org"
+class="email">pharvey@battelleecology.org</a></li>
+<li>dgouju <a href="mailto:dgouju@users.noreply.github.com"
+class="email">dgouju@users.noreply.github.com</a></li>
+<li>Clément Notin <a href="mailto:clement.notin@gmail.com"
+class="email">clement.notin@gmail.com</a></li>
+<li>x3-apptech <a
+href="mailto:66947598+x3-apptech@users.noreply.github.com"
+class="email">66947598+x3-apptech@users.noreply.github.com</a></li>
+<li>Arnie97 <a href="mailto:arnie97@gmail.com"
+class="email">arnie97@gmail.com</a></li>
+<li>Roel Arents <a
+href="mailto:2691308+roelarents@users.noreply.github.com"
+class="email">2691308+roelarents@users.noreply.github.com</a></li>
+<li>Aaron Gokaslan <a href="mailto:aaronGokaslan@gmail.com"
+class="email">aaronGokaslan@gmail.com</a></li>
+<li>techknowlogick <a href="mailto:matti@mdranta.net"
+class="email">matti@mdranta.net</a></li>
+<li>rkettelerij <a href="mailto:richard@mindloops.nl"
+class="email">richard@mindloops.nl</a></li>
+<li>Kamui <a href="mailto:fin-kamui@pm.me"
+class="email">fin-kamui@pm.me</a></li>
+<li>asdffdsazqqq <a
+href="mailto:90116442+asdffdsazqqq@users.noreply.github.com"
+class="email">90116442+asdffdsazqqq@users.noreply.github.com</a></li>
+<li>Nathaniel Wesley Filardo <a href="mailto:nfilardo@microsoft.com"
+class="email">nfilardo@microsoft.com</a></li>
+<li>ycdtosa <a href="mailto:ycdtosa@users.noreply.github.com"
+class="email">ycdtosa@users.noreply.github.com</a></li>
+<li>Erik Agterdenbos <a
+href="mailto:agterdenbos@users.noreply.github.com"
+class="email">agterdenbos@users.noreply.github.com</a></li>
+<li>Kevin Verstaen <a
+href="mailto:48050031+kverstae@users.noreply.github.com"
+class="email">48050031+kverstae@users.noreply.github.com</a></li>
+<li>MohammadReza <a href="mailto:mrvashian@gmail.com"
+class="email">mrvashian@gmail.com</a></li>
+<li>vanplus <a href="mailto:60313789+vanplus@users.noreply.github.com"
+class="email">60313789+vanplus@users.noreply.github.com</a></li>
+<li>Jack <a href="mailto:16779171+jkpe@users.noreply.github.com"
+class="email">16779171+jkpe@users.noreply.github.com</a></li>
+<li>Abdullah Saglam <a href="mailto:abdullah.saglam@stonebranch.com"
+class="email">abdullah.saglam@stonebranch.com</a></li>
+<li>Marks Polakovs <a href="mailto:github@markspolakovs.me"
+class="email">github@markspolakovs.me</a></li>
+<li>piyushgarg <a href="mailto:piyushgarg80@gmail.com"
+class="email">piyushgarg80@gmail.com</a></li>
+<li>Kaloyan Raev <a href="mailto:kaloyan-raev@users.noreply.github.com"
+class="email">kaloyan-raev@users.noreply.github.com</a></li>
+<li>IMTheNachoMan <a href="mailto:imthenachoman@gmail.com"
+class="email">imthenachoman@gmail.com</a></li>
+<li>alankrit <a href="mailto:alankrit@google.com"
+class="email">alankrit@google.com</a></li>
+<li>Bryan Kaplan &lt;#<span class="citation"
+data-cites="bryankaplan.com">@bryankaplan.com</span>&gt;</li>
+<li>LXY <a href="mailto:767763591@qq.com"
+class="email">767763591@qq.com</a></li>
+<li>Simmon Li (he/him) <a href="mailto:li.simmon@gmail.com"
+class="email">li.simmon@gmail.com</a></li>
+<li>happyxhw <a href="mailto:44490504+happyxhw@users.noreply.github.com"
+class="email">44490504+happyxhw@users.noreply.github.com</a></li>
+<li>Simmon Li (he/him) <a href="mailto:hello@crespire.dev"
+class="email">hello@crespire.dev</a></li>
+<li>Matthias Baur <a href="mailto:baurmatt@users.noreply.github.com"
+class="email">baurmatt@users.noreply.github.com</a></li>
+<li>Hunter Wittenborn <a href="mailto:hunter@hunterwittenborn.com"
+class="email">hunter@hunterwittenborn.com</a></li>
+<li>logopk <a href="mailto:peter@kreuser.name"
+class="email">peter@kreuser.name</a></li>
+<li>Gerard Bosch <a
+href="mailto:30733556+gerardbosch@users.noreply.github.com"
+class="email">30733556+gerardbosch@users.noreply.github.com</a></li>
+<li>ToBeFree <a href="mailto:github@tfrei.de"
+class="email">github@tfrei.de</a></li>
+<li>NodudeWasTaken <a
+href="mailto:75137537+NodudeWasTaken@users.noreply.github.com"
+class="email">75137537+NodudeWasTaken@users.noreply.github.com</a></li>
+<li>Peter Brunner <a href="mailto:peter@lugoues.net"
+class="email">peter@lugoues.net</a></li>
+<li>Ninh Pham <a href="mailto:dongian.rapclubkhtn@gmail.com"
+class="email">dongian.rapclubkhtn@gmail.com</a></li>
+<li>Ryan Caezar Itang <a href="mailto:sitiom@proton.me"
+class="email">sitiom@proton.me</a></li>
+<li>Peter Brunner <a href="mailto:peter@psykhe.com"
+class="email">peter@psykhe.com</a></li>
+<li>Leandro Sacchet <a href="mailto:leandro.sacchet@animati.com.br"
+class="email">leandro.sacchet@animati.com.br</a></li>
+<li>dependabot[bot] &lt;49699333+dependabot[bot]<span class="citation"
+data-cites="users.noreply.github.com">@users.noreply.github.com</span>&gt;</li>
+<li>cycneuramus <a
+href="mailto:56681631+cycneuramus@users.noreply.github.com"
+class="email">56681631+cycneuramus@users.noreply.github.com</a></li>
+<li>Arnavion <a href="mailto:me@arnavion.dev"
+class="email">me@arnavion.dev</a></li>
+<li>Christopher Merry <a href="mailto:christopher.merry@mlb.com"
+class="email">christopher.merry@mlb.com</a></li>
+<li>Thibault Coupin <a href="mailto:thibault.coupin@gmail.com"
+class="email">thibault.coupin@gmail.com</a></li>
+<li>Richard Tweed <a href="mailto:RichardoC@users.noreply.github.com"
+class="email">RichardoC@users.noreply.github.com</a></li>
+<li>Zach Kipp <a href="mailto:Zacho2@users.noreply.github.com"
+class="email">Zacho2@users.noreply.github.com</a></li>
+<li>yuudi <a href="mailto:26199752+yuudi@users.noreply.github.com"
+class="email">26199752+yuudi@users.noreply.github.com</a></li>
+<li>NickIAm <a href="mailto:NickIAm@users.noreply.github.com"
+class="email">NickIAm@users.noreply.github.com</a></li>
+<li>Juang, Yi-Lin <a href="mailto:frankyjuang@gmail.com"
+class="email">frankyjuang@gmail.com</a></li>
+<li>jumbi77 <a href="mailto:jumbi77@users.noreply.github.com"
+class="email">jumbi77@users.noreply.github.com</a></li>
+<li>Aditya Basu <a href="mailto:ab.aditya.basu@gmail.com"
+class="email">ab.aditya.basu@gmail.com</a></li>
 <li>ed <a href="mailto:s@ocv.me" class="email">s@ocv.me</a></li>
-<li>Drew Parsons <a href="mailto:dparsons@emerall.com" class="email">dparsons@emerall.com</a></li>
-<li>Joel <a href="mailto:joelnb@users.noreply.github.com" class="email">joelnb@users.noreply.github.com</a></li>
-<li>wiserain <a href="mailto:mail275@gmail.com" class="email">mail275@gmail.com</a></li>
-<li>Roel Arents <a href="mailto:roel.arents@kadaster.nl" class="email">roel.arents@kadaster.nl</a></li>
-<li>Shyim <a href="mailto:github@shyim.de" class="email">github@shyim.de</a></li>
-<li>Rintze Zelle <a href="mailto:78232505+rzelle-lallemand@users.noreply.github.com" class="email">78232505+rzelle-lallemand@users.noreply.github.com</a></li>
-<li>Damo <a href="mailto:damoclark@users.noreply.github.com" class="email">damoclark@users.noreply.github.com</a></li>
-<li>WeidiDeng <a href="mailto:weidi_deng@icloud.com" class="email">weidi_deng@icloud.com</a></li>
-<li>Brian Starkey <a href="mailto:stark3y@gmail.com" class="email">stark3y@gmail.com</a></li>
-<li>jladbrook <a href="mailto:jhladbrook@gmail.com" class="email">jhladbrook@gmail.com</a></li>
-<li>Loren Gordon <a href="mailto:lorengordon@users.noreply.github.com" class="email">lorengordon@users.noreply.github.com</a></li>
-<li>dlitster <a href="mailto:davidlitster@gmail.com" class="email">davidlitster@gmail.com</a></li>
-<li>Tobias Gion <a href="mailto:tobias@gion.io" class="email">tobias@gion.io</a></li>
-<li>Jānis Bebrītis <a href="mailto:janis.bebritis@wunder.io" class="email">janis.bebritis@wunder.io</a></li>
-<li>Adam K <a href="mailto:github.com@ak.tidy.email" class="email">github.com@ak.tidy.email</a></li>
-<li>Andrei Smirnov <a href="mailto:smirnov.captain@gmail.com" class="email">smirnov.captain@gmail.com</a></li>
-<li>Janne Hellsten <a href="mailto:jjhellst@gmail.com" class="email">jjhellst@gmail.com</a></li>
-<li>cc <a href="mailto:12904584+shvc@users.noreply.github.com" class="email">12904584+shvc@users.noreply.github.com</a></li>
-<li>Tareq Sharafy <a href="mailto:tareq.sha@gmail.com" class="email">tareq.sha@gmail.com</a></li>
-<li>kapitainsky <a href="mailto:dariuszb@me.com" class="email">dariuszb@me.com</a></li>
-<li>douchen <a href="mailto:playgoobug@gmail.com" class="email">playgoobug@gmail.com</a></li>
-<li>Sam Lai <a href="mailto:70988+slai@users.noreply.github.com" class="email">70988+slai@users.noreply.github.com</a></li>
-<li>URenko <a href="mailto:18209292+URenko@users.noreply.github.com" class="email">18209292+URenko@users.noreply.github.com</a></li>
-<li>Stanislav Gromov <a href="mailto:kullfar@gmail.com" class="email">kullfar@gmail.com</a></li>
-<li>Paulo Schreiner <a href="mailto:paulo.schreiner@delivion.de" class="email">paulo.schreiner@delivion.de</a></li>
-<li>Mariusz Suchodolski <a href="mailto:mariusz@suchodol.ski" class="email">mariusz@suchodol.ski</a></li>
-<li>danielkrajnik <a href="mailto:dan94kra@gmail.com" class="email">dan94kra@gmail.com</a></li>
-<li>Peter Fern <a href="mailto:github@0xc0dedbad.com" class="email">github@0xc0dedbad.com</a></li>
-<li>zzq <a href="mailto:i@zhangzqs.cn" class="email">i@zhangzqs.cn</a></li>
-<li>mac-15 <a href="mailto:usman.ilamdin@phpstudios.com" class="email">usman.ilamdin@phpstudios.com</a></li>
-<li>Sawada Tsunayoshi <a href="mailto:34431649+TsunayoshiSawada@users.noreply.github.com" class="email">34431649+TsunayoshiSawada@users.noreply.github.com</a></li>
-<li>Dean Attali <a href="mailto:daattali@gmail.com" class="email">daattali@gmail.com</a></li>
-<li>Fjodor42 <a href="mailto:molgaard@gmail.com" class="email">molgaard@gmail.com</a></li>
-<li>BakaWang <a href="mailto:wa11579@hotmail.com" class="email">wa11579@hotmail.com</a></li>
-<li>Mahad <a href="mailto:56235065+Mahad-lab@users.noreply.github.com" class="email">56235065+Mahad-lab@users.noreply.github.com</a></li>
-<li>Vladislav Vorobev <a href="mailto:x.miere@gmail.com" class="email">x.miere@gmail.com</a></li>
-<li>darix <a href="mailto:darix@users.noreply.github.com" class="email">darix@users.noreply.github.com</a></li>
-<li>Benjamin <a href="mailto:36415086+bbenjamin-sys@users.noreply.github.com" class="email">36415086+bbenjamin-sys@users.noreply.github.com</a></li>
-<li>Chun-Hung Tseng <a href="mailto:henrybear327@users.noreply.github.com" class="email">henrybear327@users.noreply.github.com</a></li>
-<li>Ricardo D'O. Albanus <a href="mailto:rdalbanus@users.noreply.github.com" class="email">rdalbanus@users.noreply.github.com</a></li>
-<li>gabriel-suela <a href="mailto:gscsuela@gmail.com" class="email">gscsuela@gmail.com</a></li>
-<li>Tiago Boeing <a href="mailto:contato@tiagoboeing.com" class="email">contato@tiagoboeing.com</a></li>
-<li>Edwin Mackenzie-Owen <a href="mailto:edwin.mowen@gmail.com" class="email">edwin.mowen@gmail.com</a></li>
-<li>Niklas Hambüchen <a href="mailto:mail@nh2.me" class="email">mail@nh2.me</a></li>
-<li>yuudi <a href="mailto:yuudi@users.noreply.github.com" class="email">yuudi@users.noreply.github.com</a></li>
-<li>Zach <a href="mailto:github@prozach.org" class="email">github@prozach.org</a></li>
-<li>nielash <a href="mailto:31582349+nielash@users.noreply.github.com" class="email">31582349+nielash@users.noreply.github.com</a></li>
-<li>Julian Lepinski <a href="mailto:lepinsk@users.noreply.github.com" class="email">lepinsk@users.noreply.github.com</a></li>
-<li>Raymond Berger <a href="mailto:RayBB@users.noreply.github.com" class="email">RayBB@users.noreply.github.com</a></li>
-<li>Nihaal Sangha <a href="mailto:nihaal.git@gmail.com" class="email">nihaal.git@gmail.com</a></li>
-<li>Masamune3210 <a href="mailto:1053504+Masamune3210@users.noreply.github.com" class="email">1053504+Masamune3210@users.noreply.github.com</a></li>
-<li>James Braza <a href="mailto:jamesbraza@gmail.com" class="email">jamesbraza@gmail.com</a></li>
-<li>antoinetran <a href="mailto:antoinetran@users.noreply.github.com" class="email">antoinetran@users.noreply.github.com</a></li>
-<li>alexia <a href="mailto:me@alexia.lol" class="email">me@alexia.lol</a></li>
-<li>nielash <a href="mailto:nielronash@gmail.com" class="email">nielronash@gmail.com</a></li>
-<li>Vitor Gomes <a href="mailto:vitor.gomes@delivion.de" class="email">vitor.gomes@delivion.de</a> <a href="mailto:mail@vitorgomes.com" class="email">mail@vitorgomes.com</a></li>
-<li>Jacob Hands <a href="mailto:jacob@gogit.io" class="email">jacob@gogit.io</a></li>
-<li>hideo aoyama <a href="mailto:100831251+boukendesho@users.noreply.github.com" class="email">100831251+boukendesho@users.noreply.github.com</a></li>
-<li>Roberto Ricci <a href="mailto:io@r-ricci.it" class="email">io@r-ricci.it</a></li>
-<li>Bjørn Smith <a href="mailto:bjornsmith@gmail.com" class="email">bjornsmith@gmail.com</a></li>
-<li>Alishan Ladhani <a href="mailto:8869764+aladh@users.noreply.github.com" class="email">8869764+aladh@users.noreply.github.com</a></li>
-<li>zjx20 <a href="mailto:zhoujianxiong2@gmail.com" class="email">zhoujianxiong2@gmail.com</a></li>
-<li>Oksana <a href="mailto:142890647+oks-maytech@users.noreply.github.com" class="email">142890647+oks-maytech@users.noreply.github.com</a></li>
-<li>Volodymyr Kit <a href="mailto:v.kit@maytech.net" class="email">v.kit@maytech.net</a></li>
-<li>David Pedersen <a href="mailto:limero@me.com" class="email">limero@me.com</a></li>
-<li>Drew Stinnett <a href="mailto:drew@drewlink.com" class="email">drew@drewlink.com</a></li>
-<li>Pat Patterson <a href="mailto:pat@backblaze.com" class="email">pat@backblaze.com</a></li>
-<li>Herby Gillot <a href="mailto:herby.gillot@gmail.com" class="email">herby.gillot@gmail.com</a></li>
-<li>Nikita Shoshin <a href="mailto:shoshin_nikita@fastmail.com" class="email">shoshin_nikita@fastmail.com</a></li>
-<li>rinsuki <a href="mailto:428rinsuki+git@gmail.com" class="email">428rinsuki+git@gmail.com</a></li>
-<li>Beyond Meat <a href="mailto:51850644+beyondmeat@users.noreply.github.com" class="email">51850644+beyondmeat@users.noreply.github.com</a></li>
-<li>Saleh Dindar <a href="mailto:salh@fb.com" class="email">salh@fb.com</a></li>
-<li>Volodymyr <a href="mailto:142890760+vkit-maytech@users.noreply.github.com" class="email">142890760+vkit-maytech@users.noreply.github.com</a></li>
-<li>Gabriel Espinoza <a href="mailto:31670639+gspinoza@users.noreply.github.com" class="email">31670639+gspinoza@users.noreply.github.com</a></li>
-<li>Keigo Imai <a href="mailto:keigo.imai@gmail.com" class="email">keigo.imai@gmail.com</a></li>
-<li>Ivan Yanitra <a href="mailto:iyanitra@tesla-consulting.com" class="email">iyanitra@tesla-consulting.com</a></li>
-<li>alfish2000 <a href="mailto:alfish2000@gmail.com" class="email">alfish2000@gmail.com</a></li>
-<li>wuxingzhong <a href="mailto:qq330332812@gmail.com" class="email">qq330332812@gmail.com</a></li>
-<li>Adithya Kumar <a href="mailto:akumar42@protonmail.com" class="email">akumar42@protonmail.com</a></li>
-<li>Tayo-pasedaRJ <a href="mailto:138471223+Tayo-pasedaRJ@users.noreply.github.com" class="email">138471223+Tayo-pasedaRJ@users.noreply.github.com</a></li>
-<li>Peter Kreuser <a href="mailto:logo@kreuser.name" class="email">logo@kreuser.name</a></li>
+<li>Drew Parsons <a href="mailto:dparsons@emerall.com"
+class="email">dparsons@emerall.com</a></li>
+<li>Joel <a href="mailto:joelnb@users.noreply.github.com"
+class="email">joelnb@users.noreply.github.com</a></li>
+<li>wiserain <a href="mailto:mail275@gmail.com"
+class="email">mail275@gmail.com</a></li>
+<li>Roel Arents <a href="mailto:roel.arents@kadaster.nl"
+class="email">roel.arents@kadaster.nl</a></li>
+<li>Shyim <a href="mailto:github@shyim.de"
+class="email">github@shyim.de</a></li>
+<li>Rintze Zelle <a
+href="mailto:78232505+rzelle-lallemand@users.noreply.github.com"
+class="email">78232505+rzelle-lallemand@users.noreply.github.com</a></li>
+<li>Damo <a href="mailto:damoclark@users.noreply.github.com"
+class="email">damoclark@users.noreply.github.com</a></li>
+<li>WeidiDeng <a href="mailto:weidi_deng@icloud.com"
+class="email">weidi_deng@icloud.com</a></li>
+<li>Brian Starkey <a href="mailto:stark3y@gmail.com"
+class="email">stark3y@gmail.com</a></li>
+<li>jladbrook <a href="mailto:jhladbrook@gmail.com"
+class="email">jhladbrook@gmail.com</a></li>
+<li>Loren Gordon <a href="mailto:lorengordon@users.noreply.github.com"
+class="email">lorengordon@users.noreply.github.com</a></li>
+<li>dlitster <a href="mailto:davidlitster@gmail.com"
+class="email">davidlitster@gmail.com</a></li>
+<li>Tobias Gion <a href="mailto:tobias@gion.io"
+class="email">tobias@gion.io</a></li>
+<li>Jānis Bebrītis <a href="mailto:janis.bebritis@wunder.io"
+class="email">janis.bebritis@wunder.io</a></li>
+<li>Adam K <a href="mailto:github.com@ak.tidy.email"
+class="email">github.com@ak.tidy.email</a></li>
+<li>Andrei Smirnov <a href="mailto:smirnov.captain@gmail.com"
+class="email">smirnov.captain@gmail.com</a></li>
+<li>Janne Hellsten <a href="mailto:jjhellst@gmail.com"
+class="email">jjhellst@gmail.com</a></li>
+<li>cc <a href="mailto:12904584+shvc@users.noreply.github.com"
+class="email">12904584+shvc@users.noreply.github.com</a></li>
+<li>Tareq Sharafy <a href="mailto:tareq.sha@gmail.com"
+class="email">tareq.sha@gmail.com</a></li>
+<li>kapitainsky <a href="mailto:dariuszb@me.com"
+class="email">dariuszb@me.com</a></li>
+<li>douchen <a href="mailto:playgoobug@gmail.com"
+class="email">playgoobug@gmail.com</a></li>
+<li>Sam Lai <a href="mailto:70988+slai@users.noreply.github.com"
+class="email">70988+slai@users.noreply.github.com</a></li>
+<li>URenko <a href="mailto:18209292+URenko@users.noreply.github.com"
+class="email">18209292+URenko@users.noreply.github.com</a></li>
+<li>Stanislav Gromov <a href="mailto:kullfar@gmail.com"
+class="email">kullfar@gmail.com</a></li>
+<li>Paulo Schreiner <a href="mailto:paulo.schreiner@delivion.de"
+class="email">paulo.schreiner@delivion.de</a></li>
+<li>Mariusz Suchodolski <a href="mailto:mariusz@suchodol.ski"
+class="email">mariusz@suchodol.ski</a></li>
+<li>danielkrajnik <a href="mailto:dan94kra@gmail.com"
+class="email">dan94kra@gmail.com</a></li>
+<li>Peter Fern <a href="mailto:github@0xc0dedbad.com"
+class="email">github@0xc0dedbad.com</a></li>
+<li>zzq <a href="mailto:i@zhangzqs.cn"
+class="email">i@zhangzqs.cn</a></li>
+<li>mac-15 <a href="mailto:usman.ilamdin@phpstudios.com"
+class="email">usman.ilamdin@phpstudios.com</a></li>
+<li>Sawada Tsunayoshi <a
+href="mailto:34431649+TsunayoshiSawada@users.noreply.github.com"
+class="email">34431649+TsunayoshiSawada@users.noreply.github.com</a></li>
+<li>Dean Attali <a href="mailto:daattali@gmail.com"
+class="email">daattali@gmail.com</a></li>
+<li>Fjodor42 <a href="mailto:molgaard@gmail.com"
+class="email">molgaard@gmail.com</a></li>
+<li>BakaWang <a href="mailto:wa11579@hotmail.com"
+class="email">wa11579@hotmail.com</a></li>
+<li>Mahad <a href="mailto:56235065+Mahad-lab@users.noreply.github.com"
+class="email">56235065+Mahad-lab@users.noreply.github.com</a></li>
+<li>Vladislav Vorobev <a href="mailto:x.miere@gmail.com"
+class="email">x.miere@gmail.com</a></li>
+<li>darix <a href="mailto:darix@users.noreply.github.com"
+class="email">darix@users.noreply.github.com</a></li>
+<li>Benjamin <a
+href="mailto:36415086+bbenjamin-sys@users.noreply.github.com"
+class="email">36415086+bbenjamin-sys@users.noreply.github.com</a></li>
+<li>Chun-Hung Tseng <a
+href="mailto:henrybear327@users.noreply.github.com"
+class="email">henrybear327@users.noreply.github.com</a></li>
+<li>Ricardo D'O. Albanus <a
+href="mailto:rdalbanus@users.noreply.github.com"
+class="email">rdalbanus@users.noreply.github.com</a></li>
+<li>gabriel-suela <a href="mailto:gscsuela@gmail.com"
+class="email">gscsuela@gmail.com</a></li>
+<li>Tiago Boeing <a href="mailto:contato@tiagoboeing.com"
+class="email">contato@tiagoboeing.com</a></li>
+<li>Edwin Mackenzie-Owen <a href="mailto:edwin.mowen@gmail.com"
+class="email">edwin.mowen@gmail.com</a></li>
+<li>Niklas Hambüchen <a href="mailto:mail@nh2.me"
+class="email">mail@nh2.me</a></li>
+<li>yuudi <a href="mailto:yuudi@users.noreply.github.com"
+class="email">yuudi@users.noreply.github.com</a></li>
+<li>Zach <a href="mailto:github@prozach.org"
+class="email">github@prozach.org</a></li>
+<li>nielash <a href="mailto:31582349+nielash@users.noreply.github.com"
+class="email">31582349+nielash@users.noreply.github.com</a></li>
+<li>Julian Lepinski <a href="mailto:lepinsk@users.noreply.github.com"
+class="email">lepinsk@users.noreply.github.com</a></li>
+<li>Raymond Berger <a href="mailto:RayBB@users.noreply.github.com"
+class="email">RayBB@users.noreply.github.com</a></li>
+<li>Nihaal Sangha <a href="mailto:nihaal.git@gmail.com"
+class="email">nihaal.git@gmail.com</a></li>
+<li>Masamune3210 <a
+href="mailto:1053504+Masamune3210@users.noreply.github.com"
+class="email">1053504+Masamune3210@users.noreply.github.com</a></li>
+<li>James Braza <a href="mailto:jamesbraza@gmail.com"
+class="email">jamesbraza@gmail.com</a></li>
+<li>antoinetran <a href="mailto:antoinetran@users.noreply.github.com"
+class="email">antoinetran@users.noreply.github.com</a></li>
+<li>alexia <a href="mailto:me@alexia.lol"
+class="email">me@alexia.lol</a></li>
+<li>nielash <a href="mailto:nielronash@gmail.com"
+class="email">nielronash@gmail.com</a></li>
+<li>Vitor Gomes <a href="mailto:vitor.gomes@delivion.de"
+class="email">vitor.gomes@delivion.de</a> <a
+href="mailto:mail@vitorgomes.com"
+class="email">mail@vitorgomes.com</a></li>
+<li>Jacob Hands <a href="mailto:jacob@gogit.io"
+class="email">jacob@gogit.io</a></li>
+<li>hideo aoyama <a
+href="mailto:100831251+boukendesho@users.noreply.github.com"
+class="email">100831251+boukendesho@users.noreply.github.com</a></li>
+<li>Roberto Ricci <a href="mailto:io@r-ricci.it"
+class="email">io@r-ricci.it</a></li>
+<li>Bjørn Smith <a href="mailto:bjornsmith@gmail.com"
+class="email">bjornsmith@gmail.com</a></li>
+<li>Alishan Ladhani <a
+href="mailto:8869764+aladh@users.noreply.github.com"
+class="email">8869764+aladh@users.noreply.github.com</a></li>
+<li>zjx20 <a href="mailto:zhoujianxiong2@gmail.com"
+class="email">zhoujianxiong2@gmail.com</a></li>
+<li>Oksana <a
+href="mailto:142890647+oks-maytech@users.noreply.github.com"
+class="email">142890647+oks-maytech@users.noreply.github.com</a></li>
+<li>Volodymyr Kit <a href="mailto:v.kit@maytech.net"
+class="email">v.kit@maytech.net</a></li>
+<li>David Pedersen <a href="mailto:limero@me.com"
+class="email">limero@me.com</a></li>
+<li>Drew Stinnett <a href="mailto:drew@drewlink.com"
+class="email">drew@drewlink.com</a></li>
+<li>Pat Patterson <a href="mailto:pat@backblaze.com"
+class="email">pat@backblaze.com</a></li>
+<li>Herby Gillot <a href="mailto:herby.gillot@gmail.com"
+class="email">herby.gillot@gmail.com</a></li>
+<li>Nikita Shoshin <a href="mailto:shoshin_nikita@fastmail.com"
+class="email">shoshin_nikita@fastmail.com</a></li>
+<li>rinsuki <a href="mailto:428rinsuki+git@gmail.com"
+class="email">428rinsuki+git@gmail.com</a></li>
+<li>Beyond Meat <a
+href="mailto:51850644+beyondmeat@users.noreply.github.com"
+class="email">51850644+beyondmeat@users.noreply.github.com</a></li>
+<li>Saleh Dindar <a href="mailto:salh@fb.com"
+class="email">salh@fb.com</a></li>
+<li>Volodymyr <a
+href="mailto:142890760+vkit-maytech@users.noreply.github.com"
+class="email">142890760+vkit-maytech@users.noreply.github.com</a></li>
+<li>Gabriel Espinoza <a
+href="mailto:31670639+gspinoza@users.noreply.github.com"
+class="email">31670639+gspinoza@users.noreply.github.com</a></li>
+<li>Keigo Imai <a href="mailto:keigo.imai@gmail.com"
+class="email">keigo.imai@gmail.com</a></li>
+<li>Ivan Yanitra <a href="mailto:iyanitra@tesla-consulting.com"
+class="email">iyanitra@tesla-consulting.com</a></li>
+<li>alfish2000 <a href="mailto:alfish2000@gmail.com"
+class="email">alfish2000@gmail.com</a></li>
+<li>wuxingzhong <a href="mailto:qq330332812@gmail.com"
+class="email">qq330332812@gmail.com</a></li>
+<li>Adithya Kumar <a href="mailto:akumar42@protonmail.com"
+class="email">akumar42@protonmail.com</a></li>
+<li>Tayo-pasedaRJ <a
+href="mailto:138471223+Tayo-pasedaRJ@users.noreply.github.com"
+class="email">138471223+Tayo-pasedaRJ@users.noreply.github.com</a></li>
+<li>Peter Kreuser <a href="mailto:logo@kreuser.name"
+class="email">logo@kreuser.name</a></li>
 <li>Piyush <piyushgarg80></li>
-<li>fotile96 <a href="mailto:fotile96@users.noreply.github.com" class="email">fotile96@users.noreply.github.com</a></li>
-<li>Luc Ritchie <a href="mailto:luc.ritchie@gmail.com" class="email">luc.ritchie@gmail.com</a></li>
-<li>cynful <a href="mailto:cynful@users.noreply.github.com" class="email">cynful@users.noreply.github.com</a></li>
-<li>wjielai <a href="mailto:wjielai@tencent.com" class="email">wjielai@tencent.com</a></li>
-<li>Jack Deng <a href="mailto:jackdeng@gmail.com" class="email">jackdeng@gmail.com</a></li>
-<li>Mikubill <a href="mailto:31246794+Mikubill@users.noreply.github.com" class="email">31246794+Mikubill@users.noreply.github.com</a></li>
-<li>Artur Neumann <a href="mailto:artur@jankaritech.com" class="email">artur@jankaritech.com</a></li>
-<li>Saw-jan <a href="mailto:saw.jan.grg3e@gmail.com" class="email">saw.jan.grg3e@gmail.com</a></li>
-<li>Oksana Zhykina <a href="mailto:o.zhykina@maytech.net" class="email">o.zhykina@maytech.net</a></li>
-<li>karan <a href="mailto:karan.gupta92@gmail.com" class="email">karan.gupta92@gmail.com</a></li>
-<li>viktor <a href="mailto:viktor@yakovchuk.net" class="email">viktor@yakovchuk.net</a></li>
-<li>moongdal <a href="mailto:moongdal@tutanota.com" class="email">moongdal@tutanota.com</a></li>
-<li>Mina Galić <a href="mailto:freebsd@igalic.co" class="email">freebsd@igalic.co</a></li>
-<li>Alen Šiljak <a href="mailto:dev@alensiljak.eu.org" class="email">dev@alensiljak.eu.org</a></li>
-<li>你知道未来吗 <a href="mailto:rkonfj@gmail.com" class="email">rkonfj@gmail.com</a></li>
-<li>Abhinav Dhiman <a href="mailto:8640877+ahnv@users.noreply.github.com" class="email">8640877+ahnv@users.noreply.github.com</a></li>
-<li>halms <a href="mailto:7513146+halms@users.noreply.github.com" class="email">7513146+halms@users.noreply.github.com</a></li>
-<li>ben-ba <a href="mailto:benjamin.brauner@gmx.de" class="email">benjamin.brauner@gmx.de</a></li>
-<li>Eli Orzitzer <a href="mailto:e_orz@yahoo.com" class="email">e_orz@yahoo.com</a></li>
-<li>Anthony Metzidis <a href="mailto:anthony.metzidis@gmail.com" class="email">anthony.metzidis@gmail.com</a></li>
-<li>emyarod <a href="mailto:afw5059@gmail.com" class="email">afw5059@gmail.com</a></li>
-<li>keongalvin <a href="mailto:keongalvin@gmail.com" class="email">keongalvin@gmail.com</a></li>
-<li>rarspace01 <a href="mailto:rarspace01@users.noreply.github.com" class="email">rarspace01@users.noreply.github.com</a></li>
-<li>Paul Stern <a href="mailto:paulstern45@gmail.com" class="email">paulstern45@gmail.com</a></li>
-<li>Nikhil Ahuja <a href="mailto:nikhilahuja@live.com" class="email">nikhilahuja@live.com</a></li>
-<li>Harshit Budhraja <a href="mailto:52413945+harshit-budhraja@users.noreply.github.com" class="email">52413945+harshit-budhraja@users.noreply.github.com</a></li>
-<li>Tera <a href="mailto:24725862+teraa@users.noreply.github.com" class="email">24725862+teraa@users.noreply.github.com</a></li>
-<li>Kyle Reynolds <a href="mailto:kylereynoldsdev@gmail.com" class="email">kylereynoldsdev@gmail.com</a></li>
-<li>Michael Eischer <a href="mailto:michael.eischer@gmx.de" class="email">michael.eischer@gmx.de</a></li>
-<li>Thomas Müller <a href="mailto:1005065+DeepDiver1975@users.noreply.github.com" class="email">1005065+DeepDiver1975@users.noreply.github.com</a></li>
-<li>DanielEgbers <a href="mailto:27849724+DanielEgbers@users.noreply.github.com" class="email">27849724+DanielEgbers@users.noreply.github.com</a></li>
-<li>Jack Provance <a href="mailto:49460795+njprov@users.noreply.github.com" class="email">49460795+njprov@users.noreply.github.com</a></li>
-<li>Gabriel Ramos <a href="mailto:109390599+gabrielramos02@users.noreply.github.com" class="email">109390599+gabrielramos02@users.noreply.github.com</a></li>
-<li>Dan McArdle <a href="mailto:d@nmcardle.com" class="email">d@nmcardle.com</a></li>
-<li>Joe Cai <a href="mailto:joe.cai@bigcommerce.com" class="email">joe.cai@bigcommerce.com</a></li>
-<li>Anders Swanson <a href="mailto:anders.swanson@oracle.com" class="email">anders.swanson@oracle.com</a></li>
-<li>huajin tong <a href="mailto:137764712+thirdkeyword@users.noreply.github.com" class="email">137764712+thirdkeyword@users.noreply.github.com</a></li>
-<li>John-Paul Smith <a href="mailto:john-paulsmith@users.noreply.github.com" class="email">john-paulsmith@users.noreply.github.com</a></li>
-<li>racerole <a href="mailto:148756161+racerole@users.noreply.github.com" class="email">148756161+racerole@users.noreply.github.com</a></li>
-<li>Gachoud Philippe <a href="mailto:ph.gachoud@gmail.com" class="email">ph.gachoud@gmail.com</a></li>
-<li>YukiUnHappy <a href="mailto:saberhana@yandex.com" class="email">saberhana@yandex.com</a></li>
-<li>Kyle Reynolds <a href="mailto:kyle.reynolds@bridgerphotonics.com" class="email">kyle.reynolds@bridgerphotonics.com</a></li>
-<li>Lewis Hook <a href="mailto:lewis@hook.im" class="email">lewis@hook.im</a></li>
-<li>hoyho <a href="mailto:luohaihao@gmail.com" class="email">luohaihao@gmail.com</a></li>
-<li>Vitaly <a href="mailto:9034218+gvitali@users.noreply.github.com" class="email">9034218+gvitali@users.noreply.github.com</a></li>
-<li>iotmaestro <a href="mailto:iotmaestro@proton.me" class="email">iotmaestro@proton.me</a></li>
-<li>psychopatt <a href="mailto:66741203+psychopatt@users.noreply.github.com" class="email">66741203+psychopatt@users.noreply.github.com</a></li>
-<li>Alex Garel <a href="mailto:alex@garel.org" class="email">alex@garel.org</a></li>
-<li>Warrentheo <a href="mailto:warrentheo@hotmail.com" class="email">warrentheo@hotmail.com</a></li>
-<li>Alexandre Lavigne <a href="mailto:lavigne958@gmail.com" class="email">lavigne958@gmail.com</a></li>
-<li>yoelvini <a href="mailto:134453420+yoelvini@users.noreply.github.com" class="email">134453420+yoelvini@users.noreply.github.com</a></li>
-<li>Erisa A <a href="mailto:erisa@cloudflare.com" class="email">erisa@cloudflare.com</a></li>
-<li>Pieter van Oostrum <a href="mailto:pieter@vanoostrum.org" class="email">pieter@vanoostrum.org</a></li>
-<li>jakzoe <a href="mailto:155812065+jakzoe@users.noreply.github.com" class="email">155812065+jakzoe@users.noreply.github.com</a></li>
-<li>guangwu <a href="mailto:guoguangwu@magic-shield.com" class="email">guoguangwu@magic-shield.com</a></li>
-<li>static-moonlight <a href="mailto:107991124+static-moonlight@users.noreply.github.com" class="email">107991124+static-moonlight@users.noreply.github.com</a></li>
-<li>yudrywet <a href="mailto:yudeyao@yeah.net" class="email">yudeyao@yeah.net</a></li>
-<li>Butanediol <a href="mailto:git@xnh.app" class="email">git@xnh.app</a></li>
-<li>Dave Nicolson <a href="mailto:david.nicolson@gmail.com" class="email">david.nicolson@gmail.com</a></li>
-<li>Katia Esposito <a href="mailto:katia@linux.com" class="email">katia@linux.com</a></li>
-<li>pawsey-kbuckley <a href="mailto:36438302+pawsey-kbuckley@users.noreply.github.com" class="email">36438302+pawsey-kbuckley@users.noreply.github.com</a></li>
-<li>hidewrong <a href="mailto:167099254+hidewrong@users.noreply.github.com" class="email">167099254+hidewrong@users.noreply.github.com</a></li>
-<li>Michael Terry <a href="mailto:mike@mterry.name" class="email">mike@mterry.name</a></li>
-<li>Sunny <a href="mailto:25066078+LoSunny@users.noreply.github.com" class="email">25066078+LoSunny@users.noreply.github.com</a></li>
-<li>overallteach <a href="mailto:cricis@foxmail.com" class="email">cricis@foxmail.com</a></li>
-<li>JT Olio <a href="mailto:jt@olio.lol" class="email">jt@olio.lol</a></li>
-<li>Evan McBeth <a href="mailto:64177332+AtomicRobotMan0101@users.noreply.github.com" class="email">64177332+AtomicRobotMan0101@users.noreply.github.com</a></li>
-<li>Dominik Joe Pantůček <a href="mailto:dominik.pantucek@trustica.cz" class="email">dominik.pantucek@trustica.cz</a></li>
-<li>yumeiyin <a href="mailto:155420652+yumeiyin@users.noreply.github.com" class="email">155420652+yumeiyin@users.noreply.github.com</a></li>
-<li>Bruno Fernandes <a href="mailto:54373093+folkzb@users.noreply.github.com" class="email">54373093+folkzb@users.noreply.github.com</a></li>
-<li>Thomas Schneider <a href="mailto:tspam.github@brainfuck.space" class="email">tspam.github@brainfuck.space</a></li>
-<li>Charles Hamilton <a href="mailto:52973156+chamilton-ccn@users.noreply.github.com" class="email">52973156+chamilton-ccn@users.noreply.github.com</a></li>
-<li>Tomasz Melcer <a href="mailto:tomasz@melcer.pl" class="email">tomasz@melcer.pl</a></li>
-<li>Michał Dzienisiewicz <a href="mailto:michal.piotr.dz@gmail.com" class="email">michal.piotr.dz@gmail.com</a></li>
-<li>Florian Klink <a href="mailto:flokli@flokli.de" class="email">flokli@flokli.de</a></li>
-<li>Bill Fraser <a href="mailto:bill@wfraser.dev" class="email">bill@wfraser.dev</a></li>
-<li>Thearas <a href="mailto:thearas850@gmail.com" class="email">thearas850@gmail.com</a></li>
-<li>Filipe Herculano <a href="mailto:fifo_@live.com" class="email">fifo_@live.com</a></li>
-<li>Russ Bubley <a href="mailto:russ.bubley@googlemail.com" class="email">russ.bubley@googlemail.com</a></li>
-<li>Paul Collins <a href="mailto:paul.collins@canonical.com" class="email">paul.collins@canonical.com</a></li>
-<li>Tomasz Melcer <a href="mailto:liori@exroot.org" class="email">liori@exroot.org</a></li>
-<li>itsHenry <a href="mailto:2671230065@qq.com" class="email">2671230065@qq.com</a></li>
-<li>Ke Wang <a href="mailto:me@ke.wang" class="email">me@ke.wang</a></li>
-<li>AThePeanut4 <a href="mailto:49614525+AThePeanut4@users.noreply.github.com" class="email">49614525+AThePeanut4@users.noreply.github.com</a></li>
-<li>Tobias Markus <a href="mailto:tobbi.bugs@googlemail.com" class="email">tobbi.bugs@googlemail.com</a></li>
-<li>Ernie Hershey <a href="mailto:github@ernie.org" class="email">github@ernie.org</a></li>
-<li>Will Miles <a href="mailto:wmiles@sgl.com" class="email">wmiles@sgl.com</a></li>
-<li>David Seifert <a href="mailto:16636962+SoapGentoo@users.noreply.github.com" class="email">16636962+SoapGentoo@users.noreply.github.com</a></li>
-<li>Fornax <a href="mailto:wimbrand96@gmail.com" class="email">wimbrand96@gmail.com</a></li>
-<li>Sam Harrison <a href="mailto:sam.harrison@files.com" class="email">sam.harrison@files.com</a></li>
-<li>Péter Bozsó <a href="mailto:3806723+peterbozso@users.noreply.github.com" class="email">3806723+peterbozso@users.noreply.github.com</a></li>
-<li>Georg Welzel <a href="mailto:gwelzel@mailbox.org" class="email">gwelzel@mailbox.org</a></li>
-<li>John Oxley <a href="mailto:john.oxley@gmail.com" class="email">john.oxley@gmail.com</a> <a href="mailto:joxley@meta.com" class="email">joxley@meta.com</a></li>
-<li>Pawel Palucha <a href="mailto:pawel.palucha@aetion.com" class="email">pawel.palucha@aetion.com</a></li>
-<li>crystalstall <a href="mailto:crystalruby@qq.com" class="email">crystalruby@qq.com</a></li>
-<li>nipil <a href="mailto:nipil@users.noreply.github.com" class="email">nipil@users.noreply.github.com</a></li>
-<li>yuval-cloudinary <a href="mailto:46710068+yuval-cloudinary@users.noreply.github.com" class="email">46710068+yuval-cloudinary@users.noreply.github.com</a></li>
-<li>Mathieu Moreau <a href="mailto:mrx23dot@users.noreply.github.com" class="email">mrx23dot@users.noreply.github.com</a></li>
-<li>fsantagostinobietti <a href="mailto:6057026+fsantagostinobietti@users.noreply.github.com" class="email">6057026+fsantagostinobietti@users.noreply.github.com</a></li>
-<li>Oleg Kunitsyn <a href="mailto:114359669+hiddenmarten@users.noreply.github.com" class="email">114359669+hiddenmarten@users.noreply.github.com</a></li>
+<li>fotile96 <a href="mailto:fotile96@users.noreply.github.com"
+class="email">fotile96@users.noreply.github.com</a></li>
+<li>Luc Ritchie <a href="mailto:luc.ritchie@gmail.com"
+class="email">luc.ritchie@gmail.com</a></li>
+<li>cynful <a href="mailto:cynful@users.noreply.github.com"
+class="email">cynful@users.noreply.github.com</a></li>
+<li>wjielai <a href="mailto:wjielai@tencent.com"
+class="email">wjielai@tencent.com</a></li>
+<li>Jack Deng <a href="mailto:jackdeng@gmail.com"
+class="email">jackdeng@gmail.com</a></li>
+<li>Mikubill <a href="mailto:31246794+Mikubill@users.noreply.github.com"
+class="email">31246794+Mikubill@users.noreply.github.com</a></li>
+<li>Artur Neumann <a href="mailto:artur@jankaritech.com"
+class="email">artur@jankaritech.com</a></li>
+<li>Saw-jan <a href="mailto:saw.jan.grg3e@gmail.com"
+class="email">saw.jan.grg3e@gmail.com</a></li>
+<li>Oksana Zhykina <a href="mailto:o.zhykina@maytech.net"
+class="email">o.zhykina@maytech.net</a></li>
+<li>karan <a href="mailto:karan.gupta92@gmail.com"
+class="email">karan.gupta92@gmail.com</a></li>
+<li>viktor <a href="mailto:viktor@yakovchuk.net"
+class="email">viktor@yakovchuk.net</a></li>
+<li>moongdal <a href="mailto:moongdal@tutanota.com"
+class="email">moongdal@tutanota.com</a></li>
+<li>Mina Galić <a href="mailto:freebsd@igalic.co"
+class="email">freebsd@igalic.co</a></li>
+<li>Alen Šiljak <a href="mailto:dev@alensiljak.eu.org"
+class="email">dev@alensiljak.eu.org</a></li>
+<li>你知道未来吗 <a href="mailto:rkonfj@gmail.com"
+class="email">rkonfj@gmail.com</a></li>
+<li>Abhinav Dhiman <a
+href="mailto:8640877+ahnv@users.noreply.github.com"
+class="email">8640877+ahnv@users.noreply.github.com</a></li>
+<li>halms <a href="mailto:7513146+halms@users.noreply.github.com"
+class="email">7513146+halms@users.noreply.github.com</a></li>
+<li>ben-ba <a href="mailto:benjamin.brauner@gmx.de"
+class="email">benjamin.brauner@gmx.de</a></li>
+<li>Eli Orzitzer <a href="mailto:e_orz@yahoo.com"
+class="email">e_orz@yahoo.com</a></li>
+<li>Anthony Metzidis <a href="mailto:anthony.metzidis@gmail.com"
+class="email">anthony.metzidis@gmail.com</a></li>
+<li>emyarod <a href="mailto:afw5059@gmail.com"
+class="email">afw5059@gmail.com</a></li>
+<li>keongalvin <a href="mailto:keongalvin@gmail.com"
+class="email">keongalvin@gmail.com</a></li>
+<li>rarspace01 <a href="mailto:rarspace01@users.noreply.github.com"
+class="email">rarspace01@users.noreply.github.com</a></li>
+<li>Paul Stern <a href="mailto:paulstern45@gmail.com"
+class="email">paulstern45@gmail.com</a></li>
+<li>Nikhil Ahuja <a href="mailto:nikhilahuja@live.com"
+class="email">nikhilahuja@live.com</a></li>
+<li>Harshit Budhraja <a
+href="mailto:52413945+harshit-budhraja@users.noreply.github.com"
+class="email">52413945+harshit-budhraja@users.noreply.github.com</a></li>
+<li>Tera <a href="mailto:24725862+teraa@users.noreply.github.com"
+class="email">24725862+teraa@users.noreply.github.com</a></li>
+<li>Kyle Reynolds <a href="mailto:kylereynoldsdev@gmail.com"
+class="email">kylereynoldsdev@gmail.com</a></li>
+<li>Michael Eischer <a href="mailto:michael.eischer@gmx.de"
+class="email">michael.eischer@gmx.de</a></li>
+<li>Thomas Müller <a
+href="mailto:1005065+DeepDiver1975@users.noreply.github.com"
+class="email">1005065+DeepDiver1975@users.noreply.github.com</a></li>
+<li>DanielEgbers <a
+href="mailto:27849724+DanielEgbers@users.noreply.github.com"
+class="email">27849724+DanielEgbers@users.noreply.github.com</a></li>
+<li>Jack Provance <a
+href="mailto:49460795+njprov@users.noreply.github.com"
+class="email">49460795+njprov@users.noreply.github.com</a></li>
+<li>Gabriel Ramos <a
+href="mailto:109390599+gabrielramos02@users.noreply.github.com"
+class="email">109390599+gabrielramos02@users.noreply.github.com</a></li>
+<li>Dan McArdle <a href="mailto:d@nmcardle.com"
+class="email">d@nmcardle.com</a></li>
+<li>Joe Cai <a href="mailto:joe.cai@bigcommerce.com"
+class="email">joe.cai@bigcommerce.com</a></li>
+<li>Anders Swanson <a href="mailto:anders.swanson@oracle.com"
+class="email">anders.swanson@oracle.com</a></li>
+<li>huajin tong <a
+href="mailto:137764712+thirdkeyword@users.noreply.github.com"
+class="email">137764712+thirdkeyword@users.noreply.github.com</a></li>
+<li>John-Paul Smith <a
+href="mailto:john-paulsmith@users.noreply.github.com"
+class="email">john-paulsmith@users.noreply.github.com</a></li>
+<li>racerole <a
+href="mailto:148756161+racerole@users.noreply.github.com"
+class="email">148756161+racerole@users.noreply.github.com</a></li>
+<li>Gachoud Philippe <a href="mailto:ph.gachoud@gmail.com"
+class="email">ph.gachoud@gmail.com</a></li>
+<li>YukiUnHappy <a href="mailto:saberhana@yandex.com"
+class="email">saberhana@yandex.com</a></li>
+<li>Kyle Reynolds <a href="mailto:kyle.reynolds@bridgerphotonics.com"
+class="email">kyle.reynolds@bridgerphotonics.com</a></li>
+<li>Lewis Hook <a href="mailto:lewis@hook.im"
+class="email">lewis@hook.im</a></li>
+<li>hoyho <a href="mailto:luohaihao@gmail.com"
+class="email">luohaihao@gmail.com</a></li>
+<li>Vitaly <a href="mailto:9034218+gvitali@users.noreply.github.com"
+class="email">9034218+gvitali@users.noreply.github.com</a></li>
+<li>iotmaestro <a href="mailto:iotmaestro@proton.me"
+class="email">iotmaestro@proton.me</a></li>
+<li>psychopatt <a
+href="mailto:66741203+psychopatt@users.noreply.github.com"
+class="email">66741203+psychopatt@users.noreply.github.com</a></li>
+<li>Alex Garel <a href="mailto:alex@garel.org"
+class="email">alex@garel.org</a></li>
+<li>Warrentheo <a href="mailto:warrentheo@hotmail.com"
+class="email">warrentheo@hotmail.com</a></li>
+<li>Alexandre Lavigne <a href="mailto:lavigne958@gmail.com"
+class="email">lavigne958@gmail.com</a></li>
+<li>yoelvini <a
+href="mailto:134453420+yoelvini@users.noreply.github.com"
+class="email">134453420+yoelvini@users.noreply.github.com</a></li>
+<li>Erisa A <a href="mailto:erisa@cloudflare.com"
+class="email">erisa@cloudflare.com</a></li>
+<li>Pieter van Oostrum <a href="mailto:pieter@vanoostrum.org"
+class="email">pieter@vanoostrum.org</a></li>
+<li>jakzoe <a href="mailto:155812065+jakzoe@users.noreply.github.com"
+class="email">155812065+jakzoe@users.noreply.github.com</a></li>
+<li>guangwu <a href="mailto:guoguangwu@magic-shield.com"
+class="email">guoguangwu@magic-shield.com</a></li>
+<li>static-moonlight <a
+href="mailto:107991124+static-moonlight@users.noreply.github.com"
+class="email">107991124+static-moonlight@users.noreply.github.com</a></li>
+<li>yudrywet <a href="mailto:yudeyao@yeah.net"
+class="email">yudeyao@yeah.net</a></li>
+<li>Butanediol <a href="mailto:git@xnh.app"
+class="email">git@xnh.app</a></li>
+<li>Dave Nicolson <a href="mailto:david.nicolson@gmail.com"
+class="email">david.nicolson@gmail.com</a></li>
+<li>Katia Esposito <a href="mailto:katia@linux.com"
+class="email">katia@linux.com</a></li>
+<li>pawsey-kbuckley <a
+href="mailto:36438302+pawsey-kbuckley@users.noreply.github.com"
+class="email">36438302+pawsey-kbuckley@users.noreply.github.com</a></li>
+<li>hidewrong <a
+href="mailto:167099254+hidewrong@users.noreply.github.com"
+class="email">167099254+hidewrong@users.noreply.github.com</a></li>
+<li>Michael Terry <a href="mailto:mike@mterry.name"
+class="email">mike@mterry.name</a></li>
+<li>Sunny <a href="mailto:25066078+LoSunny@users.noreply.github.com"
+class="email">25066078+LoSunny@users.noreply.github.com</a></li>
+<li>overallteach <a href="mailto:cricis@foxmail.com"
+class="email">cricis@foxmail.com</a></li>
+<li>JT Olio <a href="mailto:jt@olio.lol"
+class="email">jt@olio.lol</a></li>
+<li>Evan McBeth <a
+href="mailto:64177332+AtomicRobotMan0101@users.noreply.github.com"
+class="email">64177332+AtomicRobotMan0101@users.noreply.github.com</a></li>
+<li>Dominik Joe Pantůček <a href="mailto:dominik.pantucek@trustica.cz"
+class="email">dominik.pantucek@trustica.cz</a></li>
+<li>yumeiyin <a
+href="mailto:155420652+yumeiyin@users.noreply.github.com"
+class="email">155420652+yumeiyin@users.noreply.github.com</a></li>
+<li>Bruno Fernandes <a
+href="mailto:54373093+folkzb@users.noreply.github.com"
+class="email">54373093+folkzb@users.noreply.github.com</a></li>
+<li>Thomas Schneider <a href="mailto:tspam.github@brainfuck.space"
+class="email">tspam.github@brainfuck.space</a></li>
+<li>Charles Hamilton <a
+href="mailto:52973156+chamilton-ccn@users.noreply.github.com"
+class="email">52973156+chamilton-ccn@users.noreply.github.com</a></li>
+<li>Tomasz Melcer <a href="mailto:tomasz@melcer.pl"
+class="email">tomasz@melcer.pl</a></li>
+<li>Michał Dzienisiewicz <a href="mailto:michal.piotr.dz@gmail.com"
+class="email">michal.piotr.dz@gmail.com</a></li>
+<li>Florian Klink <a href="mailto:flokli@flokli.de"
+class="email">flokli@flokli.de</a></li>
+<li>Bill Fraser <a href="mailto:bill@wfraser.dev"
+class="email">bill@wfraser.dev</a></li>
+<li>Thearas <a href="mailto:thearas850@gmail.com"
+class="email">thearas850@gmail.com</a></li>
+<li>Filipe Herculano <a href="mailto:fifo_@live.com"
+class="email">fifo_@live.com</a></li>
+<li>Russ Bubley <a href="mailto:russ.bubley@googlemail.com"
+class="email">russ.bubley@googlemail.com</a></li>
+<li>Paul Collins <a href="mailto:paul.collins@canonical.com"
+class="email">paul.collins@canonical.com</a></li>
+<li>Tomasz Melcer <a href="mailto:liori@exroot.org"
+class="email">liori@exroot.org</a></li>
+<li>itsHenry <a href="mailto:2671230065@qq.com"
+class="email">2671230065@qq.com</a></li>
+<li>Ke Wang <a href="mailto:me@ke.wang"
+class="email">me@ke.wang</a></li>
+<li>AThePeanut4 <a
+href="mailto:49614525+AThePeanut4@users.noreply.github.com"
+class="email">49614525+AThePeanut4@users.noreply.github.com</a></li>
+<li>Tobias Markus <a href="mailto:tobbi.bugs@googlemail.com"
+class="email">tobbi.bugs@googlemail.com</a></li>
+<li>Ernie Hershey <a href="mailto:github@ernie.org"
+class="email">github@ernie.org</a></li>
+<li>Will Miles <a href="mailto:wmiles@sgl.com"
+class="email">wmiles@sgl.com</a></li>
+<li>David Seifert <a
+href="mailto:16636962+SoapGentoo@users.noreply.github.com"
+class="email">16636962+SoapGentoo@users.noreply.github.com</a></li>
+<li>Fornax <a href="mailto:wimbrand96@gmail.com"
+class="email">wimbrand96@gmail.com</a></li>
+<li>Sam Harrison <a href="mailto:sam.harrison@files.com"
+class="email">sam.harrison@files.com</a></li>
+<li>Péter Bozsó <a
+href="mailto:3806723+peterbozso@users.noreply.github.com"
+class="email">3806723+peterbozso@users.noreply.github.com</a></li>
+<li>Georg Welzel <a href="mailto:gwelzel@mailbox.org"
+class="email">gwelzel@mailbox.org</a></li>
+<li>John Oxley <a href="mailto:john.oxley@gmail.com"
+class="email">john.oxley@gmail.com</a> <a href="mailto:joxley@meta.com"
+class="email">joxley@meta.com</a></li>
+<li>Pawel Palucha <a href="mailto:pawel.palucha@aetion.com"
+class="email">pawel.palucha@aetion.com</a></li>
+<li>crystalstall <a href="mailto:crystalruby@qq.com"
+class="email">crystalruby@qq.com</a></li>
+<li>nipil <a href="mailto:nipil@users.noreply.github.com"
+class="email">nipil@users.noreply.github.com</a></li>
+<li>yuval-cloudinary <a
+href="mailto:46710068+yuval-cloudinary@users.noreply.github.com"
+class="email">46710068+yuval-cloudinary@users.noreply.github.com</a></li>
+<li>Mathieu Moreau <a href="mailto:mrx23dot@users.noreply.github.com"
+class="email">mrx23dot@users.noreply.github.com</a></li>
+<li>fsantagostinobietti <a
+href="mailto:6057026+fsantagostinobietti@users.noreply.github.com"
+class="email">6057026+fsantagostinobietti@users.noreply.github.com</a></li>
+<li>Oleg Kunitsyn <a
+href="mailto:114359669+hiddenmarten@users.noreply.github.com"
+class="email">114359669+hiddenmarten@users.noreply.github.com</a></li>
 </ul>
 <h1 id="contact-the-rclone-project">Contact the rclone project</h1>
 <h2 id="forum">Forum</h2>
@@ -46115,13 +64831,17 @@ THE SOFTWARE.</code></pre>
 <h2 id="twitter">Twitter</h2>
 <p>You can also follow Nick on twitter for rclone announcements:</p>
 <ul>
-<li><span class="citation" data-cites="njcw">[@njcw]</span>(https://twitter.com/njcw)</li>
+<li><a href="https://twitter.com/njcw"><span class="citation"
+data-cites="njcw">@njcw</span></a></li>
 </ul>
 <h2 id="email">Email</h2>
-<p>Or if all else fails or you want to ask something private or confidential</p>
+<p>Or if all else fails or you want to ask something private or
+confidential</p>
 <ul>
 <li>info@rclone.com</li>
 </ul>
-<p>Please don't email requests for help to this address - those are better directed to the forum unless you'd like to sign up for business support.</p>
+<p>Please don't email requests for help to this address - those are
+better directed to the forum unless you'd like to sign up for business
+support.</p>
 </body>
 </html>
diff --git a/MANUAL.md b/MANUAL.md
index ae77f8531..db8468c13 100644
--- a/MANUAL.md
+++ b/MANUAL.md
@@ -1,6 +1,6 @@
 % rclone(1) User Manual
 % Nick Craig-Wood
-% Nov 15, 2024
+% Jan 10, 2025
 
 # Rclone syncs your files to cloud storage
 
@@ -120,6 +120,7 @@ WebDAV or S3, that work out of the box.)
 - Enterprise File Fabric
 - Fastmail Files
 - Files.com
+- FrostFS
 - FTP
 - Gofile
 - Google Cloud Storage
@@ -20497,7 +20498,7 @@ Flags for general networking and HTTP stuff.
       --tpslimit float                     Limit HTTP transactions per second to this
       --tpslimit-burst int                 Max burst of transactions for --tpslimit (default 1)
       --use-cookies                        Enable session cookiejar
-      --user-agent string                  Set the user-agent to a specified string (default "rclone/v1.68.2")
+      --user-agent string                  Set the user-agent to a specified string (default "rclone/v1.68.2-beta.8331.25cf42493.feature/add-frostfs-support")
 ```
 
 
@@ -20934,6 +20935,21 @@ Backend-only flags (these can be set in the config file also).
       --filescom-password string                            The password used to authenticate with Files.com (obscured)
       --filescom-site string                                Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com)
       --filescom-username string                            The username used to authenticate with Files.com
+      --frostfs-address string                              Address of account
+      --frostfs-ape-cache-invalidation-duration Duration    APE cache invalidation duration (default 8s)
+      --frostfs-ape-cache-invalidation-timeout Duration     APE cache invalidation timeout (default 24s)
+      --frostfs-ape-chain-check-interval Duration           The interval for verifying that the APE chain is saved in FrostFS (default 500ms)
+      --frostfs-connection-timeout Duration                 FrostFS connection timeout (default 4s)
+      --frostfs-container-creation-policy string            Container creation policy for new containers (default "private")
+      --frostfs-description string                          Description of the remote
+      --frostfs-endpoint string                             Endpoints to connect to FrostFS node
+      --frostfs-password string                             Password to decrypt wallet
+      --frostfs-placement-policy string                     Placement policy for new containers (default "REP 3")
+      --frostfs-rebalance-interval Duration                 FrostFS rebalance connections interval (default 15s)
+      --frostfs-request-timeout Duration                    FrostFS request timeout (default 12s)
+      --frostfs-rpc-endpoint string                         Endpoint to connect to Neo rpc node
+      --frostfs-session-expiration int                      FrostFS session expiration epoch (default 4294967295)
+      --frostfs-wallet string                               Path to wallet
       --ftp-ask-password                                    Allow asking for FTP password when needed
       --ftp-close-timeout Duration                          Maximum time to wait for a response to close (default 1m0s)
       --ftp-concurrency int                                 Maximum number of FTP simultaneous connections, 0 for unlimited
@@ -34604,6 +34620,467 @@ Properties:
 
 
 
+#  FrostFS
+
+Rclone FrostFS support is provided using the
+[git.frostfs.info/TrueCloudLab/frostfs-sdk-go](https://git.frostfs.info/TrueCloudLab/frostfs-sdk-go) package
+
+## Configuration
+
+To create an FrostFS configuration named `remote`, run
+
+    rclone config
+
+Rclone config guides you through an interactive setup process. A minimal
+rclone FrostFS remote definition only requires endpoint and path to FrostFS user wallet.
+
+
+```
+No remotes found, make a new one?
+n) New remote
+s) Set configuration password
+q) Quit config
+n/s/q> n
+
+Enter name for new remote.
+name> remote
+
+Option Storage.
+Type of storage to configure.
+Choose a number from below, or type in your own value.
+ 1 / 1Fichier
+   \ (fichier)
+ 2 / Akamai NetStorage
+   \ (netstorage)
+ 3 / Alias for an existing remote
+   \ (alias)
+ 4 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others
+   \ (s3)
+ 5 / Backblaze B2
+   \ (b2)
+ 6 / Better checksums for other remotes
+   \ (hasher)
+ 7 / Box
+   \ (box)
+ 8 / Cache a remote
+   \ (cache)
+ 9 / Citrix Sharefile
+   \ (sharefile)
+10 / Combine several remotes into one
+   \ (combine)
+11 / Compress a remote
+   \ (compress)
+12 / Distributed, decentralized object storage FrostFS
+   \ (frostfs)
+13 / Dropbox
+   \ (dropbox)
+14 / Encrypt/Decrypt a remote
+   \ (crypt)
+15 / Enterprise File Fabric
+   \ (filefabric)
+16 / FTP
+   \ (ftp)
+17 / Files.com
+   \ (filescom)
+18 / Gofile
+   \ (gofile)
+19 / Google Cloud Storage (this is not Google Drive)
+   \ (google cloud storage)
+20 / Google Drive
+   \ (drive)
+21 / Google Photos
+   \ (google photos)
+22 / HTTP
+   \ (http)
+23 / Hadoop distributed file system
+   \ (hdfs)
+24 / HiDrive
+   \ (hidrive)
+25 / ImageKit.io
+   \ (imagekit)
+26 / In memory object storage system.
+   \ (memory)
+27 / Internet Archive
+   \ (internetarchive)
+28 / Jottacloud
+   \ (jottacloud)
+29 / Koofr, Digi Storage and other Koofr-compatible storage providers
+   \ (koofr)
+30 / Linkbox
+   \ (linkbox)
+31 / Local Disk
+   \ (local)
+32 / Mail.ru Cloud
+   \ (mailru)
+33 / Mega
+   \ (mega)
+34 / Microsoft Azure Blob Storage
+   \ (azureblob)
+35 / Microsoft Azure Files
+   \ (azurefiles)
+36 / Microsoft OneDrive
+   \ (onedrive)
+37 / OpenDrive
+   \ (opendrive)
+38 / OpenStack Swift (Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)
+   \ (swift)
+39 / Oracle Cloud Infrastructure Object Storage
+   \ (oracleobjectstorage)
+40 / Pcloud
+   \ (pcloud)
+41 / PikPak
+   \ (pikpak)
+42 / Pixeldrain Filesystem
+   \ (pixeldrain)
+43 / Proton Drive
+   \ (protondrive)
+44 / Put.io
+   \ (putio)
+45 / QingCloud Object Storage
+   \ (qingstor)
+46 / Quatrix by Maytech
+   \ (quatrix)
+47 / SMB / CIFS
+   \ (smb)
+48 / SSH/SFTP
+   \ (sftp)
+49 / Sia Decentralized Cloud
+   \ (sia)
+50 / Storj Decentralized Cloud Storage
+   \ (storj)
+51 / Sugarsync
+   \ (sugarsync)
+52 / Transparently chunk/split large files
+   \ (chunker)
+53 / Uloz.to
+   \ (ulozto)
+54 / Union merges the contents of several upstream fs
+   \ (union)
+55 / Uptobox
+   \ (uptobox)
+56 / WebDAV
+   \ (webdav)
+57 / Yandex Disk
+   \ (yandex)
+58 / Zoho
+   \ (zoho)
+59 / premiumize.me
+   \ (premiumizeme)
+60 / seafile
+   \ (seafile)
+Storage> frostfs
+
+Option endpoint.
+Endpoints to connect to FrostFS node
+Choose a number from below, or type in your own value.
+ 1 / One endpoint.
+   \ (s01.frostfs.devenv:8080)
+ 2 / Multiple endpoints to form pool.
+   \ (s01.frostfs.devenv:8080 s02.frostfs.devenv:8080)
+ 3 / Multiple endpoints with priority (less value is higher priority). Until s01 is healthy all request will be send to it.
+   \ (s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2)
+ 4 / Multiple endpoints with priority and weights. After s01 is unhealthy requests will be send to s02 and s03 in proportions 10% and 90% respectively.
+   \ (s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1 s03.frostfs.devenv:8080,2,9)
+endpoint> s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+
+Option connection_timeout.
+FrostFS connection timeout
+Enter a value of type Duration. Press Enter for the default (4s).
+connection_timeout> 
+
+Option request_timeout.
+FrostFS request timeout
+Enter a value of type Duration. Press Enter for the default (4s).
+request_timeout> 
+
+Option rebalance_interval.
+FrostFS rebalance connections interval
+Enter a value of type Duration. Press Enter for the default (15s).
+rebalance_interval> 
+
+Option session_expiration.
+FrostFS session expiration epoch
+Enter a signed integer. Press Enter for the default (4294967295).
+session_expiration> 
+
+Option ape_cache_invalidation_duration.
+APE cache invalidation duration
+Enter a value of type Duration. Press Enter for the default (8s).
+ape_cache_invalidation_duration> 
+
+Option ape_cache_invalidation_timeout.
+APE cache invalidation timeout
+Enter a value of type Duration. Press Enter for the default (16s).
+ape_cache_invalidation_timeout> 
+
+Option ape_chain_check_interval.
+The interval for verifying that the APE chain is saved in FrostFS.
+Enter a value of type Duration. Press Enter for the default (500ms).
+ape_chain_check_interval> 
+
+Option rpc_endpoint.
+Endpoint to connect to Neo rpc node
+Enter a value. Press Enter to leave empty.
+rpc_endpoint> 
+
+Option wallet.
+Path to wallet
+Enter a value.
+wallet> /wallets/wallet.conf
+
+Option address.
+Address of account
+Enter a value. Press Enter to leave empty.
+address> 
+
+Option password.
+Password to decrypt wallet
+Enter a value. Press Enter to leave empty.
+password> 
+
+Option placement_policy.
+Placement policy for new containers
+Choose a number from below, or type in your own value of type string.
+Press Enter for the default (REP 3).
+ 1 / Container will have 3 replicas
+   \ (REP 3)
+placement_policy> REP 1
+
+Option container_creation_policy.
+Container creation policy for new containers
+Choose a number from below, or type in your own value of type string.
+Press Enter for the default (private).
+ 1 / Public container, anyone can read and write
+   \ (public-read-write)
+ 2 / Public container, owner can read and write, others can only read
+   \ (public-read)
+ 3 / Private container, only owner has access to it
+   \ (private)
+container_creation_policy> 
+
+Edit advanced config?
+y) Yes
+n) No (default)
+y/n> n
+
+Configuration complete.
+Options:
+- type: frostfs
+- endpoint: s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+- password: M@zPGpWDravchenko/develop/go/playground/play_with_ape/cfg/wallet_akrav.js
+- placement_policy: REP 1
+Keep this "remote" remote?
+y) Yes this is OK (default)
+e) Edit this remote
+d) Delete this remote
+y/e/d> y
+```
+
+As a remote root directory, you can use either the container identifier or its user-friendly name.
+If you choose to use a container name, rclone will create a new container with that name when 
+it's used for the first time.
+
+For example, both of the following commands would be valid if there was a `~/test-copy` directory and a container with
+the identifier `23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf`:
+
+    rclone copy ~/test-copy remote:23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf/test-copy
+    rclone copy ~/test-copy remote:container-name/test-copy
+
+
+### Standard options
+
+Here are the Standard options specific to frostfs (Distributed, decentralized object storage FrostFS).
+
+#### --frostfs-endpoint
+
+Endpoints to connect to FrostFS node
+
+Properties:
+
+- Config:      endpoint
+- Env Var:     RCLONE_FROSTFS_ENDPOINT
+- Type:        string
+- Required:    true
+- Examples:
+    - "s01.frostfs.devenv:8080"
+        - One endpoint.
+    - "s01.frostfs.devenv:8080 s02.frostfs.devenv:8080"
+        - Multiple endpoints to form pool.
+    - "s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2"
+        - Multiple endpoints with priority (lower value has higher priority). Until s01 is healthy, all requests will be sent to it.
+    - "s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1 s03.frostfs.devenv:8080,2,9"
+        - Multiple endpoints with priority and weights. After the s01 endpoint is unhealthy, requests will be sent to the s02 and s03 endpoints in proportions of 10% and 90%, respectively.
+
+#### --frostfs-connection-timeout
+
+FrostFS connection timeout
+
+Properties:
+
+- Config:      connection_timeout
+- Env Var:     RCLONE_FROSTFS_CONNECTION_TIMEOUT
+- Type:        Duration
+- Default:     4s
+
+#### --frostfs-request-timeout
+
+FrostFS request timeout
+
+Properties:
+
+- Config:      request_timeout
+- Env Var:     RCLONE_FROSTFS_REQUEST_TIMEOUT
+- Type:        Duration
+- Default:     12s
+
+#### --frostfs-rebalance-interval
+
+FrostFS rebalance connections interval
+
+Properties:
+
+- Config:      rebalance_interval
+- Env Var:     RCLONE_FROSTFS_REBALANCE_INTERVAL
+- Type:        Duration
+- Default:     15s
+
+#### --frostfs-session-expiration
+
+FrostFS session expiration epoch
+
+Properties:
+
+- Config:      session_expiration
+- Env Var:     RCLONE_FROSTFS_SESSION_EXPIRATION
+- Type:        int
+- Default:     4294967295
+
+#### --frostfs-ape-cache-invalidation-duration
+
+APE cache invalidation duration
+
+Properties:
+
+- Config:      ape_cache_invalidation_duration
+- Env Var:     RCLONE_FROSTFS_APE_CACHE_INVALIDATION_DURATION
+- Type:        Duration
+- Default:     8s
+
+#### --frostfs-ape-cache-invalidation-timeout
+
+APE cache invalidation timeout
+
+Properties:
+
+- Config:      ape_cache_invalidation_timeout
+- Env Var:     RCLONE_FROSTFS_APE_CACHE_INVALIDATION_TIMEOUT
+- Type:        Duration
+- Default:     24s
+
+#### --frostfs-ape-chain-check-interval
+
+The interval for verifying that the APE chain is saved in FrostFS.
+
+Properties:
+
+- Config:      ape_chain_check_interval
+- Env Var:     RCLONE_FROSTFS_APE_CHAIN_CHECK_INTERVAL
+- Type:        Duration
+- Default:     500ms
+
+#### --frostfs-rpc-endpoint
+
+Endpoint to connect to Neo rpc node
+
+Properties:
+
+- Config:      rpc_endpoint
+- Env Var:     RCLONE_FROSTFS_RPC_ENDPOINT
+- Type:        string
+- Required:    false
+
+#### --frostfs-wallet
+
+Path to wallet
+
+Properties:
+
+- Config:      wallet
+- Env Var:     RCLONE_FROSTFS_WALLET
+- Type:        string
+- Required:    true
+
+#### --frostfs-address
+
+Address of account
+
+Properties:
+
+- Config:      address
+- Env Var:     RCLONE_FROSTFS_ADDRESS
+- Type:        string
+- Required:    false
+
+#### --frostfs-password
+
+Password to decrypt wallet
+
+Properties:
+
+- Config:      password
+- Env Var:     RCLONE_FROSTFS_PASSWORD
+- Type:        string
+- Required:    false
+
+#### --frostfs-placement-policy
+
+Placement policy for new containers
+
+Properties:
+
+- Config:      placement_policy
+- Env Var:     RCLONE_FROSTFS_PLACEMENT_POLICY
+- Type:        string
+- Default:     "REP 3"
+- Examples:
+    - "REP 3"
+        - Container will have 3 replicas
+
+#### --frostfs-container-creation-policy
+
+Container creation policy for new containers
+
+Properties:
+
+- Config:      container_creation_policy
+- Env Var:     RCLONE_FROSTFS_CONTAINER_CREATION_POLICY
+- Type:        string
+- Default:     "private"
+- Examples:
+    - "public-read-write"
+        - Public container, anyone can read and write
+    - "public-read"
+        - Public container, owner can read and write, others can only read
+    - "private"
+        - Private container, only owner has access to it
+
+### Advanced options
+
+Here are the Advanced options specific to frostfs (Distributed, decentralized object storage FrostFS).
+
+#### --frostfs-description
+
+Description of the remote.
+
+Properties:
+
+- Config:      description
+- Env Var:     RCLONE_FROSTFS_DESCRIPTION
+- Type:        string
+- Required:    false
+
+
+
 #  FTP
 
 FTP is the File Transfer Protocol. Rclone FTP support is provided using the
@@ -34727,13 +35204,13 @@ therefore works even in Windows Command Prompt:
     rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM
     rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM:
 
-### Implicit TLS
+### Implicit TLS[util.go](../../backend/frostfs/util.go)
 
 Rlone FTP supports implicit FTP over TLS servers (FTPS). This has to
 be enabled in the FTP backend config for the remote, or with
 [`--ftp-tls`](#ftp-tls). The default FTPS port is `990`, not `21` and
 can be set with [`--ftp-port`](#ftp-port).
-
+[util.go](../../backend/frostfs/util.go)
 ### Restricted filename characters
 
 In addition to the [default restricted characters set](https://rclone.org/overview/#restricted-characters)
diff --git a/MANUAL.txt b/MANUAL.txt
index 1c89d2043..79efb97d1 100644
--- a/MANUAL.txt
+++ b/MANUAL.txt
@@ -1,6 +1,6 @@
 rclone(1) User Manual
 Nick Craig-Wood
-Nov 15, 2024
+Jan 10, 2025
 
 Rclone syncs your files to cloud storage
 
@@ -109,6 +109,7 @@ S3, that work out of the box.)
 -   Enterprise File Fabric
 -   Fastmail Files
 -   Files.com
+-   FrostFS
 -   FTP
 -   Gofile
 -   Google Cloud Storage
@@ -1202,11 +1203,11 @@ what happened to it. These are reminiscent of diff files.
 
 -   = path means path was found in source and destination and was
     identical
--   `- path` means path was missing on the source, so only in the
+-   - path means path was missing on the source, so only in the
     destination
--   `+ path` means path was missing on the destination, so only in the
+-   + path means path was missing on the destination, so only in the
     source
--   `* path` means path was present in source and destination but
+-   * path means path was present in source and destination but
     different.
 -   ! path means there was an error reading or hashing the source or
     dest.
@@ -1714,11 +1715,11 @@ what happened to it. These are reminiscent of diff files.
 
 -   = path means path was found in source and destination and was
     identical
--   `- path` means path was missing on the source, so only in the
+-   - path means path was missing on the source, so only in the
     destination
--   `+ path` means path was missing on the destination, so only in the
+-   + path means path was missing on the destination, so only in the
     source
--   `* path` means path was present in source and destination but
+-   * path means path was present in source and destination but
     different.
 -   ! path means there was an error reading or hashing the source or
     dest.
@@ -2919,11 +2920,11 @@ what happened to it. These are reminiscent of diff files.
 
 -   = path means path was found in source and destination and was
     identical
--   `- path` means path was missing on the source, so only in the
+-   - path means path was missing on the source, so only in the
     destination
--   `+ path` means path was missing on the destination, so only in the
+-   + path means path was missing on the destination, so only in the
     source
--   `* path` means path was present in source and destination but
+-   * path means path was present in source and destination but
     different.
 -   ! path means there was an error reading or hashing the source or
     dest.
@@ -4023,11 +4024,11 @@ what happened to it. These are reminiscent of diff files.
 
 -   = path means path was found in source and destination and was
     identical
--   `- path` means path was missing on the source, so only in the
+-   - path means path was missing on the source, so only in the
     destination
--   `+ path` means path was missing on the destination, so only in the
+-   + path means path was missing on the destination, so only in the
     source
--   `* path` means path was present in source and destination but
+-   * path means path was present in source and destination but
     different.
 -   ! path means there was an error reading or hashing the source or
     dest.
@@ -13174,9 +13175,9 @@ Will get their own names
 
 Valid remote names
 
-Remote names are case sensitive, and must adhere to the following rules:
-- May contain number, letter, _, -, ., +, @ and space. - May not start
-with - or space. - May not end with space.
+Remote names are case sensitive, and must adhere to the following
+rules: - May contain number, letter, _, -, ., +, @ and space. - May not
+start with - or space. - May not end with space.
 
 Starting with rclone version 1.61, any Unicode numbers and letters are
 allowed, while in older versions it was limited to plain ASCII (0-9,
@@ -16096,28 +16097,49 @@ into regular expressions.
 
 Filter pattern examples
 
-  Description     Pattern          Matches                         Does not match
-  --------------- ---------------- ------------------------------- ------------------
-  Wildcard        *.jpg            /file.jpg                       /file.png
-                                   /dir/file.jpg                   /dir/file.png
-  Rooted          /*.jpg           /file.jpg                       /file.png
-                                   /file2.jpg                      /dir/file.jpg
-  Alternates      *.{jpg,png}      /file.jpg                       /file.gif
-                                   /dir/file.png                   /dir/file.gif
-  Path Wildcard   dir/**           /dir/anyfile                    file.png
-                                   /subdir/dir/subsubdir/anyfile   /subdir/file.png
-  Any Char        *.t?t            /file.txt                       /file.qxt
-                                   /dir/file.tzt                   /dir/file.png
-  Range           *.[a-z]          /file.a                         /file.0
-                                   /dir/file.b                     /dir/file.1
-  Escape          *.\?\?\?         /file.???                       /file.abc
-                                   /dir/file.???                   /dir/file.def
-  Class           *.\d\d\d         /file.012                       /file.abc
-                                   /dir/file.345                   /dir/file.def
-  Regexp          *.{{jpe?g}}      /file.jpeg                      /file.png
-                                   /dir/file.jpg                   /dir/file.jpeeg
-  Rooted Regexp   /{{.*\.jpe?g}}   /file.jpeg                      /file.png
-                                   /file.jpg                       /dir/file.jpg
+  ---------------------------------------------------------------------------------------------
+  Description         Pattern          Matches                         Does not match
+  ------------------- ---------------- ------------------------------- ------------------------
+  Wildcard            *.jpg            /file.jpg                       /file.png
+
+                                       /dir/file.jpg                   /dir/file.png
+
+  Rooted              /*.jpg           /file.jpg                       /file.png
+
+                                       /file2.jpg                      /dir/file.jpg
+
+  Alternates          *.{jpg,png}      /file.jpg                       /file.gif
+
+                                       /dir/file.png                   /dir/file.gif
+
+  Path Wildcard       dir/**           /dir/anyfile                    file.png
+
+                                       /subdir/dir/subsubdir/anyfile   /subdir/file.png
+
+  Any Char            *.t?t            /file.txt                       /file.qxt
+
+                                       /dir/file.tzt                   /dir/file.png
+
+  Range               *.[a-z]          /file.a                         /file.0
+
+                                       /dir/file.b                     /dir/file.1
+
+  Escape              *.\?\?\?         /file.???                       /file.abc
+
+                                       /dir/file.???                   /dir/file.def
+
+  Class               *.\d\d\d         /file.012                       /file.abc
+
+                                       /dir/file.345                   /dir/file.def
+
+  Regexp              *.{{jpe?g}}      /file.jpeg                      /file.png
+
+                                       /dir/file.jpg                   /dir/file.jpeeg
+
+  Rooted Regexp       /{{.*\.jpe?g}}   /file.jpeg                      /file.png
+
+                                       /file.jpg                       /dir/file.jpg
+  ---------------------------------------------------------------------------------------------
 
 How filter rules are applied to files
 
@@ -19242,58 +19264,121 @@ Features
 
 Here is an overview of the major features of each cloud storage system.
 
-  Name                                   Hash          ModTime   Case Insensitive   Duplicate Files   MIME Type   Metadata
-  ------------------------------- ------------------- --------- ------------------ ----------------- ----------- ----------
-  1Fichier                             Whirlpool          -             No                Yes             R          -
-  Akamai Netstorage                   MD5, SHA256        R/W            No                No              R          -
-  Amazon S3 (or S3 compatible)            MD5            R/W            No                No             R/W        RWU
-  Backblaze B2                           SHA1            R/W            No                No             R/W         -
-  Box                                    SHA1            R/W           Yes                No              -          -
-  Citrix ShareFile                        MD5            R/W           Yes                No              -          -
-  Dropbox                              DBHASH ¹           R            Yes                No              -          -
-  Enterprise File Fabric                   -             R/W           Yes                No             R/W         -
-  Files.com                           MD5, CRC32        DR/W           Yes                No              R          -
-  FTP                                      -           R/W ¹⁰           No                No              -          -
-  Gofile                                  MD5           DR/W            No                Yes             R          -
-  Google Cloud Storage                    MD5            R/W            No                No             R/W         -
-  Google Drive                     MD5, SHA1, SHA256    DR/W            No                Yes            R/W        DRWU
-  Google Photos                            -              -             No                Yes             R          -
-  HDFS                                     -             R/W            No                No              -          -
-  HiDrive                             HiDrive ¹²         R/W            No                No              -          -
-  HTTP                                     -              R             No                No              R          -
-  Internet Archive                 MD5, SHA1, CRC32    R/W ¹¹           No                No              -         RWU
-  Jottacloud                              MD5            R/W           Yes                No              R          RW
-  Koofr                                   MD5             -            Yes                No              -          -
-  Linkbox                                  -              R             No                No              -          -
-  Mail.ru Cloud                        Mailru ⁶          R/W           Yes                No              -          -
-  Mega                                     -              -             No                Yes             -          -
-  Memory                                  MD5            R/W            No                No              -          -
-  Microsoft Azure Blob Storage            MD5            R/W            No                No             R/W         -
-  Microsoft Azure Files Storage           MD5            R/W           Yes                No             R/W         -
-  Microsoft OneDrive                QuickXorHash ⁵      DR/W           Yes                No              R         DRW
-  OpenDrive                               MD5            R/W           Yes             Partial ⁸          -          -
-  OpenStack Swift                         MD5            R/W            No                No             R/W         -
-  Oracle Object Storage                   MD5            R/W            No                No             R/W         -
-  pCloud                              MD5, SHA1 ⁷        R/W            No                No              W          -
-  PikPak                                  MD5             R             No                No              R          -
-  Pixeldrain                            SHA256           R/W            No                No              R          RW
-  premiumize.me                            -              -            Yes                No              R          -
-  put.io                                CRC-32           R/W            No                Yes             R          -
-  Proton Drive                           SHA1            R/W            No                No              R          -
-  QingStor                                MD5            - ⁹            No                No             R/W         -
-  Quatrix by Maytech                       -             R/W            No                No              -          -
-  Seafile                                  -              -             No                No              -          -
-  SFTP                                MD5, SHA1 ²       DR/W         Depends              No              -          -
-  Sia                                      -              -             No                No              -          -
-  SMB                                      -             R/W           Yes                No              -          -
-  SugarSync                                -              -             No                No              -          -
-  Storj                                    -              R             No                No              -          -
-  Uloz.to                           MD5, SHA256 ¹³        -             No                Yes             -          -
-  Uptobox                                  -              -             No                Yes             -          -
-  WebDAV                              MD5, SHA1 ³        R ⁴         Depends              No              -          -
-  Yandex Disk                             MD5            R/W            No                No              R          -
-  Zoho WorkDrive                           -              -             No                No              -          -
-  The local filesystem                    All           DR/W         Depends              No              -         DRWU
+  --------------------------------------------------------------------------------------
+  Name                   Hash       ModTime      Case       Duplicate   MIME   Metadata
+                                              Insensitive     Files     Type  
+  ----------------- -------------- --------- ------------- ----------- ------ ----------
+  1Fichier            Whirlpool        -          No           Yes       R        -
+
+  Akamai Netstorage  MD5, SHA256      R/W         No           No        R        -
+
+  Amazon S3 (or S3       MD5          R/W         No           No       R/W      RWU
+  compatible)                                                                 
+
+  Backblaze B2           SHA1         R/W         No           No       R/W       -
+
+  Box                    SHA1         R/W         Yes          No        -        -
+
+  Citrix ShareFile       MD5          R/W         Yes          No        -        -
+
+  Dropbox              DBHASH ¹        R          Yes          No        -        -
+
+  Enterprise File         -           R/W         Yes          No       R/W       -
+  Fabric                                                                      
+
+  Files.com           MD5, CRC32     DR/W         Yes          No        R        -
+
+  FTP                     -         R/W ¹⁰        No           No        -        -
+
+  Gofile                 MD5         DR/W         No           Yes       R        -
+
+  Google Cloud           MD5          R/W         No           No       R/W       -
+  Storage                                                                     
+
+  Google Drive        MD5, SHA1,     DR/W         No           Yes      R/W      DRWU
+                        SHA256                                                
+
+  Google Photos           -            -          No           Yes       R        -
+
+  HDFS                    -           R/W         No           No        -        -
+
+  HiDrive             HiDrive ¹²      R/W         No           No        -        -
+
+  HTTP                    -            R          No           No        R        -
+
+  Internet Archive    MD5, SHA1,    R/W ¹¹        No           No        -       RWU
+                        CRC32                                                 
+
+  Jottacloud             MD5          R/W         Yes          No        R        RW
+
+  Koofr                  MD5           -          Yes          No        -        -
+
+  Linkbox                 -            R          No           No        -        -
+
+  Mail.ru Cloud        Mailru ⁶       R/W         Yes          No        -        -
+
+  Mega                    -            -          No           Yes       -        -
+
+  Memory                 MD5          R/W         No           No        -        -
+
+  Microsoft Azure        MD5          R/W         No           No       R/W       -
+  Blob Storage                                                                
+
+  Microsoft Azure        MD5          R/W         Yes          No       R/W       -
+  Files Storage                                                               
+
+  Microsoft         QuickXorHash ⁵   DR/W         Yes          No        R       DRW
+  OneDrive                                                                    
+
+  OpenDrive              MD5          R/W         Yes       Partial ⁸    -        -
+
+  OpenStack Swift        MD5          R/W         No           No       R/W       -
+
+  Oracle Object          MD5          R/W         No           No       R/W       -
+  Storage                                                                     
+
+  pCloud             MD5, SHA1 ⁷      R/W         No           No        W        -
+
+  PikPak                 MD5           R          No           No        R        -
+
+  Pixeldrain            SHA256        R/W         No           No        R        RW
+
+  premiumize.me           -            -          Yes          No        R        -
+
+  put.io                CRC-32        R/W         No           Yes       R        -
+
+  Proton Drive           SHA1         R/W         No           No        R        -
+
+  QingStor               MD5          - ⁹         No           No       R/W       -
+
+  Quatrix by              -           R/W         No           No        -        -
+  Maytech                                                                     
+
+  Seafile                 -            -          No           No        -        -
+
+  SFTP               MD5, SHA1 ²     DR/W       Depends        No        -        -
+
+  Sia                     -            -          No           No        -        -
+
+  SMB                     -           R/W         Yes          No        -        -
+
+  SugarSync               -            -          No           No        -        -
+
+  Storj                   -            R          No           No        -        -
+
+  Uloz.to           MD5, SHA256 ¹³     -          No           Yes       -        -
+
+  Uptobox                 -            -          No           Yes       -        -
+
+  WebDAV             MD5, SHA1 ³      R ⁴       Depends        No        -        -
+
+  Yandex Disk            MD5          R/W         No           No        R        -
+
+  Zoho WorkDrive          -            -          No           No        -        -
+
+  The local              All         DR/W       Depends        No        -       DRWU
+  filesystem                                                                  
+  --------------------------------------------------------------------------------------
 
 ¹ Dropbox supports its own custom hash. This is an SHA256 sum of all the
 4 MiB block SHA256s.
@@ -20081,7 +20166,7 @@ Flags for general networking and HTTP stuff.
           --tpslimit float                     Limit HTTP transactions per second to this
           --tpslimit-burst int                 Max burst of transactions for --tpslimit (default 1)
           --use-cookies                        Enable session cookiejar
-          --user-agent string                  Set the user-agent to a specified string (default "rclone/v1.68.2")
+          --user-agent string                  Set the user-agent to a specified string (default "rclone/v1.68.2-beta.8331.25cf42493.feature/add-frostfs-support")
 
 Performance
 
@@ -20488,6 +20573,21 @@ Backend-only flags (these can be set in the config file also).
           --filescom-password string                            The password used to authenticate with Files.com (obscured)
           --filescom-site string                                Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com)
           --filescom-username string                            The username used to authenticate with Files.com
+          --frostfs-address string                              Address of account
+          --frostfs-ape-cache-invalidation-duration Duration    APE cache invalidation duration (default 8s)
+          --frostfs-ape-cache-invalidation-timeout Duration     APE cache invalidation timeout (default 24s)
+          --frostfs-ape-chain-check-interval Duration           The interval for verifying that the APE chain is saved in FrostFS (default 500ms)
+          --frostfs-connection-timeout Duration                 FrostFS connection timeout (default 4s)
+          --frostfs-container-creation-policy string            Container creation policy for new containers (default "private")
+          --frostfs-description string                          Description of the remote
+          --frostfs-endpoint string                             Endpoints to connect to FrostFS node
+          --frostfs-password string                             Password to decrypt wallet
+          --frostfs-placement-policy string                     Placement policy for new containers (default "REP 3")
+          --frostfs-rebalance-interval Duration                 FrostFS rebalance connections interval (default 15s)
+          --frostfs-request-timeout Duration                    FrostFS request timeout (default 12s)
+          --frostfs-rpc-endpoint string                         Endpoint to connect to Neo rpc node
+          --frostfs-session-expiration int                      FrostFS session expiration epoch (default 4294967295)
+          --frostfs-wallet string                               Path to wallet
           --ftp-ask-password                                    Allow asking for FTP password when needed
           --ftp-close-timeout Duration                          Maximum time to wait for a response to close (default 1m0s)
           --ftp-concurrency int                                 Maximum number of FTP simultaneous connections, 0 for unlimited
@@ -22714,7 +22814,7 @@ include-style filters for Windows user directories below.
 Filters file writing guidelines
 
 1.  Begin with excluding directory trees:
-    -   e.g. `- /AppData/`
+    -   e.g. - /AppData/
     -   ** on the end is not necessary. Once a given directory level is
         excluded then everything beneath it won't be looked at by
         rclone.
@@ -22729,22 +22829,22 @@ Filters file writing guidelines
         -- or --
     -   Exclude select directories and therefore include everything else
 3.  Include select directories:
-    -   Add lines like: `+ /Documents/PersonalFiles/**` to select which
+    -   Add lines like: + /Documents/PersonalFiles/** to select which
         directories to include in the sync.
     -   ** on the end specifies to include the full depth of the
         specified tree.
     -   With Include-style filters, files at the Path1/Path2 root are
-        not included. They may be included with `+ /*`.
+        not included. They may be included with + /*.
     -   Place RCLONE_TEST files within these included directory trees.
         They will only be looked for in these directory trees.
-    -   Finish by excluding everything else by adding `- **` at the end
-        of the filters file.
+    -   Finish by excluding everything else by adding - ** at the end of
+        the filters file.
     -   Disregard step 4.
 4.  Exclude select directories:
     -   Add more lines like in step 1. For example:
-        -/Desktop/tempfiles/, or `- /testdir/.    Again, a**` on the end
-        is not necessary.
-    -   Do not add a `- **` in the file. Without this line, everything
+        -/Desktop/tempfiles/, or - /testdir/. Again, a ** on the end is
+        not necessary.
+    -   Do not add a - ** in the file. Without this line, everything
         will be included that has not been explicitly excluded.
     -   Disregard step 3.
 
@@ -22769,7 +22869,7 @@ This Windows include-style example is based on the sync root (Path1) set
 to C:\Users\MyLogin. The strategy is to select specific directories to
 be synched with a network drive (Path2).
 
--   `- /AppData/` excludes an entire tree of Windows stored stuff that
+-   - /AppData/ excludes an entire tree of Windows stored stuff that
     need not be synched. In my case, AppData has >11 GB of stuff I don't
     care about, and there are some subdirectories beneath AppData that
     are not accessible to my user login, resulting in bisync critical
@@ -22778,11 +22878,12 @@ be synched with a network drive (Path2).
     NTUSER at C:\Users\MyLogin. These files may be dynamic, locked, and
     are generally don't care.
 -   There are just a few directories with my data that I do want
-    synched, in the form of `+
-    /. By selecting only the directory trees I   want to avoid the dozen plus directories that various apps make   atC:`.
+    synched, in the form of + /<path>. By selecting only the directory
+    trees I want to avoid the dozen plus directories that various apps
+    make at C:\Users\MyLogin\Documents.
 -   Include files in the root of the sync point, C:\Users\MyLogin, by
-    adding the `+ /*` line.
--   This is an Include-style filters file, therefore it ends with `- **`
+    adding the + /* line.
+-   This is an Include-style filters file, therefore it ends with - **
     which excludes everything not explicitly included.
 
     - /AppData/
@@ -22809,14 +22910,14 @@ This noise can be quashed by adding --quiet to the bisync command line.
 Example exclude-style filters files for use with Dropbox
 
 -   Dropbox disallows synching the listed temporary and
-    configuration/data files. The `- ` filters exclude these files where
-    ever they may occur in the sync tree. Consider adding similar
-    exclusions for file types you don't need to sync, such as core dump
-    and software build files.
+    configuration/data files. The - <filename> filters exclude these
+    files where ever they may occur in the sync tree. Consider adding
+    similar exclusions for file types you don't need to sync, such as
+    core dump and software build files.
 -   bisync testing creates /testdir/ at the top level of the sync tree,
     and usually deletes the tree after the test. If a normal sync should
     run while the /testdir/ tree exists the --check-access phase may
-    fail due to unbalanced RCLONE_TEST files. The `- /testdir/` filter
+    fail due to unbalanced RCLONE_TEST files. The - /testdir/ filter
     blocks this tree from being synched. You don't need this exclusion
     if you are not doing bisync development testing.
 -   Everything else beneath the Path1/Path2 root will be synched.
@@ -23190,10 +23291,14 @@ Notes about testing
     these directories when validating and debugging a given test. These
     directories will be flushed before running another test, independent
     of the -no-cleanup usage.
--   You will likely want to add `-
-    /testdir/to your normal   bisync--filters-fileso that normal syncs do not attempt to sync   the test temporary directories, which may haveRCLONE_TESTmiscompares   in some testcases which would otherwise trip the--check-accesssystem.   The--check-accessmechanism is hard-coded to ignoreRCLONE_TESTfiles beneathbisync/testdata`,
-    so the test cases may reside on the synched tree even if there are
-    check file mismatches in the test tree.
+-   You will likely want to add - /testdir/ to your normal bisync
+    --filters-file so that normal syncs do not attempt to sync the test
+    temporary directories, which may have RCLONE_TEST miscompares in
+    some testcases which would otherwise trip the --check-access system.
+    The --check-access mechanism is hard-coded to ignore RCLONE_TEST
+    files beneath bisync/testdata, so the test cases may reside on the
+    synched tree even if there are check file mismatches in the test
+    tree.
 -   Some Dropbox tests can fail, notably printing the following message:
     src and dst identical but can't set mod time without deleting and re-uploading
     This is expected and happens due to the way Dropbox handles
@@ -23340,8 +23445,8 @@ characters (which factors into load time and RAM required).
 References
 
 rclone's bisync implementation was derived from the rclonesync-V2
-project, including documentation and test mechanisms, with
-[@cjnaz](https://github.com/cjnaz)'s full support and encouragement.
+project, including documentation and test mechanisms, with @cjnaz's full
+support and encouragement.
 
 rclone bisync is similar in nature to a range of other projects:
 
@@ -33978,6 +34083,472 @@ Properties:
 -   Type: string
 -   Required: false
 
+FrostFS
+
+Rclone FrostFS support is provided using the
+git.frostfs.info/TrueCloudLab/frostfs-sdk-go package
+
+Configuration
+
+To create an FrostFS configuration named remote, run
+
+    rclone config
+
+Rclone config guides you through an interactive setup process. A minimal
+rclone FrostFS remote definition only requires endpoint and path to
+FrostFS user wallet.
+
+    No remotes found, make a new one?
+    n) New remote
+    s) Set configuration password
+    q) Quit config
+    n/s/q> n
+
+    Enter name for new remote.
+    name> remote
+
+    Option Storage.
+    Type of storage to configure.
+    Choose a number from below, or type in your own value.
+     1 / 1Fichier
+       \ (fichier)
+     2 / Akamai NetStorage
+       \ (netstorage)
+     3 / Alias for an existing remote
+       \ (alias)
+     4 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others
+       \ (s3)
+     5 / Backblaze B2
+       \ (b2)
+     6 / Better checksums for other remotes
+       \ (hasher)
+     7 / Box
+       \ (box)
+     8 / Cache a remote
+       \ (cache)
+     9 / Citrix Sharefile
+       \ (sharefile)
+    10 / Combine several remotes into one
+       \ (combine)
+    11 / Compress a remote
+       \ (compress)
+    12 / Distributed, decentralized object storage FrostFS
+       \ (frostfs)
+    13 / Dropbox
+       \ (dropbox)
+    14 / Encrypt/Decrypt a remote
+       \ (crypt)
+    15 / Enterprise File Fabric
+       \ (filefabric)
+    16 / FTP
+       \ (ftp)
+    17 / Files.com
+       \ (filescom)
+    18 / Gofile
+       \ (gofile)
+    19 / Google Cloud Storage (this is not Google Drive)
+       \ (google cloud storage)
+    20 / Google Drive
+       \ (drive)
+    21 / Google Photos
+       \ (google photos)
+    22 / HTTP
+       \ (http)
+    23 / Hadoop distributed file system
+       \ (hdfs)
+    24 / HiDrive
+       \ (hidrive)
+    25 / ImageKit.io
+       \ (imagekit)
+    26 / In memory object storage system.
+       \ (memory)
+    27 / Internet Archive
+       \ (internetarchive)
+    28 / Jottacloud
+       \ (jottacloud)
+    29 / Koofr, Digi Storage and other Koofr-compatible storage providers
+       \ (koofr)
+    30 / Linkbox
+       \ (linkbox)
+    31 / Local Disk
+       \ (local)
+    32 / Mail.ru Cloud
+       \ (mailru)
+    33 / Mega
+       \ (mega)
+    34 / Microsoft Azure Blob Storage
+       \ (azureblob)
+    35 / Microsoft Azure Files
+       \ (azurefiles)
+    36 / Microsoft OneDrive
+       \ (onedrive)
+    37 / OpenDrive
+       \ (opendrive)
+    38 / OpenStack Swift (Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)
+       \ (swift)
+    39 / Oracle Cloud Infrastructure Object Storage
+       \ (oracleobjectstorage)
+    40 / Pcloud
+       \ (pcloud)
+    41 / PikPak
+       \ (pikpak)
+    42 / Pixeldrain Filesystem
+       \ (pixeldrain)
+    43 / Proton Drive
+       \ (protondrive)
+    44 / Put.io
+       \ (putio)
+    45 / QingCloud Object Storage
+       \ (qingstor)
+    46 / Quatrix by Maytech
+       \ (quatrix)
+    47 / SMB / CIFS
+       \ (smb)
+    48 / SSH/SFTP
+       \ (sftp)
+    49 / Sia Decentralized Cloud
+       \ (sia)
+    50 / Storj Decentralized Cloud Storage
+       \ (storj)
+    51 / Sugarsync
+       \ (sugarsync)
+    52 / Transparently chunk/split large files
+       \ (chunker)
+    53 / Uloz.to
+       \ (ulozto)
+    54 / Union merges the contents of several upstream fs
+       \ (union)
+    55 / Uptobox
+       \ (uptobox)
+    56 / WebDAV
+       \ (webdav)
+    57 / Yandex Disk
+       \ (yandex)
+    58 / Zoho
+       \ (zoho)
+    59 / premiumize.me
+       \ (premiumizeme)
+    60 / seafile
+       \ (seafile)
+    Storage> frostfs
+
+    Option endpoint.
+    Endpoints to connect to FrostFS node
+    Choose a number from below, or type in your own value.
+     1 / One endpoint.
+       \ (s01.frostfs.devenv:8080)
+     2 / Multiple endpoints to form pool.
+       \ (s01.frostfs.devenv:8080 s02.frostfs.devenv:8080)
+     3 / Multiple endpoints with priority (less value is higher priority). Until s01 is healthy all request will be send to it.
+       \ (s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2)
+     4 / Multiple endpoints with priority and weights. After s01 is unhealthy requests will be send to s02 and s03 in proportions 10% and 90% respectively.
+       \ (s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1 s03.frostfs.devenv:8080,2,9)
+    endpoint> s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+
+    Option connection_timeout.
+    FrostFS connection timeout
+    Enter a value of type Duration. Press Enter for the default (4s).
+    connection_timeout> 
+
+    Option request_timeout.
+    FrostFS request timeout
+    Enter a value of type Duration. Press Enter for the default (4s).
+    request_timeout> 
+
+    Option rebalance_interval.
+    FrostFS rebalance connections interval
+    Enter a value of type Duration. Press Enter for the default (15s).
+    rebalance_interval> 
+
+    Option session_expiration.
+    FrostFS session expiration epoch
+    Enter a signed integer. Press Enter for the default (4294967295).
+    session_expiration> 
+
+    Option ape_cache_invalidation_duration.
+    APE cache invalidation duration
+    Enter a value of type Duration. Press Enter for the default (8s).
+    ape_cache_invalidation_duration> 
+
+    Option ape_cache_invalidation_timeout.
+    APE cache invalidation timeout
+    Enter a value of type Duration. Press Enter for the default (16s).
+    ape_cache_invalidation_timeout> 
+
+    Option ape_chain_check_interval.
+    The interval for verifying that the APE chain is saved in FrostFS.
+    Enter a value of type Duration. Press Enter for the default (500ms).
+    ape_chain_check_interval> 
+
+    Option rpc_endpoint.
+    Endpoint to connect to Neo rpc node
+    Enter a value. Press Enter to leave empty.
+    rpc_endpoint> 
+
+    Option wallet.
+    Path to wallet
+    Enter a value.
+    wallet> /wallets/wallet.conf
+
+    Option address.
+    Address of account
+    Enter a value. Press Enter to leave empty.
+    address> 
+
+    Option password.
+    Password to decrypt wallet
+    Enter a value. Press Enter to leave empty.
+    password> 
+
+    Option placement_policy.
+    Placement policy for new containers
+    Choose a number from below, or type in your own value of type string.
+    Press Enter for the default (REP 3).
+     1 / Container will have 3 replicas
+       \ (REP 3)
+    placement_policy> REP 1
+
+    Option container_creation_policy.
+    Container creation policy for new containers
+    Choose a number from below, or type in your own value of type string.
+    Press Enter for the default (private).
+     1 / Public container, anyone can read and write
+       \ (public-read-write)
+     2 / Public container, owner can read and write, others can only read
+       \ (public-read)
+     3 / Private container, only owner has access to it
+       \ (private)
+    container_creation_policy> 
+
+    Edit advanced config?
+    y) Yes
+    n) No (default)
+    y/n> n
+
+    Configuration complete.
+    Options:
+    - type: frostfs
+    - endpoint: s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+    - password: M@zPGpWDravchenko/develop/go/playground/play_with_ape/cfg/wallet_akrav.js
+    - placement_policy: REP 1
+    Keep this "remote" remote?
+    y) Yes this is OK (default)
+    e) Edit this remote
+    d) Delete this remote
+    y/e/d> y
+
+As a remote root directory, you can use either the container identifier
+or its user-friendly name. If you choose to use a container name, rclone
+will create a new container with that name when it's used for the first
+time.
+
+For example, both of the following commands would be valid if there was
+a ~/test-copy directory and a container with the identifier
+23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf:
+
+    rclone copy ~/test-copy remote:23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf/test-copy
+    rclone copy ~/test-copy remote:container-name/test-copy
+
+Standard options
+
+Here are the Standard options specific to frostfs (Distributed,
+decentralized object storage FrostFS).
+
+--frostfs-endpoint
+
+Endpoints to connect to FrostFS node
+
+Properties:
+
+-   Config: endpoint
+-   Env Var: RCLONE_FROSTFS_ENDPOINT
+-   Type: string
+-   Required: true
+-   Examples:
+    -   "s01.frostfs.devenv:8080"
+        -   One endpoint.
+    -   "s01.frostfs.devenv:8080 s02.frostfs.devenv:8080"
+        -   Multiple endpoints to form pool.
+    -   "s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2"
+        -   Multiple endpoints with priority (lower value has higher
+            priority). Until s01 is healthy, all requests will be sent
+            to it.
+    -   "s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1
+        s03.frostfs.devenv:8080,2,9"
+        -   Multiple endpoints with priority and weights. After the s01
+            endpoint is unhealthy, requests will be sent to the s02 and
+            s03 endpoints in proportions of 10% and 90%, respectively.
+
+--frostfs-connection-timeout
+
+FrostFS connection timeout
+
+Properties:
+
+-   Config: connection_timeout
+-   Env Var: RCLONE_FROSTFS_CONNECTION_TIMEOUT
+-   Type: Duration
+-   Default: 4s
+
+--frostfs-request-timeout
+
+FrostFS request timeout
+
+Properties:
+
+-   Config: request_timeout
+-   Env Var: RCLONE_FROSTFS_REQUEST_TIMEOUT
+-   Type: Duration
+-   Default: 12s
+
+--frostfs-rebalance-interval
+
+FrostFS rebalance connections interval
+
+Properties:
+
+-   Config: rebalance_interval
+-   Env Var: RCLONE_FROSTFS_REBALANCE_INTERVAL
+-   Type: Duration
+-   Default: 15s
+
+--frostfs-session-expiration
+
+FrostFS session expiration epoch
+
+Properties:
+
+-   Config: session_expiration
+-   Env Var: RCLONE_FROSTFS_SESSION_EXPIRATION
+-   Type: int
+-   Default: 4294967295
+
+--frostfs-ape-cache-invalidation-duration
+
+APE cache invalidation duration
+
+Properties:
+
+-   Config: ape_cache_invalidation_duration
+-   Env Var: RCLONE_FROSTFS_APE_CACHE_INVALIDATION_DURATION
+-   Type: Duration
+-   Default: 8s
+
+--frostfs-ape-cache-invalidation-timeout
+
+APE cache invalidation timeout
+
+Properties:
+
+-   Config: ape_cache_invalidation_timeout
+-   Env Var: RCLONE_FROSTFS_APE_CACHE_INVALIDATION_TIMEOUT
+-   Type: Duration
+-   Default: 24s
+
+--frostfs-ape-chain-check-interval
+
+The interval for verifying that the APE chain is saved in FrostFS.
+
+Properties:
+
+-   Config: ape_chain_check_interval
+-   Env Var: RCLONE_FROSTFS_APE_CHAIN_CHECK_INTERVAL
+-   Type: Duration
+-   Default: 500ms
+
+--frostfs-rpc-endpoint
+
+Endpoint to connect to Neo rpc node
+
+Properties:
+
+-   Config: rpc_endpoint
+-   Env Var: RCLONE_FROSTFS_RPC_ENDPOINT
+-   Type: string
+-   Required: false
+
+--frostfs-wallet
+
+Path to wallet
+
+Properties:
+
+-   Config: wallet
+-   Env Var: RCLONE_FROSTFS_WALLET
+-   Type: string
+-   Required: true
+
+--frostfs-address
+
+Address of account
+
+Properties:
+
+-   Config: address
+-   Env Var: RCLONE_FROSTFS_ADDRESS
+-   Type: string
+-   Required: false
+
+--frostfs-password
+
+Password to decrypt wallet
+
+Properties:
+
+-   Config: password
+-   Env Var: RCLONE_FROSTFS_PASSWORD
+-   Type: string
+-   Required: false
+
+--frostfs-placement-policy
+
+Placement policy for new containers
+
+Properties:
+
+-   Config: placement_policy
+-   Env Var: RCLONE_FROSTFS_PLACEMENT_POLICY
+-   Type: string
+-   Default: "REP 3"
+-   Examples:
+    -   "REP 3"
+        -   Container will have 3 replicas
+
+--frostfs-container-creation-policy
+
+Container creation policy for new containers
+
+Properties:
+
+-   Config: container_creation_policy
+-   Env Var: RCLONE_FROSTFS_CONTAINER_CREATION_POLICY
+-   Type: string
+-   Default: "private"
+-   Examples:
+    -   "public-read-write"
+        -   Public container, anyone can read and write
+    -   "public-read"
+        -   Public container, owner can read and write, others can only
+            read
+    -   "private"
+        -   Private container, only owner has access to it
+
+Advanced options
+
+Here are the Advanced options specific to frostfs (Distributed,
+decentralized object storage FrostFS).
+
+--frostfs-description
+
+Description of the remote.
+
+Properties:
+
+-   Config: description
+-   Env Var: RCLONE_FROSTFS_DESCRIPTION
+-   Type: string
+-   Required: false
+
 FTP
 
 FTP is the File Transfer Protocol. Rclone FTP support is provided using
@@ -34097,13 +34668,12 @@ even in Windows Command Prompt:
     rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM
     rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM:
 
-Implicit TLS
+Implicit TLSutil.go
 
 Rlone FTP supports implicit FTP over TLS servers (FTPS). This has to be
 enabled in the FTP backend config for the remote, or with --ftp-tls. The
-default FTPS port is 990, not 21 and can be set with --ftp-port.
-
-Restricted filename characters
+default FTPS port is 990, not 21 and can be set with --ftp-port. util.go
+### Restricted filename characters
 
 In addition to the default restricted characters set the following
 characters are also replaced:
@@ -35946,15 +36516,23 @@ The conversion must result in a file with the same extension when the
 
 Here are some examples for allowed and prohibited conversions.
 
-  export-formats   import-formats   Upload Ext   Document Ext   Allowed
-  ---------------- ---------------- ------------ -------------- ---------
-  odt              odt              odt          odt            Yes
-  odt              docx,odt         odt          odt            Yes
-                   docx             docx         docx           Yes
-                   odt              odt          docx           No
-  odt,docx         docx,odt         docx         odt            No
-  docx,odt         docx,odt         docx         docx           Yes
-  docx,odt         docx,odt         odt          docx           No
+  -------------------------------------------------------------------------
+  export-formats    import-formats    Upload Ext   Document Ext   Allowed
+  ----------------- ----------------- ------------ -------------- ---------
+  odt               odt               odt          odt            Yes
+
+  odt               docx,odt          odt          odt            Yes
+
+                    docx              docx         docx           Yes
+
+                    odt               odt          docx           No
+
+  odt,docx          docx,odt          docx         odt            No
+
+  docx,odt          docx,odt          docx         docx           Yes
+
+  docx,odt          docx,odt          odt          docx           No
+  -------------------------------------------------------------------------
 
 This limitation can be disabled by specifying
 --drive-allow-import-name-change. When using this flag, rclone can
@@ -42575,8 +43153,9 @@ Properties:
 
 Upload chunk size.
 
-Note that this is stored in memory and there may be up to "--transfers"
-* "--azureblob-upload-concurrency" chunks stored at once in memory.
+Note that this is stored in memory and there may be up to
+"--transfers" * "--azureblob-upload-concurrency" chunks stored at once
+in memory.
 
 Properties:
 
@@ -43482,8 +44061,9 @@ Properties:
 
 Upload chunk size.
 
-Note that this is stored in memory and there may be up to "--transfers"
-* "--azurefile-upload-concurrency" chunks stored at once in memory.
+Note that this is stored in memory and there may be up to
+"--transfers" * "--azurefile-upload-concurrency" chunks stored at once
+in memory.
 
 Properties:
 
@@ -47846,8 +48426,9 @@ Chunk size for multipart uploads.
 
 Large files will be uploaded in chunks of this size.
 
-Note that this is stored in memory and there may be up to "--transfers"
-* "--pikpak-upload-concurrency" chunks stored at once in memory.
+Note that this is stored in memory and there may be up to
+"--transfers" * "--pikpak-upload-concurrency" chunks stored at once in
+memory.
 
 If you are transferring large files over high-speed links and you have
 enough memory, then increasing this will speed up the transfers.
@@ -62767,7 +63348,7 @@ Twitter
 
 You can also follow Nick on twitter for rclone announcements:
 
--   [@njcw](https://twitter.com/njcw)
+-   @njcw
 
 Email
 
diff --git a/bin/make_manual.py b/bin/make_manual.py
index c28398dfd..2ddf49f07 100755
--- a/bin/make_manual.py
+++ b/bin/make_manual.py
@@ -42,6 +42,7 @@ docs = [
     "dropbox.md",
     "filefabric.md",
     "filescom.md",
+    "frostfs.md",
     "ftp.md",
     "gofile.md",
     "googlecloudstorage.md",
diff --git a/docs/content/_index.md b/docs/content/_index.md
index 2fa03fb06..7736afe78 100644
--- a/docs/content/_index.md
+++ b/docs/content/_index.md
@@ -123,6 +123,7 @@ WebDAV or S3, that work out of the box.)
 {{< provider name="Enterprise File Fabric" home="https://storagemadeeasy.com/about/" config="/filefabric/" >}}
 {{< provider name="Fastmail Files" home="https://www.fastmail.com/" config="/webdav/#fastmail-files" >}}
 {{< provider name="Files.com" home="https://www.files.com/" config="/filescom/" >}}
+{{< provider name="FrostFS" home="https://git.frostfs.info/TrueCloudLab/" config="/frostfs/" >}}
 {{< provider name="FTP" home="https://en.wikipedia.org/wiki/File_Transfer_Protocol" config="/ftp/" >}}
 {{< provider name="Gofile" home="https://gofile.io/" config="/gofile/" >}}
 {{< provider name="Google Cloud Storage" home="https://cloud.google.com/storage/" config="/googlecloudstorage/" >}}
diff --git a/docs/content/commands/rclone.md b/docs/content/commands/rclone.md
index 4c861f498..f9956f61b 100644
--- a/docs/content/commands/rclone.md
+++ b/docs/content/commands/rclone.md
@@ -296,6 +296,21 @@ rclone [flags]
   -f, --filter stringArray                                  Add a file filtering rule
       --filter-from stringArray                             Read file filtering patterns from a file (use - to read from stdin)
       --fix-case                                            Force rename of case insensitive dest to match source
+      --frostfs-address string                              Address of account
+      --frostfs-ape-cache-invalidation-duration Duration    APE cache invalidation duration (default 8s)
+      --frostfs-ape-cache-invalidation-timeout Duration     APE cache invalidation timeout (default 24s)
+      --frostfs-ape-chain-check-interval Duration           The interval for verifying that the APE chain is saved in FrostFS (default 500ms)
+      --frostfs-connection-timeout Duration                 FrostFS connection timeout (default 4s)
+      --frostfs-container-creation-policy string            Container creation policy for new containers (default "private")
+      --frostfs-description string                          Description of the remote
+      --frostfs-endpoint string                             Endpoints to connect to FrostFS node
+      --frostfs-password string                             Password to decrypt wallet
+      --frostfs-placement-policy string                     Placement policy for new containers (default "REP 3")
+      --frostfs-rebalance-interval Duration                 FrostFS rebalance connections interval (default 15s)
+      --frostfs-request-timeout Duration                    FrostFS request timeout (default 12s)
+      --frostfs-rpc-endpoint string                         Endpoint to connect to Neo rpc node
+      --frostfs-session-expiration int                      FrostFS session expiration epoch (default 4294967295)
+      --frostfs-wallet string                               Path to wallet
       --fs-cache-expire-duration Duration                   Cache remotes for this long (0 to disable caching) (default 5m0s)
       --fs-cache-expire-interval Duration                   Interval to check for expired remotes (default 1m0s)
       --ftp-ask-password                                    Allow asking for FTP password when needed
@@ -929,7 +944,7 @@ rclone [flags]
       --use-json-log                                        Use json log format
       --use-mmap                                            Use mmap allocator (see docs)
       --use-server-modtime                                  Use server modified time instead of object metadata
-      --user-agent string                                   Set the user-agent to a specified string (default "rclone/v1.68.2")
+      --user-agent string                                   Set the user-agent to a specified string (default "rclone/v1.68.2-beta.8331.25cf42493.feature/add-frostfs-support")
   -v, --verbose count                                       Print lots more stuff (repeat for more)
   -V, --version                                             Print the version number
       --webdav-bearer-token string                          Bearer token instead of user/pass (e.g. a Macaroon)
diff --git a/docs/content/flags.md b/docs/content/flags.md
index 3e77f5c7f..a925fba6b 100644
--- a/docs/content/flags.md
+++ b/docs/content/flags.md
@@ -115,7 +115,7 @@ Flags for general networking and HTTP stuff.
       --tpslimit float                     Limit HTTP transactions per second to this
       --tpslimit-burst int                 Max burst of transactions for --tpslimit (default 1)
       --use-cookies                        Enable session cookiejar
-      --user-agent string                  Set the user-agent to a specified string (default "rclone/v1.68.2")
+      --user-agent string                  Set the user-agent to a specified string (default "rclone/v1.68.2-beta.8331.25cf42493.feature/add-frostfs-support")
 ```
 
 
@@ -552,6 +552,21 @@ Backend-only flags (these can be set in the config file also).
       --filescom-password string                            The password used to authenticate with Files.com (obscured)
       --filescom-site string                                Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com)
       --filescom-username string                            The username used to authenticate with Files.com
+      --frostfs-address string                              Address of account
+      --frostfs-ape-cache-invalidation-duration Duration    APE cache invalidation duration (default 8s)
+      --frostfs-ape-cache-invalidation-timeout Duration     APE cache invalidation timeout (default 24s)
+      --frostfs-ape-chain-check-interval Duration           The interval for verifying that the APE chain is saved in FrostFS (default 500ms)
+      --frostfs-connection-timeout Duration                 FrostFS connection timeout (default 4s)
+      --frostfs-container-creation-policy string            Container creation policy for new containers (default "private")
+      --frostfs-description string                          Description of the remote
+      --frostfs-endpoint string                             Endpoints to connect to FrostFS node
+      --frostfs-password string                             Password to decrypt wallet
+      --frostfs-placement-policy string                     Placement policy for new containers (default "REP 3")
+      --frostfs-rebalance-interval Duration                 FrostFS rebalance connections interval (default 15s)
+      --frostfs-request-timeout Duration                    FrostFS request timeout (default 12s)
+      --frostfs-rpc-endpoint string                         Endpoint to connect to Neo rpc node
+      --frostfs-session-expiration int                      FrostFS session expiration epoch (default 4294967295)
+      --frostfs-wallet string                               Path to wallet
       --ftp-ask-password                                    Allow asking for FTP password when needed
       --ftp-close-timeout Duration                          Maximum time to wait for a response to close (default 1m0s)
       --ftp-concurrency int                                 Maximum number of FTP simultaneous connections, 0 for unlimited
diff --git a/docs/content/frostfs.md b/docs/content/frostfs.md
new file mode 100644
index 000000000..d066433cc
--- /dev/null
+++ b/docs/content/frostfs.md
@@ -0,0 +1,466 @@
+---
+title: "FrostFS"
+description: "Rclone docs for FrostFS backend"
+versionIntroduced: "---"
+---
+
+# {{< icon "fa fa-file" >}} FrostFS
+
+Rclone FrostFS support is provided using the
+[git.frostfs.info/TrueCloudLab/frostfs-sdk-go](https://git.frostfs.info/TrueCloudLab/frostfs-sdk-go) package
+
+## Configuration
+
+To create an FrostFS configuration named `remote`, run
+
+    rclone config
+
+Rclone config guides you through an interactive setup process. A minimal
+rclone FrostFS remote definition only requires endpoint and path to FrostFS user wallet.
+
+
+```
+No remotes found, make a new one?
+n) New remote
+s) Set configuration password
+q) Quit config
+n/s/q> n
+
+Enter name for new remote.
+name> remote
+
+Option Storage.
+Type of storage to configure.
+Choose a number from below, or type in your own value.
+ 1 / 1Fichier
+   \ (fichier)
+ 2 / Akamai NetStorage
+   \ (netstorage)
+ 3 / Alias for an existing remote
+   \ (alias)
+ 4 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others
+   \ (s3)
+ 5 / Backblaze B2
+   \ (b2)
+ 6 / Better checksums for other remotes
+   \ (hasher)
+ 7 / Box
+   \ (box)
+ 8 / Cache a remote
+   \ (cache)
+ 9 / Citrix Sharefile
+   \ (sharefile)
+10 / Combine several remotes into one
+   \ (combine)
+11 / Compress a remote
+   \ (compress)
+12 / Distributed, decentralized object storage FrostFS
+   \ (frostfs)
+13 / Dropbox
+   \ (dropbox)
+14 / Encrypt/Decrypt a remote
+   \ (crypt)
+15 / Enterprise File Fabric
+   \ (filefabric)
+16 / FTP
+   \ (ftp)
+17 / Files.com
+   \ (filescom)
+18 / Gofile
+   \ (gofile)
+19 / Google Cloud Storage (this is not Google Drive)
+   \ (google cloud storage)
+20 / Google Drive
+   \ (drive)
+21 / Google Photos
+   \ (google photos)
+22 / HTTP
+   \ (http)
+23 / Hadoop distributed file system
+   \ (hdfs)
+24 / HiDrive
+   \ (hidrive)
+25 / ImageKit.io
+   \ (imagekit)
+26 / In memory object storage system.
+   \ (memory)
+27 / Internet Archive
+   \ (internetarchive)
+28 / Jottacloud
+   \ (jottacloud)
+29 / Koofr, Digi Storage and other Koofr-compatible storage providers
+   \ (koofr)
+30 / Linkbox
+   \ (linkbox)
+31 / Local Disk
+   \ (local)
+32 / Mail.ru Cloud
+   \ (mailru)
+33 / Mega
+   \ (mega)
+34 / Microsoft Azure Blob Storage
+   \ (azureblob)
+35 / Microsoft Azure Files
+   \ (azurefiles)
+36 / Microsoft OneDrive
+   \ (onedrive)
+37 / OpenDrive
+   \ (opendrive)
+38 / OpenStack Swift (Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)
+   \ (swift)
+39 / Oracle Cloud Infrastructure Object Storage
+   \ (oracleobjectstorage)
+40 / Pcloud
+   \ (pcloud)
+41 / PikPak
+   \ (pikpak)
+42 / Pixeldrain Filesystem
+   \ (pixeldrain)
+43 / Proton Drive
+   \ (protondrive)
+44 / Put.io
+   \ (putio)
+45 / QingCloud Object Storage
+   \ (qingstor)
+46 / Quatrix by Maytech
+   \ (quatrix)
+47 / SMB / CIFS
+   \ (smb)
+48 / SSH/SFTP
+   \ (sftp)
+49 / Sia Decentralized Cloud
+   \ (sia)
+50 / Storj Decentralized Cloud Storage
+   \ (storj)
+51 / Sugarsync
+   \ (sugarsync)
+52 / Transparently chunk/split large files
+   \ (chunker)
+53 / Uloz.to
+   \ (ulozto)
+54 / Union merges the contents of several upstream fs
+   \ (union)
+55 / Uptobox
+   \ (uptobox)
+56 / WebDAV
+   \ (webdav)
+57 / Yandex Disk
+   \ (yandex)
+58 / Zoho
+   \ (zoho)
+59 / premiumize.me
+   \ (premiumizeme)
+60 / seafile
+   \ (seafile)
+Storage> frostfs
+
+Option endpoint.
+Endpoints to connect to FrostFS node
+Choose a number from below, or type in your own value.
+ 1 / One endpoint.
+   \ (s01.frostfs.devenv:8080)
+ 2 / Multiple endpoints to form pool.
+   \ (s01.frostfs.devenv:8080 s02.frostfs.devenv:8080)
+ 3 / Multiple endpoints with priority (less value is higher priority). Until s01 is healthy all request will be send to it.
+   \ (s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2)
+ 4 / Multiple endpoints with priority and weights. After s01 is unhealthy requests will be send to s02 and s03 in proportions 10% and 90% respectively.
+   \ (s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1 s03.frostfs.devenv:8080,2,9)
+endpoint> s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+
+Option connection_timeout.
+FrostFS connection timeout
+Enter a value of type Duration. Press Enter for the default (4s).
+connection_timeout> 
+
+Option request_timeout.
+FrostFS request timeout
+Enter a value of type Duration. Press Enter for the default (12s).
+request_timeout> 
+
+Option rebalance_interval.
+FrostFS rebalance connections interval
+Enter a value of type Duration. Press Enter for the default (15s).
+rebalance_interval> 
+
+Option session_expiration.
+FrostFS session expiration epoch
+Enter a signed integer. Press Enter for the default (4294967295).
+session_expiration> 
+
+Option ape_cache_invalidation_duration.
+APE cache invalidation duration
+Enter a value of type Duration. Press Enter for the default (8s).
+ape_cache_invalidation_duration> 
+
+Option ape_cache_invalidation_timeout.
+APE cache invalidation timeout
+Enter a value of type Duration. Press Enter for the default (24s).
+ape_cache_invalidation_timeout> 
+
+Option ape_chain_check_interval.
+The interval for verifying that the APE chain is saved in FrostFS.
+Enter a value of type Duration. Press Enter for the default (500ms).
+ape_chain_check_interval> 
+
+Option rpc_endpoint.
+Endpoint to connect to Neo rpc node
+Enter a value. Press Enter to leave empty.
+rpc_endpoint> 
+
+Option wallet.
+Path to wallet
+Enter a value.
+wallet> /wallets/wallet.conf
+
+Option address.
+Address of account
+Enter a value. Press Enter to leave empty.
+address> 
+
+Option password.
+Password to decrypt wallet
+Enter a value. Press Enter to leave empty.
+password> 
+
+Option placement_policy.
+Placement policy for new containers
+Choose a number from below, or type in your own value of type string.
+Press Enter for the default (REP 3).
+ 1 / Container will have 3 replicas
+   \ (REP 3)
+placement_policy> REP 1
+
+Option container_creation_policy.
+Container creation policy for new containers
+Choose a number from below, or type in your own value of type string.
+Press Enter for the default (private).
+ 1 / Public container, anyone can read and write
+   \ (public-read-write)
+ 2 / Public container, owner can read and write, others can only read
+   \ (public-read)
+ 3 / Private container, only owner has access to it
+   \ (private)
+container_creation_policy> 
+
+Edit advanced config?
+y) Yes
+n) No (default)
+y/n> n
+
+Configuration complete.
+Options:
+- type: frostfs
+- endpoint: s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+- password: M@zPGpWDravchenko/develop/go/playground/play_with_ape/cfg/wallet_akrav.js
+- placement_policy: REP 1
+Keep this "remote" remote?
+y) Yes this is OK (default)
+e) Edit this remote
+d) Delete this remote
+y/e/d> y
+```
+
+As a remote root directory, you can use either the container identifier or its user-friendly name.
+If you choose to use a container name, rclone will create a new container with that name when 
+it's used for the first time.
+
+For example, both of the following commands would be valid if there was a `~/test-copy` directory and a container with
+the identifier `23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf`:
+
+    rclone copy ~/test-copy remote:23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf/test-copy
+    rclone copy ~/test-copy remote:container-name/test-copy
+
+{{< rem autogenerated options start" - DO NOT EDIT - instead edit fs.RegInfo in backend/frostfs/frostfs.go then run make backenddocs" >}}
+### Standard options
+
+Here are the Standard options specific to frostfs (Distributed, decentralized object storage FrostFS).
+
+#### --frostfs-endpoint
+
+Endpoints to connect to FrostFS node
+
+Properties:
+
+- Config:      endpoint
+- Env Var:     RCLONE_FROSTFS_ENDPOINT
+- Type:        string
+- Required:    true
+- Examples:
+    - "s01.frostfs.devenv:8080"
+        - One endpoint.
+    - "s01.frostfs.devenv:8080 s02.frostfs.devenv:8080"
+        - Multiple endpoints to form pool.
+    - "s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2"
+        - Multiple endpoints with priority (lower value has higher priority). Until s01 is healthy, all requests will be sent to it.
+    - "s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1 s03.frostfs.devenv:8080,2,9"
+        - Multiple endpoints with priority and weights. After the s01 endpoint is unhealthy, requests will be sent to the s02 and s03 endpoints in proportions of 10% and 90%, respectively.
+
+#### --frostfs-connection-timeout
+
+FrostFS connection timeout
+
+Properties:
+
+- Config:      connection_timeout
+- Env Var:     RCLONE_FROSTFS_CONNECTION_TIMEOUT
+- Type:        Duration
+- Default:     4s
+
+#### --frostfs-request-timeout
+
+FrostFS request timeout
+
+Properties:
+
+- Config:      request_timeout
+- Env Var:     RCLONE_FROSTFS_REQUEST_TIMEOUT
+- Type:        Duration
+- Default:     12s
+
+#### --frostfs-rebalance-interval
+
+FrostFS rebalance connections interval
+
+Properties:
+
+- Config:      rebalance_interval
+- Env Var:     RCLONE_FROSTFS_REBALANCE_INTERVAL
+- Type:        Duration
+- Default:     15s
+
+#### --frostfs-session-expiration
+
+FrostFS session expiration epoch
+
+Properties:
+
+- Config:      session_expiration
+- Env Var:     RCLONE_FROSTFS_SESSION_EXPIRATION
+- Type:        int
+- Default:     4294967295
+
+#### --frostfs-ape-cache-invalidation-duration
+
+APE cache invalidation duration
+
+Properties:
+
+- Config:      ape_cache_invalidation_duration
+- Env Var:     RCLONE_FROSTFS_APE_CACHE_INVALIDATION_DURATION
+- Type:        Duration
+- Default:     8s
+
+#### --frostfs-ape-cache-invalidation-timeout
+
+APE cache invalidation timeout
+
+Properties:
+
+- Config:      ape_cache_invalidation_timeout
+- Env Var:     RCLONE_FROSTFS_APE_CACHE_INVALIDATION_TIMEOUT
+- Type:        Duration
+- Default:     24s
+
+#### --frostfs-ape-chain-check-interval
+
+The interval for verifying that the APE chain is saved in FrostFS.
+
+Properties:
+
+- Config:      ape_chain_check_interval
+- Env Var:     RCLONE_FROSTFS_APE_CHAIN_CHECK_INTERVAL
+- Type:        Duration
+- Default:     500ms
+
+#### --frostfs-rpc-endpoint
+
+Endpoint to connect to Neo rpc node
+
+Properties:
+
+- Config:      rpc_endpoint
+- Env Var:     RCLONE_FROSTFS_RPC_ENDPOINT
+- Type:        string
+- Required:    false
+
+#### --frostfs-wallet
+
+Path to wallet
+
+Properties:
+
+- Config:      wallet
+- Env Var:     RCLONE_FROSTFS_WALLET
+- Type:        string
+- Required:    true
+
+#### --frostfs-address
+
+Address of account
+
+Properties:
+
+- Config:      address
+- Env Var:     RCLONE_FROSTFS_ADDRESS
+- Type:        string
+- Required:    false
+
+#### --frostfs-password
+
+Password to decrypt wallet
+
+Properties:
+
+- Config:      password
+- Env Var:     RCLONE_FROSTFS_PASSWORD
+- Type:        string
+- Required:    false
+
+#### --frostfs-placement-policy
+
+Placement policy for new containers
+
+Properties:
+
+- Config:      placement_policy
+- Env Var:     RCLONE_FROSTFS_PLACEMENT_POLICY
+- Type:        string
+- Default:     "REP 3"
+- Examples:
+    - "REP 3"
+        - Container will have 3 replicas
+
+#### --frostfs-container-creation-policy
+
+Container creation policy for new containers
+
+Properties:
+
+- Config:      container_creation_policy
+- Env Var:     RCLONE_FROSTFS_CONTAINER_CREATION_POLICY
+- Type:        string
+- Default:     "private"
+- Examples:
+    - "public-read-write"
+        - Public container, anyone can read and write
+    - "public-read"
+        - Public container, owner can read and write, others can only read
+    - "private"
+        - Private container, only owner has access to it
+
+### Advanced options
+
+Here are the Advanced options specific to frostfs (Distributed, decentralized object storage FrostFS).
+
+#### --frostfs-description
+
+Description of the remote.
+
+Properties:
+
+- Config:      description
+- Env Var:     RCLONE_FROSTFS_DESCRIPTION
+- Type:        string
+- Required:    false
+
+{{< rem autogenerated options stop >}}
diff --git a/rclone.1 b/rclone.1
index b58d90d0b..38306f409 100644
--- a/rclone.1
+++ b/rclone.1
@@ -1,7 +1,21 @@
-.\"t
-.\" Automatically generated by Pandoc 2.9.2.1
+'\" t
+.\" Automatically generated by Pandoc 3.1.3
 .\"
-.TH "rclone" "1" "Nov 15, 2024" "User Manual" ""
+.\" Define V font for inline verbatim, using C font in formats
+.\" that render this, and otherwise B font.
+.ie "\f[CB]x\f[]"x" \{\
+. ftr V B
+. ftr VI BI
+. ftr VB B
+. ftr VBI BI
+.\}
+.el \{\
+. ftr V CR
+. ftr VI CI
+. ftr VB CB
+. ftr VBI CBI
+.\}
+.TH "rclone" "1" "Jan 10, 2025" "User Manual" ""
 .hy
 .SH Rclone syncs your files to cloud storage
 .PP
@@ -31,7 +45,7 @@ transfer protocols.
 Rclone has powerful cloud equivalents to the unix commands rsync, cp,
 mv, mount, ls, ncdu, tree, rm, and cat.
 Rclone\[aq]s familiar syntax includes shell pipeline support, and
-\f[C]--dry-run\f[R] protection.
+\f[V]--dry-run\f[R] protection.
 It is used at the command line, in scripts or via its API.
 .PP
 Users call rclone \f[I]\[dq]The Swiss army knife of cloud
@@ -180,6 +194,8 @@ Fastmail Files
 .IP \[bu] 2
 Files.com
 .IP \[bu] 2
+FrostFS
+.IP \[bu] 2
 FTP
 .IP \[bu] 2
 Gofile
@@ -351,10 +367,10 @@ Rclone is a Go program and comes as a single binary file.
 .IP \[bu] 2
 Download (https://rclone.org/downloads/) the relevant binary.
 .IP \[bu] 2
-Extract the \f[C]rclone\f[R] executable, \f[C]rclone.exe\f[R] on
+Extract the \f[V]rclone\f[R] executable, \f[V]rclone.exe\f[R] on
 Windows, from the archive.
 .IP \[bu] 2
-Run \f[C]rclone config\f[R] to setup.
+Run \f[V]rclone config\f[R] to setup.
 See rclone config docs (https://rclone.org/docs/) for more details.
 .IP \[bu] 2
 Optionally configure automatic execution.
@@ -362,7 +378,7 @@ Optionally configure automatic execution.
 See below for some expanded Linux / macOS / Windows instructions.
 .PP
 See the usage (https://rclone.org/docs/) docs for how to use rclone, or
-run \f[C]rclone -h\f[R].
+run \f[V]rclone -h\f[R].
 .PP
 Already installed rclone can be easily updated to the latest version
 using the rclone
@@ -423,7 +439,7 @@ sudo mandb
 \f[R]
 .fi
 .PP
-Run \f[C]rclone config\f[R] to setup.
+Run \f[V]rclone config\f[R] to setup.
 See rclone config docs (https://rclone.org/docs/) for more details.
 .IP
 .nf
@@ -440,7 +456,7 @@ brew install rclone
 \f[R]
 .fi
 .PP
-NOTE: This version of rclone will not support \f[C]mount\f[R] any more
+NOTE: This version of rclone will not support \f[V]mount\f[R] any more
 (see #5373 (https://github.com/rclone/rclone/issues/5373)).
 If mounting is wanted on macOS, either install a precompiled binary or
 enable the relevant option when installing from source.
@@ -473,7 +489,7 @@ More information here (https://ports.macports.org/port/rclone/).
 .SS Precompiled binary, using curl
 .PP
 To avoid problems with macOS gatekeeper enforcing the binary to be
-signed and notarized it is enough to download with \f[C]curl\f[R].
+signed and notarized it is enough to download with \f[V]curl\f[R].
 .PP
 Download the latest version of rclone.
 .IP
@@ -501,7 +517,7 @@ sudo mv rclone /usr/local/bin/
 \f[R]
 .fi
 .PP
-(the \f[C]mkdir\f[R] command is safe to run, even if the directory
+(the \f[V]mkdir\f[R] command is safe to run, even if the directory
 already exists).
 .PP
 Remove the leftover files.
@@ -512,7 +528,7 @@ cd .. && rm -rf rclone-*-osx-amd64 rclone-current-osx-amd64.zip
 \f[R]
 .fi
 .PP
-Run \f[C]rclone config\f[R] to setup.
+Run \f[V]rclone config\f[R] to setup.
 See rclone config docs (https://rclone.org/docs/) for more details.
 .IP
 .nf
@@ -524,7 +540,7 @@ rclone config
 .PP
 When downloading a binary with a web browser, the browser will set the
 macOS gatekeeper quarantine attribute.
-Starting from Catalina, when attempting to run \f[C]rclone\f[R], a
+Starting from Catalina, when attempting to run \f[V]rclone\f[R], a
 pop-up will appear saying:
 .IP
 .nf
@@ -557,7 +573,7 @@ Bit (https://downloads.rclone.org/rclone-current-windows-386.zip)
 ARM - 64
 Bit (https://downloads.rclone.org/rclone-current-windows-arm64.zip)
 .PP
-Open this file in the Explorer and extract \f[C]rclone.exe\f[R].
+Open this file in the Explorer and extract \f[V]rclone.exe\f[R].
 Rclone is a portable executable so you can place it wherever is
 convenient.
 .PP
@@ -565,7 +581,7 @@ Open a CMD window (or powershell) and run the binary.
 Note that rclone does not launch a GUI by default, it runs in the CMD
 Window.
 .IP \[bu] 2
-Run \f[C]rclone.exe config\f[R] to setup.
+Run \f[V]rclone.exe config\f[R] to setup.
 See rclone config docs (https://rclone.org/docs/) for more details.
 .IP \[bu] 2
 Optionally configure automatic execution.
@@ -664,11 +680,11 @@ rclone (https://hub.docker.com/r/rclone/rclone).
 These images are built as part of the release process based on a minimal
 Alpine Linux.
 .PP
-The \f[C]:latest\f[R] tag will always point to the latest stable
+The \f[V]:latest\f[R] tag will always point to the latest stable
 release.
-You can use the \f[C]:beta\f[R] tag to get the latest build from master.
+You can use the \f[V]:beta\f[R] tag to get the latest build from master.
 You can also use version tags, e.g.
-\f[C]:1.49.1\f[R], \f[C]:1.49\f[R] or \f[C]:1\f[R].
+\f[V]:1.49.1\f[R], \f[V]:1.49\f[R] or \f[V]:1\f[R].
 .IP
 .nf
 \f[C]
@@ -686,14 +702,14 @@ rclone v1.49.1
 There are a few command line options to consider when starting an rclone
 Docker container from the rclone image.
 .IP \[bu] 2
-You need to mount the host rclone config dir at \f[C]/config/rclone\f[R]
+You need to mount the host rclone config dir at \f[V]/config/rclone\f[R]
 into the Docker container.
 Due to the fact that rclone updates tokens inside its config file, and
 that the update process involves a file rename, you need to mount the
 whole host rclone config dir, not just the single host rclone config
 file.
 .IP \[bu] 2
-You need to mount a host data dir at \f[C]/data\f[R] into the Docker
+You need to mount a host data dir at \f[V]/data\f[R] into the Docker
 container.
 .IP \[bu] 2
 By default, the rclone binary inside a Docker container runs with UID=0
@@ -703,28 +719,28 @@ If your config and data files reside on the host with a non-root
 UID:GID, you need to pass these on the container start command line.
 .IP \[bu] 2
 If you want to access the RC interface (either via the API or the Web
-UI), it is required to set the \f[C]--rc-addr\f[R] to \f[C]:5572\f[R] in
+UI), it is required to set the \f[V]--rc-addr\f[R] to \f[V]:5572\f[R] in
 order to connect to it from outside the container.
 An explanation about why this is necessary is present
 here (https://web.archive.org/web/20200808071950/https://pythonspeed.com/articles/docker-connection-refused/).
 .RS 2
 .IP \[bu] 2
 NOTE: Users running this container with the docker network set to
-\f[C]host\f[R] should probably set it to listen to localhost only, with
-\f[C]127.0.0.1:5572\f[R] as the value for \f[C]--rc-addr\f[R]
+\f[V]host\f[R] should probably set it to listen to localhost only, with
+\f[V]127.0.0.1:5572\f[R] as the value for \f[V]--rc-addr\f[R]
 .RE
 .IP \[bu] 2
-It is possible to use \f[C]rclone mount\f[R] inside a userspace Docker
+It is possible to use \f[V]rclone mount\f[R] inside a userspace Docker
 container, and expose the resulting fuse mount to the host.
-The exact \f[C]docker run\f[R] options to do that might vary slightly
+The exact \f[V]docker run\f[R] options to do that might vary slightly
 between hosts.
 See, e.g.
 the discussion in this
 thread (https://github.com/moby/moby/issues/9448).
 .RS 2
 .PP
-You also need to mount the host \f[C]/etc/passwd\f[R] and
-\f[C]/etc/group\f[R] for fuse to work inside the container.
+You also need to mount the host \f[V]/etc/passwd\f[R] and
+\f[V]/etc/group\f[R] for fuse to work inside the container.
 .RE
 .PP
 Here are some commands tested on an Ubuntu 18.04.3 host:
@@ -785,8 +801,8 @@ Default config directory:
 /home/$USER/snap/rclone/current/.config/rclone
 .RE
 .PP
-Note: Due to the strict confinement of Snap, \f[C]rclone mount\f[R]
-feature is \f[C]not\f[R] supported.
+Note: Due to the strict confinement of Snap, \f[V]rclone mount\f[R]
+feature is \f[V]not\f[R] supported.
 .PP
 If mounting is wanted, either install a precompiled binary or enable the
 relevant option when installing from source.
@@ -816,12 +832,12 @@ go build
 This will check out the rclone source in subfolder rclone, which you can
 later modify and send pull requests with.
 Then it will build the rclone executable in the same folder.
-As an initial check you can now run \f[C]./rclone version\f[R]
-(\f[C].\[rs]rclone version\f[R] on Windows).
+As an initial check you can now run \f[V]./rclone version\f[R]
+(\f[V].\[rs]rclone version\f[R] on Windows).
 .PP
 Note that on macOS and Windows the
 mount (https://rclone.org/commands/rclone_mount/) command will not be
-available unless you specify an additional build tag \f[C]cmount\f[R].
+available unless you specify an additional build tag \f[V]cmount\f[R].
 .IP
 .nf
 \f[C]
@@ -849,11 +865,11 @@ feature selected.
 If building with cgo, you must also set environment variable CPATH
 pointing to the fuse include directory within the WinFsp installation
 (normally
-\f[C]C:\[rs]Program Files (x86)\[rs]WinFsp\[rs]inc\[rs]fuse\f[R]).
+\f[V]C:\[rs]Program Files (x86)\[rs]WinFsp\[rs]inc\[rs]fuse\f[R]).
 .PP
-You may add arguments \f[C]-ldflags -s\f[R] to omit symbol table and
+You may add arguments \f[V]-ldflags -s\f[R] to omit symbol table and
 debug information, making the executable file smaller, and
-\f[C]-trimpath\f[R] to remove references to local file system paths.
+\f[V]-trimpath\f[R] to remove references to local file system paths.
 The official rclone releases are built with both of these.
 .IP
 .nf
@@ -863,12 +879,12 @@ go build -trimpath -ldflags -s -tags cmount
 .fi
 .PP
 If you want to customize the version string, as reported by the
-\f[C]rclone version\f[R] command, you can set one of the variables
-\f[C]fs.Version\f[R], \f[C]fs.VersionTag\f[R] (to keep default suffix
-but customize the number), or \f[C]fs.VersionSuffix\f[R] (to keep
+\f[V]rclone version\f[R] command, you can set one of the variables
+\f[V]fs.Version\f[R], \f[V]fs.VersionTag\f[R] (to keep default suffix
+but customize the number), or \f[V]fs.VersionSuffix\f[R] (to keep
 default number but customize the suffix).
 This can be done from the build command, by adding to the
-\f[C]-ldflags\f[R] argument value as shown below.
+\f[V]-ldflags\f[R] argument value as shown below.
 .IP
 .nf
 \f[C]
@@ -882,7 +898,7 @@ To get that with your own build you need to run the following command
 \f[B]before\f[R] the build command.
 It generates a Windows resource system object file, with extension
 \&.syso, e.g.
-\f[C]resource_windows_amd64.syso\f[R], that will be automatically picked
+\f[V]resource_windows_amd64.syso\f[R], that will be automatically picked
 up by future build commands.
 .IP
 .nf
@@ -906,13 +922,13 @@ go run bin/resource_windows.go -version v9.9.9-test
 \f[R]
 .fi
 .PP
-Instead of executing the \f[C]go build\f[R] command directly, you can
+Instead of executing the \f[V]go build\f[R] command directly, you can
 run it via the Makefile.
 The default target changes the version suffix from \[dq]-DEV\[dq] to
 \[dq]-beta\[dq] followed by additional commit details, embeds version
 information binary resources on Windows, and copies the resulting rclone
-executable into your GOPATH bin folder (\f[C]$(go env GOPATH)/bin\f[R],
-which corresponds to \f[C]\[ti]/go/bin/rclone\f[R] by default).
+executable into your GOPATH bin folder (\f[V]$(go env GOPATH)/bin\f[R],
+which corresponds to \f[V]\[ti]/go/bin/rclone\f[R] by default).
 .IP
 .nf
 \f[C]
@@ -940,8 +956,8 @@ source, build and install rclone - all in one operation, as a regular Go
 package.
 The source will be stored it in the Go module cache, and the resulting
 executable will be in your GOPATH bin folder
-(\f[C]$(go env GOPATH)/bin\f[R], which corresponds to
-\f[C]\[ti]/go/bin/rclone\f[R] by default).
+(\f[V]$(go env GOPATH)/bin\f[R], which corresponds to
+\f[V]\[ti]/go/bin/rclone\f[R] by default).
 .IP
 .nf
 \f[C]
@@ -953,9 +969,9 @@ In some situations, rclone executable size might be too big for
 deployment in very restricted environments when all backends with large
 SDKs are included.
 To limit binary size unused backends can be commented out in
-\f[C]backends/all/all.go\f[R] and unused commands in
-\f[C]cmd/all/all.go\f[R] before building with \f[C]go build\f[R] or
-\f[C]make\f[R]
+\f[V]backends/all/all.go\f[R] and unused commands in
+\f[V]cmd/all/all.go\f[R] before building with \f[V]go build\f[R] or
+\f[V]make\f[R]
 .SS Ansible installation
 .PP
 This can be done with Stefan Weichinger\[aq]s ansible
@@ -963,7 +979,7 @@ role (https://github.com/stefangweichinger/ansible-rclone).
 .PP
 Instructions
 .IP "1." 3
-\f[C]git clone https://github.com/stefangweichinger/ansible-rclone.git\f[R]
+\f[V]git clone https://github.com/stefangweichinger/ansible-rclone.git\f[R]
 into your local roles-directory
 .IP "2." 3
 add the role to the hosts you want rclone installed to:
@@ -978,7 +994,7 @@ add the role to the hosts you want rclone installed to:
 .SS Portable installation
 .PP
 As mentioned above (https://rclone.org/install/#quickstart), rclone is
-single executable (\f[C]rclone\f[R], or \f[C]rclone.exe\f[R] on Windows)
+single executable (\f[V]rclone\f[R], or \f[V]rclone.exe\f[R] on Windows)
 that you can download as a zip archive and extract into a location of
 your choosing.
 When executing different commands, it may create files in different
@@ -1033,11 +1049,11 @@ window.
 When configuring rclone to run from task scheduler and windows service
 you are able to set it to run hidden in background.
 From rclone version 1.54 you can also make it run hidden from anywhere
-by adding option \f[C]--no-console\f[R] (it may still flash briefly when
+by adding option \f[V]--no-console\f[R] (it may still flash briefly when
 the program starts).
 Since rclone normally writes information and any error messages to the
 console, you must redirect this to a file to be able to see it.
-Rclone has a built-in option \f[C]--log-file\f[R] for that.
+Rclone has a built-in option \f[V]--log-file\f[R] for that.
 .PP
 Example command to run a sync in background:
 .IP
@@ -1052,24 +1068,24 @@ As mentioned in the mount (https://rclone.org/commands/rclone_mount/)
 documentation, mounted drives created as Administrator are not visible
 to other accounts, not even the account that was elevated as
 Administrator.
-By running the mount command as the built-in \f[C]SYSTEM\f[R] user
+By running the mount command as the built-in \f[V]SYSTEM\f[R] user
 account, it will create drives accessible for everyone on the system.
 Both scheduled task and Windows service can be used to achieve this.
 .PP
-NOTE: Remember that when rclone runs as the \f[C]SYSTEM\f[R] user, the
+NOTE: Remember that when rclone runs as the \f[V]SYSTEM\f[R] user, the
 user profile that it sees will not be yours.
 This means that if you normally run rclone with configuration file in
 the default location, to be able to use the same configuration when
 running as the system user you must explicitly tell rclone where to find
 it with the
-\f[C]--config\f[R] (https://rclone.org/docs/#config-config-file) option,
+\f[V]--config\f[R] (https://rclone.org/docs/#config-config-file) option,
 or else it will look in the system users profile path
-(\f[C]C:\[rs]Windows\[rs]System32\[rs]config\[rs]systemprofile\f[R]).
+(\f[V]C:\[rs]Windows\[rs]System32\[rs]config\[rs]systemprofile\f[R]).
 To test your command manually from a Command Prompt, you can run it with
 the
 PsExec (https://docs.microsoft.com/en-us/sysinternals/downloads/psexec)
 utility from Microsoft\[aq]s Sysinternals suite, which takes option
-\f[C]-s\f[R] to execute commands as the \f[C]SYSTEM\f[R] user.
+\f[V]-s\f[R] to execute commands as the \f[V]SYSTEM\f[R] user.
 .SS Start from Startup folder
 .PP
 To quickly execute an rclone command you can simply create a standard
@@ -1078,9 +1094,9 @@ run.
 If you store this shortcut in the special \[dq]Startup\[dq] start-menu
 folder, Windows will automatically run it at login.
 To open this folder in Windows Explorer, enter path
-\f[C]%APPDATA%\[rs]Microsoft\[rs]Windows\[rs]Start Menu\[rs]Programs\[rs]Startup\f[R],
+\f[V]%APPDATA%\[rs]Microsoft\[rs]Windows\[rs]Start Menu\[rs]Programs\[rs]Startup\f[R],
 or
-\f[C]C:\[rs]ProgramData\[rs]Microsoft\[rs]Windows\[rs]Start Menu\[rs]Programs\[rs]StartUp\f[R]
+\f[V]C:\[rs]ProgramData\[rs]Microsoft\[rs]Windows\[rs]Start Menu\[rs]Programs\[rs]StartUp\f[R]
 if you want the command to start for \f[I]every\f[R] user that logs in.
 .PP
 This is the easiest approach to autostarting of rclone, but it offers no
@@ -1096,7 +1112,7 @@ configurable way, e.g.
 periodically on a schedule, on user log on, or at system startup.
 It can run be configured to run as the current user, or for a mount
 command that needs to be available to all users it can run as the
-\f[C]SYSTEM\f[R] user.
+\f[V]SYSTEM\f[R] user.
 For technical information, see
 https://docs.microsoft.com/windows/win32/taskschd/task-scheduler-start-page.
 .SS Run as service
@@ -1109,11 +1125,11 @@ configured to run at startup.
 For mount commands, rclone has a built-in Windows service integration
 via the third-party WinFsp library it uses.
 Registering as a regular Windows service easy, as you just have to
-execute the built-in PowerShell command \f[C]New-Service\f[R] (requires
+execute the built-in PowerShell command \f[V]New-Service\f[R] (requires
 administrative privileges).
 .PP
 Example of a PowerShell command that creates a Windows service for
-mounting some \f[C]remote:/files\f[R] as drive letter \f[C]X:\f[R], for
+mounting some \f[V]remote:/files\f[R] as drive letter \f[V]X:\f[R], for
 \f[I]all\f[R] users (service will be running as the local system
 account):
 .IP
@@ -1185,7 +1201,7 @@ options, and more.
 First, you\[aq]ll need to configure rclone.
 As the object storage systems have quite complicated authentication
 these are kept in a config file.
-(See the \f[C]--config\f[R] entry for how to find the config file and
+(See the \f[V]--config\f[R] entry for how to find the config file and
 choose its location.)
 .PP
 The easiest way to make the config is to run rclone with the config
@@ -1335,20 +1351,20 @@ rclone subcommand [options] <parameters> <parameters...>
 \f[R]
 .fi
 .PP
-A \f[C]subcommand\f[R] is a the rclone operation required, (e.g.
-\f[C]sync\f[R], \f[C]copy\f[R], \f[C]ls\f[R]).
+A \f[V]subcommand\f[R] is a the rclone operation required, (e.g.
+\f[V]sync\f[R], \f[V]copy\f[R], \f[V]ls\f[R]).
 .PP
-An \f[C]option\f[R] is a single letter flag (e.g.
-\f[C]-v\f[R]) or a group of single letter flags (e.g.
-\f[C]-Pv\f[R]) or a long flag (e.g.
-\f[C]--progress\f[R]).
+An \f[V]option\f[R] is a single letter flag (e.g.
+\f[V]-v\f[R]) or a group of single letter flags (e.g.
+\f[V]-Pv\f[R]) or a long flag (e.g.
+\f[V]--progress\f[R]).
 No options are required.
-Options can come after the \f[C]subcommand\f[R] or in between parameters
+Options can come after the \f[V]subcommand\f[R] or in between parameters
 too or on the end, but only global options can be used before the
-\f[C]subcommand\f[R].
-Anything after a \f[C]--\f[R] option will not be interpreted as an
-option so if you need to add a parameter which starts with a \f[C]-\f[R]
-then put a \f[C]--\f[R] on its own first, eg
+\f[V]subcommand\f[R].
+Anything after a \f[V]--\f[R] option will not be interpreted as an
+option so if you need to add a parameter which starts with a \f[V]-\f[R]
+then put a \f[V]--\f[R] on its own first, eg
 .IP
 .nf
 \f[C]
@@ -1356,9 +1372,9 @@ rclone lsf -- -directory-starting-with-dash
 \f[R]
 .fi
 .PP
-A \f[C]parameter\f[R] is usually a file path or rclone remote, eg
-\f[C]/path/to/file\f[R] or \f[C]remote:path/to/file\f[R] but it can be
-other things - the \f[C]subcommand\f[R] help will tell you what.
+A \f[V]parameter\f[R] is usually a file path or rclone remote, eg
+\f[V]/path/to/file\f[R] or \f[V]remote:path/to/file\f[R] but it can be
+other things - the \f[V]subcommand\f[R] help will tell you what.
 .PP
 Source and destination paths are specified by the name you gave the
 storage system in the config file then the sub path, e.g.
@@ -1366,7 +1382,7 @@ storage system in the config file then the sub path, e.g.
 .PP
 You can define as many storage paths as you like in the config file.
 .PP
-Please use the \f[C]--interactive\f[R]/\f[C]-i\f[R] flag while learning
+Please use the \f[V]--interactive\f[R]/\f[V]-i\f[R] flag while learning
 rclone to avoid accidental data loss.
 .SS Subcommands
 .PP
@@ -1523,8 +1539,8 @@ destpath/sourcepath/two.txt
 \f[R]
 .fi
 .PP
-If you are familiar with \f[C]rsync\f[R], rclone always works as if you
-had written a trailing \f[C]/\f[R] - meaning \[dq]copy the contents of
+If you are familiar with \f[V]rsync\f[R], rclone always works as if you
+had written a trailing \f[V]/\f[R] - meaning \[dq]copy the contents of
 this directory\[dq].
 This applies to all commands and whether you are talking about the
 source or destination.
@@ -1546,17 +1562,17 @@ rclone copy --max-age 24h --no-traverse /path/to/src remote:
 .PP
 Rclone will sync the modification times of files and directories if the
 backend supports it.
-If metadata syncing is required then use the \f[C]--metadata\f[R] flag.
+If metadata syncing is required then use the \f[V]--metadata\f[R] flag.
 .PP
 Note that the modification time and metadata for the root directory will
 \f[B]not\f[R] be synced.
 See https://github.com/rclone/rclone/issues/7652 for more info.
 .PP
-\f[B]Note\f[R]: Use the \f[C]-P\f[R]/\f[C]--progress\f[R] flag to view
+\f[B]Note\f[R]: Use the \f[V]-P\f[R]/\f[V]--progress\f[R] flag to view
 real-time transfer statistics.
 .PP
-\f[B]Note\f[R]: Use the \f[C]--dry-run\f[R] or the
-\f[C]--interactive\f[R]/\f[C]-i\f[R] flag to test without copying
+\f[B]Note\f[R]: Use the \f[V]--dry-run\f[R] or the
+\f[V]--interactive\f[R]/\f[V]-i\f[R] flag to test without copying
 anything.
 .IP
 .nf
@@ -1685,7 +1701,7 @@ If you don\[aq]t want to delete files from destination, use the
 copy (https://rclone.org/commands/rclone_copy/) command instead.
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\f[C]--dry-run\f[R] or the \f[C]--interactive\f[R]/\f[C]-i\f[R] flag.
+\f[V]--dry-run\f[R] or the \f[V]--interactive\f[R]/\f[V]-i\f[R] flag.
 .IP
 .nf
 \f[C]
@@ -1715,16 +1731,16 @@ directory and sync to a destination that is inside the source directory.
 .PP
 Rclone will sync the modification times of files and directories if the
 backend supports it.
-If metadata syncing is required then use the \f[C]--metadata\f[R] flag.
+If metadata syncing is required then use the \f[V]--metadata\f[R] flag.
 .PP
 Note that the modification time and metadata for the root directory will
 \f[B]not\f[R] be synced.
 See https://github.com/rclone/rclone/issues/7652 for more info.
 .PP
-\f[B]Note\f[R]: Use the \f[C]-P\f[R]/\f[C]--progress\f[R] flag to view
+\f[B]Note\f[R]: Use the \f[V]-P\f[R]/\f[V]--progress\f[R] flag to view
 real-time transfer statistics
 .PP
-\f[B]Note\f[R]: Use the \f[C]rclone dedupe\f[R] command to deal with
+\f[B]Note\f[R]: Use the \f[V]rclone dedupe\f[R] command to deal with
 \[dq]Duplicate object/directory found in source/destination -
 ignoring\[dq] errors.
 See this forum
@@ -1732,54 +1748,54 @@ post (https://forum.rclone.org/t/sync-not-clearing-duplicates/14372) for
 more info.
 .SH Logger Flags
 .PP
-The \f[C]--differ\f[R], \f[C]--missing-on-dst\f[R],
-\f[C]--missing-on-src\f[R], \f[C]--match\f[R] and \f[C]--error\f[R]
+The \f[V]--differ\f[R], \f[V]--missing-on-dst\f[R],
+\f[V]--missing-on-src\f[R], \f[V]--match\f[R] and \f[V]--error\f[R]
 flags write paths, one per line, to the file name (or stdout if it is
-\f[C]-\f[R]) supplied.
+\f[V]-\f[R]) supplied.
 What they write is described in the help below.
-For example \f[C]--differ\f[R] will write all paths which are present on
+For example \f[V]--differ\f[R] will write all paths which are present on
 both the source and destination but different.
 .PP
-The \f[C]--combined\f[R] flag will write a file (or stdout) which
+The \f[V]--combined\f[R] flag will write a file (or stdout) which
 contains all file paths with a symbol and then a space and then the path
 to tell you what happened to it.
 These are reminiscent of diff files.
 .IP \[bu] 2
-\f[C]= path\f[R] means path was found in source and destination and was
+\f[V]= path\f[R] means path was found in source and destination and was
 identical
 .IP \[bu] 2
-\[ga]- path\[ga] means path was missing on the source, so only in the
+\f[V]- path\f[R] means path was missing on the source, so only in the
 destination
 .IP \[bu] 2
-\[ga]+ path\[ga] means path was missing on the destination, so only in
+\f[V]+ path\f[R] means path was missing on the destination, so only in
 the source
 .IP \[bu] 2
-\[ga]* path\[ga] means path was present in source and destination but
+\f[V]* path\f[R] means path was present in source and destination but
 different.
 .IP \[bu] 2
-\f[C]! path\f[R] means there was an error reading or hashing the source
+\f[V]! path\f[R] means there was an error reading or hashing the source
 or dest.
 .PP
-The \f[C]--dest-after\f[R] flag writes a list file using the same format
+The \f[V]--dest-after\f[R] flag writes a list file using the same format
 flags as
-\f[C]lsf\f[R] (https://rclone.org/commands/rclone_lsf/#synopsis)
+\f[V]lsf\f[R] (https://rclone.org/commands/rclone_lsf/#synopsis)
 (including customizable options for hash, modtime,
 etc. (https://rclone.org/commands/rclone_lsf/#synopsis)) Conceptually it
-is similar to rsync\[aq]s \f[C]--itemize-changes\f[R], but not identical
+is similar to rsync\[aq]s \f[V]--itemize-changes\f[R], but not identical
 -- it should output an accurate list of what will be on the destination
 after the sync.
 .PP
 Note that these logger flags have a few limitations, and certain
 scenarios are not currently supported:
 .IP \[bu] 2
-\f[C]--max-duration\f[R] / \f[C]CutoffModeHard\f[R]
+\f[V]--max-duration\f[R] / \f[V]CutoffModeHard\f[R]
 .IP \[bu] 2
-\f[C]--compare-dest\f[R] / \f[C]--copy-dest\f[R]
+\f[V]--compare-dest\f[R] / \f[V]--copy-dest\f[R]
 .IP \[bu] 2
 server-side moves of an entire dir at once
 .IP \[bu] 2
 High-level retries, because there would be duplicates (use
-\f[C]--retries 1\f[R] to disable)
+\f[V]--retries 1\f[R] to disable)
 .IP \[bu] 2
 Possibly some unusual error scenarios
 .PP
@@ -1948,17 +1964,17 @@ To move single files, use the
 moveto (https://rclone.org/commands/rclone_moveto/) command instead.
 .PP
 If no filters are in use and if possible this will server-side move
-\f[C]source:path\f[R] into \f[C]dest:path\f[R].
-After this \f[C]source:path\f[R] will no longer exist.
+\f[V]source:path\f[R] into \f[V]dest:path\f[R].
+After this \f[V]source:path\f[R] will no longer exist.
 .PP
-Otherwise for each file in \f[C]source:path\f[R] selected by the filters
-(if any) this will move it into \f[C]dest:path\f[R].
+Otherwise for each file in \f[V]source:path\f[R] selected by the filters
+(if any) this will move it into \f[V]dest:path\f[R].
 If possible a server-side move will be used, otherwise it will copy it
-(server-side if possible) into \f[C]dest:path\f[R] then delete the
-original (if no errors on copy) in \f[C]source:path\f[R].
+(server-side if possible) into \f[V]dest:path\f[R] then delete the
+original (if no errors on copy) in \f[V]source:path\f[R].
 .PP
 If you want to delete empty source directories after move, use the
-\f[C]--delete-empty-src-dirs\f[R] flag.
+\f[V]--delete-empty-src-dirs\f[R] flag.
 .PP
 See the --no-traverse (https://rclone.org/docs/#no-traverse) option for
 controlling whether rclone lists the destination directory or not.
@@ -1967,16 +1983,16 @@ destination can speed transfers up greatly.
 .PP
 Rclone will sync the modification times of files and directories if the
 backend supports it.
-If metadata syncing is required then use the \f[C]--metadata\f[R] flag.
+If metadata syncing is required then use the \f[V]--metadata\f[R] flag.
 .PP
 Note that the modification time and metadata for the root directory will
 \f[B]not\f[R] be synced.
 See https://github.com/rclone/rclone/issues/7652 for more info.
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\f[C]--dry-run\f[R] or the \f[C]--interactive\f[R]/\f[C]-i\f[R] flag.
+\f[V]--dry-run\f[R] or the \f[V]--interactive\f[R]/\f[V]-i\f[R] flag.
 .PP
-\f[B]Note\f[R]: Use the \f[C]-P\f[R]/\f[C]--progress\f[R] flag to view
+\f[B]Note\f[R]: Use the \f[V]-P\f[R]/\f[V]--progress\f[R] flag to view
 real-time transfer statistics.
 .IP
 .nf
@@ -2101,12 +2117,12 @@ Remove the files in path.
 Unlike purge (https://rclone.org/commands/rclone_purge/) it obeys
 include/exclude filters so can be used to selectively delete files.
 .PP
-\f[C]rclone delete\f[R] only deletes files but leaves the directory
+\f[V]rclone delete\f[R] only deletes files but leaves the directory
 structure alone.
 If you want to delete a directory and all of its contents use the
 purge (https://rclone.org/commands/rclone_purge/) command.
 .PP
-If you supply the \f[C]--rmdirs\f[R] flag, it will remove all empty
+If you supply the \f[V]--rmdirs\f[R] flag, it will remove all empty
 directories along with it.
 You can also use the separate command
 rmdir (https://rclone.org/commands/rclone_rmdir/) or
@@ -2135,7 +2151,7 @@ That reads \[dq]delete everything with a minimum size of 100 MiB\[dq],
 hence delete all files bigger than 100 MiB.
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\f[C]--dry-run\f[R] or the \f[C]--interactive\f[R]/\f[C]-i\f[R] flag.
+\f[V]--dry-run\f[R] or the \f[V]--interactive\f[R]/\f[V]-i\f[R] flag.
 .IP
 .nf
 \f[C]
@@ -2224,7 +2240,7 @@ rmdir (https://rclone.org/commands/rclone_rmdir/) or
 rmdirs (https://rclone.org/commands/rclone_rmdirs/).
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\f[C]--dry-run\f[R] or the \f[C]--interactive\f[R]/\f[C]-i\f[R] flag.
+\f[V]--dry-run\f[R] or the \f[V]--interactive\f[R]/\f[V]-i\f[R] flag.
 .IP
 .nf
 \f[C]
@@ -2302,7 +2318,7 @@ Will not remove the path if it has any objects in it, not even empty
 subdirectories.
 Use command rmdirs (https://rclone.org/commands/rclone_rmdirs/) (or
 delete (https://rclone.org/commands/rclone_delete/) with option
-\f[C]--rmdirs\f[R]) to do that.
+\f[V]--rmdirs\f[R]) to do that.
 .PP
 To delete a path and any objects in it, use
 purge (https://rclone.org/commands/rclone_purge/) command.
@@ -2352,51 +2368,51 @@ For the crypt (https://rclone.org/crypt/) remote there is a dedicated
 command, cryptcheck (https://rclone.org/commands/rclone_cryptcheck/),
 that are able to check the checksums of the encrypted files.
 .PP
-If you supply the \f[C]--size-only\f[R] flag, it will only compare the
+If you supply the \f[V]--size-only\f[R] flag, it will only compare the
 sizes not the hashes as well.
 Use this for a quick check.
 .PP
-If you supply the \f[C]--download\f[R] flag, it will download the data
+If you supply the \f[V]--download\f[R] flag, it will download the data
 from both remotes and check them against each other on the fly.
 This can be useful for remotes that don\[aq]t support hashes or if you
 really want to check all the data.
 .PP
-If you supply the \f[C]--checkfile HASH\f[R] flag with a valid hash
-name, the \f[C]source:path\f[R] must point to a text file in the SUM
+If you supply the \f[V]--checkfile HASH\f[R] flag with a valid hash
+name, the \f[V]source:path\f[R] must point to a text file in the SUM
 format.
 .PP
-If you supply the \f[C]--one-way\f[R] flag, it will only check that
+If you supply the \f[V]--one-way\f[R] flag, it will only check that
 files in the source match the files in the destination, not the other
 way around.
 This means that extra files in the destination that are not in the
 source will not be detected.
 .PP
-The \f[C]--differ\f[R], \f[C]--missing-on-dst\f[R],
-\f[C]--missing-on-src\f[R], \f[C]--match\f[R] and \f[C]--error\f[R]
+The \f[V]--differ\f[R], \f[V]--missing-on-dst\f[R],
+\f[V]--missing-on-src\f[R], \f[V]--match\f[R] and \f[V]--error\f[R]
 flags write paths, one per line, to the file name (or stdout if it is
-\f[C]-\f[R]) supplied.
+\f[V]-\f[R]) supplied.
 What they write is described in the help below.
-For example \f[C]--differ\f[R] will write all paths which are present on
+For example \f[V]--differ\f[R] will write all paths which are present on
 both the source and destination but different.
 .PP
-The \f[C]--combined\f[R] flag will write a file (or stdout) which
+The \f[V]--combined\f[R] flag will write a file (or stdout) which
 contains all file paths with a symbol and then a space and then the path
 to tell you what happened to it.
 These are reminiscent of diff files.
 .IP \[bu] 2
-\f[C]= path\f[R] means path was found in source and destination and was
+\f[V]= path\f[R] means path was found in source and destination and was
 identical
 .IP \[bu] 2
-\[ga]- path\[ga] means path was missing on the source, so only in the
+\f[V]- path\f[R] means path was missing on the source, so only in the
 destination
 .IP \[bu] 2
-\[ga]+ path\[ga] means path was missing on the destination, so only in
+\f[V]+ path\f[R] means path was missing on the destination, so only in
 the source
 .IP \[bu] 2
-\[ga]* path\[ga] means path was present in source and destination but
+\f[V]* path\f[R] means path was present in source and destination but
 different.
 .IP \[bu] 2
-\f[C]! path\f[R] means there was an error reading or hashing the source
+\f[V]! path\f[R] means there was an error reading or hashing the source
 or dest.
 .PP
 The default number of parallel checks is 8.
@@ -2506,26 +2522,26 @@ Any of the filtering options can be applied to this command.
 .PP
 There are several related list commands
 .IP \[bu] 2
-\f[C]ls\f[R] to list size and path of objects only
+\f[V]ls\f[R] to list size and path of objects only
 .IP \[bu] 2
-\f[C]lsl\f[R] to list modification time, size and path of objects only
+\f[V]lsl\f[R] to list modification time, size and path of objects only
 .IP \[bu] 2
-\f[C]lsd\f[R] to list directories only
+\f[V]lsd\f[R] to list directories only
 .IP \[bu] 2
-\f[C]lsf\f[R] to list objects and directories in easy to parse format
+\f[V]lsf\f[R] to list objects and directories in easy to parse format
 .IP \[bu] 2
-\f[C]lsjson\f[R] to list objects and directories in JSON format
+\f[V]lsjson\f[R] to list objects and directories in JSON format
 .PP
-\f[C]ls\f[R],\f[C]lsl\f[R],\f[C]lsd\f[R] are designed to be
+\f[V]ls\f[R],\f[V]lsl\f[R],\f[V]lsd\f[R] are designed to be
 human-readable.
-\f[C]lsf\f[R] is designed to be human and machine-readable.
-\f[C]lsjson\f[R] is designed to be machine-readable.
+\f[V]lsf\f[R] is designed to be human and machine-readable.
+\f[V]lsjson\f[R] is designed to be machine-readable.
 .PP
-Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default - use
-\f[C]--max-depth 1\f[R] to stop the recursion.
+Note that \f[V]ls\f[R] and \f[V]lsl\f[R] recurse by default - use
+\f[V]--max-depth 1\f[R] to stop the recursion.
 .PP
-The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default - use \f[C]-R\f[R] to make them recurse.
+The other list commands \f[V]lsd\f[R],\f[V]lsf\f[R],\f[V]lsjson\f[R] do
+not recurse by default - use \f[V]-R\f[R] to make them recurse.
 .PP
 Listing a nonexistent directory will produce an error except for remotes
 which can\[aq]t have empty directories (e.g.
@@ -2598,7 +2614,7 @@ List all directories/containers/buckets in the path.
 .PP
 Lists the directories in the source path to standard output.
 Does not recurse by default.
-Use the \f[C]-R\f[R] flag to recurse.
+Use the \f[V]-R\f[R] flag to recurse.
 .PP
 This command lists the total size of the directory (if known, -1 if
 not), the modification time (if known, the current time if not), the
@@ -2625,32 +2641,32 @@ $ rclone lsd drive:test
 .fi
 .PP
 If you just want the directory names use
-\f[C]rclone lsf --dirs-only\f[R].
+\f[V]rclone lsf --dirs-only\f[R].
 .PP
 Any of the filtering options can be applied to this command.
 .PP
 There are several related list commands
 .IP \[bu] 2
-\f[C]ls\f[R] to list size and path of objects only
+\f[V]ls\f[R] to list size and path of objects only
 .IP \[bu] 2
-\f[C]lsl\f[R] to list modification time, size and path of objects only
+\f[V]lsl\f[R] to list modification time, size and path of objects only
 .IP \[bu] 2
-\f[C]lsd\f[R] to list directories only
+\f[V]lsd\f[R] to list directories only
 .IP \[bu] 2
-\f[C]lsf\f[R] to list objects and directories in easy to parse format
+\f[V]lsf\f[R] to list objects and directories in easy to parse format
 .IP \[bu] 2
-\f[C]lsjson\f[R] to list objects and directories in JSON format
+\f[V]lsjson\f[R] to list objects and directories in JSON format
 .PP
-\f[C]ls\f[R],\f[C]lsl\f[R],\f[C]lsd\f[R] are designed to be
+\f[V]ls\f[R],\f[V]lsl\f[R],\f[V]lsd\f[R] are designed to be
 human-readable.
-\f[C]lsf\f[R] is designed to be human and machine-readable.
-\f[C]lsjson\f[R] is designed to be machine-readable.
+\f[V]lsf\f[R] is designed to be human and machine-readable.
+\f[V]lsjson\f[R] is designed to be machine-readable.
 .PP
-Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default - use
-\f[C]--max-depth 1\f[R] to stop the recursion.
+Note that \f[V]ls\f[R] and \f[V]lsl\f[R] recurse by default - use
+\f[V]--max-depth 1\f[R] to stop the recursion.
 .PP
-The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default - use \f[C]-R\f[R] to make them recurse.
+The other list commands \f[V]lsd\f[R],\f[V]lsf\f[R],\f[V]lsjson\f[R] do
+not recurse by default - use \f[V]-R\f[R] to make them recurse.
 .PP
 Listing a nonexistent directory will produce an error except for remotes
 which can\[aq]t have empty directories (e.g.
@@ -2742,26 +2758,26 @@ Any of the filtering options can be applied to this command.
 .PP
 There are several related list commands
 .IP \[bu] 2
-\f[C]ls\f[R] to list size and path of objects only
+\f[V]ls\f[R] to list size and path of objects only
 .IP \[bu] 2
-\f[C]lsl\f[R] to list modification time, size and path of objects only
+\f[V]lsl\f[R] to list modification time, size and path of objects only
 .IP \[bu] 2
-\f[C]lsd\f[R] to list directories only
+\f[V]lsd\f[R] to list directories only
 .IP \[bu] 2
-\f[C]lsf\f[R] to list objects and directories in easy to parse format
+\f[V]lsf\f[R] to list objects and directories in easy to parse format
 .IP \[bu] 2
-\f[C]lsjson\f[R] to list objects and directories in JSON format
+\f[V]lsjson\f[R] to list objects and directories in JSON format
 .PP
-\f[C]ls\f[R],\f[C]lsl\f[R],\f[C]lsd\f[R] are designed to be
+\f[V]ls\f[R],\f[V]lsl\f[R],\f[V]lsd\f[R] are designed to be
 human-readable.
-\f[C]lsf\f[R] is designed to be human and machine-readable.
-\f[C]lsjson\f[R] is designed to be machine-readable.
+\f[V]lsf\f[R] is designed to be human and machine-readable.
+\f[V]lsjson\f[R] is designed to be machine-readable.
 .PP
-Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default - use
-\f[C]--max-depth 1\f[R] to stop the recursion.
+Note that \f[V]ls\f[R] and \f[V]lsl\f[R] recurse by default - use
+\f[V]--max-depth 1\f[R] to stop the recursion.
 .PP
-The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default - use \f[C]-R\f[R] to make them recurse.
+The other list commands \f[V]lsd\f[R],\f[V]lsf\f[R],\f[V]lsjson\f[R] do
+not recurse by default - use \f[V]-R\f[R] to make them recurse.
 .PP
 Listing a nonexistent directory will produce an error except for remotes
 which can\[aq]t have empty directories (e.g.
@@ -2842,8 +2858,8 @@ hashed locally enabling MD5 for any remote.
 .PP
 For other algorithms, see the
 hashsum (https://rclone.org/commands/rclone_hashsum/) command.
-Running \f[C]rclone md5sum remote:path\f[R] is equivalent to running
-\f[C]rclone hashsum MD5 remote:path\f[R].
+Running \f[V]rclone md5sum remote:path\f[R] is equivalent to running
+\f[V]rclone hashsum MD5 remote:path\f[R].
 .PP
 This command can also hash data received on standard input (stdin), by
 not passing a remote:path, or by passing a hyphen as remote:path when
@@ -2929,8 +2945,8 @@ hashed locally enabling SHA-1 for any remote.
 .PP
 For other algorithms, see the
 hashsum (https://rclone.org/commands/rclone_hashsum/) command.
-Running \f[C]rclone sha1sum remote:path\f[R] is equivalent to running
-\f[C]rclone hashsum SHA1 remote:path\f[R].
+Running \f[V]rclone sha1sum remote:path\f[R] is equivalent to running
+\f[V]rclone hashsum SHA1 remote:path\f[R].
 .PP
 This command can also hash data received on standard input (stdin), by
 not passing a remote:path, or by passing a hyphen as remote:path when
@@ -3014,10 +3030,10 @@ Prints the result to standard output.
 .PP
 By default the output is in human-readable format, but shows values in
 both human-readable format as well as the raw numbers (global option
-\f[C]--human-readable\f[R] is not considered).
-Use option \f[C]--json\f[R] to format output as JSON instead.
+\f[V]--human-readable\f[R] is not considered).
+Use option \f[V]--json\f[R] to format output as JSON instead.
 .PP
-Recurses by default, use \f[C]--max-depth 1\f[R] to stop the recursion.
+Recurses by default, use \f[V]--max-depth 1\f[R] to stop the recursion.
 .PP
 Some backends do not always provide file sizes, see for example Google
 Photos (https://rclone.org/googlephotos/#size) and Google
@@ -3206,7 +3222,7 @@ commands, flags and backends.
 Interactively find duplicate filenames and delete/rename them.
 .SS Synopsis
 .PP
-By default \f[C]dedupe\f[R] interactively finds files with duplicate
+By default \f[V]dedupe\f[R] interactively finds files with duplicate
 names and offers to delete all but one or rename them to be different.
 This is known as deduping by name.
 .PP
@@ -3215,7 +3231,7 @@ Google Drive, Opendrive) that can have duplicate file names.
 It can be run on wrapping backends (e.g.
 crypt) if they wrap a backend which supports duplicate file names.
 .PP
-However if \f[C]--by-hash\f[R] is passed in then dedupe will find files
+However if \f[V]--by-hash\f[R] is passed in then dedupe will find files
 with duplicate hashes instead which will work on any backend which
 supports at least one hash.
 This can be used to find files with duplicate content.
@@ -3229,15 +3245,15 @@ have been merged.
 Next, if deduping by name, for every group of duplicate file names /
 hashes, it will delete all but one identical file it finds without
 confirmation.
-This means that for most duplicated files the \f[C]dedupe\f[R] command
+This means that for most duplicated files the \f[V]dedupe\f[R] command
 will not be interactive.
 .PP
-\f[C]dedupe\f[R] considers files to be identical if they have the same
+\f[V]dedupe\f[R] considers files to be identical if they have the same
 file path and the same hash.
 If the backend does not support hashes (e.g.
 crypt wrapping Google Drive) then they will never be found to be
 identical.
-If you use the \f[C]--size-only\f[R] flag then files will be considered
+If you use the \f[V]--size-only\f[R] flag then files will be considered
 identical if they have the same size (any hash will be ignored).
 This can be useful on crypt backends which do not support hashes.
 .PP
@@ -3246,7 +3262,7 @@ Exactly which action is taken depends on the dedupe mode.
 By default, rclone will interactively query the user for each one.
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\f[C]--dry-run\f[R] or the \f[C]--interactive\f[R]/\f[C]-i\f[R] flag.
+\f[V]--dry-run\f[R] or the \f[V]--interactive\f[R]/\f[V]-i\f[R] flag.
 .PP
 Here is an example run.
 .PP
@@ -3265,7 +3281,7 @@ $ rclone lsl drive:dupes
 \f[R]
 .fi
 .PP
-Now the \f[C]dedupe\f[R] session
+Now the \f[V]dedupe\f[R] session
 .IP
 .nf
 \f[C]
@@ -3309,33 +3325,33 @@ $ rclone lsl drive:dupes
 \f[R]
 .fi
 .PP
-Dedupe can be run non interactively using the \f[C]--dedupe-mode\f[R]
+Dedupe can be run non interactively using the \f[V]--dedupe-mode\f[R]
 flag or by using an extra parameter with the same value
 .IP \[bu] 2
-\f[C]--dedupe-mode interactive\f[R] - interactive as above.
+\f[V]--dedupe-mode interactive\f[R] - interactive as above.
 .IP \[bu] 2
-\f[C]--dedupe-mode skip\f[R] - removes identical files then skips
+\f[V]--dedupe-mode skip\f[R] - removes identical files then skips
 anything left.
 .IP \[bu] 2
-\f[C]--dedupe-mode first\f[R] - removes identical files then keeps the
+\f[V]--dedupe-mode first\f[R] - removes identical files then keeps the
 first one.
 .IP \[bu] 2
-\f[C]--dedupe-mode newest\f[R] - removes identical files then keeps the
+\f[V]--dedupe-mode newest\f[R] - removes identical files then keeps the
 newest one.
 .IP \[bu] 2
-\f[C]--dedupe-mode oldest\f[R] - removes identical files then keeps the
+\f[V]--dedupe-mode oldest\f[R] - removes identical files then keeps the
 oldest one.
 .IP \[bu] 2
-\f[C]--dedupe-mode largest\f[R] - removes identical files then keeps the
+\f[V]--dedupe-mode largest\f[R] - removes identical files then keeps the
 largest one.
 .IP \[bu] 2
-\f[C]--dedupe-mode smallest\f[R] - removes identical files then keeps
+\f[V]--dedupe-mode smallest\f[R] - removes identical files then keeps
 the smallest one.
 .IP \[bu] 2
-\f[C]--dedupe-mode rename\f[R] - removes identical files then renames
+\f[V]--dedupe-mode rename\f[R] - removes identical files then renames
 the rest to be different.
 .IP \[bu] 2
-\f[C]--dedupe-mode list\f[R] - lists duplicate dirs and files only and
+\f[V]--dedupe-mode list\f[R] - lists duplicate dirs and files only and
 changes nothing.
 .PP
 For example, to rename all the identically named photos in your Google
@@ -3397,7 +3413,7 @@ Prints quota information about a remote to standard output.
 The output is typically used, free, quota and trash contents.
 .PP
 E.g.
-Typical output from \f[C]rclone about remote:\f[R] is:
+Typical output from \f[V]rclone about remote:\f[R] is:
 .IP
 .nf
 \f[C]
@@ -3426,7 +3442,7 @@ Objects: Total number of objects in the storage.
 .PP
 All sizes are in number of bytes.
 .PP
-Applying a \f[C]--full\f[R] flag to the command prints the bytes in
+Applying a \f[V]--full\f[R] flag to the command prints the bytes in
 full, e.g.
 .IP
 .nf
@@ -3439,7 +3455,7 @@ Other:   8849156022
 \f[R]
 .fi
 .PP
-A \f[C]--json\f[R] flag generates conveniently machine-readable output,
+A \f[V]--json\f[R] flag generates conveniently machine-readable output,
 e.g.
 .IP
 .nf
@@ -3458,7 +3474,7 @@ Not all backends print all fields.
 Information is not included if it is not provided by a backend.
 Where the value is unlimited it is omitted.
 .PP
-Some backends does not support the \f[C]rclone about\f[R] command at
+Some backends does not support the \f[V]rclone about\f[R] command at
 all, see complete list in
 documentation (https://rclone.org/overview/#optional-features).
 .IP
@@ -3614,8 +3630,8 @@ solution in rclone.
 It retains the Path1 and Path2 filesystem listings from the prior run.
 On each successive run it will: - list files on Path1 and Path2, and
 check for changes on each side.
-Changes include \f[C]New\f[R], \f[C]Newer\f[R], \f[C]Older\f[R], and
-\f[C]Deleted\f[R] files.
+Changes include \f[V]New\f[R], \f[V]Newer\f[R], \f[V]Older\f[R], and
+\f[V]Deleted\f[R] files.
 - Propagate changes on Path1 to Path2, and vice-versa.
 .PP
 Bisync is \f[B]in beta\f[R] and is considered an \f[B]advanced
@@ -3784,13 +3800,13 @@ rclone --include \[dq]*.txt\[dq] cat remote:path/to/dir
 \f[R]
 .fi
 .PP
-Use the \f[C]--head\f[R] flag to print characters only at the start,
-\f[C]--tail\f[R] for the end and \f[C]--offset\f[R] and
-\f[C]--count\f[R] to print a section in the middle.
+Use the \f[V]--head\f[R] flag to print characters only at the start,
+\f[V]--tail\f[R] for the end and \f[V]--offset\f[R] and
+\f[V]--count\f[R] to print a section in the middle.
 Note that if offset is negative it will count from the end, so
-\f[C]--offset -1 --count 1\f[R] is equivalent to \f[C]--tail 1\f[R].
+\f[V]--offset -1 --count 1\f[R] is equivalent to \f[V]--tail 1\f[R].
 .PP
-Use the \f[C]--separator\f[R] flag to print a separator value between
+Use the \f[V]--separator\f[R] flag to print a separator value between
 files.
 Be sure to shell-escape special characters.
 For example, to print a newline between files, use:
@@ -3894,45 +3910,45 @@ It doesn\[aq]t alter the file system.
 The sumfile is treated as the source and the dst:path is treated as the
 destination for the purposes of the output.
 .PP
-If you supply the \f[C]--download\f[R] flag, it will download the data
+If you supply the \f[V]--download\f[R] flag, it will download the data
 from the remote and calculate the content hash on the fly.
 This can be useful for remotes that don\[aq]t support hashes or if you
 really want to check all the data.
 .PP
 Note that hash values in the SUM file are treated as case insensitive.
 .PP
-If you supply the \f[C]--one-way\f[R] flag, it will only check that
+If you supply the \f[V]--one-way\f[R] flag, it will only check that
 files in the source match the files in the destination, not the other
 way around.
 This means that extra files in the destination that are not in the
 source will not be detected.
 .PP
-The \f[C]--differ\f[R], \f[C]--missing-on-dst\f[R],
-\f[C]--missing-on-src\f[R], \f[C]--match\f[R] and \f[C]--error\f[R]
+The \f[V]--differ\f[R], \f[V]--missing-on-dst\f[R],
+\f[V]--missing-on-src\f[R], \f[V]--match\f[R] and \f[V]--error\f[R]
 flags write paths, one per line, to the file name (or stdout if it is
-\f[C]-\f[R]) supplied.
+\f[V]-\f[R]) supplied.
 What they write is described in the help below.
-For example \f[C]--differ\f[R] will write all paths which are present on
+For example \f[V]--differ\f[R] will write all paths which are present on
 both the source and destination but different.
 .PP
-The \f[C]--combined\f[R] flag will write a file (or stdout) which
+The \f[V]--combined\f[R] flag will write a file (or stdout) which
 contains all file paths with a symbol and then a space and then the path
 to tell you what happened to it.
 These are reminiscent of diff files.
 .IP \[bu] 2
-\f[C]= path\f[R] means path was found in source and destination and was
+\f[V]= path\f[R] means path was found in source and destination and was
 identical
 .IP \[bu] 2
-\[ga]- path\[ga] means path was missing on the source, so only in the
+\f[V]- path\f[R] means path was missing on the source, so only in the
 destination
 .IP \[bu] 2
-\[ga]+ path\[ga] means path was missing on the destination, so only in
+\f[V]+ path\f[R] means path was missing on the destination, so only in
 the source
 .IP \[bu] 2
-\[ga]* path\[ga] means path was present in source and destination but
+\f[V]* path\f[R] means path was present in source and destination but
 different.
 .IP \[bu] 2
-\f[C]! path\f[R] means there was an error reading or hashing the source
+\f[V]! path\f[R] means there was an error reading or hashing the source
 or dest.
 .PP
 The default number of parallel checks is 8.
@@ -4013,7 +4029,7 @@ Output completion script for a given shell.
 .SS Synopsis
 .PP
 Generates a shell completion script for rclone.
-Run with \f[C]--help\f[R] to list the supported shells.
+Run with \f[V]--help\f[R] to list the supported shells.
 .SS Options
 .IP
 .nf
@@ -4252,9 +4268,9 @@ Output completion script for a given shell.
 Create a new remote with name, type and options.
 .SS Synopsis
 .PP
-Create a new remote of \f[C]name\f[R] with \f[C]type\f[R] and options.
-The options should be passed in pairs of \f[C]key\f[R] \f[C]value\f[R]
-or as \f[C]key=value\f[R].
+Create a new remote of \f[V]name\f[R] with \f[V]type\f[R] and options.
+The options should be passed in pairs of \f[V]key\f[R] \f[V]value\f[R]
+or as \f[V]key=value\f[R].
 .PP
 For example, to make a swift remote of name myremote using auto config
 you would do:
@@ -4276,7 +4292,7 @@ rclone config create mydrive drive config_is_local=false
 .fi
 .PP
 Note that if the config process would normally ask a question the
-default is taken (unless \f[C]--non-interactive\f[R] is used).
+default is taken (unless \f[V]--non-interactive\f[R] is used).
 Each time that happens rclone will print or DEBUG a message saying how
 to affect the value taken.
 .PP
@@ -4289,12 +4305,12 @@ consists only of base64 characters then rclone can get confused about
 whether the password is already obscured or not and put unobscured
 passwords into the config file.
 If you want to be 100% certain that the passwords get obscured then use
-the \f[C]--obscure\f[R] flag, or if you are 100% certain you are already
-passing obscured passwords then use \f[C]--no-obscure\f[R].
+the \f[V]--obscure\f[R] flag, or if you are 100% certain you are already
+passing obscured passwords then use \f[V]--no-obscure\f[R].
 You can also set obscured passwords using the
-\f[C]rclone config password\f[R] command.
+\f[V]rclone config password\f[R] command.
 .PP
-The flag \f[C]--non-interactive\f[R] is for use by applications that
+The flag \f[V]--non-interactive\f[R] is for use by applications that
 wish to configure rclone themselves, rather than using rclone\[aq]s text
 based configuration questions.
 If this flag is set, and rclone needs to ask the user a question, a JSON
@@ -4330,39 +4346,39 @@ This will look something like (some irrelevant detail removed):
 \f[R]
 .fi
 .PP
-The format of \f[C]Option\f[R] is the same as returned by
-\f[C]rclone config providers\f[R].
+The format of \f[V]Option\f[R] is the same as returned by
+\f[V]rclone config providers\f[R].
 The question should be asked to the user and returned to rclone as the
-\f[C]--result\f[R] option along with the \f[C]--state\f[R] parameter.
+\f[V]--result\f[R] option along with the \f[V]--state\f[R] parameter.
 .PP
-The keys of \f[C]Option\f[R] are used as follows:
+The keys of \f[V]Option\f[R] are used as follows:
 .IP \[bu] 2
-\f[C]Name\f[R] - name of variable - show to user
+\f[V]Name\f[R] - name of variable - show to user
 .IP \[bu] 2
-\f[C]Help\f[R] - help text.
+\f[V]Help\f[R] - help text.
 Hard wrapped at 80 chars.
 Any URLs should be clicky.
 .IP \[bu] 2
-\f[C]Default\f[R] - default value - return this if the user just wants
+\f[V]Default\f[R] - default value - return this if the user just wants
 the default.
 .IP \[bu] 2
-\f[C]Examples\f[R] - the user should be able to choose one of these
+\f[V]Examples\f[R] - the user should be able to choose one of these
 .IP \[bu] 2
-\f[C]Required\f[R] - the value should be non-empty
+\f[V]Required\f[R] - the value should be non-empty
 .IP \[bu] 2
-\f[C]IsPassword\f[R] - the value is a password and should be edited as
+\f[V]IsPassword\f[R] - the value is a password and should be edited as
 such
 .IP \[bu] 2
-\f[C]Type\f[R] - type of value, eg \f[C]bool\f[R], \f[C]string\f[R],
-\f[C]int\f[R] and others
+\f[V]Type\f[R] - type of value, eg \f[V]bool\f[R], \f[V]string\f[R],
+\f[V]int\f[R] and others
 .IP \[bu] 2
-\f[C]Exclusive\f[R] - if set no free-form entry allowed only the
-\f[C]Examples\f[R]
+\f[V]Exclusive\f[R] - if set no free-form entry allowed only the
+\f[V]Examples\f[R]
 .IP \[bu] 2
-Irrelevant keys \f[C]Provider\f[R], \f[C]ShortOpt\f[R], \f[C]Hide\f[R],
-\f[C]NoPrefix\f[R], \f[C]Advanced\f[R]
+Irrelevant keys \f[V]Provider\f[R], \f[V]ShortOpt\f[R], \f[V]Hide\f[R],
+\f[V]NoPrefix\f[R], \f[V]Advanced\f[R]
 .PP
-If \f[C]Error\f[R] is set then it should be shown to the user at the
+If \f[V]Error\f[R] is set then it should be shown to the user at the
 same time as the question.
 .IP
 .nf
@@ -4371,19 +4387,19 @@ rclone config update name --continue --state \[dq]*oauth-islocal,teamdrive,,\[dq
 \f[R]
 .fi
 .PP
-Note that when using \f[C]--continue\f[R] all passwords should be passed
+Note that when using \f[V]--continue\f[R] all passwords should be passed
 in the clear (not obscured).
 Any default config values should be passed in with each invocation of
-\f[C]--continue\f[R].
+\f[V]--continue\f[R].
 .PP
 At the end of the non interactive process, rclone will return a result
-with \f[C]State\f[R] as empty string.
+with \f[V]State\f[R] as empty string.
 .PP
-If \f[C]--all\f[R] is passed then rclone will ask all the config
+If \f[V]--all\f[R] is passed then rclone will ask all the config
 questions, not just the post config questions.
 Any parameters are used as defaults for questions as usual.
 .PP
-Note that \f[C]bin/config.py\f[R] in the rclone source implements this
+Note that \f[V]bin/config.py\f[R] in the rclone source implements this
 protocol as a readable demonstration.
 .IP
 .nf
@@ -4559,7 +4575,7 @@ This checks the config file is encrypted and that you can decrypt it.
 It will attempt to decrypt the config using the password you supply.
 .PP
 If decryption fails it will return a non-zero exit code if using
-\f[C]--password-command\f[R], otherwise it will prompt again for the
+\f[V]--password-command\f[R], otherwise it will prompt again for the
 password.
 .PP
 If the config file is not encrypted it will return a non zero exit code.
@@ -4593,7 +4609,7 @@ Remove the config file encryption password
 .PP
 This removes the config file encryption, returning it to un-encrypted.
 .PP
-If \f[C]--password-command\f[R] is in use, this will be called to supply
+If \f[V]--password-command\f[R] is in use, this will be called to supply
 the old config password.
 .PP
 If the config was not encrypted then no error will be returned and this
@@ -4630,17 +4646,17 @@ If there was no config password set then it sets a new one, otherwise it
 changes the existing config password.
 .PP
 Note that if you are changing an encryption password using
-\f[C]--password-command\f[R] then this will be called once to decrypt
+\f[V]--password-command\f[R] then this will be called once to decrypt
 the config using the old password and then again to read the new
 password to re-encrypt the config.
 .PP
-When \f[C]--password-command\f[R] is called to change the password then
-the environment variable \f[C]RCLONE_PASSWORD_CHANGE=1\f[R] will be set.
+When \f[V]--password-command\f[R] is called to change the password then
+the environment variable \f[V]RCLONE_PASSWORD_CHANGE=1\f[R] will be set.
 So if changing passwords programatically you can use the environment
 variable to distinguish which password you must supply.
 .PP
 Alternatively you can remove the password first (with
-\f[C]rclone config encryption remove\f[R]), then set it again with this
+\f[V]rclone config encryption remove\f[R]), then set it again with this
 command which may be easier if you don\[aq]t mind the unecrypted config
 file being on the disk briefly.
 .IP
@@ -4693,9 +4709,9 @@ Update password in an existing remote.
 .SS Synopsis
 .PP
 Update an existing remote\[aq]s password.
-The password should be passed in pairs of \f[C]key\f[R]
-\f[C]password\f[R] or as \f[C]key=password\f[R].
-The \f[C]password\f[R] should be passed in in clear (unobscured).
+The password should be passed in pairs of \f[V]key\f[R]
+\f[V]password\f[R] or as \f[V]key=password\f[R].
+The \f[V]password\f[R] should be passed in in clear (unobscured).
 .PP
 For example, to set password of a remote of name myremote you would do:
 .IP
@@ -4892,8 +4908,8 @@ Update options in an existing remote.
 .SS Synopsis
 .PP
 Update an existing remote\[aq]s options.
-The options should be passed in pairs of \f[C]key\f[R] \f[C]value\f[R]
-or as \f[C]key=value\f[R].
+The options should be passed in pairs of \f[V]key\f[R] \f[V]value\f[R]
+or as \f[V]key=value\f[R].
 .PP
 For example, to update the env_auth field of a remote of name myremote
 you would do:
@@ -4915,7 +4931,7 @@ rclone config update myremote env_auth=true config_refresh_token=false
 .fi
 .PP
 Note that if the config process would normally ask a question the
-default is taken (unless \f[C]--non-interactive\f[R] is used).
+default is taken (unless \f[V]--non-interactive\f[R] is used).
 Each time that happens rclone will print or DEBUG a message saying how
 to affect the value taken.
 .PP
@@ -4928,12 +4944,12 @@ consists only of base64 characters then rclone can get confused about
 whether the password is already obscured or not and put unobscured
 passwords into the config file.
 If you want to be 100% certain that the passwords get obscured then use
-the \f[C]--obscure\f[R] flag, or if you are 100% certain you are already
-passing obscured passwords then use \f[C]--no-obscure\f[R].
+the \f[V]--obscure\f[R] flag, or if you are 100% certain you are already
+passing obscured passwords then use \f[V]--no-obscure\f[R].
 You can also set obscured passwords using the
-\f[C]rclone config password\f[R] command.
+\f[V]rclone config password\f[R] command.
 .PP
-The flag \f[C]--non-interactive\f[R] is for use by applications that
+The flag \f[V]--non-interactive\f[R] is for use by applications that
 wish to configure rclone themselves, rather than using rclone\[aq]s text
 based configuration questions.
 If this flag is set, and rclone needs to ask the user a question, a JSON
@@ -4969,39 +4985,39 @@ This will look something like (some irrelevant detail removed):
 \f[R]
 .fi
 .PP
-The format of \f[C]Option\f[R] is the same as returned by
-\f[C]rclone config providers\f[R].
+The format of \f[V]Option\f[R] is the same as returned by
+\f[V]rclone config providers\f[R].
 The question should be asked to the user and returned to rclone as the
-\f[C]--result\f[R] option along with the \f[C]--state\f[R] parameter.
+\f[V]--result\f[R] option along with the \f[V]--state\f[R] parameter.
 .PP
-The keys of \f[C]Option\f[R] are used as follows:
+The keys of \f[V]Option\f[R] are used as follows:
 .IP \[bu] 2
-\f[C]Name\f[R] - name of variable - show to user
+\f[V]Name\f[R] - name of variable - show to user
 .IP \[bu] 2
-\f[C]Help\f[R] - help text.
+\f[V]Help\f[R] - help text.
 Hard wrapped at 80 chars.
 Any URLs should be clicky.
 .IP \[bu] 2
-\f[C]Default\f[R] - default value - return this if the user just wants
+\f[V]Default\f[R] - default value - return this if the user just wants
 the default.
 .IP \[bu] 2
-\f[C]Examples\f[R] - the user should be able to choose one of these
+\f[V]Examples\f[R] - the user should be able to choose one of these
 .IP \[bu] 2
-\f[C]Required\f[R] - the value should be non-empty
+\f[V]Required\f[R] - the value should be non-empty
 .IP \[bu] 2
-\f[C]IsPassword\f[R] - the value is a password and should be edited as
+\f[V]IsPassword\f[R] - the value is a password and should be edited as
 such
 .IP \[bu] 2
-\f[C]Type\f[R] - type of value, eg \f[C]bool\f[R], \f[C]string\f[R],
-\f[C]int\f[R] and others
+\f[V]Type\f[R] - type of value, eg \f[V]bool\f[R], \f[V]string\f[R],
+\f[V]int\f[R] and others
 .IP \[bu] 2
-\f[C]Exclusive\f[R] - if set no free-form entry allowed only the
-\f[C]Examples\f[R]
+\f[V]Exclusive\f[R] - if set no free-form entry allowed only the
+\f[V]Examples\f[R]
 .IP \[bu] 2
-Irrelevant keys \f[C]Provider\f[R], \f[C]ShortOpt\f[R], \f[C]Hide\f[R],
-\f[C]NoPrefix\f[R], \f[C]Advanced\f[R]
+Irrelevant keys \f[V]Provider\f[R], \f[V]ShortOpt\f[R], \f[V]Hide\f[R],
+\f[V]NoPrefix\f[R], \f[V]Advanced\f[R]
 .PP
-If \f[C]Error\f[R] is set then it should be shown to the user at the
+If \f[V]Error\f[R] is set then it should be shown to the user at the
 same time as the question.
 .IP
 .nf
@@ -5010,19 +5026,19 @@ rclone config update name --continue --state \[dq]*oauth-islocal,teamdrive,,\[dq
 \f[R]
 .fi
 .PP
-Note that when using \f[C]--continue\f[R] all passwords should be passed
+Note that when using \f[V]--continue\f[R] all passwords should be passed
 in the clear (not obscured).
 Any default config values should be passed in with each invocation of
-\f[C]--continue\f[R].
+\f[V]--continue\f[R].
 .PP
 At the end of the non interactive process, rclone will return a result
-with \f[C]State\f[R] as empty string.
+with \f[V]State\f[R] as empty string.
 .PP
-If \f[C]--all\f[R] is passed then rclone will ask all the config
+If \f[V]--all\f[R] is passed then rclone will ask all the config
 questions, not just the post config questions.
 Any parameters are used as defaults for questions as usual.
 .PP
-Note that \f[C]bin/config.py\f[R] in the rclone source implements this
+Note that \f[V]bin/config.py\f[R] in the rclone source implements this
 protocol as a readable demonstration.
 .IP
 .nf
@@ -5119,7 +5135,7 @@ This doesn\[aq]t transfer files that are identical on src and dst,
 testing by size and modification time or MD5SUM.
 It doesn\[aq]t delete files from the destination.
 .PP
-\f[B]Note\f[R]: Use the \f[C]-P\f[R]/\f[C]--progress\f[R] flag to view
+\f[B]Note\f[R]: Use the \f[V]-P\f[R]/\f[V]--progress\f[R] flag to view
 real-time transfer statistics
 .IP
 .nf
@@ -5241,38 +5257,38 @@ Copy the contents of the URL supplied content to dest:path.
 Download a URL\[aq]s content and copy it to the destination without
 saving it in temporary storage.
 .PP
-Setting \f[C]--auto-filename\f[R] will attempt to automatically
+Setting \f[V]--auto-filename\f[R] will attempt to automatically
 determine the filename from the URL (after any redirections) and used in
 the destination path.
 .PP
-With \f[C]--auto-filename-header\f[R] in addition, if a specific
+With \f[V]--auto-filename-header\f[R] in addition, if a specific
 filename is set in HTTP headers, it will be used instead of the name
 from the URL.
-With \f[C]--print-filename\f[R] in addition, the resulting file name
+With \f[V]--print-filename\f[R] in addition, the resulting file name
 will be printed.
 .PP
-Setting \f[C]--no-clobber\f[R] will prevent overwriting file on the
+Setting \f[V]--no-clobber\f[R] will prevent overwriting file on the
 destination if there is one with the same name.
 .PP
-Setting \f[C]--stdout\f[R] or making the output file name \f[C]-\f[R]
+Setting \f[V]--stdout\f[R] or making the output file name \f[V]-\f[R]
 will cause the output to be written to standard output.
 .SS Troublshooting
 .PP
-If you can\[aq]t get \f[C]rclone copyurl\f[R] to work then here are some
+If you can\[aq]t get \f[V]rclone copyurl\f[R] to work then here are some
 things you can try:
 .IP \[bu] 2
-\f[C]--disable-http2\f[R] rclone will use HTTP2 if available - try
+\f[V]--disable-http2\f[R] rclone will use HTTP2 if available - try
 disabling it
 .IP \[bu] 2
-\f[C]--bind 0.0.0.0\f[R] rclone will use IPv6 if available - try
+\f[V]--bind 0.0.0.0\f[R] rclone will use IPv6 if available - try
 disabling it
 .IP \[bu] 2
-\f[C]--bind ::0\f[R] to disable IPv4
+\f[V]--bind ::0\f[R] to disable IPv4
 .IP \[bu] 2
-\f[C]--user agent curl\f[R] - some sites have whitelists for curl\[aq]s
+\f[V]--user agent curl\f[R] - some sites have whitelists for curl\[aq]s
 user-agent - try that
 .IP \[bu] 2
-Make sure the site works with \f[C]curl\f[R] directly
+Make sure the site works with \f[V]curl\f[R] directly
 .IP
 .nf
 \f[C]
@@ -5347,38 +5363,38 @@ rclone cryptcheck remote:path encryptedremote:path
 .PP
 After it has run it will log the status of the encryptedremote:.
 .PP
-If you supply the \f[C]--one-way\f[R] flag, it will only check that
+If you supply the \f[V]--one-way\f[R] flag, it will only check that
 files in the source match the files in the destination, not the other
 way around.
 This means that extra files in the destination that are not in the
 source will not be detected.
 .PP
-The \f[C]--differ\f[R], \f[C]--missing-on-dst\f[R],
-\f[C]--missing-on-src\f[R], \f[C]--match\f[R] and \f[C]--error\f[R]
+The \f[V]--differ\f[R], \f[V]--missing-on-dst\f[R],
+\f[V]--missing-on-src\f[R], \f[V]--match\f[R] and \f[V]--error\f[R]
 flags write paths, one per line, to the file name (or stdout if it is
-\f[C]-\f[R]) supplied.
+\f[V]-\f[R]) supplied.
 What they write is described in the help below.
-For example \f[C]--differ\f[R] will write all paths which are present on
+For example \f[V]--differ\f[R] will write all paths which are present on
 both the source and destination but different.
 .PP
-The \f[C]--combined\f[R] flag will write a file (or stdout) which
+The \f[V]--combined\f[R] flag will write a file (or stdout) which
 contains all file paths with a symbol and then a space and then the path
 to tell you what happened to it.
 These are reminiscent of diff files.
 .IP \[bu] 2
-\f[C]= path\f[R] means path was found in source and destination and was
+\f[V]= path\f[R] means path was found in source and destination and was
 identical
 .IP \[bu] 2
-\[ga]- path\[ga] means path was missing on the source, so only in the
+\f[V]- path\f[R] means path was missing on the source, so only in the
 destination
 .IP \[bu] 2
-\[ga]+ path\[ga] means path was missing on the destination, so only in
+\f[V]+ path\f[R] means path was missing on the destination, so only in
 the source
 .IP \[bu] 2
-\[ga]* path\[ga] means path was present in source and destination but
+\f[V]* path\f[R] means path was present in source and destination but
 different.
 .IP \[bu] 2
-\f[C]! path\f[R] means there was an error reading or hashing the source
+\f[V]! path\f[R] means there was an error reading or hashing the source
 or dest.
 .PP
 The default number of parallel checks is 8.
@@ -5470,7 +5486,7 @@ Returns unencrypted file names when provided with a list of encrypted
 file names.
 List limit is 10 items.
 .PP
-If you supply the \f[C]--reverse\f[R] flag, it will return encrypted
+If you supply the \f[V]--reverse\f[R] flag, it will return encrypted
 file names.
 .PP
 use it like this
@@ -5484,7 +5500,7 @@ rclone cryptdecode --reverse encryptedremote: filename1 filename2
 .fi
 .PP
 Another way to accomplish this is by using the
-\f[C]rclone backend encode\f[R] (or \f[C]decode\f[R]) command.
+\f[V]rclone backend encode\f[R] (or \f[V]decode\f[R]) command.
 See the documentation on the crypt (https://rclone.org/crypt/) overlay
 for more info.
 .IP
@@ -5514,7 +5530,7 @@ Remove a single file from remote.
 .SS Synopsis
 .PP
 Remove a single file from remote.
-Unlike \f[C]delete\f[R] it cannot be used to remove a directory and it
+Unlike \f[V]delete\f[R] it cannot be used to remove a directory and it
 doesn\[aq]t obey include/exclude filters - if the specified file exists,
 it will always be removed.
 .IP
@@ -5583,7 +5599,7 @@ commands, flags and backends.
 Speaks with git-annex over stdin/stdout.
 .SS Synopsis
 .PP
-Rclone\[aq]s \f[C]gitannex\f[R] subcommand enables
+Rclone\[aq]s \f[V]gitannex\f[R] subcommand enables
 git-annex (https://git-annex.branchable.com/) to store and retrieve
 content from an rclone remote.
 It is meant to be run by git-annex, not directly by users.
@@ -5611,7 +5627,7 @@ which git-annex-remote-rclone-builtin
 .IP "2." 3
 Add a new remote to your git-annex repo.
 This new remote will connect git-annex with the
-\f[C]rclone gitannex\f[R] subcommand.
+\f[V]rclone gitannex\f[R] subcommand.
 .RS 4
 .PP
 Start by asking git-annex to describe the remote\[aq]s available
@@ -5630,16 +5646,16 @@ git annex initremote MyRemote type=external externaltype=rclone-builtin --whatel
 .PP
 \f[B]NOTE\f[R]: If you\[aq]re porting an existing
 git-annex-remote-rclone (https://github.com/git-annex-remote-rclone/git-annex-remote-rclone)
-remote to use \f[C]rclone gitannex\f[R], you can probably reuse the
+remote to use \f[V]rclone gitannex\f[R], you can probably reuse the
 configuration parameters verbatim without renaming them.
-Check parameter synonyms with \f[C]--whatelse\f[R] as shown above.
+Check parameter synonyms with \f[V]--whatelse\f[R] as shown above.
 .RE
 .PP
 The following example creates a new git-annex remote named
 \[dq]MyRemote\[dq] that will use the rclone remote named
 \[dq]SomeRcloneRemote\[dq].
 That rclone remote must be one configured in your rclone.conf file,
-which can be located with \f[C]rclone config file\f[R].
+which can be located with \f[V]rclone config file\f[R].
 .IP
 .nf
 \f[C]
@@ -5863,9 +5879,9 @@ Lists all the available remotes from the config file, or the remotes
 matching an optional filter.
 .PP
 Prints the result in human-readable format by default, and as a simple
-list of remote names, or if used with flag \f[C]--long\f[R] a tabular
+list of remote names, or if used with flag \f[V]--long\f[R] a tabular
 format including the remote names, types and descriptions.
-Using flag \f[C]--json\f[R] produces machine-readable output instead,
+Using flag \f[V]--json\f[R] produces machine-readable output instead,
 which always includes all attributes - including the source (file or
 environment).
 .PP
@@ -5924,7 +5940,7 @@ fubuwic
 \f[R]
 .fi
 .PP
-Use the \f[C]--format\f[R] option to control what gets listed.
+Use the \f[V]--format\f[R] option to control what gets listed.
 By default this is just the path, but you can use these parameters to
 control the output:
 .IP
@@ -5944,8 +5960,8 @@ M - Metadata of object in JSON blob format, eg {\[dq]key\[dq]:\[dq]value\[dq]}
 .fi
 .PP
 So if you wanted the path, size and modification time, you would use
-\f[C]--format \[dq]pst\[dq]\f[R], or maybe
-\f[C]--format \[dq]tsp\[dq]\f[R] to put the path last.
+\f[V]--format \[dq]pst\[dq]\f[R], or maybe
+\f[V]--format \[dq]tsp\[dq]\f[R] to put the path last.
 .PP
 Eg
 .IP
@@ -5961,7 +5977,7 @@ $ rclone lsf  --format \[dq]tsp\[dq] swift:bucket
 .fi
 .PP
 If you specify \[dq]h\[dq] in the format you will get the MD5 hash by
-default, use the \f[C]--hash\f[R] flag to change which hash you want.
+default, use the \f[V]--hash\f[R] flag to change which hash you want.
 Note that this can be returned as an empty string if it isn\[aq]t
 available on the object (and for directories), \[dq]ERROR\[dq] if there
 was an error reading it from the object and \[dq]UNSUPPORTED\[dq] if
@@ -5991,7 +6007,7 @@ cd65ac234e6fea5925974a51cdd865cc  canole
 (Though \[dq]rclone md5sum .\[dq] is an easier way of typing this.)
 .PP
 By default the separator is \[dq];\[dq] this can be changed with the
-\f[C]--separator\f[R] flag.
+\f[V]--separator\f[R] flag.
 Note that separators aren\[aq]t escaped in the path so putting it last
 is a good strategy.
 .PP
@@ -6022,8 +6038,8 @@ test.sh,449
 \f[R]
 .fi
 .PP
-Note that the \f[C]--absolute\f[R] parameter is useful for making lists
-of files to pass to an rclone copy with the \f[C]--files-from-raw\f[R]
+Note that the \f[V]--absolute\f[R] parameter is useful for making lists
+of files to pass to an rclone copy with the \f[V]--files-from-raw\f[R]
 flag.
 .PP
 For example, to find all the files modified within one day and copy
@@ -6036,9 +6052,9 @@ rclone copy --files-from-raw new_files /path/to/local remote:path
 \f[R]
 .fi
 .PP
-The default time format is \f[C]\[aq]2006-01-02 15:04:05\[aq]\f[R].
+The default time format is \f[V]\[aq]2006-01-02 15:04:05\[aq]\f[R].
 Other formats (https://pkg.go.dev/time#pkg-constants) can be specified
-with the \f[C]--time-format\f[R] flag.
+with the \f[V]--time-format\f[R] flag.
 Examples:
 .IP
 .nf
@@ -6052,34 +6068,34 @@ rclone lsf remote:path --format pt --time-format max
 \f[R]
 .fi
 .PP
-\f[C]--time-format max\f[R] will automatically truncate
-\[aq]\f[C]2006-01-02 15:04:05.000000000\f[R]\[aq] to the maximum
+\f[V]--time-format max\f[R] will automatically truncate
+\[aq]\f[V]2006-01-02 15:04:05.000000000\f[R]\[aq] to the maximum
 precision supported by the remote.
 .PP
 Any of the filtering options can be applied to this command.
 .PP
 There are several related list commands
 .IP \[bu] 2
-\f[C]ls\f[R] to list size and path of objects only
+\f[V]ls\f[R] to list size and path of objects only
 .IP \[bu] 2
-\f[C]lsl\f[R] to list modification time, size and path of objects only
+\f[V]lsl\f[R] to list modification time, size and path of objects only
 .IP \[bu] 2
-\f[C]lsd\f[R] to list directories only
+\f[V]lsd\f[R] to list directories only
 .IP \[bu] 2
-\f[C]lsf\f[R] to list objects and directories in easy to parse format
+\f[V]lsf\f[R] to list objects and directories in easy to parse format
 .IP \[bu] 2
-\f[C]lsjson\f[R] to list objects and directories in JSON format
+\f[V]lsjson\f[R] to list objects and directories in JSON format
 .PP
-\f[C]ls\f[R],\f[C]lsl\f[R],\f[C]lsd\f[R] are designed to be
+\f[V]ls\f[R],\f[V]lsl\f[R],\f[V]lsd\f[R] are designed to be
 human-readable.
-\f[C]lsf\f[R] is designed to be human and machine-readable.
-\f[C]lsjson\f[R] is designed to be machine-readable.
+\f[V]lsf\f[R] is designed to be human and machine-readable.
+\f[V]lsjson\f[R] is designed to be machine-readable.
 .PP
-Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default - use
-\f[C]--max-depth 1\f[R] to stop the recursion.
+Note that \f[V]ls\f[R] and \f[V]lsl\f[R] recurse by default - use
+\f[V]--max-depth 1\f[R] to stop the recursion.
 .PP
-The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default - use \f[C]-R\f[R] to make them recurse.
+The other list commands \f[V]lsd\f[R],\f[V]lsf\f[R],\f[V]lsjson\f[R] do
+not recurse by default - use \f[V]-R\f[R] to make them recurse.
 .PP
 Listing a nonexistent directory will produce an error except for remotes
 which can\[aq]t have empty directories (e.g.
@@ -6196,30 +6212,30 @@ It will always be omitted when value is not true.
 .IP \[bu] 2
 Properties Encrypted and EncryptedPath will only be included for
 encrypted remotes, and (as mentioned below) only if the
-\f[C]--encrypted\f[R] option is set.
+\f[V]--encrypted\f[R] option is set.
 .PP
 Different options may also affect which properties are included:
 .IP \[bu] 2
-If \f[C]--hash\f[R] is not specified, the Hashes property will be
+If \f[V]--hash\f[R] is not specified, the Hashes property will be
 omitted.
-The types of hash can be specified with the \f[C]--hash-type\f[R]
+The types of hash can be specified with the \f[V]--hash-type\f[R]
 parameter (which may be repeated).
-If \f[C]--hash-type\f[R] is set then it implies \f[C]--hash\f[R].
+If \f[V]--hash-type\f[R] is set then it implies \f[V]--hash\f[R].
 .IP \[bu] 2
-If \f[C]--no-modtime\f[R] is specified then ModTime will be blank.
+If \f[V]--no-modtime\f[R] is specified then ModTime will be blank.
 This can speed things up on remotes where reading the ModTime takes an
 extra request (e.g.
 s3, swift).
 .IP \[bu] 2
-If \f[C]--no-mimetype\f[R] is specified then MimeType will be blank.
+If \f[V]--no-mimetype\f[R] is specified then MimeType will be blank.
 This can speed things up on remotes where reading the MimeType takes an
 extra request (e.g.
 s3, swift).
 .IP \[bu] 2
-If \f[C]--encrypted\f[R] is not specified the Encrypted and
+If \f[V]--encrypted\f[R] is not specified the Encrypted and
 EncryptedPath properties will be omitted - even for encrypted remotes.
 .IP \[bu] 2
-If \f[C]--metadata\f[R] is set then an additional Metadata property will
+If \f[V]--metadata\f[R] is set then an additional Metadata property will
 be returned.
 This will have metadata (https://rclone.org/docs/#metadata) in rclone
 standard format as a JSON object.
@@ -6227,13 +6243,13 @@ standard format as a JSON object.
 The default is to list directories and files/objects, but this can be
 changed with the following options:
 .IP \[bu] 2
-If \f[C]--dirs-only\f[R] is specified then directories will be returned
+If \f[V]--dirs-only\f[R] is specified then directories will be returned
 only, no files/objects.
 .IP \[bu] 2
-If \f[C]--files-only\f[R] is specified then files will be returned only,
+If \f[V]--files-only\f[R] is specified then files will be returned only,
 no directories.
 .PP
-If \f[C]--stat\f[R] is set then the the output is not an array of items,
+If \f[V]--stat\f[R] is set then the the output is not an array of items,
 but instead a single JSON blob will be returned about the item pointed
 to.
 This will return an error if the item isn\[aq]t found, however on bucket
@@ -6246,7 +6262,7 @@ listed.
 If \[dq]remote:path\[dq] contains the file \[dq]subfolder/file.txt\[dq],
 the Path for \[dq]file.txt\[dq] will be \[dq]subfolder/file.txt\[dq],
 not \[dq]remote:path/subfolder/file.txt\[dq].
-When used without \f[C]--recursive\f[R] the Path will always be the same
+When used without \f[V]--recursive\f[R] the Path will always be the same
 as Name.
 .PP
 The time is in RFC3339 format with up to nanosecond precision.
@@ -6255,37 +6271,37 @@ that the remote can hold the times, so if times are accurate to the
 nearest millisecond (e.g.
 Google Drive) then 3 digits will always be shown
 (\[dq]2017-05-31T16:15:57.034+01:00\[dq]) whereas if the times are
-accurate to the nearest second (Dropbox, Box, WebDav, etc.) no digits
-will be shown (\[dq]2017-05-31T16:15:57+01:00\[dq]).
+accurate to the nearest second (Dropbox, Box, WebDav, etc.)
+no digits will be shown (\[dq]2017-05-31T16:15:57+01:00\[dq]).
 .PP
 The whole output can be processed as a JSON blob, or alternatively it
 can be processed line by line as each item is written on individual
-lines (except with \f[C]--stat\f[R]).
+lines (except with \f[V]--stat\f[R]).
 .PP
 Any of the filtering options can be applied to this command.
 .PP
 There are several related list commands
 .IP \[bu] 2
-\f[C]ls\f[R] to list size and path of objects only
+\f[V]ls\f[R] to list size and path of objects only
 .IP \[bu] 2
-\f[C]lsl\f[R] to list modification time, size and path of objects only
+\f[V]lsl\f[R] to list modification time, size and path of objects only
 .IP \[bu] 2
-\f[C]lsd\f[R] to list directories only
+\f[V]lsd\f[R] to list directories only
 .IP \[bu] 2
-\f[C]lsf\f[R] to list objects and directories in easy to parse format
+\f[V]lsf\f[R] to list objects and directories in easy to parse format
 .IP \[bu] 2
-\f[C]lsjson\f[R] to list objects and directories in JSON format
+\f[V]lsjson\f[R] to list objects and directories in JSON format
 .PP
-\f[C]ls\f[R],\f[C]lsl\f[R],\f[C]lsd\f[R] are designed to be
+\f[V]ls\f[R],\f[V]lsl\f[R],\f[V]lsd\f[R] are designed to be
 human-readable.
-\f[C]lsf\f[R] is designed to be human and machine-readable.
-\f[C]lsjson\f[R] is designed to be machine-readable.
+\f[V]lsf\f[R] is designed to be human and machine-readable.
+\f[V]lsjson\f[R] is designed to be machine-readable.
 .PP
-Note that \f[C]ls\f[R] and \f[C]lsl\f[R] recurse by default - use
-\f[C]--max-depth 1\f[R] to stop the recursion.
+Note that \f[V]ls\f[R] and \f[V]lsl\f[R] recurse by default - use
+\f[V]--max-depth 1\f[R] to stop the recursion.
 .PP
-The other list commands \f[C]lsd\f[R],\f[C]lsf\f[R],\f[C]lsjson\f[R] do
-not recurse by default - use \f[C]-R\f[R] to make them recurse.
+The other list commands \f[V]lsd\f[R],\f[V]lsf\f[R],\f[V]lsjson\f[R] do
+not recurse by default - use \f[V]-R\f[R] to make them recurse.
 .PP
 Listing a nonexistent directory will produce an error except for remotes
 which can\[aq]t have empty directories (e.g.
@@ -6370,13 +6386,13 @@ Mount the remote as file system on a mountpoint.
 Rclone mount allows Linux, FreeBSD, macOS and Windows to mount any of
 Rclone\[aq]s cloud storage systems as a file system with FUSE.
 .PP
-First set up your remote using \f[C]rclone config\f[R].
-Check it works with \f[C]rclone ls\f[R] etc.
+First set up your remote using \f[V]rclone config\f[R].
+Check it works with \f[V]rclone ls\f[R] etc.
 .PP
 On Linux and macOS, you can run mount in either foreground or background
 (aka daemon) mode.
 Mount runs in foreground mode by default.
-Use the \f[C]--daemon\f[R] flag to force background mode.
+Use the \f[V]--daemon\f[R] flag to force background mode.
 On Windows you can run mount in foreground only, the flag is ignored.
 .PP
 In background mode rclone acts as a generic Unix mount program: the main
@@ -6385,7 +6401,7 @@ the mount, waits until success or timeout and exits with appropriate
 code (killing the child process if it fails).
 .PP
 On Linux/macOS/FreeBSD start the mount like this, where
-\f[C]/path/to/local/mount\f[R] is an \f[B]empty\f[R] \f[B]existing\f[R]
+\f[V]/path/to/local/mount\f[R] is an \f[B]empty\f[R] \f[B]existing\f[R]
 directory:
 .IP
 .nf
@@ -6402,11 +6418,11 @@ used to work with the mount until rclone is interrupted e.g.
 by pressing Ctrl-C.
 .PP
 The following examples will mount to an automatically assigned drive, to
-specific drive letter \f[C]X:\f[R], to path
-\f[C]C:\[rs]path\[rs]parent\[rs]mount\f[R] (where parent directory or
+specific drive letter \f[V]X:\f[R], to path
+\f[V]C:\[rs]path\[rs]parent\[rs]mount\f[R] (where parent directory or
 drive must exist, and mount must \f[B]not\f[R] exist, and is not
 supported when mounting as a network drive), and the last example will
-mount as network share \f[C]\[rs]\[rs]cloud\[rs]remote\f[R] and map it
+mount as network share \f[V]\[rs]\[rs]cloud\[rs]remote\f[R] and map it
 to an automatically assigned drive:
 .IP
 .nf
@@ -6482,7 +6498,7 @@ mounting as a network drive instead.
 When mounting as a fixed disk drive you can either mount to an unused
 drive letter, or to a path representing a \f[B]nonexistent\f[R]
 subdirectory of an \f[B]existing\f[R] parent directory or drive.
-Using the special value \f[C]*\f[R] will tell rclone to automatically
+Using the special value \f[V]*\f[R] will tell rclone to automatically
 assign the next available drive letter, starting with Z: and moving
 backward.
 Examples:
@@ -6496,11 +6512,11 @@ rclone mount remote:path/to/files X:
 \f[R]
 .fi
 .PP
-Option \f[C]--volname\f[R] can be used to set a custom volume name for
+Option \f[V]--volname\f[R] can be used to set a custom volume name for
 the mounted file system.
 The default is to use the remote name and path.
 .PP
-To mount as network drive, you can add option \f[C]--network-mode\f[R]
+To mount as network drive, you can add option \f[V]--network-mode\f[R]
 to your mount command.
 Mounting to a directory path is not supported in this mode, it is a
 limitation Windows imposes on junctions, so the remote must always be
@@ -6512,25 +6528,25 @@ rclone mount remote:path/to/files X: --network-mode
 \f[R]
 .fi
 .PP
-A volume name specified with \f[C]--volname\f[R] will be used to create
+A volume name specified with \f[V]--volname\f[R] will be used to create
 the network share path.
-A complete UNC path, such as \f[C]\[rs]\[rs]cloud\[rs]remote\f[R],
+A complete UNC path, such as \f[V]\[rs]\[rs]cloud\[rs]remote\f[R],
 optionally with path
-\f[C]\[rs]\[rs]cloud\[rs]remote\[rs]madeup\[rs]path\f[R], will be used
+\f[V]\[rs]\[rs]cloud\[rs]remote\[rs]madeup\[rs]path\f[R], will be used
 as is.
 Any other string will be used as the share part, after a default prefix
-\f[C]\[rs]\[rs]server\[rs]\f[R].
-If no volume name is specified then \f[C]\[rs]\[rs]server\[rs]share\f[R]
+\f[V]\[rs]\[rs]server\[rs]\f[R].
+If no volume name is specified then \f[V]\[rs]\[rs]server\[rs]share\f[R]
 will be used.
 You must make sure the volume name is unique when you are mounting more
 than one drive, or else the mount command will fail.
 The share name will treated as the volume label for the mapped drive,
 shown in Windows Explorer etc, while the complete
-\f[C]\[rs]\[rs]server\[rs]share\f[R] will be reported as the remote UNC
-path by \f[C]net use\f[R] etc, just like a normal network drive mapping.
+\f[V]\[rs]\[rs]server\[rs]share\f[R] will be reported as the remote UNC
+path by \f[V]net use\f[R] etc, just like a normal network drive mapping.
 .PP
-If you specify a full network share UNC path with \f[C]--volname\f[R],
-this will implicitly set the \f[C]--network-mode\f[R] option, so the
+If you specify a full network share UNC path with \f[V]--volname\f[R],
+this will implicitly set the \f[V]--network-mode\f[R] option, so the
 following two examples have same result:
 .IP
 .nf
@@ -6543,10 +6559,10 @@ rclone mount remote:path/to/files X: --volname \[rs]\[rs]server\[rs]share
 You may also specify the network share UNC path as the mountpoint
 itself.
 Then rclone will automatically assign a drive letter, same as with
-\f[C]*\f[R] and use that as mountpoint, and instead use the UNC path
+\f[V]*\f[R] and use that as mountpoint, and instead use the UNC path
 specified as the volume name, as if it were specified with the
-\f[C]--volname\f[R] option.
-This will also implicitly set the \f[C]--network-mode\f[R] option.
+\f[V]--volname\f[R] option.
+This will also implicitly set the \f[V]--network-mode\f[R] option.
 This means the following two examples have same result:
 .IP
 .nf
@@ -6558,7 +6574,7 @@ rclone mount remote:path/to/files * --volname \[rs]\[rs]cloud\[rs]remote
 .PP
 There is yet another way to enable network mode, and to set the share
 path, and that is to pass the \[dq]native\[dq] libfuse/WinFsp option
-directly: \f[C]--fuse-flag --VolumePrefix=\[rs]server\[rs]share\f[R].
+directly: \f[V]--fuse-flag --VolumePrefix=\[rs]server\[rs]share\f[R].
 Note that the path must be with just a single backslash prefix in this
 case.
 .PP
@@ -6582,18 +6598,18 @@ By default, the owner and group will be taken from the current user, and
 the built-in group \[dq]Everyone\[dq] will be used to represent others.
 The user/group can be customized with FUSE options \[dq]UserName\[dq]
 and \[dq]GroupName\[dq], e.g.
-\f[C]-o UserName=user123 -o GroupName=\[dq]Authenticated Users\[dq]\f[R].
+\f[V]-o UserName=user123 -o GroupName=\[dq]Authenticated Users\[dq]\f[R].
 The permissions on each entry will be set according to options
-\f[C]--dir-perms\f[R] and \f[C]--file-perms\f[R], which takes a value in
+\f[V]--dir-perms\f[R] and \f[V]--file-perms\f[R], which takes a value in
 traditional Unix numeric
 notation (https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation).
 .PP
 The default permissions corresponds to
-\f[C]--file-perms 0666 --dir-perms 0777\f[R], i.e.
+\f[V]--file-perms 0666 --dir-perms 0777\f[R], i.e.
 read and write permissions to everyone.
 This means you will not be able to start any programs from the mount.
 To be able to do that you must add execute permissions, e.g.
-\f[C]--file-perms 0777 --dir-perms 0777\f[R] to add it to everyone.
+\f[V]--file-perms 0777 --dir-perms 0777\f[R] to add it to everyone.
 If the program needs to write files, chances are you will have to enable
 VFS File Caching as well (see also limitations).
 Note that the default write permission have some restrictions for
@@ -6627,14 +6643,14 @@ with Unix.
 Some example use cases will following.
 .PP
 If you set POSIX permissions for only allowing access to the owner,
-using \f[C]--file-perms 0600 --dir-perms 0700\f[R], the user group and
+using \f[V]--file-perms 0600 --dir-perms 0700\f[R], the user group and
 the built-in \[dq]Everyone\[dq] group will still be given some special
 permissions, as described above.
 Some programs may then (incorrectly) interpret this as the file being
 accessible by everyone, for example an SSH client may warn about
 \[dq]unprotected private key file\[dq].
 You can work around this by specifying
-\f[C]-o FileSecurity=\[dq]D:P(A;;FA;;;OW)\[dq]\f[R], which sets file all
+\f[V]-o FileSecurity=\[dq]D:P(A;;FA;;;OW)\[dq]\f[R], which sets file all
 access (FA) to the owner (OW), and nothing else.
 .PP
 When setting write permissions then, except for the owner, this does not
@@ -6645,12 +6661,12 @@ denied error instead.
 To set working write permissions for the built-in \[dq]Everyone\[dq]
 group, similar to what it gets by default but with the addition of the
 \[dq]write extended attributes\[dq], you can specify
-\f[C]-o FileSecurity=\[dq]D:P(A;;FRFW;;;WD)\[dq]\f[R], which sets file
+\f[V]-o FileSecurity=\[dq]D:P(A;;FRFW;;;WD)\[dq]\f[R], which sets file
 read (FR) and file write (FW) to everyone (WD).
 If file execute (FX) is also needed, then change to
-\f[C]-o FileSecurity=\[dq]D:P(A;;FRFWFX;;;WD)\[dq]\f[R], or set file all
+\f[V]-o FileSecurity=\[dq]D:P(A;;FRFWFX;;;WD)\[dq]\f[R], or set file all
 access (FA) to get full access permissions, including delete, with
-\f[C]-o FileSecurity=\[dq]D:P(A;;FA;;;WD)\[dq]\f[R].
+\f[V]-o FileSecurity=\[dq]D:P(A;;FA;;;WD)\[dq]\f[R].
 .SS Windows caveats
 .PP
 Drives created as Administrator are not visible to other accounts, not
@@ -6677,7 +6693,7 @@ account.
 There are several ways to do this: One is to use the command-line
 utility
 PsExec (https://docs.microsoft.com/en-us/sysinternals/downloads/psexec),
-from Microsoft\[aq]s Sysinternals suite, which has option \f[C]-s\f[R]
+from Microsoft\[aq]s Sysinternals suite, which has option \f[V]-s\f[R]
 to start processes as the SYSTEM account.
 Another alternative is to run the mount command from a Windows Scheduled
 Task, or a Windows Service, configured to run as the SYSTEM account.
@@ -6686,7 +6702,7 @@ infrastructure (https://github.com/winfsp/winfsp/wiki/WinFsp-Service-Architectur
 Read more in the install documentation (https://rclone.org/install/).
 Note that when running rclone as another user, it will not use the
 configuration file from your profile unless you tell it to with the
-\f[C]--config\f[R] (https://rclone.org/docs/#config-config-file) option.
+\f[V]--config\f[R] (https://rclone.org/docs/#config-config-file) option.
 Note also that it is now the SYSTEM account that will have the owner
 permissions, and other accounts will have permissions according to the
 group or others scopes.
@@ -6710,8 +6726,8 @@ local server.
 .SS Unicode Normalization
 .PP
 It is highly recommended to keep the default of
-\f[C]--no-unicode-normalization=false\f[R] for all \f[C]mount\f[R] and
-\f[C]serve\f[R] commands on macOS.
+\f[V]--no-unicode-normalization=false\f[R] for all \f[V]mount\f[R] and
+\f[V]serve\f[R] commands on macOS.
 For details, see
 vfs-case-sensitivity (https://rclone.org/commands/rclone_mount/#vfs-case-sensitivity).
 .SS NFS mount
@@ -6723,8 +6739,8 @@ If you run this in background mode using |--daemon|, you will need to
 send SIGTERM signal to the rclone process using |kill| command to stop
 the mount.
 .PP
-Note that \f[C]--nfs-cache-handle-limit\f[R] controls the maximum number
-of cached file handles stored by the \f[C]nfsmount\f[R] caching handler.
+Note that \f[V]--nfs-cache-handle-limit\f[R] controls the maximum number
+of cached file handles stored by the \f[V]nfsmount\f[R] caching handler.
 This should not be set too low or you may experience errors when trying
 to access files.
 The default is 1000000, but consider lowering this limit if the
@@ -6767,16 +6783,16 @@ will cause rlcone to update the modification time of the file.
 This may make rclone upload a full new copy of the file.
 .SS Read Only mounts
 .PP
-When mounting with \f[C]--read-only\f[R], attempts to write to files
+When mounting with \f[V]--read-only\f[R], attempts to write to files
 will fail \f[I]silently\f[R] as opposed to with a clear warning as in
 macFUSE.
 .SS Limitations
 .PP
-Without the use of \f[C]--vfs-cache-mode\f[R] this can only write files
+Without the use of \f[V]--vfs-cache-mode\f[R] this can only write files
 sequentially, it can only seek when reading.
 This means that many applications won\[aq]t work with their files on an
-rclone mount without \f[C]--vfs-cache-mode writes\f[R] or
-\f[C]--vfs-cache-mode full\f[R].
+rclone mount without \f[V]--vfs-cache-mode writes\f[R] or
+\f[V]--vfs-cache-mode full\f[R].
 See the VFS File Caching section for more info.
 When using NFS mount on macOS, if you don\[aq]t specify
 |--vfs-cache-mode| the mount point will be read-only.
@@ -6786,10 +6802,10 @@ Swift, S3, Google Compute Storage, B2) do not support the concept of
 empty directories, so empty directories will have a tendency to
 disappear once they fall out of the directory cache.
 .PP
-When \f[C]rclone mount\f[R] is invoked on Unix with \f[C]--daemon\f[R]
+When \f[V]rclone mount\f[R] is invoked on Unix with \f[V]--daemon\f[R]
 flag, the main rclone program will wait for the background mount to
 become ready or until the timeout specified by the
-\f[C]--daemon-wait\f[R] flag.
+\f[V]--daemon-wait\f[R] flag.
 On Linux it can check mount status using ProcFS so the flag in fact sets
 \f[B]maximum\f[R] time to wait, while the real wait can be less.
 On macOS / BSD the time to wait is constant and the check is performed
@@ -6807,11 +6823,11 @@ making local copies of the uploads.
 Look at the VFS File Caching for solutions to make mount more reliable.
 .SS Attribute caching
 .PP
-You can use the flag \f[C]--attr-timeout\f[R] to set the time the kernel
-caches the attributes (size, modification time, etc.) for directory
-entries.
+You can use the flag \f[V]--attr-timeout\f[R] to set the time the kernel
+caches the attributes (size, modification time, etc.)
+for directory entries.
 .PP
-The default is \f[C]1s\f[R] which caches files just long enough to avoid
+The default is \f[V]1s\f[R] which caches files just long enough to avoid
 too many callbacks to rclone from the kernel.
 .PP
 In theory 0s should be the correct value for filesystems which can
@@ -6824,18 +6840,18 @@ and excessive time listing
 directories (https://github.com/rclone/rclone/issues/2095#issuecomment-371141147).
 .PP
 The kernel can cache the info about a file for the time given by
-\f[C]--attr-timeout\f[R].
+\f[V]--attr-timeout\f[R].
 You may see corruption if the remote file changes length during this
 window.
 It will show up as either a truncated file or a file with garbage on the
 end.
-With \f[C]--attr-timeout 1s\f[R] this is very unlikely but not
+With \f[V]--attr-timeout 1s\f[R] this is very unlikely but not
 impossible.
-The higher you set \f[C]--attr-timeout\f[R] the more likely it is.
+The higher you set \f[V]--attr-timeout\f[R] the more likely it is.
 The default setting of \[dq]1s\[dq] is the lowest setting which
 mitigates the problems above.
 .PP
-If you set it higher (\f[C]10s\f[R] or \f[C]1m\f[R] say) then the kernel
+If you set it higher (\f[V]10s\f[R] or \f[V]1m\f[R] say) then the kernel
 will call back to rclone less often making it more efficient, however
 there is more chance of the corruption issue above.
 .PP
@@ -6857,28 +6873,28 @@ Units having the rclone mount service specified as a requirement will
 see all files and folders immediately in this mode.
 .PP
 Note that systemd runs mount units without any environment variables
-including \f[C]PATH\f[R] or \f[C]HOME\f[R].
-This means that tilde (\f[C]\[ti]\f[R]) expansion will not work and you
-should provide \f[C]--config\f[R] and \f[C]--cache-dir\f[R] explicitly
+including \f[V]PATH\f[R] or \f[V]HOME\f[R].
+This means that tilde (\f[V]\[ti]\f[R]) expansion will not work and you
+should provide \f[V]--config\f[R] and \f[V]--cache-dir\f[R] explicitly
 as absolute paths via rclone arguments.
-Since mounting requires the \f[C]fusermount\f[R] or
-\f[C]fusermount3\f[R] program, rclone will use the fallback PATH of
-\f[C]/bin:/usr/bin\f[R] in this scenario.
-Please ensure that \f[C]fusermount\f[R]/\f[C]fusermount3\f[R] is present
+Since mounting requires the \f[V]fusermount\f[R] or
+\f[V]fusermount3\f[R] program, rclone will use the fallback PATH of
+\f[V]/bin:/usr/bin\f[R] in this scenario.
+Please ensure that \f[V]fusermount\f[R]/\f[V]fusermount3\f[R] is present
 on this PATH.
 .SS Rclone as Unix mount helper
 .PP
-The core Unix program \f[C]/bin/mount\f[R] normally takes the
-\f[C]-t FSTYPE\f[R] argument then runs the \f[C]/sbin/mount.FSTYPE\f[R]
-helper program passing it mount options as \f[C]-o key=val,...\f[R] or
-\f[C]--opt=...\f[R].
+The core Unix program \f[V]/bin/mount\f[R] normally takes the
+\f[V]-t FSTYPE\f[R] argument then runs the \f[V]/sbin/mount.FSTYPE\f[R]
+helper program passing it mount options as \f[V]-o key=val,...\f[R] or
+\f[V]--opt=...\f[R].
 Automount (classic or systemd) behaves in a similar way.
 .PP
-rclone by default expects GNU-style flags \f[C]--key val\f[R].
+rclone by default expects GNU-style flags \f[V]--key val\f[R].
 To run it as a mount helper you should symlink rclone binary to
-\f[C]/sbin/mount.rclone\f[R] and optionally \f[C]/usr/bin/rclonefs\f[R],
+\f[V]/sbin/mount.rclone\f[R] and optionally \f[V]/usr/bin/rclonefs\f[R],
 e.g.
-\f[C]ln -s /usr/bin/rclone /sbin/mount.rclone\f[R].
+\f[V]ln -s /usr/bin/rclone /sbin/mount.rclone\f[R].
 rclone will detect it and translate command-line arguments
 appropriately.
 .PP
@@ -6920,7 +6936,7 @@ WantedBy=multi-user.target
 \f[R]
 .fi
 .PP
-or add in \f[C]/etc/fstab\f[R] a line like
+or add in \f[V]/etc/fstab\f[R] a line like
 .IP
 .nf
 \f[C]
@@ -6929,11 +6945,11 @@ sftp1:subdir /mnt/data rclone rw,noauto,nofail,_netdev,x-systemd.automount,args2
 .fi
 .PP
 or use classic Automountd.
-Remember to provide explicit \f[C]config=...,cache-dir=...\f[R] as a
-workaround for mount units being run without \f[C]HOME\f[R].
+Remember to provide explicit \f[V]config=...,cache-dir=...\f[R] as a
+workaround for mount units being run without \f[V]HOME\f[R].
 .PP
-Rclone in the mount helper mode will split \f[C]-o\f[R] argument(s) by
-comma, replace \f[C]_\f[R] by \f[C]-\f[R] and prepend \f[C]--\f[R] to
+Rclone in the mount helper mode will split \f[V]-o\f[R] argument(s) by
+comma, replace \f[V]_\f[R] by \f[V]-\f[R] and prepend \f[V]--\f[R] to
 get the command-line flags.
 Options containing commas or spaces can be wrapped in single or double
 quotes.
@@ -6941,27 +6957,27 @@ Any inner quotes inside outer quotes of the same type should be doubled.
 .PP
 Mount option syntax includes a few extra options treated specially:
 .IP \[bu] 2
-\f[C]env.NAME=VALUE\f[R] will set an environment variable for the mount
+\f[V]env.NAME=VALUE\f[R] will set an environment variable for the mount
 process.
 This helps with Automountd and Systemd.mount which don\[aq]t allow
 setting custom environment for mount helpers.
-Typically you will use \f[C]env.HTTPS_PROXY=proxy.host:3128\f[R] or
-\f[C]env.HOME=/root\f[R]
+Typically you will use \f[V]env.HTTPS_PROXY=proxy.host:3128\f[R] or
+\f[V]env.HOME=/root\f[R]
 .IP \[bu] 2
-\f[C]command=cmount\f[R] can be used to run \f[C]cmount\f[R] or any
-other rclone command rather than the default \f[C]mount\f[R].
+\f[V]command=cmount\f[R] can be used to run \f[V]cmount\f[R] or any
+other rclone command rather than the default \f[V]mount\f[R].
 .IP \[bu] 2
-\f[C]args2env\f[R] will pass mount options to the mount helper running
+\f[V]args2env\f[R] will pass mount options to the mount helper running
 in background via environment variables instead of command line
 arguments.
-This allows to hide secrets from such commands as \f[C]ps\f[R] or
-\f[C]pgrep\f[R].
+This allows to hide secrets from such commands as \f[V]ps\f[R] or
+\f[V]pgrep\f[R].
 .IP \[bu] 2
-\f[C]vv...\f[R] will be transformed into appropriate
-\f[C]--verbose=N\f[R]
+\f[V]vv...\f[R] will be transformed into appropriate
+\f[V]--verbose=N\f[R]
 .IP \[bu] 2
-standard mount options like \f[C]x-systemd.automount\f[R],
-\f[C]_netdev\f[R], \f[C]nosuid\f[R] and alike are intended only for
+standard mount options like \f[V]x-systemd.automount\f[R],
+\f[V]_netdev\f[R], \f[V]nosuid\f[R] and alike are intended only for
 Automountd and ignored by rclone.
 .SS VFS - Virtual File System
 .PP
@@ -6979,7 +6995,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -6999,7 +7015,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -7028,7 +7044,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -7041,7 +7057,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -7068,37 +7084,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -7108,10 +7124,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -7174,15 +7190,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -7207,19 +7223,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -7244,50 +7260,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -7296,7 +7312,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -7321,10 +7337,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -7347,7 +7363,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -7376,7 +7392,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -7384,11 +7400,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -7398,9 +7414,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -7416,14 +7432,14 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
@@ -7570,9 +7586,9 @@ testing by size and modification time or MD5SUM.
 src will be deleted on successful transfer.
 .PP
 \f[B]Important\f[R]: Since this can cause data loss, test first with the
-\f[C]--dry-run\f[R] or the \f[C]--interactive\f[R]/\f[C]-i\f[R] flag.
+\f[V]--dry-run\f[R] or the \f[V]--interactive\f[R]/\f[V]-i\f[R] flag.
 .PP
-\f[B]Note\f[R]: Use the \f[C]-P\f[R]/\f[C]--progress\f[R] flag to view
+\f[B]Note\f[R]: Use the \f[V]-P\f[R]/\f[V]--progress\f[R] flag to view
 real-time transfer statistics.
 .IP
 .nf
@@ -7707,9 +7723,9 @@ The supported keys are:
 .IP
 .nf
 \f[C]
- \[ua],\[da] or k,j to Move
- \[->],l to enter
- \[<-],h to return
+ ↑,↓ or k,j to Move
+ →,l to enter
+ ←,h to return
  g toggle graph
  c toggle counts
  a toggle average size in directory
@@ -7831,13 +7847,13 @@ Mount the remote as file system on a mountpoint.
 Rclone nfsmount allows Linux, FreeBSD, macOS and Windows to mount any of
 Rclone\[aq]s cloud storage systems as a file system with FUSE.
 .PP
-First set up your remote using \f[C]rclone config\f[R].
-Check it works with \f[C]rclone ls\f[R] etc.
+First set up your remote using \f[V]rclone config\f[R].
+Check it works with \f[V]rclone ls\f[R] etc.
 .PP
 On Linux and macOS, you can run mount in either foreground or background
 (aka daemon) mode.
 Mount runs in foreground mode by default.
-Use the \f[C]--daemon\f[R] flag to force background mode.
+Use the \f[V]--daemon\f[R] flag to force background mode.
 On Windows you can run mount in foreground only, the flag is ignored.
 .PP
 In background mode rclone acts as a generic Unix mount program: the main
@@ -7846,7 +7862,7 @@ the mount, waits until success or timeout and exits with appropriate
 code (killing the child process if it fails).
 .PP
 On Linux/macOS/FreeBSD start the mount like this, where
-\f[C]/path/to/local/mount\f[R] is an \f[B]empty\f[R] \f[B]existing\f[R]
+\f[V]/path/to/local/mount\f[R] is an \f[B]empty\f[R] \f[B]existing\f[R]
 directory:
 .IP
 .nf
@@ -7863,11 +7879,11 @@ used to work with the mount until rclone is interrupted e.g.
 by pressing Ctrl-C.
 .PP
 The following examples will mount to an automatically assigned drive, to
-specific drive letter \f[C]X:\f[R], to path
-\f[C]C:\[rs]path\[rs]parent\[rs]mount\f[R] (where parent directory or
+specific drive letter \f[V]X:\f[R], to path
+\f[V]C:\[rs]path\[rs]parent\[rs]mount\f[R] (where parent directory or
 drive must exist, and mount must \f[B]not\f[R] exist, and is not
 supported when mounting as a network drive), and the last example will
-mount as network share \f[C]\[rs]\[rs]cloud\[rs]remote\f[R] and map it
+mount as network share \f[V]\[rs]\[rs]cloud\[rs]remote\f[R] and map it
 to an automatically assigned drive:
 .IP
 .nf
@@ -7943,7 +7959,7 @@ mounting as a network drive instead.
 When mounting as a fixed disk drive you can either mount to an unused
 drive letter, or to a path representing a \f[B]nonexistent\f[R]
 subdirectory of an \f[B]existing\f[R] parent directory or drive.
-Using the special value \f[C]*\f[R] will tell rclone to automatically
+Using the special value \f[V]*\f[R] will tell rclone to automatically
 assign the next available drive letter, starting with Z: and moving
 backward.
 Examples:
@@ -7957,11 +7973,11 @@ rclone nfsmount remote:path/to/files X:
 \f[R]
 .fi
 .PP
-Option \f[C]--volname\f[R] can be used to set a custom volume name for
+Option \f[V]--volname\f[R] can be used to set a custom volume name for
 the mounted file system.
 The default is to use the remote name and path.
 .PP
-To mount as network drive, you can add option \f[C]--network-mode\f[R]
+To mount as network drive, you can add option \f[V]--network-mode\f[R]
 to your nfsmount command.
 Mounting to a directory path is not supported in this mode, it is a
 limitation Windows imposes on junctions, so the remote must always be
@@ -7973,25 +7989,25 @@ rclone nfsmount remote:path/to/files X: --network-mode
 \f[R]
 .fi
 .PP
-A volume name specified with \f[C]--volname\f[R] will be used to create
+A volume name specified with \f[V]--volname\f[R] will be used to create
 the network share path.
-A complete UNC path, such as \f[C]\[rs]\[rs]cloud\[rs]remote\f[R],
+A complete UNC path, such as \f[V]\[rs]\[rs]cloud\[rs]remote\f[R],
 optionally with path
-\f[C]\[rs]\[rs]cloud\[rs]remote\[rs]madeup\[rs]path\f[R], will be used
+\f[V]\[rs]\[rs]cloud\[rs]remote\[rs]madeup\[rs]path\f[R], will be used
 as is.
 Any other string will be used as the share part, after a default prefix
-\f[C]\[rs]\[rs]server\[rs]\f[R].
-If no volume name is specified then \f[C]\[rs]\[rs]server\[rs]share\f[R]
+\f[V]\[rs]\[rs]server\[rs]\f[R].
+If no volume name is specified then \f[V]\[rs]\[rs]server\[rs]share\f[R]
 will be used.
 You must make sure the volume name is unique when you are mounting more
 than one drive, or else the mount command will fail.
 The share name will treated as the volume label for the mapped drive,
 shown in Windows Explorer etc, while the complete
-\f[C]\[rs]\[rs]server\[rs]share\f[R] will be reported as the remote UNC
-path by \f[C]net use\f[R] etc, just like a normal network drive mapping.
+\f[V]\[rs]\[rs]server\[rs]share\f[R] will be reported as the remote UNC
+path by \f[V]net use\f[R] etc, just like a normal network drive mapping.
 .PP
-If you specify a full network share UNC path with \f[C]--volname\f[R],
-this will implicitly set the \f[C]--network-mode\f[R] option, so the
+If you specify a full network share UNC path with \f[V]--volname\f[R],
+this will implicitly set the \f[V]--network-mode\f[R] option, so the
 following two examples have same result:
 .IP
 .nf
@@ -8004,10 +8020,10 @@ rclone nfsmount remote:path/to/files X: --volname \[rs]\[rs]server\[rs]share
 You may also specify the network share UNC path as the mountpoint
 itself.
 Then rclone will automatically assign a drive letter, same as with
-\f[C]*\f[R] and use that as mountpoint, and instead use the UNC path
+\f[V]*\f[R] and use that as mountpoint, and instead use the UNC path
 specified as the volume name, as if it were specified with the
-\f[C]--volname\f[R] option.
-This will also implicitly set the \f[C]--network-mode\f[R] option.
+\f[V]--volname\f[R] option.
+This will also implicitly set the \f[V]--network-mode\f[R] option.
 This means the following two examples have same result:
 .IP
 .nf
@@ -8019,7 +8035,7 @@ rclone nfsmount remote:path/to/files * --volname \[rs]\[rs]cloud\[rs]remote
 .PP
 There is yet another way to enable network mode, and to set the share
 path, and that is to pass the \[dq]native\[dq] libfuse/WinFsp option
-directly: \f[C]--fuse-flag --VolumePrefix=\[rs]server\[rs]share\f[R].
+directly: \f[V]--fuse-flag --VolumePrefix=\[rs]server\[rs]share\f[R].
 Note that the path must be with just a single backslash prefix in this
 case.
 .PP
@@ -8043,18 +8059,18 @@ By default, the owner and group will be taken from the current user, and
 the built-in group \[dq]Everyone\[dq] will be used to represent others.
 The user/group can be customized with FUSE options \[dq]UserName\[dq]
 and \[dq]GroupName\[dq], e.g.
-\f[C]-o UserName=user123 -o GroupName=\[dq]Authenticated Users\[dq]\f[R].
+\f[V]-o UserName=user123 -o GroupName=\[dq]Authenticated Users\[dq]\f[R].
 The permissions on each entry will be set according to options
-\f[C]--dir-perms\f[R] and \f[C]--file-perms\f[R], which takes a value in
+\f[V]--dir-perms\f[R] and \f[V]--file-perms\f[R], which takes a value in
 traditional Unix numeric
 notation (https://en.wikipedia.org/wiki/File-system_permissions#Numeric_notation).
 .PP
 The default permissions corresponds to
-\f[C]--file-perms 0666 --dir-perms 0777\f[R], i.e.
+\f[V]--file-perms 0666 --dir-perms 0777\f[R], i.e.
 read and write permissions to everyone.
 This means you will not be able to start any programs from the mount.
 To be able to do that you must add execute permissions, e.g.
-\f[C]--file-perms 0777 --dir-perms 0777\f[R] to add it to everyone.
+\f[V]--file-perms 0777 --dir-perms 0777\f[R] to add it to everyone.
 If the program needs to write files, chances are you will have to enable
 VFS File Caching as well (see also limitations).
 Note that the default write permission have some restrictions for
@@ -8088,14 +8104,14 @@ with Unix.
 Some example use cases will following.
 .PP
 If you set POSIX permissions for only allowing access to the owner,
-using \f[C]--file-perms 0600 --dir-perms 0700\f[R], the user group and
+using \f[V]--file-perms 0600 --dir-perms 0700\f[R], the user group and
 the built-in \[dq]Everyone\[dq] group will still be given some special
 permissions, as described above.
 Some programs may then (incorrectly) interpret this as the file being
 accessible by everyone, for example an SSH client may warn about
 \[dq]unprotected private key file\[dq].
 You can work around this by specifying
-\f[C]-o FileSecurity=\[dq]D:P(A;;FA;;;OW)\[dq]\f[R], which sets file all
+\f[V]-o FileSecurity=\[dq]D:P(A;;FA;;;OW)\[dq]\f[R], which sets file all
 access (FA) to the owner (OW), and nothing else.
 .PP
 When setting write permissions then, except for the owner, this does not
@@ -8106,12 +8122,12 @@ denied error instead.
 To set working write permissions for the built-in \[dq]Everyone\[dq]
 group, similar to what it gets by default but with the addition of the
 \[dq]write extended attributes\[dq], you can specify
-\f[C]-o FileSecurity=\[dq]D:P(A;;FRFW;;;WD)\[dq]\f[R], which sets file
+\f[V]-o FileSecurity=\[dq]D:P(A;;FRFW;;;WD)\[dq]\f[R], which sets file
 read (FR) and file write (FW) to everyone (WD).
 If file execute (FX) is also needed, then change to
-\f[C]-o FileSecurity=\[dq]D:P(A;;FRFWFX;;;WD)\[dq]\f[R], or set file all
+\f[V]-o FileSecurity=\[dq]D:P(A;;FRFWFX;;;WD)\[dq]\f[R], or set file all
 access (FA) to get full access permissions, including delete, with
-\f[C]-o FileSecurity=\[dq]D:P(A;;FA;;;WD)\[dq]\f[R].
+\f[V]-o FileSecurity=\[dq]D:P(A;;FA;;;WD)\[dq]\f[R].
 .SS Windows caveats
 .PP
 Drives created as Administrator are not visible to other accounts, not
@@ -8138,7 +8154,7 @@ account.
 There are several ways to do this: One is to use the command-line
 utility
 PsExec (https://docs.microsoft.com/en-us/sysinternals/downloads/psexec),
-from Microsoft\[aq]s Sysinternals suite, which has option \f[C]-s\f[R]
+from Microsoft\[aq]s Sysinternals suite, which has option \f[V]-s\f[R]
 to start processes as the SYSTEM account.
 Another alternative is to run the mount command from a Windows Scheduled
 Task, or a Windows Service, configured to run as the SYSTEM account.
@@ -8147,7 +8163,7 @@ infrastructure (https://github.com/winfsp/winfsp/wiki/WinFsp-Service-Architectur
 Read more in the install documentation (https://rclone.org/install/).
 Note that when running rclone as another user, it will not use the
 configuration file from your profile unless you tell it to with the
-\f[C]--config\f[R] (https://rclone.org/docs/#config-config-file) option.
+\f[V]--config\f[R] (https://rclone.org/docs/#config-config-file) option.
 Note also that it is now the SYSTEM account that will have the owner
 permissions, and other accounts will have permissions according to the
 group or others scopes.
@@ -8171,8 +8187,8 @@ local server.
 .SS Unicode Normalization
 .PP
 It is highly recommended to keep the default of
-\f[C]--no-unicode-normalization=false\f[R] for all \f[C]mount\f[R] and
-\f[C]serve\f[R] commands on macOS.
+\f[V]--no-unicode-normalization=false\f[R] for all \f[V]mount\f[R] and
+\f[V]serve\f[R] commands on macOS.
 For details, see
 vfs-case-sensitivity (https://rclone.org/commands/rclone_mount/#vfs-case-sensitivity).
 .SS NFS mount
@@ -8184,8 +8200,8 @@ If you run this in background mode using |--daemon|, you will need to
 send SIGTERM signal to the rclone process using |kill| command to stop
 the mount.
 .PP
-Note that \f[C]--nfs-cache-handle-limit\f[R] controls the maximum number
-of cached file handles stored by the \f[C]nfsmount\f[R] caching handler.
+Note that \f[V]--nfs-cache-handle-limit\f[R] controls the maximum number
+of cached file handles stored by the \f[V]nfsmount\f[R] caching handler.
 This should not be set too low or you may experience errors when trying
 to access files.
 The default is 1000000, but consider lowering this limit if the
@@ -8228,16 +8244,16 @@ will cause rlcone to update the modification time of the file.
 This may make rclone upload a full new copy of the file.
 .SS Read Only mounts
 .PP
-When mounting with \f[C]--read-only\f[R], attempts to write to files
+When mounting with \f[V]--read-only\f[R], attempts to write to files
 will fail \f[I]silently\f[R] as opposed to with a clear warning as in
 macFUSE.
 .SS Limitations
 .PP
-Without the use of \f[C]--vfs-cache-mode\f[R] this can only write files
+Without the use of \f[V]--vfs-cache-mode\f[R] this can only write files
 sequentially, it can only seek when reading.
 This means that many applications won\[aq]t work with their files on an
-rclone mount without \f[C]--vfs-cache-mode writes\f[R] or
-\f[C]--vfs-cache-mode full\f[R].
+rclone mount without \f[V]--vfs-cache-mode writes\f[R] or
+\f[V]--vfs-cache-mode full\f[R].
 See the VFS File Caching section for more info.
 When using NFS mount on macOS, if you don\[aq]t specify
 |--vfs-cache-mode| the mount point will be read-only.
@@ -8247,10 +8263,10 @@ Swift, S3, Google Compute Storage, B2) do not support the concept of
 empty directories, so empty directories will have a tendency to
 disappear once they fall out of the directory cache.
 .PP
-When \f[C]rclone mount\f[R] is invoked on Unix with \f[C]--daemon\f[R]
+When \f[V]rclone mount\f[R] is invoked on Unix with \f[V]--daemon\f[R]
 flag, the main rclone program will wait for the background mount to
 become ready or until the timeout specified by the
-\f[C]--daemon-wait\f[R] flag.
+\f[V]--daemon-wait\f[R] flag.
 On Linux it can check mount status using ProcFS so the flag in fact sets
 \f[B]maximum\f[R] time to wait, while the real wait can be less.
 On macOS / BSD the time to wait is constant and the check is performed
@@ -8269,11 +8285,11 @@ Look at the VFS File Caching for solutions to make nfsmount more
 reliable.
 .SS Attribute caching
 .PP
-You can use the flag \f[C]--attr-timeout\f[R] to set the time the kernel
-caches the attributes (size, modification time, etc.) for directory
-entries.
+You can use the flag \f[V]--attr-timeout\f[R] to set the time the kernel
+caches the attributes (size, modification time, etc.)
+for directory entries.
 .PP
-The default is \f[C]1s\f[R] which caches files just long enough to avoid
+The default is \f[V]1s\f[R] which caches files just long enough to avoid
 too many callbacks to rclone from the kernel.
 .PP
 In theory 0s should be the correct value for filesystems which can
@@ -8286,18 +8302,18 @@ and excessive time listing
 directories (https://github.com/rclone/rclone/issues/2095#issuecomment-371141147).
 .PP
 The kernel can cache the info about a file for the time given by
-\f[C]--attr-timeout\f[R].
+\f[V]--attr-timeout\f[R].
 You may see corruption if the remote file changes length during this
 window.
 It will show up as either a truncated file or a file with garbage on the
 end.
-With \f[C]--attr-timeout 1s\f[R] this is very unlikely but not
+With \f[V]--attr-timeout 1s\f[R] this is very unlikely but not
 impossible.
-The higher you set \f[C]--attr-timeout\f[R] the more likely it is.
+The higher you set \f[V]--attr-timeout\f[R] the more likely it is.
 The default setting of \[dq]1s\[dq] is the lowest setting which
 mitigates the problems above.
 .PP
-If you set it higher (\f[C]10s\f[R] or \f[C]1m\f[R] say) then the kernel
+If you set it higher (\f[V]10s\f[R] or \f[V]1m\f[R] say) then the kernel
 will call back to rclone less often making it more efficient, however
 there is more chance of the corruption issue above.
 .PP
@@ -8319,28 +8335,28 @@ Units having the rclone nfsmount service specified as a requirement will
 see all files and folders immediately in this mode.
 .PP
 Note that systemd runs mount units without any environment variables
-including \f[C]PATH\f[R] or \f[C]HOME\f[R].
-This means that tilde (\f[C]\[ti]\f[R]) expansion will not work and you
-should provide \f[C]--config\f[R] and \f[C]--cache-dir\f[R] explicitly
+including \f[V]PATH\f[R] or \f[V]HOME\f[R].
+This means that tilde (\f[V]\[ti]\f[R]) expansion will not work and you
+should provide \f[V]--config\f[R] and \f[V]--cache-dir\f[R] explicitly
 as absolute paths via rclone arguments.
-Since mounting requires the \f[C]fusermount\f[R] or
-\f[C]fusermount3\f[R] program, rclone will use the fallback PATH of
-\f[C]/bin:/usr/bin\f[R] in this scenario.
-Please ensure that \f[C]fusermount\f[R]/\f[C]fusermount3\f[R] is present
+Since mounting requires the \f[V]fusermount\f[R] or
+\f[V]fusermount3\f[R] program, rclone will use the fallback PATH of
+\f[V]/bin:/usr/bin\f[R] in this scenario.
+Please ensure that \f[V]fusermount\f[R]/\f[V]fusermount3\f[R] is present
 on this PATH.
 .SS Rclone as Unix mount helper
 .PP
-The core Unix program \f[C]/bin/mount\f[R] normally takes the
-\f[C]-t FSTYPE\f[R] argument then runs the \f[C]/sbin/mount.FSTYPE\f[R]
-helper program passing it mount options as \f[C]-o key=val,...\f[R] or
-\f[C]--opt=...\f[R].
+The core Unix program \f[V]/bin/mount\f[R] normally takes the
+\f[V]-t FSTYPE\f[R] argument then runs the \f[V]/sbin/mount.FSTYPE\f[R]
+helper program passing it mount options as \f[V]-o key=val,...\f[R] or
+\f[V]--opt=...\f[R].
 Automount (classic or systemd) behaves in a similar way.
 .PP
-rclone by default expects GNU-style flags \f[C]--key val\f[R].
+rclone by default expects GNU-style flags \f[V]--key val\f[R].
 To run it as a mount helper you should symlink rclone binary to
-\f[C]/sbin/mount.rclone\f[R] and optionally \f[C]/usr/bin/rclonefs\f[R],
+\f[V]/sbin/mount.rclone\f[R] and optionally \f[V]/usr/bin/rclonefs\f[R],
 e.g.
-\f[C]ln -s /usr/bin/rclone /sbin/mount.rclone\f[R].
+\f[V]ln -s /usr/bin/rclone /sbin/mount.rclone\f[R].
 rclone will detect it and translate command-line arguments
 appropriately.
 .PP
@@ -8382,7 +8398,7 @@ WantedBy=multi-user.target
 \f[R]
 .fi
 .PP
-or add in \f[C]/etc/fstab\f[R] a line like
+or add in \f[V]/etc/fstab\f[R] a line like
 .IP
 .nf
 \f[C]
@@ -8391,11 +8407,11 @@ sftp1:subdir /mnt/data rclone rw,noauto,nofail,_netdev,x-systemd.automount,args2
 .fi
 .PP
 or use classic Automountd.
-Remember to provide explicit \f[C]config=...,cache-dir=...\f[R] as a
-workaround for mount units being run without \f[C]HOME\f[R].
+Remember to provide explicit \f[V]config=...,cache-dir=...\f[R] as a
+workaround for mount units being run without \f[V]HOME\f[R].
 .PP
-Rclone in the mount helper mode will split \f[C]-o\f[R] argument(s) by
-comma, replace \f[C]_\f[R] by \f[C]-\f[R] and prepend \f[C]--\f[R] to
+Rclone in the mount helper mode will split \f[V]-o\f[R] argument(s) by
+comma, replace \f[V]_\f[R] by \f[V]-\f[R] and prepend \f[V]--\f[R] to
 get the command-line flags.
 Options containing commas or spaces can be wrapped in single or double
 quotes.
@@ -8403,27 +8419,27 @@ Any inner quotes inside outer quotes of the same type should be doubled.
 .PP
 Mount option syntax includes a few extra options treated specially:
 .IP \[bu] 2
-\f[C]env.NAME=VALUE\f[R] will set an environment variable for the mount
+\f[V]env.NAME=VALUE\f[R] will set an environment variable for the mount
 process.
 This helps with Automountd and Systemd.mount which don\[aq]t allow
 setting custom environment for mount helpers.
-Typically you will use \f[C]env.HTTPS_PROXY=proxy.host:3128\f[R] or
-\f[C]env.HOME=/root\f[R]
+Typically you will use \f[V]env.HTTPS_PROXY=proxy.host:3128\f[R] or
+\f[V]env.HOME=/root\f[R]
 .IP \[bu] 2
-\f[C]command=cmount\f[R] can be used to run \f[C]cmount\f[R] or any
-other rclone command rather than the default \f[C]mount\f[R].
+\f[V]command=cmount\f[R] can be used to run \f[V]cmount\f[R] or any
+other rclone command rather than the default \f[V]mount\f[R].
 .IP \[bu] 2
-\f[C]args2env\f[R] will pass mount options to the mount helper running
+\f[V]args2env\f[R] will pass mount options to the mount helper running
 in background via environment variables instead of command line
 arguments.
-This allows to hide secrets from such commands as \f[C]ps\f[R] or
-\f[C]pgrep\f[R].
+This allows to hide secrets from such commands as \f[V]ps\f[R] or
+\f[V]pgrep\f[R].
 .IP \[bu] 2
-\f[C]vv...\f[R] will be transformed into appropriate
-\f[C]--verbose=N\f[R]
+\f[V]vv...\f[R] will be transformed into appropriate
+\f[V]--verbose=N\f[R]
 .IP \[bu] 2
-standard mount options like \f[C]x-systemd.automount\f[R],
-\f[C]_netdev\f[R], \f[C]nosuid\f[R] and alike are intended only for
+standard mount options like \f[V]x-systemd.automount\f[R],
+\f[V]_netdev\f[R], \f[V]nosuid\f[R] and alike are intended only for
 Automountd and ignored by rclone.
 .SS VFS - Virtual File System
 .PP
@@ -8441,7 +8457,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -8461,7 +8477,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -8490,7 +8506,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -8503,7 +8519,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -8530,37 +8546,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -8570,10 +8586,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -8636,15 +8652,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -8669,19 +8685,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -8706,50 +8722,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -8758,7 +8774,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -8783,10 +8799,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -8809,7 +8825,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -8838,7 +8854,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -8846,11 +8862,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -8860,9 +8876,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -8878,14 +8894,14 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
@@ -9055,20 +9071,20 @@ Run a command against a running rclone.
 .SS Synopsis
 .PP
 This runs a command against a running rclone.
-Use the \f[C]--url\f[R] flag to specify an non default URL to connect
+Use the \f[V]--url\f[R] flag to specify an non default URL to connect
 on.
 This can be either a \[dq]:port\[dq] which is taken to mean
 \[dq]http://localhost:port\[dq] or a \[dq]host:port\[dq] which is taken
 to mean \[dq]http://host:port\[dq]
 .PP
-A username and password can be passed in with \f[C]--user\f[R] and
-\f[C]--pass\f[R].
+A username and password can be passed in with \f[V]--user\f[R] and
+\f[V]--pass\f[R].
 .PP
-Note that \f[C]--rc-addr\f[R], \f[C]--rc-user\f[R], \f[C]--rc-pass\f[R]
-will be read also for \f[C]--url\f[R], \f[C]--user\f[R],
-\f[C]--pass\f[R].
+Note that \f[V]--rc-addr\f[R], \f[V]--rc-user\f[R], \f[V]--rc-pass\f[R]
+will be read also for \f[V]--url\f[R], \f[V]--user\f[R],
+\f[V]--pass\f[R].
 .PP
-The \f[C]--unix-socket\f[R] flag can be used to connect over a unix
+The \f[V]--unix-socket\f[R] flag can be used to connect over a unix
 socket like this
 .IP
 .nf
@@ -9084,13 +9100,13 @@ Arguments should be passed in as parameter=value.
 .PP
 The result will be returned as a JSON object by default.
 .PP
-The \f[C]--json\f[R] parameter can be used to pass in a JSON blob as an
+The \f[V]--json\f[R] parameter can be used to pass in a JSON blob as an
 input instead of key=value arguments.
 This is the only way of passing in more complicated values.
 .PP
-The \f[C]-o\f[R]/\f[C]--opt\f[R] option can be used to set a key
-\[dq]opt\[dq] with key, value options in the form \f[C]-o key=value\f[R]
-or \f[C]-o key\f[R].
+The \f[V]-o\f[R]/\f[V]--opt\f[R] option can be used to set a key
+\[dq]opt\[dq] with key, value options in the form \f[V]-o key=value\f[R]
+or \f[V]-o key\f[R].
 It can be repeated as many times as required.
 This is useful for rc commands which take the \[dq]opt\[dq] parameter
 which by convention is a dictionary of strings.
@@ -9109,7 +9125,7 @@ Will place this in the \[dq]opt\[dq] value
 \f[R]
 .fi
 .PP
-The \f[C]-a\f[R]/\f[C]--arg\f[R] option can be used to set strings in
+The \f[V]-a\f[R]/\f[V]--arg\f[R] option can be used to set strings in
 the \[dq]arg\[dq] value.
 It can be repeated as many times as required.
 This is useful for rc commands which take the \[dq]arg\[dq] parameter
@@ -9129,8 +9145,8 @@ Will place this in the \[dq]arg\[dq] value
 \f[R]
 .fi
 .PP
-Use \f[C]--loopback\f[R] to connect to the rclone instance running
-\f[C]rclone rc\f[R].
+Use \f[V]--loopback\f[R] to connect to the rclone instance running
+\f[V]rclone rc\f[R].
 This is very useful for testing commands without having to run an rclone
 rc server, e.g.:
 .IP
@@ -9140,7 +9156,7 @@ rclone rc --loopback operations/about fs=/
 \f[R]
 .fi
 .PP
-Use \f[C]rclone rc\f[R] to see a list of all possible commands.
+Use \f[V]rclone rc\f[R] to see a list of all possible commands.
 .IP
 .nf
 \f[C]
@@ -9191,7 +9207,7 @@ usually more efficient than the streaming/chunked upload endpoints,
 which use multiple requests.
 Exact behaviour depends on the remote.
 What is considered a small file may be set through
-\f[C]--streaming-upload-cutoff\f[R].
+\f[V]--streaming-upload-cutoff\f[R].
 Uploading only starts after the cutoff is reached or if the file ends
 before that.
 The data must fit into RAM.
@@ -9200,19 +9216,19 @@ please see there.
 Generally speaking, setting this cutoff too high will decrease your
 performance.
 .PP
-Use the \f[C]--size\f[R] flag to preallocate the file in advance at the
+Use the \f[V]--size\f[R] flag to preallocate the file in advance at the
 remote end and actually stream it, even if remote backend doesn\[aq]t
 support streaming.
 .PP
-\f[C]--size\f[R] should be the exact size of the input stream in bytes.
-If the size of the stream is different in length to the \f[C]--size\f[R]
+\f[V]--size\f[R] should be the exact size of the input stream in bytes.
+If the size of the stream is different in length to the \f[V]--size\f[R]
 passed in then the transfer will likely fail.
 .PP
 Note that the upload cannot be retried because the data is not stored.
 If the backend supports multipart uploading then individual chunks can
 be retried.
 If you need to transfer a lot of data, you may be better off caching it
-locally and then \f[C]rclone move\f[R] it to the destination which can
+locally and then \f[V]rclone move\f[R] it to the destination which can
 use retries.
 .IP
 .nf
@@ -9264,59 +9280,59 @@ See the rc documentation (https://rclone.org/rc/) for more info on the
 rc flags.
 .SS Server options
 .PP
-Use \f[C]--rc-addr\f[R] to specify which IP address and port the server
-should listen on, eg \f[C]--rc-addr 1.2.3.4:8000\f[R] or
-\f[C]--rc-addr :8080\f[R] to listen to all IPs.
+Use \f[V]--rc-addr\f[R] to specify which IP address and port the server
+should listen on, eg \f[V]--rc-addr 1.2.3.4:8000\f[R] or
+\f[V]--rc-addr :8080\f[R] to listen to all IPs.
 By default it only listens on localhost.
 You can use port :0 to let the OS choose an available port.
 .PP
-If you set \f[C]--rc-addr\f[R] to listen on a public or LAN accessible
+If you set \f[V]--rc-addr\f[R] to listen on a public or LAN accessible
 IP address then using Authentication is advised - see the next section
 for info.
 .PP
 You can use a unix socket by setting the url to
-\f[C]unix:///path/to/socket\f[R] or just by using an absolute path name.
+\f[V]unix:///path/to/socket\f[R] or just by using an absolute path name.
 Note that unix sockets bypass the authentication - this is expected to
 be done with file system permissions.
 .PP
-\f[C]--rc-addr\f[R] may be repeated to listen on multiple
+\f[V]--rc-addr\f[R] may be repeated to listen on multiple
 IPs/ports/sockets.
 Socket activation, described further below, can also be used to
 accomplish the same.
 .PP
-\f[C]--rc-server-read-timeout\f[R] and
-\f[C]--rc-server-write-timeout\f[R] can be used to control the timeouts
+\f[V]--rc-server-read-timeout\f[R] and
+\f[V]--rc-server-write-timeout\f[R] can be used to control the timeouts
 on the server.
 Note that this is the total time for a transfer.
 .PP
-\f[C]--rc-max-header-bytes\f[R] controls the maximum number of bytes the
+\f[V]--rc-max-header-bytes\f[R] controls the maximum number of bytes the
 server will accept in the HTTP header.
 .PP
-\f[C]--rc-baseurl\f[R] controls the URL prefix that rclone serves from.
+\f[V]--rc-baseurl\f[R] controls the URL prefix that rclone serves from.
 By default rclone will serve from the root.
-If you used \f[C]--rc-baseurl \[dq]/rclone\[dq]\f[R] then rclone would
+If you used \f[V]--rc-baseurl \[dq]/rclone\[dq]\f[R] then rclone would
 serve from a URL starting with \[dq]/rclone/\[dq].
 This is useful if you wish to proxy rclone serve.
 Rclone automatically inserts leading and trailing \[dq]/\[dq] on
-\f[C]--rc-baseurl\f[R], so \f[C]--rc-baseurl \[dq]rclone\[dq]\f[R],
-\f[C]--rc-baseurl \[dq]/rclone\[dq]\f[R] and
-\f[C]--rc-baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
+\f[V]--rc-baseurl\f[R], so \f[V]--rc-baseurl \[dq]rclone\[dq]\f[R],
+\f[V]--rc-baseurl \[dq]/rclone\[dq]\f[R] and
+\f[V]--rc-baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
 .SS TLS (SSL)
 .PP
 By default this will serve over http.
 If you want you can serve over https.
-You will need to supply the \f[C]--rc-cert\f[R] and \f[C]--rc-key\f[R]
+You will need to supply the \f[V]--rc-cert\f[R] and \f[V]--rc-key\f[R]
 flags.
 If you wish to do client side certificate validation then you will need
-to supply \f[C]--rc-client-ca\f[R] also.
+to supply \f[V]--rc-client-ca\f[R] also.
 .PP
-\f[C]--rc-cert\f[R] should be a either a PEM encoded certificate or a
+\f[V]--rc-cert\f[R] should be a either a PEM encoded certificate or a
 concatenation of that with the CA certificate.
-\f[C]--krc-ey\f[R] should be the PEM encoded private key and
-\f[C]--rc-client-ca\f[R] should be the PEM encoded client certificate
+\f[V]--krc-ey\f[R] should be the PEM encoded private key and
+\f[V]--rc-client-ca\f[R] should be the PEM encoded client certificate
 authority certificate.
 .PP
-\f[C]--rc-min-tls-version\f[R] is minimum TLS version that is
+\f[V]--rc-min-tls-version\f[R] is minimum TLS version that is
 acceptable.
 Valid values are \[dq]tls1.0\[dq], \[dq]tls1.1\[dq], \[dq]tls1.2\[dq]
 and \[dq]tls1.3\[dq] (default \[dq]tls1.0\[dq]).
@@ -9332,7 +9348,7 @@ in
 https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html
 .PP
 Socket activation can be tested ad-hoc with the
-\f[C]systemd-socket-activate\f[R]command
+\f[V]systemd-socket-activate\f[R]command
 .IP
 .nf
 \f[C]
@@ -9344,7 +9360,7 @@ This will socket-activate rclone on the first connection to port 8000
 over TCP.
 ### Template
 .PP
-\f[C]--rc-template\f[R] allows a user to specify a custom markup
+\f[V]--rc-template\f[R] allows a user to specify a custom markup
 template for HTTP and WebDAV serve functions.
 The server exports the following markup to be used within the template
 to server pages:
@@ -9481,15 +9497,15 @@ T}
 By default this will serve files without needing a login.
 .PP
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the \f[C]--rc-user\f[R] and
-\f[C]--rc-pass\f[R] flags.
+a single username and password with the \f[V]--rc-user\f[R] and
+\f[V]--rc-pass\f[R] flags.
 .PP
 If no static users are configured by either of the above methods, and
-client certificates are required by the \f[C]--client-ca\f[R] flag
+client certificates are required by the \f[V]--client-ca\f[R] flag
 passed to the server, the client certificate common name will be
 considered as the username.
 .PP
-Use \f[C]--rc-htpasswd /path/to/htpasswd\f[R] to provide an htpasswd
+Use \f[V]--rc-htpasswd /path/to/htpasswd\f[R] to provide an htpasswd
 file.
 This is in standard apache format and supports MD5, SHA1 and BCrypt for
 basic authentication.
@@ -9507,9 +9523,9 @@ htpasswd -B htpasswd anotherUser
 .PP
 The password file can be updated while rclone is running.
 .PP
-Use \f[C]--rc-realm\f[R] to set the authentication realm.
+Use \f[V]--rc-realm\f[R] to set the authentication realm.
 .PP
-Use \f[C]--rc-salt\f[R] to change the password hashing salt from the
+Use \f[V]--rc-salt\f[R] to change the password hashing salt from the
 default.
 .IP
 .nf
@@ -9577,7 +9593,7 @@ Remove empty directories under the path.
 This recursively removes any empty directories (including directories
 that only contain empty directories), that it finds under the path.
 The root path itself will also be removed if it is empty, unless you
-supply the \f[C]--leave-root\f[R] flag.
+supply the \f[V]--leave-root\f[R] flag.
 .PP
 Use command rmdir (https://rclone.org/commands/rclone_rmdir/) to delete
 just the empty directory given by path, not recurse.
@@ -9586,9 +9602,9 @@ This is useful for tidying up remotes that rclone has left a lot of
 empty directories in.
 For example the delete (https://rclone.org/commands/rclone_delete/)
 command will delete files but leave the directory structure (unless used
-with option \f[C]--rmdirs\f[R]).
+with option \f[V]--rmdirs\f[R]).
 .PP
-This will delete \f[C]--checkers\f[R] directories concurrently so if you
+This will delete \f[V]--checkers\f[R] directories concurrently so if you
 have thousands of empty directories consider increasing this number.
 .PP
 To delete a path and any objects in it, use the
@@ -9637,52 +9653,52 @@ The download is verified with a hashsum and cryptographically signed
 signature; see the release signing
 docs (https://rclone.org/release_signing/) for details.
 .PP
-If used without flags (or with implied \f[C]--stable\f[R] flag), this
+If used without flags (or with implied \f[V]--stable\f[R] flag), this
 command will install the latest stable release.
 However, some issues may be fixed (or features added) only in the latest
 beta release.
-In such cases you should run the command with the \f[C]--beta\f[R] flag,
+In such cases you should run the command with the \f[V]--beta\f[R] flag,
 i.e.
-\f[C]rclone selfupdate --beta\f[R].
+\f[V]rclone selfupdate --beta\f[R].
 You can check in advance what version would be installed by adding the
-\f[C]--check\f[R] flag, then repeat the command without it when you are
+\f[V]--check\f[R] flag, then repeat the command without it when you are
 satisfied.
 .PP
 Sometimes the rclone team may recommend you a concrete beta or stable
 rclone release to troubleshoot your issue or add a bleeding edge
 feature.
-The \f[C]--version VER\f[R] flag, if given, will update to the concrete
+The \f[V]--version VER\f[R] flag, if given, will update to the concrete
 version instead of the latest one.
-If you omit micro version from \f[C]VER\f[R] (for example
-\f[C]1.53\f[R]), the latest matching micro version will be used.
+If you omit micro version from \f[V]VER\f[R] (for example
+\f[V]1.53\f[R]), the latest matching micro version will be used.
 .PP
 Upon successful update rclone will print a message that contains a
 previous version number.
 You will need it if you later decide to revert your update for some
 reason.
 Then you\[aq]ll have to note the previous version and run the following
-command: \f[C]rclone selfupdate [--beta] OLDVER\f[R].
+command: \f[V]rclone selfupdate [--beta] OLDVER\f[R].
 If the old version contains only dots and digits (for example
-\f[C]v1.54.0\f[R]) then it\[aq]s a stable release so you won\[aq]t need
-the \f[C]--beta\f[R] flag.
+\f[V]v1.54.0\f[R]) then it\[aq]s a stable release so you won\[aq]t need
+the \f[V]--beta\f[R] flag.
 Beta releases have an additional information similar to
-\f[C]v1.54.0-beta.5111.06f1c0c61\f[R].
+\f[V]v1.54.0-beta.5111.06f1c0c61\f[R].
 (if you are a developer and use a locally built rclone, the version
-number will end with \f[C]-DEV\f[R], you will have to rebuild it as it
+number will end with \f[V]-DEV\f[R], you will have to rebuild it as it
 obviously can\[aq]t be distributed).
 .PP
 If you previously installed rclone via a package manager, the package
 may include local documentation or configure services.
-You may wish to update with the flag \f[C]--package deb\f[R] or
-\f[C]--package rpm\f[R] (whichever is correct for your OS) to update
+You may wish to update with the flag \f[V]--package deb\f[R] or
+\f[V]--package rpm\f[R] (whichever is correct for your OS) to update
 these too.
-This command with the default \f[C]--package zip\f[R] will update only
+This command with the default \f[V]--package zip\f[R] will update only
 the rclone executable so the local manual may become inaccurate after
 it.
 .PP
 The rclone mount (https://rclone.org/commands/rclone_mount/) command may
 or may not support extended FUSE options depending on the build and OS.
-\f[C]selfupdate\f[R] will refuse to update if the capability would be
+\f[V]selfupdate\f[R] will refuse to update if the capability would be
 discarded.
 .PP
 Note: Windows forbids deletion of a currently running executable so this
@@ -9692,7 +9708,7 @@ success.
 Please note that this command was not available before rclone version
 1.55.
 If it fails for you with the message
-\f[C]unknown command \[dq]selfupdate\[dq]\f[R] then you will need to
+\f[V]unknown command \[dq]selfupdate\[dq]\f[R] then you will need to
 update manually following the install instructions located at
 https://rclone.org/install/
 .IP
@@ -9807,15 +9823,15 @@ either in the same directory as the video, or in a \[dq]Subs\[dq]
 subdirectory.
 .SS Server options
 .PP
-Use \f[C]--addr\f[R] to specify which IP address and port the server
+Use \f[V]--addr\f[R] to specify which IP address and port the server
 should listen on, e.g.
-\f[C]--addr 1.2.3.4:8000\f[R] or \f[C]--addr :8080\f[R] to listen to all
+\f[V]--addr 1.2.3.4:8000\f[R] or \f[V]--addr :8080\f[R] to listen to all
 IPs.
 .PP
-Use \f[C]--name\f[R] to choose the friendly server name, which is by
+Use \f[V]--name\f[R] to choose the friendly server name, which is by
 default \[dq]rclone (hostname)\[dq].
 .PP
-Use \f[C]--log-trace\f[R] in conjunction with \f[C]-vv\f[R] to enable
+Use \f[V]--log-trace\f[R] in conjunction with \f[V]-vv\f[R] to enable
 additional debug logging of all UPNP traffic.
 .SS VFS - Virtual File System
 .PP
@@ -9833,7 +9849,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -9853,7 +9869,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -9882,7 +9898,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -9895,7 +9911,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -9922,37 +9938,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -9962,10 +9978,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -10028,15 +10044,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -10061,19 +10077,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -10098,50 +10114,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -10150,7 +10166,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -10175,10 +10191,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -10201,7 +10217,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -10230,7 +10246,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -10238,11 +10254,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -10252,9 +10268,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -10270,14 +10286,14 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
@@ -10391,19 +10407,19 @@ sudo rclone serve docker --base-dir /tmp/rclone-volumes --socket-addr localhost:
 \f[R]
 .fi
 .PP
-Running \f[C]rclone serve docker\f[R] will create the said socket,
+Running \f[V]rclone serve docker\f[R] will create the said socket,
 listening for commands from Docker to create the necessary Volumes.
-Normally you need not give the \f[C]--socket-addr\f[R] flag.
+Normally you need not give the \f[V]--socket-addr\f[R] flag.
 The API will listen on the unix domain socket at
-\f[C]/run/docker/plugins/rclone.sock\f[R].
+\f[V]/run/docker/plugins/rclone.sock\f[R].
 In the example above rclone will create a TCP socket and a small file
-\f[C]/etc/docker/plugins/rclone.spec\f[R] containing the socket address.
-We use \f[C]sudo\f[R] because both paths are writeable only by the root
+\f[V]/etc/docker/plugins/rclone.spec\f[R] containing the socket address.
+We use \f[V]sudo\f[R] because both paths are writeable only by the root
 user.
 .PP
 If you later decide to change listening socket, the docker daemon must
-be restarted to reconnect to \f[C]/run/docker/plugins/rclone.sock\f[R]
-or parse new \f[C]/etc/docker/plugins/rclone.spec\f[R].
+be restarted to reconnect to \f[V]/run/docker/plugins/rclone.sock\f[R]
+or parse new \f[V]/etc/docker/plugins/rclone.spec\f[R].
 Until you restart, any volume related docker commands will timeout
 trying to access the old socket.
 Running directly is supported on \f[B]Linux only\f[R], not on Windows or
@@ -10412,9 +10428,9 @@ This is not a problem with managed plugin mode described in details in
 the full documentation (https://rclone.org/docker).
 .PP
 The command will create volume mounts under the path given by
-\f[C]--base-dir\f[R] (by default
-\f[C]/var/lib/docker-volumes/rclone\f[R] available only to root) and
-maintain the JSON formatted file \f[C]docker-plugin.state\f[R] in the
+\f[V]--base-dir\f[R] (by default
+\f[V]/var/lib/docker-volumes/rclone\f[R] available only to root) and
+maintain the JSON formatted file \f[V]docker-plugin.state\f[R] in the
 rclone cache directory with book-keeping records of created and mounted
 volumes.
 .PP
@@ -10437,7 +10453,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -10457,7 +10473,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -10486,7 +10502,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -10499,7 +10515,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -10526,37 +10542,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -10566,10 +10582,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -10632,15 +10648,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -10665,19 +10681,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -10702,50 +10718,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -10754,7 +10770,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -10779,10 +10795,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -10805,7 +10821,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -10834,7 +10850,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -10842,11 +10858,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -10856,9 +10872,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -10874,14 +10890,14 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
@@ -11032,7 +11048,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -11052,7 +11068,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -11081,7 +11097,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -11094,7 +11110,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -11121,37 +11137,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -11161,10 +11177,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -11227,15 +11243,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -11260,19 +11276,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -11297,50 +11313,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -11349,7 +11365,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -11374,10 +11390,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -11400,7 +11416,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -11429,7 +11445,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -11437,11 +11453,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -11451,9 +11467,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -11469,36 +11485,36 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
 Use it as a last resort and only with caching.
 .SS Auth Proxy
 .PP
-If you supply the parameter \f[C]--auth-proxy /path/to/program\f[R] then
+If you supply the parameter \f[V]--auth-proxy /path/to/program\f[R] then
 rclone will use that program to generate backends on the fly which then
 are used to authenticate incoming requests.
 This uses a simple JSON based protocol with input on STDIN and output on
 STDOUT.
 .PP
-\f[B]PLEASE NOTE:\f[R] \f[C]--auth-proxy\f[R] and
-\f[C]--authorized-keys\f[R] cannot be used together, if
-\f[C]--auth-proxy\f[R] is set the authorized keys option will be
+\f[B]PLEASE NOTE:\f[R] \f[V]--auth-proxy\f[R] and
+\f[V]--authorized-keys\f[R] cannot be used together, if
+\f[V]--auth-proxy\f[R] is set the authorized keys option will be
 ignored.
 .PP
 There is an example program
 bin/test_proxy.py (https://github.com/rclone/rclone/blob/master/bin/test_proxy.py)
 in the rclone source code.
 .PP
-The program\[aq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] on
+The program\[aq]s job is to take a \f[V]user\f[R] and \f[V]pass\f[R] on
 the input and turn those into the config for a backend on STDOUT in JSON
 format.
 This config will have any default parameters for the backend added, but
@@ -11506,10 +11522,10 @@ it won\[aq]t use configuration from environment variables or command
 line options - it is the job of the proxy program to make a complete
 config.
 .PP
-This config generated must have this extra parameter - \f[C]_root\f[R] -
+This config generated must have this extra parameter - \f[V]_root\f[R] -
 root to use for the backend
 .PP
-And it may have this parameter - \f[C]_obscure\f[R] - comma separated
+And it may have this parameter - \f[V]_obscure\f[R] - comma separated
 strings for parameters to obscure
 .PP
 If password authentication was used by the client, input to the proxy
@@ -11552,22 +11568,22 @@ And as an example return this on STDOUT
 .fi
 .PP
 This would mean that an SFTP backend would be created on the fly for the
-\f[C]user\f[R] and \f[C]pass\f[R]/\f[C]public_key\f[R] returned in the
+\f[V]user\f[R] and \f[V]pass\f[R]/\f[V]public_key\f[R] returned in the
 output to the host given.
-Note that since \f[C]_obscure\f[R] is set to \f[C]pass\f[R], rclone will
-obscure the \f[C]pass\f[R] parameter before creating the backend (which
+Note that since \f[V]_obscure\f[R] is set to \f[V]pass\f[R], rclone will
+obscure the \f[V]pass\f[R] parameter before creating the backend (which
 is required for sftp backends).
 .PP
-The program can manipulate the supplied \f[C]user\f[R] in any way, for
+The program can manipulate the supplied \f[V]user\f[R] in any way, for
 example to make proxy to many different sftp backends, you could make
-the \f[C]user\f[R] be \f[C]user\[at]example.com\f[R] and then set the
-\f[C]host\f[R] to \f[C]example.com\f[R] in the output and the user to
-\f[C]user\f[R].
-For security you\[aq]d probably want to restrict the \f[C]host\f[R] to a
+the \f[V]user\f[R] be \f[V]user\[at]example.com\f[R] and then set the
+\f[V]host\f[R] to \f[V]example.com\f[R] in the output and the user to
+\f[V]user\f[R].
+For security you\[aq]d probably want to restrict the \f[V]host\f[R] to a
 limited list.
 .PP
-Note that an internal cache is keyed on \f[C]user\f[R] so only use that
-for configuration, don\[aq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
+Note that an internal cache is keyed on \f[V]user\f[R] so only use that
+for configuration, don\[aq]t use \f[V]pass\f[R] or \f[V]public_key\f[R].
 This also means that if a user\[aq]s password or public-key is changed
 the cache will need to expire (which takes 5 mins) before it takes
 effect.
@@ -11672,66 +11688,66 @@ This can be viewed in a web browser or you can make a remote of type
 http read from it.
 .PP
 You can use the filter flags (e.g.
-\f[C]--include\f[R], \f[C]--exclude\f[R]) to control what is served.
+\f[V]--include\f[R], \f[V]--exclude\f[R]) to control what is served.
 .PP
 The server will log errors.
-Use \f[C]-v\f[R] to see access logs.
+Use \f[V]-v\f[R] to see access logs.
 .PP
-\f[C]--bwlimit\f[R] will be respected for file transfers.
-Use \f[C]--stats\f[R] to control the stats printing.
+\f[V]--bwlimit\f[R] will be respected for file transfers.
+Use \f[V]--stats\f[R] to control the stats printing.
 .SS Server options
 .PP
-Use \f[C]--addr\f[R] to specify which IP address and port the server
-should listen on, eg \f[C]--addr 1.2.3.4:8000\f[R] or
-\f[C]--addr :8080\f[R] to listen to all IPs.
+Use \f[V]--addr\f[R] to specify which IP address and port the server
+should listen on, eg \f[V]--addr 1.2.3.4:8000\f[R] or
+\f[V]--addr :8080\f[R] to listen to all IPs.
 By default it only listens on localhost.
 You can use port :0 to let the OS choose an available port.
 .PP
-If you set \f[C]--addr\f[R] to listen on a public or LAN accessible IP
+If you set \f[V]--addr\f[R] to listen on a public or LAN accessible IP
 address then using Authentication is advised - see the next section for
 info.
 .PP
 You can use a unix socket by setting the url to
-\f[C]unix:///path/to/socket\f[R] or just by using an absolute path name.
+\f[V]unix:///path/to/socket\f[R] or just by using an absolute path name.
 Note that unix sockets bypass the authentication - this is expected to
 be done with file system permissions.
 .PP
-\f[C]--addr\f[R] may be repeated to listen on multiple
+\f[V]--addr\f[R] may be repeated to listen on multiple
 IPs/ports/sockets.
 Socket activation, described further below, can also be used to
 accomplish the same.
 .PP
-\f[C]--server-read-timeout\f[R] and \f[C]--server-write-timeout\f[R] can
+\f[V]--server-read-timeout\f[R] and \f[V]--server-write-timeout\f[R] can
 be used to control the timeouts on the server.
 Note that this is the total time for a transfer.
 .PP
-\f[C]--max-header-bytes\f[R] controls the maximum number of bytes the
+\f[V]--max-header-bytes\f[R] controls the maximum number of bytes the
 server will accept in the HTTP header.
 .PP
-\f[C]--baseurl\f[R] controls the URL prefix that rclone serves from.
+\f[V]--baseurl\f[R] controls the URL prefix that rclone serves from.
 By default rclone will serve from the root.
-If you used \f[C]--baseurl \[dq]/rclone\[dq]\f[R] then rclone would
+If you used \f[V]--baseurl \[dq]/rclone\[dq]\f[R] then rclone would
 serve from a URL starting with \[dq]/rclone/\[dq].
 This is useful if you wish to proxy rclone serve.
 Rclone automatically inserts leading and trailing \[dq]/\[dq] on
-\f[C]--baseurl\f[R], so \f[C]--baseurl \[dq]rclone\[dq]\f[R],
-\f[C]--baseurl \[dq]/rclone\[dq]\f[R] and
-\f[C]--baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
+\f[V]--baseurl\f[R], so \f[V]--baseurl \[dq]rclone\[dq]\f[R],
+\f[V]--baseurl \[dq]/rclone\[dq]\f[R] and
+\f[V]--baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
 .SS TLS (SSL)
 .PP
 By default this will serve over http.
 If you want you can serve over https.
-You will need to supply the \f[C]--cert\f[R] and \f[C]--key\f[R] flags.
+You will need to supply the \f[V]--cert\f[R] and \f[V]--key\f[R] flags.
 If you wish to do client side certificate validation then you will need
-to supply \f[C]--client-ca\f[R] also.
+to supply \f[V]--client-ca\f[R] also.
 .PP
-\f[C]--cert\f[R] should be a either a PEM encoded certificate or a
+\f[V]--cert\f[R] should be a either a PEM encoded certificate or a
 concatenation of that with the CA certificate.
-\f[C]--key\f[R] should be the PEM encoded private key and
-\f[C]--client-ca\f[R] should be the PEM encoded client certificate
+\f[V]--key\f[R] should be the PEM encoded private key and
+\f[V]--client-ca\f[R] should be the PEM encoded client certificate
 authority certificate.
 .PP
-\f[C]--min-tls-version\f[R] is minimum TLS version that is acceptable.
+\f[V]--min-tls-version\f[R] is minimum TLS version that is acceptable.
 Valid values are \[dq]tls1.0\[dq], \[dq]tls1.1\[dq], \[dq]tls1.2\[dq]
 and \[dq]tls1.3\[dq] (default \[dq]tls1.0\[dq]).
 .SS Socket activation
@@ -11746,7 +11762,7 @@ in
 https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html
 .PP
 Socket activation can be tested ad-hoc with the
-\f[C]systemd-socket-activate\f[R]command
+\f[V]systemd-socket-activate\f[R]command
 .IP
 .nf
 \f[C]
@@ -11758,7 +11774,7 @@ This will socket-activate rclone on the first connection to port 8000
 over TCP.
 ### Template
 .PP
-\f[C]--template\f[R] allows a user to specify a custom markup template
+\f[V]--template\f[R] allows a user to specify a custom markup template
 for HTTP and WebDAV serve functions.
 The server exports the following markup to be used within the template
 to server pages:
@@ -11895,15 +11911,15 @@ T}
 By default this will serve files without needing a login.
 .PP
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the \f[C]--user\f[R] and
-\f[C]--pass\f[R] flags.
+a single username and password with the \f[V]--user\f[R] and
+\f[V]--pass\f[R] flags.
 .PP
 If no static users are configured by either of the above methods, and
-client certificates are required by the \f[C]--client-ca\f[R] flag
+client certificates are required by the \f[V]--client-ca\f[R] flag
 passed to the server, the client certificate common name will be
 considered as the username.
 .PP
-Use \f[C]--htpasswd /path/to/htpasswd\f[R] to provide an htpasswd file.
+Use \f[V]--htpasswd /path/to/htpasswd\f[R] to provide an htpasswd file.
 This is in standard apache format and supports MD5, SHA1 and BCrypt for
 basic authentication.
 Bcrypt is recommended.
@@ -11920,9 +11936,9 @@ htpasswd -B htpasswd anotherUser
 .PP
 The password file can be updated while rclone is running.
 .PP
-Use \f[C]--realm\f[R] to set the authentication realm.
+Use \f[V]--realm\f[R] to set the authentication realm.
 .PP
-Use \f[C]--salt\f[R] to change the password hashing salt from the
+Use \f[V]--salt\f[R] to change the password hashing salt from the
 default.
 .SS VFS - Virtual File System
 .PP
@@ -11940,7 +11956,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -11960,7 +11976,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -11989,7 +12005,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -12002,7 +12018,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -12029,37 +12045,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -12069,10 +12085,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -12135,15 +12151,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -12168,19 +12184,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -12205,50 +12221,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -12257,7 +12273,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -12282,10 +12298,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -12308,7 +12324,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -12337,7 +12353,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -12345,11 +12361,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -12359,9 +12375,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -12377,36 +12393,36 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
 Use it as a last resort and only with caching.
 .SS Auth Proxy
 .PP
-If you supply the parameter \f[C]--auth-proxy /path/to/program\f[R] then
+If you supply the parameter \f[V]--auth-proxy /path/to/program\f[R] then
 rclone will use that program to generate backends on the fly which then
 are used to authenticate incoming requests.
 This uses a simple JSON based protocol with input on STDIN and output on
 STDOUT.
 .PP
-\f[B]PLEASE NOTE:\f[R] \f[C]--auth-proxy\f[R] and
-\f[C]--authorized-keys\f[R] cannot be used together, if
-\f[C]--auth-proxy\f[R] is set the authorized keys option will be
+\f[B]PLEASE NOTE:\f[R] \f[V]--auth-proxy\f[R] and
+\f[V]--authorized-keys\f[R] cannot be used together, if
+\f[V]--auth-proxy\f[R] is set the authorized keys option will be
 ignored.
 .PP
 There is an example program
 bin/test_proxy.py (https://github.com/rclone/rclone/blob/master/bin/test_proxy.py)
 in the rclone source code.
 .PP
-The program\[aq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] on
+The program\[aq]s job is to take a \f[V]user\f[R] and \f[V]pass\f[R] on
 the input and turn those into the config for a backend on STDOUT in JSON
 format.
 This config will have any default parameters for the backend added, but
@@ -12414,10 +12430,10 @@ it won\[aq]t use configuration from environment variables or command
 line options - it is the job of the proxy program to make a complete
 config.
 .PP
-This config generated must have this extra parameter - \f[C]_root\f[R] -
+This config generated must have this extra parameter - \f[V]_root\f[R] -
 root to use for the backend
 .PP
-And it may have this parameter - \f[C]_obscure\f[R] - comma separated
+And it may have this parameter - \f[V]_obscure\f[R] - comma separated
 strings for parameters to obscure
 .PP
 If password authentication was used by the client, input to the proxy
@@ -12460,22 +12476,22 @@ And as an example return this on STDOUT
 .fi
 .PP
 This would mean that an SFTP backend would be created on the fly for the
-\f[C]user\f[R] and \f[C]pass\f[R]/\f[C]public_key\f[R] returned in the
+\f[V]user\f[R] and \f[V]pass\f[R]/\f[V]public_key\f[R] returned in the
 output to the host given.
-Note that since \f[C]_obscure\f[R] is set to \f[C]pass\f[R], rclone will
-obscure the \f[C]pass\f[R] parameter before creating the backend (which
+Note that since \f[V]_obscure\f[R] is set to \f[V]pass\f[R], rclone will
+obscure the \f[V]pass\f[R] parameter before creating the backend (which
 is required for sftp backends).
 .PP
-The program can manipulate the supplied \f[C]user\f[R] in any way, for
+The program can manipulate the supplied \f[V]user\f[R] in any way, for
 example to make proxy to many different sftp backends, you could make
-the \f[C]user\f[R] be \f[C]user\[at]example.com\f[R] and then set the
-\f[C]host\f[R] to \f[C]example.com\f[R] in the output and the user to
-\f[C]user\f[R].
-For security you\[aq]d probably want to restrict the \f[C]host\f[R] to a
+the \f[V]user\f[R] be \f[V]user\[at]example.com\f[R] and then set the
+\f[V]host\f[R] to \f[V]example.com\f[R] in the output and the user to
+\f[V]user\f[R].
+For security you\[aq]d probably want to restrict the \f[V]host\f[R] to a
 limited list.
 .PP
-Note that an internal cache is keyed on \f[C]user\f[R] so only use that
-for configuration, don\[aq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
+Note that an internal cache is keyed on \f[V]user\f[R] so only use that
+for configuration, don\[aq]t use \f[V]pass\f[R] or \f[V]public_key\f[R].
 This also means that if a user\[aq]s password or public-key is changed
 the cache will need to expire (which takes 5 mins) before it takes
 effect.
@@ -12594,7 +12610,7 @@ versions where installing FUSE is very cumbersome.
 .PP
 This server does not implement any authentication so any client will be
 able to access the data.
-To limit access, you can use \f[C]serve nfs\f[R] on the loopback address
+To limit access, you can use \f[V]serve nfs\f[R] on the loopback address
 or rely on secure tunnels (such as SSH) or use firewalling.
 .PP
 For this reason, by default, a random TCP port is chosen and the
@@ -12602,31 +12618,31 @@ loopback interface is used for the listening address by default; meaning
 that it is only available to the local machine.
 If you want other machines to access the NFS mount over local network,
 you need to specify the listening address and port using the
-\f[C]--addr\f[R] flag.
+\f[V]--addr\f[R] flag.
 .PP
 Modifying files through the NFS protocol requires VFS caching.
-Usually you will need to specify \f[C]--vfs-cache-mode\f[R] in order to
-be able to write to the mountpoint (\f[C]full\f[R] is recommended).
+Usually you will need to specify \f[V]--vfs-cache-mode\f[R] in order to
+be able to write to the mountpoint (\f[V]full\f[R] is recommended).
 If you don\[aq]t specify VFS cache mode, the mount will be read-only.
 .PP
-\f[C]--nfs-cache-type\f[R] controls the type of the NFS handle cache.
-By default this is \f[C]memory\f[R] where new handles will be randomly
+\f[V]--nfs-cache-type\f[R] controls the type of the NFS handle cache.
+By default this is \f[V]memory\f[R] where new handles will be randomly
 allocated when needed.
 These are stored in memory.
 If the server is restarted the handle cache will be lost and connected
 NFS clients will get stale handle errors.
 .PP
-\f[C]--nfs-cache-type disk\f[R] uses an on disk NFS handle cache.
+\f[V]--nfs-cache-type disk\f[R] uses an on disk NFS handle cache.
 Rclone hashes the path of the object and stores it in a file named after
 the hash.
 These hashes are stored on disk the directory controlled by
-\f[C]--cache-dir\f[R] or the exact directory may be specified with
-\f[C]--nfs-cache-dir\f[R].
+\f[V]--cache-dir\f[R] or the exact directory may be specified with
+\f[V]--nfs-cache-dir\f[R].
 Using this means that the NFS server can be restarted at will without
 affecting the connected clients.
 .PP
-\f[C]--nfs-cache-type symlink\f[R] is similar to
-\f[C]--nfs-cache-type disk\f[R] in that it uses an on disk cache, but
+\f[V]--nfs-cache-type symlink\f[R] is similar to
+\f[V]--nfs-cache-type disk\f[R] in that it uses an on disk cache, but
 the cache entries are held as symlinks.
 Rclone will use the handle of the underlying file as the NFS handle
 which improves performance.
@@ -12634,13 +12650,13 @@ This sort of cache can\[aq]t be backed up and restored as the underlying
 handles will change.
 This is Linux only.
 .PP
-\f[C]--nfs-cache-handle-limit\f[R] controls the maximum number of cached
+\f[V]--nfs-cache-handle-limit\f[R] controls the maximum number of cached
 NFS handles stored by the caching handler.
 This should not be set too low or you may experience errors when trying
 to access files.
-The default is \f[C]1000000\f[R], but consider lowering this limit if
+The default is \f[V]1000000\f[R], but consider lowering this limit if
 the server\[aq]s system resource usage causes problems.
-This is only used by the \f[C]memory\f[R] type cache.
+This is only used by the \f[V]memory\f[R] type cache.
 .PP
 To serve NFS over the network use following command:
 .IP
@@ -12659,9 +12675,9 @@ mount -t nfs -o port=$PORT,mountport=$PORT,tcp $HOSTNAME:/ path/to/mountpoint
 \f[R]
 .fi
 .PP
-Where \f[C]$PORT\f[R] is the same port number used in the
-\f[C]serve nfs\f[R] command and \f[C]$HOSTNAME\f[R] is the network
-address of the machine that \f[C]serve nfs\f[R] was run on.
+Where \f[V]$PORT\f[R] is the same port number used in the
+\f[V]serve nfs\f[R] command and \f[V]$HOSTNAME\f[R] is the network
+address of the machine that \f[V]serve nfs\f[R] was run on.
 .PP
 This command is only available on Unix platforms.
 .SS VFS - Virtual File System
@@ -12680,7 +12696,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -12700,7 +12716,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -12729,7 +12745,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -12742,7 +12758,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -12769,37 +12785,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -12809,10 +12825,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -12875,15 +12891,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -12908,19 +12924,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -12945,50 +12961,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -12997,7 +13013,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -13022,10 +13038,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -13048,7 +13064,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -13077,7 +13093,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -13085,11 +13101,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -13099,9 +13115,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -13117,14 +13133,14 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
@@ -13229,8 +13245,8 @@ backups.
 The server will log errors.
 Use -v to see access logs.
 .PP
-\f[C]--bwlimit\f[R] will be respected for file transfers.
-Use \f[C]--stats\f[R] to control the stats printing.
+\f[V]--bwlimit\f[R] will be respected for file transfers.
+Use \f[V]--stats\f[R] to control the stats printing.
 .SS Setting up rclone for use by restic
 .PP
 First set up a remote for your chosen cloud
@@ -13253,11 +13269,11 @@ Where you can replace \[dq]backup\[dq] in the above by whatever path in
 the remote you wish to use.
 .PP
 By default this will serve on \[dq]localhost:8080\[dq] you can change
-this with use of the \f[C]--addr\f[R] flag.
+this with use of the \f[V]--addr\f[R] flag.
 .PP
 You might wish to start this server on boot.
 .PP
-Adding \f[C]--cache-objects=false\f[R] will cause rclone to stop caching
+Adding \f[V]--cache-objects=false\f[R] will cause rclone to stop caching
 objects returned from the List call.
 Caching is normally desirable as it speeds up downloading objects, saves
 transactions and uses very little memory.
@@ -13310,61 +13326,61 @@ $ export RESTIC_REPOSITORY=rest:http://localhost:8080/user2repo/
 .fi
 .SS Private repositories
 .PP
-The\f[C]--private-repos\f[R] flag can be used to limit users to
-repositories starting with a path of \f[C]/<username>/\f[R].
+The\f[V]--private-repos\f[R] flag can be used to limit users to
+repositories starting with a path of \f[V]/<username>/\f[R].
 .SS Server options
 .PP
-Use \f[C]--addr\f[R] to specify which IP address and port the server
-should listen on, eg \f[C]--addr 1.2.3.4:8000\f[R] or
-\f[C]--addr :8080\f[R] to listen to all IPs.
+Use \f[V]--addr\f[R] to specify which IP address and port the server
+should listen on, eg \f[V]--addr 1.2.3.4:8000\f[R] or
+\f[V]--addr :8080\f[R] to listen to all IPs.
 By default it only listens on localhost.
 You can use port :0 to let the OS choose an available port.
 .PP
-If you set \f[C]--addr\f[R] to listen on a public or LAN accessible IP
+If you set \f[V]--addr\f[R] to listen on a public or LAN accessible IP
 address then using Authentication is advised - see the next section for
 info.
 .PP
 You can use a unix socket by setting the url to
-\f[C]unix:///path/to/socket\f[R] or just by using an absolute path name.
+\f[V]unix:///path/to/socket\f[R] or just by using an absolute path name.
 Note that unix sockets bypass the authentication - this is expected to
 be done with file system permissions.
 .PP
-\f[C]--addr\f[R] may be repeated to listen on multiple
+\f[V]--addr\f[R] may be repeated to listen on multiple
 IPs/ports/sockets.
 Socket activation, described further below, can also be used to
 accomplish the same.
 .PP
-\f[C]--server-read-timeout\f[R] and \f[C]--server-write-timeout\f[R] can
+\f[V]--server-read-timeout\f[R] and \f[V]--server-write-timeout\f[R] can
 be used to control the timeouts on the server.
 Note that this is the total time for a transfer.
 .PP
-\f[C]--max-header-bytes\f[R] controls the maximum number of bytes the
+\f[V]--max-header-bytes\f[R] controls the maximum number of bytes the
 server will accept in the HTTP header.
 .PP
-\f[C]--baseurl\f[R] controls the URL prefix that rclone serves from.
+\f[V]--baseurl\f[R] controls the URL prefix that rclone serves from.
 By default rclone will serve from the root.
-If you used \f[C]--baseurl \[dq]/rclone\[dq]\f[R] then rclone would
+If you used \f[V]--baseurl \[dq]/rclone\[dq]\f[R] then rclone would
 serve from a URL starting with \[dq]/rclone/\[dq].
 This is useful if you wish to proxy rclone serve.
 Rclone automatically inserts leading and trailing \[dq]/\[dq] on
-\f[C]--baseurl\f[R], so \f[C]--baseurl \[dq]rclone\[dq]\f[R],
-\f[C]--baseurl \[dq]/rclone\[dq]\f[R] and
-\f[C]--baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
+\f[V]--baseurl\f[R], so \f[V]--baseurl \[dq]rclone\[dq]\f[R],
+\f[V]--baseurl \[dq]/rclone\[dq]\f[R] and
+\f[V]--baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
 .SS TLS (SSL)
 .PP
 By default this will serve over http.
 If you want you can serve over https.
-You will need to supply the \f[C]--cert\f[R] and \f[C]--key\f[R] flags.
+You will need to supply the \f[V]--cert\f[R] and \f[V]--key\f[R] flags.
 If you wish to do client side certificate validation then you will need
-to supply \f[C]--client-ca\f[R] also.
+to supply \f[V]--client-ca\f[R] also.
 .PP
-\f[C]--cert\f[R] should be a either a PEM encoded certificate or a
+\f[V]--cert\f[R] should be a either a PEM encoded certificate or a
 concatenation of that with the CA certificate.
-\f[C]--key\f[R] should be the PEM encoded private key and
-\f[C]--client-ca\f[R] should be the PEM encoded client certificate
+\f[V]--key\f[R] should be the PEM encoded private key and
+\f[V]--client-ca\f[R] should be the PEM encoded client certificate
 authority certificate.
 .PP
-\f[C]--min-tls-version\f[R] is minimum TLS version that is acceptable.
+\f[V]--min-tls-version\f[R] is minimum TLS version that is acceptable.
 Valid values are \[dq]tls1.0\[dq], \[dq]tls1.1\[dq], \[dq]tls1.2\[dq]
 and \[dq]tls1.3\[dq] (default \[dq]tls1.0\[dq]).
 .SS Socket activation
@@ -13379,7 +13395,7 @@ in
 https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html
 .PP
 Socket activation can be tested ad-hoc with the
-\f[C]systemd-socket-activate\f[R]command
+\f[V]systemd-socket-activate\f[R]command
 .IP
 .nf
 \f[C]
@@ -13394,15 +13410,15 @@ over TCP.
 By default this will serve files without needing a login.
 .PP
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the \f[C]--user\f[R] and
-\f[C]--pass\f[R] flags.
+a single username and password with the \f[V]--user\f[R] and
+\f[V]--pass\f[R] flags.
 .PP
 If no static users are configured by either of the above methods, and
-client certificates are required by the \f[C]--client-ca\f[R] flag
+client certificates are required by the \f[V]--client-ca\f[R] flag
 passed to the server, the client certificate common name will be
 considered as the username.
 .PP
-Use \f[C]--htpasswd /path/to/htpasswd\f[R] to provide an htpasswd file.
+Use \f[V]--htpasswd /path/to/htpasswd\f[R] to provide an htpasswd file.
 This is in standard apache format and supports MD5, SHA1 and BCrypt for
 basic authentication.
 Bcrypt is recommended.
@@ -13419,9 +13435,9 @@ htpasswd -B htpasswd anotherUser
 .PP
 The password file can be updated while rclone is running.
 .PP
-Use \f[C]--realm\f[R] to set the authentication realm.
+Use \f[V]--realm\f[R] to set the authentication realm.
 .PP
-Use \f[C]--salt\f[R] to change the password hashing salt from the
+Use \f[V]--salt\f[R] to change the password hashing salt from the
 default.
 .IP
 .nf
@@ -13467,43 +13483,43 @@ remote over a protocol.
 Serve remote:path over s3.
 .SS Synopsis
 .PP
-\f[C]serve s3\f[R] implements a basic s3 server that serves a remote via
+\f[V]serve s3\f[R] implements a basic s3 server that serves a remote via
 s3.
 This can be viewed with an s3 client, or you can make an s3 type
 remote (https://rclone.org/s3/) to read and write to it with rclone.
 .PP
-\f[C]serve s3\f[R] is considered \f[B]Experimental\f[R] so use with
+\f[V]serve s3\f[R] is considered \f[B]Experimental\f[R] so use with
 care.
 .PP
 S3 server supports Signature Version 4 authentication.
-Just use \f[C]--auth-key accessKey,secretKey\f[R] and set the
-\f[C]Authorization\f[R] header correctly in the request.
+Just use \f[V]--auth-key accessKey,secretKey\f[R] and set the
+\f[V]Authorization\f[R] header correctly in the request.
 (See the AWS
 docs (https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html)).
 .PP
-\f[C]--auth-key\f[R] can be repeated for multiple auth pairs.
-If \f[C]--auth-key\f[R] is not provided then \f[C]serve s3\f[R] will
+\f[V]--auth-key\f[R] can be repeated for multiple auth pairs.
+If \f[V]--auth-key\f[R] is not provided then \f[V]serve s3\f[R] will
 allow anonymous access.
 .PP
 Please note that some clients may require HTTPS endpoints.
 See the SSL docs for more information.
 .PP
 This command uses the VFS directory cache.
-All the functionality will work with \f[C]--vfs-cache-mode off\f[R].
-Using \f[C]--vfs-cache-mode full\f[R] (or \f[C]writes\f[R]) can be used
+All the functionality will work with \f[V]--vfs-cache-mode off\f[R].
+Using \f[V]--vfs-cache-mode full\f[R] (or \f[V]writes\f[R]) can be used
 to cache objects locally to improve performance.
 .PP
-Use \f[C]--force-path-style=false\f[R] if you want to use the bucket
+Use \f[V]--force-path-style=false\f[R] if you want to use the bucket
 name as a part of the hostname (such as mybucket.local)
 .PP
-Use \f[C]--etag-hash\f[R] if you want to change the hash uses for the
-\f[C]ETag\f[R].
-Note that using anything other than \f[C]MD5\f[R] (the default) is
+Use \f[V]--etag-hash\f[R] if you want to change the hash uses for the
+\f[V]ETag\f[R].
+Note that using anything other than \f[V]MD5\f[R] (the default) is
 likely to cause problems for S3 clients which rely on the Etag being the
 MD5.
 .SS Quickstart
 .PP
-For a simple set up, to serve \f[C]remote:path\f[R] over s3, run the
+For a simple set up, to serve \f[V]remote:path\f[R] over s3, run the
 server like this:
 .IP
 .nf
@@ -13521,7 +13537,7 @@ rclone serve s3 --auth-key ACCESS_KEY_ID,SECRET_ACCESS_KEY local:/path/to/folder
 \f[R]
 .fi
 .PP
-The \f[C]rclone.conf\f[R] for the server could look like this:
+The \f[V]rclone.conf\f[R] for the server could look like this:
 .IP
 .nf
 \f[C]
@@ -13530,10 +13546,10 @@ type = local
 \f[R]
 .fi
 .PP
-The \f[C]local\f[R] configuration is optional though.
-If you run the server with a \f[C]remote:path\f[R] like
-\f[C]/path/to/folder\f[R] (without the \f[C]local:\f[R] prefix and
-without an \f[C]rclone.conf\f[R] file), rclone will fall back to a
+The \f[V]local\f[R] configuration is optional though.
+If you run the server with a \f[V]remote:path\f[R] like
+\f[V]/path/to/folder\f[R] (without the \f[V]local:\f[R] prefix and
+without an \f[V]rclone.conf\f[R] file), rclone will fall back to a
 default configuration, which will be visible as a warning in the logs.
 But it will run nonetheless.
 .PP
@@ -13552,11 +13568,11 @@ use_multipart_uploads = false
 \f[R]
 .fi
 .PP
-Note that setting \f[C]disable_multipart_uploads = true\f[R] is to work
+Note that setting \f[V]disable_multipart_uploads = true\f[R] is to work
 around a bug which will be fixed in due course.
 .SS Bugs
 .PP
-When uploading multipart files \f[C]serve s3\f[R] holds all the parts in
+When uploading multipart files \f[V]serve s3\f[R] holds all the parts in
 memory (see #7453 (https://github.com/rclone/rclone/issues/7453)).
 This is a limitaton of the library rclone uses for serving S3 and will
 hopefully be fixed at some point.
@@ -13568,87 +13584,87 @@ The default threshold for multipart server side copies is 5G which is
 the maximum it can be, so files above this side will fail to be server
 side copied.
 .PP
-For a current list of \f[C]serve s3\f[R] bugs see the serve
+For a current list of \f[V]serve s3\f[R] bugs see the serve
 s3 (https://github.com/rclone/rclone/labels/serve%20s3) bug category on
 GitHub.
 .SS Limitations
 .PP
-\f[C]serve s3\f[R] will treat all directories in the root as buckets and
+\f[V]serve s3\f[R] will treat all directories in the root as buckets and
 ignore all files in the root.
-You can use \f[C]CreateBucket\f[R] to create folders under the root, but
+You can use \f[V]CreateBucket\f[R] to create folders under the root, but
 you can\[aq]t create empty folders under other folders not in the root.
 .PP
-When using \f[C]PutObject\f[R] or \f[C]DeleteObject\f[R], rclone will
+When using \f[V]PutObject\f[R] or \f[V]DeleteObject\f[R], rclone will
 automatically create or clean up empty folders.
 If you don\[aq]t want to clean up empty folders automatically, use
-\f[C]--no-cleanup\f[R].
+\f[V]--no-cleanup\f[R].
 .PP
-When using \f[C]ListObjects\f[R], rclone will use \f[C]/\f[R] when the
+When using \f[V]ListObjects\f[R], rclone will use \f[V]/\f[R] when the
 delimiter is empty.
 This reduces backend requests with no effect on most operations, but if
-the delimiter is something other than \f[C]/\f[R] and empty, rclone will
+the delimiter is something other than \f[V]/\f[R] and empty, rclone will
 do a full recursive search of the backend, which can take some time.
 .PP
 Versioning is not currently supported.
 .PP
 Metadata will only be saved in memory other than the rclone
-\f[C]mtime\f[R] metadata which will be set as the modification time of
+\f[V]mtime\f[R] metadata which will be set as the modification time of
 the file.
 .SS Supported operations
 .PP
-\f[C]serve s3\f[R] currently supports the following operations.
+\f[V]serve s3\f[R] currently supports the following operations.
 .IP \[bu] 2
 Bucket
 .RS 2
 .IP \[bu] 2
-\f[C]ListBuckets\f[R]
+\f[V]ListBuckets\f[R]
 .IP \[bu] 2
-\f[C]CreateBucket\f[R]
+\f[V]CreateBucket\f[R]
 .IP \[bu] 2
-\f[C]DeleteBucket\f[R]
+\f[V]DeleteBucket\f[R]
 .RE
 .IP \[bu] 2
 Object
 .RS 2
 .IP \[bu] 2
-\f[C]HeadObject\f[R]
+\f[V]HeadObject\f[R]
 .IP \[bu] 2
-\f[C]ListObjects\f[R]
+\f[V]ListObjects\f[R]
 .IP \[bu] 2
-\f[C]GetObject\f[R]
+\f[V]GetObject\f[R]
 .IP \[bu] 2
-\f[C]PutObject\f[R]
+\f[V]PutObject\f[R]
 .IP \[bu] 2
-\f[C]DeleteObject\f[R]
+\f[V]DeleteObject\f[R]
 .IP \[bu] 2
-\f[C]DeleteObjects\f[R]
+\f[V]DeleteObjects\f[R]
 .IP \[bu] 2
-\f[C]CreateMultipartUpload\f[R]
+\f[V]CreateMultipartUpload\f[R]
 .IP \[bu] 2
-\f[C]CompleteMultipartUpload\f[R]
+\f[V]CompleteMultipartUpload\f[R]
 .IP \[bu] 2
-\f[C]AbortMultipartUpload\f[R]
+\f[V]AbortMultipartUpload\f[R]
 .IP \[bu] 2
-\f[C]CopyObject\f[R]
+\f[V]CopyObject\f[R]
 .IP \[bu] 2
-\f[C]UploadPart\f[R]
+\f[V]UploadPart\f[R]
 .RE
 .PP
-Other operations will return error \f[C]Unimplemented\f[R].
+Other operations will return error \f[V]Unimplemented\f[R].
 .SS Authentication
 .PP
 By default this will serve files without needing a login.
 .PP
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the \f[C]--user\f[R] and
-\f[C]--pass\f[R] flags.
+a single username and password with the \f[V]--user\f[R] and
+\f[V]--pass\f[R] flags.
 .PP
 If no static users are configured by either of the above methods, and
-client certificates are required by the \f[C]--client-ca\f[R] flag
+client certificates are required by the \f[V]--client-ca\f[R] flag
 passed to the server, the client certificate common name will be
 considered as the username.
 .PP
-Use \f[C]--htpasswd /path/to/htpasswd\f[R] to provide an htpasswd file.
+Use \f[V]--htpasswd /path/to/htpasswd\f[R] to provide an htpasswd file.
 This is in standard apache format and supports MD5, SHA1 and BCrypt for
 basic authentication.
 Bcrypt is recommended.
@@ -13665,63 +13681,63 @@ htpasswd -B htpasswd anotherUser
 .PP
 The password file can be updated while rclone is running.
 .PP
-Use \f[C]--realm\f[R] to set the authentication realm.
+Use \f[V]--realm\f[R] to set the authentication realm.
 .PP
-Use \f[C]--salt\f[R] to change the password hashing salt from the
+Use \f[V]--salt\f[R] to change the password hashing salt from the
 default.
 .SS Server options
 .PP
-Use \f[C]--addr\f[R] to specify which IP address and port the server
-should listen on, eg \f[C]--addr 1.2.3.4:8000\f[R] or
-\f[C]--addr :8080\f[R] to listen to all IPs.
+Use \f[V]--addr\f[R] to specify which IP address and port the server
+should listen on, eg \f[V]--addr 1.2.3.4:8000\f[R] or
+\f[V]--addr :8080\f[R] to listen to all IPs.
 By default it only listens on localhost.
 You can use port :0 to let the OS choose an available port.
 .PP
-If you set \f[C]--addr\f[R] to listen on a public or LAN accessible IP
+If you set \f[V]--addr\f[R] to listen on a public or LAN accessible IP
 address then using Authentication is advised - see the next section for
 info.
 .PP
 You can use a unix socket by setting the url to
-\f[C]unix:///path/to/socket\f[R] or just by using an absolute path name.
+\f[V]unix:///path/to/socket\f[R] or just by using an absolute path name.
 Note that unix sockets bypass the authentication - this is expected to
 be done with file system permissions.
 .PP
-\f[C]--addr\f[R] may be repeated to listen on multiple
+\f[V]--addr\f[R] may be repeated to listen on multiple
 IPs/ports/sockets.
 Socket activation, described further below, can also be used to
 accomplish the same.
 .PP
-\f[C]--server-read-timeout\f[R] and \f[C]--server-write-timeout\f[R] can
+\f[V]--server-read-timeout\f[R] and \f[V]--server-write-timeout\f[R] can
 be used to control the timeouts on the server.
 Note that this is the total time for a transfer.
 .PP
-\f[C]--max-header-bytes\f[R] controls the maximum number of bytes the
+\f[V]--max-header-bytes\f[R] controls the maximum number of bytes the
 server will accept in the HTTP header.
 .PP
-\f[C]--baseurl\f[R] controls the URL prefix that rclone serves from.
+\f[V]--baseurl\f[R] controls the URL prefix that rclone serves from.
 By default rclone will serve from the root.
-If you used \f[C]--baseurl \[dq]/rclone\[dq]\f[R] then rclone would
+If you used \f[V]--baseurl \[dq]/rclone\[dq]\f[R] then rclone would
 serve from a URL starting with \[dq]/rclone/\[dq].
 This is useful if you wish to proxy rclone serve.
 Rclone automatically inserts leading and trailing \[dq]/\[dq] on
-\f[C]--baseurl\f[R], so \f[C]--baseurl \[dq]rclone\[dq]\f[R],
-\f[C]--baseurl \[dq]/rclone\[dq]\f[R] and
-\f[C]--baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
+\f[V]--baseurl\f[R], so \f[V]--baseurl \[dq]rclone\[dq]\f[R],
+\f[V]--baseurl \[dq]/rclone\[dq]\f[R] and
+\f[V]--baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
 .SS TLS (SSL)
 .PP
 By default this will serve over http.
 If you want you can serve over https.
-You will need to supply the \f[C]--cert\f[R] and \f[C]--key\f[R] flags.
+You will need to supply the \f[V]--cert\f[R] and \f[V]--key\f[R] flags.
 If you wish to do client side certificate validation then you will need
-to supply \f[C]--client-ca\f[R] also.
+to supply \f[V]--client-ca\f[R] also.
 .PP
-\f[C]--cert\f[R] should be a either a PEM encoded certificate or a
+\f[V]--cert\f[R] should be a either a PEM encoded certificate or a
 concatenation of that with the CA certificate.
-\f[C]--key\f[R] should be the PEM encoded private key and
-\f[C]--client-ca\f[R] should be the PEM encoded client certificate
+\f[V]--key\f[R] should be the PEM encoded private key and
+\f[V]--client-ca\f[R] should be the PEM encoded client certificate
 authority certificate.
 .PP
-\f[C]--min-tls-version\f[R] is minimum TLS version that is acceptable.
+\f[V]--min-tls-version\f[R] is minimum TLS version that is acceptable.
 Valid values are \[dq]tls1.0\[dq], \[dq]tls1.1\[dq], \[dq]tls1.2\[dq]
 and \[dq]tls1.3\[dq] (default \[dq]tls1.0\[dq]).
 .SS Socket activation
@@ -13736,7 +13752,7 @@ in
 https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html
 .PP
 Socket activation can be tested ad-hoc with the
-\f[C]systemd-socket-activate\f[R]command
+\f[V]systemd-socket-activate\f[R]command
 .IP
 .nf
 \f[C]
@@ -13762,7 +13778,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -13782,7 +13798,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -13811,7 +13827,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -13824,7 +13840,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -13851,37 +13867,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -13891,10 +13907,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -13957,15 +13973,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -13990,19 +14006,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -14027,50 +14043,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -14079,7 +14095,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -14104,10 +14120,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -14130,7 +14146,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -14159,7 +14175,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -14167,11 +14183,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -14181,9 +14197,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -14199,14 +14215,14 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
@@ -14321,7 +14337,7 @@ This can be used with an SFTP client or you can make a remote of type
 sftp to use with it.
 .PP
 You can use the filter flags (e.g.
-\f[C]--include\f[R], \f[C]--exclude\f[R]) to control what is served.
+\f[V]--include\f[R], \f[V]--exclude\f[R]) to control what is served.
 .PP
 The server will respond to a small number of shell commands, mainly
 md5sum, sha1sum and df, which enable it to provide support for checksums
@@ -14333,24 +14349,24 @@ with the chunk_size (https://rclone.org/sftp/#sftp-chunk-size) option on
 an sftp remote.
 .PP
 The server will log errors.
-Use \f[C]-v\f[R] to see access logs.
+Use \f[V]-v\f[R] to see access logs.
 .PP
-\f[C]--bwlimit\f[R] will be respected for file transfers.
-Use \f[C]--stats\f[R] to control the stats printing.
+\f[V]--bwlimit\f[R] will be respected for file transfers.
+Use \f[V]--stats\f[R] to control the stats printing.
 .PP
 You must provide some means of authentication, either with
-\f[C]--user\f[R]/\f[C]--pass\f[R], an authorized keys file (specify
-location with \f[C]--authorized-keys\f[R] - the default is the same as
-ssh), an \f[C]--auth-proxy\f[R], or set the \f[C]--no-auth\f[R] flag for
+\f[V]--user\f[R]/\f[V]--pass\f[R], an authorized keys file (specify
+location with \f[V]--authorized-keys\f[R] - the default is the same as
+ssh), an \f[V]--auth-proxy\f[R], or set the \f[V]--no-auth\f[R] flag for
 no authentication when logging in.
 .PP
-If you don\[aq]t supply a host \f[C]--key\f[R] then rclone will generate
+If you don\[aq]t supply a host \f[V]--key\f[R] then rclone will generate
 rsa, ecdsa and ed25519 variants, and cache them for later use in
-rclone\[aq]s cache directory (see \f[C]rclone help flags cache-dir\f[R])
+rclone\[aq]s cache directory (see \f[V]rclone help flags cache-dir\f[R])
 in the \[dq]serve-sftp\[dq] directory.
 .PP
 By default the server binds to localhost:2022 - if you want it to be
-reachable externally then supply \f[C]--addr :2022\f[R] for example.
+reachable externally then supply \f[V]--addr :2022\f[R] for example.
 .PP
 This also supports being run with socket activation, in which case it
 will listen on the first passed FD.
@@ -14359,7 +14375,7 @@ in
 https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html
 .PP
 Socket activation can be tested ad-hoc with the
-\f[C]systemd-socket-activate\f[R]command:
+\f[V]systemd-socket-activate\f[R]command:
 .IP
 .nf
 \f[C]
@@ -14370,10 +14386,10 @@ systemd-socket-activate -l 2222 -- rclone serve sftp :local:vfs/
 This will socket-activate rclone on the first connection to port 2222
 over TCP.
 .PP
-Note that the default of \f[C]--vfs-cache-mode off\f[R] is fine for the
+Note that the default of \f[V]--vfs-cache-mode off\f[R] is fine for the
 rclone sftp backend, but it may not be with other SFTP clients.
 .PP
-If \f[C]--stdio\f[R] is specified, rclone will serve SFTP over stdio,
+If \f[V]--stdio\f[R] is specified, rclone will serve SFTP over stdio,
 which can be used with sshd via \[ti]/.ssh/authorized_keys, for example:
 .IP
 .nf
@@ -14382,8 +14398,8 @@ restrict,command=\[dq]rclone serve sftp --stdio ./photos\[dq] ssh-rsa ...
 \f[R]
 .fi
 .PP
-On the client you need to set \f[C]--transfers 1\f[R] when using
-\f[C]--stdio\f[R].
+On the client you need to set \f[V]--transfers 1\f[R] when using
+\f[V]--stdio\f[R].
 Otherwise multiple instances of the rclone server are started by OpenSSH
 which can lead to \[dq]corrupted on transfer\[dq] errors.
 This is the case because the client chooses indiscriminately which
@@ -14392,7 +14408,7 @@ the state of the filing system.
 .PP
 The \[dq]restrict\[dq] in authorized_keys prevents SHA1SUMs and MD5SUMs
 from being used.
-Omitting \[dq]restrict\[dq] and using \f[C]--sftp-path-override\f[R] to
+Omitting \[dq]restrict\[dq] and using \f[V]--sftp-path-override\f[R] to
 enable checksumming is possible but less secure and you could use the
 SFTP server provided by OpenSSH in this case.
 .SS VFS - Virtual File System
@@ -14411,7 +14427,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -14431,7 +14447,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -14460,7 +14476,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -14473,7 +14489,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -14500,37 +14516,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -14540,10 +14556,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -14606,15 +14622,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -14639,19 +14655,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -14676,50 +14692,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -14728,7 +14744,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -14753,10 +14769,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -14779,7 +14795,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -14808,7 +14824,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -14816,11 +14832,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -14830,9 +14846,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -14848,36 +14864,36 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
 Use it as a last resort and only with caching.
 .SS Auth Proxy
 .PP
-If you supply the parameter \f[C]--auth-proxy /path/to/program\f[R] then
+If you supply the parameter \f[V]--auth-proxy /path/to/program\f[R] then
 rclone will use that program to generate backends on the fly which then
 are used to authenticate incoming requests.
 This uses a simple JSON based protocol with input on STDIN and output on
 STDOUT.
 .PP
-\f[B]PLEASE NOTE:\f[R] \f[C]--auth-proxy\f[R] and
-\f[C]--authorized-keys\f[R] cannot be used together, if
-\f[C]--auth-proxy\f[R] is set the authorized keys option will be
+\f[B]PLEASE NOTE:\f[R] \f[V]--auth-proxy\f[R] and
+\f[V]--authorized-keys\f[R] cannot be used together, if
+\f[V]--auth-proxy\f[R] is set the authorized keys option will be
 ignored.
 .PP
 There is an example program
 bin/test_proxy.py (https://github.com/rclone/rclone/blob/master/bin/test_proxy.py)
 in the rclone source code.
 .PP
-The program\[aq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] on
+The program\[aq]s job is to take a \f[V]user\f[R] and \f[V]pass\f[R] on
 the input and turn those into the config for a backend on STDOUT in JSON
 format.
 This config will have any default parameters for the backend added, but
@@ -14885,10 +14901,10 @@ it won\[aq]t use configuration from environment variables or command
 line options - it is the job of the proxy program to make a complete
 config.
 .PP
-This config generated must have this extra parameter - \f[C]_root\f[R] -
+This config generated must have this extra parameter - \f[V]_root\f[R] -
 root to use for the backend
 .PP
-And it may have this parameter - \f[C]_obscure\f[R] - comma separated
+And it may have this parameter - \f[V]_obscure\f[R] - comma separated
 strings for parameters to obscure
 .PP
 If password authentication was used by the client, input to the proxy
@@ -14931,22 +14947,22 @@ And as an example return this on STDOUT
 .fi
 .PP
 This would mean that an SFTP backend would be created on the fly for the
-\f[C]user\f[R] and \f[C]pass\f[R]/\f[C]public_key\f[R] returned in the
+\f[V]user\f[R] and \f[V]pass\f[R]/\f[V]public_key\f[R] returned in the
 output to the host given.
-Note that since \f[C]_obscure\f[R] is set to \f[C]pass\f[R], rclone will
-obscure the \f[C]pass\f[R] parameter before creating the backend (which
+Note that since \f[V]_obscure\f[R] is set to \f[V]pass\f[R], rclone will
+obscure the \f[V]pass\f[R] parameter before creating the backend (which
 is required for sftp backends).
 .PP
-The program can manipulate the supplied \f[C]user\f[R] in any way, for
+The program can manipulate the supplied \f[V]user\f[R] in any way, for
 example to make proxy to many different sftp backends, you could make
-the \f[C]user\f[R] be \f[C]user\[at]example.com\f[R] and then set the
-\f[C]host\f[R] to \f[C]example.com\f[R] in the output and the user to
-\f[C]user\f[R].
-For security you\[aq]d probably want to restrict the \f[C]host\f[R] to a
+the \f[V]user\f[R] be \f[V]user\[at]example.com\f[R] and then set the
+\f[V]host\f[R] to \f[V]example.com\f[R] in the output and the user to
+\f[V]user\f[R].
+For security you\[aq]d probably want to restrict the \f[V]host\f[R] to a
 limited list.
 .PP
-Note that an internal cache is keyed on \f[C]user\f[R] so only use that
-for configuration, don\[aq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
+Note that an internal cache is keyed on \f[V]user\f[R] so only use that
+for configuration, don\[aq]t use \f[V]pass\f[R] or \f[V]public_key\f[R].
 This also means that if a user\[aq]s password or public-key is changed
 the cache will need to expire (which takes 5 mins) before it takes
 effect.
@@ -15113,57 +15129,57 @@ Note that there is no authentication on http protocol - this is expected
 to be done by the permissions on the socket.
 .SS Server options
 .PP
-Use \f[C]--addr\f[R] to specify which IP address and port the server
-should listen on, eg \f[C]--addr 1.2.3.4:8000\f[R] or
-\f[C]--addr :8080\f[R] to listen to all IPs.
+Use \f[V]--addr\f[R] to specify which IP address and port the server
+should listen on, eg \f[V]--addr 1.2.3.4:8000\f[R] or
+\f[V]--addr :8080\f[R] to listen to all IPs.
 By default it only listens on localhost.
 You can use port :0 to let the OS choose an available port.
 .PP
-If you set \f[C]--addr\f[R] to listen on a public or LAN accessible IP
+If you set \f[V]--addr\f[R] to listen on a public or LAN accessible IP
 address then using Authentication is advised - see the next section for
 info.
 .PP
 You can use a unix socket by setting the url to
-\f[C]unix:///path/to/socket\f[R] or just by using an absolute path name.
+\f[V]unix:///path/to/socket\f[R] or just by using an absolute path name.
 Note that unix sockets bypass the authentication - this is expected to
 be done with file system permissions.
 .PP
-\f[C]--addr\f[R] may be repeated to listen on multiple
+\f[V]--addr\f[R] may be repeated to listen on multiple
 IPs/ports/sockets.
 Socket activation, described further below, can also be used to
 accomplish the same.
 .PP
-\f[C]--server-read-timeout\f[R] and \f[C]--server-write-timeout\f[R] can
+\f[V]--server-read-timeout\f[R] and \f[V]--server-write-timeout\f[R] can
 be used to control the timeouts on the server.
 Note that this is the total time for a transfer.
 .PP
-\f[C]--max-header-bytes\f[R] controls the maximum number of bytes the
+\f[V]--max-header-bytes\f[R] controls the maximum number of bytes the
 server will accept in the HTTP header.
 .PP
-\f[C]--baseurl\f[R] controls the URL prefix that rclone serves from.
+\f[V]--baseurl\f[R] controls the URL prefix that rclone serves from.
 By default rclone will serve from the root.
-If you used \f[C]--baseurl \[dq]/rclone\[dq]\f[R] then rclone would
+If you used \f[V]--baseurl \[dq]/rclone\[dq]\f[R] then rclone would
 serve from a URL starting with \[dq]/rclone/\[dq].
 This is useful if you wish to proxy rclone serve.
 Rclone automatically inserts leading and trailing \[dq]/\[dq] on
-\f[C]--baseurl\f[R], so \f[C]--baseurl \[dq]rclone\[dq]\f[R],
-\f[C]--baseurl \[dq]/rclone\[dq]\f[R] and
-\f[C]--baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
+\f[V]--baseurl\f[R], so \f[V]--baseurl \[dq]rclone\[dq]\f[R],
+\f[V]--baseurl \[dq]/rclone\[dq]\f[R] and
+\f[V]--baseurl \[dq]/rclone/\[dq]\f[R] are all treated identically.
 .SS TLS (SSL)
 .PP
 By default this will serve over http.
 If you want you can serve over https.
-You will need to supply the \f[C]--cert\f[R] and \f[C]--key\f[R] flags.
+You will need to supply the \f[V]--cert\f[R] and \f[V]--key\f[R] flags.
 If you wish to do client side certificate validation then you will need
-to supply \f[C]--client-ca\f[R] also.
+to supply \f[V]--client-ca\f[R] also.
 .PP
-\f[C]--cert\f[R] should be a either a PEM encoded certificate or a
+\f[V]--cert\f[R] should be a either a PEM encoded certificate or a
 concatenation of that with the CA certificate.
-\f[C]--key\f[R] should be the PEM encoded private key and
-\f[C]--client-ca\f[R] should be the PEM encoded client certificate
+\f[V]--key\f[R] should be the PEM encoded private key and
+\f[V]--client-ca\f[R] should be the PEM encoded client certificate
 authority certificate.
 .PP
-\f[C]--min-tls-version\f[R] is minimum TLS version that is acceptable.
+\f[V]--min-tls-version\f[R] is minimum TLS version that is acceptable.
 Valid values are \[dq]tls1.0\[dq], \[dq]tls1.1\[dq], \[dq]tls1.2\[dq]
 and \[dq]tls1.3\[dq] (default \[dq]tls1.0\[dq]).
 .SS Socket activation
@@ -15178,7 +15194,7 @@ in
 https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html
 .PP
 Socket activation can be tested ad-hoc with the
-\f[C]systemd-socket-activate\f[R]command
+\f[V]systemd-socket-activate\f[R]command
 .IP
 .nf
 \f[C]
@@ -15190,7 +15206,7 @@ This will socket-activate rclone on the first connection to port 8000
 over TCP.
 ### Template
 .PP
-\f[C]--template\f[R] allows a user to specify a custom markup template
+\f[V]--template\f[R] allows a user to specify a custom markup template
 for HTTP and WebDAV serve functions.
 The server exports the following markup to be used within the template
 to server pages:
@@ -15327,15 +15343,15 @@ T}
 By default this will serve files without needing a login.
 .PP
 You can either use an htpasswd file which can take lots of users, or set
-a single username and password with the \f[C]--user\f[R] and
-\f[C]--pass\f[R] flags.
+a single username and password with the \f[V]--user\f[R] and
+\f[V]--pass\f[R] flags.
 .PP
 If no static users are configured by either of the above methods, and
-client certificates are required by the \f[C]--client-ca\f[R] flag
+client certificates are required by the \f[V]--client-ca\f[R] flag
 passed to the server, the client certificate common name will be
 considered as the username.
 .PP
-Use \f[C]--htpasswd /path/to/htpasswd\f[R] to provide an htpasswd file.
+Use \f[V]--htpasswd /path/to/htpasswd\f[R] to provide an htpasswd file.
 This is in standard apache format and supports MD5, SHA1 and BCrypt for
 basic authentication.
 Bcrypt is recommended.
@@ -15352,9 +15368,9 @@ htpasswd -B htpasswd anotherUser
 .PP
 The password file can be updated while rclone is running.
 .PP
-Use \f[C]--realm\f[R] to set the authentication realm.
+Use \f[V]--realm\f[R] to set the authentication realm.
 .PP
-Use \f[C]--salt\f[R] to change the password hashing salt from the
+Use \f[V]--salt\f[R] to change the password hashing salt from the
 default.
 .SS VFS - Virtual File System
 .PP
@@ -15372,7 +15388,7 @@ The VFS layer also implements a directory cache - this caches info about
 files and directories (but not the data) in memory.
 .SS VFS Directory Cache
 .PP
-Using the \f[C]--dir-cache-time\f[R] flag, you can control how long a
+Using the \f[V]--dir-cache-time\f[R] flag, you can control how long a
 directory should be considered up to date and not refreshed from the
 backend.
 Changes made through the VFS will appear immediately or invalidate the
@@ -15392,7 +15408,7 @@ changes.
 If the backend supports polling, changes will be picked up within the
 polling interval.
 .PP
-You can send a \f[C]SIGHUP\f[R] signal to rclone for it to flush all
+You can send a \f[V]SIGHUP\f[R] signal to rclone for it to flush all
 directory caches, regardless of how old they are.
 Assuming only one rclone instance is running, you can reset the cache
 like this:
@@ -15421,7 +15437,7 @@ rclone rc vfs/forget file=path/to/file dir=path/to/dir
 .fi
 .SS VFS File Buffering
 .PP
-The \f[C]--buffer-size\f[R] flag determines the amount of memory, that
+The \f[V]--buffer-size\f[R] flag determines the amount of memory, that
 will be used to buffer data in advance.
 .PP
 Each open file will try to keep the specified amount of data in memory
@@ -15434,7 +15450,7 @@ yet read.
 If the buffer is empty, only a small amount of memory will be used.
 .PP
 The maximum memory used by rclone for buffering can be up to
-\f[C]--buffer-size * open files\f[R].
+\f[V]--buffer-size * open files\f[R].
 .SS VFS File Caching
 .PP
 These flags control the VFS file caching options.
@@ -15461,37 +15477,37 @@ find that you need one or the other or both.
 \f[R]
 .fi
 .PP
-If run with \f[C]-vv\f[R] rclone will print the location of the file
+If run with \f[V]-vv\f[R] rclone will print the location of the file
 cache.
 The files are stored in the user cache file area which is OS dependent
-but can be controlled with \f[C]--cache-dir\f[R] or setting the
+but can be controlled with \f[V]--cache-dir\f[R] or setting the
 appropriate environment variable.
 .PP
-The cache has 4 different modes selected by \f[C]--vfs-cache-mode\f[R].
+The cache has 4 different modes selected by \f[V]--vfs-cache-mode\f[R].
 The higher the cache mode the more compatible rclone becomes at the cost
 of using disk space.
 .PP
 Note that files are written back to the remote only when they are closed
-and if they haven\[aq]t been accessed for \f[C]--vfs-write-back\f[R]
+and if they haven\[aq]t been accessed for \f[V]--vfs-write-back\f[R]
 seconds.
 If rclone is quit or dies with files that haven\[aq]t been uploaded,
 these will be uploaded next time rclone is run with the same flags.
 .PP
-If using \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
+If using \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] note that the cache may exceed these
 quotas for two reasons.
 Firstly because it is only checked every
-\f[C]--vfs-cache-poll-interval\f[R].
+\f[V]--vfs-cache-poll-interval\f[R].
 Secondly because open files cannot be evicted from the cache.
-When \f[C]--vfs-cache-max-size\f[R] or
-\f[C]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
+When \f[V]--vfs-cache-max-size\f[R] or
+\f[V]--vfs-cache-min-free-size\f[R] is exceeded, rclone will attempt to
 evict the least accessed files from the cache first.
 rclone will start with files that haven\[aq]t been accessed for the
 longest.
 This cache flushing strategy is efficient and more relevant files are
 likely to remain cached.
 .PP
-The \f[C]--vfs-cache-max-age\f[R] will evict files from the cache after
+The \f[V]--vfs-cache-max-age\f[R] will evict files from the cache after
 the set time since last access has passed.
 The default value of 1 hour will start evicting files from cache that
 haven\[aq]t been accessed for 1 hour.
@@ -15501,10 +15517,10 @@ Specify the time with standard notation, s, m, h, d, w .
 .PP
 You \f[B]should not\f[R] run two copies of rclone using the same VFS
 cache with the same or overlapping remotes if using
-\f[C]--vfs-cache-mode > off\f[R].
+\f[V]--vfs-cache-mode > off\f[R].
 This can potentially cause data corruption if you do.
 You can work around this by giving each rclone its own cache hierarchy
-with \f[C]--cache-dir\f[R].
+with \f[V]--cache-dir\f[R].
 You don\[aq]t need to worry about this if the remotes in use don\[aq]t
 overlap.
 .SS --vfs-cache-mode off
@@ -15567,15 +15583,15 @@ will be sparse files with only the data that has been downloaded present
 in them.
 .PP
 This mode should support all normal file system operations and is
-otherwise identical to \f[C]--vfs-cache-mode\f[R] writes.
+otherwise identical to \f[V]--vfs-cache-mode\f[R] writes.
 .PP
-When reading a file rclone will read \f[C]--buffer-size\f[R] plus
-\f[C]--vfs-read-ahead\f[R] bytes ahead.
-The \f[C]--buffer-size\f[R] is buffered in memory whereas the
-\f[C]--vfs-read-ahead\f[R] is buffered on disk.
+When reading a file rclone will read \f[V]--buffer-size\f[R] plus
+\f[V]--vfs-read-ahead\f[R] bytes ahead.
+The \f[V]--buffer-size\f[R] is buffered in memory whereas the
+\f[V]--vfs-read-ahead\f[R] is buffered on disk.
 .PP
-When using this mode it is recommended that \f[C]--buffer-size\f[R] is
-not set too large and \f[C]--vfs-read-ahead\f[R] is set large if
+When using this mode it is recommended that \f[V]--buffer-size\f[R] is
+not set too large and \f[V]--vfs-read-ahead\f[R] is set large if
 required.
 .PP
 \f[B]IMPORTANT\f[R] not all file systems support sparse files.
@@ -15600,19 +15616,19 @@ where available on an object.
 On some backends some of these attributes are slow to read (they take an
 extra API call per object, or extra work per object).
 .PP
-For example \f[C]hash\f[R] is slow with the \f[C]local\f[R] and
-\f[C]sftp\f[R] backends as they have to read the entire file and hash
-it, and \f[C]modtime\f[R] is slow with the \f[C]s3\f[R],
-\f[C]swift\f[R], \f[C]ftp\f[R] and \f[C]qinqstor\f[R] backends because
+For example \f[V]hash\f[R] is slow with the \f[V]local\f[R] and
+\f[V]sftp\f[R] backends as they have to read the entire file and hash
+it, and \f[V]modtime\f[R] is slow with the \f[V]s3\f[R],
+\f[V]swift\f[R], \f[V]ftp\f[R] and \f[V]qinqstor\f[R] backends because
 they need to do an extra API call to fetch it.
 .PP
-If you use the \f[C]--vfs-fast-fingerprint\f[R] flag then rclone will
+If you use the \f[V]--vfs-fast-fingerprint\f[R] flag then rclone will
 not include the slow operations in the fingerprint.
 This makes the fingerprinting less accurate but much faster and will
 improve the opening time of cached files.
 .PP
-If you are running a vfs cache over \f[C]local\f[R], \f[C]s3\f[R] or
-\f[C]swift\f[R] backends then using this flag is recommended.
+If you are running a vfs cache over \f[V]local\f[R], \f[V]s3\f[R] or
+\f[V]swift\f[R] backends then using this flag is recommended.
 .PP
 Note that if you change the value of this flag, the fingerprints of the
 files in the cache may be invalidated and the files will need to be
@@ -15637,50 +15653,50 @@ These flags control the chunking:
 .fi
 .PP
 The chunking behaves differently depending on the
-\f[C]--vfs-read-chunk-streams\f[R] parameter.
-.SS \f[C]--vfs-read-chunk-streams\f[R] == 0
+\f[V]--vfs-read-chunk-streams\f[R] parameter.
+.SS \f[V]--vfs-read-chunk-streams\f[R] == 0
 .PP
 Rclone will start reading a chunk of size
-\f[C]--vfs-read-chunk-size\f[R], and then double the size for each read.
-When \f[C]--vfs-read-chunk-size-limit\f[R] is specified, and greater
-than \f[C]--vfs-read-chunk-size\f[R], the chunk size for each open file
+\f[V]--vfs-read-chunk-size\f[R], and then double the size for each read.
+When \f[V]--vfs-read-chunk-size-limit\f[R] is specified, and greater
+than \f[V]--vfs-read-chunk-size\f[R], the chunk size for each open file
 will get doubled only until the specified value is reached.
 If the value is \[dq]off\[dq], which is the default, the limit is
 disabled and the chunk size will grow indefinitely.
 .PP
-With \f[C]--vfs-read-chunk-size 100M\f[R] and
-\f[C]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
+With \f[V]--vfs-read-chunk-size 100M\f[R] and
+\f[V]--vfs-read-chunk-size-limit 0\f[R] the following parts will be
 downloaded: 0-100M, 100M-200M, 200M-300M, 300M-400M and so on.
-When \f[C]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
+When \f[V]--vfs-read-chunk-size-limit 500M\f[R] is specified, the result
 would be 0-100M, 100M-300M, 300M-700M, 700M-1200M, 1200M-1700M and so
 on.
 .PP
-Setting \f[C]--vfs-read-chunk-size\f[R] to \f[C]0\f[R] or \[dq]off\[dq]
+Setting \f[V]--vfs-read-chunk-size\f[R] to \f[V]0\f[R] or \[dq]off\[dq]
 disables chunked reading.
 .PP
 The chunks will not be buffered in memory.
-.SS \f[C]--vfs-read-chunk-streams\f[R] > 0
+.SS \f[V]--vfs-read-chunk-streams\f[R] > 0
 .PP
-Rclone reads \f[C]--vfs-read-chunk-streams\f[R] chunks of size
-\f[C]--vfs-read-chunk-size\f[R] concurrently.
+Rclone reads \f[V]--vfs-read-chunk-streams\f[R] chunks of size
+\f[V]--vfs-read-chunk-size\f[R] concurrently.
 The size for each read will stay constant.
 .PP
 This improves performance performance massively on high latency links or
 very high bandwidth links to high performance object stores.
 .PP
 Some experimentation will be needed to find the optimum values of
-\f[C]--vfs-read-chunk-size\f[R] and \f[C]--vfs-read-chunk-streams\f[R]
+\f[V]--vfs-read-chunk-size\f[R] and \f[V]--vfs-read-chunk-streams\f[R]
 as these will depend on the backend in use and the latency to the
 backend.
 .PP
 For high performance object stores (eg AWS S3) a reasonable place to
-start might be \f[C]--vfs-read-chunk-streams 16\f[R] and
-\f[C]--vfs-read-chunk-size 4M\f[R].
+start might be \f[V]--vfs-read-chunk-streams 16\f[R] and
+\f[V]--vfs-read-chunk-size 4M\f[R].
 In testing with AWS S3 the performance scaled roughly as the
-\f[C]--vfs-read-chunk-streams\f[R] setting.
+\f[V]--vfs-read-chunk-streams\f[R] setting.
 .PP
 Similar settings should work for high latency links, but depending on
-the latency they may need more \f[C]--vfs-read-chunk-streams\f[R] in
+the latency they may need more \f[V]--vfs-read-chunk-streams\f[R] in
 order to get the throughput.
 .SS VFS Performance
 .PP
@@ -15689,7 +15705,7 @@ performance or other reasons.
 See also the chunked reading feature.
 .PP
 In particular S3 and Swift benefit hugely from the
-\f[C]--no-modtime\f[R] flag (or use \f[C]--use-server-modtime\f[R] for a
+\f[V]--no-modtime\f[R] flag (or use \f[V]--use-server-modtime\f[R] for a
 slightly different effect) as each read of the modification time takes a
 transaction.
 .IP
@@ -15714,10 +15730,10 @@ These flags only come into effect when not using an on disk cache file.
 \f[R]
 .fi
 .PP
-When using VFS write caching (\f[C]--vfs-cache-mode\f[R] with value
-writes or full), the global flag \f[C]--transfers\f[R] can be set to
+When using VFS write caching (\f[V]--vfs-cache-mode\f[R] with value
+writes or full), the global flag \f[V]--transfers\f[R] can be set to
 adjust the number of parallel uploads of modified files from the cache
-(the related global flag \f[C]--checkers\f[R] has no effect on the VFS).
+(the related global flag \f[V]--checkers\f[R] has no effect on the VFS).
 .IP
 .nf
 \f[C]
@@ -15740,7 +15756,7 @@ Usually file systems on macOS are case-insensitive.
 It is possible to make macOS file systems case-sensitive but that is not
 the default.
 .PP
-The \f[C]--vfs-case-insensitive\f[R] VFS flag controls how rclone
+The \f[V]--vfs-case-insensitive\f[R] VFS flag controls how rclone
 handles these two cases.
 If its value is \[dq]false\[dq], rclone passes file names to the remote
 as-is.
@@ -15769,7 +15785,7 @@ depends on the operating system where rclone runs: \[dq]true\[dq] on
 Windows and macOS, \[dq]false\[dq] otherwise.
 If the flag is provided without a value, then it is \[dq]true\[dq].
 .PP
-The \f[C]--no-unicode-normalization\f[R] flag controls whether a similar
+The \f[V]--no-unicode-normalization\f[R] flag controls whether a similar
 \[dq]fixup\[dq] is performed for filenames that differ but are
 canonically
 equivalent (https://en.wikipedia.org/wiki/Unicode_equivalence) with
@@ -15777,11 +15793,11 @@ respect to unicode.
 Unicode normalization can be particularly helpful for users of macOS,
 which prefers form NFD instead of the NFC used by most other platforms.
 It is therefore highly recommended to keep the default of
-\f[C]false\f[R] on macOS, to avoid encoding compatibility issues.
+\f[V]false\f[R] on macOS, to avoid encoding compatibility issues.
 .PP
 In the (probably unlikely) event that a directory has multiple duplicate
 filenames after applying case and unicode normalization, the
-\f[C]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
+\f[V]--vfs-block-norm-dupes\f[R] flag allows hiding these duplicates.
 This comes with a performance tradeoff, as rclone will have to scan the
 entire directory for duplicates when listing a directory.
 For this reason, it is recommended to leave this disabled if not needed.
@@ -15791,9 +15807,9 @@ filename, an odd situation will occur: both versions of the file will be
 visible in the mount, and both will appear to be editable, however,
 editing either version will actually result in only the NFD version
 getting edited under the hood.
-\f[C]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
+\f[V]--vfs-block- norm-dupes\f[R] prevents this confusion by detecting
 this scenario, hiding the duplicates, and logging an error, similar to
-how this is handled in \f[C]rclone sync\f[R].
+how this is handled in \f[V]rclone sync\f[R].
 .SS VFS Disk Options
 .PP
 This flag allows you to manually set the statistics about the filing
@@ -15809,36 +15825,36 @@ automatically.
 .SS Alternate report of used bytes
 .PP
 Some backends, most notably S3, do not report the amount of bytes used.
-If you need this information to be available when running \f[C]df\f[R]
-on the filesystem, then pass the flag \f[C]--vfs-used-is-size\f[R] to
+If you need this information to be available when running \f[V]df\f[R]
+on the filesystem, then pass the flag \f[V]--vfs-used-is-size\f[R] to
 rclone.
 With this flag set, instead of relying on the backend to report this
 information, rclone will scan the whole remote similar to
-\f[C]rclone size\f[R] and compute the total used space itself.
+\f[V]rclone size\f[R] and compute the total used space itself.
 .PP
-\f[I]WARNING.\f[R] Contrary to \f[C]rclone size\f[R], this flag ignores
+\f[I]WARNING.\f[R] Contrary to \f[V]rclone size\f[R], this flag ignores
 filters so that the result is accurate.
 However, this is very inefficient and may cost lots of API calls
 resulting in extra charges.
 Use it as a last resort and only with caching.
 .SS Auth Proxy
 .PP
-If you supply the parameter \f[C]--auth-proxy /path/to/program\f[R] then
+If you supply the parameter \f[V]--auth-proxy /path/to/program\f[R] then
 rclone will use that program to generate backends on the fly which then
 are used to authenticate incoming requests.
 This uses a simple JSON based protocol with input on STDIN and output on
 STDOUT.
 .PP
-\f[B]PLEASE NOTE:\f[R] \f[C]--auth-proxy\f[R] and
-\f[C]--authorized-keys\f[R] cannot be used together, if
-\f[C]--auth-proxy\f[R] is set the authorized keys option will be
+\f[B]PLEASE NOTE:\f[R] \f[V]--auth-proxy\f[R] and
+\f[V]--authorized-keys\f[R] cannot be used together, if
+\f[V]--auth-proxy\f[R] is set the authorized keys option will be
 ignored.
 .PP
 There is an example program
 bin/test_proxy.py (https://github.com/rclone/rclone/blob/master/bin/test_proxy.py)
 in the rclone source code.
 .PP
-The program\[aq]s job is to take a \f[C]user\f[R] and \f[C]pass\f[R] on
+The program\[aq]s job is to take a \f[V]user\f[R] and \f[V]pass\f[R] on
 the input and turn those into the config for a backend on STDOUT in JSON
 format.
 This config will have any default parameters for the backend added, but
@@ -15846,10 +15862,10 @@ it won\[aq]t use configuration from environment variables or command
 line options - it is the job of the proxy program to make a complete
 config.
 .PP
-This config generated must have this extra parameter - \f[C]_root\f[R] -
+This config generated must have this extra parameter - \f[V]_root\f[R] -
 root to use for the backend
 .PP
-And it may have this parameter - \f[C]_obscure\f[R] - comma separated
+And it may have this parameter - \f[V]_obscure\f[R] - comma separated
 strings for parameters to obscure
 .PP
 If password authentication was used by the client, input to the proxy
@@ -15892,22 +15908,22 @@ And as an example return this on STDOUT
 .fi
 .PP
 This would mean that an SFTP backend would be created on the fly for the
-\f[C]user\f[R] and \f[C]pass\f[R]/\f[C]public_key\f[R] returned in the
+\f[V]user\f[R] and \f[V]pass\f[R]/\f[V]public_key\f[R] returned in the
 output to the host given.
-Note that since \f[C]_obscure\f[R] is set to \f[C]pass\f[R], rclone will
-obscure the \f[C]pass\f[R] parameter before creating the backend (which
+Note that since \f[V]_obscure\f[R] is set to \f[V]pass\f[R], rclone will
+obscure the \f[V]pass\f[R] parameter before creating the backend (which
 is required for sftp backends).
 .PP
-The program can manipulate the supplied \f[C]user\f[R] in any way, for
+The program can manipulate the supplied \f[V]user\f[R] in any way, for
 example to make proxy to many different sftp backends, you could make
-the \f[C]user\f[R] be \f[C]user\[at]example.com\f[R] and then set the
-\f[C]host\f[R] to \f[C]example.com\f[R] in the output and the user to
-\f[C]user\f[R].
-For security you\[aq]d probably want to restrict the \f[C]host\f[R] to a
+the \f[V]user\f[R] be \f[V]user\[at]example.com\f[R] and then set the
+\f[V]host\f[R] to \f[V]example.com\f[R] in the output and the user to
+\f[V]user\f[R].
+For security you\[aq]d probably want to restrict the \f[V]host\f[R] to a
 limited list.
 .PP
-Note that an internal cache is keyed on \f[C]user\f[R] so only use that
-for configuration, don\[aq]t use \f[C]pass\f[R] or \f[C]public_key\f[R].
+Note that an internal cache is keyed on \f[V]user\f[R] so only use that
+for configuration, don\[aq]t use \f[V]pass\f[R] or \f[V]public_key\f[R].
 This also means that if a user\[aq]s password or public-key is changed
 the cache will need to expire (which takes 5 mins) before it takes
 effect.
@@ -16321,14 +16337,14 @@ Set the modification time on file(s) as specified by remote:path to have
 the current time.
 .PP
 If remote:path does not exist then a zero sized file will be created,
-unless \f[C]--no-create\f[R] or \f[C]--recursive\f[R] is provided.
+unless \f[V]--no-create\f[R] or \f[V]--recursive\f[R] is provided.
 .PP
-If \f[C]--recursive\f[R] is used then recursively sets the modification
+If \f[V]--recursive\f[R] is used then recursively sets the modification
 time on all existing files that is found under the path.
-Filters are supported, and you can test with the \f[C]--dry-run\f[R] or
-the \f[C]--interactive\f[R]/\f[C]-i\f[R] flag.
+Filters are supported, and you can test with the \f[V]--dry-run\f[R] or
+the \f[V]--interactive\f[R]/\f[V]-i\f[R] flag.
 .PP
-If \f[C]--timestamp\f[R] is used then sets the modification time to that
+If \f[V]--timestamp\f[R] is used then sets the modification time to that
 time instead of the current time.
 Times may be specified as one of:
 .IP \[bu] 2
@@ -16341,8 +16357,8 @@ Times may be specified as one of:
 \[aq]YYYY-MM-DDTHH:MM:SS.SSS\[aq] - e.g.
 2006-01-02T15:04:05.123456789
 .PP
-Note that value of \f[C]--timestamp\f[R] is in UTC.
-If you want local time then add the \f[C]--localtime\f[R] flag.
+Note that value of \f[V]--timestamp\f[R] is in UTC.
+If you want local time then add the \f[V]--localtime\f[R] flag.
 .IP
 .nf
 \f[C]
@@ -16433,24 +16449,24 @@ For example
 \f[C]
 $ rclone tree remote:path
 /
-\[u251C]\[u2500]\[u2500] file1
-\[u251C]\[u2500]\[u2500] file2
-\[u251C]\[u2500]\[u2500] file3
-\[u2514]\[u2500]\[u2500] subdir
-    \[u251C]\[u2500]\[u2500] file4
-    \[u2514]\[u2500]\[u2500] file5
+├── file1
+├── file2
+├── file3
+└── subdir
+    ├── file4
+    └── file5
 
 1 directories, 5 files
 \f[R]
 .fi
 .PP
 You can use any of the filtering options with the tree command (e.g.
-\f[C]--include\f[R] and \f[C]--exclude\f[R].
-You can also use \f[C]--fast-list\f[R].
+\f[V]--include\f[R] and \f[V]--exclude\f[R].
+You can also use \f[V]--fast-list\f[R].
 .PP
 The tree command has many options for controlling the listing which are
 compatible with the tree command, for example you can include file sizes
-with \f[C]--size\f[R].
+with \f[V]--size\f[R].
 Note that not all of them have short options as they conflict with
 rclone\[aq]s short options.
 .PP
@@ -16542,11 +16558,11 @@ However, if the source remote points to a file, rclone will just copy
 that file.
 The destination remote must point to a directory - rclone will give the
 error
-\f[C]Failed to create file system for \[dq]remote:file\[dq]: is a file not a directory\f[R]
+\f[V]Failed to create file system for \[dq]remote:file\[dq]: is a file not a directory\f[R]
 if it isn\[aq]t.
 .PP
 For example, suppose you have a remote with a file in called
-\f[C]test.jpg\f[R], then you could copy just that file like this
+\f[V]test.jpg\f[R], then you could copy just that file like this
 .IP
 .nf
 \f[C]
@@ -16554,8 +16570,8 @@ rclone copy remote:test.jpg /tmp/download
 \f[R]
 .fi
 .PP
-The file \f[C]test.jpg\f[R] will be placed inside
-\f[C]/tmp/download\f[R].
+The file \f[V]test.jpg\f[R] will be placed inside
+\f[V]/tmp/download\f[R].
 .PP
 This is equivalent to specifying
 .IP
@@ -16565,7 +16581,7 @@ rclone copy --files-from /tmp/files remote: /tmp/download
 \f[R]
 .fi
 .PP
-Where \f[C]/tmp/files\f[R] contains the single line
+Where \f[V]/tmp/files\f[R] contains the single line
 .IP
 .nf
 \f[C]
@@ -16573,9 +16589,9 @@ test.jpg
 \f[R]
 .fi
 .PP
-It is recommended to use \f[C]copy\f[R] when copying individual files,
-not \f[C]sync\f[R].
-They have pretty much the same effect but \f[C]copy\f[R] will use a lot
+It is recommended to use \f[V]copy\f[R] when copying individual files,
+not \f[V]sync\f[R].
+They have pretty much the same effect but \f[V]copy\f[R] will use a lot
 less memory.
 .SS Syntax of remote paths
 .PP
@@ -16584,31 +16600,31 @@ The syntax of the paths passed to the rclone command are as follows.
 .PP
 This refers to the local file system.
 .PP
-On Windows \f[C]\[rs]\f[R] may be used instead of \f[C]/\f[R] in local
-paths \f[B]only\f[R], non local paths must use \f[C]/\f[R].
+On Windows \f[V]\[rs]\f[R] may be used instead of \f[V]/\f[R] in local
+paths \f[B]only\f[R], non local paths must use \f[V]/\f[R].
 See local filesystem (https://rclone.org/local/#paths-on-windows)
 documentation for more about Windows-specific paths.
 .PP
-These paths needn\[aq]t start with a leading \f[C]/\f[R] - if they
+These paths needn\[aq]t start with a leading \f[V]/\f[R] - if they
 don\[aq]t then they will be relative to the current directory.
 .SS remote:path/to/dir
 .PP
-This refers to a directory \f[C]path/to/dir\f[R] on \f[C]remote:\f[R] as
-defined in the config file (configured with \f[C]rclone config\f[R]).
+This refers to a directory \f[V]path/to/dir\f[R] on \f[V]remote:\f[R] as
+defined in the config file (configured with \f[V]rclone config\f[R]).
 .SS remote:/path/to/dir
 .PP
 On most backends this is refers to the same directory as
-\f[C]remote:path/to/dir\f[R] and that format should be preferred.
+\f[V]remote:path/to/dir\f[R] and that format should be preferred.
 On a very small number of remotes (FTP, SFTP, Dropbox for business) this
 will refer to a different directory.
-On these, paths without a leading \f[C]/\f[R] will refer to your
-\[dq]home\[dq] directory and paths with a leading \f[C]/\f[R] will refer
+On these, paths without a leading \f[V]/\f[R] will refer to your
+\[dq]home\[dq] directory and paths with a leading \f[V]/\f[R] will refer
 to the root.
 .SS :backend:path/to/dir
 .PP
 This is an advanced form for creating remotes on the fly.
-\f[C]backend\f[R] should be the name or prefix of a backend (the
-\f[C]type\f[R] in the config file) and all the configuration for the
+\f[V]backend\f[R] should be the name or prefix of a backend (the
+\f[V]type\f[R] in the config file) and all the configuration for the
 backend should be provided on the command line (or in environment
 variables).
 .PP
@@ -16621,7 +16637,7 @@ rclone lsd --http-url https://pub.rclone.org :http:
 .fi
 .PP
 To list all the directories in the root of
-\f[C]https://pub.rclone.org/\f[R].
+\f[V]https://pub.rclone.org/\f[R].
 .IP
 .nf
 \f[C]
@@ -16630,7 +16646,7 @@ rclone lsf --http-url https://example.com :http:path/to/dir
 .fi
 .PP
 To list files and directories in
-\f[C]https://example.com/path/to/dir/\f[R]
+\f[V]https://example.com/path/to/dir/\f[R]
 .IP
 .nf
 \f[C]
@@ -16639,7 +16655,7 @@ rclone copy --http-url https://example.com :http:path/to/dir /tmp/dir
 .fi
 .PP
 To copy files and directories in
-\f[C]https://example.com/path/to/dir\f[R] to \f[C]/tmp/dir\f[R].
+\f[V]https://example.com/path/to/dir\f[R] to \f[V]/tmp/dir\f[R].
 .IP
 .nf
 \f[C]
@@ -16647,13 +16663,13 @@ rclone copy --sftp-host example.com :sftp:path/to/dir /tmp/dir
 \f[R]
 .fi
 .PP
-To copy files and directories from \f[C]example.com\f[R] in the relative
-directory \f[C]path/to/dir\f[R] to \f[C]/tmp/dir\f[R] using sftp.
+To copy files and directories from \f[V]example.com\f[R] in the relative
+directory \f[V]path/to/dir\f[R] to \f[V]/tmp/dir\f[R] using sftp.
 .SS Connection strings
 .PP
 The above examples can also be written using a connection string syntax,
 so instead of providing the arguments as command line parameters
-\f[C]--http-url https://pub.rclone.org\f[R] they are provided as part of
+\f[V]--http-url https://pub.rclone.org\f[R] they are provided as part of
 the remote specification as a kind of connection string.
 .IP
 .nf
@@ -16668,8 +16684,8 @@ rclone copy :sftp,host=example.com:path/to/dir /tmp/dir
 These can apply to modify existing remotes as well as create new remotes
 with the on the fly syntax.
 This example is equivalent to adding the
-\f[C]--drive-shared-with-me\f[R] parameter to the remote
-\f[C]gdrive:\f[R].
+\f[V]--drive-shared-with-me\f[R] parameter to the remote
+\f[V]gdrive:\f[R].
 .IP
 .nf
 \f[C]
@@ -16682,7 +16698,7 @@ it only applies to the remote, not to all the remotes of that type of
 the command line.
 A common confusion is this attempt to copy a file shared on google drive
 to the normal drive which \f[B]does not work\f[R] because the
-\f[C]--drive-shared-with-me\f[R] flag applies to both the source and the
+\f[V]--drive-shared-with-me\f[R] flag applies to both the source and the
 destination.
 .IP
 .nf
@@ -16703,7 +16719,7 @@ Note that the connection string only affects the options of the
 immediate backend.
 If for example gdriveCrypt is a crypt based on gdrive, then the
 following command \f[B]will not work\f[R] as intended, because
-\f[C]shared_with_me\f[R] is ignored by the crypt backend:
+\f[V]shared_with_me\f[R] is ignored by the crypt backend:
 .IP
 .nf
 \f[C]
@@ -16720,8 +16736,8 @@ remote,parameter=value,parameter2=value2:path/to/dir
 \f[R]
 .fi
 .PP
-If the \f[C]parameter\f[R] has a \f[C]:\f[R] or \f[C],\f[R] then it must
-be placed in quotes \f[C]\[dq]\f[R] or \f[C]\[aq]\f[R], so
+If the \f[V]parameter\f[R] has a \f[V]:\f[R] or \f[V],\f[R] then it must
+be placed in quotes \f[V]\[dq]\f[R] or \f[V]\[aq]\f[R], so
 .IP
 .nf
 \f[C]
@@ -16739,11 +16755,11 @@ remote,parameter=\[dq]with\[dq]\[dq]quote\[dq],parameter2=\[aq]with\[aq]\[aq]quo
 \f[R]
 .fi
 .PP
-This will make \f[C]parameter\f[R] be \f[C]with\[dq]quote\f[R] and
-\f[C]parameter2\f[R] be \f[C]with\[aq]quote\f[R].
+This will make \f[V]parameter\f[R] be \f[V]with\[dq]quote\f[R] and
+\f[V]parameter2\f[R] be \f[V]with\[aq]quote\f[R].
 .PP
-If you leave off the \f[C]=parameter\f[R] then rclone will substitute
-\f[C]=true\f[R] which works very well with flags.
+If you leave off the \f[V]=parameter\f[R] then rclone will substitute
+\f[V]=true\f[R] which works very well with flags.
 For example, to use s3 configured in the environment you could use:
 .IP
 .nf
@@ -16761,12 +16777,12 @@ rclone lsd :s3,env_auth=true:
 .fi
 .PP
 Note that on the command line you might need to surround these
-connection strings with \f[C]\[dq]\f[R] or \f[C]\[aq]\f[R] to stop the
+connection strings with \f[V]\[dq]\f[R] or \f[V]\[aq]\f[R] to stop the
 shell interpreting any special characters within them.
 .PP
 If you are a shell master then you\[aq]ll know which strings are OK and
 which aren\[aq]t, but if you aren\[aq]t sure then enclose them in
-\f[C]\[dq]\f[R] and use \f[C]\[aq]\f[R] as the inside quote.
+\f[V]\[dq]\f[R] and use \f[V]\[aq]\f[R] as the inside quote.
 This syntax works on all OSes.
 .IP
 .nf
@@ -16776,9 +16792,9 @@ rclone copy \[dq]:http,url=\[aq]https://example.com\[aq]:path/to/dir\[dq] /tmp/d
 .fi
 .PP
 On Linux/macOS some characters are still interpreted inside
-\f[C]\[dq]\f[R] strings in the shell (notably \f[C]\[rs]\f[R] and
-\f[C]$\f[R] and \f[C]\[dq]\f[R]) so if your strings contain those you
-can swap the roles of \f[C]\[dq]\f[R] and \f[C]\[aq]\f[R] thus.
+\f[V]\[dq]\f[R] strings in the shell (notably \f[V]\[rs]\f[R] and
+\f[V]$\f[R] and \f[V]\[dq]\f[R]) so if your strings contain those you
+can swap the roles of \f[V]\[dq]\f[R] and \f[V]\[aq]\f[R] thus.
 (This syntax does not work on Windows.)
 .IP
 .nf
@@ -16829,9 +16845,9 @@ DEBUG : :s3: detected overridden config - adding \[dq]{YTu53}\[dq] suffix to nam
 .SS Valid remote names
 .PP
 Remote names are case sensitive, and must adhere to the following rules:
-- May contain number, letter, \f[C]_\f[R], \f[C]-\f[R], \f[C].\f[R],
-\f[C]+\f[R], \f[C]\[at]\f[R] and space.
-- May not start with \f[C]-\f[R] or space.
+- May contain number, letter, \f[V]_\f[R], \f[V]-\f[R], \f[V].\f[R],
+\f[V]+\f[R], \f[V]\[at]\f[R] and space.
+- May not start with \f[V]-\f[R] or space.
 - May not end with space.
 .PP
 Starting with rclone version 1.61, any Unicode numbers and letters are
@@ -16845,8 +16861,8 @@ uses a non-Unicode character set - defined by the so-called \[dq]code
 page\[dq].
 .PP
 Do not use single character names on Windows as it creates ambiguity
-with Windows drives\[aq] names, e.g.: remote called \f[C]C\f[R] is
-indistinguishable from \f[C]C\f[R] drive.
+with Windows drives\[aq] names, e.g.: remote called \f[V]C\f[R] is
+indistinguishable from \f[V]C\f[R] drive.
 Rclone will always assume that single letter name refers to a drive.
 .SS Quoting and the shell
 .PP
@@ -16859,9 +16875,10 @@ rules
 .SS Linux / OSX
 .PP
 If your names have spaces or shell metacharacters (e.g.
-\f[C]*\f[R], \f[C]?\f[R], \f[C]$\f[R], \f[C]\[aq]\f[R], \f[C]\[dq]\f[R],
-etc.) then you must quote them.
-Use single quotes \f[C]\[aq]\f[R] by default.
+\f[V]*\f[R], \f[V]?\f[R], \f[V]$\f[R], \f[V]\[aq]\f[R], \f[V]\[dq]\f[R],
+etc.)
+then you must quote them.
+Use single quotes \f[V]\[aq]\f[R] by default.
 .IP
 .nf
 \f[C]
@@ -16869,8 +16886,8 @@ rclone copy \[aq]Important files?\[aq] remote:backup
 \f[R]
 .fi
 .PP
-If you want to send a \f[C]\[aq]\f[R] you will need to use
-\f[C]\[dq]\f[R], e.g.
+If you want to send a \f[V]\[aq]\f[R] you will need to use
+\f[V]\[dq]\f[R], e.g.
 .IP
 .nf
 \f[C]
@@ -16882,7 +16899,7 @@ The rules for quoting metacharacters are complicated and if you want the
 full details you\[aq]ll have to consult the manual page for your shell.
 .SS Windows
 .PP
-If your names have spaces in you need to put them in \f[C]\[dq]\f[R],
+If your names have spaces in you need to put them in \f[V]\[dq]\f[R],
 e.g.
 .IP
 .nf
@@ -16899,17 +16916,17 @@ If you are using the root directory on its own then don\[aq]t quote it
 rclone copy E:\[rs] remote:backup
 \f[R]
 .fi
-.SS Copying files or directories with \f[C]:\f[R] in the names
+.SS Copying files or directories with \f[V]:\f[R] in the names
 .PP
-rclone uses \f[C]:\f[R] to mark a remote name.
+rclone uses \f[V]:\f[R] to mark a remote name.
 This is, however, a valid filename component in non-Windows OSes.
-The remote name parser will only search for a \f[C]:\f[R] up to the
-first \f[C]/\f[R] so if you need to act on a file or directory like this
-then use the full path starting with a \f[C]/\f[R], or use \f[C]./\f[R]
+The remote name parser will only search for a \f[V]:\f[R] up to the
+first \f[V]/\f[R] so if you need to act on a file or directory like this
+then use the full path starting with a \f[V]/\f[R], or use \f[V]./\f[R]
 as a current directory prefix.
 .PP
-So to sync a directory called \f[C]sync:me\f[R] to a remote called
-\f[C]remote:\f[R] use
+So to sync a directory called \f[V]sync:me\f[R] to a remote called
+\f[V]remote:\f[R] use
 .IP
 .nf
 \f[C]
@@ -16942,15 +16959,15 @@ rclone copy s3:oldbucket s3:newbucket
 \f[R]
 .fi
 .PP
-Will copy the contents of \f[C]oldbucket\f[R] to \f[C]newbucket\f[R]
+Will copy the contents of \f[V]oldbucket\f[R] to \f[V]newbucket\f[R]
 without downloading and re-uploading.
 .PP
 Remotes which don\[aq]t support server-side copy \f[B]will\f[R] download
 and re-upload in this case.
 .PP
-Server side copies are used with \f[C]sync\f[R] and \f[C]copy\f[R] and
-will be identified in the log when using the \f[C]-v\f[R] flag.
-The \f[C]move\f[R] command may also use them if remote doesn\[aq]t
+Server side copies are used with \f[V]sync\f[R] and \f[V]copy\f[R] and
+will be identified in the log when using the \f[V]-v\f[R] flag.
+The \f[V]move\f[R] command may also use them if remote doesn\[aq]t
 support server-side move directly.
 This is done by issuing a server-side copy then a delete which is much
 quicker than a download and re-upload.
@@ -16974,7 +16991,7 @@ Normally rclone only preserves the modification time and the content
 (MIME) type where possible.
 .PP
 Rclone supports preserving all the available metadata on files and
-directories when using the \f[C]--metadata\f[R] or \f[C]-M\f[R] flag.
+directories when using the \f[V]--metadata\f[R] or \f[V]-M\f[R] flag.
 .PP
 Exactly what metadata is supported and what that support means depends
 on the backend.
@@ -16992,15 +17009,15 @@ be re-uploaded.
 If the metadata subsequently changes on the source object without
 changing the object itself then it won\[aq]t be synced to the
 destination object.
-This is in line with the way rclone syncs \f[C]Content-Type\f[R] without
-the \f[C]--metadata\f[R] flag.
+This is in line with the way rclone syncs \f[V]Content-Type\f[R] without
+the \f[V]--metadata\f[R] flag.
 .PP
-Using \f[C]--metadata\f[R] when syncing from local to local will
+Using \f[V]--metadata\f[R] when syncing from local to local will
 preserve file attributes such as file mode, owner, extended attributes
 (not Windows).
 .PP
 Note that arbitrary metadata may be added to objects using the
-\f[C]--metadata-set key=value\f[R] flag when the object is first
+\f[V]--metadata-set key=value\f[R] flag when the object is first
 uploaded.
 This flag can be repeated as many times as necessary.
 .PP
@@ -17008,21 +17025,21 @@ The --metadata-mapper flag can be used to pass the name of a program in
 which can transform metadata when it is being copied from source to
 destination.
 .PP
-Rclone supports \f[C]--metadata-set\f[R] and \f[C]--metadata-mapper\f[R]
-when doing sever side \f[C]Move\f[R] and server side \f[C]Copy\f[R], but
-not when doing server side \f[C]DirMove\f[R] (renaming a directory) as
+Rclone supports \f[V]--metadata-set\f[R] and \f[V]--metadata-mapper\f[R]
+when doing sever side \f[V]Move\f[R] and server side \f[V]Copy\f[R], but
+not when doing server side \f[V]DirMove\f[R] (renaming a directory) as
 this would involve recursing into the directory.
-Note that you can disable \f[C]DirMove\f[R] with
-\f[C]--disable DirMove\f[R] and rclone will revert back to using
-\f[C]Move\f[R] for each individual object where \f[C]--metadata-set\f[R]
-and \f[C]--metadata-mapper\f[R] are supported.
+Note that you can disable \f[V]DirMove\f[R] with
+\f[V]--disable DirMove\f[R] and rclone will revert back to using
+\f[V]Move\f[R] for each individual object where \f[V]--metadata-set\f[R]
+and \f[V]--metadata-mapper\f[R] are supported.
 .SS Types of metadata
 .PP
 Metadata is divided into two type.
 System metadata and User metadata.
 .PP
 Metadata which the backend uses itself is called system metadata.
-For example on the local backend the system metadata \f[C]uid\f[R] will
+For example on the local backend the system metadata \f[V]uid\f[R] will
 store the user ID of the file when used on a unix based platform.
 .PP
 Arbitrary metadata is called user metadata and this can be set however
@@ -17032,11 +17049,11 @@ When objects are copied from backend to backend, they will attempt to
 interpret system metadata if it is supplied.
 Metadata may change from being user metadata to system metadata as
 objects are copied between different backends.
-For example copying an object from s3 sets the \f[C]content-type\f[R]
+For example copying an object from s3 sets the \f[V]content-type\f[R]
 metadata.
-In a backend which understands this (like \f[C]azureblob\f[R]) this will
+In a backend which understands this (like \f[V]azureblob\f[R]) this will
 become the Content-Type of the object.
-In a backend which doesn\[aq]t understand this (like the \f[C]local\f[R]
+In a backend which doesn\[aq]t understand this (like the \f[V]local\f[R]
 backend) this will become user metadata.
 However should the local object be copied back to s3, the Content-Type
 will be set correctly.
@@ -17054,8 +17071,8 @@ further in the future).
 .IP \[bu] 2
 must be lower case
 .IP \[bu] 2
-may be \f[C]a-z\f[R] \f[C]0-9\f[R] containing \f[C].\f[R] \f[C]-\f[R] or
-\f[C]_\f[R]
+may be \f[V]a-z\f[R] \f[V]0-9\f[R] containing \f[V].\f[R] \f[V]-\f[R] or
+\f[V]_\f[R]
 .IP \[bu] 2
 length is backend dependent
 .PP
@@ -17193,9 +17210,9 @@ text/plain
 T}
 .TE
 .PP
-The metadata keys \f[C]mtime\f[R] and \f[C]content-type\f[R] will take
+The metadata keys \f[V]mtime\f[R] and \f[V]content-type\f[R] will take
 precedence if supplied in the metadata over reading the
-\f[C]Content-Type\f[R] or modification time of the source object.
+\f[V]Content-Type\f[R] or modification time of the source object.
 .PP
 Hashes are not included in system metadata as there is a well defined
 way of reading those already.
@@ -17204,14 +17221,14 @@ way of reading those already.
 Rclone has a number of options to control its behaviour.
 .PP
 Options that take parameters can have the values passed in two ways,
-\f[C]--option=value\f[R] or \f[C]--option value\f[R].
+\f[V]--option=value\f[R] or \f[V]--option value\f[R].
 However boolean (true/false) options behave slightly differently to the
-other options in that \f[C]--boolean\f[R] sets the option to
-\f[C]true\f[R] and the absence of the flag sets it to \f[C]false\f[R].
-It is also possible to specify \f[C]--boolean=false\f[R] or
-\f[C]--boolean=true\f[R].
-Note that \f[C]--boolean false\f[R] is not valid - this is parsed as
-\f[C]--boolean\f[R] and the \f[C]false\f[R] is parsed as an extra
+other options in that \f[V]--boolean\f[R] sets the option to
+\f[V]true\f[R] and the absence of the flag sets it to \f[V]false\f[R].
+It is also possible to specify \f[V]--boolean=false\f[R] or
+\f[V]--boolean=true\f[R].
+Note that \f[V]--boolean false\f[R] is not valid - this is parsed as
+\f[V]--boolean\f[R] and the \f[V]false\f[R] is parsed as an extra
 command line argument for rclone.
 .SS Time or duration options
 .PP
@@ -17223,48 +17240,48 @@ with optional fraction and a unit suffix, such as \[dq]300ms\[dq],
 \[dq]-1.5h\[dq] or \[dq]2h45m\[dq].
 Default units are seconds or the following abbreviations are valid:
 .IP \[bu] 2
-\f[C]ms\f[R] - Milliseconds
+\f[V]ms\f[R] - Milliseconds
 .IP \[bu] 2
-\f[C]s\f[R] - Seconds
+\f[V]s\f[R] - Seconds
 .IP \[bu] 2
-\f[C]m\f[R] - Minutes
+\f[V]m\f[R] - Minutes
 .IP \[bu] 2
-\f[C]h\f[R] - Hours
+\f[V]h\f[R] - Hours
 .IP \[bu] 2
-\f[C]d\f[R] - Days
+\f[V]d\f[R] - Days
 .IP \[bu] 2
-\f[C]w\f[R] - Weeks
+\f[V]w\f[R] - Weeks
 .IP \[bu] 2
-\f[C]M\f[R] - Months
+\f[V]M\f[R] - Months
 .IP \[bu] 2
-\f[C]y\f[R] - Years
+\f[V]y\f[R] - Years
 .PP
 These can also be specified as an absolute time in the following
 formats:
 .IP \[bu] 2
 RFC3339 - e.g.
-\f[C]2006-01-02T15:04:05Z\f[R] or \f[C]2006-01-02T15:04:05+07:00\f[R]
+\f[V]2006-01-02T15:04:05Z\f[R] or \f[V]2006-01-02T15:04:05+07:00\f[R]
 .IP \[bu] 2
-ISO8601 Date and time, local timezone - \f[C]2006-01-02T15:04:05\f[R]
+ISO8601 Date and time, local timezone - \f[V]2006-01-02T15:04:05\f[R]
 .IP \[bu] 2
-ISO8601 Date and time, local timezone - \f[C]2006-01-02 15:04:05\f[R]
+ISO8601 Date and time, local timezone - \f[V]2006-01-02 15:04:05\f[R]
 .IP \[bu] 2
-ISO8601 Date - \f[C]2006-01-02\f[R] (YYYY-MM-DD)
+ISO8601 Date - \f[V]2006-01-02\f[R] (YYYY-MM-DD)
 .SS Size options
 .PP
 Options which use SIZE use KiB (multiples of 1024 bytes) by default.
-However, a suffix of \f[C]B\f[R] for Byte, \f[C]K\f[R] for KiB,
-\f[C]M\f[R] for MiB, \f[C]G\f[R] for GiB, \f[C]T\f[R] for TiB and
-\f[C]P\f[R] for PiB may be used.
+However, a suffix of \f[V]B\f[R] for Byte, \f[V]K\f[R] for KiB,
+\f[V]M\f[R] for MiB, \f[V]G\f[R] for GiB, \f[V]T\f[R] for TiB and
+\f[V]P\f[R] for PiB may be used.
 These are the binary units, e.g.
 1, 2**10, 2**20, 2**30 respectively.
 .SS --backup-dir=DIR
 .PP
-When using \f[C]sync\f[R], \f[C]copy\f[R] or \f[C]move\f[R] any files
+When using \f[V]sync\f[R], \f[V]copy\f[R] or \f[V]move\f[R] any files
 which would have been overwritten or deleted are moved in their original
 hierarchy into this directory.
 .PP
-If \f[C]--suffix\f[R] is set, then the moved files will have the suffix
+If \f[V]--suffix\f[R] is set, then the moved files will have the suffix
 added to them.
 If there is a file with the same path (after the suffix has been added)
 in DIR, then it will be overwritten.
@@ -17282,16 +17299,16 @@ rclone sync --interactive /path/to/local remote:current --backup-dir remote:old
 \f[R]
 .fi
 .PP
-will sync \f[C]/path/to/local\f[R] to \f[C]remote:current\f[R], but for
+will sync \f[V]/path/to/local\f[R] to \f[V]remote:current\f[R], but for
 any files which would have been updated or deleted will be stored in
-\f[C]remote:old\f[R].
+\f[V]remote:old\f[R].
 .PP
 If running rclone from a script you might want to use today\[aq]s date
-as the directory name passed to \f[C]--backup-dir\f[R] to store the old
-files, or you might want to pass \f[C]--suffix\f[R] with today\[aq]s
+as the directory name passed to \f[V]--backup-dir\f[R] to store the old
+files, or you might want to pass \f[V]--suffix\f[R] with today\[aq]s
 date.
 .PP
-See \f[C]--compare-dest\f[R] and \f[C]--copy-dest\f[R].
+See \f[V]--compare-dest\f[R] and \f[V]--copy-dest\f[R].
 .SS --bind string
 .PP
 Local address to bind to for outgoing connections.
@@ -17300,8 +17317,8 @@ host name.
 If the host name doesn\[aq]t resolve or resolves to more than one IP
 address it will give an error.
 .PP
-You can use \f[C]--bind 0.0.0.0\f[R] to force rclone to use IPv4
-addresses and \f[C]--bind ::0\f[R] to force rclone to use IPv6
+You can use \f[V]--bind 0.0.0.0\f[R] to force rclone to use IPv4
+addresses and \f[V]--bind ::0\f[R] to force rclone to use IPv6
 addresses.
 .SS --bwlimit=BANDWIDTH_SPEC
 .PP
@@ -17319,10 +17336,10 @@ would mean limit the upload and download bandwidth to 10 MiB/s.
 second.
 To use a single limit, specify the desired bandwidth in KiB/s, or use a
 suffix B|K|M|G|T|P.
-The default is \f[C]0\f[R] which means to not limit bandwidth.
+The default is \f[V]0\f[R] which means to not limit bandwidth.
 .PP
 The upload and download bandwidth can be specified separately, as
-\f[C]--bwlimit UP:DOWN\f[R], so
+\f[V]--bwlimit UP:DOWN\f[R], so
 .IP
 .nf
 \f[C]
@@ -17350,17 +17367,17 @@ run of the rclone binary.
 It is also possible to specify a \[dq]timetable\[dq] of limits, which
 will cause certain limits to be applied at certain times.
 To specify a timetable, format your entries as
-\f[C]WEEKDAY-HH:MM,BANDWIDTH WEEKDAY-HH:MM,BANDWIDTH...\f[R] where:
-\f[C]WEEKDAY\f[R] is optional element.
+\f[V]WEEKDAY-HH:MM,BANDWIDTH WEEKDAY-HH:MM,BANDWIDTH...\f[R] where:
+\f[V]WEEKDAY\f[R] is optional element.
 .IP \[bu] 2
-\f[C]BANDWIDTH\f[R] can be a single number, e.g.\f[C]100k\f[R] or a pair
-of numbers for upload:download, e.g.\f[C]10M:1M\f[R].
+\f[V]BANDWIDTH\f[R] can be a single number, e.g.\f[V]100k\f[R] or a pair
+of numbers for upload:download, e.g.\f[V]10M:1M\f[R].
 .IP \[bu] 2
-\f[C]WEEKDAY\f[R] can be written as the whole word or only using the
+\f[V]WEEKDAY\f[R] can be written as the whole word or only using the
 first 3 characters.
 It is optional.
 .IP \[bu] 2
-\f[C]HH:MM\f[R] is an hour from 00:00 to 23:59.
+\f[V]HH:MM\f[R] is an hour from 00:00 to 23:59.
 .PP
 Entries can be separated by spaces or semicolons.
 .PP
@@ -17371,10 +17388,10 @@ An example of a typical timetable to avoid link saturation during
 daytime working hours could be:
 .PP
 Using spaces as separators:
-\f[C]--bwlimit \[dq]08:00,512k 12:00,10M 13:00,512k 18:00,30M 23:00,off\[dq]\f[R]
+\f[V]--bwlimit \[dq]08:00,512k 12:00,10M 13:00,512k 18:00,30M 23:00,off\[dq]\f[R]
 .PP
 Using semicolons as separators:
-\f[C]--bwlimit \[dq]08:00,512k;12:00,10M;13:00,512k;18:00,30M;23:00,off\[dq]\f[R]
+\f[V]--bwlimit \[dq]08:00,512k;12:00,10M;13:00,512k;18:00,30M;23:00,off\[dq]\f[R]
 .PP
 In these examples, the transfer bandwidth will be set to 512 KiB/s at
 8am every day.
@@ -17383,13 +17400,13 @@ At 6pm, the bandwidth limit will be set to 30 MiB/s, and at 11pm it will
 be completely disabled (full speed).
 Anything between 11pm and 8am will remain unlimited.
 .PP
-An example of timetable with \f[C]WEEKDAY\f[R] could be:
+An example of timetable with \f[V]WEEKDAY\f[R] could be:
 .PP
 Using spaces as separators:
-\f[C]--bwlimit \[dq]Mon-00:00,512 Fri-23:59,10M Sat-10:00,1M Sun-20:00,off\[dq]\f[R]
+\f[V]--bwlimit \[dq]Mon-00:00,512 Fri-23:59,10M Sat-10:00,1M Sun-20:00,off\[dq]\f[R]
 .PP
 Using semicolons as separators:
-\f[C]--bwlimit \[dq]Mon-00:00,512;Fri-23:59,10M;Sat-10:00,1M;Sun-20:00,off\[dq]\f[R]
+\f[V]--bwlimit \[dq]Mon-00:00,512;Fri-23:59,10M;Sat-10:00,1M;Sun-20:00,off\[dq]\f[R]
 .PP
 It means that, the transfer bandwidth will be set to 512 KiB/s on
 Monday.
@@ -17397,31 +17414,32 @@ It will rise to 10 MiB/s before the end of Friday.
 At 10:00 on Saturday it will be set to 1 MiB/s.
 From 20:00 on Sunday it will be unlimited.
 .PP
-Timeslots without \f[C]WEEKDAY\f[R] are extended to the whole week.
+Timeslots without \f[V]WEEKDAY\f[R] are extended to the whole week.
 So this example:
 .PP
-\f[C]--bwlimit \[dq]Mon-00:00,512 12:00,1M Sun-20:00,off\[dq]\f[R]
+\f[V]--bwlimit \[dq]Mon-00:00,512 12:00,1M Sun-20:00,off\[dq]\f[R]
 .PP
 Is equivalent to this:
 .PP
-\f[C]--bwlimit \[dq]Mon-00:00,512Mon-12:00,1M Tue-12:00,1M Wed-12:00,1M Thu-12:00,1M Fri-12:00,1M Sat-12:00,1M Sun-12:00,1M Sun-20:00,off\[dq]\f[R]
+\f[V]--bwlimit \[dq]Mon-00:00,512Mon-12:00,1M Tue-12:00,1M Wed-12:00,1M Thu-12:00,1M Fri-12:00,1M Sat-12:00,1M Sun-12:00,1M Sun-20:00,off\[dq]\f[R]
 .PP
 Bandwidth limit apply to the data transfer for all backends.
 For most backends the directory listing bandwidth is also included
-(exceptions being the non HTTP backends, \f[C]ftp\f[R], \f[C]sftp\f[R]
-and \f[C]storj\f[R]).
+(exceptions being the non HTTP backends, \f[V]ftp\f[R], \f[V]sftp\f[R]
+and \f[V]storj\f[R]).
 .PP
 Note that the units are \f[B]Byte/s\f[R], not \f[B]bit/s\f[R].
 Typically connections are measured in bit/s - to convert divide by 8.
 For example, let\[aq]s say you have a 10 Mbit/s connection and you wish
 rclone to use half of it - 5 Mbit/s.
-This is 5/8 = 0.625 MiB/s so you would use a \f[C]--bwlimit 0.625M\f[R]
+This is 5/8 = 0.625 MiB/s so you would use a \f[V]--bwlimit 0.625M\f[R]
 parameter for rclone.
 .PP
-On Unix systems (Linux, macOS, \&...) the bandwidth limiter can be
-toggled by sending a \f[C]SIGUSR2\f[R] signal to rclone.
+On Unix systems (Linux, macOS, \&...)
+the bandwidth limiter can be toggled by sending a \f[V]SIGUSR2\f[R]
+signal to rclone.
 This allows to remove the limitations of a long running rclone transfer
-and to restore it back to the value specified with \f[C]--bwlimit\f[R]
+and to restore it back to the value specified with \f[V]--bwlimit\f[R]
 quickly when needed.
 Assuming there is only one rclone instance running, you can toggle the
 limiter like this:
@@ -17443,7 +17461,7 @@ rclone rc core/bwlimit rate=1M
 .SS --bwlimit-file=BANDWIDTH_SPEC
 .PP
 This option controls per file bandwidth limit.
-For the options see the \f[C]--bwlimit\f[R] flag.
+For the options see the \f[V]--bwlimit\f[R] flag.
 .PP
 For example use this to allow no transfers to be faster than 1 MiB/s
 .IP
@@ -17453,21 +17471,21 @@ For example use this to allow no transfers to be faster than 1 MiB/s
 \f[R]
 .fi
 .PP
-This can be used in conjunction with \f[C]--bwlimit\f[R].
+This can be used in conjunction with \f[V]--bwlimit\f[R].
 .PP
 Note that if a schedule is provided the file will use the schedule in
 effect at the start of the transfer.
 .SS --buffer-size=SIZE
 .PP
 Use this sized buffer to speed up file transfers.
-Each \f[C]--transfer\f[R] will use this much memory for buffering.
+Each \f[V]--transfer\f[R] will use this much memory for buffering.
 .PP
-When using \f[C]mount\f[R] or \f[C]cmount\f[R] each open file descriptor
+When using \f[V]mount\f[R] or \f[V]cmount\f[R] each open file descriptor
 will use this much memory for buffering.
 See the mount (https://rclone.org/commands/rclone_mount/#file-buffering)
 documentation for more details.
 .PP
-Set to \f[C]0\f[R] to disable the buffering for the minimum memory
+Set to \f[V]0\f[R] to disable the buffering for the minimum memory
 usage.
 .PP
 Note that the memory allocation of the buffers is influenced by the
@@ -17478,15 +17496,15 @@ Specify the directory rclone will use for caching, to override the
 default.
 .PP
 Default value is depending on operating system: - Windows
-\f[C]%LocalAppData%\[rs]rclone\f[R], if \f[C]LocalAppData\f[R] is
+\f[V]%LocalAppData%\[rs]rclone\f[R], if \f[V]LocalAppData\f[R] is
 defined.
-- macOS \f[C]$HOME/Library/Caches/rclone\f[R] if \f[C]HOME\f[R] is
+- macOS \f[V]$HOME/Library/Caches/rclone\f[R] if \f[V]HOME\f[R] is
 defined.
-- Unix \f[C]$XDG_CACHE_HOME/rclone\f[R] if \f[C]XDG_CACHE_HOME\f[R] is
-defined, else \f[C]$HOME/.cache/rclone\f[R] if \f[C]HOME\f[R] is
+- Unix \f[V]$XDG_CACHE_HOME/rclone\f[R] if \f[V]XDG_CACHE_HOME\f[R] is
+defined, else \f[V]$HOME/.cache/rclone\f[R] if \f[V]HOME\f[R] is
 defined.
-- Fallback (on all OS) to \f[C]$TMPDIR/rclone\f[R], where
-\f[C]TMPDIR\f[R] is the value from --temp-dir.
+- Fallback (on all OS) to \f[V]$TMPDIR/rclone\f[R], where
+\f[V]TMPDIR\f[R] is the value from --temp-dir.
 .PP
 You can use the config
 paths (https://rclone.org/commands/rclone_config_paths/) command to see
@@ -17499,8 +17517,8 @@ serve (https://rclone.org/commands/rclone_serve/), GUI and other parts
 of rclone.
 .SS --check-first
 .PP
-If this flag is set then in a \f[C]sync\f[R], \f[C]copy\f[R] or
-\f[C]move\f[R], rclone will do all the checks to see whether files need
+If this flag is set then in a \f[V]sync\f[R], \f[V]copy\f[R] or
+\f[V]move\f[R], rclone will do all the checks to see whether files need
 to be transferred before doing any of the transfers.
 Normally rclone would start running transfers as soon as possible.
 .PP
@@ -17508,24 +17526,24 @@ This flag can be useful on IO limited systems where transfers interfere
 with checking.
 .PP
 It can also be useful to ensure perfect ordering when using
-\f[C]--order-by\f[R].
+\f[V]--order-by\f[R].
 .PP
-If both \f[C]--check-first\f[R] and \f[C]--order-by\f[R] are set when
-doing \f[C]rclone move\f[R] then rclone will use the transfer thread to
+If both \f[V]--check-first\f[R] and \f[V]--order-by\f[R] are set when
+doing \f[V]rclone move\f[R] then rclone will use the transfer thread to
 delete source files which don\[aq]t need transferring.
 This will enable perfect ordering of the transfers and deletes but will
 cause the transfer stats to have more items in than expected.
 .PP
 Using this flag can use more memory as it effectively sets
-\f[C]--max-backlog\f[R] to infinite.
+\f[V]--max-backlog\f[R] to infinite.
 This means that all the info on the objects to transfer is held in
 memory before the transfers start.
 .SS --checkers=N
 .PP
 Originally controlling just the number of file checkers to run in
 parallel, e.g.
-by \f[C]rclone copy\f[R].
-Now a fairly universal parallelism control used by \f[C]rclone\f[R] in
+by \f[V]rclone copy\f[R].
+Now a fairly universal parallelism control used by \f[V]rclone\f[R] in
 several places.
 .PP
 Note: checkers do the equality checking of files during a sync.
@@ -17535,7 +17553,7 @@ are run in parallel.
 .PP
 The default is to run 8 checkers in parallel.
 However, in case of slow-reacting backends you may need to lower (rather
-than increase) this default by setting \f[C]--checkers\f[R] to 4 or less
+than increase) this default by setting \f[V]--checkers\f[R] to 4 or less
 threads.
 This is especially advised if you are experiencing backend server
 crashes during file checking phase (e.g.
@@ -17559,8 +17577,8 @@ Drive and Swift.
 For details of which remotes support which hash type see the table in
 the overview section (https://rclone.org/overview/).
 .PP
-Eg \f[C]rclone --checksum sync s3:/bucket swift:/bucket\f[R] would run
-much quicker than without the \f[C]--checksum\f[R] flag.
+Eg \f[V]rclone --checksum sync s3:/bucket swift:/bucket\f[R] would run
+much quicker than without the \f[V]--checksum\f[R] flag.
 .PP
 When using this flag, rclone won\[aq]t update mtimes of remote files if
 they are incorrect as it would normally.
@@ -17569,16 +17587,16 @@ they are incorrect as it would normally.
 Specify when colors (and other ANSI codes) should be added to the
 output.
 .PP
-\f[C]AUTO\f[R] (default) only allows ANSI codes when the output is a
+\f[V]AUTO\f[R] (default) only allows ANSI codes when the output is a
 terminal
 .PP
-\f[C]NEVER\f[R] never allow ANSI codes
+\f[V]NEVER\f[R] never allow ANSI codes
 .PP
-\f[C]ALWAYS\f[R] always add ANSI codes, regardless of the output format
+\f[V]ALWAYS\f[R] always add ANSI codes, regardless of the output format
 (terminal or file)
 .SS --compare-dest=DIR
 .PP
-When using \f[C]sync\f[R], \f[C]copy\f[R] or \f[C]move\f[R] DIR is
+When using \f[V]sync\f[R], \f[V]copy\f[R] or \f[V]move\f[R] DIR is
 checked in addition to the destination for files.
 If a file identical to the source is found that file is NOT copied from
 source.
@@ -17588,93 +17606,93 @@ backup.
 You must use the same remote as the destination of the sync.
 The compare directory must not overlap the destination directory.
 .PP
-See \f[C]--copy-dest\f[R] and \f[C]--backup-dir\f[R].
+See \f[V]--copy-dest\f[R] and \f[V]--backup-dir\f[R].
 .SS --config=CONFIG_FILE
 .PP
 Specify the location of the rclone configuration file, to override the
 default.
 E.g.
-\f[C]rclone config --config=\[dq]rclone.conf\[dq]\f[R].
+\f[V]rclone config --config=\[dq]rclone.conf\[dq]\f[R].
 .PP
 The exact default is a bit complex to describe, due to changes
 introduced through different versions of rclone while preserving
 backwards compatibility, but in most cases it is as simple as:
 .IP \[bu] 2
-\f[C]%APPDATA%/rclone/rclone.conf\f[R] on Windows
+\f[V]%APPDATA%/rclone/rclone.conf\f[R] on Windows
 .IP \[bu] 2
-\f[C]\[ti]/.config/rclone/rclone.conf\f[R] on other
+\f[V]\[ti]/.config/rclone/rclone.conf\f[R] on other
 .PP
 The complete logic is as follows: Rclone will look for an existing
 configuration file in any of the following locations, in priority order:
 .IP "1." 3
-\f[C]rclone.conf\f[R] (in program directory, where rclone executable is)
+\f[V]rclone.conf\f[R] (in program directory, where rclone executable is)
 .IP "2." 3
-\f[C]%APPDATA%/rclone/rclone.conf\f[R] (only on Windows)
+\f[V]%APPDATA%/rclone/rclone.conf\f[R] (only on Windows)
 .IP "3." 3
-\f[C]$XDG_CONFIG_HOME/rclone/rclone.conf\f[R] (on all systems, including
+\f[V]$XDG_CONFIG_HOME/rclone/rclone.conf\f[R] (on all systems, including
 Windows)
 .IP "4." 3
-\f[C]\[ti]/.config/rclone/rclone.conf\f[R] (see below for explanation of
+\f[V]\[ti]/.config/rclone/rclone.conf\f[R] (see below for explanation of
 \[ti] symbol)
 .IP "5." 3
-\f[C]\[ti]/.rclone.conf\f[R]
+\f[V]\[ti]/.rclone.conf\f[R]
 .PP
 If no existing configuration file is found, then a new one will be
 created in the following location:
 .IP \[bu] 2
 On Windows: Location 2 listed above, except in the unlikely event that
-\f[C]APPDATA\f[R] is not defined, then location 4 is used instead.
+\f[V]APPDATA\f[R] is not defined, then location 4 is used instead.
 .IP \[bu] 2
-On Unix: Location 3 if \f[C]XDG_CONFIG_HOME\f[R] is defined, else
+On Unix: Location 3 if \f[V]XDG_CONFIG_HOME\f[R] is defined, else
 location 4.
 .IP \[bu] 2
 Fallback to location 5 (on all OS), when the rclone directory cannot be
 created, but if also a home directory was not found then path
-\f[C].rclone.conf\f[R] relative to current working directory will be
+\f[V].rclone.conf\f[R] relative to current working directory will be
 used as a final resort.
 .PP
-The \f[C]\[ti]\f[R] symbol in paths above represent the home directory
+The \f[V]\[ti]\f[R] symbol in paths above represent the home directory
 of the current user on any OS, and the value is defined as following:
 .IP \[bu] 2
-On Windows: \f[C]%HOME%\f[R] if defined, else \f[C]%USERPROFILE%\f[R],
-or else \f[C]%HOMEDRIVE%\[rs]%HOMEPATH%\f[R].
+On Windows: \f[V]%HOME%\f[R] if defined, else \f[V]%USERPROFILE%\f[R],
+or else \f[V]%HOMEDRIVE%\[rs]%HOMEPATH%\f[R].
 .IP \[bu] 2
-On Unix: \f[C]$HOME\f[R] if defined, else by looking up current user in
+On Unix: \f[V]$HOME\f[R] if defined, else by looking up current user in
 OS-specific user database (e.g.
 passwd file), or else use the result from shell command
-\f[C]cd && pwd\f[R].
+\f[V]cd && pwd\f[R].
 .PP
-If you run \f[C]rclone config file\f[R] you will see where the default
+If you run \f[V]rclone config file\f[R] you will see where the default
 location is for you.
 .PP
-The fact that an existing file \f[C]rclone.conf\f[R] in the same
+The fact that an existing file \f[V]rclone.conf\f[R] in the same
 directory as the rclone executable is always preferred, means that it is
 easy to run in \[dq]portable\[dq] mode by downloading rclone executable
 to a writable directory and then create an empty file
-\f[C]rclone.conf\f[R] in the same directory.
+\f[V]rclone.conf\f[R] in the same directory.
 .PP
-If the location is set to empty string \f[C]\[dq]\[dq]\f[R] or path to a
-file with name \f[C]notfound\f[R], or the os null device represented by
-value \f[C]NUL\f[R] on Windows and \f[C]/dev/null\f[R] on Unix systems,
+If the location is set to empty string \f[V]\[dq]\[dq]\f[R] or path to a
+file with name \f[V]notfound\f[R], or the os null device represented by
+value \f[V]NUL\f[R] on Windows and \f[V]/dev/null\f[R] on Unix systems,
 then rclone will keep the config file in memory only.
 .PP
 The file format is basic
 INI (https://en.wikipedia.org/wiki/INI_file#Format): Sections of text,
-led by a \f[C][section]\f[R] header and followed by \f[C]key=value\f[R]
+led by a \f[V][section]\f[R] header and followed by \f[V]key=value\f[R]
 entries on separate lines.
 In rclone each remote is represented by its own section, where the
 section name defines the name of the remote.
-Options are specified as the \f[C]key=value\f[R] entries, where the key
-is the option name without the \f[C]--backend-\f[R] prefix, in lowercase
-and with \f[C]_\f[R] instead of \f[C]-\f[R].
+Options are specified as the \f[V]key=value\f[R] entries, where the key
+is the option name without the \f[V]--backend-\f[R] prefix, in lowercase
+and with \f[V]_\f[R] instead of \f[V]-\f[R].
 E.g.
-option \f[C]--mega-hard-delete\f[R] corresponds to key
-\f[C]hard_delete\f[R].
+option \f[V]--mega-hard-delete\f[R] corresponds to key
+\f[V]hard_delete\f[R].
 Only backend options can be specified.
-A special, and required, key \f[C]type\f[R] identifies the storage
+A special, and required, key \f[V]type\f[R] identifies the storage
 system (https://rclone.org/overview/), where the value is the internal
-lowercase name as returned by command \f[C]rclone help backends\f[R].
-Comments are indicated by \f[C];\f[R] or \f[C]#\f[R] at the beginning of
+lowercase name as returned by command \f[V]rclone help backends\f[R].
+Comments are indicated by \f[V];\f[R] or \f[V]#\f[R] at the beginning of
 a line.
 .PP
 Example:
@@ -17693,7 +17711,7 @@ obscured (https://rclone.org/commands/rclone_obscure/) form.
 Also, many storage systems uses token-based authentication instead of
 passwords, and this requires additional steps.
 It is easier, and safer, to use the interactive command
-\f[C]rclone config\f[R] instead of manually editing the configuration
+\f[V]rclone config\f[R] instead of manually editing the configuration
 file.
 .PP
 The configuration file will typically contain login information, and
@@ -17725,15 +17743,15 @@ symbolic link.
 .SS --contimeout=TIME
 .PP
 Set the connection timeout.
-This should be in go time format which looks like \f[C]5s\f[R] for 5
-seconds, \f[C]10m\f[R] for 10 minutes, or \f[C]3h30m\f[R].
+This should be in go time format which looks like \f[V]5s\f[R] for 5
+seconds, \f[V]10m\f[R] for 10 minutes, or \f[V]3h30m\f[R].
 .PP
 The connection timeout is the amount of time rclone will wait for a
 connection to go through to a remote object storage system.
-It is \f[C]1m\f[R] by default.
+It is \f[V]1m\f[R] by default.
 .SS --copy-dest=DIR
 .PP
-When using \f[C]sync\f[R], \f[C]copy\f[R] or \f[C]move\f[R] DIR is
+When using \f[V]sync\f[R], \f[V]copy\f[R] or \f[V]move\f[R] DIR is
 checked in addition to the destination for files.
 If a file identical to the source is found that file is server-side
 copied from DIR to the destination.
@@ -17743,13 +17761,13 @@ The remote in use must support server-side copy and you must use the
 same remote as the destination of the sync.
 The compare directory must not overlap the destination directory.
 .PP
-See \f[C]--compare-dest\f[R] and \f[C]--backup-dir\f[R].
+See \f[V]--compare-dest\f[R] and \f[V]--backup-dir\f[R].
 .SS --dedupe-mode MODE
 .PP
 Mode to run dedupe command in.
-One of \f[C]interactive\f[R], \f[C]skip\f[R], \f[C]first\f[R],
-\f[C]newest\f[R], \f[C]oldest\f[R], \f[C]rename\f[R].
-The default is \f[C]interactive\f[R].
+One of \f[V]interactive\f[R], \f[V]skip\f[R], \f[V]first\f[R],
+\f[V]newest\f[R], \f[V]oldest\f[R], \f[V]rename\f[R].
+The default is \f[V]interactive\f[R].
 .PD 0
 .P
 .PD
@@ -17760,12 +17778,12 @@ mean.
 If a file or directory does have a modification time rclone can read
 then rclone will display this fixed time instead.
 .PP
-The default is \f[C]2000-01-01 00:00:00 UTC\f[R].
+The default is \f[V]2000-01-01 00:00:00 UTC\f[R].
 This can be configured in any of the ways shown in the time or duration
 options.
 .PP
-For example \f[C]--default-time 2020-06-01\f[R] to set the default time
-to the 1st of June 2020 or \f[C]--default-time 0s\f[R] to set the
+For example \f[V]--default-time 2020-06-01\f[R] to set the default time
+to the 1st of June 2020 or \f[V]--default-time 0s\f[R] to set the
 default time to the time rclone started up.
 .SS --disable FEATURE,FEATURE,...
 .PP
@@ -17800,16 +17818,16 @@ See the overview features (https://rclone.org/overview/#features) and
 optional features (https://rclone.org/overview/#optional-features) to
 get an idea of which feature does what.
 .PP
-Note that some features can be set to \f[C]true\f[R] if they are
-\f[C]true\f[R]/\f[C]false\f[R] feature flag features by prefixing them
-with \f[C]!\f[R].
-For example the \f[C]CaseInsensitive\f[R] feature can be forced to
-\f[C]false\f[R] with \f[C]--disable CaseInsensitive\f[R] and forced to
-\f[C]true\f[R] with \f[C]--disable \[aq]!CaseInsensitive\[aq]\f[R].
+Note that some features can be set to \f[V]true\f[R] if they are
+\f[V]true\f[R]/\f[V]false\f[R] feature flag features by prefixing them
+with \f[V]!\f[R].
+For example the \f[V]CaseInsensitive\f[R] feature can be forced to
+\f[V]false\f[R] with \f[V]--disable CaseInsensitive\f[R] and forced to
+\f[V]true\f[R] with \f[V]--disable \[aq]!CaseInsensitive\[aq]\f[R].
 In general it isn\[aq]t a good idea doing this but it may be useful in
 extremis.
 .PP
-(Note that \f[C]!\f[R] is a shell command which you will need to escape
+(Note that \f[V]!\f[R] is a shell command which you will need to escape
 with single quotes or a backslash on unix like platforms.)
 .PP
 This flag can be useful for debugging and in exceptional circumstances
@@ -17851,7 +17869,7 @@ golang/go#42728 (https://github.com/golang/go/issues/42728)).
 .PP
 Do a trial run with no permanent changes.
 Use this to see what rclone would do without actually doing it.
-Useful when setting up the \f[C]sync\f[R] command which deletes files in
+Useful when setting up the \f[V]sync\f[R] command which deletes files in
 the destination.
 .SS --expect-continue-timeout=TIME
 .PP
@@ -17864,8 +17882,8 @@ Zero means no timeout and causes the body to be sent immediately,
 without waiting for the server to approve.
 This time does not include the time to send the request header.
 .PP
-The default is \f[C]1s\f[R].
-Set to \f[C]0\f[R] to disable.
+The default is \f[V]1s\f[R].
+Set to \f[V]0\f[R] to disable.
 .SS --error-on-no-transfer
 .PP
 By default, rclone will exit with return code 0 if there were no errors.
@@ -17883,23 +17901,23 @@ accordingly!
 Normally, a sync to a case insensitive dest (such as macOS / Windows)
 will not result in a matching filename if the source and dest filenames
 have casing differences but are otherwise identical.
-For example, syncing \f[C]hello.txt\f[R] to \f[C]HELLO.txt\f[R] will
-normally result in the dest filename remaining \f[C]HELLO.txt\f[R].
-If \f[C]--fix-case\f[R] is set, then \f[C]HELLO.txt\f[R] will be renamed
-to \f[C]hello.txt\f[R] to match the source.
+For example, syncing \f[V]hello.txt\f[R] to \f[V]HELLO.txt\f[R] will
+normally result in the dest filename remaining \f[V]HELLO.txt\f[R].
+If \f[V]--fix-case\f[R] is set, then \f[V]HELLO.txt\f[R] will be renamed
+to \f[V]hello.txt\f[R] to match the source.
 .PP
 NB: - directory names with incorrect casing will also be fixed -
-\f[C]--fix-case\f[R] will be ignored if \f[C]--immutable\f[R] is set -
-using \f[C]--local-case-sensitive\f[R] instead is not advisable; it will
-cause \f[C]HELLO.txt\f[R] to get deleted! - the old dest filename must
-not be excluded by filters.
+\f[V]--fix-case\f[R] will be ignored if \f[V]--immutable\f[R] is set -
+using \f[V]--local-case-sensitive\f[R] instead is not advisable; it will
+cause \f[V]HELLO.txt\f[R] to get deleted!
+- the old dest filename must not be excluded by filters.
 Be especially careful with
-\f[C]--files-from\f[R] (https://rclone.org/filtering/#files-from-read-list-of-source-file-names),
+\f[V]--files-from\f[R] (https://rclone.org/filtering/#files-from-read-list-of-source-file-names),
 which does not respect
-\f[C]--ignore-case\f[R] (https://rclone.org/filtering/#ignore-case-make-searches-case-insensitive)!
-- on remotes that do not support server-side move, \f[C]--fix-case\f[R]
+\f[V]--ignore-case\f[R] (https://rclone.org/filtering/#ignore-case-make-searches-case-insensitive)!
+- on remotes that do not support server-side move, \f[V]--fix-case\f[R]
 will require downloading the file and re-uploading it.
-To avoid this, do not use \f[C]--fix-case\f[R].
+To avoid this, do not use \f[V]--fix-case\f[R].
 .SS --fs-cache-expire-duration=TIME
 .PP
 When using rclone via the API rclone caches created remotes for 5
@@ -17909,17 +17927,17 @@ rclone won\[aq]t have to build it again from scratch, which makes it
 more efficient.
 .PP
 This flag sets the time that the remotes are cached for.
-If you set it to \f[C]0\f[R] (or negative) then rclone won\[aq]t cache
+If you set it to \f[V]0\f[R] (or negative) then rclone won\[aq]t cache
 the remotes at all.
 .PP
-Note that if you use some flags, eg \f[C]--backup-dir\f[R] and if this
-is set to \f[C]0\f[R] rclone may build two remotes (one for the source
-or destination and one for the \f[C]--backup-dir\f[R] where it may have
+Note that if you use some flags, eg \f[V]--backup-dir\f[R] and if this
+is set to \f[V]0\f[R] rclone may build two remotes (one for the source
+or destination and one for the \f[V]--backup-dir\f[R] where it may have
 only built one before.
 .SS --fs-cache-expire-interval=TIME
 .PP
 This controls how often rclone checks for cached remotes to expire.
-See the \f[C]--fs-cache-expire-duration\f[R] documentation above for
+See the \f[V]--fs-cache-expire-duration\f[R] documentation above for
 more info.
 The default is 60s, set to 0 to disable expiry.
 .SS --header
@@ -17928,11 +17946,11 @@ Add an HTTP header for all transactions.
 The flag can be repeated to add multiple headers.
 .PP
 If you want to add headers only for uploads use
-\f[C]--header-upload\f[R] and if you want to add headers only for
-downloads use \f[C]--header-download\f[R].
+\f[V]--header-upload\f[R] and if you want to add headers only for
+downloads use \f[V]--header-download\f[R].
 .PP
 This flag is supported for all HTTP based backends even those not
-supported by \f[C]--header-upload\f[R] and \f[C]--header-download\f[R]
+supported by \f[V]--header-upload\f[R] and \f[V]--header-download\f[R]
 so may be used as a workaround for those with care.
 .IP
 .nf
@@ -17979,37 +17997,37 @@ decimals.
 Rclone consistently uses binary units (powers of 2) for sizes and
 decimal units (powers of 10) for counts.
 The unit prefix for size is according to IEC standard notation, e.g.
-\f[C]Ki\f[R] for kibi.
-Used with byte unit, \f[C]1 KiB\f[R] means 1024 Byte.
+\f[V]Ki\f[R] for kibi.
+Used with byte unit, \f[V]1 KiB\f[R] means 1024 Byte.
 In list type of output, only the unit prefix appended to the value (e.g.
-\f[C]9.762Ki\f[R]), while in more textual output the full unit is shown
+\f[V]9.762Ki\f[R]), while in more textual output the full unit is shown
 (e.g.
-\f[C]9.762 KiB\f[R]).
+\f[V]9.762 KiB\f[R]).
 For counts the SI standard notation is used, e.g.
-prefix \f[C]k\f[R] for kilo.
-Used with file counts, \f[C]1k\f[R] means 1000 files.
+prefix \f[V]k\f[R] for kilo.
+Used with file counts, \f[V]1k\f[R] means 1000 files.
 .PP
 The various list (https://rclone.org/commands/rclone_ls/) commands
 output raw numbers by default.
-Option \f[C]--human-readable\f[R] will make them output values in
+Option \f[V]--human-readable\f[R] will make them output values in
 human-readable format instead (with the short unit prefix).
 .PP
 The about (https://rclone.org/commands/rclone_about/) command outputs
 human-readable by default, with a command-specific option
-\f[C]--full\f[R] to output the raw numbers instead.
+\f[V]--full\f[R] to output the raw numbers instead.
 .PP
 Command size (https://rclone.org/commands/rclone_size/) outputs both
 human-readable and raw numbers in the same output.
 .PP
 The tree (https://rclone.org/commands/rclone_tree/) command also
-considers \f[C]--human-readable\f[R], but it will not use the exact same
+considers \f[V]--human-readable\f[R], but it will not use the exact same
 notation as the other commands: It rounds to one decimal, and uses
 single letter suffix, e.g.
-\f[C]K\f[R] instead of \f[C]Ki\f[R].
+\f[V]K\f[R] instead of \f[V]Ki\f[R].
 The reason for this is that it relies on an external library.
 .PP
 The interactive command ncdu (https://rclone.org/commands/rclone_ncdu/)
-shows human-readable by default, and responds to key \f[C]u\f[R] for
+shows human-readable by default, and responds to key \f[V]u\f[R] for
 toggling human-readable format.
 .SS --ignore-case-sync
 .PP
@@ -18036,7 +18054,7 @@ cases where your files change due to encryption.
 However, it cannot correct partial transfers in case a transfer was
 interrupted.
 .PP
-When performing a \f[C]move\f[R]/\f[C]moveto\f[R] command, this flag
+When performing a \f[V]move\f[R]/\f[V]moveto\f[R] command, this flag
 will leave skipped files in the source location unchanged when a file
 with the same name exists on the destination.
 .SS --ignore-size
@@ -18044,7 +18062,7 @@ with the same name exists on the destination.
 Normally rclone will look at modification time and size of files to see
 if they are equal.
 If you set this flag then rclone will check only the modification time.
-If \f[C]--checksum\f[R] is set then it only checks the checksum.
+If \f[V]--checksum\f[R] is set then it only checks the checksum.
 .PP
 It will also cause rclone to skip verifying the sizes are the same after
 transfer.
@@ -18059,7 +18077,7 @@ regardless of the state of files on the destination.
 .PP
 Normally rclone would skip any files that have the same modification
 time and are the same size (or have the same checksum if using
-\f[C]--checksum\f[R]).
+\f[V]--checksum\f[R]).
 .SS --immutable
 .PP
 Treat source and destination files as immutable and disallow
@@ -18069,15 +18087,15 @@ With this option set, files will be created and deleted as requested,
 but existing files will never be updated.
 If an existing file does not match between the source and destination,
 rclone will give the error
-\f[C]Source and destination exist but do not match: immutable file modified\f[R].
+\f[V]Source and destination exist but do not match: immutable file modified\f[R].
 .PP
 Note that only commands which transfer files (e.g.
-\f[C]sync\f[R], \f[C]copy\f[R], \f[C]move\f[R]) are affected by this
+\f[V]sync\f[R], \f[V]copy\f[R], \f[V]move\f[R]) are affected by this
 behavior, and only modification is disallowed.
 Files may still be deleted explicitly (e.g.
-\f[C]delete\f[R], \f[C]purge\f[R]) or implicitly (e.g.
-\f[C]sync\f[R], \f[C]move\f[R]).
-Use \f[C]copy --immutable\f[R] if it is desired to avoid deletion as
+\f[V]delete\f[R], \f[V]purge\f[R]) or implicitly (e.g.
+\f[V]sync\f[R], \f[V]move\f[R]).
+Use \f[V]copy --immutable\f[R] if it is desired to avoid deletion as
 well as modification.
 .PP
 This can be useful as an additional layer of protection for immutable or
@@ -18085,9 +18103,9 @@ append-only data sets (notably backup archives), where modification
 implies corruption and should not be propagated.
 .SS --inplace
 .PP
-The \f[C]--inplace\f[R] flag changes the behaviour of rclone when
+The \f[V]--inplace\f[R] flag changes the behaviour of rclone when
 uploading files to some backends (backends with the
-\f[C]PartialUploads\f[R] feature flag set) such as:
+\f[V]PartialUploads\f[R] feature flag set) such as:
 .IP \[bu] 2
 local
 .IP \[bu] 2
@@ -18097,10 +18115,10 @@ sftp
 .IP \[bu] 2
 pcloud
 .PP
-Without \f[C]--inplace\f[R] (the default) rclone will first upload to a
-temporary file with an extension like this, where \f[C]XXXXXX\f[R]
+Without \f[V]--inplace\f[R] (the default) rclone will first upload to a
+temporary file with an extension like this, where \f[V]XXXXXX\f[R]
 represents a hash of the source file\[aq]s fingerprint and
-\f[C].partial\f[R] is --partial-suffix value (\f[C].partial\f[R] by
+\f[V].partial\f[R] is --partial-suffix value (\f[V].partial\f[R] by
 default).
 .IP
 .nf
@@ -18110,18 +18128,18 @@ original-file-name.XXXXXX.partial
 .fi
 .PP
 (rclone will make sure the final name is no longer than 100 characters
-by truncating the \f[C]original-file-name\f[R] part if necessary).
+by truncating the \f[V]original-file-name\f[R] part if necessary).
 .PP
-When the upload is complete, rclone will rename the \f[C].partial\f[R]
+When the upload is complete, rclone will rename the \f[V].partial\f[R]
 file to the correct name, overwriting any existing file at that point.
-If the upload fails then the \f[C].partial\f[R] file will be deleted.
+If the upload fails then the \f[V].partial\f[R] file will be deleted.
 .PP
 This prevents other users of the backend from seeing partially uploaded
 files in their new names and prevents overwriting the old file until the
 new one is completely uploaded.
 .PP
-If the \f[C]--inplace\f[R] flag is supplied, rclone will upload directly
-to the final name without creating a \f[C].partial\f[R] file.
+If the \f[V]--inplace\f[R] flag is supplied, rclone will upload directly
+to the final name without creating a \f[V].partial\f[R] file.
 .PP
 This means that an incomplete file will be visible in the directory
 listings while the upload is in progress and any existing files will be
@@ -18130,19 +18148,19 @@ If the transfer fails then the file will be deleted.
 This can cause data loss of the existing file if the transfer fails.
 .PP
 Note that on the local file system if you don\[aq]t use
-\f[C]--inplace\f[R] hard links (Unix only) will be broken.
-And if you do use \f[C]--inplace\f[R] you won\[aq]t be able to update in
+\f[V]--inplace\f[R] hard links (Unix only) will be broken.
+And if you do use \f[V]--inplace\f[R] you won\[aq]t be able to update in
 use executables.
 .PP
 Note also that versions of rclone prior to v1.63.0 behave as if the
-\f[C]--inplace\f[R] flag is always supplied.
+\f[V]--inplace\f[R] flag is always supplied.
 .SS -i, --interactive
 .PP
 This flag can be used to tell rclone that you wish a manual confirmation
 before destructive operations.
 .PP
 It is \f[B]recommended\f[R] that you use this flag while learning rclone
-especially with \f[C]rclone sync\f[R].
+especially with \f[V]rclone sync\f[R].
 .PP
 For example
 .IP
@@ -18161,22 +18179,22 @@ y/n/s/!/q> n
 .PP
 The options mean
 .IP \[bu] 2
-\f[C]y\f[R]: \f[B]Yes\f[R], this operation should go ahead.
+\f[V]y\f[R]: \f[B]Yes\f[R], this operation should go ahead.
 You can also press Return for this to happen.
-You\[aq]ll be asked every time unless you choose \f[C]s\f[R] or
-\f[C]!\f[R].
+You\[aq]ll be asked every time unless you choose \f[V]s\f[R] or
+\f[V]!\f[R].
 .IP \[bu] 2
-\f[C]n\f[R]: \f[B]No\f[R], do not do this operation.
-You\[aq]ll be asked every time unless you choose \f[C]s\f[R] or
-\f[C]!\f[R].
+\f[V]n\f[R]: \f[B]No\f[R], do not do this operation.
+You\[aq]ll be asked every time unless you choose \f[V]s\f[R] or
+\f[V]!\f[R].
 .IP \[bu] 2
-\f[C]s\f[R]: \f[B]Skip\f[R] all the following operations of this type
+\f[V]s\f[R]: \f[B]Skip\f[R] all the following operations of this type
 with no more questions.
 This takes effect until rclone exits.
 If there are any different kind of operations you\[aq]ll be prompted for
 them.
 .IP \[bu] 2
-\f[C]!\f[R]: \f[B]Do all\f[R] the following operations with no more
+\f[V]!\f[R]: \f[B]Do all\f[R] the following operations with no more
 questions.
 Useful if you\[aq]ve decided that you don\[aq]t mind rclone doing that
 kind of operation.
@@ -18184,7 +18202,7 @@ This takes effect until rclone exits .
 If there are any different kind of operations you\[aq]ll be prompted for
 them.
 .IP \[bu] 2
-\f[C]q\f[R]: \f[B]Quit\f[R] rclone now, just in case!
+\f[V]q\f[R]: \f[B]Quit\f[R] rclone now, just in case!
 .SS --leave-root
 .PP
 During rmdirs it will not remove root directory, even if it\[aq]s empty.
@@ -18193,45 +18211,45 @@ During rmdirs it will not remove root directory, even if it\[aq]s empty.
 Log all of rclone\[aq]s output to FILE.
 This is not active by default.
 This can be useful for tracking down problems with syncs in combination
-with the \f[C]-v\f[R] flag.
+with the \f[V]-v\f[R] flag.
 See the Logging section for more info.
 .PP
 If FILE exists then rclone will append to it.
 .PP
-Note that if you are using the \f[C]logrotate\f[R] program to manage
-rclone\[aq]s logs, then you should use the \f[C]copytruncate\f[R] option
+Note that if you are using the \f[V]logrotate\f[R] program to manage
+rclone\[aq]s logs, then you should use the \f[V]copytruncate\f[R] option
 as rclone doesn\[aq]t have a signal to rotate logs.
 .SS --log-format LIST
 .PP
 Comma separated list of log format options.
-Accepted options are \f[C]date\f[R], \f[C]time\f[R],
-\f[C]microseconds\f[R], \f[C]pid\f[R], \f[C]longfile\f[R],
-\f[C]shortfile\f[R], \f[C]UTC\f[R].
+Accepted options are \f[V]date\f[R], \f[V]time\f[R],
+\f[V]microseconds\f[R], \f[V]pid\f[R], \f[V]longfile\f[R],
+\f[V]shortfile\f[R], \f[V]UTC\f[R].
 Any other keywords will be silently ignored.
-\f[C]pid\f[R] will tag log messages with process identifier which useful
-with \f[C]rclone mount --daemon\f[R].
+\f[V]pid\f[R] will tag log messages with process identifier which useful
+with \f[V]rclone mount --daemon\f[R].
 Other accepted options are explained in the go
 documentation (https://pkg.go.dev/log#pkg-constants).
-The default log format is \[dq]\f[C]date\f[R],\f[C]time\f[R]\[dq].
+The default log format is \[dq]\f[V]date\f[R],\f[V]time\f[R]\[dq].
 .SS --log-level LEVEL
 .PP
 This sets the log level for rclone.
-The default log level is \f[C]NOTICE\f[R].
+The default log level is \f[V]NOTICE\f[R].
 .PP
-\f[C]DEBUG\f[R] is equivalent to \f[C]-vv\f[R].
+\f[V]DEBUG\f[R] is equivalent to \f[V]-vv\f[R].
 It outputs lots of debug info - useful for bug reports and really
 finding out what rclone is doing.
 .PP
-\f[C]INFO\f[R] is equivalent to \f[C]-v\f[R].
+\f[V]INFO\f[R] is equivalent to \f[V]-v\f[R].
 It outputs information about each transfer and prints stats once a
 minute by default.
 .PP
-\f[C]NOTICE\f[R] is the default log level if no logging flags are
+\f[V]NOTICE\f[R] is the default log level if no logging flags are
 supplied.
 It outputs very little when things are working normally.
 It outputs warnings and significant events.
 .PP
-\f[C]ERROR\f[R] is equivalent to \f[C]-q\f[R].
+\f[V]ERROR\f[R] is equivalent to \f[V]-q\f[R].
 It only outputs error messages.
 .SS --use-json-log
 .PP
@@ -18244,15 +18262,15 @@ This controls the number of low level retries rclone does.
 A low level retry is used to retry a failing operation - typically one
 HTTP request.
 This might be uploading a chunk of a big file for example.
-You will see low level retries in the log with the \f[C]-v\f[R] flag.
+You will see low level retries in the log with the \f[V]-v\f[R] flag.
 .PP
 This shouldn\[aq]t need to be changed from the default in normal
 operations.
 However, if you get a lot of low level retries you may wish to reduce
 the value so rclone moves on to a high level retry (see the
-\f[C]--retries\f[R] flag) quicker.
+\f[V]--retries\f[R] flag) quicker.
 .PP
-Disable low level retries with \f[C]--low-level-retries 1\f[R].
+Disable low level retries with \f[V]--low-level-retries 1\f[R].
 .SS --max-backlog=N
 .PP
 This is the maximum allowable backlog of files in a sync/copy/move
@@ -18265,7 +18283,7 @@ is in use.
 .PP
 Setting this large allows rclone to calculate how many files are pending
 more accurately, give a more accurate estimated finish time and make
-\f[C]--order-by\f[R] work more accurately.
+\f[V]--order-by\f[R] work more accurately.
 .PP
 Setting this small will make rclone more synchronous to the listings of
 the remote which may be desirable.
@@ -18289,22 +18307,22 @@ rclone will stop the operation in progress.
 .PP
 This modifies the recursion depth for all the commands except purge.
 .PP
-So if you do \f[C]rclone --max-depth 1 ls remote:path\f[R] you will see
+So if you do \f[V]rclone --max-depth 1 ls remote:path\f[R] you will see
 only the files in the top level directory.
-Using \f[C]--max-depth 2\f[R] means you will see all the files in first
+Using \f[V]--max-depth 2\f[R] means you will see all the files in first
 two directory levels and so on.
 .PP
-For historical reasons the \f[C]lsd\f[R] command defaults to using a
-\f[C]--max-depth\f[R] of 1 - you can override this with the command line
+For historical reasons the \f[V]lsd\f[R] command defaults to using a
+\f[V]--max-depth\f[R] of 1 - you can override this with the command line
 flag.
 .PP
 You can use this command to disable recursion (with
-\f[C]--max-depth 1\f[R]).
+\f[V]--max-depth 1\f[R]).
 .PP
-Note that if you use this with \f[C]sync\f[R] and
-\f[C]--delete-excluded\f[R] the files not recursed through are
+Note that if you use this with \f[V]sync\f[R] and
+\f[V]--delete-excluded\f[R] the files not recursed through are
 considered excluded and will be deleted on the destination.
-Test first with \f[C]--dry-run\f[R] if you are not sure what will
+Test first with \f[V]--dry-run\f[R] if you are not sure what will
 happen.
 .SS --max-duration=TIME
 .PP
@@ -18313,7 +18331,7 @@ specified.
 Defaults to off.
 .PP
 When the limit is reached all transfers will stop immediately.
-Use \f[C]--cutoff-mode\f[R] to modify this behaviour.
+Use \f[V]--cutoff-mode\f[R] to modify this behaviour.
 .PP
 Rclone will exit with exit code 10 if the duration limit is reached.
 .SS --max-transfer=SIZE
@@ -18322,23 +18340,23 @@ Rclone will stop transferring when it has reached the size specified.
 Defaults to off.
 .PP
 When the limit is reached all transfers will stop immediately.
-Use \f[C]--cutoff-mode\f[R] to modify this behaviour.
+Use \f[V]--cutoff-mode\f[R] to modify this behaviour.
 .PP
 Rclone will exit with exit code 8 if the transfer limit is reached.
 .SS --cutoff-mode=hard|soft|cautious
 .PP
-This modifies the behavior of \f[C]--max-transfer\f[R] and
-\f[C]--max-duration\f[R] Defaults to \f[C]--cutoff-mode=hard\f[R].
+This modifies the behavior of \f[V]--max-transfer\f[R] and
+\f[V]--max-duration\f[R] Defaults to \f[V]--cutoff-mode=hard\f[R].
 .PP
-Specifying \f[C]--cutoff-mode=hard\f[R] will stop transferring
+Specifying \f[V]--cutoff-mode=hard\f[R] will stop transferring
 immediately when Rclone reaches the limit.
 .PP
-Specifying \f[C]--cutoff-mode=soft\f[R] will stop starting new transfers
+Specifying \f[V]--cutoff-mode=soft\f[R] will stop starting new transfers
 when Rclone reaches the limit.
 .PP
-Specifying \f[C]--cutoff-mode=cautious\f[R] will try to prevent Rclone
+Specifying \f[V]--cutoff-mode=cautious\f[R] will try to prevent Rclone
 from reaching the limit.
-Only applicable for \f[C]--max-transfer\f[R]
+Only applicable for \f[V]--max-transfer\f[R]
 .SS -M, --metadata
 .PP
 Setting this flag enables rclone to copy the metadata from the source to
@@ -18347,16 +18365,16 @@ For local backends this is ownership, permissions, xattr etc.
 See the metadata section for more info.
 .SS --metadata-mapper SpaceSepList
 .PP
-If you supply the parameter \f[C]--metadata-mapper /path/to/program\f[R]
+If you supply the parameter \f[V]--metadata-mapper /path/to/program\f[R]
 then rclone will use that program to map metadata from source object to
 destination object.
 .PP
 The argument to this flag should be a command with an optional space
 separated list of arguments.
 If one of the arguments has a space in then enclose it in
-\f[C]\[dq]\f[R], if you want a literal \f[C]\[dq]\f[R] in an argument
-then enclose the argument in \f[C]\[dq]\f[R] and double the
-\f[C]\[dq]\f[R].
+\f[V]\[dq]\f[R], if you want a literal \f[V]\[dq]\f[R] in an argument
+then enclose the argument in \f[V]\[dq]\f[R] and double the
+\f[V]\[dq]\f[R].
 See CSV encoding (https://godoc.org/encoding/csv) for more info.
 .IP
 .nf
@@ -18377,30 +18395,30 @@ it into a metadata blob on the output suitable for the destination
 backend.
 .PP
 Input to the program (via STDIN) might look like this.
-This provides some context for the \f[C]Metadata\f[R] which may be
+This provides some context for the \f[V]Metadata\f[R] which may be
 important.
 .IP \[bu] 2
-\f[C]SrcFs\f[R] is the config string for the remote that the object is
+\f[V]SrcFs\f[R] is the config string for the remote that the object is
 currently on.
 .IP \[bu] 2
-\f[C]SrcFsType\f[R] is the name of the source backend.
+\f[V]SrcFsType\f[R] is the name of the source backend.
 .IP \[bu] 2
-\f[C]DstFs\f[R] is the config string for the remote that the object is
+\f[V]DstFs\f[R] is the config string for the remote that the object is
 being copied to
 .IP \[bu] 2
-\f[C]DstFsType\f[R] is the name of the destination backend.
+\f[V]DstFsType\f[R] is the name of the destination backend.
 .IP \[bu] 2
-\f[C]Remote\f[R] is the path of the object relative to the root.
+\f[V]Remote\f[R] is the path of the object relative to the root.
 .IP \[bu] 2
-\f[C]Size\f[R], \f[C]MimeType\f[R], \f[C]ModTime\f[R] are attributes of
+\f[V]Size\f[R], \f[V]MimeType\f[R], \f[V]ModTime\f[R] are attributes of
 the object.
 .IP \[bu] 2
-\f[C]IsDir\f[R] is \f[C]true\f[R] if this is a directory (not yet
+\f[V]IsDir\f[R] is \f[V]true\f[R] if this is a directory (not yet
 implemented).
 .IP \[bu] 2
-\f[C]ID\f[R] is the source \f[C]ID\f[R] of the object if known.
+\f[V]ID\f[R] is the source \f[V]ID\f[R] of the object if known.
 .IP \[bu] 2
-\f[C]Metadata\f[R] is the backend specific metadata as described in the
+\f[V]Metadata\f[R] is the backend specific metadata as described in the
 backend docs.
 .IP
 .nf
@@ -18431,7 +18449,7 @@ backend docs.
 .PP
 The program should then modify the input as desired and send it to
 STDOUT.
-The returned \f[C]Metadata\f[R] field will be used in its entirety for
+The returned \f[V]Metadata\f[R] field will be used in its entirety for
 the destination object.
 Any other fields will be ignored.
 Note in this example we translate user names and permissions and add
@@ -18482,12 +18500,12 @@ at
 bin/test_metadata_mapper.py (https://github.com/rclone/rclone/blob/master/bin/test_metadata_mapper.py).
 .PP
 If you want to see the input to the metadata mapper and the output
-returned from it in the log you can use \f[C]-vv --dump mapper\f[R].
+returned from it in the log you can use \f[V]-vv --dump mapper\f[R].
 .PP
 See the metadata section for more info.
 .SS --metadata-set key=value
 .PP
-Add metadata \f[C]key\f[R] = \f[C]value\f[R] when uploading.
+Add metadata \f[V]key\f[R] = \f[V]value\f[R] when uploading.
 This can be repeated as many times as required.
 See the metadata section for more info.
 .SS --modify-window=TIME
@@ -18496,10 +18514,10 @@ When checking whether a file has been modified, this is the maximum
 allowed time difference that a file can have and still be considered
 equivalent.
 .PP
-The default is \f[C]1ns\f[R] unless this is overridden by a remote.
+The default is \f[V]1ns\f[R] unless this is overridden by a remote.
 For example OS X only stores modification times to the nearest second so
 if you are reading and writing to an OS X filing system this will be
-\f[C]1s\f[R] by default.
+\f[V]1s\f[R] by default.
 .PP
 This command line flag allows you to override that computed default.
 .SS --multi-thread-write-buffer-size=SIZE
@@ -18514,7 +18532,7 @@ to experiment with different values.
 Specially for magnetic drives and remote file systems a higher value can
 be useful.
 .PP
-Nevertheless, the default of \f[C]128k\f[R] should be fine for almost
+Nevertheless, the default of \f[V]128k\f[R] should be fine for almost
 all use cases, so before changing it ensure that network is not really
 your bottleneck.
 .PP
@@ -18526,8 +18544,8 @@ better than other values.
 .PP
 Normally the chunk size for multi thread transfers is set by the
 backend.
-However some backends such as \f[C]local\f[R] and \f[C]smb\f[R] (which
-implement \f[C]OpenWriterAt\f[R] but not \f[C]OpenChunkWriter\f[R])
+However some backends such as \f[V]local\f[R] and \f[V]smb\f[R] (which
+implement \f[V]OpenWriterAt\f[R] but not \f[V]OpenChunkWriter\f[R])
 don\[aq]t have a natural chunk size.
 .PP
 In this case the value of this option is used (default 64Mi).
@@ -18538,59 +18556,59 @@ multiple threads to transfer the file (default 256M).
 .PP
 Capable backends are marked in the
 overview (https://rclone.org/overview/#optional-features) as
-\f[C]MultithreadUpload\f[R].
-(They need to implement either the \f[C]OpenWriterAt\f[R] or
-\f[C]OpenChunkWriter\f[R] internal interfaces).
-These include include, \f[C]local\f[R], \f[C]s3\f[R],
-\f[C]azureblob\f[R], \f[C]b2\f[R], \f[C]oracleobjectstorage\f[R] and
-\f[C]smb\f[R] at the time of writing.
+\f[V]MultithreadUpload\f[R].
+(They need to implement either the \f[V]OpenWriterAt\f[R] or
+\f[V]OpenChunkWriter\f[R] internal interfaces).
+These include include, \f[V]local\f[R], \f[V]s3\f[R],
+\f[V]azureblob\f[R], \f[V]b2\f[R], \f[V]oracleobjectstorage\f[R] and
+\f[V]smb\f[R] at the time of writing.
 .PP
 On the local disk, rclone preallocates the file (using
-\f[C]fallocate(FALLOC_FL_KEEP_SIZE)\f[R] on unix or
-\f[C]NTSetInformationFile\f[R] on Windows both of which takes no time)
+\f[V]fallocate(FALLOC_FL_KEEP_SIZE)\f[R] on unix or
+\f[V]NTSetInformationFile\f[R] on Windows both of which takes no time)
 then each thread writes directly into the file at the correct place.
 This means that rclone won\[aq]t create fragmented or sparse files and
 there won\[aq]t be any assembly time at the end of the transfer.
 .PP
 The number of threads used to transfer is controlled by
-\f[C]--multi-thread-streams\f[R].
+\f[V]--multi-thread-streams\f[R].
 .PP
-Use \f[C]-vv\f[R] if you wish to see info about the threads.
+Use \f[V]-vv\f[R] if you wish to see info about the threads.
 .PP
-This will work with the \f[C]sync\f[R]/\f[C]copy\f[R]/\f[C]move\f[R]
-commands and friends \f[C]copyto\f[R]/\f[C]moveto\f[R].
-Multi thread transfers will be used with \f[C]rclone mount\f[R] and
-\f[C]rclone serve\f[R] if \f[C]--vfs-cache-mode\f[R] is set to
-\f[C]writes\f[R] or above.
+This will work with the \f[V]sync\f[R]/\f[V]copy\f[R]/\f[V]move\f[R]
+commands and friends \f[V]copyto\f[R]/\f[V]moveto\f[R].
+Multi thread transfers will be used with \f[V]rclone mount\f[R] and
+\f[V]rclone serve\f[R] if \f[V]--vfs-cache-mode\f[R] is set to
+\f[V]writes\f[R] or above.
 .PP
 \f[B]NB\f[R] that this \f[B]only\f[R] works with supported backends as
 the destination but will work with any backend as the source.
 .PP
 \f[B]NB\f[R] that multi-thread copies are disabled for local to local
 copies as they are faster without unless
-\f[C]--multi-thread-streams\f[R] is set explicitly.
+\f[V]--multi-thread-streams\f[R] is set explicitly.
 .PP
 \f[B]NB\f[R] on Windows using multi-thread transfers to the local disk
 will cause the resulting files to be
 sparse (https://en.wikipedia.org/wiki/Sparse_file).
-Use \f[C]--local-no-sparse\f[R] to disable sparse files (which may cause
+Use \f[V]--local-no-sparse\f[R] to disable sparse files (which may cause
 long delays at the start of transfers) or disable multi-thread transfers
-with \f[C]--multi-thread-streams 0\f[R]
+with \f[V]--multi-thread-streams 0\f[R]
 .SS --multi-thread-streams=N
 .PP
 When using multi thread transfers (see above
-\f[C]--multi-thread-cutoff\f[R]) this sets the number of streams to use.
-Set to \f[C]0\f[R] to disable multi thread transfers (Default 4).
+\f[V]--multi-thread-cutoff\f[R]) this sets the number of streams to use.
+Set to \f[V]0\f[R] to disable multi thread transfers (Default 4).
 .PP
-If the backend has a \f[C]--backend-upload-concurrency\f[R] setting (eg
-\f[C]--s3-upload-concurrency\f[R]) then this setting will be used as the
+If the backend has a \f[V]--backend-upload-concurrency\f[R] setting (eg
+\f[V]--s3-upload-concurrency\f[R]) then this setting will be used as the
 number of transfers instead if it is larger than the value of
-\f[C]--multi-thread-streams\f[R] or \f[C]--multi-thread-streams\f[R]
+\f[V]--multi-thread-streams\f[R] or \f[V]--multi-thread-streams\f[R]
 isn\[aq]t set.
 .SS --no-check-dest
 .PP
-The \f[C]--no-check-dest\f[R] can be used with \f[C]move\f[R] or
-\f[C]copy\f[R] and it causes rclone not to check the destination at all
+The \f[V]--no-check-dest\f[R] can be used with \f[V]move\f[R] or
+\f[V]copy\f[R] and it causes rclone not to check the destination at all
 when copying files.
 .PP
 This means that:
@@ -18602,7 +18620,7 @@ files are always transferred
 this can cause duplicates on remotes which allow it (e.g.
 Google Drive)
 .IP \[bu] 2
-\f[C]--retries 1\f[R] is recommended otherwise you\[aq]ll transfer
+\f[V]--retries 1\f[R] is recommended otherwise you\[aq]ll transfer
 everything again on a retry
 .PP
 This flag is useful to minimise the transactions if you know that none
@@ -18611,31 +18629,31 @@ of the files are on the destination.
 This is a specialized flag which should be ignored by most users!
 .SS --no-gzip-encoding
 .PP
-Don\[aq]t set \f[C]Accept-Encoding: gzip\f[R].
+Don\[aq]t set \f[V]Accept-Encoding: gzip\f[R].
 This means that rclone won\[aq]t ask the server for compressed files
 automatically.
 Useful if you\[aq]ve set the server to return files with
-\f[C]Content-Encoding: gzip\f[R] but you uploaded compressed files.
+\f[V]Content-Encoding: gzip\f[R] but you uploaded compressed files.
 .PP
 There is no need to set this in normal operation, and doing so will
 decrease the network transfer efficiency of rclone.
 .SS --no-traverse
 .PP
-The \f[C]--no-traverse\f[R] flag controls whether the destination file
-system is traversed when using the \f[C]copy\f[R] or \f[C]move\f[R]
+The \f[V]--no-traverse\f[R] flag controls whether the destination file
+system is traversed when using the \f[V]copy\f[R] or \f[V]move\f[R]
 commands.
-\f[C]--no-traverse\f[R] is not compatible with \f[C]sync\f[R] and will
-be ignored if you supply it with \f[C]sync\f[R].
+\f[V]--no-traverse\f[R] is not compatible with \f[V]sync\f[R] and will
+be ignored if you supply it with \f[V]sync\f[R].
 .PP
 If you are only copying a small number of files (or are filtering most
 of the files) and/or have a large number of files on the destination
-then \f[C]--no-traverse\f[R] will stop rclone listing the destination
+then \f[V]--no-traverse\f[R] will stop rclone listing the destination
 and save time.
 .PP
 However, if you are copying a large number of files, especially if you
 are doing a copy where lots of the files under consideration haven\[aq]t
 changed and won\[aq]t need copying then you shouldn\[aq]t use
-\f[C]--no-traverse\f[R].
+\f[V]--no-traverse\f[R].
 .PP
 See rclone copy (https://rclone.org/commands/rclone_copy/) for an
 example of how to use it.
@@ -18651,9 +18669,9 @@ duplicate files if the data is ever copied back to a local filesystem.
 .PP
 Using this flag will disable that functionality, treating each unicode
 character as unique.
-For example, by default e\[u0301] and \['e] will be normalized into the
-same character.
-With \f[C]--no-unicode-normalization\f[R] they will be treated as unique
+For example, by default é and é will be normalized into the same
+character.
+With \f[V]--no-unicode-normalization\f[R] they will be treated as unique
 characters.
 .SS --no-update-modtime
 .PP
@@ -18669,60 +18687,60 @@ When using this flag, rclone won\[aq]t update modification times of
 remote directories if they are incorrect as it would normally.
 .SS --order-by string
 .PP
-The \f[C]--order-by\f[R] flag controls the order in which files in the
-backlog are processed in \f[C]rclone sync\f[R], \f[C]rclone copy\f[R]
-and \f[C]rclone move\f[R].
+The \f[V]--order-by\f[R] flag controls the order in which files in the
+backlog are processed in \f[V]rclone sync\f[R], \f[V]rclone copy\f[R]
+and \f[V]rclone move\f[R].
 .PP
 The order by string is constructed like this.
 The first part describes what aspect is being measured:
 .IP \[bu] 2
-\f[C]size\f[R] - order by the size of the files
+\f[V]size\f[R] - order by the size of the files
 .IP \[bu] 2
-\f[C]name\f[R] - order by the full path of the files
+\f[V]name\f[R] - order by the full path of the files
 .IP \[bu] 2
-\f[C]modtime\f[R] - order by the modification date of the files
+\f[V]modtime\f[R] - order by the modification date of the files
 .PP
 This can have a modifier appended with a comma:
 .IP \[bu] 2
-\f[C]ascending\f[R] or \f[C]asc\f[R] - order so that the smallest (or
+\f[V]ascending\f[R] or \f[V]asc\f[R] - order so that the smallest (or
 oldest) is processed first
 .IP \[bu] 2
-\f[C]descending\f[R] or \f[C]desc\f[R] - order so that the largest (or
+\f[V]descending\f[R] or \f[V]desc\f[R] - order so that the largest (or
 newest) is processed first
 .IP \[bu] 2
-\f[C]mixed\f[R] - order so that the smallest is processed first for some
+\f[V]mixed\f[R] - order so that the smallest is processed first for some
 threads and the largest for others
 .PP
-If the modifier is \f[C]mixed\f[R] then it can have an optional
-percentage (which defaults to \f[C]50\f[R]), e.g.
-\f[C]size,mixed,25\f[R] which means that 25% of the threads should be
+If the modifier is \f[V]mixed\f[R] then it can have an optional
+percentage (which defaults to \f[V]50\f[R]), e.g.
+\f[V]size,mixed,25\f[R] which means that 25% of the threads should be
 taking the smallest items and 75% the largest.
 The threads which take the smallest first will always take the smallest
 first and likewise the largest first threads.
-The \f[C]mixed\f[R] mode can be useful to minimise the transfer time
+The \f[V]mixed\f[R] mode can be useful to minimise the transfer time
 when you are transferring a mixture of large and small files - the large
 files are guaranteed upload threads and bandwidth and the small files
 will be processed continuously.
 .PP
-If no modifier is supplied then the order is \f[C]ascending\f[R].
+If no modifier is supplied then the order is \f[V]ascending\f[R].
 .PP
 For example
 .IP \[bu] 2
-\f[C]--order-by size,desc\f[R] - send the largest files first
+\f[V]--order-by size,desc\f[R] - send the largest files first
 .IP \[bu] 2
-\f[C]--order-by modtime,ascending\f[R] - send the oldest files first
+\f[V]--order-by modtime,ascending\f[R] - send the oldest files first
 .IP \[bu] 2
-\f[C]--order-by name\f[R] - send the files with alphabetically by path
+\f[V]--order-by name\f[R] - send the files with alphabetically by path
 first
 .PP
-If the \f[C]--order-by\f[R] flag is not supplied or it is supplied with
+If the \f[V]--order-by\f[R] flag is not supplied or it is supplied with
 an empty string then the default ordering will be used which is as
 scanned.
-With \f[C]--checkers 1\f[R] this is mostly alphabetical, however with
-the default \f[C]--checkers 8\f[R] it is somewhat random.
+With \f[V]--checkers 1\f[R] this is mostly alphabetical, however with
+the default \f[V]--checkers 8\f[R] it is somewhat random.
 .SS Limitations
 .PP
-The \f[C]--order-by\f[R] flag does not do a separate pass over the data.
+The \f[V]--order-by\f[R] flag does not do a separate pass over the data.
 This means that it may transfer some files out of the order specified if
 .IP \[bu] 2
 there are no files in the backlog or the source has not been fully
@@ -18732,7 +18750,7 @@ there are more than --max-backlog files in the backlog
 .PP
 Rclone will do its best to transfer the best file it has so in practice
 this should not cause a problem.
-Think of \f[C]--order-by\f[R] as being more of a best efforts flag
+Think of \f[V]--order-by\f[R] as being more of a best efforts flag
 rather than a perfect ordering.
 .PP
 If you want perfect ordering then you will need to specify --check-first
@@ -18741,25 +18759,25 @@ transferring any.
 .SS --partial-suffix
 .PP
 When --inplace is not used, it causes rclone to use the
-\f[C]--partial-suffix\f[R] as suffix for temporary files.
+\f[V]--partial-suffix\f[R] as suffix for temporary files.
 .PP
 Suffix length limit is 16 characters.
 .PP
-The default is \f[C].partial\f[R].
+The default is \f[V].partial\f[R].
 .SS --password-command SpaceSepList
 .PP
 This flag supplies a program which should supply the config password
 when run.
 This is an alternative to rclone prompting for the password or setting
-the \f[C]RCLONE_CONFIG_PASS\f[R] variable.
+the \f[V]RCLONE_CONFIG_PASS\f[R] variable.
 It is also used when setting the config password for the first time.
 .PP
 The argument to this should be a command with a space separated list of
 arguments.
 If one of the arguments has a space in then enclose it in
-\f[C]\[dq]\f[R], if you want a literal \f[C]\[dq]\f[R] in an argument
-then enclose the argument in \f[C]\[dq]\f[R] and double the
-\f[C]\[dq]\f[R].
+\f[V]\[dq]\f[R], if you want a literal \f[V]\[dq]\f[R] in an argument
+then enclose the argument in \f[V]\[dq]\f[R] and double the
+\f[V]\[dq]\f[R].
 See CSV encoding (https://godoc.org/encoding/csv) for more info.
 .PP
 Eg
@@ -18773,7 +18791,7 @@ Eg
 .fi
 .PP
 Note that when changing the configuration password the environment
-variable \f[C]RCLONE_PASSWORD_CHANGE=1\f[R] will be set.
+variable \f[V]RCLONE_PASSWORD_CHANGE=1\f[R] will be set.
 This can be used to distinguish initial decryption of the config file
 from the new password.
 .PP
@@ -18791,29 +18809,29 @@ Log messages will push the static block down to the bottom of the
 terminal where it will stay.
 .PP
 Normally this is updated every 500mS but this period can be overridden
-with the \f[C]--stats\f[R] flag.
+with the \f[V]--stats\f[R] flag.
 .PP
-This can be used with the \f[C]--stats-one-line\f[R] flag for a simpler
+This can be used with the \f[V]--stats-one-line\f[R] flag for a simpler
 display.
 .PP
 To change the display length of filenames (for different terminal
-widths), see the \f[C]--stats-file-name-length\f[R] option.
+widths), see the \f[V]--stats-file-name-length\f[R] option.
 The default output is formatted for 80 character wide terminals.
 .PP
 Note: On Windows until this
 bug (https://github.com/Azure/go-ansiterm/issues/26) is fixed all
-non-ASCII characters will be replaced with \f[C].\f[R] when
-\f[C]--progress\f[R] is in use.
+non-ASCII characters will be replaced with \f[V].\f[R] when
+\f[V]--progress\f[R] is in use.
 .SS --progress-terminal-title
 .PP
-This flag, when used with \f[C]-P/--progress\f[R], will print the string
-\f[C]ETA: %s\f[R] to the terminal title.
+This flag, when used with \f[V]-P/--progress\f[R], will print the string
+\f[V]ETA: %s\f[R] to the terminal title.
 .SS -q, --quiet
 .PP
 This flag will limit rclone\[aq]s output to error messages only.
 .SS --refresh-times
 .PP
-The \f[C]--refresh-times\f[R] flag can be used to update modification
+The \f[V]--refresh-times\f[R] flag can be used to update modification
 times of existing files when they are out of sync on backends which
 don\[aq]t support hashes.
 .PP
@@ -18822,15 +18840,15 @@ you now wish to correct them.
 .PP
 This flag is \f[B]only\f[R] useful for destinations which don\[aq]t
 support hashes (e.g.
-\f[C]crypt\f[R]).
+\f[V]crypt\f[R]).
 .PP
-This can be used any of the sync commands \f[C]sync\f[R], \f[C]copy\f[R]
-or \f[C]move\f[R].
+This can be used any of the sync commands \f[V]sync\f[R], \f[V]copy\f[R]
+or \f[V]move\f[R].
 .PP
 To use this flag you will need to be doing a modification time sync (so
-not using \f[C]--size-only\f[R] or \f[C]--checksum\f[R]).
-The flag will have no effect when using \f[C]--size-only\f[R] or
-\f[C]--checksum\f[R].
+not using \f[V]--size-only\f[R] or \f[V]--checksum\f[R]).
+The flag will have no effect when using \f[V]--size-only\f[R] or
+\f[V]--checksum\f[R].
 .PP
 If this flag is used when rclone comes to upload a file it will check to
 see if there is an existing file on the destination.
@@ -18839,13 +18857,13 @@ but has a differing timestamp then instead of re-uploading it, rclone
 will update the timestamp on the destination file.
 If the checksum does not match rclone will upload the new file.
 If the checksum is absent (e.g.
-on a \f[C]crypt\f[R] backend) then rclone will update the timestamp.
+on a \f[V]crypt\f[R] backend) then rclone will update the timestamp.
 .PP
 Note that some remotes can\[aq]t set the modification time without
 re-uploading the file so this flag is less useful on them.
 .PP
 Normally if you are doing a modification time sync rclone will update
-modification times without \f[C]--refresh-times\f[R] provided that the
+modification times without \f[V]--refresh-times\f[R] provided that the
 remote supports checksums \f[B]and\f[R] the checksums match on the file.
 However if the checksums are absent then rclone will upload the file
 rather than setting the timestamp as this is the safe behaviour.
@@ -18856,14 +18874,14 @@ Retry the entire sync if it fails this many times it fails (default 3).
 Some remotes can be unreliable and a few retries help pick up the files
 which didn\[aq]t get transferred because of errors.
 .PP
-Disable retries with \f[C]--retries 1\f[R].
+Disable retries with \f[V]--retries 1\f[R].
 .SS --retries-sleep=TIME
 .PP
 This sets the interval between each retry specified by
-\f[C]--retries\f[R]
+\f[V]--retries\f[R]
 .PP
-The default is \f[C]0\f[R].
-Use \f[C]0\f[R] to disable.
+The default is \f[V]0\f[R].
+Use \f[V]0\f[R] to disable.
 .SS --server-side-across-configs
 .PP
 Allow server-side operations (e.g.
@@ -18885,22 +18903,22 @@ modified by the desktop sync client which doesn\[aq]t set checksums of
 modification times in the same way as rclone.
 .SS --stats=TIME
 .PP
-Commands which transfer data (\f[C]sync\f[R], \f[C]copy\f[R],
-\f[C]copyto\f[R], \f[C]move\f[R], \f[C]moveto\f[R]) will print data
+Commands which transfer data (\f[V]sync\f[R], \f[V]copy\f[R],
+\f[V]copyto\f[R], \f[V]move\f[R], \f[V]moveto\f[R]) will print data
 transfer stats at regular intervals to show their progress.
 .PP
 This sets the interval.
 .PP
-The default is \f[C]1m\f[R].
-Use \f[C]0\f[R] to disable.
+The default is \f[V]1m\f[R].
+Use \f[V]0\f[R] to disable.
 .PP
 If you set the stats interval then all commands can show stats.
-This can be useful when running other commands, \f[C]check\f[R] or
-\f[C]mount\f[R] for example.
+This can be useful when running other commands, \f[V]check\f[R] or
+\f[V]mount\f[R] for example.
 .PP
-Stats are logged at \f[C]INFO\f[R] level by default which means they
-won\[aq]t show at default log level \f[C]NOTICE\f[R].
-Use \f[C]--stats-log-level NOTICE\f[R] or \f[C]-v\f[R] to make them
+Stats are logged at \f[V]INFO\f[R] level by default which means they
+won\[aq]t show at default log level \f[V]NOTICE\f[R].
+Use \f[V]--stats-log-level NOTICE\f[R] or \f[V]-v\f[R] to make them
 show.
 See the Logging section for more info on log levels.
 .PP
@@ -18908,20 +18926,20 @@ Note that on macOS you can send a SIGINFO (which is normally ctrl-T in
 the terminal) to make the stats print immediately.
 .SS --stats-file-name-length integer
 .PP
-By default, the \f[C]--stats\f[R] output will truncate file names and
+By default, the \f[V]--stats\f[R] output will truncate file names and
 paths longer than 40 characters.
-This is equivalent to providing \f[C]--stats-file-name-length 40\f[R].
-Use \f[C]--stats-file-name-length 0\f[R] to disable any truncation of
+This is equivalent to providing \f[V]--stats-file-name-length 40\f[R].
+Use \f[V]--stats-file-name-length 0\f[R] to disable any truncation of
 file names printed by stats.
 .SS --stats-log-level string
 .PP
-Log level to show \f[C]--stats\f[R] output at.
-This can be \f[C]DEBUG\f[R], \f[C]INFO\f[R], \f[C]NOTICE\f[R], or
-\f[C]ERROR\f[R].
-The default is \f[C]INFO\f[R].
-This means at the default level of logging which is \f[C]NOTICE\f[R] the
+Log level to show \f[V]--stats\f[R] output at.
+This can be \f[V]DEBUG\f[R], \f[V]INFO\f[R], \f[V]NOTICE\f[R], or
+\f[V]ERROR\f[R].
+The default is \f[V]INFO\f[R].
+This means at the default level of logging which is \f[V]NOTICE\f[R] the
 stats won\[aq]t show - if you want them to then use
-\f[C]--stats-log-level NOTICE\f[R].
+\f[V]--stats-log-level NOTICE\f[R].
 See the Logging section for more info on log levels.
 .SS --stats-one-line
 .PP
@@ -18931,7 +18949,7 @@ showing the most important stats only.
 .PP
 When this is specified, rclone enables the single-line stats and
 prepends the display with a date string.
-The default is \f[C]2006/01/02 15:04:05 -\f[R]
+The default is \f[V]2006/01/02 15:04:05 -\f[R]
 .SS --stats-one-line-date-format
 .PP
 When this is specified, rclone enables the single-line stats and
@@ -18950,10 +18968,10 @@ Data transfer volume will still be reported in bytes.
 The rate is reported as a binary unit, not SI unit.
 So 1 Mbit/s equals 1,048,576 bit/s and not 1,000,000 bit/s.
 .PP
-The default is \f[C]bytes\f[R].
+The default is \f[V]bytes\f[R].
 .SS --suffix=SUFFIX
 .PP
-When using \f[C]sync\f[R], \f[C]copy\f[R] or \f[C]move\f[R] any files
+When using \f[V]sync\f[R], \f[V]copy\f[R] or \f[V]move\f[R] any files
 which would have been overwritten or deleted will have the suffix added
 to them.
 If there is a file with the same path (after the suffix has been added),
@@ -18963,8 +18981,8 @@ The remote in use must support server-side move or copy and you must use
 the same remote as the destination of the sync.
 .PP
 This is for use with files to add the suffix in the current directory or
-with \f[C]--backup-dir\f[R].
-See \f[C]--backup-dir\f[R] for more info.
+with \f[V]--backup-dir\f[R].
+See \f[V]--backup-dir\f[R] for more info.
 .PP
 For example
 .IP
@@ -18974,12 +18992,12 @@ rclone copy --interactive /path/to/local/file remote:current --suffix .bak
 \f[R]
 .fi
 .PP
-will copy \f[C]/path/to/local\f[R] to \f[C]remote:current\f[R], but for
+will copy \f[V]/path/to/local\f[R] to \f[V]remote:current\f[R], but for
 any files which would have been updated or deleted have .bak added.
 .PP
-If using \f[C]rclone sync\f[R] with \f[C]--suffix\f[R] and without
-\f[C]--backup-dir\f[R] then it is recommended to put a filter rule in
-excluding the suffix otherwise the \f[C]sync\f[R] will delete the backup
+If using \f[V]rclone sync\f[R] with \f[V]--suffix\f[R] and without
+\f[V]--backup-dir\f[R] then it is recommended to put a filter rule in
+excluding the suffix otherwise the \f[V]sync\f[R] will delete the backup
 files.
 .IP
 .nf
@@ -18989,33 +19007,33 @@ rclone sync --interactive /path/to/local/file remote:current --suffix .bak --exc
 .fi
 .SS --suffix-keep-extension
 .PP
-When using \f[C]--suffix\f[R], setting this causes rclone put the SUFFIX
+When using \f[V]--suffix\f[R], setting this causes rclone put the SUFFIX
 before the extension of the files that it backs up rather than after.
 .PP
-So let\[aq]s say we had \f[C]--suffix -2019-01-01\f[R], without the flag
-\f[C]file.txt\f[R] would be backed up to \f[C]file.txt-2019-01-01\f[R]
+So let\[aq]s say we had \f[V]--suffix -2019-01-01\f[R], without the flag
+\f[V]file.txt\f[R] would be backed up to \f[V]file.txt-2019-01-01\f[R]
 and with the flag it would be backed up to
-\f[C]file-2019-01-01.txt\f[R].
+\f[V]file-2019-01-01.txt\f[R].
 This can be helpful to make sure the suffixed files can still be opened.
 .PP
 If a file has two (or more) extensions and the second (or subsequent)
 extension is recognised as a valid mime type, then the suffix will go
 before that extension.
-So \f[C]file.tar.gz\f[R] would be backed up to
-\f[C]file-2019-01-01.tar.gz\f[R] whereas \f[C]file.badextension.gz\f[R]
-would be backed up to \f[C]file.badextension-2019-01-01.gz\f[R].
+So \f[V]file.tar.gz\f[R] would be backed up to
+\f[V]file-2019-01-01.tar.gz\f[R] whereas \f[V]file.badextension.gz\f[R]
+would be backed up to \f[V]file.badextension-2019-01-01.gz\f[R].
 .SS --syslog
 .PP
 On capable OSes (not Windows or Plan9) send all log output to syslog.
 .PP
 This can be useful for running rclone in a script or
-\f[C]rclone mount\f[R].
+\f[V]rclone mount\f[R].
 .SS --syslog-facility string
 .PP
-If using \f[C]--syslog\f[R] this sets the syslog facility (e.g.
-\f[C]KERN\f[R], \f[C]USER\f[R]).
-See \f[C]man syslog\f[R] for a list of possible facilities.
-The default facility is \f[C]DAEMON\f[R].
+If using \f[V]--syslog\f[R] this sets the syslog facility (e.g.
+\f[V]KERN\f[R], \f[V]USER\f[R]).
+See \f[V]man syslog\f[R] for a list of possible facilities.
+The default facility is \f[V]DAEMON\f[R].
 .SS --temp-dir=DIR
 .PP
 Specify the directory rclone will use for temporary files, to override
@@ -19023,13 +19041,13 @@ the default.
 Make sure the directory exists and have accessible permissions.
 .PP
 By default the operating system\[aq]s temp directory will be used: - On
-Unix systems, \f[C]$TMPDIR\f[R] if non-empty, else \f[C]/tmp\f[R].
-- On Windows, the first non-empty value from \f[C]%TMP%\f[R],
-\f[C]%TEMP%\f[R], \f[C]%USERPROFILE%\f[R], or the Windows directory.
+Unix systems, \f[V]$TMPDIR\f[R] if non-empty, else \f[V]/tmp\f[R].
+- On Windows, the first non-empty value from \f[V]%TMP%\f[R],
+\f[V]%TEMP%\f[R], \f[V]%USERPROFILE%\f[R], or the Windows directory.
 .PP
 When overriding the default with this option, the specified path will be
-set as value of environment variable \f[C]TMPDIR\f[R] on Unix systems
-and \f[C]TMP\f[R] and \f[C]TEMP\f[R] on Windows.
+set as value of environment variable \f[V]TMPDIR\f[R] on Unix systems
+and \f[V]TMP\f[R] and \f[V]TEMP\f[R] on Windows.
 .PP
 You can use the config
 paths (https://rclone.org/commands/rclone_config_paths/) command to see
@@ -19045,37 +19063,37 @@ For HTTP based backends it is an HTTP PUT/GET/POST/etc and its response.
 For FTP/SFTP it is a round trip transaction over TCP.
 .PP
 For example, to limit rclone to 10 transactions per second use
-\f[C]--tpslimit 10\f[R], or to 1 transaction every 2 seconds use
-\f[C]--tpslimit 0.5\f[R].
+\f[V]--tpslimit 10\f[R], or to 1 transaction every 2 seconds use
+\f[V]--tpslimit 0.5\f[R].
 .PP
 Use this when the number of transactions per second from rclone is
 causing a problem with the cloud storage provider (e.g.
 getting you banned or rate limited).
 .PP
-This can be very useful for \f[C]rclone mount\f[R] to control the
+This can be very useful for \f[V]rclone mount\f[R] to control the
 behaviour of applications using it.
 .PP
 This limit applies to all HTTP based backends and to the FTP and SFTP
 backends.
 It does not apply to the local backend or the Storj backend.
 .PP
-See also \f[C]--tpslimit-burst\f[R].
+See also \f[V]--tpslimit-burst\f[R].
 .SS --tpslimit-burst int
 .PP
-Max burst of transactions for \f[C]--tpslimit\f[R] (default
-\f[C]1\f[R]).
+Max burst of transactions for \f[V]--tpslimit\f[R] (default
+\f[V]1\f[R]).
 .PP
-Normally \f[C]--tpslimit\f[R] will do exactly the number of transaction
+Normally \f[V]--tpslimit\f[R] will do exactly the number of transaction
 per second specified.
-However if you supply \f[C]--tps-burst\f[R] then rclone can save up some
+However if you supply \f[V]--tps-burst\f[R] then rclone can save up some
 transactions from when it was idle giving a burst of up to the parameter
 supplied.
 .PP
-For example if you provide \f[C]--tpslimit-burst 10\f[R] then if rclone
-has been idle for more than 10*\f[C]--tpslimit\f[R] then it can do 10
+For example if you provide \f[V]--tpslimit-burst 10\f[R] then if rclone
+has been idle for more than 10*\f[V]--tpslimit\f[R] then it can do 10
 transactions very quickly before they are limited again.
 .PP
-This may be used to increase performance of \f[C]--tpslimit\f[R] without
+This may be used to increase performance of \f[V]--tpslimit\f[R] without
 changing the long term average number of transactions per second.
 .SS --track-renames
 .PP
@@ -19083,21 +19101,21 @@ By default, rclone doesn\[aq]t keep track of renamed files, so if you
 rename a file locally then sync it to a remote, rclone will delete the
 old file on the remote and upload a new copy.
 .PP
-An rclone sync with \f[C]--track-renames\f[R] runs like a normal sync,
+An rclone sync with \f[V]--track-renames\f[R] runs like a normal sync,
 but keeps track of objects which exist in the destination but not in the
 source (which would normally be deleted), and which objects exist in the
 source but not the destination (which would normally be transferred).
 These objects are then candidates for renaming.
 .PP
 After the sync, rclone matches up the source only and destination only
-objects using the \f[C]--track-renames-strategy\f[R] specified and
+objects using the \f[V]--track-renames-strategy\f[R] specified and
 either renames the destination object or transfers the source and
 deletes the destination object.
-\f[C]--track-renames\f[R] is stateless like all of rclone\[aq]s syncs.
+\f[V]--track-renames\f[R] is stateless like all of rclone\[aq]s syncs.
 .PP
 To use this flag the destination must support server-side copy or
 server-side move, and to use a hash based
-\f[C]--track-renames-strategy\f[R] (the default) the source and the
+\f[V]--track-renames-strategy\f[R] (the default) the source and the
 destination must have a compatible hash.
 .PP
 If the destination does not support server-side copy or move, rclone
@@ -19105,60 +19123,60 @@ will fall back to the default behaviour and log an error level message
 to the console.
 .PP
 Encrypted destinations are not currently supported by
-\f[C]--track-renames\f[R] if \f[C]--track-renames-strategy\f[R] includes
-\f[C]hash\f[R].
+\f[V]--track-renames\f[R] if \f[V]--track-renames-strategy\f[R] includes
+\f[V]hash\f[R].
 .PP
-Note that \f[C]--track-renames\f[R] is incompatible with
-\f[C]--no-traverse\f[R] and that it uses extra memory to keep track of
+Note that \f[V]--track-renames\f[R] is incompatible with
+\f[V]--no-traverse\f[R] and that it uses extra memory to keep track of
 all the rename candidates.
 .PP
-Note also that \f[C]--track-renames\f[R] is incompatible with
-\f[C]--delete-before\f[R] and will select \f[C]--delete-after\f[R]
-instead of \f[C]--delete-during\f[R].
+Note also that \f[V]--track-renames\f[R] is incompatible with
+\f[V]--delete-before\f[R] and will select \f[V]--delete-after\f[R]
+instead of \f[V]--delete-during\f[R].
 .SS --track-renames-strategy (hash,modtime,leaf,size)
 .PP
 This option changes the file matching criteria for
-\f[C]--track-renames\f[R].
+\f[V]--track-renames\f[R].
 .PP
 The matching is controlled by a comma separated selection of these
 tokens:
 .IP \[bu] 2
-\f[C]modtime\f[R] - the modification time of the file - not supported on
+\f[V]modtime\f[R] - the modification time of the file - not supported on
 all backends
 .IP \[bu] 2
-\f[C]hash\f[R] - the hash of the file contents - not supported on all
+\f[V]hash\f[R] - the hash of the file contents - not supported on all
 backends
 .IP \[bu] 2
-\f[C]leaf\f[R] - the name of the file not including its directory name
+\f[V]leaf\f[R] - the name of the file not including its directory name
 .IP \[bu] 2
-\f[C]size\f[R] - the size of the file (this is always enabled)
+\f[V]size\f[R] - the size of the file (this is always enabled)
 .PP
-The default option is \f[C]hash\f[R].
+The default option is \f[V]hash\f[R].
 .PP
-Using \f[C]--track-renames-strategy modtime,leaf\f[R] would match files
+Using \f[V]--track-renames-strategy modtime,leaf\f[R] would match files
 based on modification time, the leaf of the file name and the size only.
 .PP
-Using \f[C]--track-renames-strategy modtime\f[R] or \f[C]leaf\f[R] can
-enable \f[C]--track-renames\f[R] support for encrypted destinations.
+Using \f[V]--track-renames-strategy modtime\f[R] or \f[V]leaf\f[R] can
+enable \f[V]--track-renames\f[R] support for encrypted destinations.
 .PP
-Note that the \f[C]hash\f[R] strategy is not supported with encrypted
+Note that the \f[V]hash\f[R] strategy is not supported with encrypted
 destinations.
 .SS --delete-(before,during,after)
 .PP
 This option allows you to specify when files on your destination are
 deleted when you sync folders.
 .PP
-Specifying the value \f[C]--delete-before\f[R] will delete all files
+Specifying the value \f[V]--delete-before\f[R] will delete all files
 present on the destination, but not on the source \f[I]before\f[R]
 starting the transfer of any new or updated files.
 This uses two passes through the file systems, one for the deletions and
 one for the copies.
 .PP
-Specifying \f[C]--delete-during\f[R] will delete files while checking
+Specifying \f[V]--delete-during\f[R] will delete files while checking
 and uploading files.
 This is the fastest option and uses the least memory.
 .PP
-Specifying \f[C]--delete-after\f[R] (the default value) will delay
+Specifying \f[V]--delete-after\f[R] (the default value) will delay
 deletion of files until all new/updated files have been successfully
 transferred.
 The files to be deleted are collected in the copy pass then deleted
@@ -19168,16 +19186,16 @@ memory.
 This is the safest mode as it will only delete files if there have been
 no errors subsequent to that.
 If there have been errors before the deletions start then you will get
-the message \f[C]not deleting files as there were IO errors\f[R].
+the message \f[V]not deleting files as there were IO errors\f[R].
 .SS --fast-list
 .PP
 When doing anything which involves a directory listing (e.g.
-\f[C]sync\f[R], \f[C]copy\f[R], \f[C]ls\f[R] - in fact nearly every
+\f[V]sync\f[R], \f[V]copy\f[R], \f[V]ls\f[R] - in fact nearly every
 command), rclone has different strategies to choose from.
 .PP
 The basic strategy is to list one directory and processes it before
 using more directory lists to process any subdirectories.
-This is a mandatory backend feature, called \f[C]List\f[R], which means
+This is a mandatory backend feature, called \f[V]List\f[R], which means
 it is supported by all backends.
 This strategy uses small amount of memory, and because it can be
 parallelised it is fast for operations involving processing of the list
@@ -19187,7 +19205,7 @@ Some backends provide the support for an alternative strategy, where all
 files beneath a directory can be listed in one (or a small number) of
 transactions.
 Rclone supports this alternative strategy through an optional backend
-feature called \f[C]ListR\f[R] (https://rclone.org/overview/#listr).
+feature called \f[V]ListR\f[R] (https://rclone.org/overview/#listr).
 You can see in the storage system overview documentation\[aq]s optional
 features (https://rclone.org/overview/#optional-features) section which
 backends it is enabled for (these tend to be the bucket-based ones, e.g.
@@ -19201,42 +19219,42 @@ require more memory if rclone has to keep the whole listing in memory.
 .PP
 Which listing strategy rclone picks for a given operation is
 complicated, but in general it tries to choose the best possible.
-It will prefer \f[C]ListR\f[R] in situations where it doesn\[aq]t need
+It will prefer \f[V]ListR\f[R] in situations where it doesn\[aq]t need
 to store the listed files in memory, e.g.
-for unlimited recursive \f[C]ls\f[R] command variants.
-In other situations it will prefer \f[C]List\f[R], e.g.
-for \f[C]sync\f[R] and \f[C]copy\f[R], where it needs to keep the listed
+for unlimited recursive \f[V]ls\f[R] command variants.
+In other situations it will prefer \f[V]List\f[R], e.g.
+for \f[V]sync\f[R] and \f[V]copy\f[R], where it needs to keep the listed
 files in memory, and is performing operations on them where
 parallelization may be a huge advantage.
 .PP
 Rclone is not able to take all relevant parameters into account for
 deciding the best strategy, and therefore allows you to influence the
-choice in two ways: You can stop rclone from using \f[C]ListR\f[R] by
+choice in two ways: You can stop rclone from using \f[V]ListR\f[R] by
 disabling the feature, using the --disable option
-(\f[C]--disable ListR\f[R]), or you can allow rclone to use
-\f[C]ListR\f[R] where it would normally choose not to do so due to
-higher memory usage, using the \f[C]--fast-list\f[R] option.
+(\f[V]--disable ListR\f[R]), or you can allow rclone to use
+\f[V]ListR\f[R] where it would normally choose not to do so due to
+higher memory usage, using the \f[V]--fast-list\f[R] option.
 Rclone should always produce identical results either way.
-Using \f[C]--disable ListR\f[R] or \f[C]--fast-list\f[R] on a remote
-which doesn\[aq]t support \f[C]ListR\f[R] does nothing, rclone will just
+Using \f[V]--disable ListR\f[R] or \f[V]--fast-list\f[R] on a remote
+which doesn\[aq]t support \f[V]ListR\f[R] does nothing, rclone will just
 ignore it.
 .PP
 A rule of thumb is that if you pay for transactions and can fit your
-entire sync listing into memory, then \f[C]--fast-list\f[R] is
+entire sync listing into memory, then \f[V]--fast-list\f[R] is
 recommended.
 If you have a very big sync to do, then don\[aq]t use
-\f[C]--fast-list\f[R], otherwise you will run out of memory.
+\f[V]--fast-list\f[R], otherwise you will run out of memory.
 Run some tests and compare before you decide, and if in doubt then just
 leave the default, let rclone decide, i.e.
-not use \f[C]--fast-list\f[R].
+not use \f[V]--fast-list\f[R].
 .SS --timeout=TIME
 .PP
 This sets the IO idle timeout.
 If a transfer has started but then becomes idle for this long it is
 considered broken and disconnected.
 .PP
-The default is \f[C]5m\f[R].
-Set to \f[C]0\f[R] to disable.
+The default is \f[V]5m\f[R].
+Set to \f[V]0\f[R] to disable.
 .SS --transfers=N
 .PP
 The number of file transfers to run in parallel.
@@ -19255,10 +19273,10 @@ have a modified time that is newer than the source file.
 .PP
 This can be useful in avoiding needless transfers when transferring to a
 remote which doesn\[aq]t support modification times directly (or when
-using \f[C]--use-server-modtime\f[R] to avoid extra API calls) as it is
-more accurate than a \f[C]--size-only\f[R] check and faster than using
-\f[C]--checksum\f[R].
-On such remotes (or when using \f[C]--use-server-modtime\f[R]) the time
+using \f[V]--use-server-modtime\f[R] to avoid extra API calls) as it is
+more accurate than a \f[V]--size-only\f[R] check and faster than using
+\f[V]--checksum\f[R].
+On such remotes (or when using \f[V]--use-server-modtime\f[R]) the time
 checked will be the uploaded time.
 .PP
 If an existing destination file has a modification time older than the
@@ -19270,11 +19288,11 @@ If an existing destination file has a modification time equal (within
 the computed modify window) to the source file\[aq]s, it will be updated
 if the sizes are different.
 The checksum will not be checked in this case unless the
-\f[C]--checksum\f[R] flag is provided.
+\f[V]--checksum\f[R] flag is provided.
 .PP
 In all other cases the file will not be updated.
 .PP
-Consider using the \f[C]--modify-window\f[R] flag to compensate for time
+Consider using the \f[V]--modify-window\f[R] flag to compensate for time
 skews between the source and the backend, for backends that do not
 support mod times, and instead use uploaded times.
 However, if the backend does not support checksums, note that syncing or
@@ -19284,7 +19302,7 @@ transfers for safety.
 .PP
 If this flag is set then rclone will use anonymous memory allocated by
 mmap on Unix based platforms and VirtualAlloc on Windows for its
-transfer buffers (size controlled by \f[C]--buffer-size\f[R]).
+transfer buffers (size controlled by \f[V]--buffer-size\f[R]).
 Memory allocated like this does not go on the Go heap and can be
 returned to the OS immediately when it is finished with.
 .PP
@@ -19305,28 +19323,28 @@ modtime is needed by an operation.
 .PP
 Use this flag to disable the extra API call and rely instead on the
 server\[aq]s modified time.
-In cases such as a local to remote sync using \f[C]--update\f[R],
+In cases such as a local to remote sync using \f[V]--update\f[R],
 knowing the local file is newer than the time it was last uploaded to
 the remote is sufficient.
 In those cases, this flag can speed up the process and reduce the number
 of API calls necessary.
 .PP
 Using this flag on a sync operation without also using
-\f[C]--update\f[R] would cause all files modified at any time other than
+\f[V]--update\f[R] would cause all files modified at any time other than
 the last upload time to be uploaded again, which is probably not what
 you want.
 .SS -v, -vv, --verbose
 .PP
-With \f[C]-v\f[R] rclone will tell you about each file that is
+With \f[V]-v\f[R] rclone will tell you about each file that is
 transferred and a small number of significant events.
 .PP
-With \f[C]-vv\f[R] rclone will become very verbose telling you about
+With \f[V]-vv\f[R] rclone will become very verbose telling you about
 every file it considers and transfers.
 Please send bug reports with a log with this setting.
 .PP
 When setting verbosity as an environment variable, use
-\f[C]RCLONE_VERBOSE=1\f[R] or \f[C]RCLONE_VERBOSE=2\f[R] for
-\f[C]-v\f[R] and \f[C]-vv\f[R] respectively.
+\f[V]RCLONE_VERBOSE=1\f[R] or \f[V]RCLONE_VERBOSE=2\f[R] for
+\f[V]-v\f[R] and \f[V]-vv\f[R] respectively.
 .SS -V, --version
 .PP
 Prints the version number
@@ -19351,28 +19369,28 @@ This loads the PEM encoded client side certificate.
 This is used for mutual TLS
 authentication (https://en.wikipedia.org/wiki/Mutual_authentication).
 .PP
-The \f[C]--client-key\f[R] flag is required too when using this.
+The \f[V]--client-key\f[R] flag is required too when using this.
 .SS --client-key string
 .PP
 This loads the PEM encoded client side private key used for mutual TLS
 authentication.
-Used in conjunction with \f[C]--client-cert\f[R].
+Used in conjunction with \f[V]--client-cert\f[R].
 .SS --no-check-certificate=true/false
 .PP
-\f[C]--no-check-certificate\f[R] controls whether a client verifies the
+\f[V]--no-check-certificate\f[R] controls whether a client verifies the
 server\[aq]s certificate chain and host name.
-If \f[C]--no-check-certificate\f[R] is true, TLS accepts any certificate
+If \f[V]--no-check-certificate\f[R] is true, TLS accepts any certificate
 presented by the server and any host name in that certificate.
 In this mode, TLS is susceptible to man-in-the-middle attacks.
 .PP
-This option defaults to \f[C]false\f[R].
+This option defaults to \f[V]false\f[R].
 .PP
 \f[B]This should be used only for testing.\f[R]
 .SS Configuration Encryption
 .PP
 Your configuration file contains information for logging in to your
 cloud services.
-This means that you should keep your \f[C]rclone.conf\f[R] file in a
+This means that you should keep your \f[V]rclone.conf\f[R] file in a
 secure location.
 .PP
 If you are in an environment where that isn\[aq]t possible, you can add
@@ -19381,7 +19399,7 @@ This means that you will have to supply the password every time you
 start rclone.
 .PP
 To add a password to your rclone configuration, execute
-\f[C]rclone config\f[R].
+\f[V]rclone config\f[R].
 .IP
 .nf
 \f[C]
@@ -19397,7 +19415,7 @@ e/n/d/s/q>
 \f[R]
 .fi
 .PP
-Go into \f[C]s\f[R], Set configuration password:
+Go into \f[V]s\f[R], Set configuration password:
 .IP
 .nf
 \f[C]
@@ -19454,13 +19472,13 @@ encrypted rclone configuration in public if it contains sensitive
 information, maybe except if you use a very strong password.
 .PP
 If it is safe in your environment, you can set the
-\f[C]RCLONE_CONFIG_PASS\f[R] environment variable to contain your
+\f[V]RCLONE_CONFIG_PASS\f[R] environment variable to contain your
 password, in which case it will be used for decrypting the
 configuration.
 .PP
 You can set this for a session from a script.
 For unix like systems save this to a file called
-\f[C]set-rclone-password\f[R]:
+\f[V]set-rclone-password\f[R]:
 .IP
 .nf
 \f[C]
@@ -19472,7 +19490,7 @@ export RCLONE_CONFIG_PASS
 .fi
 .PP
 Then source the file when you want to use it.
-From the shell you would do \f[C]source set-rclone-password\f[R].
+From the shell you would do \f[V]source set-rclone-password\f[R].
 It will then ask you for the password and set it in the environment
 variable.
 .PP
@@ -19481,10 +19499,10 @@ which will retrieve the password and print on standard output.
 This script should have a fully specified path name and not rely on any
 environment variables.
 The script is supplied either via
-\f[C]--password-command=\[dq]...\[dq]\f[R] command line argument or via
-the \f[C]RCLONE_PASSWORD_COMMAND\f[R] environment variable.
+\f[V]--password-command=\[dq]...\[dq]\f[R] command line argument or via
+the \f[V]RCLONE_PASSWORD_COMMAND\f[R] environment variable.
 .PP
-One useful example of this is using the \f[C]passwordstore\f[R]
+One useful example of this is using the \f[V]passwordstore\f[R]
 application to retrieve the password:
 .IP
 .nf
@@ -19493,9 +19511,9 @@ export RCLONE_PASSWORD_COMMAND=\[dq]pass rclone/config\[dq]
 \f[R]
 .fi
 .PP
-If the \f[C]passwordstore\f[R] password manager holds the password for
+If the \f[V]passwordstore\f[R] password manager holds the password for
 the rclone configuration, using the script method means the password is
-primarily protected by the \f[C]passwordstore\f[R] system, and is never
+primarily protected by the \f[V]passwordstore\f[R] system, and is never
 embedded in the clear in scripts, nor available for examination using
 the standard commands available.
 It is quite possible with long running rclone sessions for copies of
@@ -19505,12 +19523,12 @@ Using the script method of supplying the password enhances the security
 of the config password considerably.
 .PP
 If you are running rclone inside a script, unless you are using the
-\f[C]--password-command\f[R] method, you might want to disable password
+\f[V]--password-command\f[R] method, you might want to disable password
 prompts.
-To do that, pass the parameter \f[C]--ask-password=false\f[R] to rclone.
+To do that, pass the parameter \f[V]--ask-password=false\f[R] to rclone.
 This will make rclone fail instead of asking for a password if
-\f[C]RCLONE_CONFIG_PASS\f[R] doesn\[aq]t contain a valid password, and
-\f[C]--password-command\f[R] has not been supplied.
+\f[V]RCLONE_CONFIG_PASS\f[R] doesn\[aq]t contain a valid password, and
+\f[V]--password-command\f[R] has not been supplied.
 .PP
 Whenever running commands that may be affected by options in a
 configuration file, rclone will look for an existing file according to
@@ -19523,11 +19541,11 @@ by overriding the location, e.g.
 with one of the documented special values for memory-only configuration.
 Since only backend options can be stored in configuration files, this is
 normally unnecessary for commands that do not operate on backends, e.g.
-\f[C]completion\f[R].
+\f[V]completion\f[R].
 However, it will be relevant for commands that do operate on backends in
 general, but are used without referencing a stored remote, e.g.
 listing local filesystem paths, or connection strings:
-\f[C]rclone --config=\[dq]\[dq] ls .\f[R]
+\f[V]rclone --config=\[dq]\[dq] ls .\f[R]
 .SS Configuration Encryption Cheatsheet
 .PP
 You can quickly apply a configuration encryption without plain-text at
@@ -19537,11 +19555,11 @@ Detailed instructions for popular OSes:
 .IP \[bu] 2
 Generate and store a password
 .PP
-\f[C]security add-generic-password -a rclone -s config -w $(openssl rand -base64 40)\f[R]
+\f[V]security add-generic-password -a rclone -s config -w $(openssl rand -base64 40)\f[R]
 .IP \[bu] 2
 Add the retrieval instruction to your .zprofile / .profile
 .PP
-\f[C]export RCLONE_PASSWORD_COMMAND=\[dq]/usr/bin/security find-generic-password -a rclone -s config -w\[dq]\f[R]
+\f[V]export RCLONE_PASSWORD_COMMAND=\[dq]/usr/bin/security find-generic-password -a rclone -s config -w\[dq]\f[R]
 .SS Linux
 .IP \[bu] 2
 Prerequisite
@@ -19549,31 +19567,31 @@ Prerequisite
 Linux doesn\[aq]t come with a default password manager.
 Let\[aq]s install the \[dq]pass\[dq] utility using a package manager,
 e.g.
-\f[C]apt install pass\f[R], \f[C]yum install pass\f[R],
+\f[V]apt install pass\f[R], \f[V]yum install pass\f[R],
 etc. (https://www.passwordstore.org/#download); then initialize a
 password store:
 .PP
-\f[C]pass init rclone\f[R]
+\f[V]pass init rclone\f[R]
 .IP \[bu] 2
 Generate and store a password
 .PP
-\f[C]echo $(openssl rand -base64 40) | pass insert -m rclone/config\f[R]
+\f[V]echo $(openssl rand -base64 40) | pass insert -m rclone/config\f[R]
 .IP \[bu] 2
 Add the retrieval instruction
 .PP
-\f[C]export RCLONE_PASSWORD_COMMAND=\[dq]/usr/bin/pass rclone/config\[dq]\f[R]
+\f[V]export RCLONE_PASSWORD_COMMAND=\[dq]/usr/bin/pass rclone/config\[dq]\f[R]
 .SS Windows
 .IP \[bu] 2
 Generate and store a password
 .PP
-\f[C]New-Object -TypeName PSCredential -ArgumentList \[dq]rclone\[dq], (ConvertTo-SecureString -String ([System.Web.Security.Membership]::GeneratePassword(40, 10)) -AsPlainText -Force) | Export-Clixml -Path \[dq]rclone-credential.xml\[dq]\f[R]
+\f[V]New-Object -TypeName PSCredential -ArgumentList \[dq]rclone\[dq], (ConvertTo-SecureString -String ([System.Web.Security.Membership]::GeneratePassword(40, 10)) -AsPlainText -Force) | Export-Clixml -Path \[dq]rclone-credential.xml\[dq]\f[R]
 .IP \[bu] 2
 Add the password retrieval instruction
 .PP
-\f[C][Environment]::SetEnvironmentVariable(\[dq]RCLONE_PASSWORD_COMMAND\[dq], \[dq][System.Runtime.InteropServices.Marshal]::PtrToStringAuto([System.Runtime.InteropServices.Marshal]::SecureStringToBSTR((Import-Clixml -Path \[dq]rclone-credential.xml\[dq]).Password))\[dq])\f[R]
+\f[V][Environment]::SetEnvironmentVariable(\[dq]RCLONE_PASSWORD_COMMAND\[dq], \[dq][System.Runtime.InteropServices.Marshal]::PtrToStringAuto([System.Runtime.InteropServices.Marshal]::SecureStringToBSTR((Import-Clixml -Path \[dq]rclone-credential.xml\[dq]).Password))\[dq])\f[R]
 .SS Encrypt the config file (all systems)
 .IP \[bu] 2
-Execute \f[C]rclone config\f[R] -> \f[C]s\f[R]
+Execute \f[V]rclone config\f[R] -> \f[V]s\f[R]
 .IP \[bu] 2
 Add/update the password from previous steps
 .SS Developer options
@@ -19582,19 +19600,19 @@ These options are useful when developing or debugging rclone.
 There are also some more remote specific options which aren\[aq]t
 documented here which are used for testing.
 These start with remote name e.g.
-\f[C]--drive-test-option\f[R] - see the docs for the remote in question.
+\f[V]--drive-test-option\f[R] - see the docs for the remote in question.
 .SS --cpuprofile=FILE
 .PP
 Write CPU profile to file.
-This can be analysed with \f[C]go tool pprof\f[R].
+This can be analysed with \f[V]go tool pprof\f[R].
 .SS --dump flag,flag,flag
 .PP
-The \f[C]--dump\f[R] flag takes a comma separated list of flags to dump
+The \f[V]--dump\f[R] flag takes a comma separated list of flags to dump
 info about.
 .PP
-Note that some headers including \f[C]Accept-Encoding\f[R] as shown may
+Note that some headers including \f[V]Accept-Encoding\f[R] as shown may
 not be correct in the request and the response may not show
-\f[C]Content-Encoding\f[R] if the go standard libraries auto gzip
+\f[V]Content-Encoding\f[R] if the go standard libraries auto gzip
 encoding was in effect.
 In this case the body of the request will be gunzipped before showing
 it.
@@ -19602,12 +19620,12 @@ it.
 The available flags are:
 .SS --dump headers
 .PP
-Dump HTTP headers with \f[C]Authorization:\f[R] lines removed.
+Dump HTTP headers with \f[V]Authorization:\f[R] lines removed.
 May still contain sensitive info.
 Can be very verbose.
 Useful for debugging only.
 .PP
-Use \f[C]--dump auth\f[R] if you do want the \f[C]Authorization:\f[R]
+Use \f[V]--dump auth\f[R] if you do want the \f[V]Authorization:\f[R]
 headers.
 .SS --dump bodies
 .PP
@@ -19619,19 +19637,19 @@ Note that the bodies are buffered in memory so don\[aq]t use this for
 enormous files.
 .SS --dump requests
 .PP
-Like \f[C]--dump bodies\f[R] but dumps the request bodies and the
+Like \f[V]--dump bodies\f[R] but dumps the request bodies and the
 response headers.
 Useful for debugging download problems.
 .SS --dump responses
 .PP
-Like \f[C]--dump bodies\f[R] but dumps the response bodies and the
+Like \f[V]--dump bodies\f[R] but dumps the response bodies and the
 request headers.
 Useful for debugging upload problems.
 .SS --dump auth
 .PP
 Dump HTTP headers - will contain sensitive info such as
-\f[C]Authorization:\f[R] headers - use \f[C]--dump headers\f[R] to dump
-without \f[C]Authorization:\f[R] headers.
+\f[V]Authorization:\f[R] headers - use \f[V]--dump headers\f[R] to dump
+without \f[V]Authorization:\f[R] headers.
 Can be very verbose.
 Useful for debugging only.
 .SS --dump filters
@@ -19645,62 +19663,62 @@ to standard output.
 .SS --dump openfiles
 .PP
 This dumps a list of the open files at the end of the command.
-It uses the \f[C]lsof\f[R] command to do that so you\[aq]ll need that
+It uses the \f[V]lsof\f[R] command to do that so you\[aq]ll need that
 installed to use it.
 .SS --dump mapper
 .PP
 This shows the JSON blobs being sent to the program supplied with
-\f[C]--metadata-mapper\f[R] and received from it.
+\f[V]--metadata-mapper\f[R] and received from it.
 It can be useful for debugging the metadata mapper interface.
 .SS --memprofile=FILE
 .PP
 Write memory profile to file.
-This can be analysed with \f[C]go tool pprof\f[R].
+This can be analysed with \f[V]go tool pprof\f[R].
 .SS Filtering
 .PP
 For the filtering options
 .IP \[bu] 2
-\f[C]--delete-excluded\f[R]
+\f[V]--delete-excluded\f[R]
 .IP \[bu] 2
-\f[C]--filter\f[R]
+\f[V]--filter\f[R]
 .IP \[bu] 2
-\f[C]--filter-from\f[R]
+\f[V]--filter-from\f[R]
 .IP \[bu] 2
-\f[C]--exclude\f[R]
+\f[V]--exclude\f[R]
 .IP \[bu] 2
-\f[C]--exclude-from\f[R]
+\f[V]--exclude-from\f[R]
 .IP \[bu] 2
-\f[C]--exclude-if-present\f[R]
+\f[V]--exclude-if-present\f[R]
 .IP \[bu] 2
-\f[C]--include\f[R]
+\f[V]--include\f[R]
 .IP \[bu] 2
-\f[C]--include-from\f[R]
+\f[V]--include-from\f[R]
 .IP \[bu] 2
-\f[C]--files-from\f[R]
+\f[V]--files-from\f[R]
 .IP \[bu] 2
-\f[C]--files-from-raw\f[R]
+\f[V]--files-from-raw\f[R]
 .IP \[bu] 2
-\f[C]--min-size\f[R]
+\f[V]--min-size\f[R]
 .IP \[bu] 2
-\f[C]--max-size\f[R]
+\f[V]--max-size\f[R]
 .IP \[bu] 2
-\f[C]--min-age\f[R]
+\f[V]--min-age\f[R]
 .IP \[bu] 2
-\f[C]--max-age\f[R]
+\f[V]--max-age\f[R]
 .IP \[bu] 2
-\f[C]--dump filters\f[R]
+\f[V]--dump filters\f[R]
 .IP \[bu] 2
-\f[C]--metadata-include\f[R]
+\f[V]--metadata-include\f[R]
 .IP \[bu] 2
-\f[C]--metadata-include-from\f[R]
+\f[V]--metadata-include-from\f[R]
 .IP \[bu] 2
-\f[C]--metadata-exclude\f[R]
+\f[V]--metadata-exclude\f[R]
 .IP \[bu] 2
-\f[C]--metadata-exclude-from\f[R]
+\f[V]--metadata-exclude-from\f[R]
 .IP \[bu] 2
-\f[C]--metadata-filter\f[R]
+\f[V]--metadata-filter\f[R]
 .IP \[bu] 2
-\f[C]--metadata-filter-from\f[R]
+\f[V]--metadata-filter-from\f[R]
 .PP
 See the filtering section (https://rclone.org/filtering/).
 .SS Remote control
@@ -19708,41 +19726,41 @@ See the filtering section (https://rclone.org/filtering/).
 For the remote control options and for instructions on how to remote
 control rclone
 .IP \[bu] 2
-\f[C]--rc\f[R]
+\f[V]--rc\f[R]
 .IP \[bu] 2
-and anything starting with \f[C]--rc-\f[R]
+and anything starting with \f[V]--rc-\f[R]
 .PP
 See the remote control section (https://rclone.org/rc/).
 .SS Logging
 .PP
-rclone has 4 levels of logging, \f[C]ERROR\f[R], \f[C]NOTICE\f[R],
-\f[C]INFO\f[R] and \f[C]DEBUG\f[R].
+rclone has 4 levels of logging, \f[V]ERROR\f[R], \f[V]NOTICE\f[R],
+\f[V]INFO\f[R] and \f[V]DEBUG\f[R].
 .PP
 By default, rclone logs to standard error.
 This means you can redirect standard error and still see the normal
 output of rclone commands (e.g.
-\f[C]rclone ls\f[R]).
+\f[V]rclone ls\f[R]).
 .PP
-By default, rclone will produce \f[C]Error\f[R] and \f[C]Notice\f[R]
+By default, rclone will produce \f[V]Error\f[R] and \f[V]Notice\f[R]
 level messages.
 .PP
-If you use the \f[C]-q\f[R] flag, rclone will only produce
-\f[C]Error\f[R] messages.
+If you use the \f[V]-q\f[R] flag, rclone will only produce
+\f[V]Error\f[R] messages.
 .PP
-If you use the \f[C]-v\f[R] flag, rclone will produce \f[C]Error\f[R],
-\f[C]Notice\f[R] and \f[C]Info\f[R] messages.
+If you use the \f[V]-v\f[R] flag, rclone will produce \f[V]Error\f[R],
+\f[V]Notice\f[R] and \f[V]Info\f[R] messages.
 .PP
-If you use the \f[C]-vv\f[R] flag, rclone will produce \f[C]Error\f[R],
-\f[C]Notice\f[R], \f[C]Info\f[R] and \f[C]Debug\f[R] messages.
+If you use the \f[V]-vv\f[R] flag, rclone will produce \f[V]Error\f[R],
+\f[V]Notice\f[R], \f[V]Info\f[R] and \f[V]Debug\f[R] messages.
 .PP
-You can also control the log levels with the \f[C]--log-level\f[R] flag.
+You can also control the log levels with the \f[V]--log-level\f[R] flag.
 .PP
-If you use the \f[C]--log-file=FILE\f[R] option, rclone will redirect
-\f[C]Error\f[R], \f[C]Info\f[R] and \f[C]Debug\f[R] messages along with
+If you use the \f[V]--log-file=FILE\f[R] option, rclone will redirect
+\f[V]Error\f[R], \f[V]Info\f[R] and \f[V]Debug\f[R] messages along with
 standard error to FILE.
 .PP
-If you use the \f[C]--syslog\f[R] flag then rclone will log to syslog
-and the \f[C]--syslog-facility\f[R] control which facility it uses.
+If you use the \f[V]--syslog\f[R] flag then rclone will log to syslog
+and the \f[V]--syslog-facility\f[R] control which facility it uses.
 .PP
 Rclone prefixes all log messages with their level in capitals, e.g.
 INFO which makes it easy to grep the log file for different kinds of
@@ -19751,20 +19769,20 @@ information.
 .PP
 Rclone can publish metrics in the OpenMetrics/Prometheus format.
 .PP
-To enable the metrics endpoint, use the \f[C]--metrics-addr\f[R] flag.
-Metrics can also be published on the \f[C]--rc-addr\f[R] port if the
-\f[C]--rc\f[R] flag and \f[C]--rc-enable-metrics\f[R] flags are supplied
-or if using rclone rcd \f[C]--rc-enable-metrics\f[R]
+To enable the metrics endpoint, use the \f[V]--metrics-addr\f[R] flag.
+Metrics can also be published on the \f[V]--rc-addr\f[R] port if the
+\f[V]--rc\f[R] flag and \f[V]--rc-enable-metrics\f[R] flags are supplied
+or if using rclone rcd \f[V]--rc-enable-metrics\f[R]
 .PP
 Rclone provides extensive configuration options for the metrics HTTP
 endpoint.
 These settings are grouped under the Metrics section and have a prefix
-\f[C]--metrics-*\f[R].
+\f[V]--metrics-*\f[R].
 .PP
-When metrics are enabled with \f[C]--rc-enable-metrics\f[R], they will
+When metrics are enabled with \f[V]--rc-enable-metrics\f[R], they will
 be published on the same port as the rc API.
-In this case, the \f[C]--metrics-*\f[R] flags will be ignored, and the
-HTTP endpoint configuration will be managed by the \f[C]--rc-*\f[R]
+In this case, the \f[V]--metrics-*\f[R] flags will be ignored, and the
+HTTP endpoint configuration will be managed by the \f[V]--rc-*\f[R]
 parameters.
 .SS Exit Code
 .PP
@@ -19780,7 +19798,7 @@ When rclone is running it will accumulate errors as it goes along, and
 only exit with a non-zero exit code if (after retries) there were still
 failed transfers.
 For every error counted there will be a high priority log message
-(visible with \f[C]-q\f[R]) showing the message and which file caused
+(visible with \f[V]-q\f[R]) showing the message and which file caused
 the problem.
 A high priority message is also shown when starting a retry so the user
 can see that any previous error messages may not be valid after the
@@ -19789,31 +19807,31 @@ If rclone has done a retry it will log a high priority message if the
 retry was successful.
 .SS List of exit codes
 .IP \[bu] 2
-\f[C]0\f[R] - success
+\f[V]0\f[R] - success
 .IP \[bu] 2
-\f[C]1\f[R] - Syntax or usage error
+\f[V]1\f[R] - Syntax or usage error
 .IP \[bu] 2
-\f[C]2\f[R] - Error not otherwise categorised
+\f[V]2\f[R] - Error not otherwise categorised
 .IP \[bu] 2
-\f[C]3\f[R] - Directory not found
+\f[V]3\f[R] - Directory not found
 .IP \[bu] 2
-\f[C]4\f[R] - File not found
+\f[V]4\f[R] - File not found
 .IP \[bu] 2
-\f[C]5\f[R] - Temporary error (one that more retries might fix) (Retry
+\f[V]5\f[R] - Temporary error (one that more retries might fix) (Retry
 errors)
 .IP \[bu] 2
-\f[C]6\f[R] - Less serious errors (like 461 errors from dropbox)
+\f[V]6\f[R] - Less serious errors (like 461 errors from dropbox)
 (NoRetry errors)
 .IP \[bu] 2
-\f[C]7\f[R] - Fatal error (one that more retries won\[aq]t fix, like
+\f[V]7\f[R] - Fatal error (one that more retries won\[aq]t fix, like
 account suspended) (Fatal errors)
 .IP \[bu] 2
-\f[C]8\f[R] - Transfer exceeded - limit set by --max-transfer reached
+\f[V]8\f[R] - Transfer exceeded - limit set by --max-transfer reached
 .IP \[bu] 2
-\f[C]9\f[R] - Operation successful, but no files transferred (Requires
-\f[C]--error-on-no-transfer\f[R])
+\f[V]9\f[R] - Operation successful, but no files transferred (Requires
+\f[V]--error-on-no-transfer\f[R])
 .IP \[bu] 2
-\f[C]10\f[R] - Duration exceeded - limit set by --max-duration reached
+\f[V]10\f[R] - Duration exceeded - limit set by --max-duration reached
 .SS Environment Variables
 .PP
 Rclone can be configured entirely using environment variables.
@@ -19823,29 +19841,29 @@ These can be used to set defaults for options or config file entries.
 Every option in rclone can have its default set by environment variable.
 .PP
 To find the name of the environment variable, first, take the long
-option name, strip the leading \f[C]--\f[R], change \f[C]-\f[R] to
-\f[C]_\f[R], make upper case and prepend \f[C]RCLONE_\f[R].
+option name, strip the leading \f[V]--\f[R], change \f[V]-\f[R] to
+\f[V]_\f[R], make upper case and prepend \f[V]RCLONE_\f[R].
 .PP
-For example, to always set \f[C]--stats 5s\f[R], set the environment
-variable \f[C]RCLONE_STATS=5s\f[R].
+For example, to always set \f[V]--stats 5s\f[R], set the environment
+variable \f[V]RCLONE_STATS=5s\f[R].
 If you set stats on the command line this will override the environment
 variable setting.
 .PP
-Or to always use the trash in drive \f[C]--drive-use-trash\f[R], set
-\f[C]RCLONE_DRIVE_USE_TRASH=true\f[R].
+Or to always use the trash in drive \f[V]--drive-use-trash\f[R], set
+\f[V]RCLONE_DRIVE_USE_TRASH=true\f[R].
 .PP
 Verbosity is slightly different, the environment variable equivalent of
-\f[C]--verbose\f[R] or \f[C]-v\f[R] is \f[C]RCLONE_VERBOSE=1\f[R], or
-for \f[C]-vv\f[R], \f[C]RCLONE_VERBOSE=2\f[R].
+\f[V]--verbose\f[R] or \f[V]-v\f[R] is \f[V]RCLONE_VERBOSE=1\f[R], or
+for \f[V]-vv\f[R], \f[V]RCLONE_VERBOSE=2\f[R].
 .PP
 The same parser is used for the options and the environment variables so
 they take exactly the same form.
 .PP
 The options set by environment variables can be seen with the
-\f[C]-vv\f[R] flag, e.g.
-\f[C]rclone version -vv\f[R].
+\f[V]-vv\f[R] flag, e.g.
+\f[V]rclone version -vv\f[R].
 .PP
-Options that can appear multiple times (type \f[C]stringArray\f[R]) are
+Options that can appear multiple times (type \f[V]stringArray\f[R]) are
 treated slighly differently as environment variables can only be defined
 once.
 In order to allow a simple mechanism for adding one or many items, the
@@ -19863,28 +19881,28 @@ Equivalent options
 T}
 _
 T{
-\f[C]RCLONE_EXCLUDE=\[dq]*.jpg\[dq]\f[R]
+\f[V]RCLONE_EXCLUDE=\[dq]*.jpg\[dq]\f[R]
 T}@T{
-\f[C]--exclude \[dq]*.jpg\[dq]\f[R]
+\f[V]--exclude \[dq]*.jpg\[dq]\f[R]
 T}
 T{
-\f[C]RCLONE_EXCLUDE=\[dq]*.jpg,*.png\[dq]\f[R]
+\f[V]RCLONE_EXCLUDE=\[dq]*.jpg,*.png\[dq]\f[R]
 T}@T{
-\f[C]--exclude \[dq]*.jpg\[dq]\f[R] \f[C]--exclude \[dq]*.png\[dq]\f[R]
+\f[V]--exclude \[dq]*.jpg\[dq]\f[R] \f[V]--exclude \[dq]*.png\[dq]\f[R]
 T}
 T{
-\f[C]RCLONE_EXCLUDE=\[aq]\[dq]*.jpg\[dq],\[dq]*.png\[dq]\[aq]\f[R]
+\f[V]RCLONE_EXCLUDE=\[aq]\[dq]*.jpg\[dq],\[dq]*.png\[dq]\[aq]\f[R]
 T}@T{
-\f[C]--exclude \[dq]*.jpg\[dq]\f[R] \f[C]--exclude \[dq]*.png\[dq]\f[R]
+\f[V]--exclude \[dq]*.jpg\[dq]\f[R] \f[V]--exclude \[dq]*.png\[dq]\f[R]
 T}
 T{
-\f[C]RCLONE_EXCLUDE=\[aq]\[dq]/directory with comma , in it /**\[dq]\[aq]\f[R]
+\f[V]RCLONE_EXCLUDE=\[aq]\[dq]/directory with comma , in it /**\[dq]\[aq]\f[R]
 T}@T{
 \[ga]--exclude \[dq]/directory with comma , in it /**\[dq]
 T}
 .TE
 .PP
-If \f[C]stringArray\f[R] options are defined as environment variables
+If \f[V]stringArray\f[R] options are defined as environment variables
 \f[B]and\f[R] options on the command line then all the values will be
 used.
 .SS Config file
@@ -19895,13 +19913,13 @@ The names of the config items are documented in the page for each
 backend.
 .PP
 To find the name of the environment variable, you need to set, take
-\f[C]RCLONE_CONFIG_\f[R] + name of remote + \f[C]_\f[R] + name of config
+\f[V]RCLONE_CONFIG_\f[R] + name of remote + \f[V]_\f[R] + name of config
 file option and make it all uppercase.
 Note one implication here is the remote\[aq]s name must be convertible
 into a valid environment variable name, so it can only contain letters,
-digits, or the \f[C]_\f[R] (underscore) character.
+digits, or the \f[V]_\f[R] (underscore) character.
 .PP
-For example, to configure an S3 remote named \f[C]mys3:\f[R] without a
+For example, to configure an S3 remote named \f[V]mys3:\f[R] without a
 config file (using unix ways of setting environment variables):
 .IP
 .nf
@@ -19917,7 +19935,7 @@ mys3:
 .fi
 .PP
 Note that if you want to create a remote using environment variables you
-must create the \f[C]..._TYPE\f[R] variable as above.
+must create the \f[V]..._TYPE\f[R] variable as above.
 .PP
 Note that the name of a remote created using environment variable is
 case insensitive, in contrast to regular remotes stored in config file
@@ -19955,54 +19973,54 @@ The various different methods of backend configuration are read in this
 order and the first one with a value is used.
 .IP \[bu] 2
 Parameters in connection strings, e.g.
-\f[C]myRemote,skip_links:\f[R]
+\f[V]myRemote,skip_links:\f[R]
 .IP \[bu] 2
 Flag values as supplied on the command line, e.g.
-\f[C]--skip-links\f[R]
+\f[V]--skip-links\f[R]
 .IP \[bu] 2
 Remote specific environment vars, e.g.
-\f[C]RCLONE_CONFIG_MYREMOTE_SKIP_LINKS\f[R] (see above).
+\f[V]RCLONE_CONFIG_MYREMOTE_SKIP_LINKS\f[R] (see above).
 .IP \[bu] 2
 Backend-specific environment vars, e.g.
-\f[C]RCLONE_LOCAL_SKIP_LINKS\f[R].
+\f[V]RCLONE_LOCAL_SKIP_LINKS\f[R].
 .IP \[bu] 2
 Backend generic environment vars, e.g.
-\f[C]RCLONE_SKIP_LINKS\f[R].
+\f[V]RCLONE_SKIP_LINKS\f[R].
 .IP \[bu] 2
 Config file, e.g.
-\f[C]skip_links = true\f[R].
+\f[V]skip_links = true\f[R].
 .IP \[bu] 2
 Default values, e.g.
-\f[C]false\f[R] - these can\[aq]t be changed.
+\f[V]false\f[R] - these can\[aq]t be changed.
 .PP
-So if both \f[C]--skip-links\f[R] is supplied on the command line and an
-environment variable \f[C]RCLONE_LOCAL_SKIP_LINKS\f[R] is set, the
+So if both \f[V]--skip-links\f[R] is supplied on the command line and an
+environment variable \f[V]RCLONE_LOCAL_SKIP_LINKS\f[R] is set, the
 command line flag will take preference.
 .PP
 The backend configurations set by environment variables can be seen with
-the \f[C]-vv\f[R] flag, e.g.
-\f[C]rclone about myRemote: -vv\f[R].
+the \f[V]-vv\f[R] flag, e.g.
+\f[V]rclone about myRemote: -vv\f[R].
 .PP
 For non backend configuration the order is as follows:
 .IP \[bu] 2
 Flag values as supplied on the command line, e.g.
-\f[C]--stats 5s\f[R].
+\f[V]--stats 5s\f[R].
 .IP \[bu] 2
 Environment vars, e.g.
-\f[C]RCLONE_STATS=5s\f[R].
+\f[V]RCLONE_STATS=5s\f[R].
 .IP \[bu] 2
 Default values, e.g.
-\f[C]1m\f[R] - these can\[aq]t be changed.
+\f[V]1m\f[R] - these can\[aq]t be changed.
 .SS Other environment variables
 .IP \[bu] 2
-\f[C]RCLONE_CONFIG_PASS\f[R] set to contain your config file password
+\f[V]RCLONE_CONFIG_PASS\f[R] set to contain your config file password
 (see Configuration Encryption section)
 .IP \[bu] 2
-\f[C]HTTP_PROXY\f[R], \f[C]HTTPS_PROXY\f[R] and \f[C]NO_PROXY\f[R] (or
+\f[V]HTTP_PROXY\f[R], \f[V]HTTPS_PROXY\f[R] and \f[V]NO_PROXY\f[R] (or
 the lowercase versions thereof).
 .RS 2
 .IP \[bu] 2
-\f[C]HTTPS_PROXY\f[R] takes precedence over \f[C]HTTP_PROXY\f[R] for
+\f[V]HTTPS_PROXY\f[R] takes precedence over \f[V]HTTP_PROXY\f[R] for
 https requests.
 .IP \[bu] 2
 The environment values may be either a complete URL or a
@@ -20010,20 +20028,20 @@ The environment values may be either a complete URL or a
 assumed.
 .RE
 .IP \[bu] 2
-\f[C]USER\f[R] and \f[C]LOGNAME\f[R] values are used as fallbacks for
+\f[V]USER\f[R] and \f[V]LOGNAME\f[R] values are used as fallbacks for
 current username.
 The primary method for looking up username is OS-specific: Windows API
 on Windows, real user ID in /etc/passwd on Unix systems.
 In the documentation the current username is simply referred to as
-\f[C]$USER\f[R].
+\f[V]$USER\f[R].
 .IP \[bu] 2
-\f[C]RCLONE_CONFIG_DIR\f[R] - rclone \f[B]sets\f[R] this variable for
+\f[V]RCLONE_CONFIG_DIR\f[R] - rclone \f[B]sets\f[R] this variable for
 use in config files and sub processes to point to the directory holding
 the config file.
 .PP
 The options set by environment variables can be seen with the
-\f[C]-vv\f[R] and \f[C]--log-level=DEBUG\f[R] flags, e.g.
-\f[C]rclone version -vv\f[R].
+\f[V]-vv\f[R] and \f[V]--log-level=DEBUG\f[R] flags, e.g.
+\f[V]rclone version -vv\f[R].
 .SH Configuring rclone on a remote / headless machine
 .PP
 Some of the configurations (those involving oauth2) require an Internet
@@ -20036,8 +20054,8 @@ alternative means of configuration.
 There are two ways of doing it, described below.
 .SS Configuring using rclone authorize
 .PP
-On the headless box run \f[C]rclone\f[R] config but answer \f[C]N\f[R]
-to the \f[C]Use auto config?\f[R] question.
+On the headless box run \f[V]rclone\f[R] config but answer \f[V]N\f[R]
+to the \f[V]Use auto config?\f[R] question.
 .IP
 .nf
 \f[C]
@@ -20109,7 +20127,7 @@ rclone config
 .PP
 to set up the config file.
 .PP
-Find the config file by running \f[C]rclone config file\f[R], for
+Find the config file by running \f[V]rclone config file\f[R], for
 example
 .IP
 .nf
@@ -20120,9 +20138,9 @@ Configuration file is stored at:
 \f[R]
 .fi
 .PP
-Now transfer it to the remote box (scp, cut paste, ftp, sftp, etc.) and
-place it in the correct place (use \f[C]rclone config file\f[R] on the
-remote box to find out where).
+Now transfer it to the remote box (scp, cut paste, ftp, sftp, etc.)
+and place it in the correct place (use \f[V]rclone config file\f[R] on
+the remote box to find out where).
 .SS Configuring using SSH Tunnel
 .PP
 Linux and MacOS users can utilize SSH Tunnel to redirect the headless
@@ -20134,8 +20152,8 @@ ssh -L localhost:53682:localhost:53682 username\[at]remote_server
 \f[R]
 .fi
 .PP
-Then on the headless box run \f[C]rclone config\f[R] and answer
-\f[C]Y\f[R] to the \f[C]Use auto config?\f[R] question.
+Then on the headless box run \f[V]rclone config\f[R] and answer
+\f[V]Y\f[R] to the \f[V]Use auto config?\f[R] question.
 .IP
 .nf
 \f[C]
@@ -20150,13 +20168,13 @@ y/n> y
 .fi
 .PP
 Then copy and paste the auth url
-\f[C]http://127.0.0.1:53682/auth?state=xxxxxxxxxxxx\f[R] to the browser
+\f[V]http://127.0.0.1:53682/auth?state=xxxxxxxxxxxx\f[R] to the browser
 on your local machine, complete the auth and it is done.
 .SH Filtering, includes and excludes
 .PP
-Filter flags determine which files rclone \f[C]sync\f[R],
-\f[C]move\f[R], \f[C]ls\f[R], \f[C]lsl\f[R], \f[C]md5sum\f[R],
-\f[C]sha1sum\f[R], \f[C]size\f[R], \f[C]delete\f[R], \f[C]check\f[R] and
+Filter flags determine which files rclone \f[V]sync\f[R],
+\f[V]move\f[R], \f[V]ls\f[R], \f[V]lsl\f[R], \f[V]md5sum\f[R],
+\f[V]sha1sum\f[R], \f[V]size\f[R], \f[V]delete\f[R], \f[V]check\f[R] and
 similar commands apply to.
 .PP
 They are specified in terms of path/file name patterns; path/file lists;
@@ -20164,26 +20182,26 @@ file age and size, or presence of a file in a directory.
 Bucket based remotes without the concept of directory apply filters to
 object key, age and size in an analogous way.
 .PP
-Rclone \f[C]purge\f[R] does not obey filters.
+Rclone \f[V]purge\f[R] does not obey filters.
 .PP
 To test filters without risk of damage to data, apply them to
-\f[C]rclone ls\f[R], or with the \f[C]--dry-run\f[R] and \f[C]-vv\f[R]
+\f[V]rclone ls\f[R], or with the \f[V]--dry-run\f[R] and \f[V]-vv\f[R]
 flags.
 .PP
 Rclone filter patterns can only be used in filter command line options,
 not in the specification of a remote.
 .PP
 E.g.
-\f[C]rclone copy \[dq]remote:dir*.jpg\[dq] /path/to/dir\f[R] does not
+\f[V]rclone copy \[dq]remote:dir*.jpg\[dq] /path/to/dir\f[R] does not
 have a filter effect.
-\f[C]rclone copy remote:dir /path/to/dir --include \[dq]*.jpg\[dq]\f[R]
+\f[V]rclone copy remote:dir /path/to/dir --include \[dq]*.jpg\[dq]\f[R]
 does.
 .PP
-\f[B]Important\f[R] Avoid mixing any two of \f[C]--include...\f[R],
-\f[C]--exclude...\f[R] or \f[C]--filter...\f[R] flags in an rclone
+\f[B]Important\f[R] Avoid mixing any two of \f[V]--include...\f[R],
+\f[V]--exclude...\f[R] or \f[V]--filter...\f[R] flags in an rclone
 command.
 The results might not be what you expect.
-Instead use a \f[C]--filter...\f[R] flag.
+Instead use a \f[V]--filter...\f[R] flag.
 .SS Patterns for matching path/file names
 .SS Pattern syntax
 .PP
@@ -20246,12 +20264,12 @@ Any re2 regular expression not containing \[ga]}}\[ga]
 \f[R]
 .fi
 .PP
-If the filter pattern starts with a \f[C]/\f[R] then it only matches at
+If the filter pattern starts with a \f[V]/\f[R] then it only matches at
 the top level of the directory tree, \f[B]relative to the root of the
 remote\f[R] (not necessarily the root of the drive).
-If it does not start with \f[C]/\f[R] then it is matched starting at the
+If it does not start with \f[V]/\f[R] then it is matched starting at the
 \f[B]end of the path/file name\f[R] but it only matches a complete path
-element - it must match from a \f[C]/\f[R] separator or the beginning of
+element - it must match from a \f[V]/\f[R] separator or the beginning of
 the path/file.
 .IP
 .nf
@@ -20274,30 +20292,30 @@ for a Microsoft Windows local directory structure
 .nf
 \f[C]
 F:
-\[u251C]\[u2500]\[u2500] bkp
-\[u251C]\[u2500]\[u2500] data
-\[br]   \[u251C]\[u2500]\[u2500] excl
-\[br]   \[br]   \[u251C]\[u2500]\[u2500] 123.jpg
-\[br]   \[br]   \[u2514]\[u2500]\[u2500] 456.jpg
-\[br]   \[u251C]\[u2500]\[u2500] incl
-\[br]   \[br]   \[u2514]\[u2500]\[u2500] document.pdf
+├── bkp
+├── data
+│   ├── excl
+│   │   ├── 123.jpg
+│   │   └── 456.jpg
+│   ├── incl
+│   │   └── document.pdf
 \f[R]
 .fi
 .PP
-To copy the contents of folder \f[C]data\f[R] into folder \f[C]bkp\f[R]
-excluding the contents of subfolder \f[C]excl\f[R]the following command
-treats \f[C]F:\[rs]data\f[R] and \f[C]F:\[rs]bkp\f[R] as top level for
+To copy the contents of folder \f[V]data\f[R] into folder \f[V]bkp\f[R]
+excluding the contents of subfolder \f[V]excl\f[R]the following command
+treats \f[V]F:\[rs]data\f[R] and \f[V]F:\[rs]bkp\f[R] as top level for
 filtering.
 .PP
-\f[C]rclone copy F:\[rs]data\[rs] F:\[rs]bkp\[rs] --exclude=/excl/**\f[R]
+\f[V]rclone copy F:\[rs]data\[rs] F:\[rs]bkp\[rs] --exclude=/excl/**\f[R]
 .PP
-\f[B]Important\f[R] Use \f[C]/\f[R] in path/file name patterns and not
-\f[C]\[rs]\f[R] even if running on Microsoft Windows.
+\f[B]Important\f[R] Use \f[V]/\f[R] in path/file name patterns and not
+\f[V]\[rs]\f[R] even if running on Microsoft Windows.
 .PP
-Simple patterns are case sensitive unless the \f[C]--ignore-case\f[R]
+Simple patterns are case sensitive unless the \f[V]--ignore-case\f[R]
 flag is used.
 .PP
-Without \f[C]--ignore-case\f[R] (default)
+Without \f[V]--ignore-case\f[R] (default)
 .IP
 .nf
 \f[C]
@@ -20306,7 +20324,7 @@ potato - matches \[dq]potato\[dq]
 \f[R]
 .fi
 .PP
-With \f[C]--ignore-case\f[R]
+With \f[V]--ignore-case\f[R]
 .IP
 .nf
 \f[C]
@@ -20317,21 +20335,21 @@ potato - matches \[dq]potato\[dq]
 .SS Using regular expressions in filter patterns
 .PP
 The syntax of filter patterns is glob style matching (like
-\f[C]bash\f[R] uses) to make things easy for users.
+\f[V]bash\f[R] uses) to make things easy for users.
 However this does not provide absolute control over the matching, so for
 advanced users rclone also provides a regular expression syntax.
 .PP
 The regular expressions used are as defined in the Go regular expression
 reference (https://golang.org/pkg/regexp/syntax/).
-Regular expressions should be enclosed in \f[C]{{\f[R] \f[C]}}\f[R].
+Regular expressions should be enclosed in \f[V]{{\f[R] \f[V]}}\f[R].
 They will match only the last path segment if the glob doesn\[aq]t start
-with \f[C]/\f[R] or the whole path name if it does.
+with \f[V]/\f[R] or the whole path name if it does.
 Note that rclone does not attempt to parse the supplied regular
 expression, meaning that using any regular expression filter will
 prevent rclone from using directory filter rules, as it will instead
 check every path against the supplied regular expression(s).
 .PP
-Here is how the \f[C]{{regexp}}\f[R] is transformed into an full regular
+Here is how the \f[V]{{regexp}}\f[R] is transformed into an full regular
 expression to match the entire path:
 .IP
 .nf
@@ -20359,8 +20377,8 @@ You can also use regexp flags - to set case insensitive, for example
 .PP
 Be careful with wildcards in regular expressions - you don\[aq]t want
 them to match path separators normally.
-To match any file name starting with \f[C]start\f[R] and ending with
-\f[C]end\f[R] write
+To match any file name starting with \f[V]start\f[R] and ending with
+\f[V]end\f[R] write
 .IP
 .nf
 \f[C]
@@ -20376,18 +20394,18 @@ Not
 \f[R]
 .fi
 .PP
-Which will match a directory called \f[C]start\f[R] with a file called
-\f[C]end.jpg\f[R] in it as the \f[C].*\f[R] will match \f[C]/\f[R]
+Which will match a directory called \f[V]start\f[R] with a file called
+\f[V]end.jpg\f[R] in it as the \f[V].*\f[R] will match \f[V]/\f[R]
 characters.
 .PP
-Note that you can use \f[C]-vv --dump filters\f[R] to show the filter
+Note that you can use \f[V]-vv --dump filters\f[R] to show the filter
 patterns in regexp format - rclone implements the glob patterns by
 transforming them into regular expressions.
 .SS Filter pattern examples
 .PP
 .TS
 tab(@);
-l l l l.
+lw(19.2n) lw(14.0n) lw(12.2n) lw(24.5n).
 T{
 Description
 T}@T{
@@ -20401,162 +20419,162 @@ _
 T{
 Wildcard
 T}@T{
-\f[C]*.jpg\f[R]
+\f[V]*.jpg\f[R]
 T}@T{
-\f[C]/file.jpg\f[R]
+\f[V]/file.jpg\f[R]
 T}@T{
-\f[C]/file.png\f[R]
+\f[V]/file.png\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/dir/file.jpg\f[R]
+\f[V]/dir/file.jpg\f[R]
 T}@T{
-\f[C]/dir/file.png\f[R]
+\f[V]/dir/file.png\f[R]
 T}
 T{
 Rooted
 T}@T{
-\f[C]/*.jpg\f[R]
+\f[V]/*.jpg\f[R]
 T}@T{
-\f[C]/file.jpg\f[R]
+\f[V]/file.jpg\f[R]
 T}@T{
-\f[C]/file.png\f[R]
+\f[V]/file.png\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/file2.jpg\f[R]
+\f[V]/file2.jpg\f[R]
 T}@T{
-\f[C]/dir/file.jpg\f[R]
+\f[V]/dir/file.jpg\f[R]
 T}
 T{
 Alternates
 T}@T{
-\f[C]*.{jpg,png}\f[R]
+\f[V]*.{jpg,png}\f[R]
 T}@T{
-\f[C]/file.jpg\f[R]
+\f[V]/file.jpg\f[R]
 T}@T{
-\f[C]/file.gif\f[R]
+\f[V]/file.gif\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/dir/file.png\f[R]
+\f[V]/dir/file.png\f[R]
 T}@T{
-\f[C]/dir/file.gif\f[R]
+\f[V]/dir/file.gif\f[R]
 T}
 T{
 Path Wildcard
 T}@T{
-\f[C]dir/**\f[R]
+\f[V]dir/**\f[R]
 T}@T{
-\f[C]/dir/anyfile\f[R]
+\f[V]/dir/anyfile\f[R]
 T}@T{
-\f[C]file.png\f[R]
+\f[V]file.png\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/subdir/dir/subsubdir/anyfile\f[R]
+\f[V]/subdir/dir/subsubdir/anyfile\f[R]
 T}@T{
-\f[C]/subdir/file.png\f[R]
+\f[V]/subdir/file.png\f[R]
 T}
 T{
 Any Char
 T}@T{
-\f[C]*.t?t\f[R]
+\f[V]*.t?t\f[R]
 T}@T{
-\f[C]/file.txt\f[R]
+\f[V]/file.txt\f[R]
 T}@T{
-\f[C]/file.qxt\f[R]
+\f[V]/file.qxt\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/dir/file.tzt\f[R]
+\f[V]/dir/file.tzt\f[R]
 T}@T{
-\f[C]/dir/file.png\f[R]
+\f[V]/dir/file.png\f[R]
 T}
 T{
 Range
 T}@T{
-\f[C]*.[a-z]\f[R]
+\f[V]*.[a-z]\f[R]
 T}@T{
-\f[C]/file.a\f[R]
+\f[V]/file.a\f[R]
 T}@T{
-\f[C]/file.0\f[R]
+\f[V]/file.0\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/dir/file.b\f[R]
+\f[V]/dir/file.b\f[R]
 T}@T{
-\f[C]/dir/file.1\f[R]
+\f[V]/dir/file.1\f[R]
 T}
 T{
 Escape
 T}@T{
-\f[C]*.\[rs]?\[rs]?\[rs]?\f[R]
+\f[V]*.\[rs]?\[rs]?\[rs]?\f[R]
 T}@T{
-\f[C]/file.???\f[R]
+\f[V]/file.???\f[R]
 T}@T{
-\f[C]/file.abc\f[R]
+\f[V]/file.abc\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/dir/file.???\f[R]
+\f[V]/dir/file.???\f[R]
 T}@T{
-\f[C]/dir/file.def\f[R]
+\f[V]/dir/file.def\f[R]
 T}
 T{
 Class
 T}@T{
-\f[C]*.\[rs]d\[rs]d\[rs]d\f[R]
+\f[V]*.\[rs]d\[rs]d\[rs]d\f[R]
 T}@T{
-\f[C]/file.012\f[R]
+\f[V]/file.012\f[R]
 T}@T{
-\f[C]/file.abc\f[R]
+\f[V]/file.abc\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/dir/file.345\f[R]
+\f[V]/dir/file.345\f[R]
 T}@T{
-\f[C]/dir/file.def\f[R]
+\f[V]/dir/file.def\f[R]
 T}
 T{
 Regexp
 T}@T{
-\f[C]*.{{jpe?g}}\f[R]
+\f[V]*.{{jpe?g}}\f[R]
 T}@T{
-\f[C]/file.jpeg\f[R]
+\f[V]/file.jpeg\f[R]
 T}@T{
-\f[C]/file.png\f[R]
+\f[V]/file.png\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/dir/file.jpg\f[R]
+\f[V]/dir/file.jpg\f[R]
 T}@T{
-\f[C]/dir/file.jpeeg\f[R]
+\f[V]/dir/file.jpeeg\f[R]
 T}
 T{
 Rooted Regexp
 T}@T{
-\f[C]/{{.*\[rs].jpe?g}}\f[R]
+\f[V]/{{.*\[rs].jpe?g}}\f[R]
 T}@T{
-\f[C]/file.jpeg\f[R]
+\f[V]/file.jpeg\f[R]
 T}@T{
-\f[C]/file.png\f[R]
+\f[V]/file.png\f[R]
 T}
 T{
 T}@T{
 T}@T{
-\f[C]/file.jpg\f[R]
+\f[V]/file.jpg\f[R]
 T}@T{
-\f[C]/dir/file.jpg\f[R]
+\f[V]/dir/file.jpg\f[R]
 T}
 .TE
 .SS How filter rules are applied to files
@@ -20564,17 +20582,17 @@ T}
 Rclone path/file name filters are made up of one or more of the
 following flags:
 .IP \[bu] 2
-\f[C]--include\f[R]
+\f[V]--include\f[R]
 .IP \[bu] 2
-\f[C]--include-from\f[R]
+\f[V]--include-from\f[R]
 .IP \[bu] 2
-\f[C]--exclude\f[R]
+\f[V]--exclude\f[R]
 .IP \[bu] 2
-\f[C]--exclude-from\f[R]
+\f[V]--exclude-from\f[R]
 .IP \[bu] 2
-\f[C]--filter\f[R]
+\f[V]--filter\f[R]
 .IP \[bu] 2
-\f[C]--filter-from\f[R]
+\f[V]--filter-from\f[R]
 .PP
 There can be more than one instance of individual flags.
 .PP
@@ -20591,16 +20609,16 @@ Multiple instances of the same flag are processed from left to right
 according to their position in the command line.
 .PP
 To mix up the order of processing includes and excludes use
-\f[C]--filter...\f[R] flags.
+\f[V]--filter...\f[R] flags.
 .PP
-Within \f[C]--include-from\f[R], \f[C]--exclude-from\f[R] and
-\f[C]--filter-from\f[R] flags rules are processed from top to bottom of
+Within \f[V]--include-from\f[R], \f[V]--exclude-from\f[R] and
+\f[V]--filter-from\f[R] flags rules are processed from top to bottom of
 the referenced file.
 .PP
-If there is an \f[C]--include\f[R] or \f[C]--include-from\f[R] flag
-specified, rclone implies a \f[C]- **\f[R] rule which it adds to the
+If there is an \f[V]--include\f[R] or \f[V]--include-from\f[R] flag
+specified, rclone implies a \f[V]- **\f[R] rule which it adds to the
 bottom of the internal rule list.
-Specifying a \f[C]+\f[R] rule with a \f[C]--filter...\f[R] flag does not
+Specifying a \f[V]+\f[R] rule with a \f[V]--filter...\f[R] flag does not
 imply that rule.
 .PP
 Each path/file name passed through rclone is matched against the
@@ -20614,13 +20632,13 @@ included.
 .PP
 Any path/file included at that stage is processed by the rclone command.
 .PP
-\f[C]--files-from\f[R] and \f[C]--files-from-raw\f[R] flags over-ride
+\f[V]--files-from\f[R] and \f[V]--files-from-raw\f[R] flags over-ride
 and cannot be combined with other filter options.
 .PP
 To see the internal combined rule list, in regular expression form, for
-a command add the \f[C]--dump filters\f[R] flag.
-Running an rclone command with \f[C]--dump filters\f[R] and
-\f[C]-vv\f[R] flags lists the internal filter elements and shows how
+a command add the \f[V]--dump filters\f[R] flag.
+Running an rclone command with \f[V]--dump filters\f[R] and
+\f[V]-vv\f[R] flags lists the internal filter elements and shows how
 they are applied to each source path/file.
 There is not currently a means provided to pass regular expression
 filter options into rclone directly though character class filter rules
@@ -20630,12 +20648,12 @@ Go regular expression reference (https://golang.org/pkg/regexp/syntax/)
 .PP
 Rclone commands are applied to path/file names not directories.
 The entire contents of a directory can be matched to a filter by the
-pattern \f[C]directory/*\f[R] or recursively by \f[C]directory/**\f[R].
+pattern \f[V]directory/*\f[R] or recursively by \f[V]directory/**\f[R].
 .PP
-Directory filter rules are defined with a closing \f[C]/\f[R] separator.
+Directory filter rules are defined with a closing \f[V]/\f[R] separator.
 .PP
 E.g.
-\f[C]/directory/subdirectory/\f[R] is an rclone directory filter rule.
+\f[V]/directory/subdirectory/\f[R] is an rclone directory filter rule.
 .PP
 Rclone commands can use directory filter rules to determine whether they
 recurse into subdirectories.
@@ -20650,25 +20668,25 @@ against the supplied regular expression(s).
 .PP
 Directory recursion optimisation occurs if either:
 .IP \[bu] 2
-A source remote does not support the rclone \f[C]ListR\f[R] primitive.
+A source remote does not support the rclone \f[V]ListR\f[R] primitive.
 local, sftp, Microsoft OneDrive and WebDAV do not support
-\f[C]ListR\f[R].
+\f[V]ListR\f[R].
 Google Drive and most bucket type storage do.
 Full list (https://rclone.org/overview/#optional-features)
 .IP \[bu] 2
-On other remotes (those that support \f[C]ListR\f[R]), if the rclone
+On other remotes (those that support \f[V]ListR\f[R]), if the rclone
 command is not naturally recursive, and provided it is not run with the
-\f[C]--fast-list\f[R] flag.
-\f[C]ls\f[R], \f[C]lsf -R\f[R] and \f[C]size\f[R] are naturally
-recursive but \f[C]sync\f[R], \f[C]copy\f[R] and \f[C]move\f[R] are not.
+\f[V]--fast-list\f[R] flag.
+\f[V]ls\f[R], \f[V]lsf -R\f[R] and \f[V]size\f[R] are naturally
+recursive but \f[V]sync\f[R], \f[V]copy\f[R] and \f[V]move\f[R] are not.
 .IP \[bu] 2
-Whenever the \f[C]--disable ListR\f[R] flag is applied to an rclone
+Whenever the \f[V]--disable ListR\f[R] flag is applied to an rclone
 command.
 .PP
 Rclone commands imply directory filter rules from path/file filter
 rules.
 To view the directory filter rules rclone has implied for a command
-specify the \f[C]--dump filters\f[R] flag.
+specify the \f[V]--dump filters\f[R] flag.
 .PP
 E.g.
 for an include rule
@@ -20692,16 +20710,16 @@ scope of an rclone command but path/file filters still have to be
 specified.
 .PP
 E.g.
-\f[C]rclone ls remote: --include /directory/\f[R] will not match any
+\f[V]rclone ls remote: --include /directory/\f[R] will not match any
 files.
-Because it is an \f[C]--include\f[R] option the \f[C]--exclude **\f[R]
-rule is implied, and the \f[C]/directory/\f[R] pattern serves only to
+Because it is an \f[V]--include\f[R] option the \f[V]--exclude **\f[R]
+rule is implied, and the \f[V]/directory/\f[R] pattern serves only to
 optimise access to the remote by ignoring everything outside of that
 directory.
 .PP
 E.g.
-\f[C]rclone ls remote: --filter-from filter-list.txt\f[R] with a file
-\f[C]filter-list.txt\f[R]:
+\f[V]rclone ls remote: --filter-from filter-list.txt\f[R] with a file
+\f[V]filter-list.txt\f[R]:
 .IP
 .nf
 \f[C]
@@ -20712,19 +20730,19 @@ E.g.
 \f[R]
 .fi
 .PP
-All files in directories \f[C]dir1\f[R] or \f[C]dir2\f[R] or their
+All files in directories \f[V]dir1\f[R] or \f[V]dir2\f[R] or their
 subdirectories are completely excluded from the listing.
-Only files of suffix \f[C]pdf\f[R] in the root of \f[C]remote:\f[R] or
+Only files of suffix \f[V]pdf\f[R] in the root of \f[V]remote:\f[R] or
 its subdirectories are listed.
-The \f[C]- **\f[R] rule prevents listing of any path/files not
+The \f[V]- **\f[R] rule prevents listing of any path/files not
 previously matched by the rules above.
 .PP
-Option \f[C]exclude-if-present\f[R] creates a directory exclude rule
+Option \f[V]exclude-if-present\f[R] creates a directory exclude rule
 based on the presence of a file in a directory and takes precedence over
 other rclone directory filter rules.
 .PP
 When using pattern list syntax, if a pattern item contains either
-\f[C]/\f[R] or \f[C]**\f[R], then rclone will not able to imply a
+\f[V]/\f[R] or \f[V]**\f[R], then rclone will not able to imply a
 directory filter rule from this pattern list.
 .PP
 E.g.
@@ -20736,23 +20754,23 @@ for an include rule
 \f[R]
 .fi
 .PP
-Rclone will match files below directories \f[C]dir1\f[R] or
-\f[C]dir2\f[R] only, but will not be able to use this filter to exclude
-a directory \f[C]dir3\f[R] from being traversed.
+Rclone will match files below directories \f[V]dir1\f[R] or
+\f[V]dir2\f[R] only, but will not be able to use this filter to exclude
+a directory \f[V]dir3\f[R] from being traversed.
 .PP
 Directory recursion optimisation may affect performance, but normally
 not the result.
 One exception to this is sync operations with option
-\f[C]--create-empty-src-dirs\f[R], where any traversed empty directories
+\f[V]--create-empty-src-dirs\f[R], where any traversed empty directories
 will be created.
-With the pattern list example \f[C]{dir1/**,dir2/**}\f[R] above, this
-would create an empty directory \f[C]dir3\f[R] on destination (when it
+With the pattern list example \f[V]{dir1/**,dir2/**}\f[R] above, this
+would create an empty directory \f[V]dir3\f[R] on destination (when it
 exists on source).
-Changing the filter to \f[C]{dir1,dir2}/**\f[R], or splitting it into
-two include rules \f[C]--include dir1/** --include dir2/**\f[R], will
+Changing the filter to \f[V]{dir1,dir2}/**\f[R], or splitting it into
+two include rules \f[V]--include dir1/** --include dir2/**\f[R], will
 match the same files while also filtering directories, with the result
-that an empty directory \f[C]dir3\f[R] will no longer be created.
-.SS \f[C]--exclude\f[R] - Exclude files matching pattern
+that an empty directory \f[V]dir3\f[R] will no longer be created.
+.SS \f[V]--exclude\f[R] - Exclude files matching pattern
 .PP
 Excludes path/file names from an rclone command based on a single
 exclude rule.
@@ -20760,41 +20778,41 @@ exclude rule.
 This flag can be repeated.
 See above for the order filter flags are processed in.
 .PP
-\f[C]--exclude\f[R] should not be used with \f[C]--include\f[R],
-\f[C]--include-from\f[R], \f[C]--filter\f[R] or \f[C]--filter-from\f[R]
+\f[V]--exclude\f[R] should not be used with \f[V]--include\f[R],
+\f[V]--include-from\f[R], \f[V]--filter\f[R] or \f[V]--filter-from\f[R]
 flags.
 .PP
-\f[C]--exclude\f[R] has no effect when combined with
-\f[C]--files-from\f[R] or \f[C]--files-from-raw\f[R] flags.
+\f[V]--exclude\f[R] has no effect when combined with
+\f[V]--files-from\f[R] or \f[V]--files-from-raw\f[R] flags.
 .PP
 E.g.
-\f[C]rclone ls remote: --exclude *.bak\f[R] excludes all .bak files from
+\f[V]rclone ls remote: --exclude *.bak\f[R] excludes all .bak files from
 listing.
 .PP
 E.g.
-\f[C]rclone size remote: --exclude \[dq]/dir/**\[dq]\f[R] returns the
-total size of all files on \f[C]remote:\f[R] excluding those in root
-directory \f[C]dir\f[R] and sub directories.
+\f[V]rclone size remote: --exclude \[dq]/dir/**\[dq]\f[R] returns the
+total size of all files on \f[V]remote:\f[R] excluding those in root
+directory \f[V]dir\f[R] and sub directories.
 .PP
 E.g.
 on Microsoft Windows
-\f[C]rclone ls remote: --exclude \[dq]*\[rs][{JP,KR,HK}\[rs]]*\[dq]\f[R]
-lists the files in \f[C]remote:\f[R] without \f[C][JP]\f[R] or
-\f[C][KR]\f[R] or \f[C][HK]\f[R] in their name.
-Quotes prevent the shell from interpreting the \f[C]\[rs]\f[R]
-characters.\f[C]\[rs]\f[R] characters escape the \f[C][\f[R] and
-\f[C]]\f[R] so an rclone filter treats them literally rather than as a
+\f[V]rclone ls remote: --exclude \[dq]*\[rs][{JP,KR,HK}\[rs]]*\[dq]\f[R]
+lists the files in \f[V]remote:\f[R] without \f[V][JP]\f[R] or
+\f[V][KR]\f[R] or \f[V][HK]\f[R] in their name.
+Quotes prevent the shell from interpreting the \f[V]\[rs]\f[R]
+characters.\f[V]\[rs]\f[R] characters escape the \f[V][\f[R] and
+\f[V]]\f[R] so an rclone filter treats them literally rather than as a
 character-range.
-The \f[C]{\f[R] and \f[C]}\f[R] define an rclone pattern list.
+The \f[V]{\f[R] and \f[V]}\f[R] define an rclone pattern list.
 For other operating systems single quotes are required ie
-\f[C]rclone ls remote: --exclude \[aq]*\[rs][{JP,KR,HK}\[rs]]*\[aq]\f[R]
-.SS \f[C]--exclude-from\f[R] - Read exclude patterns from file
+\f[V]rclone ls remote: --exclude \[aq]*\[rs][{JP,KR,HK}\[rs]]*\[aq]\f[R]
+.SS \f[V]--exclude-from\f[R] - Read exclude patterns from file
 .PP
 Excludes path/file names from an rclone command based on rules in a
 named file.
 The file contains a list of remarks and pattern rules.
 .PP
-For an example \f[C]exclude-file.txt\f[R]:
+For an example \f[V]exclude-file.txt\f[R]:
 .IP
 .nf
 \f[C]
@@ -20804,28 +20822,28 @@ file2.jpg
 \f[R]
 .fi
 .PP
-\f[C]rclone ls remote: --exclude-from exclude-file.txt\f[R] lists the
-files on \f[C]remote:\f[R] except those named \f[C]file2.jpg\f[R] or
-with a suffix \f[C].bak\f[R].
+\f[V]rclone ls remote: --exclude-from exclude-file.txt\f[R] lists the
+files on \f[V]remote:\f[R] except those named \f[V]file2.jpg\f[R] or
+with a suffix \f[V].bak\f[R].
 That is equivalent to
-\f[C]rclone ls remote: --exclude file2.jpg --exclude \[dq]*.bak\[dq]\f[R].
+\f[V]rclone ls remote: --exclude file2.jpg --exclude \[dq]*.bak\[dq]\f[R].
 .PP
 This flag can be repeated.
 See above for the order filter flags are processed in.
 .PP
-The \f[C]--exclude-from\f[R] flag is useful where multiple exclude
+The \f[V]--exclude-from\f[R] flag is useful where multiple exclude
 filter rules are applied to an rclone command.
 .PP
-\f[C]--exclude-from\f[R] should not be used with \f[C]--include\f[R],
-\f[C]--include-from\f[R], \f[C]--filter\f[R] or \f[C]--filter-from\f[R]
+\f[V]--exclude-from\f[R] should not be used with \f[V]--include\f[R],
+\f[V]--include-from\f[R], \f[V]--filter\f[R] or \f[V]--filter-from\f[R]
 flags.
 .PP
-\f[C]--exclude-from\f[R] has no effect when combined with
-\f[C]--files-from\f[R] or \f[C]--files-from-raw\f[R] flags.
+\f[V]--exclude-from\f[R] has no effect when combined with
+\f[V]--files-from\f[R] or \f[V]--files-from-raw\f[R] flags.
 .PP
-\f[C]--exclude-from\f[R] followed by \f[C]-\f[R] reads filter rules from
+\f[V]--exclude-from\f[R] followed by \f[V]-\f[R] reads filter rules from
 standard input.
-.SS \f[C]--include\f[R] - Include files matching pattern
+.SS \f[V]--include\f[R] - Include files matching pattern
 .PP
 Adds a single include rule based on path/file names to an rclone
 command.
@@ -20833,25 +20851,25 @@ command.
 This flag can be repeated.
 See above for the order filter flags are processed in.
 .PP
-\f[C]--include\f[R] has no effect when combined with
-\f[C]--files-from\f[R] or \f[C]--files-from-raw\f[R] flags.
+\f[V]--include\f[R] has no effect when combined with
+\f[V]--files-from\f[R] or \f[V]--files-from-raw\f[R] flags.
 .PP
-\f[C]--include\f[R] implies \f[C]--exclude **\f[R] at the end of an
+\f[V]--include\f[R] implies \f[V]--exclude **\f[R] at the end of an
 rclone internal filter list.
-Therefore if you mix \f[C]--include\f[R] and \f[C]--include-from\f[R]
-flags with \f[C]--exclude\f[R], \f[C]--exclude-from\f[R],
-\f[C]--filter\f[R] or \f[C]--filter-from\f[R], you must use include
+Therefore if you mix \f[V]--include\f[R] and \f[V]--include-from\f[R]
+flags with \f[V]--exclude\f[R], \f[V]--exclude-from\f[R],
+\f[V]--filter\f[R] or \f[V]--filter-from\f[R], you must use include
 rules for all the files you want in the include statement.
-For more flexibility use the \f[C]--filter-from\f[R] flag.
+For more flexibility use the \f[V]--filter-from\f[R] flag.
 .PP
 E.g.
-\f[C]rclone ls remote: --include \[dq]*.{png,jpg}\[dq]\f[R] lists the
-files on \f[C]remote:\f[R] with suffix \f[C].png\f[R] and
-\f[C].jpg\f[R].
+\f[V]rclone ls remote: --include \[dq]*.{png,jpg}\[dq]\f[R] lists the
+files on \f[V]remote:\f[R] with suffix \f[V].png\f[R] and
+\f[V].jpg\f[R].
 All other files are excluded.
 .PP
 E.g.
-multiple rclone copy commands can be combined with \f[C]--include\f[R]
+multiple rclone copy commands can be combined with \f[V]--include\f[R]
 and a pattern-list.
 .IP
 .nf
@@ -20870,18 +20888,18 @@ rclone copy /vol1 remote: --include \[dq]{A,B}/**\[dq]
 .fi
 .PP
 E.g.
-\f[C]rclone ls remote:/wheat --include \[dq]??[\[ha][:punct:]]*\[dq]\f[R]
-lists the files \f[C]remote:\f[R] directory \f[C]wheat\f[R] (and
+\f[V]rclone ls remote:/wheat --include \[dq]??[\[ha][:punct:]]*\[dq]\f[R]
+lists the files \f[V]remote:\f[R] directory \f[V]wheat\f[R] (and
 subdirectories) whose third character is not punctuation.
 This example uses an ASCII character
 class (https://golang.org/pkg/regexp/syntax/).
-.SS \f[C]--include-from\f[R] - Read include patterns from file
+.SS \f[V]--include-from\f[R] - Read include patterns from file
 .PP
 Adds path/file names to an rclone command based on rules in a named
 file.
 The file contains a list of remarks and pattern rules.
 .PP
-For an example \f[C]include-file.txt\f[R]:
+For an example \f[V]include-file.txt\f[R]:
 .IP
 .nf
 \f[C]
@@ -20891,62 +20909,62 @@ file2.avi
 \f[R]
 .fi
 .PP
-\f[C]rclone ls remote: --include-from include-file.txt\f[R] lists the
-files on \f[C]remote:\f[R] with name \f[C]file2.avi\f[R] or suffix
-\f[C].jpg\f[R].
+\f[V]rclone ls remote: --include-from include-file.txt\f[R] lists the
+files on \f[V]remote:\f[R] with name \f[V]file2.avi\f[R] or suffix
+\f[V].jpg\f[R].
 That is equivalent to
-\f[C]rclone ls remote: --include file2.avi --include \[dq]*.jpg\[dq]\f[R].
+\f[V]rclone ls remote: --include file2.avi --include \[dq]*.jpg\[dq]\f[R].
 .PP
 This flag can be repeated.
 See above for the order filter flags are processed in.
 .PP
-The \f[C]--include-from\f[R] flag is useful where multiple include
+The \f[V]--include-from\f[R] flag is useful where multiple include
 filter rules are applied to an rclone command.
 .PP
-\f[C]--include-from\f[R] implies \f[C]--exclude **\f[R] at the end of an
+\f[V]--include-from\f[R] implies \f[V]--exclude **\f[R] at the end of an
 rclone internal filter list.
-Therefore if you mix \f[C]--include\f[R] and \f[C]--include-from\f[R]
-flags with \f[C]--exclude\f[R], \f[C]--exclude-from\f[R],
-\f[C]--filter\f[R] or \f[C]--filter-from\f[R], you must use include
+Therefore if you mix \f[V]--include\f[R] and \f[V]--include-from\f[R]
+flags with \f[V]--exclude\f[R], \f[V]--exclude-from\f[R],
+\f[V]--filter\f[R] or \f[V]--filter-from\f[R], you must use include
 rules for all the files you want in the include statement.
-For more flexibility use the \f[C]--filter-from\f[R] flag.
+For more flexibility use the \f[V]--filter-from\f[R] flag.
 .PP
-\f[C]--exclude-from\f[R] has no effect when combined with
-\f[C]--files-from\f[R] or \f[C]--files-from-raw\f[R] flags.
+\f[V]--exclude-from\f[R] has no effect when combined with
+\f[V]--files-from\f[R] or \f[V]--files-from-raw\f[R] flags.
 .PP
-\f[C]--exclude-from\f[R] followed by \f[C]-\f[R] reads filter rules from
+\f[V]--exclude-from\f[R] followed by \f[V]-\f[R] reads filter rules from
 standard input.
-.SS \f[C]--filter\f[R] - Add a file-filtering rule
+.SS \f[V]--filter\f[R] - Add a file-filtering rule
 .PP
 Specifies path/file names to an rclone command, based on a single
-include or exclude rule, in \f[C]+\f[R] or \f[C]-\f[R] format.
+include or exclude rule, in \f[V]+\f[R] or \f[V]-\f[R] format.
 .PP
 This flag can be repeated.
 See above for the order filter flags are processed in.
 .PP
-\f[C]--filter +\f[R] differs from \f[C]--include\f[R].
-In the case of \f[C]--include\f[R] rclone implies an
-\f[C]--exclude *\f[R] rule which it adds to the bottom of the internal
+\f[V]--filter +\f[R] differs from \f[V]--include\f[R].
+In the case of \f[V]--include\f[R] rclone implies an
+\f[V]--exclude *\f[R] rule which it adds to the bottom of the internal
 rule list.
-\f[C]--filter...+\f[R] does not imply that rule.
+\f[V]--filter...+\f[R] does not imply that rule.
 .PP
-\f[C]--filter\f[R] has no effect when combined with
-\f[C]--files-from\f[R] or \f[C]--files-from-raw\f[R] flags.
+\f[V]--filter\f[R] has no effect when combined with
+\f[V]--files-from\f[R] or \f[V]--files-from-raw\f[R] flags.
 .PP
-\f[C]--filter\f[R] should not be used with \f[C]--include\f[R],
-\f[C]--include-from\f[R], \f[C]--exclude\f[R] or
-\f[C]--exclude-from\f[R] flags.
+\f[V]--filter\f[R] should not be used with \f[V]--include\f[R],
+\f[V]--include-from\f[R], \f[V]--exclude\f[R] or
+\f[V]--exclude-from\f[R] flags.
 .PP
 E.g.
-\f[C]rclone ls remote: --filter \[dq]- *.bak\[dq]\f[R] excludes all
-\f[C].bak\f[R] files from a list of \f[C]remote:\f[R].
-.SS \f[C]--filter-from\f[R] - Read filtering patterns from a file
+\f[V]rclone ls remote: --filter \[dq]- *.bak\[dq]\f[R] excludes all
+\f[V].bak\f[R] files from a list of \f[V]remote:\f[R].
+.SS \f[V]--filter-from\f[R] - Read filtering patterns from a file
 .PP
 Adds path/file names to an rclone command based on rules in a named
 file.
 The file contains a list of remarks and pattern rules.
-Include rules start with \f[C]+\f[R] and exclude rules with \f[C]-\f[R].
-\f[C]!\f[R] clears existing rules.
+Include rules start with \f[V]+\f[R] and exclude rules with \f[V]-\f[R].
+\f[V]!\f[R] clears existing rules.
 Rules are processed in the order they are defined.
 .PP
 This flag can be repeated.
@@ -20958,11 +20976,11 @@ work down.
 Lines starting with # or ; are ignored, and can be used to write
 comments.
 Inline comments are not supported.
-\f[I]Use \f[CI]-vv --dump filters\f[I] to see how they appear in the
+\f[I]Use \f[VI]-vv --dump filters\f[I] to see how they appear in the
 final regexp.\f[R]
 .PP
 E.g.
-for \f[C]filter-file.txt\f[R]:
+for \f[V]filter-file.txt\f[R]:
 .IP
 .nf
 \f[C]
@@ -20979,17 +20997,17 @@ for \f[C]filter-file.txt\f[R]:
 \f[R]
 .fi
 .PP
-\f[C]rclone ls remote: --filter-from filter-file.txt\f[R] lists the
-path/files on \f[C]remote:\f[R] including all \f[C]jpg\f[R] and
-\f[C]png\f[R] files, excluding any matching \f[C]secret*.jpg\f[R] and
-including \f[C]file2.avi\f[R].
-It also includes everything in the directory \f[C]dir\f[R] at the root
-of \f[C]remote\f[R], except \f[C]remote:dir/Trash\f[R] which it
+\f[V]rclone ls remote: --filter-from filter-file.txt\f[R] lists the
+path/files on \f[V]remote:\f[R] including all \f[V]jpg\f[R] and
+\f[V]png\f[R] files, excluding any matching \f[V]secret*.jpg\f[R] and
+including \f[V]file2.avi\f[R].
+It also includes everything in the directory \f[V]dir\f[R] at the root
+of \f[V]remote\f[R], except \f[V]remote:dir/Trash\f[R] which it
 excludes.
 Everything else is excluded.
 .PP
 E.g.
-for an alternative \f[C]filter-file.txt\f[R]:
+for an alternative \f[V]filter-file.txt\f[R]:
 .IP
 .nf
 \f[C]
@@ -21001,12 +21019,12 @@ for an alternative \f[C]filter-file.txt\f[R]:
 \f[R]
 .fi
 .PP
-Files \f[C]file1.jpg\f[R], \f[C]file3.png\f[R] and \f[C]file2.avi\f[R]
-are listed whilst \f[C]secret17.jpg\f[R] and files without the suffix
-\f[C].jpg\f[R] or \f[C].png\f[R] are excluded.
+Files \f[V]file1.jpg\f[R], \f[V]file3.png\f[R] and \f[V]file2.avi\f[R]
+are listed whilst \f[V]secret17.jpg\f[R] and files without the suffix
+\f[V].jpg\f[R] or \f[V].png\f[R] are excluded.
 .PP
 E.g.
-for an alternative \f[C]filter-file.txt\f[R]:
+for an alternative \f[V]filter-file.txt\f[R]:
 .IP
 .nf
 \f[C]
@@ -21019,47 +21037,47 @@ for an alternative \f[C]filter-file.txt\f[R]:
 .fi
 .PP
 Only file 42.doc is listed.
-Prior rules are cleared by the \f[C]!\f[R].
-.SS \f[C]--files-from\f[R] - Read list of source-file names
+Prior rules are cleared by the \f[V]!\f[R].
+.SS \f[V]--files-from\f[R] - Read list of source-file names
 .PP
 Adds path/files to an rclone command from a list in a named file.
 Rclone processes the path/file names in the order of the list, and no
 others.
 .PP
-Other filter flags (\f[C]--include\f[R], \f[C]--include-from\f[R],
-\f[C]--exclude\f[R], \f[C]--exclude-from\f[R], \f[C]--filter\f[R] and
-\f[C]--filter-from\f[R]) are ignored when \f[C]--files-from\f[R] is
+Other filter flags (\f[V]--include\f[R], \f[V]--include-from\f[R],
+\f[V]--exclude\f[R], \f[V]--exclude-from\f[R], \f[V]--filter\f[R] and
+\f[V]--filter-from\f[R]) are ignored when \f[V]--files-from\f[R] is
 used.
 .PP
-\f[C]--files-from\f[R] expects a list of files as its input.
+\f[V]--files-from\f[R] expects a list of files as its input.
 Leading or trailing whitespace is stripped from the input lines.
-Lines starting with \f[C]#\f[R] or \f[C];\f[R] are ignored.
+Lines starting with \f[V]#\f[R] or \f[V];\f[R] are ignored.
 .PP
-Rclone commands with a \f[C]--files-from\f[R] flag traverse the remote,
-treating the names in \f[C]--files-from\f[R] as a set of filters.
+Rclone commands with a \f[V]--files-from\f[R] flag traverse the remote,
+treating the names in \f[V]--files-from\f[R] as a set of filters.
 .PP
-If the \f[C]--no-traverse\f[R] and \f[C]--files-from\f[R] flags are used
+If the \f[V]--no-traverse\f[R] and \f[V]--files-from\f[R] flags are used
 together an rclone command does not traverse the remote.
 Instead it addresses each path/file named in the file individually.
 For each path/file name, that requires typically 1 API call.
-This can be efficient for a short \f[C]--files-from\f[R] list and a
+This can be efficient for a short \f[V]--files-from\f[R] list and a
 remote containing many files.
 .PP
-Rclone commands do not error if any names in the \f[C]--files-from\f[R]
+Rclone commands do not error if any names in the \f[V]--files-from\f[R]
 file are missing from the source remote.
 .PP
-The \f[C]--files-from\f[R] flag can be repeated in a single rclone
+The \f[V]--files-from\f[R] flag can be repeated in a single rclone
 command to read path/file names from more than one file.
 The files are read from left to right along the command line.
 .PP
-Paths within the \f[C]--files-from\f[R] file are interpreted as starting
+Paths within the \f[V]--files-from\f[R] file are interpreted as starting
 with the root specified in the rclone command.
-Leading \f[C]/\f[R] separators are ignored.
+Leading \f[V]/\f[R] separators are ignored.
 See --files-from-raw if you need the input to be processed in a raw
 manner.
 .PP
 E.g.
-for a file \f[C]files-from.txt\f[R]:
+for a file \f[V]files-from.txt\f[R]:
 .IP
 .nf
 \f[C]
@@ -21069,13 +21087,13 @@ subdir/file2.jpg
 \f[R]
 .fi
 .PP
-\f[C]rclone copy --files-from files-from.txt /home/me/pics remote:pics\f[R]
+\f[V]rclone copy --files-from files-from.txt /home/me/pics remote:pics\f[R]
 copies the following, if they exist, and only those files.
 .IP
 .nf
 \f[C]
-/home/me/pics/file1.jpg        \[->] remote:pics/file1.jpg
-/home/me/pics/subdir/file2.jpg \[->] remote:pics/subdir/file2.jpg
+/home/me/pics/file1.jpg        → remote:pics/file1.jpg
+/home/me/pics/subdir/file2.jpg → remote:pics/subdir/file2.jpg
 \f[R]
 .fi
 .PP
@@ -21090,9 +21108,9 @@ to copy the following files referenced by their absolute paths:
 \f[R]
 .fi
 .PP
-First find a common subdirectory - in this case \f[C]/home\f[R] and put
-the remaining files in \f[C]files-from.txt\f[R] with or without leading
-\f[C]/\f[R], e.g.
+First find a common subdirectory - in this case \f[V]/home\f[R] and put
+the remaining files in \f[V]files-from.txt\f[R] with or without leading
+\f[V]/\f[R], e.g.
 .IP
 .nf
 \f[C]
@@ -21114,13 +21132,13 @@ The three files are transferred as follows:
 .IP
 .nf
 \f[C]
-/home/user1/42       \[->] remote:backup/user1/important
-/home/user1/dir/ford \[->] remote:backup/user1/dir/file
-/home/user2/prefect  \[->] remote:backup/user2/stuff
+/home/user1/42       → remote:backup/user1/important
+/home/user1/dir/ford → remote:backup/user1/dir/file
+/home/user2/prefect  → remote:backup/user2/stuff
 \f[R]
 .fi
 .PP
-Alternatively if \f[C]/\f[R] is chosen as root \f[C]files-from.txt\f[R]
+Alternatively if \f[V]/\f[R] is chosen as root \f[V]files-from.txt\f[R]
 will be:
 .IP
 .nf
@@ -21139,120 +21157,120 @@ rclone copy --files-from files-from.txt / remote:backup
 \f[R]
 .fi
 .PP
-Then there will be an extra \f[C]home\f[R] directory on the remote:
+Then there will be an extra \f[V]home\f[R] directory on the remote:
 .IP
 .nf
 \f[C]
-/home/user1/42       \[->] remote:backup/home/user1/42
-/home/user1/dir/ford \[->] remote:backup/home/user1/dir/ford
-/home/user2/prefect  \[->] remote:backup/home/user2/prefect
+/home/user1/42       → remote:backup/home/user1/42
+/home/user1/dir/ford → remote:backup/home/user1/dir/ford
+/home/user2/prefect  → remote:backup/home/user2/prefect
 \f[R]
 .fi
-.SS \f[C]--files-from-raw\f[R] - Read list of source-file names without any processing
+.SS \f[V]--files-from-raw\f[R] - Read list of source-file names without any processing
 .PP
-This flag is the same as \f[C]--files-from\f[R] except that input is
+This flag is the same as \f[V]--files-from\f[R] except that input is
 read in a raw manner.
 Lines with leading / trailing whitespace, and lines starting with
-\f[C];\f[R] or \f[C]#\f[R] are read without any processing.
+\f[V];\f[R] or \f[V]#\f[R] are read without any processing.
 rclone lsf (https://rclone.org/commands/rclone_lsf/) has a compatible
 format that can be used to export file lists from remotes for input to
-\f[C]--files-from-raw\f[R].
-.SS \f[C]--ignore-case\f[R] - make searches case insensitive
+\f[V]--files-from-raw\f[R].
+.SS \f[V]--ignore-case\f[R] - make searches case insensitive
 .PP
 By default, rclone filter patterns are case sensitive.
-The \f[C]--ignore-case\f[R] flag makes all of the filters patterns on
+The \f[V]--ignore-case\f[R] flag makes all of the filters patterns on
 the command line case insensitive.
 .PP
 E.g.
-\f[C]--include \[dq]zaphod.txt\[dq]\f[R] does not match a file
-\f[C]Zaphod.txt\f[R].
-With \f[C]--ignore-case\f[R] a match is made.
+\f[V]--include \[dq]zaphod.txt\[dq]\f[R] does not match a file
+\f[V]Zaphod.txt\f[R].
+With \f[V]--ignore-case\f[R] a match is made.
 .SS Quoting shell metacharacters
 .PP
 Rclone commands with filter patterns containing shell metacharacters may
 not as work as expected in your shell and may require quoting.
 .PP
 E.g.
-linux, OSX (\f[C]*\f[R] metacharacter)
+linux, OSX (\f[V]*\f[R] metacharacter)
 .IP \[bu] 2
-\f[C]--include \[rs]*.jpg\f[R]
+\f[V]--include \[rs]*.jpg\f[R]
 .IP \[bu] 2
-\f[C]--include \[aq]*.jpg\[aq]\f[R]
+\f[V]--include \[aq]*.jpg\[aq]\f[R]
 .IP \[bu] 2
-\f[C]--include=\[aq]*.jpg\[aq]\f[R]
+\f[V]--include=\[aq]*.jpg\[aq]\f[R]
 .PP
 Microsoft Windows expansion is done by the command, not shell, so
-\f[C]--include *.jpg\f[R] does not require quoting.
+\f[V]--include *.jpg\f[R] does not require quoting.
 .PP
 If the rclone error
-\f[C]Command .... needs .... arguments maximum: you provided .... non flag arguments:\f[R]
+\f[V]Command .... needs .... arguments maximum: you provided .... non flag arguments:\f[R]
 is encountered, the cause is commonly spaces within the name of a remote
 or flag value.
 The fix then is to quote values containing spaces.
 .SS Other filters
-.SS \f[C]--min-size\f[R] - Don\[aq]t transfer any file smaller than this
+.SS \f[V]--min-size\f[R] - Don\[aq]t transfer any file smaller than this
 .PP
 Controls the minimum size file within the scope of an rclone command.
-Default units are \f[C]KiB\f[R] but abbreviations \f[C]B\f[R],
-\f[C]K\f[R], \f[C]M\f[R], \f[C]G\f[R], \f[C]T\f[R] or \f[C]P\f[R] are
+Default units are \f[V]KiB\f[R] but abbreviations \f[V]B\f[R],
+\f[V]K\f[R], \f[V]M\f[R], \f[V]G\f[R], \f[V]T\f[R] or \f[V]P\f[R] are
 valid.
 .PP
 E.g.
-\f[C]rclone ls remote: --min-size 50k\f[R] lists files on
-\f[C]remote:\f[R] of 50 KiB size or larger.
+\f[V]rclone ls remote: --min-size 50k\f[R] lists files on
+\f[V]remote:\f[R] of 50 KiB size or larger.
 .PP
 See the size option docs (https://rclone.org/docs/#size-option) for more
 info.
-.SS \f[C]--max-size\f[R] - Don\[aq]t transfer any file larger than this
+.SS \f[V]--max-size\f[R] - Don\[aq]t transfer any file larger than this
 .PP
 Controls the maximum size file within the scope of an rclone command.
-Default units are \f[C]KiB\f[R] but abbreviations \f[C]B\f[R],
-\f[C]K\f[R], \f[C]M\f[R], \f[C]G\f[R], \f[C]T\f[R] or \f[C]P\f[R] are
+Default units are \f[V]KiB\f[R] but abbreviations \f[V]B\f[R],
+\f[V]K\f[R], \f[V]M\f[R], \f[V]G\f[R], \f[V]T\f[R] or \f[V]P\f[R] are
 valid.
 .PP
 E.g.
-\f[C]rclone ls remote: --max-size 1G\f[R] lists files on
-\f[C]remote:\f[R] of 1 GiB size or smaller.
+\f[V]rclone ls remote: --max-size 1G\f[R] lists files on
+\f[V]remote:\f[R] of 1 GiB size or smaller.
 .PP
 See the size option docs (https://rclone.org/docs/#size-option) for more
 info.
-.SS \f[C]--max-age\f[R] - Don\[aq]t transfer any file older than this
+.SS \f[V]--max-age\f[R] - Don\[aq]t transfer any file older than this
 .PP
 Controls the maximum age of files within the scope of an rclone command.
 .PP
-\f[C]--max-age\f[R] applies only to files and not to directories.
+\f[V]--max-age\f[R] applies only to files and not to directories.
 .PP
 E.g.
-\f[C]rclone ls remote: --max-age 2d\f[R] lists files on
-\f[C]remote:\f[R] of 2 days old or less.
+\f[V]rclone ls remote: --max-age 2d\f[R] lists files on
+\f[V]remote:\f[R] of 2 days old or less.
 .PP
 See the time option docs (https://rclone.org/docs/#time-option) for
 valid formats.
-.SS \f[C]--min-age\f[R] - Don\[aq]t transfer any file younger than this
+.SS \f[V]--min-age\f[R] - Don\[aq]t transfer any file younger than this
 .PP
 Controls the minimum age of files within the scope of an rclone command.
-(see \f[C]--max-age\f[R] for valid formats)
+(see \f[V]--max-age\f[R] for valid formats)
 .PP
-\f[C]--min-age\f[R] applies only to files and not to directories.
+\f[V]--min-age\f[R] applies only to files and not to directories.
 .PP
 E.g.
-\f[C]rclone ls remote: --min-age 2d\f[R] lists files on
-\f[C]remote:\f[R] of 2 days old or more.
+\f[V]rclone ls remote: --min-age 2d\f[R] lists files on
+\f[V]remote:\f[R] of 2 days old or more.
 .PP
 See the time option docs (https://rclone.org/docs/#time-option) for
 valid formats.
 .SS Other flags
-.SS \f[C]--delete-excluded\f[R] - Delete files on dest excluded from sync
+.SS \f[V]--delete-excluded\f[R] - Delete files on dest excluded from sync
 .PP
 \f[B]Important\f[R] this flag is dangerous to your data - use with
-\f[C]--dry-run\f[R] and \f[C]-v\f[R] first.
+\f[V]--dry-run\f[R] and \f[V]-v\f[R] first.
 .PP
-In conjunction with \f[C]rclone sync\f[R], \f[C]--delete-excluded\f[R]
+In conjunction with \f[V]rclone sync\f[R], \f[V]--delete-excluded\f[R]
 deletes any files on the destination which are excluded from the
 command.
 .PP
 E.g.
-the scope of \f[C]rclone sync --interactive A: B:\f[R] can be
+the scope of \f[V]rclone sync --interactive A: B:\f[R] can be
 restricted:
 .IP
 .nf
@@ -21261,9 +21279,9 @@ rclone --min-size 50k --delete-excluded sync A: B:
 \f[R]
 .fi
 .PP
-All files on \f[C]B:\f[R] which are less than 50 KiB are deleted because
+All files on \f[V]B:\f[R] which are less than 50 KiB are deleted because
 they are excluded from the rclone sync command.
-.SS \f[C]--dump filters\f[R] - dump the filters to the output
+.SS \f[V]--dump filters\f[R] - dump the filters to the output
 .PP
 Dumps the defined filters to standard output in regular expression
 format.
@@ -21271,7 +21289,7 @@ format.
 Useful for debugging.
 .SS Exclude directory based on a file
 .PP
-The \f[C]--exclude-if-present\f[R] flag controls whether a directory is
+The \f[V]--exclude-if-present\f[R] flag controls whether a directory is
 within the scope of an rclone command based on the presence of a named
 file within it.
 The flag can be repeated to check for multiple file names, presence of
@@ -21291,20 +21309,20 @@ dir1/dir2/dir3/.ignore
 \f[R]
 .fi
 .PP
-The command \f[C]rclone ls --exclude-if-present .ignore dir1\f[R] does
-not list \f[C]dir3\f[R], \f[C]file3\f[R] or \f[C].ignore\f[R].
+The command \f[V]rclone ls --exclude-if-present .ignore dir1\f[R] does
+not list \f[V]dir3\f[R], \f[V]file3\f[R] or \f[V].ignore\f[R].
 .SS Metadata filters
 .PP
 The metadata filters work in a very similar way to the normal file name
 filters, except they match metadata (https://rclone.org/docs/#metadata)
 on the object.
 .PP
-The metadata should be specified as \f[C]key=value\f[R] patterns.
+The metadata should be specified as \f[V]key=value\f[R] patterns.
 This may be wildcarded using the normal filter patterns or regular
 expressions.
 .PP
 For example if you wished to list only local files with a mode of
-\f[C]100664\f[R] you could do that with:
+\f[V]100664\f[R] you could do that with:
 .IP
 .nf
 \f[C]
@@ -21312,8 +21330,8 @@ rclone lsf -M --files-only --metadata-include \[dq]mode=100664\[dq] .
 \f[R]
 .fi
 .PP
-Or if you wished to show files with an \f[C]atime\f[R], \f[C]mtime\f[R]
-or \f[C]btime\f[R] at a given date:
+Or if you wished to show files with an \f[V]atime\f[R], \f[V]mtime\f[R]
+or \f[V]btime\f[R] at a given date:
 .IP
 .nf
 \f[C]
@@ -21326,19 +21344,19 @@ directories.
 .PP
 The filters can be applied using these flags.
 .IP \[bu] 2
-\f[C]--metadata-include\f[R] - Include metadatas matching pattern
+\f[V]--metadata-include\f[R] - Include metadatas matching pattern
 .IP \[bu] 2
-\f[C]--metadata-include-from\f[R] - Read metadata include patterns from
+\f[V]--metadata-include-from\f[R] - Read metadata include patterns from
 file (use - to read from stdin)
 .IP \[bu] 2
-\f[C]--metadata-exclude\f[R] - Exclude metadatas matching pattern
+\f[V]--metadata-exclude\f[R] - Exclude metadatas matching pattern
 .IP \[bu] 2
-\f[C]--metadata-exclude-from\f[R] - Read metadata exclude patterns from
+\f[V]--metadata-exclude-from\f[R] - Read metadata exclude patterns from
 file (use - to read from stdin)
 .IP \[bu] 2
-\f[C]--metadata-filter\f[R] - Add a metadata filtering rule
+\f[V]--metadata-filter\f[R] - Add a metadata filtering rule
 .IP \[bu] 2
-\f[C]--metadata-filter-from\f[R] - Read metadata filtering patterns from
+\f[V]--metadata-filter-from\f[R] - Read metadata filtering patterns from
 a file (use - to read from stdin)
 .PP
 Each flag can be repeated.
@@ -21352,9 +21370,9 @@ forum (https://forum.rclone.org/) are:
 .IP \[bu] 2
 Not using paths relative to the root of the remote
 .IP \[bu] 2
-Not using \f[C]/\f[R] to match from the root of a remote
+Not using \f[V]/\f[R] to match from the root of a remote
 .IP \[bu] 2
-Not using \f[C]**\f[R] to match the contents of a directory
+Not using \f[V]**\f[R] to match the contents of a directory
 .SH GUI (Experimental)
 .PP
 Rclone can serve a web based GUI (graphical user interface).
@@ -21387,13 +21405,13 @@ It is possible to separate the rclone and the GUI - see below for
 details.
 .PP
 If you wish to check for updates then you can add
-\f[C]--rc-web-gui-update\f[R] to the command line.
+\f[V]--rc-web-gui-update\f[R] to the command line.
 .PP
 If you find your GUI broken, you may force it to update by add
-\f[C]--rc-web-gui-force-update\f[R].
+\f[V]--rc-web-gui-force-update\f[R].
 .PP
 By default, rclone will open your browser.
-Add \f[C]--rc-web-gui-no-open-browser\f[R] to disable this feature.
+Add \f[V]--rc-web-gui-no-open-browser\f[R] to disable this feature.
 .SS Using the GUI
 .PP
 Once the GUI opens, you will be looking at the dashboard which has an
@@ -21415,7 +21433,7 @@ Log out
 (More docs and walkthrough video to come!)
 .SS How it works
 .PP
-When you run the \f[C]rclone rcd --rc-web-gui\f[R] this is what happens
+When you run the \f[V]rclone rcd --rc-web-gui\f[R] this is what happens
 .IP \[bu] 2
 Rclone starts but only runs the remote control API (\[dq]rc\[dq]).
 .IP \[bu] 2
@@ -21427,24 +21445,24 @@ If the API bundle is missing then rclone will download it.
 rclone will start serving the files from the API bundle over the same
 port as the API
 .IP \[bu] 2
-rclone will open the browser with a \f[C]login_token\f[R] so it can log
+rclone will open the browser with a \f[V]login_token\f[R] so it can log
 straight in.
 .SS Advanced use
 .PP
-The \f[C]rclone rcd\f[R] may use any of the flags documented on the rc
+The \f[V]rclone rcd\f[R] may use any of the flags documented on the rc
 page (https://rclone.org/rc/#supported-parameters).
 .PP
-The flag \f[C]--rc-web-gui\f[R] is shorthand for
+The flag \f[V]--rc-web-gui\f[R] is shorthand for
 .IP \[bu] 2
 Download the web GUI if necessary
 .IP \[bu] 2
 Check we are using some authentication
 .IP \[bu] 2
-\f[C]--rc-user gui\f[R]
+\f[V]--rc-user gui\f[R]
 .IP \[bu] 2
-\f[C]--rc-pass <random password>\f[R]
+\f[V]--rc-pass <random password>\f[R]
 .IP \[bu] 2
-\f[C]--rc-serve\f[R]
+\f[V]--rc-serve\f[R]
 .PP
 These flags can be overridden as desired.
 .PP
@@ -21455,31 +21473,31 @@ documentation (https://rclone.org/commands/rclone_rcd/).
 For example the GUI could be served on a public port over SSL using an
 htpasswd file using the following flags:
 .IP \[bu] 2
-\f[C]--rc-web-gui\f[R]
+\f[V]--rc-web-gui\f[R]
 .IP \[bu] 2
-\f[C]--rc-addr :443\f[R]
+\f[V]--rc-addr :443\f[R]
 .IP \[bu] 2
-\f[C]--rc-htpasswd /path/to/htpasswd\f[R]
+\f[V]--rc-htpasswd /path/to/htpasswd\f[R]
 .IP \[bu] 2
-\f[C]--rc-cert /path/to/ssl.crt\f[R]
+\f[V]--rc-cert /path/to/ssl.crt\f[R]
 .IP \[bu] 2
-\f[C]--rc-key /path/to/ssl.key\f[R]
+\f[V]--rc-key /path/to/ssl.key\f[R]
 .SS Example: Running a GUI behind a proxy
 .PP
-If you want to run the GUI behind a proxy at \f[C]/rclone\f[R] you could
+If you want to run the GUI behind a proxy at \f[V]/rclone\f[R] you could
 use these flags:
 .IP \[bu] 2
-\f[C]--rc-web-gui\f[R]
+\f[V]--rc-web-gui\f[R]
 .IP \[bu] 2
-\f[C]--rc-baseurl rclone\f[R]
+\f[V]--rc-baseurl rclone\f[R]
 .IP \[bu] 2
-\f[C]--rc-htpasswd /path/to/htpasswd\f[R]
+\f[V]--rc-htpasswd /path/to/htpasswd\f[R]
 .PP
 Or instead of htpasswd if you just want a single user and password:
 .IP \[bu] 2
-\f[C]--rc-user me\f[R]
+\f[V]--rc-user me\f[R]
 .IP \[bu] 2
-\f[C]--rc-pass mypassword\f[R]
+\f[V]--rc-pass mypassword\f[R]
 .SS Project
 .PP
 The GUI is being developed in the: rclone/rclone-webui-react
@@ -21491,7 +21509,7 @@ If you have questions then please ask them on the rclone
 forum (https://forum.rclone.org/).
 .SH Remote controlling rclone with its API
 .PP
-If rclone is run with the \f[C]--rc\f[R] flag then it starts an HTTP
+If rclone is run with the \f[V]--rc\f[R] flag then it starts an HTTP
 server which can be used to remote control rclone using its API.
 .PP
 You can either use the rc command to access the API or use HTTP
@@ -21566,17 +21584,17 @@ If this is set then rclone will serve the files in that directory.
 It will also open the root in the web browser if specified.
 This is for implementing browser based GUIs for rclone functions.
 .PP
-If \f[C]--rc-user\f[R] or \f[C]--rc-pass\f[R] is set then the URL that
+If \f[V]--rc-user\f[R] or \f[V]--rc-pass\f[R] is set then the URL that
 is opened will have the authorization in the URL in the
-\f[C]http://user:pass\[at]localhost/\f[R] style.
+\f[V]http://user:pass\[at]localhost/\f[R] style.
 .PP
 Default Off.
 .SS --rc-enable-metrics
 .PP
-Enable OpenMetrics/Prometheus compatible endpoint at \f[C]/metrics\f[R].
+Enable OpenMetrics/Prometheus compatible endpoint at \f[V]/metrics\f[R].
 If more control over the metrics is desired (for example running it on a
 different port or with different auth) then endpoint can be enabled with
-the \f[C]--metrics-*\f[R] flags instead.
+the \f[V]--metrics-*\f[R] flags instead.
 .PP
 Default Off.
 .SS --rc-web-gui
@@ -21627,12 +21645,12 @@ Interval duration to check for expired async jobs (default 10s).
 By default rclone will require authorisation to have been set up on the
 rc interface in order to use any methods which access any rclone
 remotes.
-Eg \f[C]operations/list\f[R] is denied as it involved creating a remote
-as is \f[C]sync/copy\f[R].
+Eg \f[V]operations/list\f[R] is denied as it involved creating a remote
+as is \f[V]sync/copy\f[R].
 .PP
 If this is set then no authorisation will be required on the server to
 use these methods.
-The alternative is to use \f[C]--rc-user\f[R] and \f[C]--rc-pass\f[R]
+The alternative is to use \f[V]--rc-user\f[R] and \f[V]--rc-pass\f[R]
 and use these credentials in the request.
 .PP
 Default Off.
@@ -21647,7 +21665,7 @@ User-specified template.
 .SS Accessing the remote control via the rclone rc command
 .PP
 Rclone itself implements the remote control protocol in its
-\f[C]rclone rc\f[R] command.
+\f[V]rclone rc\f[R] command.
 .PP
 You can use it like this
 .IP
@@ -21661,11 +21679,11 @@ $ rclone rc rc/noop param1=one param2=two
 \f[R]
 .fi
 .PP
-Run \f[C]rclone rc\f[R] on its own to see the help for the installed
+Run \f[V]rclone rc\f[R] on its own to see the help for the installed
 remote control commands.
 .SS JSON input
 .PP
-\f[C]rclone rc\f[R] also supports a \f[C]--json\f[R] flag which can be
+\f[V]rclone rc\f[R] also supports a \f[V]--json\f[R] flag which can be
 used to send more complicated input parameters.
 .IP
 .nf
@@ -21687,7 +21705,7 @@ $ rclone rc --json \[aq]{ \[dq]p1\[dq]: [1,\[dq]2\[dq],null,4], \[dq]p2\[dq]: {
 .fi
 .PP
 If the parameter being passed is an object then it can be passed as a
-JSON string rather than using the \f[C]--json\f[R] flag which simplifies
+JSON string rather than using the \f[V]--json\f[R] flag which simplifies
 the command line.
 .IP
 .nf
@@ -21707,27 +21725,27 @@ rclone rc operations/list --json \[aq]{\[dq]fs\[dq]: \[dq]/tmp\[dq], \[dq]remote
 .PP
 The rc interface supports some special parameters which apply to
 \f[B]all\f[R] commands.
-These start with \f[C]_\f[R] to show they are different.
+These start with \f[V]_\f[R] to show they are different.
 .SS Running asynchronous jobs with _async = true
 .PP
 Each rc call is classified as a job and it is assigned its own id.
 By default jobs are executed immediately as they are created or
 synchronously.
 .PP
-If \f[C]_async\f[R] has a true value when supplied to an rc call then it
+If \f[V]_async\f[R] has a true value when supplied to an rc call then it
 will return immediately with a job id and the task will be run in the
 background.
-The \f[C]job/status\f[R] call can be used to get information of the
+The \f[V]job/status\f[R] call can be used to get information of the
 background job.
 The job can be queried for up to 1 minute after it has finished.
 .PP
 It is recommended that potentially long running jobs, e.g.
-\f[C]sync/sync\f[R], \f[C]sync/copy\f[R], \f[C]sync/move\f[R],
-\f[C]operations/purge\f[R] are run with the \f[C]_async\f[R] flag to
+\f[V]sync/sync\f[R], \f[V]sync/copy\f[R], \f[V]sync/move\f[R],
+\f[V]operations/purge\f[R] are run with the \f[V]_async\f[R] flag to
 avoid any potential problems with the HTTP request and response timing
 out.
 .PP
-Starting a job with the \f[C]_async\f[R] flag:
+Starting a job with the \f[V]_async\f[R] flag:
 .IP
 .nf
 \f[C]
@@ -21740,7 +21758,7 @@ $ rclone rc --json \[aq]{ \[dq]p1\[dq]: [1,\[dq]2\[dq],null,4], \[dq]p2\[dq]: {
 .PP
 Query the status to see if the job has finished.
 For more information on the meaning of these return parameters see the
-\f[C]job/status\f[R] call.
+\f[V]job/status\f[R] call.
 .IP
 .nf
 \f[C]
@@ -21770,7 +21788,7 @@ $ rclone rc --json \[aq]{ \[dq]jobid\[dq]:2 }\[aq] job/status
 \f[R]
 .fi
 .PP
-\f[C]job/list\f[R] can be used to show the running or recently completed
+\f[V]job/list\f[R] can be used to show the running or recently completed
 jobs
 .IP
 .nf
@@ -21786,13 +21804,13 @@ $ rclone rc job/list
 .SS Setting config flags with _config
 .PP
 If you wish to set config (the equivalent of the global flags) for the
-duration of an rc call only then pass in the \f[C]_config\f[R]
+duration of an rc call only then pass in the \f[V]_config\f[R]
 parameter.
 .PP
-This should be in the same format as the \f[C]config\f[R] key returned
+This should be in the same format as the \f[V]config\f[R] key returned
 by options/get.
 .PP
-For example, if you wished to run a sync with the \f[C]--checksum\f[R]
+For example, if you wished to run a sync with the \f[V]--checksum\f[R]
 parameter, you would pass this parameter in your JSON blob.
 .IP
 .nf
@@ -21801,7 +21819,7 @@ parameter, you would pass this parameter in your JSON blob.
 \f[R]
 .fi
 .PP
-If using \f[C]rclone rc\f[R] this could be passed as
+If using \f[V]rclone rc\f[R] this could be passed as
 .IP
 .nf
 \f[C]
@@ -21814,7 +21832,7 @@ which were set with command line flags or environment variables.
 .PP
 Note that it is possible to set some values as strings or integers - see
 data types for more info.
-Here is an example setting the equivalent of \f[C]--buffer-size\f[R] in
+Here is an example setting the equivalent of \f[V]--buffer-size\f[R] in
 string or integer format.
 .IP
 .nf
@@ -21824,15 +21842,15 @@ string or integer format.
 \f[R]
 .fi
 .PP
-If you wish to check the \f[C]_config\f[R] assignment has worked
-properly then calling \f[C]options/local\f[R] will show what the value
+If you wish to check the \f[V]_config\f[R] assignment has worked
+properly then calling \f[V]options/local\f[R] will show what the value
 got set to.
 .SS Setting filter flags with _filter
 .PP
 If you wish to set filters for the duration of an rc call only then pass
-in the \f[C]_filter\f[R] parameter.
+in the \f[V]_filter\f[R] parameter.
 .PP
-This should be in the same format as the \f[C]filter\f[R] key returned
+This should be in the same format as the \f[V]filter\f[R] key returned
 by options/get.
 .PP
 For example, if you wished to run a sync with these flags
@@ -21851,7 +21869,7 @@ you would pass this parameter in your JSON blob.
 \f[R]
 .fi
 .PP
-If using \f[C]rclone rc\f[R] this could be passed as
+If using \f[V]rclone rc\f[R] this could be passed as
 .IP
 .nf
 \f[C]
@@ -21864,7 +21882,7 @@ which were set with command line flags or environment variables.
 .PP
 Note that it is possible to set some values as strings or integers - see
 data types for more info.
-Here is an example setting the equivalent of \f[C]--buffer-size\f[R] in
+Here is an example setting the equivalent of \f[V]--buffer-size\f[R] in
 string or integer format.
 .IP
 .nf
@@ -21874,21 +21892,21 @@ string or integer format.
 \f[R]
 .fi
 .PP
-If you wish to check the \f[C]_filter\f[R] assignment has worked
-properly then calling \f[C]options/local\f[R] will show what the value
+If you wish to check the \f[V]_filter\f[R] assignment has worked
+properly then calling \f[V]options/local\f[R] will show what the value
 got set to.
 .SS Assigning operations to groups with _group = value
 .PP
 Each rc call has its own stats group for tracking its metrics.
 By default grouping is done by the composite group name from prefix
-\f[C]job/\f[R] and id of the job like so \f[C]job/1\f[R].
+\f[V]job/\f[R] and id of the job like so \f[V]job/1\f[R].
 .PP
-If \f[C]_group\f[R] has a value then stats for that request will be
+If \f[V]_group\f[R] has a value then stats for that request will be
 grouped under that value.
 This allows caller to group stats under their own name.
 .PP
-Stats for specific group can be accessed by passing \f[C]group\f[R] to
-\f[C]core/stats\f[R]:
+Stats for specific group can be accessed by passing \f[V]group\f[R] to
+\f[V]core/stats\f[R]:
 .IP
 .nf
 \f[C]
@@ -21905,29 +21923,29 @@ When the API returns types, these will mostly be straight forward
 integer, string or boolean types.
 .PP
 However some of the types returned by the options/get call and taken by
-the options/set calls as well as the \f[C]vfsOpt\f[R],
-\f[C]mountOpt\f[R] and the \f[C]_config\f[R] parameters.
+the options/set calls as well as the \f[V]vfsOpt\f[R],
+\f[V]mountOpt\f[R] and the \f[V]_config\f[R] parameters.
 .IP \[bu] 2
-\f[C]Duration\f[R] - these are returned as an integer duration in
+\f[V]Duration\f[R] - these are returned as an integer duration in
 nanoseconds.
 They may be set as an integer, or they may be set with time string, eg
 \[dq]5s\[dq].
 See the options section (https://rclone.org/docs/#options) for more
 info.
 .IP \[bu] 2
-\f[C]Size\f[R] - these are returned as an integer number of bytes.
+\f[V]Size\f[R] - these are returned as an integer number of bytes.
 They may be set as an integer or they may be set with a size suffix
 string, eg \[dq]10M\[dq].
 See the options section (https://rclone.org/docs/#options) for more
 info.
 .IP \[bu] 2
-Enumerated type (such as \f[C]CutoffMode\f[R], \f[C]DumpFlags\f[R],
-\f[C]LogLevel\f[R], \f[C]VfsCacheMode\f[R] - these will be returned as
+Enumerated type (such as \f[V]CutoffMode\f[R], \f[V]DumpFlags\f[R],
+\f[V]LogLevel\f[R], \f[V]VfsCacheMode\f[R] - these will be returned as
 an integer and may be set as an integer but more conveniently they can
-be set as a string, eg \[dq]HARD\[dq] for \f[C]CutoffMode\f[R] or
-\f[C]DEBUG\f[R] for \f[C]LogLevel\f[R].
+be set as a string, eg \[dq]HARD\[dq] for \f[V]CutoffMode\f[R] or
+\f[V]DEBUG\f[R] for \f[V]LogLevel\f[R].
 .IP \[bu] 2
-\f[C]BandwidthSpec\f[R] - this will be set and returned as a string, eg
+\f[V]BandwidthSpec\f[R] - this will be set and returned as a string, eg
 \[dq]1M\[dq].
 .SS Option blocks
 .PP
@@ -21937,7 +21955,7 @@ configuration options.
 This can be used to build user interfaces for displaying and setting any
 rclone option.
 .PP
-These consist of arrays of \f[C]Option\f[R] blocks.
+These consist of arrays of \f[V]Option\f[R] blocks.
 These have the following format.
 Each block describes a single option.
 .PP
@@ -22103,13 +22121,13 @@ T}@T{
 N
 T}@T{
 set if this option should be redacted when using
-\f[C]rclone config redacted\f[R]
+\f[V]rclone config redacted\f[R]
 T}
 .TE
 .PP
-An example of this might be the \f[C]--log-level\f[R] flag.
-Note that the \f[C]Name\f[R] of the option becomes the command line flag
-with \f[C]_\f[R] replaced with \f[C]-\f[R].
+An example of this might be the \f[V]--log-level\f[R] flag.
+Note that the \f[V]Name\f[R] of the option becomes the command line flag
+with \f[V]_\f[R] replaced with \f[V]-\f[R].
 .IP
 .nf
 \f[C]
@@ -22145,17 +22163,17 @@ with \f[C]_\f[R] replaced with \f[C]-\f[R].
 \f[R]
 .fi
 .PP
-Note that the \f[C]Help\f[R] may be multiple lines separated by
-\f[C]\[rs]n\f[R].
+Note that the \f[V]Help\f[R] may be multiple lines separated by
+\f[V]\[rs]n\f[R].
 The first line will always be a short sentence and this is the sentence
-shown when running \f[C]rclone help flags\f[R].
+shown when running \f[V]rclone help flags\f[R].
 .SS Specifying remotes to work on
 .PP
-Remotes are specified with the \f[C]fs=\f[R], \f[C]srcFs=\f[R],
-\f[C]dstFs=\f[R] parameters depending on the command being used.
+Remotes are specified with the \f[V]fs=\f[R], \f[V]srcFs=\f[R],
+\f[V]dstFs=\f[R] parameters depending on the command being used.
 .PP
 The parameters can be a string as per the rest of rclone, eg
-\f[C]s3:bucket/path\f[R] or \f[C]:sftp:/my/dir\f[R].
+\f[V]s3:bucket/path\f[R] or \f[V]:sftp:/my/dir\f[R].
 They can also be specified as JSON blobs.
 .PP
 If specifying a JSON blob it should be a object mapping strings to
@@ -22163,21 +22181,21 @@ strings.
 These values will be used to configure the remote.
 There are 3 special values which may be set:
 .IP \[bu] 2
-\f[C]type\f[R] - set to \f[C]type\f[R] to specify a remote called
-\f[C]:type:\f[R]
+\f[V]type\f[R] - set to \f[V]type\f[R] to specify a remote called
+\f[V]:type:\f[R]
 .IP \[bu] 2
-\f[C]_name\f[R] - set to \f[C]name\f[R] to specify a remote called
-\f[C]name:\f[R]
+\f[V]_name\f[R] - set to \f[V]name\f[R] to specify a remote called
+\f[V]name:\f[R]
 .IP \[bu] 2
-\f[C]_root\f[R] - sets the root of the remote - may be empty
+\f[V]_root\f[R] - sets the root of the remote - may be empty
 .PP
-One of \f[C]_name\f[R] or \f[C]type\f[R] should normally be set.
-If the \f[C]local\f[R] backend is desired then \f[C]type\f[R] should be
-set to \f[C]local\f[R].
-If \f[C]_root\f[R] isn\[aq]t specified then it defaults to the root of
+One of \f[V]_name\f[R] or \f[V]type\f[R] should normally be set.
+If the \f[V]local\f[R] backend is desired then \f[V]type\f[R] should be
+set to \f[V]local\f[R].
+If \f[V]_root\f[R] isn\[aq]t specified then it defaults to the root of
 the remote.
 .PP
-For example this JSON is equivalent to \f[C]remote:/tmp\f[R]
+For example this JSON is equivalent to \f[V]remote:/tmp\f[R]
 .IP
 .nf
 \f[C]
@@ -22189,7 +22207,7 @@ For example this JSON is equivalent to \f[C]remote:/tmp\f[R]
 .fi
 .PP
 And this is equivalent to
-\f[C]:sftp,host=\[aq]example.com\[aq]:/tmp\f[R]
+\f[V]:sftp,host=\[aq]example.com\[aq]:/tmp\f[R]
 .IP
 .nf
 \f[C]
@@ -22201,7 +22219,7 @@ And this is equivalent to
 \f[R]
 .fi
 .PP
-And this is equivalent to \f[C]/tmp/dir\f[R]
+And this is equivalent to \f[V]/tmp/dir\f[R]
 .IP
 .nf
 \f[C]
@@ -23852,7 +23870,7 @@ This allows you to remove a plugin using it\[aq]s name.
 This takes parameters:
 .IP \[bu] 2
 name - name of the plugin in the format
-\f[C]author\f[R]/\f[C]plugin_name\f[R].
+\f[V]author\f[R]/\f[V]plugin_name\f[R].
 .PP
 E.g.
 .PP
@@ -23866,7 +23884,7 @@ This allows you to remove a plugin using it\[aq]s name.
 This takes the following parameters:
 .IP \[bu] 2
 name - name of the plugin in the format
-\f[C]author\f[R]/\f[C]plugin_name\f[R].
+\f[V]author\f[R]/\f[V]plugin_name\f[R].
 .PP
 Example:
 .IP
@@ -23904,10 +23922,10 @@ parameter passing is working properly.
 This takes the following parameters
 .IP \[bu] 2
 path1 - a remote directory string e.g.
-\f[C]drive:path1\f[R]
+\f[V]drive:path1\f[R]
 .IP \[bu] 2
 path2 - a remote directory string e.g.
-\f[C]drive:path2\f[R]
+\f[V]drive:path2\f[R]
 .IP \[bu] 2
 dryRun - dry-run mode
 .IP \[bu] 2
@@ -23923,8 +23941,8 @@ threshold (default: 50)
 .IP \[bu] 2
 force - Bypass maxDelete safety check and run the sync
 .IP \[bu] 2
-checkSync - \f[C]true\f[R] by default, \f[C]false\f[R] disables
-comparison of final listings, \f[C]only\f[R] will skip sync, only
+checkSync - \f[V]true\f[R] by default, \f[V]false\f[R] disables
+comparison of final listings, \f[V]only\f[R] will skip sync, only
 compare listings from the last run
 .IP \[bu] 2
 createEmptySrcDirs - Sync creation and deletion of empty directories.
@@ -23941,7 +23959,7 @@ errors, instead of requiring resync.
 Use at your own risk!
 .IP \[bu] 2
 workdir - server directory for history files (default:
-\f[C]\[ti]/.cache/rclone/bisync\f[R])
+\f[V]\[ti]/.cache/rclone/bisync\f[R])
 .IP \[bu] 2
 backupdir1 - --backup-dir for Path1.
 Must be a non-overlapping path on the same remote.
@@ -24076,8 +24094,8 @@ must be supplied.
 .PP
 This returns info about the upload queue for the selected VFS.
 .PP
-This is only useful if \f[C]--vfs-cache-mode\f[R] > off.
-If you call it when the \f[C]--vfs-cache-mode\f[R] is off, it will
+This is only useful if \f[V]--vfs-cache-mode\f[R] > off.
+If you call it when the \f[V]--vfs-cache-mode\f[R] is off, it will
 return an empty result.
 .IP
 .nf
@@ -24099,14 +24117,14 @@ return an empty result.
 \f[R]
 .fi
 .PP
-The \f[C]expiry\f[R] time is the time until the file is elegible for
+The \f[V]expiry\f[R] time is the time until the file is elegible for
 being uploaded in floating point seconds.
 This may go negative.
-As rclone only transfers \f[C]--transfers\f[R] files at once, only the
-lowest \f[C]--transfers\f[R] expiry times will have \f[C]uploading\f[R]
-as \f[C]true\f[R].
+As rclone only transfers \f[V]--transfers\f[R] files at once, only the
+lowest \f[V]--transfers\f[R] expiry times will have \f[V]uploading\f[R]
+as \f[V]true\f[R].
 So there may be files with negative expiry times for which
-\f[C]uploading\f[R] is \f[C]false\f[R].
+\f[V]uploading\f[R] is \f[V]false\f[R].
 .PP
 This command takes an \[dq]fs\[dq] parameter.
 If this parameter is not supplied and if there is only one VFS in use
@@ -24115,31 +24133,31 @@ If there is more than one VFS in use then the \[dq]fs\[dq] parameter
 must be supplied.
 .SS vfs/queue-set-expiry: Set the expiry time for an item queued for upload.
 .PP
-Use this to adjust the \f[C]expiry\f[R] time for an item in the upload
+Use this to adjust the \f[V]expiry\f[R] time for an item in the upload
 queue.
-You will need to read the \f[C]id\f[R] of the item using
-\f[C]vfs/queue\f[R] before using this call.
+You will need to read the \f[V]id\f[R] of the item using
+\f[V]vfs/queue\f[R] before using this call.
 .PP
-You can then set \f[C]expiry\f[R] to a floating point number of seconds
+You can then set \f[V]expiry\f[R] to a floating point number of seconds
 from now when the item is eligible for upload.
 If you want the item to be uploaded as soon as possible then set it to a
 large negative number (eg -1000000000).
 If you want the upload of the item to be delayed for a long time then
 set it to a large positive number.
 .PP
-Setting the \f[C]expiry\f[R] of an item which has already has started
+Setting the \f[V]expiry\f[R] of an item which has already has started
 uploading will have no effect - the item will carry on being uploaded.
 .PP
-This will return an error if called with \f[C]--vfs-cache-mode\f[R] off
-or if the \f[C]id\f[R] passed is not found.
+This will return an error if called with \f[V]--vfs-cache-mode\f[R] off
+or if the \f[V]id\f[R] passed is not found.
 .PP
 This takes the following parameters
 .IP \[bu] 2
-\f[C]fs\f[R] - select the VFS in use (optional)
+\f[V]fs\f[R] - select the VFS in use (optional)
 .IP \[bu] 2
-\f[C]id\f[R] - a numeric ID as returned from \f[C]vfs/queue\f[R]
+\f[V]id\f[R] - a numeric ID as returned from \f[V]vfs/queue\f[R]
 .IP \[bu] 2
-\f[C]expiry\f[R] - a new expiry time as floating point seconds
+\f[V]expiry\f[R] - a new expiry time as floating point seconds
 .PP
 This returns an empty result on success, or an error.
 .PP
@@ -24233,7 +24251,7 @@ All calls must made using POST.
 The input objects can be supplied using URL parameters, POST parameters
 or by supplying \[dq]Content-Type: application/json\[dq] and a JSON blob
 in the body.
-There are examples of these below using \f[C]curl\f[R].
+There are examples of these below using \f[V]curl\f[R].
 .PP
 The response will be a JSON blob in the body of the response.
 This is formatted to be reasonably human-readable.
@@ -24305,7 +24323,7 @@ curl -X POST \[aq]http://localhost:5572/rc/error?potato=1&sausage=2\[aq]
 .fi
 .PP
 Note that curl doesn\[aq]t return errors to the shell unless you use the
-\f[C]-f\f[R] option
+\f[V]-f\f[R] option
 .IP
 .nf
 \f[C]
@@ -24393,7 +24411,7 @@ curl -H \[dq]Content-Type: application/json\[dq] -X POST -d \[aq]{\[dq]potato\[d
 .fi
 .SS Debugging rclone with pprof
 .PP
-If you use the \f[C]--rc\f[R] flag this will also enable the use of the
+If you use the \f[V]--rc\f[R] flag this will also enable the use of the
 go profiling tools on the same port.
 .PP
 To use these, first install go (https://golang.org/doc/install).
@@ -24410,7 +24428,7 @@ go tool pprof -web http://localhost:5572/debug/pprof/heap
 This should open a page in your browser showing what is using what
 memory.
 .PP
-You can also use the \f[C]-text\f[R] flag to produce a textual summary
+You can also use the \f[V]-text\f[R] flag to produce a textual summary
 .IP
 .nf
 \f[C]
@@ -24453,33 +24471,33 @@ http://localhost:5572/debug/pprof/
 .PP
 Here is how to use some of them:
 .IP \[bu] 2
-Memory: \f[C]go tool pprof http://localhost:5572/debug/pprof/heap\f[R]
+Memory: \f[V]go tool pprof http://localhost:5572/debug/pprof/heap\f[R]
 .IP \[bu] 2
 Go routines:
-\f[C]curl http://localhost:5572/debug/pprof/goroutine?debug=1\f[R]
+\f[V]curl http://localhost:5572/debug/pprof/goroutine?debug=1\f[R]
 .IP \[bu] 2
 30-second CPU profile:
-\f[C]go tool pprof http://localhost:5572/debug/pprof/profile\f[R]
+\f[V]go tool pprof http://localhost:5572/debug/pprof/profile\f[R]
 .IP \[bu] 2
 5-second execution trace:
-\f[C]wget http://localhost:5572/debug/pprof/trace?seconds=5\f[R]
+\f[V]wget http://localhost:5572/debug/pprof/trace?seconds=5\f[R]
 .IP \[bu] 2
 Goroutine blocking profile
 .RS 2
 .IP \[bu] 2
 Enable first with:
-\f[C]rclone rc debug/set-block-profile-rate rate=1\f[R] (docs)
+\f[V]rclone rc debug/set-block-profile-rate rate=1\f[R] (docs)
 .IP \[bu] 2
-\f[C]go tool pprof http://localhost:5572/debug/pprof/block\f[R]
+\f[V]go tool pprof http://localhost:5572/debug/pprof/block\f[R]
 .RE
 .IP \[bu] 2
 Contended mutexes:
 .RS 2
 .IP \[bu] 2
 Enable first with:
-\f[C]rclone rc debug/set-mutex-profile-fraction rate=1\f[R] (docs)
+\f[V]rclone rc debug/set-mutex-profile-fraction rate=1\f[R] (docs)
 .IP \[bu] 2
-\f[C]go tool pprof http://localhost:5572/debug/pprof/mutex\f[R]
+\f[V]go tool pprof http://localhost:5572/debug/pprof/mutex\f[R]
 .RE
 .PP
 See the net/http/pprof docs (https://golang.org/pkg/net/http/pprof/) for
@@ -24500,7 +24518,7 @@ Here is an overview of the major features of each cloud storage system.
 .PP
 .TS
 tab(@);
-l c c c c c c.
+lw(17.5n) cw(11.9n) cw(5.6n) cw(11.2n) cw(10.6n) cw(6.9n) cw(6.2n).
 T{
 Name
 T}@T{
@@ -24610,7 +24628,7 @@ T}
 T{
 Dropbox
 T}@T{
-DBHASH \[S1]
+DBHASH ¹
 T}@T{
 R
 T}@T{
@@ -24657,7 +24675,7 @@ FTP
 T}@T{
 -
 T}@T{
-R/W \[S1]\[u2070]
+R/W ¹⁰
 T}@T{
 No
 T}@T{
@@ -24745,7 +24763,7 @@ T}
 T{
 HiDrive
 T}@T{
-HiDrive \[S1]\[S2]
+HiDrive ¹²
 T}@T{
 R/W
 T}@T{
@@ -24777,7 +24795,7 @@ Internet Archive
 T}@T{
 MD5, SHA1, CRC32
 T}@T{
-R/W \[S1]\[S1]
+R/W ¹¹
 T}@T{
 No
 T}@T{
@@ -24835,7 +24853,7 @@ T}
 T{
 Mail.ru Cloud
 T}@T{
-Mailru \[u2076]
+Mailru ⁶
 T}@T{
 R/W
 T}@T{
@@ -24910,7 +24928,7 @@ T}
 T{
 Microsoft OneDrive
 T}@T{
-QuickXorHash \[u2075]
+QuickXorHash ⁵
 T}@T{
 DR/W
 T}@T{
@@ -24931,7 +24949,7 @@ R/W
 T}@T{
 Yes
 T}@T{
-Partial \[u2078]
+Partial ⁸
 T}@T{
 -
 T}@T{
@@ -24970,7 +24988,7 @@ T}
 T{
 pCloud
 T}@T{
-MD5, SHA1 \[u2077]
+MD5, SHA1 ⁷
 T}@T{
 R/W
 T}@T{
@@ -25062,7 +25080,7 @@ QingStor
 T}@T{
 MD5
 T}@T{
-- \[u2079]
+- ⁹
 T}@T{
 No
 T}@T{
@@ -25105,7 +25123,7 @@ T}
 T{
 SFTP
 T}@T{
-MD5, SHA1 \[S2]
+MD5, SHA1 ²
 T}@T{
 DR/W
 T}@T{
@@ -25180,7 +25198,7 @@ T}
 T{
 Uloz.to
 T}@T{
-MD5, SHA256 \[S1]\[S3]
+MD5, SHA256 ¹³
 T}@T{
 -
 T}@T{
@@ -25210,9 +25228,9 @@ T}
 T{
 WebDAV
 T}@T{
-MD5, SHA1 \[S3]
+MD5, SHA1 ³
 T}@T{
-R \[u2074]
+R ⁴
 T}@T{
 Depends
 T}@T{
@@ -25269,58 +25287,57 @@ DRWU
 T}
 .TE
 .PP
-\[S1] Dropbox supports its own custom
+¹ Dropbox supports its own custom
 hash (https://www.dropbox.com/developers/reference/content-hash).
 This is an SHA256 sum of all the 4 MiB block SHA256s.
 .PP
-\[S2] SFTP supports checksums if the same login has shell access and
-\f[C]md5sum\f[R] or \f[C]sha1sum\f[R] as well as \f[C]echo\f[R] are in
+² SFTP supports checksums if the same login has shell access and
+\f[V]md5sum\f[R] or \f[V]sha1sum\f[R] as well as \f[V]echo\f[R] are in
 the remote\[aq]s PATH.
 .PP
-\[S3] WebDAV supports hashes when used with Fastmail Files, Owncloud and
+³ WebDAV supports hashes when used with Fastmail Files, Owncloud and
 Nextcloud only.
 .PP
-\[u2074] WebDAV supports modtimes when used with Fastmail Files,
-Owncloud and Nextcloud only.
+⁴ WebDAV supports modtimes when used with Fastmail Files, Owncloud and
+Nextcloud only.
 .PP
-\[u2075]
+⁵
 QuickXorHash (https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash)
 is Microsoft\[aq]s own hash.
 .PP
-\[u2076] Mail.ru uses its own modified SHA1 hash
+⁶ Mail.ru uses its own modified SHA1 hash
 .PP
-\[u2077] pCloud only supports SHA1 (not MD5) in its EU region
+⁷ pCloud only supports SHA1 (not MD5) in its EU region
 .PP
-\[u2078] Opendrive does not support creation of duplicate files using
-their web client interface or other stock clients, but the underlying
-storage platform has been determined to allow duplicate files, and it is
-possible to create them with \f[C]rclone\f[R].
+⁸ Opendrive does not support creation of duplicate files using their web
+client interface or other stock clients, but the underlying storage
+platform has been determined to allow duplicate files, and it is
+possible to create them with \f[V]rclone\f[R].
 It may be that this is a mistake or an unsupported feature.
 .PP
-\[u2079] QingStor does not support SetModTime for objects bigger than 5
-GiB.
+⁹ QingStor does not support SetModTime for objects bigger than 5 GiB.
 .PP
-\[S1]\[u2070] FTP supports modtimes for the major FTP servers, and also
-others if they advertised required protocol extensions.
+¹⁰ FTP supports modtimes for the major FTP servers, and also others if
+they advertised required protocol extensions.
 See this (https://rclone.org/ftp/#modification-times) for more details.
 .PP
-\[S1]\[S1] Internet Archive requires option \f[C]wait_archive\f[R] to be
-set to a non-zero value for full modtime support.
+¹¹ Internet Archive requires option \f[V]wait_archive\f[R] to be set to
+a non-zero value for full modtime support.
 .PP
-\[S1]\[S2] HiDrive supports its own custom
+¹² HiDrive supports its own custom
 hash (https://static.hidrive.com/dev/0001).
 It combines SHA1 sums for each 4 KiB block hierarchically to a single
 top-level sum.
 .PP
-\[S1]\[S3] Uloz.to provides server-calculated MD5 hash upon file upload.
+¹³ Uloz.to provides server-calculated MD5 hash upon file upload.
 MD5 and SHA256 hashes are client-calculated and stored as metadata
 fields.
 .SS Hash
 .PP
 The cloud storage system supports various hash types of the objects.
 The hashes are used when transferring data as an integrity check and can
-be specifically used with the \f[C]--checksum\f[R] flag in syncs and in
-the \f[C]check\f[R] command.
+be specifically used with the \f[V]--checksum\f[R] flag in syncs and in
+the \f[V]check\f[R] command.
 .PP
 To use the verify checksums when transferring between cloud storage
 systems they must support a common hash type.
@@ -25336,7 +25353,7 @@ To be relevant for syncing it should be able to store the modification
 time of the source object.
 If this is not the case, rclone will only check the file size by
 default, though can be configured to check the file hash (with the
-\f[C]--checksum\f[R] flag).
+\f[V]--checksum\f[R] flag).
 Ideally it should also be possible to change the timestamp of an
 existing file without having to re-upload it.
 .PP
@@ -25350,62 +25367,62 @@ Explanation
 T}
 _
 T{
-\f[C]-\f[R]
+\f[V]-\f[R]
 T}@T{
 ModTimes not supported - times likely the upload time
 T}
 T{
-\f[C]R\f[R]
+\f[V]R\f[R]
 T}@T{
 ModTimes supported on files but can\[aq]t be changed without re-upload
 T}
 T{
-\f[C]R/W\f[R]
+\f[V]R/W\f[R]
 T}@T{
 Read and Write ModTimes fully supported on files
 T}
 T{
-\f[C]DR\f[R]
+\f[V]DR\f[R]
 T}@T{
 ModTimes supported on files and directories but can\[aq]t be changed
 without re-upload
 T}
 T{
-\f[C]DR/W\f[R]
+\f[V]DR/W\f[R]
 T}@T{
 Read and Write ModTimes fully supported on files and directories
 T}
 .TE
 .PP
-Storage systems with a \f[C]-\f[R] in the ModTime column, means the
+Storage systems with a \f[V]-\f[R] in the ModTime column, means the
 modification read on objects is not the modification time of the file
 when uploaded.
 It is most likely the time the file was uploaded, or possibly something
 else (like the time the picture was taken in Google Photos).
 .PP
-Storage systems with a \f[C]R\f[R] (for read-only) in the ModTime
+Storage systems with a \f[V]R\f[R] (for read-only) in the ModTime
 column, means the it keeps modification times on objects, and updates
 them when uploading objects, but it does not support changing only the
-modification time (\f[C]SetModTime\f[R] operation) without re-uploading,
+modification time (\f[V]SetModTime\f[R] operation) without re-uploading,
 possibly not even without deleting existing first.
-Some operations in rclone, such as \f[C]copy\f[R] and \f[C]sync\f[R]
-commands, will automatically check for \f[C]SetModTime\f[R] support and
+Some operations in rclone, such as \f[V]copy\f[R] and \f[V]sync\f[R]
+commands, will automatically check for \f[V]SetModTime\f[R] support and
 re-upload if necessary to keep the modification times in sync.
-Other commands will not work without \f[C]SetModTime\f[R] support, e.g.
-\f[C]touch\f[R] command on an existing file will fail, and changes to
-modification time only on a files in a \f[C]mount\f[R] will be silently
+Other commands will not work without \f[V]SetModTime\f[R] support, e.g.
+\f[V]touch\f[R] command on an existing file will fail, and changes to
+modification time only on a files in a \f[V]mount\f[R] will be silently
 ignored.
 .PP
-Storage systems with \f[C]R/W\f[R] (for read/write) in the ModTime
+Storage systems with \f[V]R/W\f[R] (for read/write) in the ModTime
 column, means they do also support modtime-only operations.
 .PP
-Storage systems with \f[C]D\f[R] in the ModTime column means that the
+Storage systems with \f[V]D\f[R] in the ModTime column means that the
 following symbols apply to directories as well as files.
 .SS Case Insensitive
 .PP
 If a cloud storage systems is case sensitive then it is possible to have
 two files which differ only in case, e.g.
-\f[C]file.txt\f[R] and \f[C]FILE.txt\f[R].
+\f[V]file.txt\f[R] and \f[V]FILE.txt\f[R].
 If a cloud storage system is case insensitive then that isn\[aq]t
 possible.
 .PP
@@ -25435,12 +25452,12 @@ If a cloud storage system allows duplicate files then it can have two
 objects with the same name.
 .PP
 This confuses rclone greatly when syncing - use the
-\f[C]rclone dedupe\f[R] command to rename or remove duplicates.
+\f[V]rclone dedupe\f[R] command to rename or remove duplicates.
 .SS Restricted filenames
 .PP
 Some cloud storage systems might have restrictions on the characters
 that are usable in file or directory names.
-When \f[C]rclone\f[R] detects such a name during a file upload, it will
+When \f[V]rclone\f[R] detects such a name during a file upload, it will
 transparently replace the restricted characters with similar looking
 Unicode characters.
 To handle the different sets of restricted characters for different
@@ -25450,23 +25467,22 @@ This process is designed to avoid ambiguous file names as much as
 possible and allow to move files between many cloud storage systems
 transparently.
 .PP
-The name shown by \f[C]rclone\f[R] to the user or during log output will
+The name shown by \f[V]rclone\f[R] to the user or during log output will
 only contain a minimal set of replaced characters to ensure correct
 formatting and not necessarily the actual name used on the cloud
 storage.
 .PP
 This transformation is reversed when downloading a file or parsing
-\f[C]rclone\f[R] arguments.
-For example, when uploading a file named \f[C]my file?.txt\f[R] to
-Onedrive, it will be displayed as \f[C]my file?.txt\f[R] on the console,
-but stored as \f[C]my file\[uFF1F].txt\f[R] to Onedrive (the \f[C]?\f[R]
-gets replaced by the similar looking \f[C]\[uFF1F]\f[R] character, the
-so-called \[dq]fullwidth question mark\[dq]).
+\f[V]rclone\f[R] arguments.
+For example, when uploading a file named \f[V]my file?.txt\f[R] to
+Onedrive, it will be displayed as \f[V]my file?.txt\f[R] on the console,
+but stored as \f[V]my file？.txt\f[R] to Onedrive (the \f[V]?\f[R] gets
+replaced by the similar looking \f[V]？\f[R] character, the so-called
+\[dq]fullwidth question mark\[dq]).
 The reverse transformation allows to read a file
-\f[C]unusual/name.txt\f[R] from Google Drive, by passing the name
-\f[C]unusual\[uFF0F]name.txt\f[R] on the command line (the \f[C]/\f[R]
-needs to be replaced by the similar looking \f[C]\[uFF0F]\f[R]
-character).
+\f[V]unusual/name.txt\f[R] from Google Drive, by passing the name
+\f[V]unusual／name.txt\f[R] on the command line (the \f[V]/\f[R] needs
+to be replaced by the similar looking \f[V]／\f[R] character).
 .SS Caveats
 .PP
 The filename encoding system works well in most cases, at least where
@@ -25477,12 +25493,12 @@ E.g.
 when file names are written in Chinese, or Japanese, where it is always
 the Unicode fullwidth variants of the punctuation marks that are used.
 .PP
-On Windows, the characters \f[C]:\f[R], \f[C]*\f[R] and \f[C]?\f[R] are
+On Windows, the characters \f[V]:\f[R], \f[V]*\f[R] and \f[V]?\f[R] are
 examples of restricted characters.
 If these are used in filenames on a remote that supports it, Rclone will
 transparently convert them to their fullwidth Unicode variants
-\f[C]\[uFF0A]\f[R], \f[C]\[uFF1F]\f[R] and \f[C]\[uFF1A]\f[R] when
-downloading to Windows, and back again when uploading.
+\f[V]＊\f[R], \f[V]？\f[R] and \f[V]：\f[R] when downloading to Windows,
+and back again when uploading.
 This way files with names that are not allowed on Windows can still be
 stored.
 .PP
@@ -25491,30 +25507,30 @@ same Unicode characters in their names, they will be included in the
 same conversion process.
 E.g.
 if you create a file in your Windows filesystem with name
-\f[C]Test\[uFF1A]1.jpg\f[R], where \f[C]\[uFF1A]\f[R] is the Unicode
-fullwidth colon symbol, and use rclone to upload it to Google Drive,
-which supports regular \f[C]:\f[R] (halfwidth question mark), rclone
-will replace the fullwidth \f[C]:\f[R] with the halfwidth \f[C]:\f[R]
-and store the file as \f[C]Test:1.jpg\f[R] in Google Drive.
+\f[V]Test：1.jpg\f[R], where \f[V]：\f[R] is the Unicode fullwidth colon
+symbol, and use rclone to upload it to Google Drive, which supports
+regular \f[V]:\f[R] (halfwidth question mark), rclone will replace the
+fullwidth \f[V]:\f[R] with the halfwidth \f[V]:\f[R] and store the file
+as \f[V]Test:1.jpg\f[R] in Google Drive.
 Since both Windows and Google Drive allows the name
-\f[C]Test\[uFF1A]1.jpg\f[R], it would probably be better if rclone just
-kept the name as is in this case.
+\f[V]Test：1.jpg\f[R], it would probably be better if rclone just kept
+the name as is in this case.
 .PP
 With the opposite situation; if you have a file named
-\f[C]Test:1.jpg\f[R], in your Google Drive, e.g.
-uploaded from a Linux system where \f[C]:\f[R] is valid in file names.
+\f[V]Test:1.jpg\f[R], in your Google Drive, e.g.
+uploaded from a Linux system where \f[V]:\f[R] is valid in file names.
 Then later use rclone to copy this file to your Windows computer you
 will notice that on your local disk it gets renamed to
-\f[C]Test\[uFF1A]1.jpg\f[R].
-The original filename is not legal on Windows, due to the \f[C]:\f[R],
+\f[V]Test：1.jpg\f[R].
+The original filename is not legal on Windows, due to the \f[V]:\f[R],
 and rclone therefore renames it to make the copy possible.
 That is all good.
 However, this can also lead to an issue: If you already had a
-\f[I]different\f[R] file named \f[C]Test\[uFF1A]1.jpg\f[R] on Windows,
-and then use rclone to copy either way.
-Rclone will then treat the file originally named \f[C]Test:1.jpg\f[R] on
-Google Drive and the file originally named \f[C]Test\[uFF1A]1.jpg\f[R]
-on Windows as the same file, and replace the contents from one with the
+\f[I]different\f[R] file named \f[V]Test：1.jpg\f[R] on Windows, and
+then use rclone to copy either way.
+Rclone will then treat the file originally named \f[V]Test:1.jpg\f[R] on
+Google Drive and the file originally named \f[V]Test：1.jpg\f[R] on
+Windows as the same file, and replace the contents from one with the
 other.
 .PP
 Its virtually impossible to handle all cases like these correctly in all
@@ -25531,11 +25547,9 @@ characters, and Google drive a storage system with few.)
 The table below shows the characters that are replaced by default.
 .PP
 When a replacement character is found in a filename, this character will
-be escaped with the \f[C]\[u201B]\f[R] character to avoid ambiguous file
-names.
+be escaped with the \f[V]‛\f[R] character to avoid ambiguous file names.
 (e.g.
-a file named \f[C]\[u2400].txt\f[R] would shown as
-\f[C]\[u201B]\[u2400].txt\f[R])
+a file named \f[V]␀.txt\f[R] would shown as \f[V]‛␀.txt\f[R])
 .PP
 Each cloud storage backend can use a different set of characters, which
 will be specified in the documentation for each backend.
@@ -25556,238 +25570,238 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 SOH
 T}@T{
 0x01
 T}@T{
-\[u2401]
+␁
 T}
 T{
 STX
 T}@T{
 0x02
 T}@T{
-\[u2402]
+␂
 T}
 T{
 ETX
 T}@T{
 0x03
 T}@T{
-\[u2403]
+␃
 T}
 T{
 EOT
 T}@T{
 0x04
 T}@T{
-\[u2404]
+␄
 T}
 T{
 ENQ
 T}@T{
 0x05
 T}@T{
-\[u2405]
+␅
 T}
 T{
 ACK
 T}@T{
 0x06
 T}@T{
-\[u2406]
+␆
 T}
 T{
 BEL
 T}@T{
 0x07
 T}@T{
-\[u2407]
+␇
 T}
 T{
 BS
 T}@T{
 0x08
 T}@T{
-\[u2408]
+␈
 T}
 T{
 HT
 T}@T{
 0x09
 T}@T{
-\[u2409]
+␉
 T}
 T{
 LF
 T}@T{
 0x0A
 T}@T{
-\[u240A]
+␊
 T}
 T{
 VT
 T}@T{
 0x0B
 T}@T{
-\[u240B]
+␋
 T}
 T{
 FF
 T}@T{
 0x0C
 T}@T{
-\[u240C]
+␌
 T}
 T{
 CR
 T}@T{
 0x0D
 T}@T{
-\[u240D]
+␍
 T}
 T{
 SO
 T}@T{
 0x0E
 T}@T{
-\[u240E]
+␎
 T}
 T{
 SI
 T}@T{
 0x0F
 T}@T{
-\[u240F]
+␏
 T}
 T{
 DLE
 T}@T{
 0x10
 T}@T{
-\[u2410]
+␐
 T}
 T{
 DC1
 T}@T{
 0x11
 T}@T{
-\[u2411]
+␑
 T}
 T{
 DC2
 T}@T{
 0x12
 T}@T{
-\[u2412]
+␒
 T}
 T{
 DC3
 T}@T{
 0x13
 T}@T{
-\[u2413]
+␓
 T}
 T{
 DC4
 T}@T{
 0x14
 T}@T{
-\[u2414]
+␔
 T}
 T{
 NAK
 T}@T{
 0x15
 T}@T{
-\[u2415]
+␕
 T}
 T{
 SYN
 T}@T{
 0x16
 T}@T{
-\[u2416]
+␖
 T}
 T{
 ETB
 T}@T{
 0x17
 T}@T{
-\[u2417]
+␗
 T}
 T{
 CAN
 T}@T{
 0x18
 T}@T{
-\[u2418]
+␘
 T}
 T{
 EM
 T}@T{
 0x19
 T}@T{
-\[u2419]
+␙
 T}
 T{
 SUB
 T}@T{
 0x1A
 T}@T{
-\[u241A]
+␚
 T}
 T{
 ESC
 T}@T{
 0x1B
 T}@T{
-\[u241B]
+␛
 T}
 T{
 FS
 T}@T{
 0x1C
 T}@T{
-\[u241C]
+␜
 T}
 T{
 GS
 T}@T{
 0x1D
 T}@T{
-\[u241D]
+␝
 T}
 T{
 RS
 T}@T{
 0x1E
 T}@T{
-\[u241E]
+␞
 T}
 T{
 US
 T}@T{
 0x1F
 T}@T{
-\[u241F]
+␟
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 T{
 DEL
 T}@T{
 0x7F
 T}@T{
-\[u2421]
+␡
 T}
 .TE
 .PP
@@ -25806,12 +25820,12 @@ _
 T{
 \&.
 T}@T{
-\[uFF0E]
+．
 T}
 T{
 \&..
 T}@T{
-\[uFF0E]\[uFF0E]
+．．
 T}
 .TE
 .SS Invalid UTF-8 bytes
@@ -25822,8 +25836,8 @@ or directory names.
 In this case all invalid UTF-8 bytes will be replaced with a quoted
 representation of the byte value to allow uploading a file to such a
 backend.
-For example, the invalid byte \f[C]0xFE\f[R] will be encoded as
-\f[C]\[u201B]FE\f[R].
+For example, the invalid byte \f[V]0xFE\f[R] will be encoded as
+\f[V]‛FE\f[R].
 .PP
 A common source of invalid UTF-8 bytes are local filesystems, that store
 names in a different encoding than UTF-8 or UTF-16, like latin1.
@@ -25832,30 +25846,29 @@ for details.
 .SS Encoding option
 .PP
 Most backends have an encoding option, specified as a flag
-\f[C]--backend-encoding\f[R] where \f[C]backend\f[R] is the name of the
-backend, or as a config parameter \f[C]encoding\f[R] (you\[aq]ll need to
-select the Advanced config in \f[C]rclone config\f[R] to see it).
+\f[V]--backend-encoding\f[R] where \f[V]backend\f[R] is the name of the
+backend, or as a config parameter \f[V]encoding\f[R] (you\[aq]ll need to
+select the Advanced config in \f[V]rclone config\f[R] to see it).
 .PP
 This will have default value which encodes and decodes characters in
 such a way as to preserve the maximum number of characters (see above).
 .PP
 However this can be incorrect in some scenarios, for example if you have
-a Windows file system with Unicode fullwidth characters
-\f[C]\[uFF0A]\f[R], \f[C]\[uFF1F]\f[R] or \f[C]\[uFF1A]\f[R], that you
-want to remain as those characters on the remote rather than being
-translated to regular (halfwidth) \f[C]*\f[R], \f[C]?\f[R] and
-\f[C]:\f[R].
+a Windows file system with Unicode fullwidth characters \f[V]＊\f[R],
+\f[V]？\f[R] or \f[V]：\f[R], that you want to remain as those
+characters on the remote rather than being translated to regular
+(halfwidth) \f[V]*\f[R], \f[V]?\f[R] and \f[V]:\f[R].
 .PP
-The \f[C]--backend-encoding\f[R] flags allow you to change that.
+The \f[V]--backend-encoding\f[R] flags allow you to change that.
 You can disable the encoding completely with
-\f[C]--backend-encoding Raw\f[R] or set \f[C]encoding = Raw\f[R] in the
+\f[V]--backend-encoding Raw\f[R] or set \f[V]encoding = Raw\f[R] in the
 config file.
 .PP
 Encoding takes a comma separated list of encodings.
 You can see the list of all possible values by passing an invalid value
 to this flag, e.g.
-\f[C]--local-encoding \[dq]help\[dq]\f[R].
-The command \f[C]rclone help flags encoding\f[R] will show you the
+\f[V]--local-encoding \[dq]help\[dq]\f[R].
+The command \f[V]rclone help flags encoding\f[R] will show you the
 defaults for the backends.
 .PP
 .TS
@@ -25872,86 +25885,86 @@ _
 T{
 Asterisk
 T}@T{
-\f[C]*\f[R]
+\f[V]*\f[R]
 T}@T{
-\f[C]\[uFF0A]\f[R]
+\f[V]＊\f[R]
 T}
 T{
 BackQuote
 T}@T{
-\f[C]\[ga]\f[R]
+\f[V]\[ga]\f[R]
 T}@T{
-\f[C]\[uFF40]\f[R]
+\f[V]｀\f[R]
 T}
 T{
 BackSlash
 T}@T{
-\f[C]\[rs]\f[R]
+\f[V]\[rs]\f[R]
 T}@T{
-\f[C]\[uFF3C]\f[R]
+\f[V]＼\f[R]
 T}
 T{
 Colon
 T}@T{
-\f[C]:\f[R]
+\f[V]:\f[R]
 T}@T{
-\f[C]\[uFF1A]\f[R]
+\f[V]：\f[R]
 T}
 T{
 CrLf
 T}@T{
 CR 0x0D, LF 0x0A
 T}@T{
-\f[C]\[u240D]\f[R], \f[C]\[u240A]\f[R]
+\f[V]␍\f[R], \f[V]␊\f[R]
 T}
 T{
 Ctl
 T}@T{
 All control characters 0x00-0x1F
 T}@T{
-\f[C]\[u2400]\[u2401]\[u2402]\[u2403]\[u2404]\[u2405]\[u2406]\[u2407]\[u2408]\[u2409]\[u240A]\[u240B]\[u240C]\[u240D]\[u240E]\[u240F]\[u2410]\[u2411]\[u2412]\[u2413]\[u2414]\[u2415]\[u2416]\[u2417]\[u2418]\[u2419]\[u241A]\[u241B]\[u241C]\[u241D]\[u241E]\[u241F]\f[R]
+\f[V]␀␁␂␃␄␅␆␇␈␉␊␋␌␍␎␏␐␑␒␓␔␕␖␗␘␙␚␛␜␝␞␟\f[R]
 T}
 T{
 Del
 T}@T{
 DEL 0x7F
 T}@T{
-\f[C]\[u2421]\f[R]
+\f[V]␡\f[R]
 T}
 T{
 Dollar
 T}@T{
-\f[C]$\f[R]
+\f[V]$\f[R]
 T}@T{
-\f[C]\[uFF04]\f[R]
+\f[V]＄\f[R]
 T}
 T{
 Dot
 T}@T{
-\f[C].\f[R] or \f[C]..\f[R] as entire string
+\f[V].\f[R] or \f[V]..\f[R] as entire string
 T}@T{
-\f[C]\[uFF0E]\f[R], \f[C]\[uFF0E]\[uFF0E]\f[R]
+\f[V]．\f[R], \f[V]．．\f[R]
 T}
 T{
 DoubleQuote
 T}@T{
-\f[C]\[dq]\f[R]
+\f[V]\[dq]\f[R]
 T}@T{
-\f[C]\[uFF02]\f[R]
+\f[V]＂\f[R]
 T}
 T{
 Exclamation
 T}@T{
-\f[C]!\f[R]
+\f[V]!\f[R]
 T}@T{
-\f[C]\[uFF01]\f[R]
+\f[V]！\f[R]
 T}
 T{
 Hash
 T}@T{
-\f[C]#\f[R]
+\f[V]#\f[R]
 T}@T{
-\f[C]\[uFF03]\f[R]
+\f[V]＃\f[R]
 T}
 T{
 InvalidUtf8
@@ -25959,126 +25972,123 @@ T}@T{
 An invalid UTF-8 character (e.g.
 latin1)
 T}@T{
-\f[C]\[uFFFD]\f[R]
+\f[V]�\f[R]
 T}
 T{
 LeftCrLfHtVt
 T}@T{
 CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the left of a string
 T}@T{
-\f[C]\[u240D]\f[R], \f[C]\[u240A]\f[R], \f[C]\[u2409]\f[R],
-\f[C]\[u240B]\f[R]
+\f[V]␍\f[R], \f[V]␊\f[R], \f[V]␉\f[R], \f[V]␋\f[R]
 T}
 T{
 LeftPeriod
 T}@T{
-\f[C].\f[R] on the left of a string
+\f[V].\f[R] on the left of a string
 T}@T{
-\f[C].\f[R]
+\f[V].\f[R]
 T}
 T{
 LeftSpace
 T}@T{
 SPACE on the left of a string
 T}@T{
-\f[C]\[u2420]\f[R]
+\f[V]␠\f[R]
 T}
 T{
 LeftTilde
 T}@T{
-\f[C]\[ti]\f[R] on the left of a string
+\f[V]\[ti]\f[R] on the left of a string
 T}@T{
-\f[C]\[uFF5E]\f[R]
+\f[V]～\f[R]
 T}
 T{
 LtGt
 T}@T{
-\f[C]<\f[R], \f[C]>\f[R]
+\f[V]<\f[R], \f[V]>\f[R]
 T}@T{
-\f[C]\[uFF1C]\f[R], \f[C]\[uFF1E]\f[R]
+\f[V]＜\f[R], \f[V]＞\f[R]
 T}
 T{
-None \[S1]
+None ¹
 T}@T{
 NUL 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 Percent
 T}@T{
-\f[C]%\f[R]
+\f[V]%\f[R]
 T}@T{
-\f[C]\[uFF05]\f[R]
+\f[V]％\f[R]
 T}
 T{
 Pipe
 T}@T{
 |
 T}@T{
-\f[C]\[uFF5C]\f[R]
+\f[V]｜\f[R]
 T}
 T{
 Question
 T}@T{
-\f[C]?\f[R]
+\f[V]?\f[R]
 T}@T{
-\f[C]\[uFF1F]\f[R]
+\f[V]？\f[R]
 T}
 T{
 RightCrLfHtVt
 T}@T{
 CR 0x0D, LF 0x0A, HT 0x09, VT 0x0B on the right of a string
 T}@T{
-\f[C]\[u240D]\f[R], \f[C]\[u240A]\f[R], \f[C]\[u2409]\f[R],
-\f[C]\[u240B]\f[R]
+\f[V]␍\f[R], \f[V]␊\f[R], \f[V]␉\f[R], \f[V]␋\f[R]
 T}
 T{
 RightPeriod
 T}@T{
-\f[C].\f[R] on the right of a string
+\f[V].\f[R] on the right of a string
 T}@T{
-\f[C].\f[R]
+\f[V].\f[R]
 T}
 T{
 RightSpace
 T}@T{
 SPACE on the right of a string
 T}@T{
-\f[C]\[u2420]\f[R]
+\f[V]␠\f[R]
 T}
 T{
 Semicolon
 T}@T{
-\f[C];\f[R]
+\f[V];\f[R]
 T}@T{
-\f[C]\[uFF1B]\f[R]
+\f[V]；\f[R]
 T}
 T{
 SingleQuote
 T}@T{
-\f[C]\[aq]\f[R]
+\f[V]\[aq]\f[R]
 T}@T{
-\f[C]\[uFF07]\f[R]
+\f[V]＇\f[R]
 T}
 T{
 Slash
 T}@T{
-\f[C]/\f[R]
+\f[V]/\f[R]
 T}@T{
-\f[C]\[uFF0F]\f[R]
+\f[V]／\f[R]
 T}
 T{
 SquareBracket
 T}@T{
-\f[C][\f[R], \f[C]]\f[R]
+\f[V][\f[R], \f[V]]\f[R]
 T}@T{
-\f[C]\[uFF3B]\f[R], \f[C]\[uFF3D]\f[R]
+\f[V]［\f[R], \f[V]］\f[R]
 T}
 .TE
 .PP
-\[S1] Encoding from NUL 0x00 to \[u2400] is always implicit except when
-using Raw.
+¹ Encoding from NUL 0x00 to ␀ is always implicit except when using Raw.
 It was previously incorrectly documented as disabling encoding, and to
 maintain backward compatibility, its behavior has not been changed.
 .SS Encoding example: FTP
@@ -26111,20 +26121,20 @@ Slash,LtGt,DoubleQuote,Colon,Question,Asterisk,Pipe,BackSlash,Ctl,RightSpace,Rig
 \f[R]
 .fi
 .PP
-This can be specified using the \f[C]--ftp-encoding\f[R] flag or using
-an \f[C]encoding\f[R] parameter in the config file.
+This can be specified using the \f[V]--ftp-encoding\f[R] flag or using
+an \f[V]encoding\f[R] parameter in the config file.
 .SS Encoding example: Windows
 .PP
 As a nother example, take a Windows system where there is a file with
-name \f[C]Test\[uFF1A]1.jpg\f[R], where \f[C]\[uFF1A]\f[R] is the
-Unicode fullwidth colon symbol.
-When using rclone to copy this to a remote which supports \f[C]:\f[R],
+name \f[V]Test：1.jpg\f[R], where \f[V]：\f[R] is the Unicode fullwidth
+colon symbol.
+When using rclone to copy this to a remote which supports \f[V]:\f[R],
 the regular (halfwidth) colon (such as Google Drive), you will notice
-that the file gets renamed to \f[C]Test:1.jpg\f[R].
+that the file gets renamed to \f[V]Test:1.jpg\f[R].
 .PP
 To avoid this you can change the set of characters rclone should convert
 for the local filesystem, using command-line argument
-\f[C]--local-encoding\f[R].
+\f[V]--local-encoding\f[R].
 Rclone\[aq]s default behavior on Windows corresponds to
 .IP
 .nf
@@ -26133,10 +26143,10 @@ Rclone\[aq]s default behavior on Windows corresponds to
 \f[R]
 .fi
 .PP
-If you want to use fullwidth characters \f[C]\[uFF1A]\f[R],
-\f[C]\[uFF0A]\f[R] and \f[C]\[uFF1F]\f[R] in your filenames without
-rclone changing them when uploading to a remote, then set the same as
-the default value but without \f[C]Colon,Question,Asterisk\f[R]:
+If you want to use fullwidth characters \f[V]：\f[R], \f[V]＊\f[R] and
+\f[V]？\f[R] in your filenames without rclone changing them when
+uploading to a remote, then set the same as the default value but
+without \f[V]Colon,Question,Asterisk\f[R]:
 .IP
 .nf
 \f[C]
@@ -26145,18 +26155,18 @@ the default value but without \f[C]Colon,Question,Asterisk\f[R]:
 .fi
 .PP
 Alternatively, you can disable the conversion of any characters with
-\f[C]--local-encoding Raw\f[R].
+\f[V]--local-encoding Raw\f[R].
 .PP
-Instead of using command-line argument \f[C]--local-encoding\f[R], you
+Instead of using command-line argument \f[V]--local-encoding\f[R], you
 may also set it as environment
 variable (https://rclone.org/docs/#environment-variables)
-\f[C]RCLONE_LOCAL_ENCODING\f[R], or
+\f[V]RCLONE_LOCAL_ENCODING\f[R], or
 configure (https://rclone.org/docs/#configure) a remote of type
-\f[C]local\f[R] in your config, and set the \f[C]encoding\f[R] option
+\f[V]local\f[R] in your config, and set the \f[V]encoding\f[R] option
 there.
 .PP
 The risk by doing this is that if you have a filename with the regular
-(halfwidth) \f[C]:\f[R], \f[C]*\f[R] and \f[C]?\f[R] in your cloud
+(halfwidth) \f[V]:\f[R], \f[V]*\f[R] and \f[V]?\f[R] in your cloud
 storage, and you try to download it to your Windows filesystem, this
 will fail.
 These characters are not valid in filenames on Windows, and you have
@@ -26166,17 +26176,17 @@ fullwidth variants.
 .PP
 MIME types (also known as media types) classify types of documents using
 a simple text classification, e.g.
-\f[C]text/html\f[R] or \f[C]application/pdf\f[R].
+\f[V]text/html\f[R] or \f[V]application/pdf\f[R].
 .PP
-Some cloud storage systems support reading (\f[C]R\f[R]) the MIME type
-of objects and some support writing (\f[C]W\f[R]) the MIME type of
+Some cloud storage systems support reading (\f[V]R\f[R]) the MIME type
+of objects and some support writing (\f[V]W\f[R]) the MIME type of
 objects.
 .PP
 The MIME type can be important if you are serving files directly to HTTP
 from the storage system.
 .PP
-If you are copying from a remote which supports reading (\f[C]R\f[R]) to
-a remote which supports writing (\f[C]W\f[R]) then rclone will preserve
+If you are copying from a remote which supports reading (\f[V]R\f[R]) to
+a remote which supports writing (\f[V]W\f[R]) then rclone will preserve
 the MIME types.
 Otherwise they will be guessed from the extension, or the remote itself
 may assign the MIME type.
@@ -26198,33 +26208,33 @@ Explanation
 T}
 _
 T{
-\f[C]R\f[R]
+\f[V]R\f[R]
 T}@T{
 Read only System Metadata on files only
 T}
 T{
-\f[C]RW\f[R]
+\f[V]RW\f[R]
 T}@T{
 Read and write System Metadata on files only
 T}
 T{
-\f[C]RWU\f[R]
+\f[V]RWU\f[R]
 T}@T{
 Read and write System Metadata and read and write User Metadata on files
 only
 T}
 T{
-\f[C]DR\f[R]
+\f[V]DR\f[R]
 T}@T{
 Read only System Metadata on files and directories
 T}
 T{
-\f[C]DRW\f[R]
+\f[V]DRW\f[R]
 T}@T{
 Read and write System Metadata on files and directories
 T}
 T{
-\f[C]DRWU\f[R]
+\f[V]DRWU\f[R]
 T}@T{
 Read and write System Metadata and read and write User Metadata on files
 and directories
@@ -26929,7 +26939,7 @@ Yes
 T}@T{
 Yes
 T}@T{
-Yes \[u2075]
+Yes ⁵
 T}@T{
 No
 T}@T{
@@ -26969,7 +26979,7 @@ T}
 T{
 OpenStack Swift
 T}@T{
-Yes \[S1]
+Yes ¹
 T}@T{
 Yes
 T}@T{
@@ -27246,7 +27256,7 @@ SFTP
 T}@T{
 No
 T}@T{
-Yes \[u2074]
+Yes ⁴
 T}@T{
 Yes
 T}@T{
@@ -27344,7 +27354,7 @@ T}
 T{
 Storj
 T}@T{
-Yes \[S2]
+Yes ²
 T}@T{
 Yes
 T}@T{
@@ -27431,7 +27441,7 @@ No
 T}@T{
 No
 T}@T{
-Yes \[S3]
+Yes ³
 T}@T{
 No
 T}@T{
@@ -27518,18 +27528,18 @@ Yes
 T}
 .TE
 .PP
-\[S1] Note Swift implements this in order to delete directory markers
-but it doesn\[aq]t actually have a quicker way of deleting files other
-than deleting them individually.
+¹ Note Swift implements this in order to delete directory markers but it
+doesn\[aq]t actually have a quicker way of deleting files other than
+deleting them individually.
 .PP
-\[S2] Storj implements this efficiently only for entire buckets.
+² Storj implements this efficiently only for entire buckets.
 If purging a directory inside a bucket, files are deleted individually.
 .PP
-\[S3] StreamUpload is not supported with Nextcloud
+³ StreamUpload is not supported with Nextcloud
 .PP
-\[u2074] Use the \f[C]--sftp-copy-is-hardlink\f[R] flag to enable.
+⁴ Use the \f[V]--sftp-copy-is-hardlink\f[R] flag to enable.
 .PP
-\[u2075] Use the \f[C]--onedrive-delta\f[R] flag to enable.
+⁵ Use the \f[V]--onedrive-delta\f[R] flag to enable.
 .SS Purge
 .PP
 This deletes a directory quicker than just deleting all the files in the
@@ -27539,45 +27549,44 @@ directory.
 Used when copying an object to and from the same remote.
 This known as a server-side copy so you can copy a file without
 downloading it and uploading it again.
-It is used if you use \f[C]rclone copy\f[R] or \f[C]rclone move\f[R] if
-the remote doesn\[aq]t support \f[C]Move\f[R] directly.
+It is used if you use \f[V]rclone copy\f[R] or \f[V]rclone move\f[R] if
+the remote doesn\[aq]t support \f[V]Move\f[R] directly.
 .PP
-If the server doesn\[aq]t support \f[C]Copy\f[R] directly then for copy
+If the server doesn\[aq]t support \f[V]Copy\f[R] directly then for copy
 operations the file is downloaded then re-uploaded.
 .SS Move
 .PP
 Used when moving/renaming an object on the same remote.
 This is known as a server-side move of a file.
-This is used in \f[C]rclone move\f[R] if the server doesn\[aq]t support
-\f[C]DirMove\f[R].
+This is used in \f[V]rclone move\f[R] if the server doesn\[aq]t support
+\f[V]DirMove\f[R].
 .PP
-If the server isn\[aq]t capable of \f[C]Move\f[R] then rclone simulates
-it with \f[C]Copy\f[R] then delete.
-If the server doesn\[aq]t support \f[C]Copy\f[R] then rclone will
+If the server isn\[aq]t capable of \f[V]Move\f[R] then rclone simulates
+it with \f[V]Copy\f[R] then delete.
+If the server doesn\[aq]t support \f[V]Copy\f[R] then rclone will
 download the file and re-upload it.
 .SS DirMove
 .PP
-This is used to implement \f[C]rclone move\f[R] to move a directory if
+This is used to implement \f[V]rclone move\f[R] to move a directory if
 possible.
-If it isn\[aq]t then it will use \f[C]Move\f[R] on each file (which
-falls back to \f[C]Copy\f[R] then download and upload - see
-\f[C]Move\f[R] section).
+If it isn\[aq]t then it will use \f[V]Move\f[R] on each file (which
+falls back to \f[V]Copy\f[R] then download and upload - see
+\f[V]Move\f[R] section).
 .SS CleanUp
 .PP
 This is used for emptying the trash for a remote by
-\f[C]rclone cleanup\f[R].
+\f[V]rclone cleanup\f[R].
 .PP
-If the server can\[aq]t do \f[C]CleanUp\f[R] then
-\f[C]rclone cleanup\f[R] will return an error.
+If the server can\[aq]t do \f[V]CleanUp\f[R] then
+\f[V]rclone cleanup\f[R] will return an error.
 .PP
-\[dd]\[dd] Note that while Box implements this it has to delete every
-file individually so it will be slower than emptying the trash via the
-WebUI
+‡‡ Note that while Box implements this it has to delete every file
+individually so it will be slower than emptying the trash via the WebUI
 .SS ListR
 .PP
 The remote supports a recursive list to list all the contents beneath a
 directory quickly.
-This enables the \f[C]--fast-list\f[R] flag to work.
+This enables the \f[V]--fast-list\f[R] flag to work.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
 .SS StreamUpload
@@ -27586,7 +27595,7 @@ Some remotes allow files to be uploaded without knowing the file size in
 advance.
 This allows certain operations to work without spooling the file to
 local disk first, e.g.
-\f[C]rclone rcat\f[R].
+\f[V]rclone rcat\f[R].
 .SS MultithreadUpload
 .PP
 Some remotes allow transfers to the remote to be sent as chunks in
@@ -27600,14 +27609,14 @@ that allows others to access them, even if they don\[aq]t have an
 account on the particular cloud provider.
 .SS About
 .PP
-Rclone \f[C]about\f[R] prints quota information for a remote.
+Rclone \f[V]about\f[R] prints quota information for a remote.
 Typical output includes bytes used, free, quota and in trash.
 .PP
-If a remote lacks about capability \f[C]rclone about remote:\f[R]returns
+If a remote lacks about capability \f[V]rclone about remote:\f[R]returns
 an error.
 .PP
 Backends without about capability cannot determine free space for an
-rclone mount, or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount, or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See rclone about command (https://rclone.org/commands/rclone_about/)
@@ -27726,7 +27735,7 @@ Flags for general networking and HTTP stuff.
       --tpslimit float                     Limit HTTP transactions per second to this
       --tpslimit-burst int                 Max burst of transactions for --tpslimit (default 1)
       --use-cookies                        Enable session cookiejar
-      --user-agent string                  Set the user-agent to a specified string (default \[dq]rclone/v1.68.2\[dq])
+      --user-agent string                  Set the user-agent to a specified string (default \[dq]rclone/v1.68.2-beta.8331.25cf42493.feature/add-frostfs-support\[dq])
 \f[R]
 .fi
 .SS Performance
@@ -28163,6 +28172,21 @@ Backend-only flags (these can be set in the config file also).
       --filescom-password string                            The password used to authenticate with Files.com (obscured)
       --filescom-site string                                Your site subdomain (e.g. mysite) or custom domain (e.g. myfiles.customdomain.com)
       --filescom-username string                            The username used to authenticate with Files.com
+      --frostfs-address string                              Address of account
+      --frostfs-ape-cache-invalidation-duration Duration    APE cache invalidation duration (default 8s)
+      --frostfs-ape-cache-invalidation-timeout Duration     APE cache invalidation timeout (default 24s)
+      --frostfs-ape-chain-check-interval Duration           The interval for verifying that the APE chain is saved in FrostFS (default 500ms)
+      --frostfs-connection-timeout Duration                 FrostFS connection timeout (default 4s)
+      --frostfs-container-creation-policy string            Container creation policy for new containers (default \[dq]private\[dq])
+      --frostfs-description string                          Description of the remote
+      --frostfs-endpoint string                             Endpoints to connect to FrostFS node
+      --frostfs-password string                             Password to decrypt wallet
+      --frostfs-placement-policy string                     Placement policy for new containers (default \[dq]REP 3\[dq])
+      --frostfs-rebalance-interval Duration                 FrostFS rebalance connections interval (default 15s)
+      --frostfs-request-timeout Duration                    FrostFS request timeout (default 12s)
+      --frostfs-rpc-endpoint string                         Endpoint to connect to Neo rpc node
+      --frostfs-session-expiration int                      FrostFS session expiration epoch (default 4294967295)
+      --frostfs-wallet string                               Path to wallet
       --ftp-ask-password                                    Allow asking for FTP password when needed
       --ftp-close-timeout Duration                          Maximum time to wait for a response to close (default 1m0s)
       --ftp-concurrency int                                 Maximum number of FTP simultaneous connections, 0 for unlimited
@@ -28709,7 +28733,7 @@ files for use with \f[I]swarm stacks\f[R] across multiple cluster nodes.
 .PP
 Docker Volume
 Plugins (https://docs.docker.com/engine/extend/plugins_volume/) augment
-the default \f[C]local\f[R] volume driver included in Docker with
+the default \f[V]local\f[R] volume driver included in Docker with
 stateful volumes shared across containers and hosts.
 Unlike local volumes, your data will \f[I]not\f[R] be deleted when such
 volume is removed.
@@ -28748,7 +28772,7 @@ sudo mkdir -p /var/lib/docker-plugins/rclone/cache
 .fi
 .PP
 Install the managed rclone docker plugin for your architecture (here
-\f[C]amd64\f[R]):
+\f[V]amd64\f[R]):
 .IP
 .nf
 \f[C]
@@ -28766,13 +28790,13 @@ docker volume create firstvolume -d rclone -o type=sftp -o sftp-host=_hostname_
 .fi
 .PP
 Note that since all options are static, you don\[aq]t even have to run
-\f[C]rclone config\f[R] or create the \f[C]rclone.conf\f[R] file (but
-the \f[C]config\f[R] directory should still be present).
-In the simplest case you can use \f[C]localhost\f[R] as
+\f[V]rclone config\f[R] or create the \f[V]rclone.conf\f[R] file (but
+the \f[V]config\f[R] directory should still be present).
+In the simplest case you can use \f[V]localhost\f[R] as
 \f[I]hostname\f[R] and your SSH credentials as \f[I]username\f[R] and
 \f[I]password\f[R].
 You can also change the remote path to your home directory on the host,
-for example \f[C]-o path=/home/username\f[R].
+for example \f[V]-o path=/home/username\f[R].
 .PP
 Time to create a test container and mount the volume into it:
 .IP
@@ -28784,9 +28808,9 @@ docker run --rm -it -v firstvolume:/mnt --workdir /mnt ubuntu:latest bash
 .PP
 If all goes well, you will enter the new container and change right to
 the mounted SFTP remote.
-You can type \f[C]ls\f[R] to list the mounted directory or otherwise
+You can type \f[V]ls\f[R] to list the mounted directory or otherwise
 play with it.
-Type \f[C]exit\f[R] when you are done.
+Type \f[V]exit\f[R] when you are done.
 The container will stop but the volume will stay, ready to be reused.
 When it\[aq]s not needed anymore, remove it:
 .IP
@@ -28815,9 +28839,9 @@ Run rclone config (https://rclone.org/commands/rclone_config_create/) on
 graphical user interface.
 Create the Google Drive
 remote (https://rclone.org/drive/#standard-options).
-When done, transfer the resulting \f[C]rclone.conf\f[R] to the Swarm
+When done, transfer the resulting \f[V]rclone.conf\f[R] to the Swarm
 cluster and save as
-\f[C]/var/lib/docker-plugins/rclone/config/rclone.conf\f[R] on
+\f[V]/var/lib/docker-plugins/rclone/config/rclone.conf\f[R] on
 \f[I]every\f[R] node.
 By default this location is accessible only to the root user so you will
 need appropriate privileges.
@@ -28834,7 +28858,7 @@ token = {\[dq]access_token\[dq]:...}
 \f[R]
 .fi
 .PP
-Now create the file named \f[C]example.yml\f[R] with a swarm stack
+Now create the file named \f[V]example.yml\f[R] with a swarm stack
 description like this:
 .IP
 .nf
@@ -28865,9 +28889,9 @@ docker stack deploy example -c ./example.yml
 .fi
 .PP
 After a few seconds docker will spread the parsed stack description over
-cluster, create the \f[C]example_heimdall\f[R] service on port
+cluster, create the \f[V]example_heimdall\f[R] service on port
 \f[I]8080\f[R], run service containers on one or more cluster nodes and
-request the \f[C]example_configdata\f[R] volume from rclone plugins on
+request the \f[V]example_configdata\f[R] volume from rclone plugins on
 the node hosts.
 You can use the following commands to confirm results:
 .IP
@@ -28879,14 +28903,14 @@ docker volume ls
 \f[R]
 .fi
 .PP
-Point your browser to \f[C]http://cluster.host.address:8080\f[R] and
+Point your browser to \f[V]http://cluster.host.address:8080\f[R] and
 play with the service.
-Stop it with \f[C]docker stack remove example\f[R] when you are done.
-Note that the \f[C]example_configdata\f[R] volume(s) created on demand
+Stop it with \f[V]docker stack remove example\f[R] when you are done.
+Note that the \f[V]example_configdata\f[R] volume(s) created on demand
 at the cluster nodes will not be automatically removed together with the
 stack but stay for future reuse.
 You can remove them manually by invoking the
-\f[C]docker volume remove example_configdata\f[R] command on every node.
+\f[V]docker volume remove example_configdata\f[R] command on every node.
 .SS Creating Volumes via CLI
 .PP
 Volumes can be created with docker volume
@@ -28901,11 +28925,11 @@ docker volume create vol3 -d rclone -o type=storj -o path=heimdall -o storj-acce
 \f[R]
 .fi
 .PP
-Note the \f[C]-d rclone\f[R] flag that tells docker to request volume
+Note the \f[V]-d rclone\f[R] flag that tells docker to request volume
 from the rclone driver.
 This works even if you installed managed driver by its full name
-\f[C]rclone/docker-volume-rclone\f[R] because you provided the
-\f[C]--alias rclone\f[R] option.
+\f[V]rclone/docker-volume-rclone\f[R] because you provided the
+\f[V]--alias rclone\f[R] option.
 .PP
 Volumes can be inspected as follows:
 .IP
@@ -28917,26 +28941,26 @@ docker volume inspect vol1
 .fi
 .SS Volume Configuration
 .PP
-Rclone flags and volume options are set via the \f[C]-o\f[R] flag to the
-\f[C]docker volume create\f[R] command.
+Rclone flags and volume options are set via the \f[V]-o\f[R] flag to the
+\f[V]docker volume create\f[R] command.
 They include backend-specific parameters as well as mount and
 \f[I]VFS\f[R] options.
-Also there are a few special \f[C]-o\f[R] options: \f[C]remote\f[R],
-\f[C]fs\f[R], \f[C]type\f[R], \f[C]path\f[R], \f[C]mount-type\f[R] and
-\f[C]persist\f[R].
+Also there are a few special \f[V]-o\f[R] options: \f[V]remote\f[R],
+\f[V]fs\f[R], \f[V]type\f[R], \f[V]path\f[R], \f[V]mount-type\f[R] and
+\f[V]persist\f[R].
 .PP
-\f[C]remote\f[R] determines an existing remote name from the config
+\f[V]remote\f[R] determines an existing remote name from the config
 file, with trailing colon and optionally with a remote path.
 See the full syntax in the rclone
 documentation (https://rclone.org/docs/#syntax-of-remote-paths).
-This option can be aliased as \f[C]fs\f[R] to prevent confusion with the
+This option can be aliased as \f[V]fs\f[R] to prevent confusion with the
 \f[I]remote\f[R] parameter of such backends as \f[I]crypt\f[R] or
 \f[I]alias\f[R].
 .PP
-The \f[C]remote=:backend:dir/subdir\f[R] syntax can be used to create
+The \f[V]remote=:backend:dir/subdir\f[R] syntax can be used to create
 on-the-fly (config-less)
 remotes (https://rclone.org/docs/#backend-path-to-dir), while the
-\f[C]type\f[R] and \f[C]path\f[R] options provide a simpler alternative
+\f[V]type\f[R] and \f[V]path\f[R] options provide a simpler alternative
 for this.
 Using two split options
 .IP
@@ -28955,50 +28979,50 @@ is equivalent to the combined syntax
 .fi
 .PP
 but is arguably easier to parameterize in scripts.
-The \f[C]path\f[R] part is optional.
+The \f[V]path\f[R] part is optional.
 .PP
 Mount and VFS
 options (https://rclone.org/commands/rclone_serve_docker/#options) as
 well as backend parameters (https://rclone.org/flags/#backend-flags) are
-named like their twin command-line flags without the \f[C]--\f[R] CLI
+named like their twin command-line flags without the \f[V]--\f[R] CLI
 prefix.
 Optionally you can use underscores instead of dashes in option names.
-For example, \f[C]--vfs-cache-mode full\f[R] becomes
-\f[C]-o vfs-cache-mode=full\f[R] or \f[C]-o vfs_cache_mode=full\f[R].
-Boolean CLI flags without value will gain the \f[C]true\f[R] value, e.g.
-\f[C]--allow-other\f[R] becomes \f[C]-o allow-other=true\f[R] or
-\f[C]-o allow_other=true\f[R].
+For example, \f[V]--vfs-cache-mode full\f[R] becomes
+\f[V]-o vfs-cache-mode=full\f[R] or \f[V]-o vfs_cache_mode=full\f[R].
+Boolean CLI flags without value will gain the \f[V]true\f[R] value, e.g.
+\f[V]--allow-other\f[R] becomes \f[V]-o allow-other=true\f[R] or
+\f[V]-o allow_other=true\f[R].
 .PP
 Please note that you can provide parameters only for the backend
-immediately referenced by the backend type of mounted \f[C]remote\f[R].
+immediately referenced by the backend type of mounted \f[V]remote\f[R].
 If this is a wrapping backend like \f[I]alias, chunker or crypt\f[R],
 you cannot provide options for the referred to remote or backend.
 This limitation is imposed by the rclone connection string parser.
-The only workaround is to feed plugin with \f[C]rclone.conf\f[R] or
+The only workaround is to feed plugin with \f[V]rclone.conf\f[R] or
 configure plugin arguments (see below).
 .SS Special Volume Options
 .PP
-\f[C]mount-type\f[R] determines the mount method and in general can be
-one of: \f[C]mount\f[R], \f[C]cmount\f[R], or \f[C]mount2\f[R].
-This can be aliased as \f[C]mount_type\f[R].
+\f[V]mount-type\f[R] determines the mount method and in general can be
+one of: \f[V]mount\f[R], \f[V]cmount\f[R], or \f[V]mount2\f[R].
+This can be aliased as \f[V]mount_type\f[R].
 It should be noted that the managed rclone docker plugin currently does
-not support the \f[C]cmount\f[R] method and \f[C]mount2\f[R] is rarely
+not support the \f[V]cmount\f[R] method and \f[V]mount2\f[R] is rarely
 needed.
 This option defaults to the first found method, which is usually
-\f[C]mount\f[R] so you generally won\[aq]t need it.
+\f[V]mount\f[R] so you generally won\[aq]t need it.
 .PP
-\f[C]persist\f[R] is a reserved boolean (true/false) option.
+\f[V]persist\f[R] is a reserved boolean (true/false) option.
 In future it will allow to persist on-the-fly remotes in the plugin
-\f[C]rclone.conf\f[R] file.
+\f[V]rclone.conf\f[R] file.
 .SS Connection Strings
 .PP
-The \f[C]remote\f[R] value can be extended with connection
+The \f[V]remote\f[R] value can be extended with connection
 strings (https://rclone.org/docs/#connection-strings) as an alternative
 way to supply backend parameters.
-This is equivalent to the \f[C]-o\f[R] backend options with one
+This is equivalent to the \f[V]-o\f[R] backend options with one
 \f[I]syntactic difference\f[R].
 Inside connection string the backend prefix must be dropped from
-parameter names but in the \f[C]-o param=value\f[R] array it must be
+parameter names but in the \f[V]-o param=value\f[R] array it must be
 present.
 For instance, compare the following option array
 .IP
@@ -29016,11 +29040,11 @@ with equivalent connection string:
 \f[R]
 .fi
 .PP
-This difference exists because flag options \f[C]-o key=val\f[R] include
+This difference exists because flag options \f[V]-o key=val\f[R] include
 not only backend parameters but also mount/VFS flags and possibly other
 settings.
-Also it allows to discriminate the \f[C]remote\f[R] option from the
-\f[C]crypt-remote\f[R] (or similarly named backend parameters) and
+Also it allows to discriminate the \f[V]remote\f[R] option from the
+\f[V]crypt-remote\f[R] (or similarly named backend parameters) and
 arguably simplifies scripting due to clearer value substitution.
 .SS Using with Swarm or Compose
 .PP
@@ -29037,11 +29061,11 @@ They are mostly similar, differences are explained in the docker
 documentation (https://docs.docker.com/compose/compose-file/compose-versioning/#upgrading).
 .PP
 Volumes are described by the children of the top-level
-\f[C]volumes:\f[R] node.
+\f[V]volumes:\f[R] node.
 Each of them should be named after its volume and have at least two
-elements, the self-explanatory \f[C]driver: rclone\f[R] value and the
-\f[C]driver_opts:\f[R] structure playing the same role as
-\f[C]-o key=val\f[R] CLI flags:
+elements, the self-explanatory \f[V]driver: rclone\f[R] value and the
+\f[V]driver_opts:\f[R] structure playing the same role as
+\f[V]-o key=val\f[R] CLI flags:
 .IP
 .nf
 \f[C]
@@ -29057,17 +29081,17 @@ volumes:
 \f[R]
 .fi
 .PP
-Notice a few important details: - YAML prefers \f[C]_\f[R] in option
-names instead of \f[C]-\f[R].
+Notice a few important details: - YAML prefers \f[V]_\f[R] in option
+names instead of \f[V]-\f[R].
 - YAML treats single and double quotes interchangeably.
 Simple strings and integers can be left unquoted.
-- Boolean values must be quoted like \f[C]\[aq]true\[aq]\f[R] or
-\f[C]\[dq]false\[dq]\f[R] because these two words are reserved by YAML.
-- The filesystem string is keyed with \f[C]remote\f[R] (or with
-\f[C]fs\f[R]).
+- Boolean values must be quoted like \f[V]\[aq]true\[aq]\f[R] or
+\f[V]\[dq]false\[dq]\f[R] because these two words are reserved by YAML.
+- The filesystem string is keyed with \f[V]remote\f[R] (or with
+\f[V]fs\f[R]).
 Normally you can omit quotes here, but if the string ends with colon,
 you \f[B]must\f[R] quote it like
-\f[C]remote: \[dq]storage_box:\[dq]\f[R].
+\f[V]remote: \[dq]storage_box:\[dq]\f[R].
 - YAML is picky about surrounding braces in values as this is in fact
 another syntax for key/value
 mappings (http://yaml.org/spec/1.2/spec.html#id2790832).
@@ -29088,10 +29112,10 @@ can be installed.
 Note that plugin will \f[B]not\f[R] create them automatically.
 By default they must exist on host at the following locations (though
 you can tweak the paths): -
-\f[C]/var/lib/docker-plugins/rclone/config\f[R] is reserved for the
-\f[C]rclone.conf\f[R] config file and \f[B]must\f[R] exist even if
+\f[V]/var/lib/docker-plugins/rclone/config\f[R] is reserved for the
+\f[V]rclone.conf\f[R] config file and \f[B]must\f[R] exist even if
 it\[aq]s empty and the config file is not present.
-- \f[C]/var/lib/docker-plugins/rclone/cache\f[R] holds the plugin state
+- \f[V]/var/lib/docker-plugins/rclone/cache\f[R] holds the plugin state
 file as well as optional VFS caches.
 .PP
 You can install managed
@@ -29104,41 +29128,41 @@ docker plugin install rclone/docker-volume-rclone:amd64 --grant-all-permissions
 \f[R]
 .fi
 .PP
-The \f[C]:amd64\f[R] part of the image specification after colon is
+The \f[V]:amd64\f[R] part of the image specification after colon is
 called a \f[I]tag\f[R].
 Usually you will want to install the latest plugin for your
 architecture.
-In this case the tag will just name it, like \f[C]amd64\f[R] above.
+In this case the tag will just name it, like \f[V]amd64\f[R] above.
 The following plugin architectures are currently available: -
-\f[C]amd64\f[R] - \f[C]arm64\f[R] - \f[C]arm-v7\f[R]
+\f[V]amd64\f[R] - \f[V]arm64\f[R] - \f[V]arm-v7\f[R]
 .PP
 Sometimes you might want a concrete plugin version, not the latest one.
 Then you should use image tag in the form
-\f[C]:ARCHITECTURE-VERSION\f[R].
-For example, to install plugin version \f[C]v1.56.2\f[R] on architecture
-\f[C]arm64\f[R] you will use tag \f[C]arm64-1.56.2\f[R] (note the
-removed \f[C]v\f[R]) so the full image specification becomes
-\f[C]rclone/docker-volume-rclone:arm64-1.56.2\f[R].
+\f[V]:ARCHITECTURE-VERSION\f[R].
+For example, to install plugin version \f[V]v1.56.2\f[R] on architecture
+\f[V]arm64\f[R] you will use tag \f[V]arm64-1.56.2\f[R] (note the
+removed \f[V]v\f[R]) so the full image specification becomes
+\f[V]rclone/docker-volume-rclone:arm64-1.56.2\f[R].
 .PP
-We also provide the \f[C]latest\f[R] plugin tag, but since docker does
+We also provide the \f[V]latest\f[R] plugin tag, but since docker does
 not support multi-architecture plugins as of the time of this writing,
-this tag is currently an \f[B]alias for \f[CB]amd64\f[B]\f[R].
-By convention the \f[C]latest\f[R] tag is the default one and can be
-omitted, thus both \f[C]rclone/docker-volume-rclone:latest\f[R] and just
-\f[C]rclone/docker-volume-rclone\f[R] will refer to the latest plugin
-release for the \f[C]amd64\f[R] platform.
+this tag is currently an \f[B]alias for \f[VB]amd64\f[B]\f[R].
+By convention the \f[V]latest\f[R] tag is the default one and can be
+omitted, thus both \f[V]rclone/docker-volume-rclone:latest\f[R] and just
+\f[V]rclone/docker-volume-rclone\f[R] will refer to the latest plugin
+release for the \f[V]amd64\f[R] platform.
 .PP
-Also the \f[C]amd64\f[R] part can be omitted from the versioned rclone
+Also the \f[V]amd64\f[R] part can be omitted from the versioned rclone
 plugin tags.
 For example, rclone image reference
-\f[C]rclone/docker-volume-rclone:amd64-1.56.2\f[R] can be abbreviated as
-\f[C]rclone/docker-volume-rclone:1.56.2\f[R] for convenience.
+\f[V]rclone/docker-volume-rclone:amd64-1.56.2\f[R] can be abbreviated as
+\f[V]rclone/docker-volume-rclone:1.56.2\f[R] for convenience.
 However, for non-intel architectures you still have to use the full tag
-as \f[C]amd64\f[R] or \f[C]latest\f[R] will fail to start.
+as \f[V]amd64\f[R] or \f[V]latest\f[R] will fail to start.
 .PP
 Managed plugin is in fact a special container running in a namespace
 separate from normal docker containers.
-Inside it runs the \f[C]rclone serve docker\f[R] command.
+Inside it runs the \f[V]rclone serve docker\f[R] command.
 The config and cache directories are bind-mounted into the container at
 start.
 The docker daemon connects to a unix socket created by the command
@@ -29164,14 +29188,14 @@ remove all active volumes connected with it as well as containers and
 swarm services that use them.
 This is rather tedious so please carefully plan in advance.
 .PP
-You can tweak the following settings: \f[C]args\f[R], \f[C]config\f[R],
-\f[C]cache\f[R], \f[C]HTTP_PROXY\f[R], \f[C]HTTPS_PROXY\f[R],
-\f[C]NO_PROXY\f[R] and \f[C]RCLONE_VERBOSE\f[R].
+You can tweak the following settings: \f[V]args\f[R], \f[V]config\f[R],
+\f[V]cache\f[R], \f[V]HTTP_PROXY\f[R], \f[V]HTTPS_PROXY\f[R],
+\f[V]NO_PROXY\f[R] and \f[V]RCLONE_VERBOSE\f[R].
 It\[aq]s \f[I]your\f[R] task to keep plugin settings in sync across
 swarm cluster nodes.
 .PP
-\f[C]args\f[R] sets command-line arguments for the
-\f[C]rclone serve docker\f[R] command (\f[I]none\f[R] by default).
+\f[V]args\f[R] sets command-line arguments for the
+\f[V]rclone serve docker\f[R] command (\f[I]none\f[R] by default).
 Arguments should be separated by space so you will normally want to put
 them in quotes on the docker plugin
 set (https://docs.docker.com/engine/reference/commandline/plugin_set/)
@@ -29183,32 +29207,32 @@ including backend parameters that will be used as defaults for volume
 creation.
 Note that plugin will fail (due to this docker
 bug (https://github.com/moby/moby/blob/v20.10.7/plugin/v2/plugin.go#L195))
-if the \f[C]args\f[R] value is empty.
+if the \f[V]args\f[R] value is empty.
 Use e.g.
-\f[C]args=\[dq]-v\[dq]\f[R] as a workaround.
+\f[V]args=\[dq]-v\[dq]\f[R] as a workaround.
 .PP
-\f[C]config=/host/dir\f[R] sets alternative host location for the config
+\f[V]config=/host/dir\f[R] sets alternative host location for the config
 directory.
-Plugin will look for \f[C]rclone.conf\f[R] here.
+Plugin will look for \f[V]rclone.conf\f[R] here.
 It\[aq]s not an error if the config file is not present but the
 directory must exist.
 Please note that plugin can periodically rewrite the config file, for
 example when it renews storage access tokens.
 Keep this in mind and try to avoid races between the plugin and other
 instances of rclone on the host that might try to change the config
-simultaneously resulting in corrupted \f[C]rclone.conf\f[R].
+simultaneously resulting in corrupted \f[V]rclone.conf\f[R].
 You can also put stuff like private key files for SFTP remotes in this
 directory.
 Just note that it\[aq]s bind-mounted inside the plugin container at the
-predefined path \f[C]/data/config\f[R].
-For example, if your key file is named \f[C]sftp-box1.key\f[R] on the
+predefined path \f[V]/data/config\f[R].
+For example, if your key file is named \f[V]sftp-box1.key\f[R] on the
 host, the corresponding volume config option should read
-\f[C]-o sftp-key-file=/data/config/sftp-box1.key\f[R].
+\f[V]-o sftp-key-file=/data/config/sftp-box1.key\f[R].
 .PP
-\f[C]cache=/host/dir\f[R] sets alternative host location for the
+\f[V]cache=/host/dir\f[R] sets alternative host location for the
 \f[I]cache\f[R] directory.
 The plugin will keep VFS caches here.
-Also it will create and maintain the \f[C]docker-plugin.state\f[R] file
+Also it will create and maintain the \f[V]docker-plugin.state\f[R] file
 in this directory.
 When the plugin is restarted or reinstalled, it will look in this file
 to recreate any volumes that existed previously.
@@ -29218,16 +29242,16 @@ Usually this is not a problem as the docker daemon normally will restart
 affected user containers after failures, daemon restarts or host
 reboots.
 .PP
-\f[C]RCLONE_VERBOSE\f[R] sets plugin verbosity from \f[C]0\f[R] (errors
-only, by default) to \f[C]2\f[R] (debugging).
-Verbosity can be also tweaked via \f[C]args=\[dq]-v [-v] ...\[dq]\f[R].
+\f[V]RCLONE_VERBOSE\f[R] sets plugin verbosity from \f[V]0\f[R] (errors
+only, by default) to \f[V]2\f[R] (debugging).
+Verbosity can be also tweaked via \f[V]args=\[dq]-v [-v] ...\[dq]\f[R].
 Since arguments are more generic, you will rarely need this setting.
 The plugin output by default feeds the docker daemon log on local host.
 Log entries are reflected as \f[I]errors\f[R] in the docker log but
 retain their actual level assigned by rclone in the encapsulated message
 string.
 .PP
-\f[C]HTTP_PROXY\f[R], \f[C]HTTPS_PROXY\f[R], \f[C]NO_PROXY\f[R]
+\f[V]HTTP_PROXY\f[R], \f[V]HTTPS_PROXY\f[R], \f[V]NO_PROXY\f[R]
 customize the plugin proxy settings.
 .PP
 You can set custom plugin options right when you install it, \f[I]in one
@@ -29270,7 +29294,7 @@ Please use managed mode on these systems.
 Proceed further only if you are on Linux.
 .PP
 First, install rclone (https://rclone.org/install/).
-You can just run it (type \f[C]rclone serve docker\f[R] and hit enter)
+You can just run it (type \f[V]rclone serve docker\f[R] and hit enter)
 for the test.
 .PP
 Install \f[I]FUSE\f[R]:
@@ -29286,7 +29310,7 @@ docker-volume-rclone.service (https://raw.githubusercontent.com/rclone/rclone/ma
 and
 docker-volume-rclone.socket (https://raw.githubusercontent.com/rclone/rclone/master/contrib/docker-plugin/systemd/docker-volume-rclone.socket).
 .PP
-Put them to the \f[C]/etc/systemd/system/\f[R] directory:
+Put them to the \f[V]/etc/systemd/system/\f[R] directory:
 .IP
 .nf
 \f[C]
@@ -29296,7 +29320,7 @@ cp docker-volume-plugin.socket  /etc/systemd/system/
 .fi
 .PP
 Please note that all commands in this section must be run as
-\f[I]root\f[R] but we omit \f[C]sudo\f[R] prefix for brevity.
+\f[I]root\f[R] but we omit \f[V]sudo\f[R] prefix for brevity.
 Now create directories required by the service:
 .IP
 .nf
@@ -29319,13 +29343,13 @@ systemctl restart docker
 \f[R]
 .fi
 .PP
-Or run the service directly: - run \f[C]systemctl daemon-reload\f[R] to
+Or run the service directly: - run \f[V]systemctl daemon-reload\f[R] to
 let systemd pick up new config - run
-\f[C]systemctl enable docker-volume-rclone.service\f[R] to make the new
+\f[V]systemctl enable docker-volume-rclone.service\f[R] to make the new
 service start automatically when you power on your machine.
-- run \f[C]systemctl start docker-volume-rclone.service\f[R] to start
+- run \f[V]systemctl start docker-volume-rclone.service\f[R] to start
 the service now.
-- run \f[C]systemctl restart docker\f[R] to restart docker daemon and
+- run \f[V]systemctl restart docker\f[R] to restart docker daemon and
 let it detect the new plugin socket.
 Note that this step is not needed in managed mode where docker knows
 about plugin state changes.
@@ -29345,9 +29369,9 @@ docker plugin inspect rclone
 .fi
 .PP
 Note that docker (including latest 20.10.7) will not show actual values
-of \f[C]args\f[R], just the defaults.
+of \f[V]args\f[R], just the defaults.
 .PP
-Use \f[C]journalctl --unit docker\f[R] to see managed plugin output as
+Use \f[V]journalctl --unit docker\f[R] to see managed plugin output as
 part of the docker daemon log.
 Note that docker reflects plugin lines as \f[I]errors\f[R] but their
 actual level can be seen from encapsulated message string.
@@ -29363,7 +29387,7 @@ sudo runc --root /run/docker/runtime-runc/plugins.moby exec $PLUGID rclone versi
 \f[R]
 .fi
 .PP
-You can even use \f[C]runc\f[R] to run shell inside the plugin
+You can even use \f[V]runc\f[R] to run shell inside the plugin
 container:
 .IP
 .nf
@@ -29388,8 +29412,8 @@ though this is rarely needed.
 Finally I\[aq]d like to mention a \f[I]caveat with updating volume
 settings\f[R].
 Docker CLI does not have a dedicated command like
-\f[C]docker volume update\f[R].
-It may be tempting to invoke \f[C]docker volume create\f[R] with updated
+\f[V]docker volume update\f[R].
+It may be tempting to invoke \f[V]docker volume create\f[R] with updated
 options on existing volume, but there is a gotcha.
 The command will do nothing, it won\[aq]t even return an error.
 I hope that docker maintainers will fix this some day.
@@ -29416,7 +29440,7 @@ If docker refuses to remove the volume, you should find containers or
 swarm services that use it and stop them first.
 .SS Bisync
 .PP
-\f[C]bisync\f[R] is \f[B]in beta\f[R] and is considered an \f[B]advanced
+\f[V]bisync\f[R] is \f[B]in beta\f[R] and is considered an \f[B]advanced
 command\f[R], so use with care.
 Make sure you have read and understood the entire
 manual (https://rclone.org/bisync) (especially the Limitations section)
@@ -29427,16 +29451,16 @@ Questions can be asked in the Rclone Forum (https://forum.rclone.org/).
 Install rclone (https://rclone.org/install/) and setup your remotes.
 .IP \[bu] 2
 Bisync will create its working directory at
-\f[C]\[ti]/.cache/rclone/bisync\f[R] on Linux,
-\f[C]/Users/yourusername/Library/Caches/rclone/bisync\f[R] on Mac, or
-\f[C]C:\[rs]Users\[rs]MyLogin\[rs]AppData\[rs]Local\[rs]rclone\[rs]bisync\f[R]
+\f[V]\[ti]/.cache/rclone/bisync\f[R] on Linux,
+\f[V]/Users/yourusername/Library/Caches/rclone/bisync\f[R] on Mac, or
+\f[V]C:\[rs]Users\[rs]MyLogin\[rs]AppData\[rs]Local\[rs]rclone\[rs]bisync\f[R]
 on Windows.
 Make sure that this location is writable.
 .IP \[bu] 2
-Run bisync with the \f[C]--resync\f[R] flag, specifying the paths to the
+Run bisync with the \f[V]--resync\f[R] flag, specifying the paths to the
 local and remote sync directory roots.
 .IP \[bu] 2
-For successive sync runs, leave off the \f[C]--resync\f[R] flag.
+For successive sync runs, leave off the \f[V]--resync\f[R] flag.
 (\f[B]Important!\f[R])
 .IP \[bu] 2
 Consider using a filters file for excluding unnecessary files and
@@ -29456,8 +29480,8 @@ rclone bisync remote1:path1 remote2:path2 --create-empty-src-dirs --compare size
 \f[R]
 .fi
 .PP
-If all looks good, run it again without \f[C]--dry-run\f[R].
-After that, remove \f[C]--resync\f[R] as well.
+If all looks good, run it again without \f[V]--dry-run\f[R].
+After that, remove \f[V]--resync\f[R] as well.
 .PP
 Here is a typical run log (with timestamps removed for clarity):
 .IP
@@ -29554,34 +29578,34 @@ Optional Flags:
 .PP
 Arbitrary rclone flags may be specified on the bisync command
 line (https://rclone.org/commands/rclone_bisync/), for example
-\f[C]rclone bisync ./testdir/path1/ gdrive:testdir/path2/ --drive-skip-gdocs -v -v --timeout 10s\f[R]
+\f[V]rclone bisync ./testdir/path1/ gdrive:testdir/path2/ --drive-skip-gdocs -v -v --timeout 10s\f[R]
 Note that interactions of various rclone flags with bisync process flow
 has not been fully tested yet.
 .SS Paths
 .PP
 Path1 and Path2 arguments may be references to any mix of local
 directory paths (absolute or relative), UNC paths
-(\f[C]//server/share/path\f[R]), Windows drive paths (with a drive
-letter and \f[C]:\f[R]) or configured
+(\f[V]//server/share/path\f[R]), Windows drive paths (with a drive
+letter and \f[V]:\f[R]) or configured
 remotes (https://rclone.org/docs/#syntax-of-remote-paths) with optional
 subdirectory paths.
-Cloud references are distinguished by having a \f[C]:\f[R] in the
+Cloud references are distinguished by having a \f[V]:\f[R] in the
 argument (see Windows support below).
 .PP
 Path1 and Path2 are treated equally, in that neither has priority for
-file changes (except during \f[C]--resync\f[R]), and access efficiency
+file changes (except during \f[V]--resync\f[R]), and access efficiency
 does not change whether a remote is on Path1 or Path2.
 .PP
 The listings in bisync working directory (default:
-\f[C]\[ti]/.cache/rclone/bisync\f[R]) are named based on the Path1 and
+\f[V]\[ti]/.cache/rclone/bisync\f[R]) are named based on the Path1 and
 Path2 arguments so that separate syncs to individual directories within
 the tree may be set up, e.g.:
-\f[C]path_to_local_tree..dropbox_subdir.lst\f[R].
+\f[V]path_to_local_tree..dropbox_subdir.lst\f[R].
 .PP
 Any empty directories after the sync on both the Path1 and Path2
 filesystems are not deleted by default, unless
-\f[C]--create-empty-src-dirs\f[R] is specified.
-If the \f[C]--remove-empty-dirs\f[R] flag is specified, then both paths
+\f[V]--create-empty-src-dirs\f[R] is specified.
+If the \f[V]--remove-empty-dirs\f[R] flag is specified, then both paths
 will have ALL empty directories purged as the last step in the process.
 .SS Command-line flags
 .SS --resync
@@ -29591,8 +29615,8 @@ matching superset of all files.
 By default, Path2 files that do not exist in Path1 will be copied to
 Path1, and the process will then copy the Path1 tree to Path2.
 .PP
-The \f[C]--resync\f[R] sequence is roughly equivalent to the following
-(but see \f[C]--resync-mode\f[R] for other options):
+The \f[V]--resync\f[R] sequence is roughly equivalent to the following
+(but see \f[V]--resync-mode\f[R] for other options):
 .IP
 .nf
 \f[C]
@@ -29606,13 +29630,14 @@ bisync will fail.
 This is required for safety - that bisync can verify that both paths are
 valid.
 .PP
-When using \f[C]--resync\f[R], a newer version of a file on the Path2
+When using \f[V]--resync\f[R], a newer version of a file on the Path2
 filesystem will (by default) be overwritten by the Path1 filesystem
 version.
 (Note that this is NOT entirely
 symmetrical (https://github.com/rclone/rclone/issues/5681#issuecomment-938761815),
 and more symmetrical options can be specified with the
-\f[C]--resync-mode\f[R] flag.) Carefully evaluate deltas using
+\f[V]--resync-mode\f[R] flag.)
+Carefully evaluate deltas using
 --dry-run (https://rclone.org/flags/#non-backend-flags).
 .PP
 For a resync run, one of the paths may be empty (no files in the path
@@ -29622,28 +29647,28 @@ non-resync run will fail.
 .PP
 For a non-resync run, either path being empty (no files in the tree)
 fails with
-\f[C]Empty current PathN listing. Cannot sync to an empty directory: X.pathN.lst\f[R]
+\f[V]Empty current PathN listing. Cannot sync to an empty directory: X.pathN.lst\f[R]
 This is a safety check that an unexpected empty path does not result in
 deleting \f[B]everything\f[R] in the other path.
 .PP
-Note that \f[C]--resync\f[R] implies \f[C]--resync-mode path1\f[R]
-unless a different \f[C]--resync-mode\f[R] is explicitly specified.
-It is not necessary to use both the \f[C]--resync\f[R] and
-\f[C]--resync-mode\f[R] flags -- either one is sufficient without the
+Note that \f[V]--resync\f[R] implies \f[V]--resync-mode path1\f[R]
+unless a different \f[V]--resync-mode\f[R] is explicitly specified.
+It is not necessary to use both the \f[V]--resync\f[R] and
+\f[V]--resync-mode\f[R] flags -- either one is sufficient without the
 other.
 .PP
-\f[B]Note:\f[R] \f[C]--resync\f[R] (including \f[C]--resync-mode\f[R])
+\f[B]Note:\f[R] \f[V]--resync\f[R] (including \f[V]--resync-mode\f[R])
 should only be used under three specific (rare) circumstances: 1.
 It is your \f[I]first\f[R] bisync run (between these two paths) 2.
 You\[aq]ve just made changes to your bisync settings (such as editing
-the contents of your \f[C]--filters-file\f[R]) 3.
+the contents of your \f[V]--filters-file\f[R]) 3.
 There was an error on the prior run, and as a result, bisync now
-requires \f[C]--resync\f[R] to recover
+requires \f[V]--resync\f[R] to recover
 .PP
-The rest of the time, you should \f[I]omit\f[R] \f[C]--resync\f[R].
-The reason is because \f[C]--resync\f[R] will only \f[I]copy\f[R] (not
+The rest of the time, you should \f[I]omit\f[R] \f[V]--resync\f[R].
+The reason is because \f[V]--resync\f[R] will only \f[I]copy\f[R] (not
 \f[I]sync\f[R]) each side to the other.
-Therefore, if you included \f[C]--resync\f[R] for every bisync run, it
+Therefore, if you included \f[V]--resync\f[R] for every bisync run, it
 would never be possible to delete a file -- the deleted file would
 always keep reappearing at the end of every run (because it\[aq]s being
 copied from the other side where it still exists).
@@ -29651,9 +29676,9 @@ Similarly, renaming a file would always result in a duplicate copy (both
 old and new name) on both sides.
 .PP
 If you find that frequent interruptions from #3 are an issue, rather
-than automatically running \f[C]--resync\f[R], the recommended
-alternative is to use the \f[C]--resilient\f[R], \f[C]--recover\f[R],
-and \f[C]--conflict-resolve\f[R] flags, (along with Graceful Shutdown
+than automatically running \f[V]--resync\f[R], the recommended
+alternative is to use the \f[V]--resilient\f[R], \f[V]--recover\f[R],
+and \f[V]--conflict-resolve\f[R] flags, (along with Graceful Shutdown
 mode, when needed) for a very robust \[dq]set-it-and-forget-it\[dq]
 bisync setup that can automatically bounce back from almost any
 interruption it might encounter.
@@ -29667,146 +29692,149 @@ Consider adding something like the following:
 .SS --resync-mode CHOICE
 .PP
 In the event that a file differs on both sides during a
-\f[C]--resync\f[R], \f[C]--resync-mode\f[R] controls which version will
+\f[V]--resync\f[R], \f[V]--resync-mode\f[R] controls which version will
 overwrite the other.
-The supported options are similar to \f[C]--conflict-resolve\f[R].
+The supported options are similar to \f[V]--conflict-resolve\f[R].
 For all of the following options, the version that is kept is referred
 to as the \[dq]winner\[dq], and the version that is overwritten
 (deleted) is referred to as the \[dq]loser\[dq].
 The options are named after the \[dq]winner\[dq]:
 .IP \[bu] 2
-\f[C]path1\f[R] - (the default) - the version from Path1 is
-unconditionally considered the winner (regardless of \f[C]modtime\f[R]
-and \f[C]size\f[R], if any).
+\f[V]path1\f[R] - (the default) - the version from Path1 is
+unconditionally considered the winner (regardless of \f[V]modtime\f[R]
+and \f[V]size\f[R], if any).
 This can be useful if one side is more trusted or up-to-date than the
-other, at the time of the \f[C]--resync\f[R].
+other, at the time of the \f[V]--resync\f[R].
 .IP \[bu] 2
-\f[C]path2\f[R] - same as \f[C]path1\f[R], except the path2 version is
+\f[V]path2\f[R] - same as \f[V]path1\f[R], except the path2 version is
 considered the winner.
 .IP \[bu] 2
-\f[C]newer\f[R] - the newer file (by \f[C]modtime\f[R]) is considered
+\f[V]newer\f[R] - the newer file (by \f[V]modtime\f[R]) is considered
 the winner, regardless of which side it came from.
 This may result in having a mix of some winners from Path1, and some
 winners from Path2.
 (The implementation is analogous to running
-\f[C]rclone copy --update\f[R] in both directions.)
+\f[V]rclone copy --update\f[R] in both directions.)
 .IP \[bu] 2
-\f[C]older\f[R] - same as \f[C]newer\f[R], except the older file is
+\f[V]older\f[R] - same as \f[V]newer\f[R], except the older file is
 considered the winner, and the newer file is considered the loser.
 .IP \[bu] 2
-\f[C]larger\f[R] - the larger file (by \f[C]size\f[R]) is considered the
-winner (regardless of \f[C]modtime\f[R], if any).
-This can be a useful option for remotes without \f[C]modtime\f[R]
+\f[V]larger\f[R] - the larger file (by \f[V]size\f[R]) is considered the
+winner (regardless of \f[V]modtime\f[R], if any).
+This can be a useful option for remotes without \f[V]modtime\f[R]
 support, or with the kinds of files (such as logs) that tend to grow but
 not shrink, over time.
 .IP \[bu] 2
-\f[C]smaller\f[R] - the smaller file (by \f[C]size\f[R]) is considered
-the winner (regardless of \f[C]modtime\f[R], if any).
+\f[V]smaller\f[R] - the smaller file (by \f[V]size\f[R]) is considered
+the winner (regardless of \f[V]modtime\f[R], if any).
 .PP
 For all of the above options, note the following: - If either of the
 underlying remotes lacks support for the chosen method, it will be
-ignored and will fall back to the default of \f[C]path1\f[R].
-(For example, if \f[C]--resync-mode newer\f[R] is set, but one of the
-paths uses a remote that doesn\[aq]t support \f[C]modtime\f[R].) - If a
-winner can\[aq]t be determined because the chosen method\[aq]s attribute
-is missing or equal, it will be ignored, and bisync will instead try to
-determine whether the files differ by looking at the other
-\f[C]--compare\f[R] methods in effect.
-(For example, if \f[C]--resync-mode newer\f[R] is set, but the Path1 and
-Path2 modtimes are identical, bisync will compare the sizes.) If bisync
-concludes that they differ, preference is given to whichever is the
-\[dq]source\[dq] at that moment.
+ignored and will fall back to the default of \f[V]path1\f[R].
+(For example, if \f[V]--resync-mode newer\f[R] is set, but one of the
+paths uses a remote that doesn\[aq]t support \f[V]modtime\f[R].)
+- If a winner can\[aq]t be determined because the chosen method\[aq]s
+attribute is missing or equal, it will be ignored, and bisync will
+instead try to determine whether the files differ by looking at the
+other \f[V]--compare\f[R] methods in effect.
+(For example, if \f[V]--resync-mode newer\f[R] is set, but the Path1 and
+Path2 modtimes are identical, bisync will compare the sizes.)
+If bisync concludes that they differ, preference is given to whichever
+is the \[dq]source\[dq] at that moment.
 (In practice, this gives a slight advantage to Path2, as the 2to1 copy
-comes before the 1to2 copy.) If the files \f[I]do not\f[R] differ,
-nothing is copied (as both sides are already correct).
+comes before the 1to2 copy.)
+If the files \f[I]do not\f[R] differ, nothing is copied (as both sides
+are already correct).
 - These options apply only to files that exist on both sides (with the
 same name and relative path).
 Files that exist \f[I]only\f[R] on one side and not the other are
-\f[I]always\f[R] copied to the other, during \f[C]--resync\f[R] (this is
+\f[I]always\f[R] copied to the other, during \f[V]--resync\f[R] (this is
 one of the main differences between resync and non-resync runs.).
-- \f[C]--conflict-resolve\f[R], \f[C]--conflict-loser\f[R], and
-\f[C]--conflict-suffix\f[R] do not apply during \f[C]--resync\f[R], and
-unlike these flags, nothing is renamed during \f[C]--resync\f[R].
-When a file differs on both sides during \f[C]--resync\f[R], one version
-always overwrites the other (much like in \f[C]rclone copy\f[R].)
-(Consider using \f[C]--backup-dir\f[R] to retain a backup of the losing
-version.) - Unlike for \f[C]--conflict-resolve\f[R],
-\f[C]--resync-mode none\f[R] is not a valid option (or rather, it will
-be interpreted as \[dq]no resync\[dq], unless \f[C]--resync\f[R] has
-also been specified, in which case it will be ignored.) - Winners and
-losers are decided at the individual file-level only (there is not
-currently an option to pick an entire winning directory atomically,
-although the \f[C]path1\f[R] and \f[C]path2\f[R] options typically
-produce a similar result.) - To maintain backward-compatibility, the
-\f[C]--resync\f[R] flag implies \f[C]--resync-mode path1\f[R] unless a
-different \f[C]--resync-mode\f[R] is explicitly specified.
-Similarly, all \f[C]--resync-mode\f[R] options (except \f[C]none\f[R])
-imply \f[C]--resync\f[R], so it is not necessary to use both the
-\f[C]--resync\f[R] and \f[C]--resync-mode\f[R] flags simultaneously --
+- \f[V]--conflict-resolve\f[R], \f[V]--conflict-loser\f[R], and
+\f[V]--conflict-suffix\f[R] do not apply during \f[V]--resync\f[R], and
+unlike these flags, nothing is renamed during \f[V]--resync\f[R].
+When a file differs on both sides during \f[V]--resync\f[R], one version
+always overwrites the other (much like in \f[V]rclone copy\f[R].)
+(Consider using \f[V]--backup-dir\f[R] to retain a backup of the losing
+version.)
+- Unlike for \f[V]--conflict-resolve\f[R], \f[V]--resync-mode none\f[R]
+is not a valid option (or rather, it will be interpreted as \[dq]no
+resync\[dq], unless \f[V]--resync\f[R] has also been specified, in which
+case it will be ignored.)
+- Winners and losers are decided at the individual file-level only
+(there is not currently an option to pick an entire winning directory
+atomically, although the \f[V]path1\f[R] and \f[V]path2\f[R] options
+typically produce a similar result.)
+- To maintain backward-compatibility, the \f[V]--resync\f[R] flag
+implies \f[V]--resync-mode path1\f[R] unless a different
+\f[V]--resync-mode\f[R] is explicitly specified.
+Similarly, all \f[V]--resync-mode\f[R] options (except \f[V]none\f[R])
+imply \f[V]--resync\f[R], so it is not necessary to use both the
+\f[V]--resync\f[R] and \f[V]--resync-mode\f[R] flags simultaneously --
 either one is sufficient without the other.
 .SS --check-access
 .PP
 Access check files are an additional safety measure against data loss.
-bisync will ensure it can find matching \f[C]RCLONE_TEST\f[R] files in
+bisync will ensure it can find matching \f[V]RCLONE_TEST\f[R] files in
 the same places in the Path1 and Path2 filesystems.
-\f[C]RCLONE_TEST\f[R] files are not generated automatically.
-For \f[C]--check-access\f[R] to succeed, you must first either:
-\f[B]A)\f[R] Place one or more \f[C]RCLONE_TEST\f[R] files in both
-systems, or \f[B]B)\f[R] Set \f[C]--check-filename\f[R] to a filename
+\f[V]RCLONE_TEST\f[R] files are not generated automatically.
+For \f[V]--check-access\f[R] to succeed, you must first either:
+\f[B]A)\f[R] Place one or more \f[V]RCLONE_TEST\f[R] files in both
+systems, or \f[B]B)\f[R] Set \f[V]--check-filename\f[R] to a filename
 already in use in various locations throughout your sync\[aq]d fileset.
 Recommended methods for \f[B]A)\f[R] include: *
-\f[C]rclone touch Path1/RCLONE_TEST\f[R] (create a new file) *
-\f[C]rclone copyto Path1/RCLONE_TEST Path2/RCLONE_TEST\f[R] (copy an
+\f[V]rclone touch Path1/RCLONE_TEST\f[R] (create a new file) *
+\f[V]rclone copyto Path1/RCLONE_TEST Path2/RCLONE_TEST\f[R] (copy an
 existing file) *
-\f[C]rclone copy Path1/RCLONE_TEST Path2/RCLONE_TEST  --include \[dq]RCLONE_TEST\[dq]\f[R]
+\f[V]rclone copy Path1/RCLONE_TEST Path2/RCLONE_TEST  --include \[dq]RCLONE_TEST\[dq]\f[R]
 (copy multiple files at once, recursively) * create the files manually
-(outside of rclone) * run \f[C]bisync\f[R] once \f[I]without\f[R]
-\f[C]--check-access\f[R] to set matching files on both filesystems will
+(outside of rclone) * run \f[V]bisync\f[R] once \f[I]without\f[R]
+\f[V]--check-access\f[R] to set matching files on both filesystems will
 also work, but is not preferred, due to potential for user error (you
 are temporarily disabling the safety feature).
 .PP
-Note that \f[C]--check-access\f[R] is still enforced on
-\f[C]--resync\f[R], so \f[C]bisync --resync --check-access\f[R] will not
+Note that \f[V]--check-access\f[R] is still enforced on
+\f[V]--resync\f[R], so \f[V]bisync --resync --check-access\f[R] will not
 work as a method of initially setting the files (this is to ensure that
 bisync can\[aq]t inadvertently circumvent its own safety
 switch (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20%2D%2Dcheck%2Daccess%20doesn%27t%20always%20fail%20when%20it%20should).)
 .PP
-Time stamps and file contents for \f[C]RCLONE_TEST\f[R] files are not
+Time stamps and file contents for \f[V]RCLONE_TEST\f[R] files are not
 important, just the names and locations.
 If you have symbolic links in your sync tree it is recommended to place
-\f[C]RCLONE_TEST\f[R] files in the linked-to directory tree to protect
+\f[V]RCLONE_TEST\f[R] files in the linked-to directory tree to protect
 against bisync assuming a bunch of deleted files if the linked-to tree
 should not be accessible.
 See also the --check-filename flag.
 .SS --check-filename
 .PP
 Name of the file(s) used in access health validation.
-The default \f[C]--check-filename\f[R] is \f[C]RCLONE_TEST\f[R].
+The default \f[V]--check-filename\f[R] is \f[V]RCLONE_TEST\f[R].
 One or more files having this filename must exist, synchronized between
 your source and destination filesets, in order for
-\f[C]--check-access\f[R] to succeed.
+\f[V]--check-access\f[R] to succeed.
 See --check-access for additional details.
 .SS --compare
 .PP
-As of \f[C]v1.66\f[R], bisync fully supports comparing based on any
+As of \f[V]v1.66\f[R], bisync fully supports comparing based on any
 combination of size, modtime, and checksum (lifting the prior
 restriction on backends without modtime support.)
 .PP
-By default (without the \f[C]--compare\f[R] flag), bisync inherits the
-same comparison options as \f[C]sync\f[R] (that is: \f[C]size\f[R] and
-\f[C]modtime\f[R] by default, unless modified with flags such as
-\f[C]--checksum\f[R] (https://rclone.org/docs/#c-checksum) or
-\f[C]--size-only\f[R].)
+By default (without the \f[V]--compare\f[R] flag), bisync inherits the
+same comparison options as \f[V]sync\f[R] (that is: \f[V]size\f[R] and
+\f[V]modtime\f[R] by default, unless modified with flags such as
+\f[V]--checksum\f[R] (https://rclone.org/docs/#c-checksum) or
+\f[V]--size-only\f[R].)
 .PP
-If the \f[C]--compare\f[R] flag is set, it will override these defaults.
+If the \f[V]--compare\f[R] flag is set, it will override these defaults.
 This can be useful if you wish to compare based on combinations not
-currently supported in \f[C]sync\f[R], such as comparing all three of
-\f[C]size\f[R] AND \f[C]modtime\f[R] AND \f[C]checksum\f[R]
-simultaneously (or just \f[C]modtime\f[R] AND \f[C]checksum\f[R]).
+currently supported in \f[V]sync\f[R], such as comparing all three of
+\f[V]size\f[R] AND \f[V]modtime\f[R] AND \f[V]checksum\f[R]
+simultaneously (or just \f[V]modtime\f[R] AND \f[V]checksum\f[R]).
 .PP
-\f[C]--compare\f[R] takes a comma-separated list, with the currently
-supported values being \f[C]size\f[R], \f[C]modtime\f[R], and
-\f[C]checksum\f[R].
+\f[V]--compare\f[R] takes a comma-separated list, with the currently
+supported values being \f[V]size\f[R], \f[V]modtime\f[R], and
+\f[V]checksum\f[R].
 For example, if you want to compare size and checksum, but not modtime,
 you would do:
 .IP
@@ -29824,14 +29852,14 @@ Or if you want to compare all three:
 \f[R]
 .fi
 .PP
-\f[C]--compare\f[R] overrides any conflicting flags.
+\f[V]--compare\f[R] overrides any conflicting flags.
 For example, if you set the conflicting flags
-\f[C]--compare checksum --size-only\f[R], \f[C]--size-only\f[R] will be
+\f[V]--compare checksum --size-only\f[R], \f[V]--size-only\f[R] will be
 ignored, and bisync will compare checksum and not size.
 To avoid confusion, it is recommended to use \f[I]either\f[R]
-\f[C]--compare\f[R] or the normal \f[C]sync\f[R] flags, but not both.
+\f[V]--compare\f[R] or the normal \f[V]sync\f[R] flags, but not both.
 .PP
-If \f[C]--compare\f[R] includes \f[C]checksum\f[R] and both remotes
+If \f[V]--compare\f[R] includes \f[V]checksum\f[R] and both remotes
 support checksums but have no hash types in common with each other,
 checksums will be considered \f[I]only\f[R] for comparisons within the
 same side (to determine what has changed since the prior sync), but not
@@ -29839,138 +29867,141 @@ for comparisons against the opposite side.
 If one side supports checksums and the other does not, checksums will
 only be considered on the side that supports them.
 .PP
-When comparing with \f[C]checksum\f[R] and/or \f[C]size\f[R] without
-\f[C]modtime\f[R], bisync cannot determine whether a file is
-\f[C]newer\f[R] or \f[C]older\f[R] -- only whether it is
-\f[C]changed\f[R] or \f[C]unchanged\f[R].
-(If it is \f[C]changed\f[R] on both sides, bisync still does the
+When comparing with \f[V]checksum\f[R] and/or \f[V]size\f[R] without
+\f[V]modtime\f[R], bisync cannot determine whether a file is
+\f[V]newer\f[R] or \f[V]older\f[R] -- only whether it is
+\f[V]changed\f[R] or \f[V]unchanged\f[R].
+(If it is \f[V]changed\f[R] on both sides, bisync still does the
 standard equality-check to avoid declaring a sync conflict unless it
 absolutely has to.)
 .PP
-It is recommended to do a \f[C]--resync\f[R] when changing
-\f[C]--compare\f[R] settings, as otherwise your prior listing files may
+It is recommended to do a \f[V]--resync\f[R] when changing
+\f[V]--compare\f[R] settings, as otherwise your prior listing files may
 not contain the attributes you wish to compare (for example, they will
 not have stored checksums if you were not previously comparing
 checksums.)
 .SS --ignore-listing-checksum
 .PP
-When \f[C]--checksum\f[R] or \f[C]--compare checksum\f[R] is set, bisync
+When \f[V]--checksum\f[R] or \f[V]--compare checksum\f[R] is set, bisync
 will retrieve (or generate) checksums (for backends that support them)
 when creating the listings for both paths, and store the checksums in
 the listing files.
-\f[C]--ignore-listing-checksum\f[R] will disable this behavior, which
+\f[V]--ignore-listing-checksum\f[R] will disable this behavior, which
 may speed things up considerably, especially on backends (such as
 local (https://rclone.org/local/)) where hashes must be computed on the
 fly instead of retrieved.
 Please note the following:
 .IP \[bu] 2
-As of \f[C]v1.66\f[R], \f[C]--ignore-listing-checksum\f[R] is now
-automatically set when neither \f[C]--checksum\f[R] nor
-\f[C]--compare checksum\f[R] are in use (as the checksums would not be
+As of \f[V]v1.66\f[R], \f[V]--ignore-listing-checksum\f[R] is now
+automatically set when neither \f[V]--checksum\f[R] nor
+\f[V]--compare checksum\f[R] are in use (as the checksums would not be
 used for anything.)
 .IP \[bu] 2
-\f[C]--ignore-listing-checksum\f[R] is NOT the same as
-\f[C]--ignore-checksum\f[R] (https://rclone.org/docs/#ignore-checksum),
+\f[V]--ignore-listing-checksum\f[R] is NOT the same as
+\f[V]--ignore-checksum\f[R] (https://rclone.org/docs/#ignore-checksum),
 and you may wish to use one or the other, or both.
-In a nutshell: \f[C]--ignore-listing-checksum\f[R] controls whether
+In a nutshell: \f[V]--ignore-listing-checksum\f[R] controls whether
 checksums are considered when scanning for diffs, while
-\f[C]--ignore-checksum\f[R] controls whether checksums are considered
+\f[V]--ignore-checksum\f[R] controls whether checksums are considered
 during the copy/sync operations that follow, if there ARE diffs.
 .IP \[bu] 2
-Unless \f[C]--ignore-listing-checksum\f[R] is passed, bisync currently
+Unless \f[V]--ignore-listing-checksum\f[R] is passed, bisync currently
 computes hashes for one path \f[I]even when there\[aq]s no common hash
 with the other path\f[R] (for example, a
 crypt (https://rclone.org/crypt/#modification-times-and-hashes) remote.)
 This can still be beneficial, as the hashes will still be used to detect
-changes within the same side (if \f[C]--checksum\f[R] or
-\f[C]--compare checksum\f[R] is set), even if they can\[aq]t be used to
+changes within the same side (if \f[V]--checksum\f[R] or
+\f[V]--compare checksum\f[R] is set), even if they can\[aq]t be used to
 compare against the opposite side.
 .IP \[bu] 2
 If you wish to ignore listing checksums \f[I]only\f[R] on remotes where
-they are slow to compute, consider using \f[C]--no-slow-hash\f[R] (or
-\f[C]--slow-hash-sync-only\f[R]) instead of
-\f[C]--ignore-listing-checksum\f[R].
+they are slow to compute, consider using \f[V]--no-slow-hash\f[R] (or
+\f[V]--slow-hash-sync-only\f[R]) instead of
+\f[V]--ignore-listing-checksum\f[R].
 .IP \[bu] 2
-If \f[C]--ignore-listing-checksum\f[R] is used simultaneously with
-\f[C]--compare checksum\f[R] (or \f[C]--checksum\f[R]), checksums will
+If \f[V]--ignore-listing-checksum\f[R] is used simultaneously with
+\f[V]--compare checksum\f[R] (or \f[V]--checksum\f[R]), checksums will
 be ignored for bisync deltas, but still considered during the sync
 operations that follow (if deltas are detected based on modtime and/or
 size.)
 .SS --no-slow-hash
 .PP
-On some remotes (notably \f[C]local\f[R]), checksums can dramatically
+On some remotes (notably \f[V]local\f[R]), checksums can dramatically
 slow down a bisync run, because hashes cannot be stored and need to be
 computed in real-time when they are requested.
-On other remotes (such as \f[C]drive\f[R]), they add practically no time
+On other remotes (such as \f[V]drive\f[R]), they add practically no time
 at all.
-The \f[C]--no-slow-hash\f[R] flag will automatically skip checksums on
+The \f[V]--no-slow-hash\f[R] flag will automatically skip checksums on
 remotes where they are slow, while still comparing them on others
-(assuming \f[C]--compare\f[R] includes \f[C]checksum\f[R].) This can be
-useful when one of your bisync paths is slow but you still want to check
-checksums on the other, for a more robust sync.
+(assuming \f[V]--compare\f[R] includes \f[V]checksum\f[R].)
+This can be useful when one of your bisync paths is slow but you still
+want to check checksums on the other, for a more robust sync.
 .SS --slow-hash-sync-only
 .PP
-Same as \f[C]--no-slow-hash\f[R], except slow hashes are still
+Same as \f[V]--no-slow-hash\f[R], except slow hashes are still
 considered during sync calls.
 They are still NOT considered for determining deltas, nor or they
 included in listings.
-They are also skipped during \f[C]--resync\f[R].
+They are also skipped during \f[V]--resync\f[R].
 The main use case for this flag is when you have a large number of
 files, but relatively few of them change from run to run -- so you
 don\[aq]t want to check your entire tree every time (it would take too
 long), but you still want to consider checksums for the smaller group of
-files for which a \f[C]modtime\f[R] or \f[C]size\f[R] change was
+files for which a \f[V]modtime\f[R] or \f[V]size\f[R] change was
 detected.
 Keep in mind that this speed savings comes with a safety trade-off: if a
 file\[aq]s content were to change without a change to its
-\f[C]modtime\f[R] or \f[C]size\f[R], bisync would not detect it, and it
+\f[V]modtime\f[R] or \f[V]size\f[R], bisync would not detect it, and it
 would not be synced.
 .PP
-\f[C]--slow-hash-sync-only\f[R] is only useful if both remotes share a
+\f[V]--slow-hash-sync-only\f[R] is only useful if both remotes share a
 common hash type (if they don\[aq]t, bisync will automatically fall back
-to \f[C]--no-slow-hash\f[R].) Both \f[C]--no-slow-hash\f[R] and
-\f[C]--slow-hash-sync-only\f[R] have no effect without
-\f[C]--compare checksum\f[R] (or \f[C]--checksum\f[R]).
+to \f[V]--no-slow-hash\f[R].)
+Both \f[V]--no-slow-hash\f[R] and \f[V]--slow-hash-sync-only\f[R] have
+no effect without \f[V]--compare checksum\f[R] (or
+\f[V]--checksum\f[R]).
 .SS --download-hash
 .PP
-If \f[C]--download-hash\f[R] is set, bisync will use best efforts to
+If \f[V]--download-hash\f[R] is set, bisync will use best efforts to
 obtain an MD5 checksum by downloading and computing on-the-fly, when
 checksums are not otherwise available (for example, a remote that
-doesn\[aq]t support them.) Note that since rclone has to download the
-entire file, this may dramatically slow down your bisync runs, and is
-also likely to use a lot of data, so it is probably not practical for
-bisync paths with a large total file size.
+doesn\[aq]t support them.)
+Note that since rclone has to download the entire file, this may
+dramatically slow down your bisync runs, and is also likely to use a lot
+of data, so it is probably not practical for bisync paths with a large
+total file size.
 However, it can be a good option for syncing small-but-important files
 with maximum accuracy (for example, a source code repo on a
-\f[C]crypt\f[R] remote.) An additional advantage over methods like
-\f[C]cryptcheck\f[R] (https://rclone.org/commands/rclone_cryptcheck/) is
+\f[V]crypt\f[R] remote.)
+An additional advantage over methods like
+\f[V]cryptcheck\f[R] (https://rclone.org/commands/rclone_cryptcheck/) is
 that the original file is not required for comparison (for example,
-\f[C]--download-hash\f[R] can be used to bisync two different crypt
+\f[V]--download-hash\f[R] can be used to bisync two different crypt
 remotes with different passwords.)
 .PP
-When \f[C]--download-hash\f[R] is set, bisync still looks for more
+When \f[V]--download-hash\f[R] is set, bisync still looks for more
 efficient checksums first, and falls back to downloading only when none
 are found.
 It takes priority over conflicting flags such as
-\f[C]--no-slow-hash\f[R].
-\f[C]--download-hash\f[R] is not suitable for Google Docs and other
+\f[V]--no-slow-hash\f[R].
+\f[V]--download-hash\f[R] is not suitable for Google Docs and other
 files of unknown size, as their checksums would change from run to run
 (due to small variances in the internals of the generated export file.)
-Therefore, bisync automatically skips \f[C]--download-hash\f[R] for
+Therefore, bisync automatically skips \f[V]--download-hash\f[R] for
 files with a size less than 0.
 .PP
-See also: \f[C]Hasher\f[R] (https://rclone.org/hasher/) backend,
-\f[C]cryptcheck\f[R] (https://rclone.org/commands/rclone_cryptcheck/)
+See also: \f[V]Hasher\f[R] (https://rclone.org/hasher/) backend,
+\f[V]cryptcheck\f[R] (https://rclone.org/commands/rclone_cryptcheck/)
 command,
-\f[C]rclone check --download\f[R] (https://rclone.org/commands/rclone_check/)
-option, \f[C]md5sum\f[R] (https://rclone.org/commands/rclone_md5sum/)
+\f[V]rclone check --download\f[R] (https://rclone.org/commands/rclone_check/)
+option, \f[V]md5sum\f[R] (https://rclone.org/commands/rclone_md5sum/)
 command
 .SS --max-delete
 .PP
-As a safety check, if greater than the \f[C]--max-delete\f[R] percent of
+As a safety check, if greater than the \f[V]--max-delete\f[R] percent of
 files were deleted on either the Path1 or Path2 filesystem, then bisync
 will abort with a warning message, without making any changes.
-The default \f[C]--max-delete\f[R] is \f[C]50%\f[R].
+The default \f[V]--max-delete\f[R] is \f[V]50%\f[R].
 One way to trigger this limit is to rename a directory that contains
 more than half of your files.
 This will appear to bisync as a bunch of deleted files and a bunch of
@@ -29979,8 +30010,8 @@ This safety check is intended to block bisync from deleting all of the
 files on both filesystems due to a temporary network access issue, or if
 the user had inadvertently deleted the files on one side or the other.
 To force the sync, either set a different delete percentage limit, e.g.
-\f[C]--max-delete 75\f[R] (allows up to 75% deletion), or use
-\f[C]--force\f[R] to bypass the check.
+\f[V]--max-delete 75\f[R] (allows up to 75% deletion), or use
+\f[V]--force\f[R] to bypass the check.
 .PP
 Also see the all files changed check.
 .SS --filters-file
@@ -29994,7 +30025,7 @@ An example filters file contains filters for non-allowed files for
 synching with Dropbox.
 .PP
 If you make changes to your filters file then bisync requires a run with
-\f[C]--resync\f[R].
+\f[V]--resync\f[R].
 This is a safety feature, which prevents existing files on the Path1
 and/or Path2 side from seeming to disappear from view (since they are
 excluded in the new listings), which would fool bisync into seeing them
@@ -30002,144 +30033,145 @@ as deleted (as compared to the prior run listings), and then bisync
 would proceed to delete them for real.
 .PP
 To block this from happening, bisync calculates an MD5 hash of the
-filters file and stores the hash in a \f[C].md5\f[R] file in the same
+filters file and stores the hash in a \f[V].md5\f[R] file in the same
 place as your filters file.
-On the next run with \f[C]--filters-file\f[R] set, bisync re-calculates
+On the next run with \f[V]--filters-file\f[R] set, bisync re-calculates
 the MD5 hash of the current filters file and compares it to the hash
-stored in the \f[C].md5\f[R] file.
+stored in the \f[V].md5\f[R] file.
 If they don\[aq]t match, the run aborts with a critical error and thus
-forces you to do a \f[C]--resync\f[R], likely avoiding a disaster.
+forces you to do a \f[V]--resync\f[R], likely avoiding a disaster.
 .SS --conflict-resolve CHOICE
 .PP
 In bisync, a \[dq]conflict\[dq] is a file that is \f[I]new\f[R] or
 \f[I]changed\f[R] on \f[I]both sides\f[R] (relative to the prior run)
 AND is \f[I]not currently identical\f[R] on both sides.
-\f[C]--conflict-resolve\f[R] controls how bisync handles such a
+\f[V]--conflict-resolve\f[R] controls how bisync handles such a
 scenario.
 The currently supported options are:
 .IP \[bu] 2
-\f[C]none\f[R] - (the default) - do not attempt to pick a winner, keep
-and rename both files according to \f[C]--conflict-loser\f[R] and
-\f[C]--conflict-suffix\f[R] settings.
-For example, with the default settings, \f[C]file.txt\f[R] on Path1 is
-renamed \f[C]file.txt.conflict1\f[R] and \f[C]file.txt\f[R] on Path2 is
-renamed \f[C]file.txt.conflict2\f[R].
+\f[V]none\f[R] - (the default) - do not attempt to pick a winner, keep
+and rename both files according to \f[V]--conflict-loser\f[R] and
+\f[V]--conflict-suffix\f[R] settings.
+For example, with the default settings, \f[V]file.txt\f[R] on Path1 is
+renamed \f[V]file.txt.conflict1\f[R] and \f[V]file.txt\f[R] on Path2 is
+renamed \f[V]file.txt.conflict2\f[R].
 Both are copied to the opposite path during the run, so both sides end
 up with a copy of both files.
-(As \f[C]none\f[R] is the default, it is not necessary to specify
-\f[C]--conflict-resolve none\f[R] -- you can just omit the flag.)
+(As \f[V]none\f[R] is the default, it is not necessary to specify
+\f[V]--conflict-resolve none\f[R] -- you can just omit the flag.)
 .IP \[bu] 2
-\f[C]newer\f[R] - the newer file (by \f[C]modtime\f[R]) is considered
+\f[V]newer\f[R] - the newer file (by \f[V]modtime\f[R]) is considered
 the winner and is copied without renaming.
 The older file (the \[dq]loser\[dq]) is handled according to
-\f[C]--conflict-loser\f[R] and \f[C]--conflict-suffix\f[R] settings
-(either renamed or deleted.) For example, if \f[C]file.txt\f[R] on Path1
-is newer than \f[C]file.txt\f[R] on Path2, the result on both sides
-(with other default settings) will be \f[C]file.txt\f[R] (winner from
-Path1) and \f[C]file.txt.conflict1\f[R] (loser from Path2).
+\f[V]--conflict-loser\f[R] and \f[V]--conflict-suffix\f[R] settings
+(either renamed or deleted.)
+For example, if \f[V]file.txt\f[R] on Path1 is newer than
+\f[V]file.txt\f[R] on Path2, the result on both sides (with other
+default settings) will be \f[V]file.txt\f[R] (winner from Path1) and
+\f[V]file.txt.conflict1\f[R] (loser from Path2).
 .IP \[bu] 2
-\f[C]older\f[R] - same as \f[C]newer\f[R], except the older file is
+\f[V]older\f[R] - same as \f[V]newer\f[R], except the older file is
 considered the winner, and the newer file is considered the loser.
 .IP \[bu] 2
-\f[C]larger\f[R] - the larger file (by \f[C]size\f[R]) is considered the
-winner (regardless of \f[C]modtime\f[R], if any).
+\f[V]larger\f[R] - the larger file (by \f[V]size\f[R]) is considered the
+winner (regardless of \f[V]modtime\f[R], if any).
 .IP \[bu] 2
-\f[C]smaller\f[R] - the smaller file (by \f[C]size\f[R]) is considered
-the winner (regardless of \f[C]modtime\f[R], if any).
+\f[V]smaller\f[R] - the smaller file (by \f[V]size\f[R]) is considered
+the winner (regardless of \f[V]modtime\f[R], if any).
 .IP \[bu] 2
-\f[C]path1\f[R] - the version from Path1 is unconditionally considered
-the winner (regardless of \f[C]modtime\f[R] and \f[C]size\f[R], if any).
+\f[V]path1\f[R] - the version from Path1 is unconditionally considered
+the winner (regardless of \f[V]modtime\f[R] and \f[V]size\f[R], if any).
 This can be useful if one side is usually more trusted or up-to-date
 than the other.
 .IP \[bu] 2
-\f[C]path2\f[R] - same as \f[C]path1\f[R], except the path2 version is
+\f[V]path2\f[R] - same as \f[V]path1\f[R], except the path2 version is
 considered the winner.
 .PP
 For all of the above options, note the following: - If either of the
 underlying remotes lacks support for the chosen method, it will be
-ignored and fall back to \f[C]none\f[R].
-(For example, if \f[C]--conflict-resolve newer\f[R] is set, but one of
-the paths uses a remote that doesn\[aq]t support \f[C]modtime\f[R].) -
-If a winner can\[aq]t be determined because the chosen method\[aq]s
+ignored and fall back to \f[V]none\f[R].
+(For example, if \f[V]--conflict-resolve newer\f[R] is set, but one of
+the paths uses a remote that doesn\[aq]t support \f[V]modtime\f[R].)
+- If a winner can\[aq]t be determined because the chosen method\[aq]s
 attribute is missing or equal, it will be ignored and fall back to
-\f[C]none\f[R].
-(For example, if \f[C]--conflict-resolve newer\f[R] is set, but the
-Path1 and Path2 modtimes are identical, even if the sizes may differ.) -
-If the file\[aq]s content is currently identical on both sides, it is
+\f[V]none\f[R].
+(For example, if \f[V]--conflict-resolve newer\f[R] is set, but the
+Path1 and Path2 modtimes are identical, even if the sizes may differ.)
+- If the file\[aq]s content is currently identical on both sides, it is
 not considered a \[dq]conflict\[dq], even if new or changed on both
 sides since the prior sync.
 (For example, if you made a change on one side and then synced it to the
-other side by other means.) Therefore, none of the conflict resolution
-flags apply in this scenario.
+other side by other means.)
+Therefore, none of the conflict resolution flags apply in this scenario.
 - The conflict resolution flags do not apply during a
-\f[C]--resync\f[R], as there is no \[dq]prior run\[dq] to speak of (but
-see \f[C]--resync-mode\f[R] for similar options.)
+\f[V]--resync\f[R], as there is no \[dq]prior run\[dq] to speak of (but
+see \f[V]--resync-mode\f[R] for similar options.)
 .SS --conflict-loser CHOICE
 .PP
-\f[C]--conflict-loser\f[R] determines what happens to the
-\[dq]loser\[dq] of a sync conflict (when \f[C]--conflict-resolve\f[R]
-determines a winner) or to both files (when there is no winner.) The
-currently supported options are:
+\f[V]--conflict-loser\f[R] determines what happens to the
+\[dq]loser\[dq] of a sync conflict (when \f[V]--conflict-resolve\f[R]
+determines a winner) or to both files (when there is no winner.)
+The currently supported options are:
 .IP \[bu] 2
-\f[C]num\f[R] - (the default) - auto-number the conflicts by
+\f[V]num\f[R] - (the default) - auto-number the conflicts by
 automatically appending the next available number to the
-\f[C]--conflict-suffix\f[R], in chronological order.
+\f[V]--conflict-suffix\f[R], in chronological order.
 For example, with the default settings, the first conflict for
-\f[C]file.txt\f[R] will be renamed \f[C]file.txt.conflict1\f[R].
-If \f[C]file.txt.conflict1\f[R] already exists,
-\f[C]file.txt.conflict2\f[R] will be used instead (etc., up to a maximum
+\f[V]file.txt\f[R] will be renamed \f[V]file.txt.conflict1\f[R].
+If \f[V]file.txt.conflict1\f[R] already exists,
+\f[V]file.txt.conflict2\f[R] will be used instead (etc., up to a maximum
 of 9223372036854775807 conflicts.)
 .IP \[bu] 2
-\f[C]pathname\f[R] - rename the conflicts according to which side they
-came from, which was the default behavior prior to \f[C]v1.66\f[R].
-For example, with \f[C]--conflict-suffix path\f[R], \f[C]file.txt\f[R]
-from Path1 will be renamed \f[C]file.txt.path1\f[R], and
-\f[C]file.txt\f[R] from Path2 will be renamed \f[C]file.txt.path2\f[R].
+\f[V]pathname\f[R] - rename the conflicts according to which side they
+came from, which was the default behavior prior to \f[V]v1.66\f[R].
+For example, with \f[V]--conflict-suffix path\f[R], \f[V]file.txt\f[R]
+from Path1 will be renamed \f[V]file.txt.path1\f[R], and
+\f[V]file.txt\f[R] from Path2 will be renamed \f[V]file.txt.path2\f[R].
 If two non-identical suffixes are provided (ex.
-\f[C]--conflict-suffix cloud,local\f[R]), the trailing digit is omitted.
-Importantly, note that with \f[C]pathname\f[R], there is no
-auto-numbering beyond \f[C]2\f[R], so if \f[C]file.txt.path2\f[R]
+\f[V]--conflict-suffix cloud,local\f[R]), the trailing digit is omitted.
+Importantly, note that with \f[V]pathname\f[R], there is no
+auto-numbering beyond \f[V]2\f[R], so if \f[V]file.txt.path2\f[R]
 somehow already exists, it will be overwritten.
-Using a dynamic date variable in your \f[C]--conflict-suffix\f[R] (see
+Using a dynamic date variable in your \f[V]--conflict-suffix\f[R] (see
 below) is one possible way to avoid this.
 Note also that conflicts-of-conflicts are possible, if the original
 conflict is not manually resolved -- for example, if for some reason you
-edited \f[C]file.txt.path1\f[R] on both sides, and those edits were
-different, the result would be \f[C]file.txt.path1.path1\f[R] and
-\f[C]file.txt.path1.path2\f[R] (in addition to
-\f[C]file.txt.path2\f[R].)
+edited \f[V]file.txt.path1\f[R] on both sides, and those edits were
+different, the result would be \f[V]file.txt.path1.path1\f[R] and
+\f[V]file.txt.path1.path2\f[R] (in addition to
+\f[V]file.txt.path2\f[R].)
 .IP \[bu] 2
-\f[C]delete\f[R] - keep the winner only and delete the loser, instead of
+\f[V]delete\f[R] - keep the winner only and delete the loser, instead of
 renaming it.
-If a winner cannot be determined (see \f[C]--conflict-resolve\f[R] for
-details on how this could happen), \f[C]delete\f[R] is ignored and the
-default \f[C]num\f[R] is used instead (i.e.
+If a winner cannot be determined (see \f[V]--conflict-resolve\f[R] for
+details on how this could happen), \f[V]delete\f[R] is ignored and the
+default \f[V]num\f[R] is used instead (i.e.
 both versions are kept and renamed, and neither is deleted.)
-\f[C]delete\f[R] is inherently the most destructive option, so use it
+\f[V]delete\f[R] is inherently the most destructive option, so use it
 only with care.
 .PP
 For all of the above options, note that if a winner cannot be determined
-(see \f[C]--conflict-resolve\f[R] for details on how this could happen),
-or if \f[C]--conflict-resolve\f[R] is not in use, \f[I]both\f[R] files
+(see \f[V]--conflict-resolve\f[R] for details on how this could happen),
+or if \f[V]--conflict-resolve\f[R] is not in use, \f[I]both\f[R] files
 will be renamed.
 .SS --conflict-suffix STRING[,STRING]
 .PP
-\f[C]--conflict-suffix\f[R] controls the suffix that is appended when
-bisync renames a \f[C]--conflict-loser\f[R] (default:
-\f[C]conflict\f[R]).
-\f[C]--conflict-suffix\f[R] will accept either one string or two
+\f[V]--conflict-suffix\f[R] controls the suffix that is appended when
+bisync renames a \f[V]--conflict-loser\f[R] (default:
+\f[V]conflict\f[R]).
+\f[V]--conflict-suffix\f[R] will accept either one string or two
 comma-separated strings to assign different suffixes to Path1 vs.
 Path2.
 This may be helpful later in identifying the source of the conflict.
 (For example,
-\f[C]--conflict-suffix dropboxconflict,laptopconflict\f[R])
+\f[V]--conflict-suffix dropboxconflict,laptopconflict\f[R])
 .PP
-With \f[C]--conflict-loser num\f[R], a number is always appended to the
+With \f[V]--conflict-loser num\f[R], a number is always appended to the
 suffix.
-With \f[C]--conflict-loser pathname\f[R], a number is appended only when
+With \f[V]--conflict-loser pathname\f[R], a number is appended only when
 one suffix is specified (or when two identical suffixes are specified.)
 i.e.
-with \f[C]--conflict-loser pathname\f[R], all of the following would
+with \f[V]--conflict-loser pathname\f[R], all of the following would
 produce exactly the same result:
 .IP
 .nf
@@ -30152,12 +30184,12 @@ produce exactly the same result:
 .PP
 Suffixes may be as short as 1 character.
 By default, the suffix is appended after any other extensions (ex.
-\f[C]file.jpg.conflict1\f[R]), however, this can be changed with the
-\f[C]--suffix-keep-extension\f[R] (https://rclone.org/docs/#suffix-keep-extension)
+\f[V]file.jpg.conflict1\f[R]), however, this can be changed with the
+\f[V]--suffix-keep-extension\f[R] (https://rclone.org/docs/#suffix-keep-extension)
 flag (i.e.
-to instead result in \f[C]file.conflict1.jpg\f[R]).
+to instead result in \f[V]file.conflict1.jpg\f[R]).
 .PP
-\f[C]--conflict-suffix\f[R] supports several \f[I]dynamic date
+\f[V]--conflict-suffix\f[R] supports several \f[I]dynamic date
 variables\f[R] when enclosed in curly braces as globs.
 This can be helpful to track the date and/or time that each conflict was
 handled by bisync.
@@ -30176,21 +30208,23 @@ here (https://pkg.go.dev/time#example-Time.Format) are supported, but
 take care to ensure that your chosen format does not use any characters
 that are illegal on your remotes (for example, macOS does not allow
 colons in filenames, and slashes are also best avoided as they are often
-interpreted as directory separators.) To address this particular issue,
-an additional \f[C]{MacFriendlyTime}\f[R] (or just \f[C]{mac}\f[R])
-option is supported, which results in \f[C]2006-01-02 0304PM\f[R].
+interpreted as directory separators.)
+To address this particular issue, an additional
+\f[V]{MacFriendlyTime}\f[R] (or just \f[V]{mac}\f[R]) option is
+supported, which results in \f[V]2006-01-02 0304PM\f[R].
 .PP
-Note that \f[C]--conflict-suffix\f[R] is entirely separate from
+Note that \f[V]--conflict-suffix\f[R] is entirely separate from
 rclone\[aq]s main
-\f[C]--sufix\f[R] (https://rclone.org/docs/#suffix-suffix) flag.
+\f[V]--sufix\f[R] (https://rclone.org/docs/#suffix-suffix) flag.
 This is intentional, as users may wish to use both flags simultaneously,
-if also using \f[C]--backup-dir\f[R].
+if also using \f[V]--backup-dir\f[R].
 .PP
-Finally, note that the default in bisync prior to \f[C]v1.66\f[R] was to
-rename conflicts with \f[C]..path1\f[R] and \f[C]..path2\f[R] (with two
-periods, and \f[C]path\f[R] instead of \f[C]conflict\f[R].) Bisync now
-defaults to a single dot instead of a double dot, but additional dots
-can be added by including them in the specified suffix string.
+Finally, note that the default in bisync prior to \f[V]v1.66\f[R] was to
+rename conflicts with \f[V]..path1\f[R] and \f[V]..path2\f[R] (with two
+periods, and \f[V]path\f[R] instead of \f[V]conflict\f[R].)
+Bisync now defaults to a single dot instead of a double dot, but
+additional dots can be added by including them in the specified suffix
+string.
 For example, for behavior equivalent to the previous default, use:
 .IP
 .nf
@@ -30212,14 +30246,14 @@ A resync run would correct the error.
 Note that the default-enabled integrity check locally executes a load of
 both the final Path1 and Path2 listings, and thus adds to the run time
 of a sync.
-Using \f[C]--check-sync=false\f[R] will disable it and may significantly
+Using \f[V]--check-sync=false\f[R] will disable it and may significantly
 reduce the sync run times for very large numbers of files.
 .PP
-The check may be run manually with \f[C]--check-sync=only\f[R].
+The check may be run manually with \f[V]--check-sync=only\f[R].
 It runs only the integrity check and terminates without actually
 synching.
 .PP
-Note that currently, \f[C]--check-sync\f[R] \f[B]only checks listing
+Note that currently, \f[V]--check-sync\f[R] \f[B]only checks listing
 snapshots and NOT the actual files on the remotes.\f[R] Note also that
 the listing snapshots will not know about any changes that happened
 during or after the latest bisync run, as those will be discovered on
@@ -30232,11 +30266,11 @@ This is normal, and any differences will be detected and synced on the
 next run.
 .PP
 For a robust integrity check of the current state of the remotes (as
-opposed to just their listing snapshots), consider using \f[C]check\f[R]
+opposed to just their listing snapshots), consider using \f[V]check\f[R]
 (or
-\f[C]cryptcheck\f[R] (https://rclone.org/commands/rclone_cryptcheck/),
-if at least one path is a \f[C]crypt\f[R] remote) instead of
-\f[C]--check-sync\f[R], keeping in mind that differences are expected if
+\f[V]cryptcheck\f[R] (https://rclone.org/commands/rclone_cryptcheck/),
+if at least one path is a \f[V]crypt\f[R] remote) instead of
+\f[V]--check-sync\f[R], keeping in mind that differences are expected if
 files changed during or after your last bisync run.
 .PP
 For example, a possible sequence could look like this:
@@ -30271,53 +30305,53 @@ rclone sync Path1 Path2 --filter-from /path/to/filters.txt --create-empty-src-di
 (or switch Path1 and Path2 to make Path2 the source-of-truth)
 .PP
 Or, if neither side is totally up-to-date, you could run a
-\f[C]--resync\f[R] to bring them back into agreement (but remember that
+\f[V]--resync\f[R] to bring them back into agreement (but remember that
 this could cause deleted files to re-appear.)
 .PP
-*Note also that \f[C]rclone check\f[R] does not currently include empty
+*Note also that \f[V]rclone check\f[R] does not currently include empty
 directories, so if you want to know if any empty directories are out of
-sync, consider alternatively running the above \f[C]rclone sync\f[R]
-command with \f[C]--dry-run\f[R] added.
+sync, consider alternatively running the above \f[V]rclone sync\f[R]
+command with \f[V]--dry-run\f[R] added.
 .PP
-See also: Concurrent modifications, \f[C]--resilient\f[R]
+See also: Concurrent modifications, \f[V]--resilient\f[R]
 .SS --resilient
 .PP
-\f[B]\f[BI]Caution: this is an experimental feature. Use at your own
-risk!\f[B]\f[R]
+\f[B]\f[BI]Caution: this is an experimental feature.
+Use at your own risk!\f[B]\f[R]
 .PP
 By default, most errors or interruptions will cause bisync to abort and
-require \f[C]--resync\f[R] to recover.
+require \f[V]--resync\f[R] to recover.
 This is a safety feature, to prevent bisync from running again until a
 user checks things out.
 However, in some cases, bisync can go too far and enforce a lockout when
 one isn\[aq]t actually necessary, like for certain less-serious errors
 that might resolve themselves on the next run.
-When \f[C]--resilient\f[R] is specified, bisync tries its best to
-recover and self-correct, and only requires \f[C]--resync\f[R] as a last
+When \f[V]--resilient\f[R] is specified, bisync tries its best to
+recover and self-correct, and only requires \f[V]--resync\f[R] as a last
 resort when a human\[aq]s involvement is absolutely necessary.
 The intended use case is for running bisync as a background process
 (such as via scheduled cron).
 .PP
-When using \f[C]--resilient\f[R] mode, bisync will still report the
+When using \f[V]--resilient\f[R] mode, bisync will still report the
 error and abort, however it will not lock out future runs -- allowing
 the possibility of retrying at the next normally scheduled time, without
-requiring a \f[C]--resync\f[R] first.
+requiring a \f[V]--resync\f[R] first.
 Examples of such retryable errors include access test failures, missing
 listing files, and filter change detections.
 These safety features will still prevent the \f[I]current\f[R] run from
 proceeding -- the difference is that if conditions have improved by the
 time of the \f[I]next\f[R] run, that next run will be allowed to
 proceed.
-Certain more serious errors will still enforce a \f[C]--resync\f[R]
-lockout, even in \f[C]--resilient\f[R] mode, to prevent data loss.
+Certain more serious errors will still enforce a \f[V]--resync\f[R]
+lockout, even in \f[V]--resilient\f[R] mode, to prevent data loss.
 .PP
-Behavior of \f[C]--resilient\f[R] may change in a future version.
-(See also: \f[C]--recover\f[R], \f[C]--max-lock\f[R], Graceful Shutdown)
+Behavior of \f[V]--resilient\f[R] may change in a future version.
+(See also: \f[V]--recover\f[R], \f[V]--max-lock\f[R], Graceful Shutdown)
 .SS --recover
 .PP
-If \f[C]--recover\f[R] is set, in the event of a sudden interruption or
+If \f[V]--recover\f[R] is set, in the event of a sudden interruption or
 other un-graceful shutdown, bisync will attempt to automatically recover
-on the next run, instead of requiring \f[C]--resync\f[R].
+on the next run, instead of requiring \f[V]--resync\f[R].
 Bisync is able to recover robustly by keeping one \[dq]backup\[dq]
 listing at all times, representing the state of both paths after the
 last known successful sync.
@@ -30335,25 +30369,26 @@ later aborts, and then that same file changes AGAIN before the next run,
 bisync will think it is a sync conflict, and handle it accordingly.
 (From bisync\[aq]s perspective, the file has changed on both sides since
 the last trusted sync, and the files on either side are not currently
-identical.) Therefore, \f[C]--recover\f[R] carries with it a slightly
-increased chance of having conflicts -- though in practice this is
-pretty rare, as the conditions required to cause it are quite specific.
+identical.)
+Therefore, \f[V]--recover\f[R] carries with it a slightly increased
+chance of having conflicts -- though in practice this is pretty rare, as
+the conditions required to cause it are quite specific.
 This risk can be reduced by using bisync\[aq]s \[dq]Graceful
-Shutdown\[dq] mode (triggered by sending \f[C]SIGINT\f[R] or
-\f[C]Ctrl+C\f[R]), when you have the choice, instead of forcing a sudden
+Shutdown\[dq] mode (triggered by sending \f[V]SIGINT\f[R] or
+\f[V]Ctrl+C\f[R]), when you have the choice, instead of forcing a sudden
 termination.
 .PP
-\f[C]--recover\f[R] and \f[C]--resilient\f[R] are similar, but distinct
--- the main difference is that \f[C]--resilient\f[R] is about
-\f[I]retrying\f[R], while \f[C]--recover\f[R] is about
+\f[V]--recover\f[R] and \f[V]--resilient\f[R] are similar, but distinct
+-- the main difference is that \f[V]--resilient\f[R] is about
+\f[I]retrying\f[R], while \f[V]--recover\f[R] is about
 \f[I]recovering\f[R].
 Most users will probably want both.
-\f[C]--resilient\f[R] allows retrying when bisync has chosen to abort
-itself due to safety features such as failing \f[C]--check-access\f[R]
+\f[V]--resilient\f[R] allows retrying when bisync has chosen to abort
+itself due to safety features such as failing \f[V]--check-access\f[R]
 or detecting a filter change.
-\f[C]--resilient\f[R] does not cover external interruptions such as a
+\f[V]--resilient\f[R] does not cover external interruptions such as a
 user shutting down their computer in the middle of a sync -- that is
-what \f[C]--recover\f[R] is for.
+what \f[V]--recover\f[R] is for.
 .SS --max-lock
 .PP
 Bisync uses lock files as a safety feature to prevent interference from
@@ -30362,62 +30397,63 @@ Bisync normally removes these lock files at the end of a run, but if
 bisync is abruptly interrupted, these files will be left behind.
 By default, they will lock out all future runs, until the user has a
 chance to manually check things out and remove the lock.
-As an alternative, \f[C]--max-lock\f[R] can be used to make them
+As an alternative, \f[V]--max-lock\f[R] can be used to make them
 automatically expire after a certain period of time, so that future runs
 are not locked out forever, and auto-recovery is possible.
-\f[C]--max-lock\f[R] can be any duration \f[C]2m\f[R] or greater (or
-\f[C]0\f[R] to disable).
+\f[V]--max-lock\f[R] can be any duration \f[V]2m\f[R] or greater (or
+\f[V]0\f[R] to disable).
 If set, lock files older than this will be considered \[dq]expired\[dq],
 and future runs will be allowed to disregard them and proceed.
-(Note that the \f[C]--max-lock\f[R] duration must be set by the process
+(Note that the \f[V]--max-lock\f[R] duration must be set by the process
 that left the lock file -- not the later one interpreting it.)
 .PP
 If set, bisync will also \[dq]renew\[dq] these lock files every
-\f[C]--max-lock minus one minute\f[R] throughout a run, for extra
+\f[V]--max-lock minus one minute\f[R] throughout a run, for extra
 safety.
-(For example, with \f[C]--max-lock 5m\f[R], bisync would renew the lock
+(For example, with \f[V]--max-lock 5m\f[R], bisync would renew the lock
 file (for another 5 minutes) every 4 minutes until the run has
-completed.) In other words, it should not be possible for a lock file to
-pass its expiration time while the process that created it is still
-running -- and you can therefore be reasonably sure that any
-\f[I]expired\f[R] lock file you may find was left there by an
-interrupted run, not one that is still running and just taking awhile.
+completed.)
+In other words, it should not be possible for a lock file to pass its
+expiration time while the process that created it is still running --
+and you can therefore be reasonably sure that any \f[I]expired\f[R] lock
+file you may find was left there by an interrupted run, not one that is
+still running and just taking awhile.
 .PP
-If \f[C]--max-lock\f[R] is \f[C]0\f[R] or not set, the default is that
+If \f[V]--max-lock\f[R] is \f[V]0\f[R] or not set, the default is that
 lock files will never expire, and will block future runs (of these same
 two bisync paths) indefinitely.
 .PP
 For maximum resilience from disruptions, consider setting a relatively
-short duration like \f[C]--max-lock 2m\f[R] along with
-\f[C]--resilient\f[R] and \f[C]--recover\f[R], and a relatively frequent
+short duration like \f[V]--max-lock 2m\f[R] along with
+\f[V]--resilient\f[R] and \f[V]--recover\f[R], and a relatively frequent
 cron schedule.
 The result will be a very robust \[dq]set-it-and-forget-it\[dq] bisync
 run that can automatically bounce back from almost any interruption it
 might encounter, without requiring the user to get involved and run a
-\f[C]--resync\f[R].
+\f[V]--resync\f[R].
 (See also: Graceful Shutdown mode)
 .SS --backup-dir1 and --backup-dir2
 .PP
-As of \f[C]v1.66\f[R],
-\f[C]--backup-dir\f[R] (https://rclone.org/docs/#backup-dir-dir) is
+As of \f[V]v1.66\f[R],
+\f[V]--backup-dir\f[R] (https://rclone.org/docs/#backup-dir-dir) is
 supported in bisync.
-Because \f[C]--backup-dir\f[R] must be a non-overlapping path on the
-same remote, Bisync has introduced new \f[C]--backup-dir1\f[R] and
-\f[C]--backup-dir2\f[R] flags to support separate backup-dirs for
-\f[C]Path1\f[R] and \f[C]Path2\f[R] (bisyncing between different remotes
-with \f[C]--backup-dir\f[R] would not otherwise be possible.)
-\f[C]--backup-dir1\f[R] and \f[C]--backup-dir2\f[R] can use different
-remotes from each other, but \f[C]--backup-dir1\f[R] must use the same
-remote as \f[C]Path1\f[R], and \f[C]--backup-dir2\f[R] must use the same
-remote as \f[C]Path2\f[R].
+Because \f[V]--backup-dir\f[R] must be a non-overlapping path on the
+same remote, Bisync has introduced new \f[V]--backup-dir1\f[R] and
+\f[V]--backup-dir2\f[R] flags to support separate backup-dirs for
+\f[V]Path1\f[R] and \f[V]Path2\f[R] (bisyncing between different remotes
+with \f[V]--backup-dir\f[R] would not otherwise be possible.)
+\f[V]--backup-dir1\f[R] and \f[V]--backup-dir2\f[R] can use different
+remotes from each other, but \f[V]--backup-dir1\f[R] must use the same
+remote as \f[V]Path1\f[R], and \f[V]--backup-dir2\f[R] must use the same
+remote as \f[V]Path2\f[R].
 Each backup directory must not overlap its respective bisync Path
 without being excluded by a filter rule.
 .PP
-The standard \f[C]--backup-dir\f[R] will also work, if both paths use
+The standard \f[V]--backup-dir\f[R] will also work, if both paths use
 the same remote (but note that deleted files from both paths would be
 mixed together in the same dir).
-If either \f[C]--backup-dir1\f[R] and \f[C]--backup-dir2\f[R] are set,
-they will override \f[C]--backup-dir\f[R].
+If either \f[V]--backup-dir1\f[R] and \f[V]--backup-dir2\f[R] are set,
+they will override \f[V]--backup-dir\f[R].
 .PP
 Example:
 .IP
@@ -30428,48 +30464,48 @@ rclone bisync /Users/someuser/some/local/path/Bisync gdrive:Bisync --backup-dir1
 .fi
 .PP
 In this example, if the user deletes a file in
-\f[C]/Users/someuser/some/local/path/Bisync\f[R], bisync will propagate
+\f[V]/Users/someuser/some/local/path/Bisync\f[R], bisync will propagate
 the delete to the other side by moving the corresponding file from
-\f[C]gdrive:Bisync\f[R] to \f[C]gdrive:BackupDir\f[R].
-If the user deletes a file from \f[C]gdrive:Bisync\f[R], bisync moves it
-from \f[C]/Users/someuser/some/local/path/Bisync\f[R] to
-\f[C]/Users/someuser/some/local/path/BackupDir\f[R].
+\f[V]gdrive:Bisync\f[R] to \f[V]gdrive:BackupDir\f[R].
+If the user deletes a file from \f[V]gdrive:Bisync\f[R], bisync moves it
+from \f[V]/Users/someuser/some/local/path/Bisync\f[R] to
+\f[V]/Users/someuser/some/local/path/BackupDir\f[R].
 .PP
 In the event of a rename due to a sync conflict, the rename is not
 considered a delete, unless a previous conflict with the same name
 already exists and would get overwritten.
 .PP
-See also: \f[C]--suffix\f[R] (https://rclone.org/docs/#suffix-suffix),
-\f[C]--suffix-keep-extension\f[R] (https://rclone.org/docs/#suffix-keep-extension)
+See also: \f[V]--suffix\f[R] (https://rclone.org/docs/#suffix-suffix),
+\f[V]--suffix-keep-extension\f[R] (https://rclone.org/docs/#suffix-keep-extension)
 .SS Operation
 .SS Runtime flow details
 .PP
-bisync retains the listings of the \f[C]Path1\f[R] and \f[C]Path2\f[R]
+bisync retains the listings of the \f[V]Path1\f[R] and \f[V]Path2\f[R]
 filesystems from the prior run.
 On each successive run it will:
 .IP \[bu] 2
-list files on \f[C]path1\f[R] and \f[C]path2\f[R], and check for changes
+list files on \f[V]path1\f[R] and \f[V]path2\f[R], and check for changes
 on each side.
-Changes include \f[C]New\f[R], \f[C]Newer\f[R], \f[C]Older\f[R], and
-\f[C]Deleted\f[R] files.
+Changes include \f[V]New\f[R], \f[V]Newer\f[R], \f[V]Older\f[R], and
+\f[V]Deleted\f[R] files.
 .IP \[bu] 2
-Propagate changes on \f[C]path1\f[R] to \f[C]path2\f[R], and vice-versa.
+Propagate changes on \f[V]path1\f[R] to \f[V]path2\f[R], and vice-versa.
 .SS Safety measures
 .IP \[bu] 2
 Lock file prevents multiple simultaneous runs when taking a while.
 This can be particularly useful if bisync is run by cron scheduler.
 .IP \[bu] 2
 Handle change conflicts non-destructively by creating
-\f[C].conflict1\f[R], \f[C].conflict2\f[R], etc.
-file versions, according to \f[C]--conflict-resolve\f[R],
-\f[C]--conflict-loser\f[R], and \f[C]--conflict-suffix\f[R] settings.
+\f[V].conflict1\f[R], \f[V].conflict2\f[R], etc.
+file versions, according to \f[V]--conflict-resolve\f[R],
+\f[V]--conflict-loser\f[R], and \f[V]--conflict-suffix\f[R] settings.
 .IP \[bu] 2
-File system access health check using \f[C]RCLONE_TEST\f[R] files (see
-the \f[C]--check-access\f[R] flag).
+File system access health check using \f[V]RCLONE_TEST\f[R] files (see
+the \f[V]--check-access\f[R] flag).
 .IP \[bu] 2
 Abort on excessive deletes - protects against a failed listing being
 interpreted as all the files were deleted.
-See the \f[C]--max-delete\f[R] and \f[C]--force\f[R] flags.
+See the \f[V]--max-delete\f[R] and \f[V]--force\f[R] flags.
 .IP \[bu] 2
 If something evil happens, bisync goes into a safe state to block damage
 by later runs.
@@ -30496,7 +30532,7 @@ File is new on Path2, does not exist on Path1
 T}@T{
 Path2 version survives
 T}@T{
-\f[C]rclone copy\f[R] Path2 to Path1
+\f[V]rclone copy\f[R] Path2 to Path1
 T}
 T{
 Path2 newer
@@ -30505,7 +30541,7 @@ File is newer on Path2, unchanged on Path1
 T}@T{
 Path2 version survives
 T}@T{
-\f[C]rclone copy\f[R] Path2 to Path1
+\f[V]rclone copy\f[R] Path2 to Path1
 T}
 T{
 Path2 deleted
@@ -30514,7 +30550,7 @@ File is deleted on Path2, unchanged on Path1
 T}@T{
 File is deleted
 T}@T{
-\f[C]rclone delete\f[R] Path1
+\f[V]rclone delete\f[R] Path1
 T}
 T{
 Path1 new
@@ -30523,7 +30559,7 @@ File is new on Path1, does not exist on Path2
 T}@T{
 Path1 version survives
 T}@T{
-\f[C]rclone copy\f[R] Path1 to Path2
+\f[V]rclone copy\f[R] Path1 to Path2
 T}
 T{
 Path1 newer
@@ -30532,7 +30568,7 @@ File is newer on Path1, unchanged on Path2
 T}@T{
 Path1 version survives
 T}@T{
-\f[C]rclone copy\f[R] Path1 to Path2
+\f[V]rclone copy\f[R] Path1 to Path2
 T}
 T{
 Path1 older
@@ -30541,7 +30577,7 @@ File is older on Path1, unchanged on Path2
 T}@T{
 \f[I]Path1 version survives\f[R]
 T}@T{
-\f[C]rclone copy\f[R] Path1 to Path2
+\f[V]rclone copy\f[R] Path1 to Path2
 T}
 T{
 Path2 older
@@ -30550,7 +30586,7 @@ File is older on Path2, unchanged on Path1
 T}@T{
 \f[I]Path2 version survives\f[R]
 T}@T{
-\f[C]rclone copy\f[R] Path2 to Path1
+\f[V]rclone copy\f[R] Path2 to Path1
 T}
 T{
 Path1 deleted
@@ -30559,7 +30595,7 @@ File no longer exists on Path1
 T}@T{
 File is deleted
 T}@T{
-\f[C]rclone delete\f[R] Path2
+\f[V]rclone delete\f[R] Path2
 T}
 .TE
 .SS Unusual sync checks
@@ -30593,11 +30629,11 @@ T}@T{
 File is new on Path1 AND new on Path2 (and Path1 version is NOT
 identical to Path2)
 T}@T{
-Conflicts handled according to \f[C]--conflict-resolve\f[R] &
-\f[C]--conflict-loser\f[R] settings
+Conflicts handled according to \f[V]--conflict-resolve\f[R] &
+\f[V]--conflict-loser\f[R] settings
 T}@T{
-default: \f[C]rclone copy\f[R] renamed \f[C]Path2.conflict2\f[R] file to
-Path1, \f[C]rclone copy\f[R] renamed \f[C]Path1.conflict1\f[R] file to
+default: \f[V]rclone copy\f[R] renamed \f[V]Path2.conflict2\f[R] file to
+Path1, \f[V]rclone copy\f[R] renamed \f[V]Path1.conflict1\f[R] file to
 Path2
 T}
 T{
@@ -30606,11 +30642,11 @@ T}@T{
 File is newer on Path2 AND also changed (newer/older/size) on Path1 (and
 Path1 version is NOT identical to Path2)
 T}@T{
-Conflicts handled according to \f[C]--conflict-resolve\f[R] &
-\f[C]--conflict-loser\f[R] settings
+Conflicts handled according to \f[V]--conflict-resolve\f[R] &
+\f[V]--conflict-loser\f[R] settings
 T}@T{
-default: \f[C]rclone copy\f[R] renamed \f[C]Path2.conflict2\f[R] file to
-Path1, \f[C]rclone copy\f[R] renamed \f[C]Path1.conflict1\f[R] file to
+default: \f[V]rclone copy\f[R] renamed \f[V]Path2.conflict2\f[R] file to
+Path1, \f[V]rclone copy\f[R] renamed \f[V]Path1.conflict1\f[R] file to
 Path2
 T}
 T{
@@ -30620,7 +30656,7 @@ File is newer on Path2 AND also deleted on Path1
 T}@T{
 Path2 version survives
 T}@T{
-\f[C]rclone copy\f[R] Path2 to Path1
+\f[V]rclone copy\f[R] Path2 to Path1
 T}
 T{
 Path2 deleted AND Path1 changed
@@ -30629,7 +30665,7 @@ File is deleted on Path2 AND changed (newer/older/size) on Path1
 T}@T{
 Path1 version survives
 T}@T{
-\f[C]rclone copy\f[R] Path1 to Path2
+\f[V]rclone copy\f[R] Path1 to Path2
 T}
 T{
 Path1 deleted AND Path2 changed
@@ -30638,22 +30674,23 @@ File is deleted on Path1 AND changed (newer/older/size) on Path2
 T}@T{
 Path2 version survives
 T}@T{
-\f[C]rclone copy\f[R] Path2 to Path1
+\f[V]rclone copy\f[R] Path2 to Path1
 T}
 .TE
 .PP
-As of \f[C]rclone v1.64\f[R], bisync is now better at detecting
+As of \f[V]rclone v1.64\f[R], bisync is now better at detecting
 \f[I]false positive\f[R] sync conflicts, which would previously have
 resulted in unnecessary renames and duplicates.
 Now, when bisync comes to a file that it wants to rename (because it is
 new/changed on both sides), it first checks whether the Path1 and Path2
 versions are currently \f[I]identical\f[R] (using the same underlying
-function as \f[C]check\f[R].) If bisync concludes that the files are
-identical, it will skip them and move on.
+function as \f[V]check\f[R].)
+If bisync concludes that the files are identical, it will skip them and
+move on.
 Otherwise, it will create renamed duplicates, as before.
 This behavior also improves the experience of renaming
 directories (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=Renamed%20directories),
-as a \f[C]--resync\f[R] is no longer required, so long as the same
+as a \f[V]--resync\f[R] is no longer required, so long as the same
 change has been made on both sides.
 .SS All files changed check
 .PP
@@ -30662,11 +30699,11 @@ changed (e.g.
 timestamps have changed due to changing the system\[aq]s timezone) then
 bisync will abort without making any changes.
 Any new files are not considered for this check.
-You could use \f[C]--force\f[R] to force the sync (whichever side has
+You could use \f[V]--force\f[R] to force the sync (whichever side has
 the changed timestamp files wins).
-Alternately, a \f[C]--resync\f[R] may be used (Path1 versions will be
+Alternately, a \f[V]--resync\f[R] may be used (Path1 versions will be
 pushed to Path2).
-Consider the situation carefully and perhaps use \f[C]--dry-run\f[R]
+Consider the situation carefully and perhaps use \f[V]--dry-run\f[R]
 before you commit to the changes.
 .SS Modification times
 .PP
@@ -30676,7 +30713,7 @@ changing the modification time and size, then bisync will \f[I]not\f[R]
 notice the change, and thus will not copy it to the other side.
 As an alternative, consider comparing by checksum (if your remotes
 support it).
-See \f[C]--compare\f[R] for details.
+See \f[V]--compare\f[R] for details.
 .SS Error handling
 .PP
 Certain bisync critical errors, such as file copy/move failing, will
@@ -30684,33 +30721,33 @@ result in a bisync lockout of following runs.
 The lockout is asserted because the sync status and history of the Path1
 and Path2 filesystems cannot be trusted, so it is safer to block any
 further changes until someone checks things out.
-The recovery is to do a \f[C]--resync\f[R] again.
+The recovery is to do a \f[V]--resync\f[R] again.
 .PP
-It is recommended to use \f[C]--resync --dry-run --verbose\f[R]
+It is recommended to use \f[V]--resync --dry-run --verbose\f[R]
 initially and \f[I]carefully\f[R] review what changes will be made
-before running the \f[C]--resync\f[R] without \f[C]--dry-run\f[R].
+before running the \f[V]--resync\f[R] without \f[V]--dry-run\f[R].
 .PP
 Most of these events come up due to an error status from an internal
 call.
-On such a critical error the \f[C]{...}.path1.lst\f[R] and
-\f[C]{...}.path2.lst\f[R] listing files are renamed to extension
-\f[C].lst-err\f[R], which blocks any future bisync runs (since the
-normal \f[C].lst\f[R] files are not found).
-Bisync keeps them under \f[C]bisync\f[R] subdirectory of the rclone
-cache directory, typically at \f[C]${HOME}/.cache/rclone/bisync/\f[R] on
+On such a critical error the \f[V]{...}.path1.lst\f[R] and
+\f[V]{...}.path2.lst\f[R] listing files are renamed to extension
+\f[V].lst-err\f[R], which blocks any future bisync runs (since the
+normal \f[V].lst\f[R] files are not found).
+Bisync keeps them under \f[V]bisync\f[R] subdirectory of the rclone
+cache directory, typically at \f[V]${HOME}/.cache/rclone/bisync/\f[R] on
 Linux.
 .PP
 Some errors are considered temporary and re-running the bisync is not
 blocked.
 The \f[I]critical return\f[R] blocks further bisync runs.
 .PP
-See also: \f[C]--resilient\f[R], \f[C]--recover\f[R],
-\f[C]--max-lock\f[R], Graceful Shutdown
+See also: \f[V]--resilient\f[R], \f[V]--recover\f[R],
+\f[V]--max-lock\f[R], Graceful Shutdown
 .SS Lock file
 .PP
 When bisync is running, a lock file is created in the bisync working
 directory, typically at
-\f[C]\[ti]/.cache/rclone/bisync/PATH1..PATH2.lck\f[R] on Linux.
+\f[V]\[ti]/.cache/rclone/bisync/PATH1..PATH2.lck\f[R] on Linux.
 If bisync should crash or hang, the lock file will remain in place and
 block any further runs of bisync \f[I]for the same paths\f[R].
 Delete the lock file as part of debugging the situation.
@@ -30719,7 +30756,7 @@ The lock file effectively blocks follow-on (e.g., scheduled by
 The lock file contains \f[I]PID\f[R] of the blocking process, which may
 help in debug.
 Lock files can be set to automatically expire after a certain amount of
-time, using the \f[C]--max-lock\f[R] flag.
+time, using the \f[V]--max-lock\f[R] flag.
 .PP
 \f[B]Note\f[R] that while concurrent bisync runs are allowed, \f[I]be
 very cautious\f[R] that there is no overlap in the trees being synched
@@ -30727,14 +30764,14 @@ between concurrent runs, lest there be replicated files, deleted files
 and general mayhem.
 .SS Return codes
 .PP
-\f[C]rclone bisync\f[R] returns the following codes to calling program:
-- \f[C]0\f[R] on a successful run, - \f[C]1\f[R] for a non-critical
-failing run (a rerun may be successful), - \f[C]2\f[R] for a critically
-aborted run (requires a \f[C]--resync\f[R] to recover).
+\f[V]rclone bisync\f[R] returns the following codes to calling program:
+- \f[V]0\f[R] on a successful run, - \f[V]1\f[R] for a non-critical
+failing run (a rerun may be successful), - \f[V]2\f[R] for a critically
+aborted run (requires a \f[V]--resync\f[R] to recover).
 .SS Graceful Shutdown
 .PP
 Bisync has a \[dq]Graceful Shutdown\[dq] mode which is activated by
-sending \f[C]SIGINT\f[R] or pressing \f[C]Ctrl+C\f[R] during a run.
+sending \f[V]SIGINT\f[R] or pressing \f[V]Ctrl+C\f[R] during a run.
 Once triggered, bisync will use best efforts to exit cleanly before the
 timer runs out.
 If bisync is in the middle of transferring files, it will attempt to
@@ -30743,26 +30780,26 @@ more.
 If it cannot do so within 30 seconds, it will cancel the in-progress
 transfers at that point and then give itself a maximum of 60 seconds to
 wrap up, save its state for next time, and exit.
-With the \f[C]-vP\f[R] flags you will see constant status updates and a
+With the \f[V]-vP\f[R] flags you will see constant status updates and a
 final confirmation of whether or not the graceful shutdown was
 successful.
 .PP
 At any point during the \[dq]Graceful Shutdown\[dq] sequence, a second
-\f[C]SIGINT\f[R] or \f[C]Ctrl+C\f[R] will trigger an immediate,
+\f[V]SIGINT\f[R] or \f[V]Ctrl+C\f[R] will trigger an immediate,
 un-graceful exit, which will leave things in a messier state.
 Usually a robust recovery will still be possible if using
-\f[C]--recover\f[R] mode, otherwise you will need to do a
-\f[C]--resync\f[R].
+\f[V]--recover\f[R] mode, otherwise you will need to do a
+\f[V]--resync\f[R].
 .PP
 If you plan to use Graceful Shutdown mode, it is recommended to use
-\f[C]--resilient\f[R] and \f[C]--recover\f[R], and it is important to
-NOT use \f[C]--inplace\f[R] (https://rclone.org/docs/#inplace),
+\f[V]--resilient\f[R] and \f[V]--recover\f[R], and it is important to
+NOT use \f[V]--inplace\f[R] (https://rclone.org/docs/#inplace),
 otherwise you risk leaving partially-written files on one side, which
 may be confused for real files on the next run.
 Note also that in the event of an abrupt interruption, a lock file will
 be left behind to block concurrent runs.
 You will need to delete it before you can proceed with the next run (or
-wait for it to expire on its own, if using \f[C]--max-lock\f[R].)
+wait for it to expire on its own, if using \f[V]--max-lock\f[R].)
 .SS Limitations
 .SS Supported backends
 .PP
@@ -30775,27 +30812,27 @@ If it works, or sorta works, please let us know and we\[aq]ll update the
 list.
 Run the test suite to check for proper operation as described below.
 .PP
-The first release of \f[C]rclone bisync\f[R] required both underlying
+The first release of \f[V]rclone bisync\f[R] required both underlying
 backends to support modification times, and refused to run otherwise.
-This limitation has been lifted as of \f[C]v1.66\f[R], as bisync now
+This limitation has been lifted as of \f[V]v1.66\f[R], as bisync now
 supports comparing checksum and/or size instead of (or in addition to)
 modtime.
-See \f[C]--compare\f[R] for details.
+See \f[V]--compare\f[R] for details.
 .SS Concurrent modifications
 .PP
 When using \f[B]Local, FTP or SFTP\f[R] remotes with
-\f[C]--inplace\f[R] (https://rclone.org/docs/#inplace), rclone does not
+\f[V]--inplace\f[R] (https://rclone.org/docs/#inplace), rclone does not
 create \f[I]temporary\f[R] files at the destination when copying, and
 thus if the connection is lost the created file may be corrupt, which
 will likely propagate back to the original path on the next sync,
 resulting in data loss.
-It is therefore recommended to \f[I]omit\f[R] \f[C]--inplace\f[R].
+It is therefore recommended to \f[I]omit\f[R] \f[V]--inplace\f[R].
 .PP
 Files that \f[B]change during\f[R] a bisync run may result in data loss.
-Prior to \f[C]rclone v1.66\f[R], this was commonly seen in highly
+Prior to \f[V]rclone v1.66\f[R], this was commonly seen in highly
 dynamic environments, where the filesystem was getting hammered by
 running processes during the sync.
-As of \f[C]rclone v1.66\f[R], bisync was redesigned to use a
+As of \f[V]rclone v1.66\f[R], bisync was redesigned to use a
 \[dq]snapshot\[dq] model, greatly reducing the risks from changes during
 a sync.
 Changes that are not detected during the current sync will now be
@@ -30806,32 +30843,33 @@ internally rechecked next time, for added safety.
 It should therefore no longer be necessary to sync only at quiet times
 -- however, note that an error can still occur if a file happens to
 change at the exact moment it\[aq]s being read/written by bisync (same
-as would happen in \f[C]rclone sync\f[R].) (See also:
-\f[C]--ignore-checksum\f[R] (https://rclone.org/docs/#ignore-checksum),
-\f[C]--local-no-check-updated\f[R] (https://rclone.org/local/#local-no-check-updated))
+as would happen in \f[V]rclone sync\f[R].)
+(See also:
+\f[V]--ignore-checksum\f[R] (https://rclone.org/docs/#ignore-checksum),
+\f[V]--local-no-check-updated\f[R] (https://rclone.org/local/#local-no-check-updated))
 .SS Empty directories
 .PP
 By default, new/deleted empty directories on one path are \f[I]not\f[R]
 propagated to the other side.
 This is because bisync (and rclone) natively works on files, not
 directories.
-However, this can be changed with the \f[C]--create-empty-src-dirs\f[R]
+However, this can be changed with the \f[V]--create-empty-src-dirs\f[R]
 flag, which works in much the same way as in
-\f[C]sync\f[R] (https://rclone.org/commands/rclone_sync/) and
-\f[C]copy\f[R] (https://rclone.org/commands/rclone_copy/).
+\f[V]sync\f[R] (https://rclone.org/commands/rclone_sync/) and
+\f[V]copy\f[R] (https://rclone.org/commands/rclone_copy/).
 When used, empty directories created or deleted on one side will also be
 created or deleted on the other side.
-The following should be noted: * \f[C]--create-empty-src-dirs\f[R] is
-not compatible with \f[C]--remove-empty-dirs\f[R].
+The following should be noted: * \f[V]--create-empty-src-dirs\f[R] is
+not compatible with \f[V]--remove-empty-dirs\f[R].
 Use only one or the other (or neither).
 * It is not recommended to switch back and forth between
-\f[C]--create-empty-src-dirs\f[R] and the default (no
-\f[C]--create-empty-src-dirs\f[R]) without running \f[C]--resync\f[R].
+\f[V]--create-empty-src-dirs\f[R] and the default (no
+\f[V]--create-empty-src-dirs\f[R]) without running \f[V]--resync\f[R].
 This is because it may appear as though all directories (not just the
 empty ones) were created/deleted, when actually you\[aq]ve just toggled
 between making them visible/invisible to bisync.
 It looks scarier than it is, but it\[aq]s still probably best to stick
-to one or the other, and use \f[C]--resync\f[R] when you need to switch.
+to one or the other, and use \f[V]--resync\f[R] when you need to switch.
 .SS Renamed directories
 .PP
 By default, renaming a folder on the Path1 side results in deleting all
@@ -30841,53 +30879,53 @@ Bisync sees this as all files in the old directory name as deleted and
 all files in the new directory name as new.
 .PP
 A recommended solution is to use
-\f[C]--track-renames\f[R] (https://rclone.org/docs/#track-renames),
-which is now supported in bisync as of \f[C]rclone v1.66\f[R].
-Note that \f[C]--track-renames\f[R] is not available during
-\f[C]--resync\f[R], as \f[C]--resync\f[R] does not delete anything
-(\f[C]--track-renames\f[R] only supports \f[C]sync\f[R], not
-\f[C]copy\f[R].)
+\f[V]--track-renames\f[R] (https://rclone.org/docs/#track-renames),
+which is now supported in bisync as of \f[V]rclone v1.66\f[R].
+Note that \f[V]--track-renames\f[R] is not available during
+\f[V]--resync\f[R], as \f[V]--resync\f[R] does not delete anything
+(\f[V]--track-renames\f[R] only supports \f[V]sync\f[R], not
+\f[V]copy\f[R].)
 .PP
 Otherwise, the most effective and efficient method of renaming a
 directory is to rename it to the same name on both sides.
-(As of \f[C]rclone v1.64\f[R], a \f[C]--resync\f[R] is no longer
+(As of \f[V]rclone v1.64\f[R], a \f[V]--resync\f[R] is no longer
 required after doing so, as bisync will automatically detect that Path1
 and Path2 are in agreement.)
-.SS \f[C]--fast-list\f[R] used by default
+.SS \f[V]--fast-list\f[R] used by default
 .PP
 Unlike most other rclone commands, bisync uses
-\f[C]--fast-list\f[R] (https://rclone.org/docs/#fast-list) by default,
+\f[V]--fast-list\f[R] (https://rclone.org/docs/#fast-list) by default,
 for backends that support it.
 In many cases this is desirable, however, there are some scenarios in
-which bisync could be faster \f[I]without\f[R] \f[C]--fast-list\f[R],
+which bisync could be faster \f[I]without\f[R] \f[V]--fast-list\f[R],
 and there is also a known issue concerning Google Drive users with many
 empty
 directories (https://github.com/rclone/rclone/commit/cbf3d4356135814921382dd3285d859d15d0aa77).
-For now, the recommended way to avoid using \f[C]--fast-list\f[R] is to
-add \f[C]--disable ListR\f[R] to all bisync commands.
+For now, the recommended way to avoid using \f[V]--fast-list\f[R] is to
+add \f[V]--disable ListR\f[R] to all bisync commands.
 The default behavior may change in a future version.
 .SS Case (and unicode) sensitivity
 .PP
-As of \f[C]v1.66\f[R], case and unicode form differences no longer cause
+As of \f[V]v1.66\f[R], case and unicode form differences no longer cause
 critical errors, and normalization (when comparing between filesystems)
 is handled according to the same flags and defaults as
-\f[C]rclone sync\f[R].
+\f[V]rclone sync\f[R].
 See the following options (all of which are supported by bisync) to
 control this behavior more granularly: -
-\f[C]--fix-case\f[R] (https://rclone.org/docs/#fix-case) -
-\f[C]--ignore-case-sync\f[R] (https://rclone.org/docs/#ignore-case-sync)
+\f[V]--fix-case\f[R] (https://rclone.org/docs/#fix-case) -
+\f[V]--ignore-case-sync\f[R] (https://rclone.org/docs/#ignore-case-sync)
 -
-\f[C]--no-unicode-normalization\f[R] (https://rclone.org/docs/#no-unicode-normalization)
+\f[V]--no-unicode-normalization\f[R] (https://rclone.org/docs/#no-unicode-normalization)
 -
-\f[C]--local-unicode-normalization\f[R] (https://rclone.org/local/#local-unicode-normalization)
+\f[V]--local-unicode-normalization\f[R] (https://rclone.org/local/#local-unicode-normalization)
 and
-\f[C]--local-case-sensitive\f[R] (https://rclone.org/local/#local-case-sensitive)
+\f[V]--local-case-sensitive\f[R] (https://rclone.org/local/#local-case-sensitive)
 (caution: these are normally not what you want.)
 .PP
-Note that in the (probably rare) event that \f[C]--fix-case\f[R] is used
+Note that in the (probably rare) event that \f[V]--fix-case\f[R] is used
 AND a file is new/changed on both sides AND the checksums match AND the
 filename case does not match, the Path1 filename is considered the
-winner, for the purposes of \f[C]--fix-case\f[R] (Path2 will be renamed
+winner, for the purposes of \f[V]--fix-case\f[R] (Path2 will be renamed
 to match it).
 .SS Windows support
 .PP
@@ -30895,19 +30933,19 @@ Bisync has been tested on Windows 8.1, Windows 10 Pro 64-bit and on
 Windows GitHub runners.
 .PP
 Drive letters are allowed, including drive letters mapped to network
-drives (\f[C]rclone bisync J:\[rs]localsync GDrive:\f[R]).
+drives (\f[V]rclone bisync J:\[rs]localsync GDrive:\f[R]).
 If a drive letter is omitted, the shell current drive is the default.
-Drive letters are a single character follows by \f[C]:\f[R], so cloud
+Drive letters are a single character follows by \f[V]:\f[R], so cloud
 names must be more than one character long.
 .PP
 Absolute paths (with or without a drive letter), and relative paths
 (with or without a drive letter) are supported.
 .PP
 Working directory is created at
-\f[C]C:\[rs]Users\[rs]MyLogin\[rs]AppData\[rs]Local\[rs]rclone\[rs]bisync\f[R].
+\f[V]C:\[rs]Users\[rs]MyLogin\[rs]AppData\[rs]Local\[rs]rclone\[rs]bisync\f[R].
 .PP
-Note that bisync output may show a mix of forward \f[C]/\f[R] and back
-\f[C]\[rs]\f[R] slashes.
+Note that bisync output may show a mix of forward \f[V]/\f[R] and back
+\f[V]\[rs]\f[R] slashes.
 .PP
 Be careful of case independent directory and file naming on Windows vs.
 case dependent Linux
@@ -30916,13 +30954,13 @@ case dependent Linux
 See filtering documentation (https://rclone.org/filtering/) for how
 filter rules are written and interpreted.
 .PP
-Bisync\[aq]s \f[C]--filters-file\f[R] flag slightly extends the
+Bisync\[aq]s \f[V]--filters-file\f[R] flag slightly extends the
 rclone\[aq]s
 --filter-from (https://rclone.org/filtering/#filter-from-read-filtering-patterns-from-a-file)
 filtering mechanism.
 For a given bisync run you may provide \f[I]only one\f[R]
-\f[C]--filters-file\f[R].
-The \f[C]--include*\f[R], \f[C]--exclude*\f[R], and \f[C]--filter\f[R]
+\f[V]--filters-file\f[R].
+The \f[V]--include*\f[R], \f[V]--exclude*\f[R], and \f[V]--filter\f[R]
 flags are also supported.
 .SS How to filter directories
 .PP
@@ -30933,7 +30971,7 @@ Examples of directory trees (always beneath the Path1/Path2 root level)
 you may want to exclude from your sync: - Directory trees containing
 only software build intermediate files.
 - Directory trees containing application temporary files and data such
-as the Windows \f[C]C:\[rs]Users\[rs]MyLogin\[rs]AppData\[rs]\f[R] tree.
+as the Windows \f[V]C:\[rs]Users\[rs]MyLogin\[rs]AppData\[rs]\f[R] tree.
 - Directory trees containing files that are large, less important, or
 are getting thrashed continuously by ongoing processes.
 .PP
@@ -30947,9 +30985,9 @@ Begin with excluding directory trees:
 .RS 4
 .IP \[bu] 2
 e.g.
-\[ga]- /AppData/\[ga]
+\f[V]- /AppData/\f[R]
 .IP \[bu] 2
-\f[C]**\f[R] on the end is not necessary.
+\f[V]**\f[R] on the end is not necessary.
 Once a given directory level is excluded then everything beneath it
 won\[aq]t be looked at by rclone.
 .IP \[bu] 2
@@ -30975,20 +31013,20 @@ else\f[R]
 Include select directories:
 .RS 4
 .IP \[bu] 2
-Add lines like: \[ga]+ /Documents/PersonalFiles/**\[ga] to select which
+Add lines like: \f[V]+ /Documents/PersonalFiles/**\f[R] to select which
 directories to include in the sync.
 .IP \[bu] 2
-\f[C]**\f[R] on the end specifies to include the full depth of the
+\f[V]**\f[R] on the end specifies to include the full depth of the
 specified tree.
 .IP \[bu] 2
 With Include-style filters, files at the Path1/Path2 root are not
 included.
-They may be included with \[ga]+ /*\[ga].
+They may be included with \f[V]+ /*\f[R].
 .IP \[bu] 2
 Place RCLONE_TEST files within these included directory trees.
 They will only be looked for in these directory trees.
 .IP \[bu] 2
-Finish by excluding everything else by adding \[ga]- **\[ga] at the end
+Finish by excluding everything else by adding \f[V]- **\f[R] at the end
 of the filters file.
 .IP \[bu] 2
 Disregard step 4.
@@ -30998,10 +31036,10 @@ Exclude select directories:
 .RS 4
 .IP \[bu] 2
 Add more lines like in step 1.
-For example: \f[C]-/Desktop/tempfiles/\f[R], or \[ga]-
-/testdir/\f[C].    Again, a\f[R]**\[ga] on the end is not necessary.
+For example: \f[V]-/Desktop/tempfiles/\f[R], or \f[V]- /testdir/\f[R].
+Again, a \f[V]**\f[R] on the end is not necessary.
 .IP \[bu] 2
-Do \f[I]not\f[R] add a \[ga]- **\[ga] in the file.
+Do \f[I]not\f[R] add a \f[V]- **\f[R] in the file.
 Without this line, everything will be included that has not been
 explicitly excluded.
 .IP \[bu] 2
@@ -31013,17 +31051,17 @@ documentation (https://rclone.org/filtering/):
 .IP \[bu] 2
 Lines may start with spaces and tabs - rclone strips leading whitespace.
 .IP \[bu] 2
-If the first non-whitespace character is a \f[C]#\f[R] then the line is
+If the first non-whitespace character is a \f[V]#\f[R] then the line is
 a comment and will be ignored.
 .IP \[bu] 2
 Blank lines are ignored.
 .IP \[bu] 2
 The first non-whitespace character on a filter line must be a
-\f[C]+\f[R] or \f[C]-\f[R].
+\f[V]+\f[R] or \f[V]-\f[R].
 .IP \[bu] 2
-Exactly 1 space is allowed between the \f[C]+/-\f[R] and the path term.
+Exactly 1 space is allowed between the \f[V]+/-\f[R] and the path term.
 .IP \[bu] 2
-Only forward slashes (\f[C]/\f[R]) are used in path terms, even on
+Only forward slashes (\f[V]/\f[R]) are used in path terms, even on
 Windows.
 .IP \[bu] 2
 The rest of the line is taken as the path term.
@@ -31031,30 +31069,32 @@ Trailing whitespace is taken literally, and probably is an error.
 .SS Example include-style filters for Windows user directories
 .PP
 This Windows \f[I]include-style\f[R] example is based on the sync root
-(Path1) set to \f[C]C:\[rs]Users\[rs]MyLogin\f[R].
+(Path1) set to \f[V]C:\[rs]Users\[rs]MyLogin\f[R].
 The strategy is to select specific directories to be synched with a
 network drive (Path2).
 .IP \[bu] 2
-\[ga]- /AppData/\[ga] excludes an entire tree of Windows stored stuff
+\f[V]- /AppData/\f[R] excludes an entire tree of Windows stored stuff
 that need not be synched.
 In my case, AppData has >11 GB of stuff I don\[aq]t care about, and
 there are some subdirectories beneath AppData that are not accessible to
 my user login, resulting in bisync critical aborts.
 .IP \[bu] 2
 Windows creates cache files starting with both upper and lowercase
-\f[C]NTUSER\f[R] at \f[C]C:\[rs]Users\[rs]MyLogin\f[R].
+\f[V]NTUSER\f[R] at \f[V]C:\[rs]Users\[rs]MyLogin\f[R].
 These files may be dynamic, locked, and are generally \f[I]don\[aq]t
 care\f[R].
 .IP \[bu] 2
 There are just a few directories with \f[I]my\f[R] data that I do want
-synched, in the form of \[ga]+
-/\f[C]. By selecting only the directory trees I   want to avoid the dozen plus directories that various apps make   at\f[R]C:\[ga].
+synched, in the form of \f[V]+ /<path>\f[R].
+By selecting only the directory trees I want to avoid the dozen plus
+directories that various apps make at
+\f[V]C:\[rs]Users\[rs]MyLogin\[rs]Documents\f[R].
 .IP \[bu] 2
 Include files in the root of the sync point,
-\f[C]C:\[rs]Users\[rs]MyLogin\f[R], by adding the \[ga]+ /*\[ga] line.
+\f[V]C:\[rs]Users\[rs]MyLogin\f[R], by adding the \f[V]+ /*\f[R] line.
 .IP \[bu] 2
-This is an Include-style filters file, therefore it ends with \[ga]-
-**\[ga] which excludes everything not explicitly included.
+This is an Include-style filters file, therefore it ends with
+\f[V]- **\f[R] which excludes everything not explicitly included.
 .IP
 .nf
 \f[C]
@@ -31073,31 +31113,31 @@ This is an Include-style filters file, therefore it ends with \[ga]-
 .fi
 .PP
 Note also that Windows implements several \[dq]library\[dq] links such
-as \f[C]C:\[rs]Users\[rs]MyLogin\[rs]My Documents\[rs]My Music\f[R]
-pointing to \f[C]C:\[rs]Users\[rs]MyLogin\[rs]Music\f[R].
-rclone sees these as links, so you must add \f[C]--links\f[R] to the
+as \f[V]C:\[rs]Users\[rs]MyLogin\[rs]My Documents\[rs]My Music\f[R]
+pointing to \f[V]C:\[rs]Users\[rs]MyLogin\[rs]Music\f[R].
+rclone sees these as links, so you must add \f[V]--links\f[R] to the
 bisync command line if you which to follow these links.
 I find that I get permission errors in trying to follow the links, so I
-don\[aq]t include the rclone \f[C]--links\f[R] flag, but then you get
-lots of \f[C]Can\[aq]t follow symlink\&...\f[R] noise from rclone about
+don\[aq]t include the rclone \f[V]--links\f[R] flag, but then you get
+lots of \f[V]Can\[aq]t follow symlink\&...\f[R] noise from rclone about
 not following the links.
-This noise can be quashed by adding \f[C]--quiet\f[R] to the bisync
+This noise can be quashed by adding \f[V]--quiet\f[R] to the bisync
 command line.
 .SS Example exclude-style filters files for use with Dropbox
 .IP \[bu] 2
 Dropbox disallows synching the listed temporary and configuration/data
 files.
-The \[ga]- \[ga] filters exclude these files where ever they may occur
-in the sync tree.
+The \f[V]- <filename>\f[R] filters exclude these files where ever they
+may occur in the sync tree.
 Consider adding similar exclusions for file types you don\[aq]t need to
 sync, such as core dump and software build files.
 .IP \[bu] 2
-bisync testing creates \f[C]/testdir/\f[R] at the top level of the sync
+bisync testing creates \f[V]/testdir/\f[R] at the top level of the sync
 tree, and usually deletes the tree after the test.
-If a normal sync should run while the \f[C]/testdir/\f[R] tree exists
-the \f[C]--check-access\f[R] phase may fail due to unbalanced
+If a normal sync should run while the \f[V]/testdir/\f[R] tree exists
+the \f[V]--check-access\f[R] phase may fail due to unbalanced
 RCLONE_TEST files.
-The \[ga]- /testdir/\[ga] filter blocks this tree from being synched.
+The \f[V]- /testdir/\f[R] filter blocks this tree from being synched.
 You don\[aq]t need this exclusion if you are not doing bisync
 development testing.
 .IP \[bu] 2
@@ -31134,10 +31174,10 @@ root.
 .SS How --check-access handles filters
 .PP
 At the start of a bisync run, listings are gathered for Path1 and Path2
-while using the user\[aq]s \f[C]--filters-file\f[R].
+while using the user\[aq]s \f[V]--filters-file\f[R].
 During the check access phase, bisync scans these listings for
-\f[C]RCLONE_TEST\f[R] files.
-Any \f[C]RCLONE_TEST\f[R] files hidden by the \f[C]--filters-file\f[R]
+\f[V]RCLONE_TEST\f[R] files.
+Any \f[V]RCLONE_TEST\f[R] files hidden by the \f[V]--filters-file\f[R]
 are \f[I]not\f[R] in the listings and thus not checked during the check
 access phase.
 .SS Troubleshooting
@@ -31172,15 +31212,15 @@ The second has no deltas between local and remote.
 .fi
 .SS Dry run oddity
 .PP
-The \f[C]--dry-run\f[R] messages may indicate that it would try to
+The \f[V]--dry-run\f[R] messages may indicate that it would try to
 delete some files.
 For example, if a file is new on Path2 and does not exist on Path1 then
-it would normally be copied to Path1, but with \f[C]--dry-run\f[R]
+it would normally be copied to Path1, but with \f[V]--dry-run\f[R]
 enabled those copies don\[aq]t happen, which leads to the attempted
 delete on Path2, blocked again by --dry-run:
-\f[C]... Not deleting as --dry-run\f[R].
+\f[V]... Not deleting as --dry-run\f[R].
 .PP
-This whole confusing situation is an artifact of the \f[C]--dry-run\f[R]
+This whole confusing situation is an artifact of the \f[V]--dry-run\f[R]
 flag.
 Scrutinize the proposed deletes carefully, and if the files would have
 been copied to Path1 then the threatened deletes on Path2 may be
@@ -31188,11 +31228,11 @@ disregarded.
 .SS Retries
 .PP
 Rclone has built-in retries.
-If you run with \f[C]--verbose\f[R] you\[aq]ll see error and retry
+If you run with \f[V]--verbose\f[R] you\[aq]ll see error and retry
 messages such as shown below.
 This is usually not a bug.
-If at the end of the run, you see \f[C]Bisync successful\f[R] and not
-\f[C]Bisync critical error\f[R] or \f[C]Bisync aborted\f[R] then the run
+If at the end of the run, you see \f[V]Bisync successful\f[R] and not
+\f[V]Bisync critical error\f[R] or \f[V]Bisync aborted\f[R] then the run
 was successful, and you can ignore the error messages.
 .PP
 The following run shows an intermittent fail.
@@ -31219,7 +31259,7 @@ was successful.
 .fi
 .PP
 This log shows a \f[I]Critical failure\f[R] which requires a
-\f[C]--resync\f[R] to recover from.
+\f[V]--resync\f[R] to recover from.
 See the Runtime Error Handling section.
 .IP
 .nf
@@ -31235,60 +31275,61 @@ See the Runtime Error Handling section.
 .fi
 .SS Denied downloads of \[dq]infected\[dq] or \[dq]abusive\[dq] files
 .PP
-Google Drive has a filter for certain file types (\f[C].exe\f[R],
-\f[C].apk\f[R], et cetera) that by default cannot be copied from Google
+Google Drive has a filter for certain file types (\f[V].exe\f[R],
+\f[V].apk\f[R], et cetera) that by default cannot be copied from Google
 Drive to the local filesystem.
-If you are having problems, run with \f[C]--verbose\f[R] to see
+If you are having problems, run with \f[V]--verbose\f[R] to see
 specifically which files are generating complaints.
 If the error is
-\f[C]This file has been identified as malware or spam and cannot be downloaded\f[R],
+\f[V]This file has been identified as malware or spam and cannot be downloaded\f[R],
 consider using the flag
 --drive-acknowledge-abuse (https://rclone.org/drive/#drive-acknowledge-abuse).
 .SS Google Docs (and other files of unknown size)
 .PP
-As of \f[C]v1.66\f[R], Google
+As of \f[V]v1.66\f[R], Google
 Docs (https://rclone.org/drive/#import-export-of-google-documents)
-(including Google Sheets, Slides, etc.) are now supported in bisync,
-subject to the same options, defaults, and limitations as in
-\f[C]rclone sync\f[R].
+(including Google Sheets, Slides, etc.)
+are now supported in bisync, subject to the same options, defaults, and
+limitations as in \f[V]rclone sync\f[R].
 When bisyncing drive with non-drive backends, the drive -> non-drive
 direction is controlled by
-\f[C]--drive-export-formats\f[R] (https://rclone.org/drive/#drive-export-formats)
-(default \f[C]\[dq]docx,xlsx,pptx,svg\[dq]\f[R]) and the non-drive ->
+\f[V]--drive-export-formats\f[R] (https://rclone.org/drive/#drive-export-formats)
+(default \f[V]\[dq]docx,xlsx,pptx,svg\[dq]\f[R]) and the non-drive ->
 drive direction is controlled by
-\f[C]--drive-import-formats\f[R] (https://rclone.org/drive/#drive-import-formats)
+\f[V]--drive-import-formats\f[R] (https://rclone.org/drive/#drive-import-formats)
 (default none.)
 .PP
 For example, with the default export/import formats, a Google Sheet on
-the drive side will be synced to an \f[C].xlsx\f[R] file on the
+the drive side will be synced to an \f[V].xlsx\f[R] file on the
 non-drive side.
-In the reverse direction, \f[C].xlsx\f[R] files with filenames that
+In the reverse direction, \f[V].xlsx\f[R] files with filenames that
 match an existing Google Sheet will be synced to that Google Sheet,
-while \f[C].xlsx\f[R] files that do NOT match an existing Google Sheet
-will be copied to drive as normal \f[C].xlsx\f[R] files (without
+while \f[V].xlsx\f[R] files that do NOT match an existing Google Sheet
+will be copied to drive as normal \f[V].xlsx\f[R] files (without
 conversion to Sheets, although the Google Drive web browser UI may still
 give you the option to open it as one.)
 .PP
-If \f[C]--drive-import-formats\f[R] is set (it\[aq]s not, by default),
+If \f[V]--drive-import-formats\f[R] is set (it\[aq]s not, by default),
 then all of the specified formats will be converted to Google Docs, if
 there is no existing Google Doc with a matching name.
 Caution: such conversion can be quite lossy, and in most cases it\[aq]s
 probably not what you want!
 .PP
 To bisync Google Docs as URL shortcut links (in a manner similar to
-\[dq]Drive for Desktop\[dq]), use: \f[C]--drive-export-formats url\f[R]
+\[dq]Drive for Desktop\[dq]), use: \f[V]--drive-export-formats url\f[R]
 (or
 alternatives (https://rclone.org/drive/#exportformats:~:text=available%20Google%20Documents.-,Extension,macOS,-Standard%20options).)
 .PP
 Note that these link files cannot be edited on the non-drive side -- you
 will get errors if you try to sync an edited link file back to drive.
 They CAN be deleted (it will result in deleting the corresponding Google
-Doc.) If you create a \f[C].url\f[R] file on the non-drive side that
-does not match an existing Google Doc, bisyncing it will just result in
-copying the literal \f[C].url\f[R] file over to drive (no Google Doc
-will be created.) So, as a general rule of thumb, think of them as
-read-only placeholders on the non-drive side, and make all your changes
-on the drive side.
+Doc.)
+If you create a \f[V].url\f[R] file on the non-drive side that does not
+match an existing Google Doc, bisyncing it will just result in copying
+the literal \f[V].url\f[R] file over to drive (no Google Doc will be
+created.)
+So, as a general rule of thumb, think of them as read-only placeholders
+on the non-drive side, and make all your changes on the drive side.
 .PP
 Likewise, even with other export-formats, it is best to only move/rename
 Google Docs on the drive side.
@@ -31296,20 +31337,20 @@ This is because otherwise, bisync will interpret this as a file deleted
 and another created, and accordingly, it will delete the Google Doc and
 create a new file at the new path.
 (Whether or not that new file is a Google Doc depends on
-\f[C]--drive-import-formats\f[R].)
+\f[V]--drive-import-formats\f[R].)
 .PP
 Lastly, take note that all Google Docs on the drive side have a size of
-\f[C]-1\f[R] and no checksum.
-Therefore, they cannot be reliably synced with the \f[C]--checksum\f[R]
-or \f[C]--size-only\f[R] flags.
+\f[V]-1\f[R] and no checksum.
+Therefore, they cannot be reliably synced with the \f[V]--checksum\f[R]
+or \f[V]--size-only\f[R] flags.
 (To be exact: they will still get created/deleted, and bisync\[aq]s
 delta engine will notice changes and queue them for syncing, but the
-underlying sync function will consider them identical and skip them.) To
-work around this, use the default (modtime and size) instead of
-\f[C]--checksum\f[R] or \f[C]--size-only\f[R].
+underlying sync function will consider them identical and skip them.)
+To work around this, use the default (modtime and size) instead of
+\f[V]--checksum\f[R] or \f[V]--size-only\f[R].
 .PP
 To ignore Google Docs entirely, use
-\f[C]--drive-skip-gdocs\f[R] (https://rclone.org/drive/#drive-skip-gdocs).
+\f[V]--drive-skip-gdocs\f[R] (https://rclone.org/drive/#drive-skip-gdocs).
 .SS Usage examples
 .SS Cron
 .PP
@@ -31337,10 +31378,10 @@ See crontab
 syntax (https://www.man7.org/linux/man-pages/man1/crontab.1p.html#INPUT_FILES)
 for the details of crontab time interval expressions.
 .PP
-If you run \f[C]rclone bisync\f[R] as a cron job, redirect stdout/stderr
+If you run \f[V]rclone bisync\f[R] as a cron job, redirect stdout/stderr
 to a file.
 The 2nd example runs a sync to Dropbox every hour and logs all stdout
-(via the \f[C]>>\f[R]) and stderr (via \f[C]2>&1\f[R]) to a log file.
+(via the \f[V]>>\f[R]) and stderr (via \f[V]2>&1\f[R]) to a log file.
 .IP
 .nf
 \f[C]
@@ -31363,40 +31404,40 @@ bisync for this local crypt directory to a directory outside of the main
 sync tree.
 .SS Linux server setup
 .IP \[bu] 2
-\f[C]/path/to/DBoxroot\f[R] is the root of my local sync tree.
+\f[V]/path/to/DBoxroot\f[R] is the root of my local sync tree.
 There are numerous subdirectories.
 .IP \[bu] 2
-\f[C]/path/to/DBoxroot/crypt\f[R] is the root subdirectory for files
+\f[V]/path/to/DBoxroot/crypt\f[R] is the root subdirectory for files
 that are encrypted.
 This local directory target is setup as an rclone crypt remote named
-\f[C]Dropcrypt:\f[R].
+\f[V]Dropcrypt:\f[R].
 See rclone.conf snippet below.
 .IP \[bu] 2
-\f[C]/path/to/my/unencrypted/files\f[R] is the root of my sensitive
+\f[V]/path/to/my/unencrypted/files\f[R] is the root of my sensitive
 files - not encrypted, not within the tree synched to Dropbox.
 .IP \[bu] 2
 To sync my local unencrypted files with the encrypted Dropbox versions I
-manually run \f[C]bisync /path/to/my/unencrypted/files DropCrypt:\f[R].
+manually run \f[V]bisync /path/to/my/unencrypted/files DropCrypt:\f[R].
 This step could be bundled into a script to run before and after the
 full Dropbox tree sync in the last step, thus actively keeping the
 sensitive files in sync.
 .IP \[bu] 2
-\f[C]bisync /path/to/DBoxroot Dropbox:\f[R] runs periodically via cron,
+\f[V]bisync /path/to/DBoxroot Dropbox:\f[R] runs periodically via cron,
 keeping my full local sync tree in sync with Dropbox.
 .SS Windows notebook setup
 .IP \[bu] 2
 The Dropbox client runs keeping the local tree
-\f[C]C:\[rs]Users\[rs]MyLogin\[rs]Dropbox\f[R] always in sync with
+\f[V]C:\[rs]Users\[rs]MyLogin\[rs]Dropbox\f[R] always in sync with
 Dropbox.
-I could have used \f[C]rclone bisync\f[R] instead.
+I could have used \f[V]rclone bisync\f[R] instead.
 .IP \[bu] 2
 A separate directory tree at
-\f[C]C:\[rs]Users\[rs]MyLogin\[rs]Documents\[rs]DropLocal\f[R] hosts the
+\f[V]C:\[rs]Users\[rs]MyLogin\[rs]Documents\[rs]DropLocal\f[R] hosts the
 tree of unencrypted files/folders.
 .IP \[bu] 2
 To sync my local unencrypted files with the encrypted Dropbox versions I
 manually run the following command:
-\f[C]rclone bisync C:\[rs]Users\[rs]MyLogin\[rs]Documents\[rs]DropLocal Dropcrypt:\f[R].
+\f[V]rclone bisync C:\[rs]Users\[rs]MyLogin\[rs]Documents\[rs]DropLocal Dropcrypt:\f[R].
 .IP \[bu] 2
 The Dropbox client then syncs the changes with Dropbox.
 .SS rclone.conf snippet
@@ -31423,12 +31464,12 @@ You should read this section only if you are developing for rclone.
 You need to have rclone source code locally to work with bisync tests.
 .PP
 Bisync has a dedicated test framework implemented in the
-\f[C]bisync_test.go\f[R] file located in the rclone source tree.
-The test suite is based on the \f[C]go test\f[R] command.
+\f[V]bisync_test.go\f[R] file located in the rclone source tree.
+The test suite is based on the \f[V]go test\f[R] command.
 Series of tests are stored in subdirectories below the
-\f[C]cmd/bisync/testdata\f[R] directory.
+\f[V]cmd/bisync/testdata\f[R] directory.
 Individual tests can be invoked by their directory name, e.g.
-\f[C]go test . -case basic -remote local -remote2 gdrive: -v\f[R]
+\f[V]go test . -case basic -remote local -remote2 gdrive: -v\f[R]
 .PP
 Tests will make a temporary folder on remote and purge it afterwards.
 If during test run there are intermittent errors and rclone retries,
@@ -31467,58 +31508,58 @@ Options:
 .fi
 .PP
 Note: unlike rclone flags which must be prefixed by double dash
-(\f[C]--\f[R]), the test command flags can be equally prefixed by a
-single \f[C]-\f[R] or double dash.
+(\f[V]--\f[R]), the test command flags can be equally prefixed by a
+single \f[V]-\f[R] or double dash.
 .SS Running tests
 .IP \[bu] 2
-\f[C]go test . -case basic -remote local -remote2 local\f[R] runs the
-\f[C]test_basic\f[R] test case using only the local filesystem, synching
+\f[V]go test . -case basic -remote local -remote2 local\f[R] runs the
+\f[V]test_basic\f[R] test case using only the local filesystem, synching
 one local directory with another local directory.
 Test script output is to the console, while commands within scenario.txt
-have their output sent to the \f[C].../workdir/test.log\f[R] file, which
+have their output sent to the \f[V].../workdir/test.log\f[R] file, which
 is finally compared to the golden copy.
 .IP \[bu] 2
-The first argument after \f[C]go test\f[R] should be a relative name of
+The first argument after \f[V]go test\f[R] should be a relative name of
 the directory containing bisync source code.
-If you run tests right from there, the argument will be \f[C].\f[R]
+If you run tests right from there, the argument will be \f[V].\f[R]
 (current directory) as in most examples below.
 If you run bisync tests from the rclone source directory, the command
-should be \f[C]go test ./cmd/bisync ...\f[R].
+should be \f[V]go test ./cmd/bisync ...\f[R].
 .IP \[bu] 2
 The test engine will mangle rclone output to ensure comparability with
 golden listings and logs.
 .IP \[bu] 2
-Test scenarios are located in \f[C]./cmd/bisync/testdata\f[R].
-The test \f[C]-case\f[R] argument should match the full name of a
+Test scenarios are located in \f[V]./cmd/bisync/testdata\f[R].
+The test \f[V]-case\f[R] argument should match the full name of a
 subdirectory under that directory.
-Every test subdirectory name on disk must start with \f[C]test_\f[R],
+Every test subdirectory name on disk must start with \f[V]test_\f[R],
 this prefix can be omitted on command line for brevity.
 Also, underscores in the name can be replaced by dashes for convenience.
 .IP \[bu] 2
-\f[C]go test . -remote local -remote2 local -case all\f[R] runs all
+\f[V]go test . -remote local -remote2 local -case all\f[R] runs all
 tests.
 .IP \[bu] 2
-Path1 and Path2 may either be the keyword \f[C]local\f[R] or may be
+Path1 and Path2 may either be the keyword \f[V]local\f[R] or may be
 names of configured cloud services.
-\f[C]go test . -remote gdrive: -remote2 dropbox: -case basic\f[R] will
+\f[V]go test . -remote gdrive: -remote2 dropbox: -case basic\f[R] will
 run the test between these two services, without transferring any files
 to the local filesystem.
 .IP \[bu] 2
 Test run stdout and stderr console output may be directed to a file,
 e.g.
-\f[C]go test . -remote gdrive: -remote2 local -case all > runlog.txt 2>&1\f[R]
+\f[V]go test . -remote gdrive: -remote2 local -case all > runlog.txt 2>&1\f[R]
 .SS Test execution flow
 .IP "1." 3
-The base setup in the \f[C]initial\f[R] directory of the testcase is
+The base setup in the \f[V]initial\f[R] directory of the testcase is
 applied on the Path1 and Path2 filesystems (via rclone copy the initial
 directory to Path1, then rclone sync Path1 to Path2).
 .IP "2." 3
 The commands in the scenario.txt file are applied, with output directed
-to the \f[C]test.log\f[R] file in the test working directory.
-Typically, the first actual command in the \f[C]scenario.txt\f[R] file
-is to do a \f[C]--resync\f[R], which establishes the baseline
-\f[C]{...}.path1.lst\f[R] and \f[C]{...}.path2.lst\f[R] files in the
-test working directory (\f[C].../workdir/\f[R] relative to the temporary
+to the \f[V]test.log\f[R] file in the test working directory.
+Typically, the first actual command in the \f[V]scenario.txt\f[R] file
+is to do a \f[V]--resync\f[R], which establishes the baseline
+\f[V]{...}.path1.lst\f[R] and \f[V]{...}.path2.lst\f[R] files in the
+test working directory (\f[V].../workdir/\f[R] relative to the temporary
 test directory).
 Various commands and listing snapshots are done within the test.
 .IP "3." 3
@@ -31527,46 +31568,51 @@ contents of the testcase\[aq]s golden directory.
 .SS Notes about testing
 .IP \[bu] 2
 Test cases are in individual directories beneath
-\f[C]./cmd/bisync/testdata\f[R].
+\f[V]./cmd/bisync/testdata\f[R].
 A command line reference to a test is understood to reference a
-directory beneath \f[C]testdata\f[R].
+directory beneath \f[V]testdata\f[R].
 For example,
-\f[C]go test ./cmd/bisync -case dry-run -remote gdrive: -remote2 local\f[R]
-refers to the test case in \f[C]./cmd/bisync/testdata/test_dry_run\f[R].
+\f[V]go test ./cmd/bisync -case dry-run -remote gdrive: -remote2 local\f[R]
+refers to the test case in \f[V]./cmd/bisync/testdata/test_dry_run\f[R].
 .IP \[bu] 2
-The test working directory is located at \f[C].../workdir\f[R] relative
-to a temporary test directory, usually under \f[C]/tmp\f[R] on Linux.
+The test working directory is located at \f[V].../workdir\f[R] relative
+to a temporary test directory, usually under \f[V]/tmp\f[R] on Linux.
 .IP \[bu] 2
 The local test sync tree is created at a temporary directory named like
-\f[C]bisync.XXX\f[R] under system temporary directory.
+\f[V]bisync.XXX\f[R] under system temporary directory.
 .IP \[bu] 2
 The remote test sync tree is located at a temporary directory under
-\f[C]<remote:>/bisync.XXX/\f[R].
+\f[V]<remote:>/bisync.XXX/\f[R].
 .IP \[bu] 2
-\f[C]path1\f[R] and/or \f[C]path2\f[R] subdirectories are created in a
+\f[V]path1\f[R] and/or \f[V]path2\f[R] subdirectories are created in a
 temporary directory under the respective local or cloud test remote.
 .IP \[bu] 2
 By default, the Path1 and Path2 test dirs and workdir will be deleted
 after each test run.
-The \f[C]-no-cleanup\f[R] flag disables purging these directories when
+The \f[V]-no-cleanup\f[R] flag disables purging these directories when
 validating and debugging a given test.
 These directories will be flushed before running another test,
-independent of the \f[C]-no-cleanup\f[R] usage.
+independent of the \f[V]-no-cleanup\f[R] usage.
 .IP \[bu] 2
-You will likely want to add \[ga]-
-/testdir/\f[C]to your normal   bisync\f[R]--filters-file\f[C]so that normal syncs do not attempt to sync   the test temporary directories, which may have\f[R]RCLONE_TEST\f[C]miscompares   in some testcases which would otherwise trip the\f[R]--check-access\f[C]system.   The\f[R]--check-access\f[C]mechanism is hard-coded to ignore\f[R]RCLONE_TEST\f[C]files beneath\f[R]bisync/testdata\[ga],
-so the test cases may reside on the synched tree even if there are check
-file mismatches in the test tree.
+You will likely want to add \f[V]- /testdir/\f[R] to your normal bisync
+\f[V]--filters-file\f[R] so that normal syncs do not attempt to sync the
+test temporary directories, which may have \f[V]RCLONE_TEST\f[R]
+miscompares in some testcases which would otherwise trip the
+\f[V]--check-access\f[R] system.
+The \f[V]--check-access\f[R] mechanism is hard-coded to ignore
+\f[V]RCLONE_TEST\f[R] files beneath \f[V]bisync/testdata\f[R], so the
+test cases may reside on the synched tree even if there are check file
+mismatches in the test tree.
 .IP \[bu] 2
 Some Dropbox tests can fail, notably printing the following message:
-\f[C]src and dst identical but can\[aq]t set mod time without deleting and re-uploading\f[R]
+\f[V]src and dst identical but can\[aq]t set mod time without deleting and re-uploading\f[R]
 This is expected and happens due to the way Dropbox handles modification
 times.
-You should use the \f[C]-refresh-times\f[R] test flag to make up for
+You should use the \f[V]-refresh-times\f[R] test flag to make up for
 this.
 .IP \[bu] 2
 If Dropbox tests hit request limit for you and print error message
-\f[C]too_many_requests/...: Too many requests or write operations.\f[R]
+\f[V]too_many_requests/...: Too many requests or write operations.\f[R]
 then follow the Dropbox App ID
 instructions (https://rclone.org/dropbox/#get-your-own-dropbox-app-id).
 .SS Updating golden results
@@ -31575,8 +31621,8 @@ Sometimes even a slight change in the bisync source can cause little
 changes spread around many log files.
 Updating them manually would be a nightmare.
 .PP
-The \f[C]-golden\f[R] flag will store the \f[C]test.log\f[R] and
-\f[C]*.lst\f[R] listings from each test case into respective golden
+The \f[V]-golden\f[R] flag will store the \f[V]test.log\f[R] and
+\f[V]*.lst\f[R] listings from each test case into respective golden
 directories.
 Golden results will automatically contain generic strings instead of
 local or cloud paths which means that they should match when run with a
@@ -31585,106 +31631,107 @@ different cloud service.
 Your normal workflow might be as follows: 1.
 Git-clone the rclone sources locally 2.
 Modify bisync source and check that it builds 3.
-Run the whole test suite \f[C]go test ./cmd/bisync -remote local\f[R] 4.
+Run the whole test suite \f[V]go test ./cmd/bisync -remote local\f[R] 4.
 If some tests show log difference, recheck them individually, e.g.:
-\f[C]go test ./cmd/bisync -remote local -case basic\f[R] 5.
+\f[V]go test ./cmd/bisync -remote local -case basic\f[R] 5.
 If you are convinced with the difference, goldenize all tests at once:
-\f[C]go test ./cmd/bisync -remote local -golden\f[R] 6.
-Use word diff: \f[C]git diff --word-diff ./cmd/bisync/testdata/\f[R].
+\f[V]go test ./cmd/bisync -remote local -golden\f[R] 6.
+Use word diff: \f[V]git diff --word-diff ./cmd/bisync/testdata/\f[R].
 Please note that normal line-level diff is generally useless here.
 7.
-Check the difference \f[I]carefully\f[R]! 8.
-Commit the change (\f[C]git commit\f[R]) \f[I]only\f[R] if you are sure.
+Check the difference \f[I]carefully\f[R]!
+8.
+Commit the change (\f[V]git commit\f[R]) \f[I]only\f[R] if you are sure.
 If unsure, save your code changes then wipe the log diffs from git:
-\f[C]git reset [--hard]\f[R].
+\f[V]git reset [--hard]\f[R].
 .SS Structure of test scenarios
 .IP \[bu] 2
-\f[C]<testname>/initial/\f[R] contains a tree of files that will be set
+\f[V]<testname>/initial/\f[R] contains a tree of files that will be set
 as the initial condition on both Path1 and Path2 testdirs.
 .IP \[bu] 2
-\f[C]<testname>/modfiles/\f[R] contains files that will be used to
+\f[V]<testname>/modfiles/\f[R] contains files that will be used to
 modify the Path1 and/or Path2 filesystems.
 .IP \[bu] 2
-\f[C]<testname>/golden/\f[R] contains the expected content of the test
-working directory (\f[C]workdir\f[R]) at the completion of the testcase.
+\f[V]<testname>/golden/\f[R] contains the expected content of the test
+working directory (\f[V]workdir\f[R]) at the completion of the testcase.
 .IP \[bu] 2
-\f[C]<testname>/scenario.txt\f[R] contains the body of the test, in the
+\f[V]<testname>/scenario.txt\f[R] contains the body of the test, in the
 form of various commands to modify files, run bisync, and snapshot
 listings.
-Output from these commands is captured to \f[C].../workdir/test.log\f[R]
+Output from these commands is captured to \f[V].../workdir/test.log\f[R]
 for comparison to the golden files.
 .SS Supported test commands
 .IP \[bu] 2
-\f[C]test <some message>\f[R] Print the line to the console and to the
-\f[C]test.log\f[R]:
-\f[C]test sync is working correctly with options x, y, z\f[R]
+\f[V]test <some message>\f[R] Print the line to the console and to the
+\f[V]test.log\f[R]:
+\f[V]test sync is working correctly with options x, y, z\f[R]
 .IP \[bu] 2
-\f[C]copy-listings <prefix>\f[R] Save a copy of all \f[C].lst\f[R]
+\f[V]copy-listings <prefix>\f[R] Save a copy of all \f[V].lst\f[R]
 listings in the test working directory with the specified prefix:
-\f[C]save-listings exclude-pass-run\f[R]
+\f[V]save-listings exclude-pass-run\f[R]
 .IP \[bu] 2
-\f[C]move-listings <prefix>\f[R] Similar to \f[C]copy-listings\f[R] but
+\f[V]move-listings <prefix>\f[R] Similar to \f[V]copy-listings\f[R] but
 removes the source
 .IP \[bu] 2
-\f[C]purge-children <dir>\f[R] This will delete all child files and
+\f[V]purge-children <dir>\f[R] This will delete all child files and
 purge all child subdirs under given directory but keep the parent
 intact.
 This behavior is important for tests with Google Drive because removing
 and re-creating the parent would change its ID.
 .IP \[bu] 2
-\f[C]delete-file <file>\f[R] Delete a single file.
+\f[V]delete-file <file>\f[R] Delete a single file.
 .IP \[bu] 2
-\f[C]delete-glob <dir> <pattern>\f[R] Delete a group of files located
+\f[V]delete-glob <dir> <pattern>\f[R] Delete a group of files located
 one level deep in the given directory with names matching a given glob
 pattern.
 .IP \[bu] 2
-\f[C]touch-glob YYYY-MM-DD <dir> <pattern>\f[R] Change modification time
+\f[V]touch-glob YYYY-MM-DD <dir> <pattern>\f[R] Change modification time
 on a group of files.
 .IP \[bu] 2
-\f[C]touch-copy YYYY-MM-DD <source-file> <dest-dir>\f[R] Change file
+\f[V]touch-copy YYYY-MM-DD <source-file> <dest-dir>\f[R] Change file
 modification time then copy it to destination.
 .IP \[bu] 2
-\f[C]copy-file <source-file> <dest-dir>\f[R] Copy a single file to given
+\f[V]copy-file <source-file> <dest-dir>\f[R] Copy a single file to given
 directory.
 .IP \[bu] 2
-\f[C]copy-as <source-file> <dest-file>\f[R] Similar to above but
+\f[V]copy-as <source-file> <dest-file>\f[R] Similar to above but
 destination must include both directory and the new file name at
 destination.
 .IP \[bu] 2
-\f[C]copy-dir <src> <dst>\f[R] and \f[C]sync-dir <src> <dst>\f[R]
+\f[V]copy-dir <src> <dst>\f[R] and \f[V]sync-dir <src> <dst>\f[R]
 Copy/sync a directory.
-Equivalent of \f[C]rclone copy\f[R] and \f[C]rclone sync\f[R].
+Equivalent of \f[V]rclone copy\f[R] and \f[V]rclone sync\f[R].
 .IP \[bu] 2
-\f[C]list-dirs <dir>\f[R] Equivalent to
-\f[C]rclone lsf -R --dirs-only <dir>\f[R]
+\f[V]list-dirs <dir>\f[R] Equivalent to
+\f[V]rclone lsf -R --dirs-only <dir>\f[R]
 .IP \[bu] 2
-\f[C]bisync [options]\f[R] Runs bisync against \f[C]-remote\f[R] and
-\f[C]-remote2\f[R].
+\f[V]bisync [options]\f[R] Runs bisync against \f[V]-remote\f[R] and
+\f[V]-remote2\f[R].
 .SS Supported substitution terms
 .IP \[bu] 2
-\f[C]{testdir/}\f[R] - the root dir of the testcase
+\f[V]{testdir/}\f[R] - the root dir of the testcase
 .IP \[bu] 2
-\f[C]{datadir/}\f[R] - the \f[C]modfiles\f[R] dir under the testcase
+\f[V]{datadir/}\f[R] - the \f[V]modfiles\f[R] dir under the testcase
 root
 .IP \[bu] 2
-\f[C]{workdir/}\f[R] - the temporary test working directory
+\f[V]{workdir/}\f[R] - the temporary test working directory
 .IP \[bu] 2
-\f[C]{path1/}\f[R] - the root of the Path1 test directory tree
+\f[V]{path1/}\f[R] - the root of the Path1 test directory tree
 .IP \[bu] 2
-\f[C]{path2/}\f[R] - the root of the Path2 test directory tree
+\f[V]{path2/}\f[R] - the root of the Path2 test directory tree
 .IP \[bu] 2
-\f[C]{session}\f[R] - base name of the test listings
+\f[V]{session}\f[R] - base name of the test listings
 .IP \[bu] 2
-\f[C]{/}\f[R] - OS-specific path separator
+\f[V]{/}\f[R] - OS-specific path separator
 .IP \[bu] 2
-\f[C]{spc}\f[R], \f[C]{tab}\f[R], \f[C]{eol}\f[R] - whitespace
+\f[V]{spc}\f[R], \f[V]{tab}\f[R], \f[V]{eol}\f[R] - whitespace
 .IP \[bu] 2
-\f[C]{chr:HH}\f[R] - raw byte with given hexadecimal code
+\f[V]{chr:HH}\f[R] - raw byte with given hexadecimal code
 .PP
-Substitution results of the terms named like \f[C]{dir/}\f[R] will end
-with \f[C]/\f[R] (or backslash on Windows), so it is not necessary to
+Substitution results of the terms named like \f[V]{dir/}\f[R] will end
+with \f[V]/\f[R] (or backslash on Windows), so it is not necessary to
 include slash in the usage, for example
-\f[C]delete-file {path1/}file1.txt\f[R].
+\f[V]delete-file {path1/}file1.txt\f[R].
 .SS Benchmarks
 .PP
 \f[I]This section is work in progress.\f[R]
@@ -31778,10 +31825,10 @@ files to be copied was dominated by the network bandwidth.
 rclone\[aq]s bisync implementation was derived from the
 rclonesync-V2 (https://github.com/cjnaz/rclonesync-V2) project,
 including documentation and test mechanisms, with
-[\[at]cjnaz](https://github.com/cjnaz)\[aq]s full support and
+\[at]cjnaz (https://github.com/cjnaz)\[aq]s full support and
 encouragement.
 .PP
-\f[C]rclone bisync\f[R] is similar in nature to a range of other
+\f[V]rclone bisync\f[R] is similar in nature to a range of other
 projects:
 .IP \[bu] 2
 unison (https://github.com/bcpierce00/unison)
@@ -31805,22 +31852,22 @@ Also note a number of academic publications by Benjamin
 Pierce (http://www.cis.upenn.edu/%7Ebcpierce/papers/index.shtml#File%20Synchronization)
 about \f[I]Unison\f[R] and synchronization in general.
 .SS Changelog
-.SS \f[C]v1.68\f[R]
+.SS \f[V]v1.68\f[R]
 .IP \[bu] 2
 Fixed an issue affecting backends that round modtimes to a lower
 precision.
-.SS \f[C]v1.67\f[R]
+.SS \f[V]v1.67\f[R]
 .IP \[bu] 2
 Added integration tests against all backends.
-.SS \f[C]v1.66\f[R]
+.SS \f[V]v1.66\f[R]
 .IP \[bu] 2
 Copies and deletes are now handled in one operation instead of two
 .IP \[bu] 2
-\f[C]--track-renames\f[R] and \f[C]--backup-dir\f[R] are now supported
+\f[V]--track-renames\f[R] and \f[V]--backup-dir\f[R] are now supported
 .IP \[bu] 2
 Partial uploads known issue on
-\f[C]local\f[R]/\f[C]ftp\f[R]/\f[C]sftp\f[R] has been resolved (unless
-using \f[C]--inplace\f[R])
+\f[V]local\f[R]/\f[V]ftp\f[R]/\f[V]sftp\f[R] has been resolved (unless
+using \f[V]--inplace\f[R])
 .IP \[bu] 2
 Final listings are now generated from sync results, to avoid needing to
 re-list
@@ -31833,28 +31880,28 @@ uncertainty, essentially marking the file as needing to be rechecked
 next time.
 .IP \[bu] 2
 A few basic terminal colors are now supported, controllable with
-\f[C]--color\f[R] (https://rclone.org/docs/#color-when)
-(\f[C]AUTO\f[R]|\f[C]NEVER\f[R]|\f[C]ALWAYS\f[R])
+\f[V]--color\f[R] (https://rclone.org/docs/#color-when)
+(\f[V]AUTO\f[R]|\f[V]NEVER\f[R]|\f[V]ALWAYS\f[R])
 .IP \[bu] 2
 Initial listing snapshots of Path1 and Path2 are now generated
 concurrently, using the same \[dq]march\[dq] infrastructure as
-\f[C]check\f[R] and \f[C]sync\f[R], for performance improvements and
+\f[V]check\f[R] and \f[V]sync\f[R], for performance improvements and
 less risk of
 error (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=4.%20Listings%20should%20alternate%20between%20paths%20to%20minimize%20errors).
 .IP \[bu] 2
 Fixed handling of unicode normalization and case insensitivity, support
-for \f[C]--fix-case\f[R] (https://rclone.org/docs/#fix-case),
-\f[C]--ignore-case-sync\f[R], \f[C]--no-unicode-normalization\f[R]
+for \f[V]--fix-case\f[R] (https://rclone.org/docs/#fix-case),
+\f[V]--ignore-case-sync\f[R], \f[V]--no-unicode-normalization\f[R]
 .IP \[bu] 2
-\f[C]--resync\f[R] is now much more efficient (especially for users of
-\f[C]--create-empty-src-dirs\f[R])
+\f[V]--resync\f[R] is now much more efficient (especially for users of
+\f[V]--create-empty-src-dirs\f[R])
 .IP \[bu] 2
 Google Docs (and other files of unknown size) are now supported (with
-the same options as in \f[C]sync\f[R])
+the same options as in \f[V]sync\f[R])
 .IP \[bu] 2
 Equality checks before a sync conflict rename now fall back to
-\f[C]cryptcheck\f[R] (when possible) or \f[C]--download\f[R], instead of
-of \f[C]--size-only\f[R], when \f[C]check\f[R] is not available.
+\f[V]cryptcheck\f[R] (when possible) or \f[V]--download\f[R], instead of
+of \f[V]--size-only\f[R], when \f[V]check\f[R] is not available.
 .IP \[bu] 2
 Bisync no longer fails to find the correct listing file when configs are
 overridden with backend-specific flags.
@@ -31864,26 +31911,26 @@ modtime, and checksum, lifting the prior restriction on backends without
 modtime support.
 .IP \[bu] 2
 Bisync now supports a \[dq]Graceful Shutdown\[dq] mode to cleanly cancel
-a run early without requiring \f[C]--resync\f[R].
+a run early without requiring \f[V]--resync\f[R].
 .IP \[bu] 2
-New \f[C]--recover\f[R] flag allows robust recovery in the event of
-interruptions, without requiring \f[C]--resync\f[R].
+New \f[V]--recover\f[R] flag allows robust recovery in the event of
+interruptions, without requiring \f[V]--resync\f[R].
 .IP \[bu] 2
-A new \f[C]--max-lock\f[R] setting allows lock files to automatically
+A new \f[V]--max-lock\f[R] setting allows lock files to automatically
 renew and expire, for better automatic recovery when a run is
 interrupted.
 .IP \[bu] 2
 Bisync now supports auto-resolving sync conflicts and customizing rename
-behavior with new \f[C]--conflict-resolve\f[R],
-\f[C]--conflict-loser\f[R], and \f[C]--conflict-suffix\f[R] flags.
+behavior with new \f[V]--conflict-resolve\f[R],
+\f[V]--conflict-loser\f[R], and \f[V]--conflict-suffix\f[R] flags.
 .IP \[bu] 2
-A new \f[C]--resync-mode\f[R] flag allows more control over which
-version of a file gets kept during a \f[C]--resync\f[R].
+A new \f[V]--resync-mode\f[R] flag allows more control over which
+version of a file gets kept during a \f[V]--resync\f[R].
 .IP \[bu] 2
 Bisync now supports
-\f[C]--retries\f[R] (https://rclone.org/docs/#retries-int) and
-\f[C]--retries-sleep\f[R] (when \f[C]--resilient\f[R] is set.)
-.SS \f[C]v1.64\f[R]
+\f[V]--retries\f[R] (https://rclone.org/docs/#retries-int) and
+\f[V]--retries-sleep\f[R] (when \f[V]--resilient\f[R] is set.)
+.SS \f[V]v1.64\f[R]
 .IP \[bu] 2
 Fixed an
 issue (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=1.%20Dry%20runs%20are%20not%20completely%20dry)
@@ -31891,10 +31938,10 @@ causing dry runs to inadvertently commit filter changes
 .IP \[bu] 2
 Fixed an
 issue (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=2.%20%2D%2Dresync%20deletes%20data%2C%20contrary%20to%20docs)
-causing \f[C]--resync\f[R] to erroneously delete empty folders and
+causing \f[V]--resync\f[R] to erroneously delete empty folders and
 duplicate files unique to Path2
 .IP \[bu] 2
-\f[C]--check-access\f[R] is now enforced during \f[C]--resync\f[R],
+\f[V]--check-access\f[R] is now enforced during \f[V]--resync\f[R],
 preventing data loss in certain user error
 scenarios (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=%2D%2Dcheck%2Daccess%20doesn%27t%20always%20fail%20when%20it%20should)
 .IP \[bu] 2
@@ -31908,15 +31955,15 @@ conflicts (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:
 (identical files are now left alone instead of renamed)
 .IP \[bu] 2
 Added support for
-\f[C]--create-empty-src-dirs\f[R] (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20Bisync%20should%20create/delete%20empty%20directories%20as%20sync%20does%2C%20when%20%2D%2Dcreate%2Dempty%2Dsrc%2Ddirs%20is%20passed)
+\f[V]--create-empty-src-dirs\f[R] (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=3.%20Bisync%20should%20create/delete%20empty%20directories%20as%20sync%20does%2C%20when%20%2D%2Dcreate%2Dempty%2Dsrc%2Ddirs%20is%20passed)
 .IP \[bu] 2
-Added experimental \f[C]--resilient\f[R] mode to allow recovery from
+Added experimental \f[V]--resilient\f[R] mode to allow recovery from
 self-correctable
 errors (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=2.%20Bisync%20should%20be%20more%20resilient%20to%20self%2Dcorrectable%20errors)
 .IP \[bu] 2
-Added new \f[C]--ignore-listing-checksum\f[R]
+Added new \f[V]--ignore-listing-checksum\f[R]
 flag (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=6.%20%2D%2Dignore%2Dchecksum%20should%20be%20split%20into%20two%20flags%20for%20separate%20purposes)
-to distinguish from \f[C]--ignore-checksum\f[R]
+to distinguish from \f[V]--ignore-checksum\f[R]
 .IP \[bu] 2
 Performance
 improvements (https://forum.rclone.org/t/bisync-bugs-and-feature-requests/37636#:~:text=6.%20Deletes%20take%20several%20times%20longer%20than%20copies)
@@ -31945,14 +31992,14 @@ also.
 The git repository hosted on GitHub -
 https://github.com/rclone/rclone/blob/master/docs/content/KEYS
 .IP \[bu] 2
-\f[C]gpg --keyserver hkps://keys.openpgp.org --search nick\[at]craig-wood.com\f[R]
+\f[V]gpg --keyserver hkps://keys.openpgp.org --search nick\[at]craig-wood.com\f[R]
 .IP \[bu] 2
-\f[C]gpg --keyserver hkps://keyserver.ubuntu.com --search nick\[at]craig-wood.com\f[R]
+\f[V]gpg --keyserver hkps://keyserver.ubuntu.com --search nick\[at]craig-wood.com\f[R]
 .IP \[bu] 2
 https://www.craig-wood.com/nick/pub/pgp-key.txt
 .PP
 After importing the key, verify that the fingerprint of one of the keys
-matches: \f[C]FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA\f[R] as this key
+matches: \f[V]FBF737ECE9F8AB18604BD2AC93935E02FF3B54FA\f[R] as this key
 is used for signing.
 .PP
 We recommend that you cross-check the fingerprint shown above through
@@ -31963,14 +32010,14 @@ domains you can be confident that you obtained the correct key.
 The source for this page on
 GitHub (https://github.com/rclone/rclone/blob/master/docs/content/release_signing.md).
 .IP \[bu] 2
-Through DNS \f[C]dig key.rclone.org txt\f[R]
+Through DNS \f[V]dig key.rclone.org txt\f[R]
 .PP
 If you find anything that doesn\[aq]t not match, please contact the
 developers at once.
 .SS How to verify the release
 .PP
 In the release directory you will see the release files and some files
-called \f[C]MD5SUMS\f[R], \f[C]SHA1SUMS\f[R] and \f[C]SHA256SUMS\f[R].
+called \f[V]MD5SUMS\f[R], \f[V]SHA1SUMS\f[R] and \f[V]SHA256SUMS\f[R].
 .IP
 .nf
 \f[C]
@@ -31987,7 +32034,7 @@ version.txt
 \f[R]
 .fi
 .PP
-The \f[C]MD5SUMS\f[R], \f[C]SHA1SUMS\f[R] and \f[C]SHA256SUMS\f[R]
+The \f[V]MD5SUMS\f[R], \f[V]SHA1SUMS\f[R] and \f[V]SHA256SUMS\f[R]
 contain hashes of the binary files in the release directory along with a
 signature.
 .PP
@@ -32016,12 +32063,12 @@ iF0EARECAB0WIQT79zfs6firGGBL0qyTk14C/ztU+gUCZLVKJQAKCRCTk14C/ztU
 .PP
 The first step is to download the binary and SUMs file and verify that
 the SUMs you have downloaded match.
-Here we download \f[C]rclone-v1.63.1-windows-amd64.zip\f[R] - choose the
+Here we download \f[V]rclone-v1.63.1-windows-amd64.zip\f[R] - choose the
 binary (or binaries) appropriate to your architecture.
-We\[aq]ve also chosen the \f[C]SHA256SUMS\f[R] as these are the most
+We\[aq]ve also chosen the \f[V]SHA256SUMS\f[R] as these are the most
 secure.
 You could verify the other types of hash also for extra security.
-\f[C]rclone selfupdate\f[R] verifies just the \f[C]SHA256SUMS\f[R].
+\f[V]rclone selfupdate\f[R] verifies just the \f[V]SHA256SUMS\f[R].
 .IP
 .nf
 \f[C]
@@ -32060,7 +32107,7 @@ gpg: Good signature from \[dq]Nick Craig-Wood <nick\[at]craig-wood.com>\[dq] [ul
 .PP
 Verify the signature was good and is using the fingerprint shown above.
 .PP
-Repeat for \f[C]MD5SUMS\f[R] and \f[C]SHA1SUMS\f[R] if desired.
+Repeat for \f[V]MD5SUMS\f[R] and \f[V]SHA1SUMS\f[R] if desired.
 .SS Verify the hashes
 .PP
 Now that we know the signatures on the hashes are OK we can verify the
@@ -32107,16 +32154,16 @@ This is a backend for the 1fichier (https://1fichier.com) cloud storage
 service.
 Note that a Premium subscription is required to use the API.
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 The initial setup for 1Fichier involves getting the API key from the
 website which you need to do in your browser.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -32166,7 +32213,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your 1Fichier account
 .IP
@@ -32224,49 +32271,49 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 \[dq]
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 $
 T}@T{
 0x24
 T}@T{
-\[uFF04]
+＄
 T}
 T{
 \[ga]
 T}@T{
 0x60
 T}@T{
-\[uFF40]
+｀
 T}
 T{
 \[aq]
 T}@T{
 0x27
 T}@T{
-\[uFF07]
+＇
 T}
 .TE
 .PP
@@ -32290,7 +32337,7 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 .TE
 .PP
@@ -32408,9 +32455,9 @@ Type: string
 Required: false
 .SS Limitations
 .PP
-\f[C]rclone about\f[R] is not supported by the 1Fichier backend.
+\f[V]rclone about\f[R] is not supported by the 1Fichier backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -32418,39 +32465,39 @@ about (https://rclone.org/overview/#optional-features) and rclone
 about (https://rclone.org/commands/rclone_about/)
 .SH Alias
 .PP
-The \f[C]alias\f[R] remote provides a new name for another remote.
+The \f[V]alias\f[R] remote provides a new name for another remote.
 .PP
 Paths may be as deep as required or a local path, e.g.
-\f[C]remote:directory/subdirectory\f[R] or
-\f[C]/directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R] or
+\f[V]/directory/subdirectory\f[R].
 .PP
-During the initial setup with \f[C]rclone config\f[R] you will specify
+During the initial setup with \f[V]rclone config\f[R] you will specify
 the target remote.
 The target remote can either be a local path or another remote.
 .PP
 Subfolders can be used in target remote.
-Assume an alias remote named \f[C]backup\f[R] with the target
-\f[C]mydrive:private/backup\f[R].
-Invoking \f[C]rclone mkdir backup:desktop\f[R] is exactly the same as
-invoking \f[C]rclone mkdir mydrive:private/backup/desktop\f[R].
+Assume an alias remote named \f[V]backup\f[R] with the target
+\f[V]mydrive:private/backup\f[R].
+Invoking \f[V]rclone mkdir backup:desktop\f[R] is exactly the same as
+invoking \f[V]rclone mkdir mydrive:private/backup/desktop\f[R].
 .PP
-There will be no special handling of paths containing \f[C]..\f[R]
+There will be no special handling of paths containing \f[V]..\f[R]
 segments.
-Invoking \f[C]rclone mkdir backup:../desktop\f[R] is exactly the same as
-invoking \f[C]rclone mkdir mydrive:private/backup/../desktop\f[R].
+Invoking \f[V]rclone mkdir backup:../desktop\f[R] is exactly the same as
+invoking \f[V]rclone mkdir mydrive:private/backup/../desktop\f[R].
 The empty path is not allowed as a remote.
-To alias the current directory use \f[C].\f[R] instead.
+To alias the current directory use \f[V].\f[R] instead.
 .PP
 The target remote can also be a connection
 string (https://rclone.org/docs/#connection-strings).
 This can be used to modify the config of a remote for different uses,
 e.g.
-the alias \f[C]myDriveTrash\f[R] with the target remote
-\f[C]myDrive,trashed_only:\f[R] can be used to only show the trashed
-files in \f[C]myDrive\f[R].
+the alias \f[V]myDriveTrash\f[R] with the target remote
+\f[V]myDrive,trashed_only:\f[R] can be used to only show the trashed
+files in \f[V]myDrive\f[R].
 .SS Configuration
 .PP
-Here is an example of how to make an alias called \f[C]remote\f[R] for
+Here is an example of how to make an alias called \f[V]remote\f[R] for
 local folder.
 First run:
 .IP
@@ -32507,9 +32554,9 @@ e/n/d/r/c/s/q> q
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
-List directories in top level in \f[C]/mnt/storage/backup\f[R]
+List directories in top level in \f[V]/mnt/storage/backup\f[R]
 .IP
 .nf
 \f[C]
@@ -32517,7 +32564,7 @@ rclone lsd remote:
 \f[R]
 .fi
 .PP
-List all the files in \f[C]/mnt/storage/backup\f[R]
+List all the files in \f[V]/mnt/storage/backup\f[R]
 .IP
 .nf
 \f[C]
@@ -32633,9 +32680,10 @@ Tencent Cloud Object Storage (COS)
 .IP \[bu] 2
 Wasabi
 .PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:bucket/path/to/dir\f[R].
+Paths are specified as \f[V]remote:bucket\f[R] (or \f[V]remote:\f[R] for
+the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:bucket/path/to/dir\f[R].
 .PP
 Once you have made a remote (see the provider specific section above)
 you can use it like this:
@@ -32664,7 +32712,7 @@ rclone ls remote:bucket
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote bucket, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote bucket, deleting any
 excess files in the bucket.
 .IP
 .nf
@@ -32891,7 +32939,7 @@ y/e/d>
 .SS Modification times
 .PP
 The modified time is stored as metadata on the object as
-\f[C]X-Amz-Meta-Mtime\f[R] as floating point since the epoch, accurate
+\f[V]X-Amz-Meta-Mtime\f[R] as floating point since the epoch, accurate
 to 1 ns.
 .PP
 If the modification time needs to be updated rclone will attempt to
@@ -32901,19 +32949,19 @@ In the case the object is larger than 5Gb or is in Glacier or Glacier
 Deep Archive storage the object will be uploaded rather than copied.
 .PP
 Note that reading this from the object takes an additional
-\f[C]HEAD\f[R] request as the metadata isn\[aq]t returned in object
+\f[V]HEAD\f[R] request as the metadata isn\[aq]t returned in object
 listings.
 .SS Hashes
 .PP
 For small objects which weren\[aq]t uploaded as multipart uploads
-(objects sized below \f[C]--s3-upload-cutoff\f[R] if uploaded with
-rclone) rclone uses the \f[C]ETag:\f[R] header as an MD5 checksum.
+(objects sized below \f[V]--s3-upload-cutoff\f[R] if uploaded with
+rclone) rclone uses the \f[V]ETag:\f[R] header as an MD5 checksum.
 .PP
 However for objects which were uploaded as multipart uploads or with
-server side encryption (SSE-AWS or SSE-C) the \f[C]ETag\f[R] header is
+server side encryption (SSE-AWS or SSE-C) the \f[V]ETag\f[R] header is
 no longer the MD5 sum of the data, so rclone adds an additional piece of
-metadata \f[C]X-Amz-Meta-Md5chksum\f[R] which is a base64 encoded MD5
-hash (in the same format as is required for \f[C]Content-MD5\f[R]).
+metadata \f[V]X-Amz-Meta-Md5chksum\f[R] which is a base64 encoded MD5
+hash (in the same format as is required for \f[V]Content-MD5\f[R]).
 You can use base64 -d and hexdump to check this value manually:
 .IP
 .nf
@@ -32922,15 +32970,15 @@ echo \[aq]VWTGdNx3LyXQDfA0e2Edxw==\[aq] | base64 -d | hexdump
 \f[R]
 .fi
 .PP
-or you can use \f[C]rclone check\f[R] to verify the hashes are OK.
+or you can use \f[V]rclone check\f[R] to verify the hashes are OK.
 .PP
 For large objects, calculating this hash can take some time so the
 addition of this hash can be disabled with
-\f[C]--s3-disable-checksum\f[R].
+\f[V]--s3-disable-checksum\f[R].
 This will mean that these objects do not have an MD5 checksum.
 .PP
 Note that reading this from the object takes an additional
-\f[C]HEAD\f[R] request as the metadata isn\[aq]t returned in object
+\f[V]HEAD\f[R] request as the metadata isn\[aq]t returned in object
 listings.
 .SS Reducing costs
 .SS Avoiding HEAD requests to read the modification time
@@ -32947,10 +32995,10 @@ is inefficient on S3 because it requires an extra API call to retrieve
 the metadata.
 .PP
 The extra API calls can be avoided when syncing (using
-\f[C]rclone sync\f[R] or \f[C]rclone copy\f[R]) in a few different ways,
+\f[V]rclone sync\f[R] or \f[V]rclone copy\f[R]) in a few different ways,
 each with its own tradeoffs.
 .IP \[bu] 2
-\f[C]--size-only\f[R]
+\f[V]--size-only\f[R]
 .RS 2
 .IP \[bu] 2
 Only checks the size of files.
@@ -32960,10 +33008,10 @@ Uses no extra transactions.
 If the file doesn\[aq]t change size then rclone won\[aq]t detect it has
 changed.
 .IP \[bu] 2
-\f[C]rclone sync --size-only /path/to/source s3:bucket\f[R]
+\f[V]rclone sync --size-only /path/to/source s3:bucket\f[R]
 .RE
 .IP \[bu] 2
-\f[C]--checksum\f[R]
+\f[V]--checksum\f[R]
 .RS 2
 .IP \[bu] 2
 Checks the size and MD5 checksum of files.
@@ -32978,10 +33026,10 @@ disk, will cause lots of disk activity.
 If the source and destination are both S3 this is the
 \f[B]recommended\f[R] flag to use for maximum efficiency.
 .IP \[bu] 2
-\f[C]rclone sync --checksum /path/to/source s3:bucket\f[R]
+\f[V]rclone sync --checksum /path/to/source s3:bucket\f[R]
 .RE
 .IP \[bu] 2
-\f[C]--update --use-server-modtime\f[R]
+\f[V]--update --use-server-modtime\f[R]
 .RS 2
 .IP \[bu] 2
 Uses no extra transactions.
@@ -32991,30 +33039,30 @@ Modification time becomes the time the object was uploaded.
 For many operations this is sufficient to determine if it needs
 uploading.
 .IP \[bu] 2
-Using \f[C]--update\f[R] along with \f[C]--use-server-modtime\f[R],
+Using \f[V]--update\f[R] along with \f[V]--use-server-modtime\f[R],
 avoids the extra API call and uploads files whose local modification
 time is newer than the time it was last uploaded.
 .IP \[bu] 2
 Files created with timestamps in the past will be missed by the sync.
 .IP \[bu] 2
-\f[C]rclone sync --update --use-server-modtime /path/to/source s3:bucket\f[R]
+\f[V]rclone sync --update --use-server-modtime /path/to/source s3:bucket\f[R]
 .RE
 .PP
 These flags can and should be used in combination with
-\f[C]--fast-list\f[R] - see below.
+\f[V]--fast-list\f[R] - see below.
 .PP
-If using \f[C]rclone mount\f[R] or any command using the VFS (eg
-\f[C]rclone serve\f[R]) commands then you might want to consider using
-the VFS flag \f[C]--no-modtime\f[R] which will stop rclone reading the
+If using \f[V]rclone mount\f[R] or any command using the VFS (eg
+\f[V]rclone serve\f[R]) commands then you might want to consider using
+the VFS flag \f[V]--no-modtime\f[R] which will stop rclone reading the
 modification time for every object.
-You could also use \f[C]--use-server-modtime\f[R] if you are happy with
+You could also use \f[V]--use-server-modtime\f[R] if you are happy with
 the modification times of the objects being the time of upload.
 .SS Avoiding GET requests to read directory listings
 .PP
 Rclone\[aq]s default directory traversal is to process each directory
 individually.
 This takes one API call per directory.
-Using the \f[C]--fast-list\f[R] flag will read all info about the
+Using the \f[V]--fast-list\f[R] flag will read all info about the
 objects into memory first using a smaller number of API calls (one per
 1000 objects).
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
@@ -33026,16 +33074,16 @@ rclone sync --fast-list --checksum /path/to/source s3:bucket
 \f[R]
 .fi
 .PP
-\f[C]--fast-list\f[R] trades off API transactions for memory use.
+\f[V]--fast-list\f[R] trades off API transactions for memory use.
 As a rough guide rclone uses 1k of memory per object stored, so using
-\f[C]--fast-list\f[R] on a sync of a million objects will use roughly 1
+\f[V]--fast-list\f[R] on a sync of a million objects will use roughly 1
 GiB of RAM.
 .PP
 If you are only copying a small number of files into a big repository
-then using \f[C]--no-traverse\f[R] is a good idea.
+then using \f[V]--no-traverse\f[R] is a good idea.
 This finds objects directly instead of through directory listings.
 You can do a \[dq]top-up\[dq] sync very cheaply by using
-\f[C]--max-age\f[R] and \f[C]--no-traverse\f[R] to copy only recent
+\f[V]--max-age\f[R] and \f[V]--no-traverse\f[R] to copy only recent
 files, eg
 .IP
 .nf
@@ -33044,9 +33092,9 @@ rclone copy --max-age 24h --no-traverse /path/to/source s3:bucket
 \f[R]
 .fi
 .PP
-You\[aq]d then do a full \f[C]rclone sync\f[R] less often.
+You\[aq]d then do a full \f[V]rclone sync\f[R] less often.
 .PP
-Note that \f[C]--fast-list\f[R] isn\[aq]t required in the top-up sync.
+Note that \f[V]--fast-list\f[R] isn\[aq]t required in the top-up sync.
 .SS Avoiding HEAD requests after PUT
 .PP
 By default, rclone will HEAD every object it uploads.
@@ -33079,7 +33127,7 @@ See below for how to increase the number of API requests rclone makes.
 .SS Increasing the rate of API requests
 .PP
 You can increase the rate of API requests to S3 by increasing the
-parallelism using \f[C]--transfers\f[R] and \f[C]--checkers\f[R]
+parallelism using \f[V]--transfers\f[R] and \f[V]--checkers\f[R]
 options.
 .PP
 Rclone uses a very conservative defaults for these settings, as not all
@@ -33103,39 +33151,39 @@ settings for your setup.
 .SS Versions
 .PP
 When bucket versioning is enabled (this can be done with rclone with the
-\f[C]rclone backend versioning\f[R] command) when rclone uploads a new
+\f[V]rclone backend versioning\f[R] command) when rclone uploads a new
 version of a file it creates a new version of
 it (https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html)
 Likewise when you delete a file, the old version will be marked hidden
 and still be available.
 .PP
 Old versions of files, where available, are visible using the
-\f[C]--s3-versions\f[R] flag.
+\f[V]--s3-versions\f[R] flag.
 .PP
 It is also possible to view a bucket as it was at a certain point in
-time, using the \f[C]--s3-version-at\f[R] flag.
+time, using the \f[V]--s3-version-at\f[R] flag.
 This will show the file versions as they were at that time, showing
 files that have been deleted afterwards, and hiding files that were
 created since.
 .PP
 If you wish to remove all the old versions then you can use the
-\f[C]rclone backend cleanup-hidden remote:bucket\f[R] command which will
+\f[V]rclone backend cleanup-hidden remote:bucket\f[R] command which will
 delete all the old hidden versions of files, leaving the current ones
 intact.
 You can also supply a path and only old versions under that path will be
 deleted, e.g.
-\f[C]rclone backend cleanup-hidden remote:bucket/path/to/stuff\f[R].
+\f[V]rclone backend cleanup-hidden remote:bucket/path/to/stuff\f[R].
 .PP
-When you \f[C]purge\f[R] a bucket, the current and the old versions will
+When you \f[V]purge\f[R] a bucket, the current and the old versions will
 be deleted then the bucket will be deleted.
 .PP
-However \f[C]delete\f[R] will cause the current versions of the files to
+However \f[V]delete\f[R] will cause the current versions of the files to
 become hidden old versions.
 .PP
 Here is a session showing the listing and retrieval of an old version
-followed by a \f[C]cleanup\f[R] of the old versions.
+followed by a \f[V]cleanup\f[R] of the old versions.
 .PP
-Show current version and all the versions with \f[C]--s3-versions\f[R]
+Show current version and all the versions with \f[V]--s3-versions\f[R]
 flag.
 .IP
 .nf
@@ -33177,7 +33225,7 @@ $ rclone -q --s3-versions ls s3:cleanup-test
 .fi
 .SS Versions naming caveat
 .PP
-When using \f[C]--s3-versions\f[R] flag rclone is relying on the file
+When using \f[V]--s3-versions\f[R] flag rclone is relying on the file
 name to work out whether the objects are versions or not.
 Versions\[aq] names are created by inserting timestamp between file name
 and its extension.
@@ -33191,17 +33239,17 @@ and its extension.
 .fi
 .PP
 If there are real files present with the same names as versions, then
-behaviour of \f[C]--s3-versions\f[R] can be unpredictable.
+behaviour of \f[V]--s3-versions\f[R] can be unpredictable.
 .SS Cleanup
 .PP
-If you run \f[C]rclone cleanup s3:bucket\f[R] then it will remove all
+If you run \f[V]rclone cleanup s3:bucket\f[R] then it will remove all
 pending multipart uploads older than 24 hours.
-You can use the \f[C]--interactive\f[R]/\f[C]i\f[R] or
-\f[C]--dry-run\f[R] flag to see exactly what it will do.
+You can use the \f[V]--interactive\f[R]/\f[V]i\f[R] or
+\f[V]--dry-run\f[R] flag to see exactly what it will do.
 If you want more control over the expiry date then run
-\f[C]rclone backend cleanup s3:bucket -o max-age=1h\f[R] to expire all
+\f[V]rclone backend cleanup s3:bucket -o max-age=1h\f[R] to expire all
 uploads older than one hour.
-You can use \f[C]rclone backend list-multipart-uploads s3:bucket\f[R] to
+You can use \f[V]rclone backend list-multipart-uploads s3:bucket\f[R] to
 see the pending multipart uploads.
 .SS Restricted filename characters
 .PP
@@ -33230,14 +33278,14 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 .TE
 .PP
@@ -33256,12 +33304,12 @@ _
 T{
 \&.
 T}@T{
-\[uFF0E]
+．
 T}
 T{
 \&..
 T}@T{
-\[uFF0E]\[uFF0E]
+．．
 T}
 .TE
 .SS Multipart uploads
@@ -33273,16 +33321,16 @@ Note that files uploaded \f[I]both\f[R] with multipart upload
 \f[I]and\f[R] through crypt remotes do not have MD5 sums.
 .PP
 rclone switches from single part uploads to multipart uploads at the
-point specified by \f[C]--s3-upload-cutoff\f[R].
+point specified by \f[V]--s3-upload-cutoff\f[R].
 This can be a maximum of 5 GiB and a minimum of 0 (ie always upload
 multipart files).
 .PP
 The chunk sizes used in the multipart upload are specified by
-\f[C]--s3-chunk-size\f[R] and the number of chunks uploaded concurrently
-is specified by \f[C]--s3-upload-concurrency\f[R].
+\f[V]--s3-chunk-size\f[R] and the number of chunks uploaded concurrently
+is specified by \f[V]--s3-upload-concurrency\f[R].
 .PP
-Multipart uploads will use \f[C]--transfers\f[R] *
-\f[C]--s3-upload-concurrency\f[R] * \f[C]--s3-chunk-size\f[R] extra
+Multipart uploads will use \f[V]--transfers\f[R] *
+\f[V]--s3-upload-concurrency\f[R] * \f[V]--s3-chunk-size\f[R] extra
 memory.
 Single part uploads to not use extra memory.
 .PP
@@ -33290,49 +33338,49 @@ Single part transfers can be faster than multipart transfers or slower
 depending on your latency from S3 - the more latency, the more likely
 single part transfers will be faster.
 .PP
-Increasing \f[C]--s3-upload-concurrency\f[R] will increase throughput (8
-would be a sensible value) and increasing \f[C]--s3-chunk-size\f[R] also
+Increasing \f[V]--s3-upload-concurrency\f[R] will increase throughput (8
+would be a sensible value) and increasing \f[V]--s3-chunk-size\f[R] also
 increases throughput (16M would be sensible).
 Increasing either of these will use more memory.
 The default values are high enough to gain most of the possible
 performance without using too much memory.
 .SS Buckets and Regions
 .PP
-With Amazon S3 you can list buckets (\f[C]rclone lsd\f[R]) using any
+With Amazon S3 you can list buckets (\f[V]rclone lsd\f[R]) using any
 region, but you can only access the content of a bucket from the region
 it was created in.
 If you attempt to access a bucket from the wrong region, you will get an
 error,
-\f[C]incorrect region, the bucket is not in \[aq]XXX\[aq] region\f[R].
+\f[V]incorrect region, the bucket is not in \[aq]XXX\[aq] region\f[R].
 .SS Authentication
 .PP
-There are a number of ways to supply \f[C]rclone\f[R] with a set of AWS
+There are a number of ways to supply \f[V]rclone\f[R] with a set of AWS
 credentials, with and without using the environment.
 .PP
 The different authentication methods are tried in this order:
 .IP \[bu] 2
-Directly in the rclone configuration file (\f[C]env_auth = false\f[R] in
+Directly in the rclone configuration file (\f[V]env_auth = false\f[R] in
 the config file):
 .RS 2
 .IP \[bu] 2
-\f[C]access_key_id\f[R] and \f[C]secret_access_key\f[R] are required.
+\f[V]access_key_id\f[R] and \f[V]secret_access_key\f[R] are required.
 .IP \[bu] 2
-\f[C]session_token\f[R] can be optionally set when using AWS STS.
+\f[V]session_token\f[R] can be optionally set when using AWS STS.
 .RE
 .IP \[bu] 2
-Runtime configuration (\f[C]env_auth = true\f[R] in the config file):
+Runtime configuration (\f[V]env_auth = true\f[R] in the config file):
 .RS 2
 .IP \[bu] 2
 Export the following environment variables before running
-\f[C]rclone\f[R]:
+\f[V]rclone\f[R]:
 .RS 2
 .IP \[bu] 2
-Access Key ID: \f[C]AWS_ACCESS_KEY_ID\f[R] or \f[C]AWS_ACCESS_KEY\f[R]
+Access Key ID: \f[V]AWS_ACCESS_KEY_ID\f[R] or \f[V]AWS_ACCESS_KEY\f[R]
 .IP \[bu] 2
-Secret Access Key: \f[C]AWS_SECRET_ACCESS_KEY\f[R] or
-\f[C]AWS_SECRET_KEY\f[R]
+Secret Access Key: \f[V]AWS_SECRET_ACCESS_KEY\f[R] or
+\f[V]AWS_SECRET_KEY\f[R]
 .IP \[bu] 2
-Session Token: \f[C]AWS_SESSION_TOKEN\f[R] (optional)
+Session Token: \f[V]AWS_SESSION_TOKEN\f[R] (optional)
 .RE
 .IP \[bu] 2
 Or, use a named
@@ -33342,24 +33390,24 @@ profile (https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.ht
 Profile files are standard files used by AWS CLI tools
 .IP \[bu] 2
 By default it will use the profile in your home directory (e.g.
-\f[C]\[ti]/.aws/credentials\f[R] on unix based systems) file and the
+\f[V]\[ti]/.aws/credentials\f[R] on unix based systems) file and the
 \[dq]default\[dq] profile, to change set these environment variables or
 config keys:
 .RS 2
 .IP \[bu] 2
-\f[C]AWS_SHARED_CREDENTIALS_FILE\f[R] to control which file or the
-\f[C]shared_credentials_file\f[R] config key.
+\f[V]AWS_SHARED_CREDENTIALS_FILE\f[R] to control which file or the
+\f[V]shared_credentials_file\f[R] config key.
 .IP \[bu] 2
-\f[C]AWS_PROFILE\f[R] to control which profile to use or the
-\f[C]profile\f[R] config key.
+\f[V]AWS_PROFILE\f[R] to control which profile to use or the
+\f[V]profile\f[R] config key.
 .RE
 .RE
 .IP \[bu] 2
-Or, run \f[C]rclone\f[R] in an ECS task with an IAM role (AWS only).
+Or, run \f[V]rclone\f[R] in an ECS task with an IAM role (AWS only).
 .IP \[bu] 2
-Or, run \f[C]rclone\f[R] on an EC2 instance with an IAM role (AWS only).
+Or, run \f[V]rclone\f[R] on an EC2 instance with an IAM role (AWS only).
 .IP \[bu] 2
-Or, run \f[C]rclone\f[R] in an EKS pod with an IAM role that is
+Or, run \f[V]rclone\f[R] in an EKS pod with an IAM role that is
 associated with a service account (AWS only).
 .IP \[bu] 2
 Or, use process
@@ -33367,33 +33415,33 @@ credentials (https://docs.aws.amazon.com/sdkref/latest/guide/feature-process-cre
 to read config from an external program.
 .RE
 .PP
-With \f[C]env_auth = true\f[R] rclone (which uses the SDK for Go v2)
+With \f[V]env_auth = true\f[R] rclone (which uses the SDK for Go v2)
 should support all authentication
 methods (https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.html)
-that the \f[C]aws\f[R] CLI tool does and the other AWS SDKs.
+that the \f[V]aws\f[R] CLI tool does and the other AWS SDKs.
 .PP
-If none of these option actually end up providing \f[C]rclone\f[R] with
+If none of these option actually end up providing \f[V]rclone\f[R] with
 AWS credentials then S3 interaction will be non-authenticated (see the
 anonymous access section for more info).
 .SS S3 Permissions
 .PP
-When using the \f[C]sync\f[R] subcommand of \f[C]rclone\f[R] the
+When using the \f[V]sync\f[R] subcommand of \f[V]rclone\f[R] the
 following minimum permissions are required to be available on the bucket
 being written to:
 .IP \[bu] 2
-\f[C]ListBucket\f[R]
+\f[V]ListBucket\f[R]
 .IP \[bu] 2
-\f[C]DeleteObject\f[R]
+\f[V]DeleteObject\f[R]
 .IP \[bu] 2
-\f[C]GetObject\f[R]
+\f[V]GetObject\f[R]
 .IP \[bu] 2
-\f[C]PutObject\f[R]
+\f[V]PutObject\f[R]
 .IP \[bu] 2
-\f[C]PutObjectACL\f[R]
+\f[V]PutObjectACL\f[R]
 .IP \[bu] 2
-\f[C]CreateBucket\f[R] (unless using s3-no-check-bucket)
+\f[V]CreateBucket\f[R] (unless using s3-no-check-bucket)
 .PP
-When using the \f[C]lsd\f[R] subcommand, the \f[C]ListAllMyBuckets\f[R]
+When using the \f[V]lsd\f[R] subcommand, the \f[V]ListAllMyBuckets\f[R]
 permission is required.
 .PP
 Example policy:
@@ -33433,23 +33481,23 @@ Example policy:
 Notes on above:
 .IP "1." 3
 This is a policy that can be used when creating bucket.
-It assumes that \f[C]USER_NAME\f[R] has been created.
+It assumes that \f[V]USER_NAME\f[R] has been created.
 .IP "2." 3
 The Resource entry must include both resource ARNs, as one implies the
 bucket and the other implies the bucket\[aq]s objects.
 .IP "3." 3
 When using s3-no-check-bucket and the bucket already exsits, the
-\f[C]\[dq]arn:aws:s3:::BUCKET_NAME\[dq]\f[R] doesn\[aq]t have to be
+\f[V]\[dq]arn:aws:s3:::BUCKET_NAME\[dq]\f[R] doesn\[aq]t have to be
 included.
 .PP
 For reference, here\[aq]s an Ansible
 script (https://gist.github.com/ebridges/ebfc9042dd7c756cd101cfa807b7ae2b)
 that will generate one or more buckets that will work with
-\f[C]rclone sync\f[R].
+\f[V]rclone sync\f[R].
 .SS Key Management System (KMS)
 .PP
 If you are using server-side encryption with KMS then you must make sure
-rclone is configured with \f[C]server_side_encryption = aws:kms\f[R]
+rclone is configured with \f[V]server_side_encryption = aws:kms\f[R]
 otherwise you will find you can\[aq]t transfer small objects - these
 will create checksum errors.
 .SS Glacier and Glacier Deep Archive
@@ -33486,7 +33534,7 @@ upload objects in such a bucket must include the Content-MD5 header.
 As mentioned in the Modification times and hashes section, small files
 that are not uploaded as multipart, use a different tag, causing the
 upload to fail.
-A simple solution is to set the \f[C]--s3-upload-cutoff 0\f[R] and force
+A simple solution is to set the \f[V]--s3-upload-cutoff 0\f[R] and force
 all the files to be uploaded as multipart.
 .SS Standard options
 .PP
@@ -35346,11 +35394,11 @@ Default: false
 Set this if the backend might gzip objects.
 .PP
 Normally providers will not alter objects when they are downloaded.
-If an object was not uploaded with \f[C]Content-Encoding: gzip\f[R] then
+If an object was not uploaded with \f[V]Content-Encoding: gzip\f[R] then
 it won\[aq]t be set on download.
 .PP
 However some providers may gzip objects even if they weren\[aq]t
-uploaded with \f[C]Content-Encoding: gzip\f[R] (eg Cloudflare).
+uploaded with \f[V]Content-Encoding: gzip\f[R] (eg Cloudflare).
 .PP
 A symptom of this would be receiving errors like
 .IP
@@ -35379,9 +35427,9 @@ Type: Tristate
 Default: unset
 .SS --s3-use-accept-encoding-gzip
 .PP
-Whether to send \f[C]Accept-Encoding: gzip\f[R] header.
+Whether to send \f[V]Accept-Encoding: gzip\f[R] header.
 .PP
-By default, rclone will append \f[C]Accept-Encoding: gzip\f[R] to the
+By default, rclone will append \f[V]Accept-Encoding: gzip\f[R] to the
 request to download compressed objects whenever possible.
 .PP
 However some providers such as Google Cloud Storage may alter the HTTP
@@ -35442,22 +35490,22 @@ Set if rclone should report BucketAlreadyExists errors on bucket
 creation.
 .PP
 At some point during the evolution of the s3 protocol, AWS started
-returning an \f[C]AlreadyOwnedByYou\f[R] error when attempting to create
+returning an \f[V]AlreadyOwnedByYou\f[R] error when attempting to create
 a bucket that the user already owned, rather than a
-\f[C]BucketAlreadyExists\f[R] error.
+\f[V]BucketAlreadyExists\f[R] error.
 .PP
 Unfortunately exactly what has been implemented by s3 clones is a little
-inconsistent, some return \f[C]AlreadyOwnedByYou\f[R], some return
-\f[C]BucketAlreadyExists\f[R] and some return no error at all.
+inconsistent, some return \f[V]AlreadyOwnedByYou\f[R], some return
+\f[V]BucketAlreadyExists\f[R] and some return no error at all.
 .PP
 This is important to rclone because it ensures the bucket exists by
 creating it on quite a lot of operations (unless
-\f[C]--s3-no-check-bucket\f[R] is used).
+\f[V]--s3-no-check-bucket\f[R] is used).
 .PP
-If rclone knows the provider can return \f[C]AlreadyOwnedByYou\f[R] or
-returns no error then it can report \f[C]BucketAlreadyExists\f[R] errors
+If rclone knows the provider can return \f[V]AlreadyOwnedByYou\f[R] or
+returns no error then it can report \f[V]BucketAlreadyExists\f[R] errors
 when the user attempts to create a bucket not owned by them.
-Otherwise rclone ignores the \f[C]BucketAlreadyExists\f[R] error which
+Otherwise rclone ignores the \f[V]BucketAlreadyExists\f[R] error which
 can lead to confusion.
 .PP
 This should be automatically set correctly for all providers rclone
@@ -35497,26 +35545,26 @@ Set to debug the SDK
 .PP
 This can be set to a comma separated list of the following functions:
 .IP \[bu] 2
-\f[C]Signing\f[R]
+\f[V]Signing\f[R]
 .IP \[bu] 2
-\f[C]Retries\f[R]
+\f[V]Retries\f[R]
 .IP \[bu] 2
-\f[C]Request\f[R]
+\f[V]Request\f[R]
 .IP \[bu] 2
-\f[C]RequestWithBody\f[R]
+\f[V]RequestWithBody\f[R]
 .IP \[bu] 2
-\f[C]Response\f[R]
+\f[V]Response\f[R]
 .IP \[bu] 2
-\f[C]ResponseWithBody\f[R]
+\f[V]ResponseWithBody\f[R]
 .IP \[bu] 2
-\f[C]DeprecatedUsage\f[R]
+\f[V]DeprecatedUsage\f[R]
 .IP \[bu] 2
-\f[C]RequestEventMessage\f[R]
+\f[V]RequestEventMessage\f[R]
 .IP \[bu] 2
-\f[C]ResponseEventMessage\f[R]
+\f[V]ResponseEventMessage\f[R]
 .PP
-Use \f[C]Off\f[R] to disable and \f[C]All\f[R] to set all log levels.
-You will need to use \f[C]-vv\f[R] to see the debug level logs.
+Use \f[V]Off\f[R] to disable and \f[V]All\f[R] to set all log levels.
+You will need to use \f[V]-vv\f[R] to see the debug level logs.
 .PP
 Properties:
 .IP \[bu] 2
@@ -35964,7 +36012,7 @@ It doesn\[aq]t return anything.
 .SS Anonymous access to public buckets
 .PP
 If you want to use rclone to access a public bucket, configure with a
-blank \f[C]access_key_id\f[R] and \f[C]secret_access_key\f[R].
+blank \f[V]access_key_id\f[R] and \f[V]secret_access_key\f[R].
 Your config should end up looking like this:
 .IP
 .nf
@@ -36006,11 +36054,11 @@ Its main software interface is S3 object storage.
 To use rclone with AWS Snowball Edge devices, configure as standard for
 an \[aq]S3 Compatible Service\[aq].
 .PP
-If using rclone pre v1.59 be sure to set \f[C]upload_cutoff = 0\f[R]
+If using rclone pre v1.59 be sure to set \f[V]upload_cutoff = 0\f[R]
 otherwise you will run into authentication header issues as the snowball
 device does not support query parameter based authentication.
 .PP
-With rclone v1.59 or later setting \f[C]upload_cutoff\f[R] should not be
+With rclone v1.59 or later setting \f[V]upload_cutoff\f[R] should not be
 necessary.
 .PP
 eg.
@@ -36055,15 +36103,15 @@ storage_class =
 .PP
 If you are using an older version of CEPH (e.g.
 10.2.x Jewel) and a version of rclone before v1.59 then you may need to
-supply the parameter \f[C]--s3-upload-cutoff 0\f[R] or put this in the
-config file as \f[C]upload_cutoff 0\f[R] to work around a bug which
+supply the parameter \f[V]--s3-upload-cutoff 0\f[R] or put this in the
+config file as \f[V]upload_cutoff 0\f[R] to work around a bug which
 causes uploading of small files to fail.
 .PP
-Note also that Ceph sometimes puts \f[C]/\f[R] in the passwords it gives
+Note also that Ceph sometimes puts \f[V]/\f[R] in the passwords it gives
 users.
 If you read the secret access key using the command line tools you will
-get a JSON blob with the \f[C]/\f[R] escaped as \f[C]\[rs]/\f[R].
-Make sure you only write \f[C]/\f[R] in the secret access key.
+get a JSON blob with the \f[V]/\f[R] escaped as \f[V]\[rs]/\f[R].
+Make sure you only write \f[V]/\f[R] in the secret access key.
 .PP
 Eg the dump from Ceph looks something like this (irrelevant keys
 removed).
@@ -36084,8 +36132,8 @@ removed).
 \f[R]
 .fi
 .PP
-Because this is a json dump, it is encoding the \f[C]/\f[R] as
-\f[C]\[rs]/\f[R], so if you use the secret key as \f[C]xxxxxx/xxxx\f[R]
+Because this is a json dump, it is encoding the \f[V]/\f[R] as
+\f[V]\[rs]/\f[R], so if you use the secret key as \f[V]xxxxxx/xxxx\f[R]
 it will work fine.
 .SS Cloudflare R2
 .PP
@@ -36194,18 +36242,18 @@ acl = private
 \f[R]
 .fi
 .PP
-Now run \f[C]rclone lsf r2:\f[R] to see your buckets and
-\f[C]rclone lsf r2:bucket\f[R] to look within a bucket.
+Now run \f[V]rclone lsf r2:\f[R] to see your buckets and
+\f[V]rclone lsf r2:bucket\f[R] to look within a bucket.
 .PP
 For R2 tokens with the \[dq]Object Read & Write\[dq] permission, you may
-also need to add \f[C]no_check_bucket = true\f[R] for object uploads to
+also need to add \f[V]no_check_bucket = true\f[R] for object uploads to
 work correctly.
 .PP
 Note that Cloudflare decompresses files uploaded with
-\f[C]Content-Encoding: gzip\f[R] by default which is a deviation from
+\f[V]Content-Encoding: gzip\f[R] by default which is a deviation from
 what AWS does.
 If this is causing a problem then upload the files with
-\f[C]--header-upload \[dq]Cache-Control: no-transform\[dq]\f[R]
+\f[V]--header-upload \[dq]Cache-Control: no-transform\[dq]\f[R]
 .SS Dreamhost
 .PP
 Dreamhost DreamObjects (https://www.dreamhost.com/cloud/storage/) is an
@@ -36253,7 +36301,7 @@ endpoint = https://storage.googleapis.com
 \f[R]
 .fi
 .PP
-\f[B]Note\f[R] that \f[C]--s3-versions\f[R] does not work with GCS when
+\f[B]Note\f[R] that \f[V]--s3-versions\f[R] does not work with GCS when
 it needs to do directory paging.
 Rclone will return the error:
 .IP
@@ -36276,17 +36324,17 @@ key.
 These can be retrieved on the \[dq]Applications &
 API (https://cloud.digitalocean.com/settings/api/tokens)\[dq] page of
 the DigitalOcean control panel.
-They will be needed when prompted by \f[C]rclone config\f[R] for your
-\f[C]access_key_id\f[R] and \f[C]secret_access_key\f[R].
+They will be needed when prompted by \f[V]rclone config\f[R] for your
+\f[V]access_key_id\f[R] and \f[V]secret_access_key\f[R].
 .PP
-When prompted for a \f[C]region\f[R] or \f[C]location_constraint\f[R],
+When prompted for a \f[V]region\f[R] or \f[V]location_constraint\f[R],
 press enter to use the default value.
-The region must be included in the \f[C]endpoint\f[R] setting (e.g.
-\f[C]nyc3.digitaloceanspaces.com\f[R]).
+The region must be included in the \f[V]endpoint\f[R] setting (e.g.
+\f[V]nyc3.digitaloceanspaces.com\f[R]).
 The default values can be used for other settings.
 .PP
 Going through the whole process of creating a new remote by running
-\f[C]rclone config\f[R], each prompt should be answered as shown below:
+\f[V]rclone config\f[R], each prompt should be answered as shown below:
 .IP
 .nf
 \f[C]
@@ -36800,9 +36848,9 @@ by selecting \f[B]Manager resources\f[R] > \f[B]Object Storage Key
 Manager\f[R].
 .PP
 Here is an example of a configuration.
-First, run \f[C]rclone config\f[R].
+First, run \f[V]rclone config\f[R].
 This will walk you through an interactive setup process.
-Type \f[C]n\f[R] to add the new remote, and then enter a name:
+Type \f[V]n\f[R] to add the new remote, and then enter a name:
 .IP
 .nf
 \f[C]
@@ -36811,7 +36859,7 @@ name> ionos-fra
 \f[R]
 .fi
 .PP
-Type \f[C]s3\f[R] to choose the connection type:
+Type \f[V]s3\f[R] to choose the connection type:
 .IP
 .nf
 \f[C]
@@ -36826,7 +36874,7 @@ Storage> s3
 \f[R]
 .fi
 .PP
-Type \f[C]IONOS\f[R]:
+Type \f[V]IONOS\f[R]:
 .IP
 .nf
 \f[C]
@@ -36843,7 +36891,7 @@ provider> IONOS
 .fi
 .PP
 Press Enter to choose the default option
-\f[C]Enter AWS credentials in the next step\f[R]:
+\f[V]Enter AWS credentials in the next step\f[R]:
 .IP
 .nf
 \f[C]
@@ -36951,7 +36999,7 @@ y/n>
 \f[R]
 .fi
 .PP
-Press Enter to save the configuration, and then \f[C]q\f[R] to quit the
+Press Enter to save the configuration, and then \f[V]q\f[R] to quit the
 configuration process:
 .IP
 .nf
@@ -36971,8 +37019,9 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Done! Now you can try some commands (for macOS, use \f[C]./rclone\f[R]
-instead of \f[C]rclone\f[R]).
+Done!
+Now you can try some commands (for macOS, use \f[V]./rclone\f[R] instead
+of \f[V]rclone\f[R]).
 .IP "1)" 3
 Create a bucket (the name must be unique within the whole IONOS S3)
 .IP
@@ -37051,7 +37100,7 @@ Drive Capacity: 26 GiB Free, 165 GiB Total
 \f[R]
 .fi
 .PP
-These details need to go into \f[C]rclone config\f[R] like this.
+These details need to go into \f[V]rclone config\f[R] like this.
 Note that it is important to put the region in as stated above.
 .IP
 .nf
@@ -37101,7 +37150,7 @@ Kodo can be widely applied to mass data management.
 .PP
 To configure access to Qiniu Kodo, follow the steps below:
 .IP "1." 3
-Run \f[C]rclone config\f[R] and select \f[C]n\f[R] for a new remote.
+Run \f[V]rclone config\f[R] and select \f[V]n\f[R] for a new remote.
 .IP
 .nf
 \f[C]
@@ -37123,7 +37172,7 @@ name> qiniu
 \f[R]
 .fi
 .IP "3." 3
-Select \f[C]s3\f[R] storage.
+Select \f[V]s3\f[R] storage.
 .IP
 .nf
 \f[C]
@@ -37136,7 +37185,7 @@ Storage> s3
 \f[R]
 .fi
 .IP "4." 3
-Select \f[C]Qiniu\f[R] provider.
+Select \f[V]Qiniu\f[R] provider.
 .IP
 .nf
 \f[C]
@@ -37317,11 +37366,11 @@ sovereignty.
 Before you can use RackCorp Object Storage, you\[aq]ll need to \[dq]sign
 up (https://www.rackcorp.com/signup)\[dq] for an account on our
 \[dq]portal (https://portal.rackcorp.com)\[dq].
-Next you can create an \f[C]access key\f[R], a \f[C]secret key\f[R] and
-\f[C]buckets\f[R], in your location of choice with ease.
+Next you can create an \f[V]access key\f[R], a \f[V]secret key\f[R] and
+\f[V]buckets\f[R], in your location of choice with ease.
 These details are required for the next steps of configuration, when
-\f[C]rclone config\f[R] asks for your \f[C]access_key_id\f[R] and
-\f[C]secret_access_key\f[R].
+\f[V]rclone config\f[R] asks for your \f[V]access_key_id\f[R] and
+\f[V]secret_access_key\f[R].
 .PP
 Your config should end up looking a bit like this:
 .IP
@@ -37344,7 +37393,7 @@ Rclone can serve any remote over the S3 protocol.
 For details see the rclone serve
 s3 (https://rclone.org/commands/rclone_serve_http/) documentation.
 .PP
-For example, to serve \f[C]remote:path\f[R] over s3, run the server like
+For example, to serve \f[V]remote:path\f[R] over s3, run the server like
 this:
 .IP
 .nf
@@ -37368,7 +37417,7 @@ use_multipart_uploads = false
 \f[R]
 .fi
 .PP
-Note that setting \f[C]disable_multipart_uploads = true\f[R] is to work
+Note that setting \f[V]disable_multipart_uploads = true\f[R] is to work
 around a bug (https://rclone.org/commands/rclone_serve_http/#bugs) which
 will be fixed in due course.
 .SS Scaleway
@@ -37402,9 +37451,9 @@ copy_cutoff = 5M
 .PP
 Scaleway Glacier (https://www.scaleway.com/en/glacier-cold-storage/) is
 the low-cost S3 Glacier alternative from Scaleway and it works the same
-way as on S3 by accepting the \[dq]GLACIER\[dq] \f[C]storage_class\f[R].
+way as on S3 by accepting the \[dq]GLACIER\[dq] \f[V]storage_class\f[R].
 So you can configure your remote with the
-\f[C]storage_class = GLACIER\f[R] option to upload directly to Scaleway
+\f[V]storage_class = GLACIER\f[R] option to upload directly to Scaleway
 Glacier.
 Don\[aq]t forget that in this state you can\[aq]t read files back after,
 you will need to restore them to \[dq]STANDARD\[dq] storage_class first
@@ -37416,7 +37465,7 @@ Cloud (https://www.seagate.com/gb/en/services/cloud/storage/) is an S3
 compatible object storage platform from Seagate (https://seagate.com/)
 intended for enterprise use.
 .PP
-Here is a config run through for a remote called \f[C]remote\f[R] - you
+Here is a config run through for a remote called \f[V]remote\f[R] - you
 may choose a different name of course.
 Note that to create an access key and secret key you will need to create
 a service account first.
@@ -37433,7 +37482,7 @@ name> remote
 \f[R]
 .fi
 .PP
-Choose \f[C]s3\f[R] backend
+Choose \f[V]s3\f[R] backend
 .IP
 .nf
 \f[C]
@@ -37447,7 +37496,7 @@ Storage> s3
 \f[R]
 .fi
 .PP
-Choose \f[C]LyveCloud\f[R] as S3 provider
+Choose \f[V]LyveCloud\f[R] as S3 provider
 .IP
 .nf
 \f[C]
@@ -37544,7 +37593,7 @@ location_constraint>
 \f[R]
 .fi
 .PP
-Choose default ACL (\f[C]private\f[R]).
+Choose default ACL (\f[V]private\f[R]).
 .IP
 .nf
 \f[C]
@@ -37586,7 +37635,7 @@ store (https://github.com/chrislusf/seaweedfs/wiki/Gateway-to-Remote-Object-Stor
 to cache data and metadata with asynchronous write back, for fast local
 speed and minimize access cost.
 .PP
-Assuming the SeaweedFS are configured with \f[C]weed shell\f[R] as such:
+Assuming the SeaweedFS are configured with \f[V]weed shell\f[R] as such:
 .IP
 .nf
 \f[C]
@@ -38133,7 +38182,7 @@ and secure your data in a 100% French cloud, independent of GAFAM..
 .PP
 To configure access to Leviia, follow the steps below:
 .IP "1." 3
-Run \f[C]rclone config\f[R] and select \f[C]n\f[R] for a new remote.
+Run \f[V]rclone config\f[R] and select \f[V]n\f[R] for a new remote.
 .IP
 .nf
 \f[C]
@@ -38155,7 +38204,7 @@ name> leviia
 \f[R]
 .fi
 .IP "3." 3
-Select \f[C]s3\f[R] storage.
+Select \f[V]s3\f[R] storage.
 .IP
 .nf
 \f[C]
@@ -38168,7 +38217,7 @@ Storage> s3
 \f[R]
 .fi
 .IP "4." 3
-Select \f[C]Leviia\f[R] provider.
+Select \f[V]Leviia\f[R] provider.
 .IP
 .nf
 \f[C]
@@ -38581,7 +38630,7 @@ Option endpoint.
 Endpoint for Magalu Object Storage API.
 Choose a number from below, or type in your own value.
 Press Enter to leave empty.
- 1 / S\[~a]o Paulo, SP (BR), br-se1
+ 1 / São Paulo, SP (BR), br-se1
    \[rs] (br-se1.magaluobjects.com)
  2 / Fortaleza, CE (BR), br-ne1
    \[rs] (br-ne1.magaluobjects.com)
@@ -38759,7 +38808,7 @@ It is secure, stable, massive, convenient, low-delay and low-cost.
 .PP
 To configure access to Tencent COS, follow the steps below:
 .IP "1." 3
-Run \f[C]rclone config\f[R] and select \f[C]n\f[R] for a new remote.
+Run \f[V]rclone config\f[R] and select \f[V]n\f[R] for a new remote.
 .IP
 .nf
 \f[C]
@@ -38781,7 +38830,7 @@ name> cos
 \f[R]
 .fi
 .IP "3." 3
-Select \f[C]s3\f[R] storage.
+Select \f[V]s3\f[R] storage.
 .IP
 .nf
 \f[C]
@@ -38794,7 +38843,7 @@ Storage> s3
 \f[R]
 .fi
 .IP "4." 3
-Select \f[C]TencentCOS\f[R] provider.
+Select \f[V]TencentCOS\f[R] provider.
 .IP
 .nf
 \f[C]
@@ -38899,8 +38948,8 @@ cos                  s3
 .SS Netease NOS
 .PP
 For Netease NOS configure as per the configurator
-\f[C]rclone config\f[R] setting the provider \f[C]Netease\f[R].
-This will automatically set \f[C]force_path_style = false\f[R] which is
+\f[V]rclone config\f[R] setting the provider \f[V]Netease\f[R].
+This will automatically set \f[V]force_path_style = false\f[R] which is
 necessary for it to run properly.
 .SS Petabox
 .PP
@@ -38980,7 +39029,7 @@ Press Enter to leave empty.
    \[rs] (ap-southeast-1)
  4 / Middle East (Bahrain)
    \[rs] (me-south-1)
- 5 / South America (S\[~a]o Paulo)
+ 5 / South America (São Paulo)
    \[rs] (sa-east-1)
 region> 1
 
@@ -38998,7 +39047,7 @@ Choose a number from below, or type in your own value.
    \[rs] (s3.ap-southeast-1.petabox.io)
  5 / Middle East (Bahrain)
    \[rs] (s3.me-south-1.petabox.io)
- 6 / South America (S\[~a]o Paulo)
+ 6 / South America (São Paulo)
    \[rs] (s3.sa-east-1.petabox.io)
 endpoint> 1
 
@@ -39073,8 +39122,8 @@ endpoint = s3.petabox.io
 Storj is a decentralized cloud storage which can be used through its
 native protocol or an S3 compatible gateway.
 .PP
-The S3 compatible gateway is configured using \f[C]rclone config\f[R]
-with a type of \f[C]s3\f[R] and with a provider name of \f[C]Storj\f[R].
+The S3 compatible gateway is configured using \f[V]rclone config\f[R]
+with a type of \f[V]s3\f[R] and with a provider name of \f[V]Storj\f[R].
 Here is an example run of the configurator.
 .IP
 .nf
@@ -39122,7 +39171,7 @@ Note that s3 credentials are generated when you create an access
 grant (https://docs.storj.io/dcs/api-reference/s3-compatible-gateway#usage).
 .SS Backend quirks
 .IP \[bu] 2
-\f[C]--chunk-size\f[R] is forced to be 64 MiB or greater.
+\f[V]--chunk-size\f[R] is forced to be 64 MiB or greater.
 This will use more memory than the default of 5 MiB.
 .IP \[bu] 2
 Server side copy is disabled as it isn\[aq]t currently supported in the
@@ -39139,38 +39188,38 @@ stored, nor is any MD5SUM (if one is available from the source).
 .PP
 This has the following consequences:
 .IP \[bu] 2
-Using \f[C]rclone rcat\f[R] will fail as the medatada doesn\[aq]t match
+Using \f[V]rclone rcat\f[R] will fail as the medatada doesn\[aq]t match
 after upload
 .IP \[bu] 2
-Uploading files with \f[C]rclone mount\f[R] will fail for the same
+Uploading files with \f[V]rclone mount\f[R] will fail for the same
 reason
 .RS 2
 .IP \[bu] 2
-This can worked around by using \f[C]--vfs-cache-mode writes\f[R] or
-\f[C]--vfs-cache-mode full\f[R] or setting \f[C]--s3-upload-cutoff\f[R]
+This can worked around by using \f[V]--vfs-cache-mode writes\f[R] or
+\f[V]--vfs-cache-mode full\f[R] or setting \f[V]--s3-upload-cutoff\f[R]
 large
 .RE
 .IP \[bu] 2
 Files uploaded via a multipart upload won\[aq]t have their modtimes
 .RS 2
 .IP \[bu] 2
-This will mean that \f[C]rclone sync\f[R] will likely keep trying to
-upload files bigger than \f[C]--s3-upload-cutoff\f[R]
+This will mean that \f[V]rclone sync\f[R] will likely keep trying to
+upload files bigger than \f[V]--s3-upload-cutoff\f[R]
 .IP \[bu] 2
-This can be worked around with \f[C]--checksum\f[R] or
-\f[C]--size-only\f[R] or setting \f[C]--s3-upload-cutoff\f[R] large
+This can be worked around with \f[V]--checksum\f[R] or
+\f[V]--size-only\f[R] or setting \f[V]--s3-upload-cutoff\f[R] large
 .IP \[bu] 2
-The maximum value for \f[C]--s3-upload-cutoff\f[R] is 5GiB though
+The maximum value for \f[V]--s3-upload-cutoff\f[R] is 5GiB though
 .RE
 .PP
 One general purpose workaround is to set
-\f[C]--s3-upload-cutoff 5G\f[R].
+\f[V]--s3-upload-cutoff 5G\f[R].
 This means that rclone will upload files smaller than 5GiB as single
 parts.
 Note that this can be set in the config file with
-\f[C]upload_cutoff = 5G\f[R] or configured in the advanced settings.
+\f[V]upload_cutoff = 5G\f[R] or configured in the advanced settings.
 If you regularly transfer files larger than 5G then using
-\f[C]--checksum\f[R] or \f[C]--size-only\f[R] in \f[C]rclone sync\f[R]
+\f[V]--checksum\f[R] or \f[V]--size-only\f[R] in \f[V]rclone sync\f[R]
 is the recommended workaround.
 .SS Comparison with the native protocol
 .PP
@@ -39212,9 +39261,9 @@ At some point rclone will gain a sync mode which is effectively this
 workaround but built in to rclone.
 .SS Limitations
 .PP
-\f[C]rclone about\f[R] is not supported by the S3 backend.
+\f[V]rclone about\f[R] is not supported by the S3 backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -39227,9 +39276,9 @@ Storage (https://c2.synology.com/en-global/object-storage/overview)
 provides a secure, S3-compatible, and cost-effective cloud storage
 solution without API request, download fees, and deletion penalty.
 .PP
-The S3 compatible gateway is configured using \f[C]rclone config\f[R]
-with a type of \f[C]s3\f[R] and with a provider name of
-\f[C]Synology\f[R].
+The S3 compatible gateway is configured using \f[V]rclone config\f[R]
+with a type of \f[V]s3\f[R] and with a provider name of
+\f[V]Synology\f[R].
 Here is an example run of the configurator.
 .PP
 First run:
@@ -39365,9 +39414,10 @@ y/e/d> y
 B2 is Backblaze\[aq]s cloud storage
 system (https://www.backblaze.com/cloud-storage).
 .PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:bucket/path/to/dir\f[R].
+Paths are specified as \f[V]remote:bucket\f[R] (or \f[V]remote:\f[R] for
+the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:bucket/path/to/dir\f[R].
 .SS Configuration
 .PP
 Here is an example of making a b2 configuration.
@@ -39421,7 +39471,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this
+This remote is called \f[V]remote\f[R] and can now be used like this
 .PP
 See all buckets
 .IP
@@ -39447,7 +39497,7 @@ rclone ls remote:bucket
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote bucket, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote bucket, deleting any
 excess files in the bucket.
 .IP
 .nf
@@ -39465,23 +39515,23 @@ You can use these with rclone too; you will need to use rclone version
 1.43 or later.
 .PP
 Follow Backblaze\[aq]s docs to create an Application Key with the
-required permission and add the \f[C]applicationKeyId\f[R] as the
-\f[C]account\f[R] and the \f[C]Application Key\f[R] itself as the
-\f[C]key\f[R].
+required permission and add the \f[V]applicationKeyId\f[R] as the
+\f[V]account\f[R] and the \f[V]Application Key\f[R] itself as the
+\f[V]key\f[R].
 .PP
 Note that you must put the \f[I]applicationKeyId\f[R] as the
-\f[C]account\f[R] \[en] you can\[aq]t use the master Account ID.
+\f[V]account\f[R] \[en] you can\[aq]t use the master Account ID.
 If you try then B2 will return 401 errors.
 .SS --fast-list
 .PP
-This remote supports \f[C]--fast-list\f[R] which allows you to use fewer
+This remote supports \f[V]--fast-list\f[R] which allows you to use fewer
 transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
 .SS Modification times
 .PP
 The modification time is stored as metadata on the object as
-\f[C]X-Bz-Info-src_last_modified_millis\f[R] as milliseconds since
+\f[V]X-Bz-Info-src_last_modified_millis\f[R] as milliseconds since
 1970-01-01 in the Backblaze standard.
 Other tools should be able to use this as a modified time.
 .PP
@@ -39510,7 +39560,7 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -39522,17 +39572,17 @@ Note that in 2020-05 Backblaze started allowing \ characters in file
 names.
 Rclone hasn\[aq]t changed its encoding as this could cause syncs to
 re-transfer files.
-If you want rclone not to replace \ then see the \f[C]--b2-encoding\f[R]
-flag below and remove the \f[C]BackSlash\f[R] from the string.
+If you want rclone not to replace \ then see the \f[V]--b2-encoding\f[R]
+flag below and remove the \f[V]BackSlash\f[R] from the string.
 This can be set in the config.
 .SS SHA1 checksums
 .PP
 The SHA1 checksums of the files are checked on upload and download and
 will be used in the syncing process.
 .PP
-Large files (bigger than the limit in \f[C]--b2-upload-cutoff\f[R])
+Large files (bigger than the limit in \f[V]--b2-upload-cutoff\f[R])
 which are uploaded in chunks will store their SHA1 on the object as
-\f[C]X-Bz-Info-large_file_sha1\f[R] as recommended by Backblaze.
+\f[V]X-Bz-Info-large_file_sha1\f[R] as recommended by Backblaze.
 .PP
 For a large file to be uploaded with an SHA1 checksum, the source needs
 to support SHA1 checksums.
@@ -39541,28 +39591,28 @@ local disk will have an SHA1.
 See the overview (https://rclone.org/overview/#features) for exactly
 which remotes support SHA1.
 .PP
-Sources which don\[aq]t support SHA1, in particular \f[C]crypt\f[R] will
+Sources which don\[aq]t support SHA1, in particular \f[V]crypt\f[R] will
 upload large files without SHA1 checksums.
 This may be fixed in the future (see
 #1767 (https://github.com/rclone/rclone/issues/1767)).
 .PP
-Files sizes below \f[C]--b2-upload-cutoff\f[R] will always have an SHA1
+Files sizes below \f[V]--b2-upload-cutoff\f[R] will always have an SHA1
 regardless of the source.
 .SS Transfers
 .PP
 Backblaze recommends that you do lots of transfers simultaneously for
 maximum speed.
 In tests from my SSD equipped laptop the optimum setting is about
-\f[C]--transfers 32\f[R] though higher numbers may be used for a slight
+\f[V]--transfers 32\f[R] though higher numbers may be used for a slight
 speed improvement.
 The optimum number for you may vary depending on your hardware, how big
 the files are, how much you want to load your computer, etc.
-The default of \f[C]--transfers 4\f[R] is definitely too low for
+The default of \f[V]--transfers 4\f[R] is definitely too low for
 Backblaze B2 though.
 .PP
 Note that uploading big files (bigger than 200 MiB by default) will use
 a 96 MiB RAM buffer by default.
-There can be at most \f[C]--transfers\f[R] of these in use at any
+There can be at most \f[V]--transfers\f[R] of these in use at any
 moment, so this sets the upper limit on the memory used.
 .SS Versions
 .PP
@@ -39579,50 +39629,50 @@ panel or when creating the bucket using the --b2-lifecycle flag or after
 creation using the rclone backend lifecycle command.
 .PP
 You may opt in to a \[dq]hard delete\[dq] of files with the
-\f[C]--b2-hard-delete\f[R] flag which permanently removes files on
+\f[V]--b2-hard-delete\f[R] flag which permanently removes files on
 deletion instead of hiding them.
 .PP
 Old versions of files, where available, are visible using the
-\f[C]--b2-versions\f[R] flag.
+\f[V]--b2-versions\f[R] flag.
 .PP
 It is also possible to view a bucket as it was at a certain point in
-time, using the \f[C]--b2-version-at\f[R] flag.
+time, using the \f[V]--b2-version-at\f[R] flag.
 This will show the file versions as they were at that time, showing
 files that have been deleted afterwards, and hiding files that were
 created since.
 .PP
 If you wish to remove all the old versions, and unfinished large file
-uploads, then you can use the \f[C]rclone cleanup remote:bucket\f[R]
+uploads, then you can use the \f[V]rclone cleanup remote:bucket\f[R]
 command which will delete all the old versions of files, leaving the
 current ones intact.
 You can also supply a path and only old versions under that path will be
 deleted, e.g.
-\f[C]rclone cleanup remote:bucket/path/to/stuff\f[R].
+\f[V]rclone cleanup remote:bucket/path/to/stuff\f[R].
 .PP
-Note that \f[C]cleanup\f[R] will remove partially uploaded files from
+Note that \f[V]cleanup\f[R] will remove partially uploaded files from
 the bucket if they are more than a day old.
 If you want more control over the expiry date then run
-\f[C]rclone backend cleanup b2:bucket -o max-age=1h\f[R] to remove all
+\f[V]rclone backend cleanup b2:bucket -o max-age=1h\f[R] to remove all
 unfinished large file uploads older than one hour, leaving old versions
 intact.
 .PP
 If you wish to remove all the old versions, leaving current files and
 unfinished large files intact, then you can use the
-\f[C]rclone backend cleanup-hidden remote:bucket\f[R] command.
+\f[V]rclone backend cleanup-hidden remote:bucket\f[R] command.
 You can also supply a path and only old versions under that path will be
 deleted, e.g.
-\f[C]rclone backend cleanup-hidden remote:bucket/path/to/stuff\f[R].
+\f[V]rclone backend cleanup-hidden remote:bucket/path/to/stuff\f[R].
 .PP
-When you \f[C]purge\f[R] a bucket, the current and the old versions will
+When you \f[V]purge\f[R] a bucket, the current and the old versions will
 be deleted then the bucket will be deleted.
 .PP
-However \f[C]delete\f[R] will cause the current versions of the files to
+However \f[V]delete\f[R] will cause the current versions of the files to
 become hidden old versions.
 .PP
 Here is a session showing the listing and retrieval of an old version
-followed by a \f[C]cleanup\f[R] of the old versions.
+followed by a \f[V]cleanup\f[R] of the old versions.
 .PP
-Show current version and all the versions with \f[C]--b2-versions\f[R]
+Show current version and all the versions with \f[V]--b2-versions\f[R]
 flag.
 .IP
 .nf
@@ -39664,7 +39714,7 @@ $ rclone -q --b2-versions ls b2:cleanup-test
 .fi
 .SS Versions naming caveat
 .PP
-When using \f[C]--b2-versions\f[R] flag rclone is relying on the file
+When using \f[V]--b2-versions\f[R] flag rclone is relying on the file
 name to work out whether the objects are versions or not.
 Versions\[aq] names are created by inserting timestamp between file name
 and its extension.
@@ -39678,7 +39728,7 @@ and its extension.
 .fi
 .PP
 If there are real files present with the same names as versions, then
-behaviour of \f[C]--b2-versions\f[R] can be unpredictable.
+behaviour of \f[V]--b2-versions\f[R] can be unpredictable.
 .SS Data usage
 .PP
 It is useful to know how many requests are sent to the server in
@@ -39695,7 +39745,7 @@ All copy commands send the following 4 requests:
 \f[R]
 .fi
 .PP
-The \f[C]b2_list_file_names\f[R] request will be sent once for every 1k
+The \f[V]b2_list_file_names\f[R] request will be sent once for every 1k
 files in the remote path, providing the checksum and modification time
 of the listed files.
 As of version 1.33 issue
@@ -39727,11 +39777,11 @@ start and finish the upload) and another 2 requests for each chunk:
 .fi
 .SS Versions
 .PP
-Versions can be viewed with the \f[C]--b2-versions\f[R] flag.
+Versions can be viewed with the \f[V]--b2-versions\f[R] flag.
 When it is set rclone will show and act on older versions of files.
 For example
 .PP
-Listing without \f[C]--b2-versions\f[R]
+Listing without \f[V]--b2-versions\f[R]
 .IP
 .nf
 \f[C]
@@ -39757,7 +39807,7 @@ seen.
 These have the UTC date that they were uploaded to the server to the
 nearest millisecond appended to them.
 .PP
-Note that when using \f[C]--b2-versions\f[R] no file write operations
+Note that when using \f[V]--b2-versions\f[R] no file write operations
 are permitted, so you can\[aq]t upload files or delete them.
 .SS B2 and rclone link
 .PP
@@ -39781,7 +39831,7 @@ https://f002.backblazeb2.com/file/bucket/path?Authorization=xxxxxxxx
 .fi
 .PP
 you can then use the authorization token (the part of the url from the
-\f[C]?Authorization=\f[R] on) on any file path under that directory.
+\f[V]?Authorization=\f[R] on) on any file path under that directory.
 For example:
 .IP
 .nf
@@ -40291,9 +40341,9 @@ rclone backend cleanup-hidden b2:bucket/path/to/dir
 .fi
 .SS Limitations
 .PP
-\f[C]rclone about\f[R] is not supported by the B2 backend.
+\f[V]rclone about\f[R] is not supported by the B2 backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -40301,18 +40351,18 @@ about (https://rclone.org/overview/#optional-features) and rclone
 about (https://rclone.org/commands/rclone_about/)
 .SH Box
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .PP
 The initial setup for Box involves getting a token from Box which you
 can do either in your browser, or with a config.json downloaded from Box
 to use JWT authentication.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -40391,10 +40441,10 @@ Note that rclone runs a webserver on your local machine to collect the
 token as returned from Box.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this it may require you
 to unblock it temporarily if you are running a host firewall.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Box
 .IP
@@ -40449,7 +40499,7 @@ places
 Get an error on a token refresh
 .PP
 then rclone will return an error which includes the text
-\f[C]Invalid refresh token\f[R].
+\f[V]Invalid refresh token\f[R].
 .PP
 To fix this you will need to use oauth2 again to update the refresh
 token.
@@ -40528,7 +40578,7 @@ y/e/d> y
 Box allows modification times to be set on objects accurate to 1 second.
 These will be used to detect whether objects need syncing or not.
 .PP
-Box supports SHA1 type hashes, so you can use the \f[C]--checksum\f[R]
+Box supports SHA1 type hashes, so you can use the \f[V]--checksum\f[R]
 flag.
 .SS Restricted filename characters
 .PP
@@ -40552,7 +40602,7 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -40575,7 +40625,7 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 .TE
 .PP
@@ -40585,10 +40635,10 @@ be used in JSON strings.
 .SS Transfers
 .PP
 For files above 50 MiB rclone will use a chunked transfer.
-Rclone will upload up to \f[C]--transfers\f[R] chunks at the same time
+Rclone will upload up to \f[V]--transfers\f[R] chunks at the same time
 (shared among all the multipart uploads).
 Chunks are buffered in memory and are normally 8 MiB so increasing
-\f[C]--transfers\f[R] will increase memory use.
+\f[V]--transfers\f[R] will increase memory use.
 .SS Deleting files
 .PP
 Depending on the enterprise settings for your user, the item will either
@@ -40601,8 +40651,8 @@ Emptying the trash via the WebUI does not have this limitation so it is
 advised to empty the trash via the WebUI.
 .SS Root folder ID
 .PP
-You can set the \f[C]root_folder_id\f[R] for rclone.
-This is the directory (identified by its \f[C]Folder ID\f[R]) that
+You can set the \f[V]root_folder_id\f[R] for rclone.
+This is the directory (identified by its \f[V]Folder ID\f[R]) that
 rclone considers to be the root of your Box drive.
 .PP
 Normally you will leave this blank and rclone will determine the correct
@@ -40611,14 +40661,14 @@ root to use itself.
 However you can set this to restrict rclone to a specific folder
 hierarchy.
 .PP
-In order to do this you will have to find the \f[C]Folder ID\f[R] of the
+In order to do this you will have to find the \f[V]Folder ID\f[R] of the
 directory you wish rclone to display.
 This will be the last segment of the URL when you open the relevant
 folder in the Box web interface.
 .PP
 So if the folder you want rclone to use has a URL which looks like
-\f[C]https://app.box.com/folder/11xxxxxxxxx8\f[R] in the browser, then
-you use \f[C]11xxxxxxxxx8\f[R] as the \f[C]root_folder_id\f[R] in the
+\f[V]https://app.box.com/folder/11xxxxxxxxx8\f[R] in the browser, then
+you use \f[V]11xxxxxxxxx8\f[R] as the \f[V]root_folder_id\f[R] in the
 config.
 .SS Standard options
 .PP
@@ -40659,8 +40709,8 @@ Box App config.json location
 .PP
 Leave blank normally.
 .PP
-Leading \f[C]\[ti]\f[R] will be expanded in the file name as will
-environment variables such as \f[C]${RCLONE_CONFIG_DIR}\f[R].
+Leading \f[V]\[ti]\f[R] will be expanded in the file name as will
+environment variables such as \f[V]${RCLONE_CONFIG_DIR}\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -40881,9 +40931,9 @@ Required: false
 Note that Box is case insensitive so you can\[aq]t have a file called
 \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .PP
-Box file names can\[aq]t have the \f[C]\[rs]\f[R] character in.
+Box file names can\[aq]t have the \f[V]\[rs]\f[R] character in.
 rclone maps this to and from an identical looking unicode equivalent
-\f[C]\[uFF3C]\f[R] (U+FF3C Fullwidth Reverse Solidus).
+\f[V]＼\f[R] (U+FF3C Fullwidth Reverse Solidus).
 .PP
 Box only supports filenames up to 255 characters in length.
 .PP
@@ -40891,9 +40941,9 @@ Box has API rate
 limits (https://developer.box.com/guides/api-calls/permissions-and-errors/rate-limits/)
 that sometimes reduce the speed of rclone.
 .PP
-\f[C]rclone about\f[R] is not supported by the Box backend.
+\f[V]rclone about\f[R] is not supported by the Box backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -40904,39 +40954,39 @@ about (https://rclone.org/commands/rclone_about/)
 Here is how to create your own Box App ID for rclone:
 .IP "1." 3
 Go to the Box Developer Console (https://app.box.com/developers/console)
-and login, then click \f[C]My Apps\f[R] on the sidebar.
-Click \f[C]Create New App\f[R] and select \f[C]Custom App\f[R].
+and login, then click \f[V]My Apps\f[R] on the sidebar.
+Click \f[V]Create New App\f[R] and select \f[V]Custom App\f[R].
 .IP "2." 3
 In the first screen on the box that pops up, you can pretty much enter
 whatever you want.
-The \f[C]App Name\f[R] can be whatever.
-For \f[C]Purpose\f[R] choose automation to avoid having to fill out
+The \f[V]App Name\f[R] can be whatever.
+For \f[V]Purpose\f[R] choose automation to avoid having to fill out
 anything else.
-Click \f[C]Next\f[R].
+Click \f[V]Next\f[R].
 .IP "3." 3
 In the second screen of the creation screen, select
-\f[C]User Authentication (OAuth 2.0)\f[R].
-Then click \f[C]Create App\f[R].
+\f[V]User Authentication (OAuth 2.0)\f[R].
+Then click \f[V]Create App\f[R].
 .IP "4." 3
-You should now be on the \f[C]Configuration\f[R] tab of your new app.
+You should now be on the \f[V]Configuration\f[R] tab of your new app.
 If not, click on it at the top of the webpage.
-Copy down \f[C]Client ID\f[R] and \f[C]Client Secret\f[R], you\[aq]ll
+Copy down \f[V]Client ID\f[R] and \f[V]Client Secret\f[R], you\[aq]ll
 need those for rclone.
 .IP "5." 3
 Under \[dq]OAuth 2.0 Redirect URI\[dq], add
-\f[C]http://127.0.0.1:53682/\f[R]
+\f[V]http://127.0.0.1:53682/\f[R]
 .IP "6." 3
-For \f[C]Application Scopes\f[R], select
-\f[C]Read all files and folders stored in Box\f[R] and
-\f[C]Write all files and folders stored in box\f[R] (assuming you want
+For \f[V]Application Scopes\f[R], select
+\f[V]Read all files and folders stored in Box\f[R] and
+\f[V]Write all files and folders stored in box\f[R] (assuming you want
 to do both).
 Leave others unchecked.
-Click \f[C]Save Changes\f[R] at the top right.
+Click \f[V]Save Changes\f[R] at the top right.
 .SH Cache
 .PP
-The \f[C]cache\f[R] remote wraps another existing remote and stores file
+The \f[V]cache\f[R] remote wraps another existing remote and stores file
 structure and its data for long running tasks like
-\f[C]rclone mount\f[R].
+\f[V]rclone mount\f[R].
 .SS Status
 .PP
 The cache backend code is working but it currently doesn\[aq]t have a
@@ -40955,9 +41005,9 @@ backend isn\[aq]t needed in those scenarios any more.
 .SS Configuration
 .PP
 To get started you just need to have an existing remote which can be
-configured with \f[C]cache\f[R].
+configured with \f[V]cache\f[R].
 .PP
-Here is an example of how to make a remote called \f[C]test-cache\f[R].
+Here is an example of how to make a remote called \f[V]test-cache\f[R].
 First run:
 .IP
 .nf
@@ -41076,7 +41126,7 @@ rclone mount --allow-other test-cache: /var/tmp/test-cache
 .PP
 In an effort to make writing through cache more reliable, the backend
 now supports this feature which can be activated by specifying a
-\f[C]cache-tmp-upload-path\f[R].
+\f[V]cache-tmp-upload-path\f[R].
 .PP
 A files goes through these states when using this feature:
 .IP "1." 3
@@ -41086,8 +41136,8 @@ When the copy to the temporary location is complete the file is part of
 the cached remote and looks and behaves like any other file (reading
 included)
 .IP "3." 3
-After \f[C]cache-tmp-wait-time\f[R] passes and the file is next in line,
-\f[C]rclone move\f[R] is used to move the file to the cloud provider
+After \f[V]cache-tmp-wait-time\f[R] passes and the file is next in line,
+\f[V]rclone move\f[R] is used to move the file to the cloud provider
 .IP "4." 3
 Reading the file still works during the upload but most modifications on
 it will be prohibited
@@ -41095,8 +41145,8 @@ it will be prohibited
 Once the move is complete the file is unlocked for modifications as it
 becomes as any other regular file
 .IP "6." 3
-If the file is being read through \f[C]cache\f[R] when it\[aq]s actually
-deleted from the temporary path then \f[C]cache\f[R] will simply swap
+If the file is being read through \f[V]cache\f[R] when it\[aq]s actually
+deleted from the temporary path then \f[V]cache\f[R] will simply swap
 the source to the cloud provider without interrupting the reading (small
 blip can happen though)
 .PP
@@ -41104,16 +41154,16 @@ Files are uploaded in sequence and only one file is uploaded at a time.
 Uploads will be stored in a queue and be processed based on the order
 they were added.
 The queue and the temporary storage is persistent across restarts but
-can be cleared on startup with the \f[C]--cache-db-purge\f[R] flag.
+can be cleared on startup with the \f[V]--cache-db-purge\f[R] flag.
 .SS Write Support
 .PP
-Writes are supported through \f[C]cache\f[R].
+Writes are supported through \f[V]cache\f[R].
 One caveat is that a mounted cache remote does not add any retry or
 fallback mechanism to the upload operation.
 This will depend on the implementation of the wrapped remote.
-Consider using \f[C]Offline uploading\f[R] for reliable writes.
+Consider using \f[V]Offline uploading\f[R] for reliable writes.
 .PP
-One special case is covered with \f[C]cache-writes\f[R] which will cache
+One special case is covered with \f[V]cache-writes\f[R] which will cache
 the file data at the same time as the upload when it is enabled making
 it available from the cache store immediately once the upload is
 finished.
@@ -41142,56 +41192,56 @@ playback cache will deploy the configured number of workers.
 This integration opens the doorway to additional performance
 improvements which will be explored in the near future.
 .PP
-\f[B]Note:\f[R] If Plex options are not configured, \f[C]cache\f[R] will
+\f[B]Note:\f[R] If Plex options are not configured, \f[V]cache\f[R] will
 function with its configured options without adapting any of its
 settings.
 .PP
 How to enable?
-Run \f[C]rclone config\f[R] and add all the Plex options (endpoint,
+Run \f[V]rclone config\f[R] and add all the Plex options (endpoint,
 username and password) in your remote and it will be automatically
 enabled.
 .PP
-Affected settings: - \f[C]cache-workers\f[R]: \f[I]Configured value\f[R]
+Affected settings: - \f[V]cache-workers\f[R]: \f[I]Configured value\f[R]
 during confirmed playback or \f[I]1\f[R] all the other times
 .SS Certificate Validation
 .PP
 When the Plex server is configured to only accept secure connections, it
-is possible to use \f[C].plex.direct\f[R] URLs to ensure certificate
+is possible to use \f[V].plex.direct\f[R] URLs to ensure certificate
 validation succeeds.
 These URLs are used by Plex internally to connect to the Plex server
 securely.
 .PP
 The format for these URLs is the following:
 .PP
-\f[C]https://ip-with-dots-replaced.server-hash.plex.direct:32400/\f[R]
+\f[V]https://ip-with-dots-replaced.server-hash.plex.direct:32400/\f[R]
 .PP
-The \f[C]ip-with-dots-replaced\f[R] part can be any IPv4 address, where
+The \f[V]ip-with-dots-replaced\f[R] part can be any IPv4 address, where
 the dots have been replaced with dashes, e.g.
-\f[C]127.0.0.1\f[R] becomes \f[C]127-0-0-1\f[R].
+\f[V]127.0.0.1\f[R] becomes \f[V]127-0-0-1\f[R].
 .PP
-To get the \f[C]server-hash\f[R] part, the easiest way is to visit
+To get the \f[V]server-hash\f[R] part, the easiest way is to visit
 .PP
 https://plex.tv/api/resources?includeHttps=1&X-Plex-Token=your-plex-token
 .PP
 This page will list all the available Plex servers for your account with
-at least one \f[C].plex.direct\f[R] link for each.
+at least one \f[V].plex.direct\f[R] link for each.
 Copy one URL and replace the IP address with the desired address.
-This can be used as the \f[C]plex_url\f[R] value.
+This can be used as the \f[V]plex_url\f[R] value.
 .SS Known issues
 .SS Mount and --dir-cache-time
 .PP
 --dir-cache-time controls the first layer of directory caching which
 works at the mount layer.
-Being an independent caching mechanism from the \f[C]cache\f[R] backend,
+Being an independent caching mechanism from the \f[V]cache\f[R] backend,
 it will manage its own entries based on the configured time.
 .PP
 To avoid getting in a scenario where dir cache has obsolete data and
-cache would have the correct one, try to set \f[C]--dir-cache-time\f[R]
-to a lower time than \f[C]--cache-info-age\f[R].
+cache would have the correct one, try to set \f[V]--dir-cache-time\f[R]
+to a lower time than \f[V]--cache-info-age\f[R].
 Default values are already configured in this way.
 .SS Windows support - Experimental
 .PP
-There are a couple of issues with Windows \f[C]mount\f[R] functionality
+There are a couple of issues with Windows \f[V]mount\f[R] functionality
 that still require some investigations.
 It should be considered as experimental thus far as fixes come in for
 this OS.
@@ -41220,8 +41270,8 @@ lead to cloud provider throttles or bans due to repeated queries on it
 for very large mounts.
 .PP
 Some recommendations: - don\[aq]t use a very small interval for entry
-information (\f[C]--cache-info-age\f[R]) - while writes aren\[aq]t yet
-optimised, you can still write through \f[C]cache\f[R] which gives you
+information (\f[V]--cache-info-age\f[R]) - while writes aren\[aq]t yet
+optimised, you can still write through \f[V]cache\f[R] which gives you
 the advantage of adding the file in the cache at the same time if
 configured to do so.
 .PP
@@ -41233,8 +41283,8 @@ https://github.com/rclone/rclone/issues/1936
 .SS cache and crypt
 .PP
 One common scenario is to keep your data encrypted in the cloud provider
-using the \f[C]crypt\f[R] remote.
-\f[C]crypt\f[R] uses a similar technique to wrap around an existing
+using the \f[V]crypt\f[R] remote.
+\f[V]crypt\f[R] uses a similar technique to wrap around an existing
 remote and handles this translation in a seamless way.
 .PP
 There is an issue with wrapping the remotes in this order: \f[B]cloud
@@ -41249,25 +41299,25 @@ Organizing the remotes in this order yields better results: \f[B]cloud
 remote\f[R] -> \f[B]cache\f[R] -> \f[B]crypt\f[R]
 .SS absolute remote paths
 .PP
-\f[C]cache\f[R] can not differentiate between relative and absolute
+\f[V]cache\f[R] can not differentiate between relative and absolute
 paths for the wrapped remote.
-Any path given in the \f[C]remote\f[R] config setting and on the command
+Any path given in the \f[V]remote\f[R] config setting and on the command
 line will be passed to the wrapped remote as is, but for storing the
 chunks on disk the path will be made relative by removing any leading
-\f[C]/\f[R] character.
+\f[V]/\f[R] character.
 .PP
 This behavior is irrelevant for most backend types, but there are
-backends where a leading \f[C]/\f[R] changes the effective directory,
+backends where a leading \f[V]/\f[R] changes the effective directory,
 e.g.
-in the \f[C]sftp\f[R] backend paths starting with a \f[C]/\f[R] are
+in the \f[V]sftp\f[R] backend paths starting with a \f[V]/\f[R] are
 relative to the root of the SSH server and paths without are relative to
 the user home directory.
-As a result \f[C]sftp:bin\f[R] and \f[C]sftp:/bin\f[R] will share the
+As a result \f[V]sftp:bin\f[R] and \f[V]sftp:/bin\f[R] will share the
 same cache folder, even if they represent a different directory on the
 SSH server.
 .SS Cache and Remote Control (--rc)
 .PP
-Cache supports the new \f[C]--rc\f[R] mode in rclone and can be remote
+Cache supports the new \f[V]--rc\f[R] mode in rclone and can be remote
 controlled through the following end points: By default, the listener is
 disabled if you do not add the flag.
 .SS rc cache/expire
@@ -41776,7 +41826,7 @@ rclone backend stats remote: [options] [<arguments>+]
 .fi
 .SH Chunker
 .PP
-The \f[C]chunker\f[R] overlay transparently splits large files into
+The \f[V]chunker\f[R] overlay transparently splits large files into
 smaller chunks during upload to wrapped remote and transparently
 assembles them back when the file is downloaded.
 This allows to effectively overcome size limits imposed by storage
@@ -41788,16 +41838,16 @@ configuration instructions for that remote.
 You can also use a local pathname instead of a remote.
 .PP
 First check your chosen remote is working - we\[aq]ll call it
-\f[C]remote:path\f[R] here.
-Note that anything inside \f[C]remote:path\f[R] will be chunked and
+\f[V]remote:path\f[R] here.
+Note that anything inside \f[V]remote:path\f[R] will be chunked and
 anything outside won\[aq]t.
 This means that if you are using a bucket-based remote (e.g.
 S3, B2, swift) then you should probably put the bucket in the remote
-\f[C]s3:bucket\f[R].
+\f[V]s3:bucket\f[R].
 .PP
-Now configure \f[C]chunker\f[R] using \f[C]rclone config\f[R].
-We will call this one \f[C]overlay\f[R] to separate it from the
-\f[C]remote\f[R] itself.
+Now configure \f[V]chunker\f[R] using \f[V]rclone config\f[R].
+We will call this one \f[V]overlay\f[R] to separate it from the
+\f[V]remote\f[R] itself.
 .IP
 .nf
 \f[C]
@@ -41860,13 +41910,13 @@ y/e/d> y
 .fi
 .SS Specifying the remote
 .PP
-In normal use, make sure the remote has a \f[C]:\f[R] in.
-If you specify the remote without a \f[C]:\f[R] then rclone will use a
+In normal use, make sure the remote has a \f[V]:\f[R] in.
+If you specify the remote without a \f[V]:\f[R] then rclone will use a
 local directory of that name.
-So if you use a remote of \f[C]/path/to/secret/files\f[R] then rclone
+So if you use a remote of \f[V]/path/to/secret/files\f[R] then rclone
 will chunk stuff in that directory.
-If you use a remote of \f[C]name\f[R] then rclone will put files in a
-directory called \f[C]name\f[R] in the current directory.
+If you use a remote of \f[V]name\f[R] then rclone will put files in a
+directory called \f[V]name\f[R] in the current directory.
 .SS Chunking
 .PP
 When rclone starts a file upload, chunker checks the file size.
@@ -41893,7 +41943,7 @@ assembles it by concatenating data chunks in order.
 As the split is trivial one could even manually concatenate data chunks
 together to obtain the original content.
 .PP
-When the \f[C]list\f[R] rclone command scans a directory on wrapped
+When the \f[V]list\f[R] rclone command scans a directory on wrapped
 remote, the potential chunk files are accounted for, grouped and
 assembled into composite directory entries.
 Any temporary chunks are hidden.
@@ -41906,7 +41956,7 @@ with or damaged.
 If chunker detects a missing chunk it will by default print warning,
 skip the whole incomplete group of chunks but proceed with current
 command.
-You can set the \f[C]--chunker-fail-hard\f[R] flag to have commands
+You can set the \f[V]--chunker-fail-hard\f[R] flag to have commands
 abort with error message in such cases.
 .PP
 \f[B]Caveat\f[R]: As it is now, chunker will always create a temporary
@@ -41917,17 +41967,17 @@ throughput when handling transfers primarily composed of small files on
 some backends (e.g.
 Box).
 A workaround to this issue is to use chunker only for files above the
-chunk threshold via \f[C]--min-size\f[R] and then perform a separate
+chunk threshold via \f[V]--min-size\f[R] and then perform a separate
 call without chunker on the remaining files.
 .SS Chunk names
 .PP
-The default chunk name format is \f[C]*.rclone_chunk.###\f[R], hence by
-default chunk names are \f[C]BIG_FILE_NAME.rclone_chunk.001\f[R],
-\f[C]BIG_FILE_NAME.rclone_chunk.002\f[R] etc.
-You can configure another name format using the \f[C]name_format\f[R]
+The default chunk name format is \f[V]*.rclone_chunk.###\f[R], hence by
+default chunk names are \f[V]BIG_FILE_NAME.rclone_chunk.001\f[R],
+\f[V]BIG_FILE_NAME.rclone_chunk.002\f[R] etc.
+You can configure another name format using the \f[V]name_format\f[R]
 configuration file option.
-The format uses asterisk \f[C]*\f[R] as a placeholder for the base file
-name and one or more consecutive hash characters \f[C]#\f[R] as a
+The format uses asterisk \f[V]*\f[R] as a placeholder for the base file
+name and one or more consecutive hash characters \f[V]#\f[R] as a
 placeholder for sequential chunk number.
 There must be one and only one asterisk.
 The number of consecutive hash characters defines the minimum length of
@@ -41939,25 +41989,25 @@ By default numbering starts from 1 but there is another option that
 allows user to start from 0, e.g.
 for compatibility with legacy software.
 .PP
-For example, if name format is \f[C]big_*-##.part\f[R] and original file
-name is \f[C]data.txt\f[R] and numbering starts from 0, then the first
-chunk will be named \f[C]big_data.txt-00.part\f[R], the 99th chunk will
-be \f[C]big_data.txt-98.part\f[R] and the 302nd chunk will become
-\f[C]big_data.txt-301.part\f[R].
+For example, if name format is \f[V]big_*-##.part\f[R] and original file
+name is \f[V]data.txt\f[R] and numbering starts from 0, then the first
+chunk will be named \f[V]big_data.txt-00.part\f[R], the 99th chunk will
+be \f[V]big_data.txt-98.part\f[R] and the 302nd chunk will become
+\f[V]big_data.txt-301.part\f[R].
 .PP
-Note that \f[C]list\f[R] assembles composite directory entries only when
+Note that \f[V]list\f[R] assembles composite directory entries only when
 chunk names match the configured format and treats non-conforming file
 names as normal non-chunked files.
 .PP
-When using \f[C]norename\f[R] transactions, chunk names will
+When using \f[V]norename\f[R] transactions, chunk names will
 additionally have a unique file version suffix.
-For example, \f[C]BIG_FILE_NAME.rclone_chunk.001_bp562k\f[R].
+For example, \f[V]BIG_FILE_NAME.rclone_chunk.001_bp562k\f[R].
 .SS Metadata
 .PP
 Besides data chunks chunker will by default create metadata object for a
 composite file.
 The object is named after the original file.
-Chunker allows user to disable metadata completely (the \f[C]none\f[R]
+Chunker allows user to disable metadata completely (the \f[V]none\f[R]
 format).
 Note that metadata is normally not created for files smaller than the
 configured chunk size.
@@ -41968,17 +42018,17 @@ This is the default format.
 It supports hash sums and chunk validation for composite files.
 Meta objects carry the following fields:
 .IP \[bu] 2
-\f[C]ver\f[R] - version of format, currently \f[C]1\f[R]
+\f[V]ver\f[R] - version of format, currently \f[V]1\f[R]
 .IP \[bu] 2
-\f[C]size\f[R] - total size of composite file
+\f[V]size\f[R] - total size of composite file
 .IP \[bu] 2
-\f[C]nchunks\f[R] - number of data chunks in file
+\f[V]nchunks\f[R] - number of data chunks in file
 .IP \[bu] 2
-\f[C]md5\f[R] - MD5 hashsum of composite file (if present)
+\f[V]md5\f[R] - MD5 hashsum of composite file (if present)
 .IP \[bu] 2
-\f[C]sha1\f[R] - SHA1 hashsum (if present)
+\f[V]sha1\f[R] - SHA1 hashsum (if present)
 .IP \[bu] 2
-\f[C]txn\f[R] - identifies current version of the file
+\f[V]txn\f[R] - identifies current version of the file
 .PP
 There is no field for composite file name as it\[aq]s simply equal to
 the name of meta object on the wrapped remote.
@@ -41987,7 +42037,7 @@ time handling.
 .SS No metadata
 .PP
 You can disable meta objects by setting the meta format option to
-\f[C]none\f[R].
+\f[V]none\f[R].
 In this mode chunker will scan directory for all files that follow
 configured chunk name format, group them by detecting chunks with the
 same base name and show group names as virtual composite files.
@@ -41996,8 +42046,8 @@ last chunk) than format with metadata enabled.
 .SS Hashsums
 .PP
 Chunker supports hashsums only when a compatible metadata is present.
-Hence, if you choose metadata format of \f[C]none\f[R], chunker will
-report hashsum as \f[C]UNSUPPORTED\f[R].
+Hence, if you choose metadata format of \f[V]none\f[R], chunker will
+report hashsum as \f[V]UNSUPPORTED\f[R].
 .PP
 Please note that by default metadata is stored only for composite files.
 If a file is smaller than configured chunk size, chunker will
@@ -42015,8 +42065,8 @@ same hash type as supported by wrapped remote so that your file listings
 look coherent.
 .PP
 If your storage backend does not support MD5 or SHA1 but you need
-consistent file hashing, configure chunker with \f[C]md5all\f[R] or
-\f[C]sha1all\f[R].
+consistent file hashing, configure chunker with \f[V]md5all\f[R] or
+\f[V]sha1all\f[R].
 These two modes guarantee given hash for all files.
 If wrapped remote doesn\[aq]t support it, chunker will then add metadata
 to all files, even small.
@@ -42024,8 +42074,8 @@ However, this can double the amount of small files in storage and incur
 additional service charges.
 You can even use chunker to force md5/sha1 support in any other remote
 at expense of sidecar meta objects by setting e.g.
-\f[C]hash_type=sha1all\f[R] to force hashsums and
-\f[C]chunk_size=1P\f[R] to effectively disable chunking.
+\f[V]hash_type=sha1all\f[R] to force hashsums and
+\f[V]chunk_size=1P\f[R] to effectively disable chunking.
 .PP
 Normally, when a file is copied to chunker controlled remote, chunker
 will ask the file source for compatible file hash and revert to
@@ -42036,12 +42086,12 @@ Also, chunker will reject a server-side copy or move operation if source
 and destination hashsum types are different resulting in the extra
 network bandwidth, too.
 In some rare cases this may be undesired, so chunker provides two
-optional choices: \f[C]sha1quick\f[R] and \f[C]md5quick\f[R].
+optional choices: \f[V]sha1quick\f[R] and \f[V]md5quick\f[R].
 If the source does not support primary hash type and the quick mode is
 enabled, chunker will try to fall back to the secondary type.
 This will save CPU and bandwidth but can result in empty hashsums at
 destination.
-Beware of consequences: the \f[C]sync\f[R] command will revert
+Beware of consequences: the \f[V]sync\f[R] command will revert
 (sometimes silently) to time/size comparison if compatible hashsums
 between source and target are not found.
 .SS Modification times
@@ -42052,7 +42102,7 @@ For a small non-chunked file the chunker overlay simply manipulates
 modification time of the wrapped remote file.
 For a composite file with metadata chunker will get and set modification
 time of the metadata object on the wrapped remote.
-If file is chunked but metadata format is \f[C]none\f[R] then chunker
+If file is chunked but metadata format is \f[V]none\f[R] then chunker
 will use modification time of the first data chunk.
 .SS Migrations
 .PP
@@ -42066,7 +42116,7 @@ Create another directory (most probably on the same cloud storage) and
 configure a new remote with desired metadata format, hash type, chunk
 naming etc.
 .IP \[bu] 2
-Now run \f[C]rclone sync --interactive oldchunks: newchunks:\f[R] and
+Now run \f[V]rclone sync --interactive oldchunks: newchunks:\f[R] and
 all your data will be transparently converted in transfer.
 This may take some time, yet chunker will try server-side copy if
 possible.
@@ -42076,26 +42126,26 @@ the old remote.
 .PP
 If rclone gets killed during a long operation on a big composite file,
 hidden temporary chunks may stay in the directory.
-They will not be shown by the \f[C]list\f[R] command but will eat up
+They will not be shown by the \f[V]list\f[R] command but will eat up
 your account quota.
-Please note that the \f[C]deletefile\f[R] command deletes only active
+Please note that the \f[V]deletefile\f[R] command deletes only active
 chunks of a file.
 As a workaround, you can use remote of the wrapped file system to see
 them.
 An easy way to get rid of hidden garbage is to copy littered directory
 somewhere using the chunker remote and purge the original directory.
-The \f[C]copy\f[R] command will copy only active chunks while the
-\f[C]purge\f[R] will remove everything including garbage.
+The \f[V]copy\f[R] command will copy only active chunks while the
+\f[V]purge\f[R] will remove everything including garbage.
 .SS Caveats and Limitations
 .PP
-Chunker requires wrapped remote to support server-side \f[C]move\f[R]
-(or \f[C]copy\f[R] + \f[C]delete\f[R]) operations, otherwise it will
+Chunker requires wrapped remote to support server-side \f[V]move\f[R]
+(or \f[V]copy\f[R] + \f[V]delete\f[R]) operations, otherwise it will
 explicitly refuse to start.
 This is because it internally renames temporary chunk files to their
 final names when an operation completes successfully.
 .PP
 Chunker encodes chunk number in file name, so with default
-\f[C]name_format\f[R] setting it adds 17 characters.
+\f[V]name_format\f[R] setting it adds 17 characters.
 Also chunker adds 7 characters of temporary suffix during operations.
 Many file systems limit base file name without path by 255 characters.
 Using rclone\[aq]s crypt remote as a base file system limits file name
@@ -42103,14 +42153,14 @@ by 143 characters.
 Thus, maximum name length is 231 for most files and 119 for
 chunker-over-crypt.
 A user in need can change name format to e.g.
-\f[C]*.rcc##\f[R] and save 10 characters (provided at most 99 chunks per
+\f[V]*.rcc##\f[R] and save 10 characters (provided at most 99 chunks per
 file).
 .PP
 Note that a move implemented using the copy-and-delete method may incur
 double charging with some cloud storage providers.
 .PP
 Chunker will not automatically rename existing chunks when you run
-\f[C]rclone config\f[R] on a live remote and change the chunk name
+\f[V]rclone config\f[R] on a live remote and change the chunk name
 format.
 Beware that in result of this some files which have been treated as
 chunks before the change can pop up in directory listings as normal
@@ -42123,11 +42173,11 @@ If wrapped remote is case insensitive, the chunker overlay will inherit
 that property (so you can\[aq]t have a file called \[dq]Hello.doc\[dq]
 and \[dq]hello.doc\[dq] in the same directory).
 .PP
-Chunker included in rclone releases up to \f[C]v1.54\f[R] can sometimes
+Chunker included in rclone releases up to \f[V]v1.54\f[R] can sometimes
 fail to detect metadata produced by recent versions of rclone.
 We recommend users to keep rclone up-to-date to avoid data corruption.
 .PP
-Changing \f[C]transactions\f[R] is dangerous and requires explicit
+Changing \f[V]transactions\f[R] is dangerous and requires explicit
 migration.
 .SS Standard options
 .PP
@@ -42410,9 +42460,9 @@ transfer service aimed as business.
 .PP
 The initial setup for Citrix ShareFile involves getting a token from
 Citrix ShareFile which you can in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -42492,10 +42542,10 @@ Note that rclone runs a webserver on your local machine to collect the
 token as returned from Citrix ShareFile.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this it may require you
 to unblock it temporarily if you are running a host firewall.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your ShareFile
 .IP
@@ -42522,7 +42572,7 @@ rclone copy /home/source remote:backup
 .fi
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Modification times and hashes
 .PP
 ShareFile allows modification times to be set on objects accurate to 1
@@ -42530,14 +42580,14 @@ second.
 These will be used to detect whether objects need syncing or not.
 .PP
 ShareFile supports MD5 type hashes, so you can use the
-\f[C]--checksum\f[R] flag.
+\f[V]--checksum\f[R] flag.
 .SS Transfers
 .PP
 For files above 128 MiB rclone will use a chunked transfer.
-Rclone will upload up to \f[C]--transfers\f[R] chunks at the same time
+Rclone will upload up to \f[V]--transfers\f[R] chunks at the same time
 (shared among all the multipart uploads).
 Chunks are buffered in memory and are normally 64 MiB so increasing
-\f[C]--transfers\f[R] will increase memory use.
+\f[V]--transfers\f[R] will increase memory use.
 .SS Restricted filename characters
 .PP
 In addition to the default restricted characters
@@ -42560,56 +42610,56 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 *
 T}@T{
 0x2A
 T}@T{
-\[uFF0A]
+＊
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 ?
 T}@T{
 0x3F
 T}@T{
-\[uFF1F]
+？
 T}
 T{
 :
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 T{
 |
 T}@T{
 0x7C
 T}@T{
-\[uFF5C]
+｜
 T}
 T{
 \[dq]
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 .TE
 .PP
@@ -42633,14 +42683,14 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 T{
 \&.
 T}@T{
 0x2E
 T}@T{
-\[uFF0E]
+．
 T}
 .TE
 .PP
@@ -42864,9 +42914,9 @@ called \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .PP
 ShareFile only supports filenames up to 256 characters in length.
 .PP
-\f[C]rclone about\f[R] is not supported by the Citrix ShareFile backend.
+\f[V]rclone about\f[R] is not supported by the Citrix ShareFile backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -42874,9 +42924,9 @@ about (https://rclone.org/overview/#optional-features) and rclone
 about (https://rclone.org/commands/rclone_about/)
 .SH Crypt
 .PP
-Rclone \f[C]crypt\f[R] remotes encrypt and decrypt other remotes.
+Rclone \f[V]crypt\f[R] remotes encrypt and decrypt other remotes.
 .PP
-A remote of type \f[C]crypt\f[R] does not access a storage
+A remote of type \f[V]crypt\f[R] does not access a storage
 system (https://rclone.org/overview/) directly, but instead wraps
 another remote, which in turn accesses the storage system.
 This is similar to how alias (https://rclone.org/alias/),
@@ -42892,7 +42942,7 @@ crypt remote.
 Accessing a storage system through a crypt remote realizes client-side
 encryption, which makes it safe to keep your data in a location you do
 not trust will not get compromised.
-When working against the \f[C]crypt\f[R] remote, rclone will
+When working against the \f[V]crypt\f[R] remote, rclone will
 automatically encrypt (before uploading) and decrypt (after downloading)
 on your local system as needed on the fly, leaving the data encrypted at
 rest in the wrapped remote.
@@ -42942,29 +42992,29 @@ Names (file- and directory names) are also encrypted by default, but
 this has some implications and is therefore possible to be turned off.
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]secret\f[R].
+Here is an example of how to make a remote called \f[V]secret\f[R].
 .PP
-To use \f[C]crypt\f[R], first set up the underlying remote.
-Follow the \f[C]rclone config\f[R] instructions for the specific
+To use \f[V]crypt\f[R], first set up the underlying remote.
+Follow the \f[V]rclone config\f[R] instructions for the specific
 backend.
 .PP
 Before configuring the crypt remote, check the underlying remote is
 working.
-In this example the underlying remote is called \f[C]remote\f[R].
-We will configure a path \f[C]path\f[R] within this remote to contain
+In this example the underlying remote is called \f[V]remote\f[R].
+We will configure a path \f[V]path\f[R] within this remote to contain
 the encrypted content.
-Anything inside \f[C]remote:path\f[R] will be encrypted and anything
+Anything inside \f[V]remote:path\f[R] will be encrypted and anything
 outside will not.
 .PP
-Configure \f[C]crypt\f[R] using \f[C]rclone config\f[R].
-In this example the \f[C]crypt\f[R] remote is called \f[C]secret\f[R],
-to differentiate it from the underlying \f[C]remote\f[R].
+Configure \f[V]crypt\f[R] using \f[V]rclone config\f[R].
+In this example the \f[V]crypt\f[R] remote is called \f[V]secret\f[R],
+to differentiate it from the underlying \f[V]remote\f[R].
 .PP
-When you are done you can use the crypt remote named \f[C]secret\f[R]
+When you are done you can use the crypt remote named \f[V]secret\f[R]
 just as you would with any other remote, e.g.
-\f[C]rclone copy D:\[rs]docs secret:\[rs]docs\f[R], and rclone will
+\f[V]rclone copy D:\[rs]docs secret:\[rs]docs\f[R], and rclone will
 encrypt and decrypt as needed on the fly.
-If you access the wrapped remote \f[C]remote:path\f[R] directly you will
+If you access the wrapped remote \f[V]remote:path\f[R] directly you will
 bypass the encryption, and anything you read will be in encrypted form,
 and anything you write will be unencrypted.
 To avoid issues it is best to configure a dedicated path for encrypted
@@ -43060,14 +43110,14 @@ y/e/d>
 \f[R]
 .fi
 .PP
-\f[B]Important\f[R] The crypt password stored in \f[C]rclone.conf\f[R]
+\f[B]Important\f[R] The crypt password stored in \f[V]rclone.conf\f[R]
 is lightly obscured.
 That only protects it from cursory inspection.
 It is not secure unless configuration
 encryption (https://rclone.org/docs/#configuration-encryption) of
-\f[C]rclone.conf\f[R] is specified.
+\f[V]rclone.conf\f[R] is specified.
 .PP
-A long passphrase is recommended, or \f[C]rclone config\f[R] can
+A long passphrase is recommended, or \f[V]rclone config\f[R] can
 generate a random one.
 .PP
 The obscured password is created using AES-CTR with a static key.
@@ -43091,27 +43141,27 @@ string that rclone accepts as a source/destination of other commands.
 .PP
 The primary use case is to specify the path into an already configured
 remote (e.g.
-\f[C]remote:path/to/dir\f[R] or \f[C]remote:bucket\f[R]), such that data
+\f[V]remote:path/to/dir\f[R] or \f[V]remote:bucket\f[R]), such that data
 in a remote untrusted location can be stored encrypted.
 .PP
 You may also specify a local filesystem path, such as
-\f[C]/path/to/dir\f[R] on Linux, \f[C]C:\[rs]path\[rs]to\[rs]dir\f[R] on
+\f[V]/path/to/dir\f[R] on Linux, \f[V]C:\[rs]path\[rs]to\[rs]dir\f[R] on
 Windows.
 By creating a crypt remote pointing to such a local filesystem path, you
 can use rclone as a utility for pure local file encryption, for example
 to keep encrypted files on a removable USB drive.
 .PP
-\f[B]Note\f[R]: A string which do not contain a \f[C]:\f[R] will by
+\f[B]Note\f[R]: A string which do not contain a \f[V]:\f[R] will by
 rclone be treated as a relative path in the local filesystem.
-For example, if you enter the name \f[C]remote\f[R] without the trailing
-\f[C]:\f[R], it will be treated as a subdirectory of the current
+For example, if you enter the name \f[V]remote\f[R] without the trailing
+\f[V]:\f[R], it will be treated as a subdirectory of the current
 directory with name \[dq]remote\[dq].
 .PP
-If a path \f[C]remote:path/to/dir\f[R] is specified, rclone stores
-encrypted files in \f[C]path/to/dir\f[R] on the remote.
+If a path \f[V]remote:path/to/dir\f[R] is specified, rclone stores
+encrypted files in \f[V]path/to/dir\f[R] on the remote.
 With file name encryption, files saved to
-\f[C]secret:subdir/subfile\f[R] are stored in the unencrypted path
-\f[C]path/to/dir\f[R] but the \f[C]subdir/subpath\f[R] element is
+\f[V]secret:subdir/subfile\f[R] are stored in the unencrypted path
+\f[V]path/to/dir\f[R] but the \f[V]subdir/subpath\f[R] element is
 encrypted.
 .PP
 The path you specify does not have to exist, rclone will create it when
@@ -43123,8 +43173,8 @@ content, it is recommended to point the crypt remote to a separate
 directory within the wrapped remote.
 If you use a bucket-based storage system (e.g.
 Swift, S3, Google Compute Storage, B2) it is generally advisable to wrap
-the crypt remote around a specific bucket (\f[C]s3:bucket\f[R]).
-If wrapping around the entire root of the storage (\f[C]s3:\f[R]), and
+the crypt remote around a specific bucket (\f[V]s3:bucket\f[R]).
+If wrapping around the entire root of the storage (\f[V]s3:\f[R]), and
 use the optional file name encryption, rclone will encrypt the bucket
 name.
 .SS Changing password
@@ -43177,13 +43227,13 @@ encryption.
 .nf
 \f[C]
 plaintext/
-\[u251C]\[u2500]\[u2500] file0.txt
-\[u251C]\[u2500]\[u2500] file1.txt
-\[u2514]\[u2500]\[u2500] subdir
-    \[u251C]\[u2500]\[u2500] file2.txt
-    \[u251C]\[u2500]\[u2500] file3.txt
-    \[u2514]\[u2500]\[u2500] subsubdir
-        \[u2514]\[u2500]\[u2500] file4.txt
+├── file0.txt
+├── file1.txt
+└── subdir
+    ├── file2.txt
+    ├── file3.txt
+    └── subsubdir
+        └── file4.txt
 \f[R]
 .fi
 .PP
@@ -43225,7 +43275,7 @@ $ rclone -q ls secret:subdir
 \f[R]
 .fi
 .PP
-Without file name encryption \f[C].bin\f[R] extensions are added to
+Without file name encryption \f[V].bin\f[R] extensions are added to
 underlying names.
 This prevents the cloud provider attempting to interpret file content.
 .IP
@@ -43297,13 +43347,13 @@ file name encryption.
 Where file names are 143 or fewer characters in length issues should not
 be encountered, irrespective of cloud storage provider.
 .PP
-An experimental advanced option \f[C]filename_encoding\f[R] is now
+An experimental advanced option \f[V]filename_encoding\f[R] is now
 provided to address this problem to a certain degree.
 For cloud storage systems with case sensitive file names (e.g.
-Google Drive), \f[C]base64\f[R] can be used to reduce file name length.
+Google Drive), \f[V]base64\f[R] can be used to reduce file name length.
 For cloud storage systems using UTF-16 to store file names internally
 (e.g.
-OneDrive, Dropbox, Box), \f[C]base32768\f[R] can be used to drastically
+OneDrive, Dropbox, Box), \f[V]base32768\f[R] can be used to drastically
 reduce file name length.
 .PP
 An alternative, future rclone file name encryption mode may tolerate
@@ -43316,14 +43366,14 @@ There are two options:
 True
 .PP
 Encrypts the whole file path including directory names Example:
-\f[C]1/12/123.txt\f[R] is encrypted to
-\f[C]p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0\f[R]
+\f[V]1/12/123.txt\f[R] is encrypted to
+\f[V]p0e52nreeaj0a5ea7s64m4j72s/l42g6771hnv3an9cgc8cr2n1ng/qgm4avr35m5loi1th53ato71v0\f[R]
 .PP
 False
 .PP
 Only encrypts file names, skips directory names Example:
-\f[C]1/12/123.txt\f[R] is encrypted to
-\f[C]1/12/qgm4avr35m5loi1th53ato71v0\f[R]
+\f[V]1/12/123.txt\f[R] is encrypted to
+\f[V]1/12/qgm4avr35m5loi1th53ato71v0\f[R]
 .SS Modification times and hashes
 .PP
 Crypt stores modification times using the underlying remote so support
@@ -43333,8 +43383,8 @@ Hashes are not stored for crypt.
 However the data integrity is protected by an extremely strong crypto
 authenticator.
 .PP
-Use the \f[C]rclone cryptcheck\f[R] command to check the integrity of an
-encrypted remote instead of \f[C]rclone check\f[R] which can\[aq]t check
+Use the \f[V]rclone cryptcheck\f[R] command to check the integrity of an
+encrypted remote instead of \f[V]rclone check\f[R] which can\[aq]t check
 the checksums properly.
 .SS Standard options
 .PP
@@ -43564,10 +43614,10 @@ Default: false
 If set, this will raise an error when crypt comes across a filename that
 can\[aq]t be decrypted.
 .PP
-(By default, rclone will just log a NOTICE and continue as normal.) This
-can happen if encrypted and unencrypted files are stored in the same
-directory (which is not recommended.) It may also indicate a more
-serious problem that should be investigated.
+(By default, rclone will just log a NOTICE and continue as normal.)
+This can happen if encrypted and unencrypted files are stored in the
+same directory (which is not recommended.)
+It may also indicate a more serious problem that should be investigated.
 .PP
 Properties:
 .IP \[bu] 2
@@ -43723,23 +43773,23 @@ rclone rc backend/command command=decode fs=crypt: encryptedfile1 [encryptedfile
 .SS Backing up an encrypted remote
 .PP
 If you wish to backup an encrypted remote, it is recommended that you
-use \f[C]rclone sync\f[R] on the encrypted files, and make sure the
+use \f[V]rclone sync\f[R] on the encrypted files, and make sure the
 passwords are the same in the new encrypted remote.
 .PP
 This will have the following advantages
 .IP \[bu] 2
-\f[C]rclone sync\f[R] will check the checksums while copying
+\f[V]rclone sync\f[R] will check the checksums while copying
 .IP \[bu] 2
-you can use \f[C]rclone check\f[R] between the encrypted remotes
+you can use \f[V]rclone check\f[R] between the encrypted remotes
 .IP \[bu] 2
 you don\[aq]t decrypt and encrypt unnecessarily
 .PP
 For example, let\[aq]s say you have your original remote at
-\f[C]remote:\f[R] with the encrypted version at \f[C]eremote:\f[R] with
-path \f[C]remote:crypt\f[R].
-You would then set up the new remote \f[C]remote2:\f[R] and then the
-encrypted version \f[C]eremote2:\f[R] with path \f[C]remote2:crypt\f[R]
-using the same passwords as \f[C]eremote:\f[R].
+\f[V]remote:\f[R] with the encrypted version at \f[V]eremote:\f[R] with
+path \f[V]remote:crypt\f[R].
+You would then set up the new remote \f[V]remote2:\f[R] and then the
+encrypted version \f[V]eremote2:\f[R] with path \f[V]remote2:crypt\f[R]
+using the same passwords as \f[V]eremote:\f[R].
 .PP
 To sync the two remotes you would do
 .IP
@@ -43763,7 +43813,7 @@ Files are encrypted 1:1 source file to destination object.
 The file has a header and is divided into chunks.
 .SS Header
 .IP \[bu] 2
-8 bytes magic string \f[C]RCLONE\[rs]x00\[rs]x00\f[R]
+8 bytes magic string \f[V]RCLONE\[rs]x00\[rs]x00\f[R]
 .IP \[bu] 2
 24 bytes Nonce (IV)
 .PP
@@ -43772,9 +43822,8 @@ random number generator.
 The nonce is incremented for each chunk read making sure each nonce is
 unique for each block written.
 The chance of a nonce being reused is minuscule.
-If you wrote an exabyte of data (10\[S1]\[u2078] bytes) you would have a
-probability of approximately 2\[tmu]10\[u207B]\[S3]\[S2] of re-using a
-nonce.
+If you wrote an exabyte of data (10¹⁸ bytes) you would have a
+probability of approximately 2×10⁻³² of re-using a nonce.
 .SS Chunk
 .PP
 Each chunk will contain 64 KiB of data, except for the last one which
@@ -43817,7 +43866,7 @@ This is the overhead for big files.
 .SS Name encryption
 .PP
 File names are encrypted segment by segment - the path is broken up into
-\f[C]/\f[R] separated strings and these are encrypted individually.
+\f[V]/\f[R] separated strings and these are encrypted individually.
 .PP
 File segments are padded using PKCS#7 to a multiple of 16 bytes before
 encryption.
@@ -43840,24 +43889,24 @@ This uses a 32 byte key (256 bits) and a 16 byte (128 bits) IV both of
 which are derived from the user password.
 .PP
 After encryption they are written out using a modified version of
-standard \f[C]base32\f[R] encoding as described in RFC4648.
+standard \f[V]base32\f[R] encoding as described in RFC4648.
 The standard encoding is modified in two ways:
 .IP \[bu] 2
 it becomes lower case (no-one likes upper case filenames!)
 .IP \[bu] 2
-we strip the padding character \f[C]=\f[R]
+we strip the padding character \f[V]=\f[R]
 .PP
-\f[C]base32\f[R] is used rather than the more efficient \f[C]base64\f[R]
+\f[V]base32\f[R] is used rather than the more efficient \f[V]base64\f[R]
 so rclone can be used on case insensitive remotes (e.g.
 Windows, Box, Dropbox, Onedrive etc).
 .SS Key derivation
 .PP
-Rclone uses \f[C]scrypt\f[R] with parameters \f[C]N=16384, r=8, p=1\f[R]
+Rclone uses \f[V]scrypt\f[R] with parameters \f[V]N=16384, r=8, p=1\f[R]
 with an optional user supplied salt (password2) to derive the 32+32+16 =
 80 bytes of key material required.
 If the user doesn\[aq]t supply a salt then rclone uses an internal one.
 .PP
-\f[C]scrypt\f[R] makes it impractical to mount a dictionary attack on
+\f[V]scrypt\f[R] makes it impractical to mount a dictionary attack on
 rclone encrypted data.
 For full protection against this you should always use a salt.
 .SS SEE ALSO
@@ -43873,7 +43922,7 @@ Anything you do with this remote is at your own risk.
 Please understand the risks associated with using experimental code and
 don\[aq]t use this remote in critical applications.
 .PP
-The \f[C]Compress\f[R] remote adds compression to another remote.
+The \f[V]Compress\f[R] remote adds compression to another remote.
 It is best used with remotes containing many large compressible files.
 .SS Configuration
 .PP
@@ -43951,8 +44000,8 @@ While you may download and decompress these files at will, do
 Files without correct metadata files will not be recognized by rclone.
 .SS File names
 .PP
-The compressed files will be named \f[C]*.###########.gz\f[R] where
-\f[C]*\f[R] is the base file and the \f[C]#\f[R] part is base64 encoded
+The compressed files will be named \f[V]*.###########.gz\f[R] where
+\f[V]*\f[R] is the base file and the \f[V]#\f[R] part is base64 encoded
 size of the uncompressed file.
 The file names should not be changed by anything other than the rclone
 compression backend.
@@ -44057,7 +44106,7 @@ Any metadata supported by the underlying remote is read and written.
 See the metadata (https://rclone.org/docs/#metadata) docs for more info.
 .SH Combine
 .PP
-The \f[C]combine\f[R] backend joins remotes together into a single
+The \f[V]combine\f[R] backend joins remotes together into a single
 directory tree.
 .PP
 For example you might have a remote for images on one provider:
@@ -44066,8 +44115,8 @@ For example you might have a remote for images on one provider:
 \f[C]
 $ rclone tree s3:imagesbucket
 /
-\[u251C]\[u2500]\[u2500] image1.jpg
-\[u2514]\[u2500]\[u2500] image2.jpg
+├── image1.jpg
+└── image2.jpg
 \f[R]
 .fi
 .PP
@@ -44077,28 +44126,28 @@ And a remote for files on another:
 \f[C]
 $ rclone tree drive:important/files
 /
-\[u251C]\[u2500]\[u2500] file1.txt
-\[u2514]\[u2500]\[u2500] file2.txt
+├── file1.txt
+└── file2.txt
 \f[R]
 .fi
 .PP
-The \f[C]combine\f[R] backend can join these together into a synthetic
+The \f[V]combine\f[R] backend can join these together into a synthetic
 directory structure like this:
 .IP
 .nf
 \f[C]
 $ rclone tree combined:
 /
-\[u251C]\[u2500]\[u2500] files
-\[br]   \[u251C]\[u2500]\[u2500] file1.txt
-\[br]   \[u2514]\[u2500]\[u2500] file2.txt
-\[u2514]\[u2500]\[u2500] images
-    \[u251C]\[u2500]\[u2500] image1.jpg
-    \[u2514]\[u2500]\[u2500] image2.jpg
+├── files
+│   ├── file1.txt
+│   └── file2.txt
+└── images
+    ├── image1.jpg
+    └── image2.jpg
 \f[R]
 .fi
 .PP
-You\[aq]d do this by specifying an \f[C]upstreams\f[R] parameter in the
+You\[aq]d do this by specifying an \f[V]upstreams\f[R] parameter in the
 config like this
 .IP
 .nf
@@ -44107,12 +44156,12 @@ upstreams = images=s3:imagesbucket files=drive:important/files
 \f[R]
 .fi
 .PP
-During the initial setup with \f[C]rclone config\f[R] you will specify
+During the initial setup with \f[V]rclone config\f[R] you will specify
 the upstreams remotes as a space separated list.
 The upstream remotes can either be a local paths or other remotes.
 .SS Configuration
 .PP
-Here is an example of how to make a combine called \f[C]remote\f[R] for
+Here is an example of how to make a combine called \f[V]remote\f[R] for
 the example above.
 First run:
 .IP
@@ -44167,7 +44216,7 @@ Rclone has a convenience feature for making a combine backend for all
 the shared drives you have access to.
 .PP
 Assuming your main (non shared drive) Google drive remote is called
-\f[C]drive:\f[R] you would run
+\f[V]drive:\f[R] you would run
 .IP
 .nf
 \f[C]
@@ -44194,8 +44243,8 @@ upstreams = \[dq]My Drive=My Drive:\[dq] \[dq]Test Drive=Test Drive:\[dq]
 .fi
 .PP
 If you then add that config to your config file (find it with
-\f[C]rclone config file\f[R]) then you can access all the shared drives
-in one place with the \f[C]AllDrives:\f[R] remote.
+\f[V]rclone config file\f[R]) then you can access all the shared drives
+in one place with the \f[V]AllDrives:\f[R] remote.
 .PP
 See the Google Drive docs (https://rclone.org/drive/#drives) for full
 info.
@@ -44259,17 +44308,17 @@ Any metadata supported by the underlying remote is read and written.
 See the metadata (https://rclone.org/docs/#metadata) docs for more info.
 .SH Dropbox
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Dropbox paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 The initial setup for dropbox involves getting a token from Dropbox
 which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -44323,7 +44372,7 @@ Note that rclone runs a webserver on your local machine to collect the
 token as returned from Dropbox.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and it may require you to
+This is on \f[V]http://127.0.0.1:53682/\f[R] and it may require you to
 unblock it temporarily if you are running a host firewall, or use manual
 mode.
 .PP
@@ -44356,17 +44405,17 @@ rclone copy /home/source remote:backup
 .PP
 Rclone supports Dropbox for business and Team Folders.
 .PP
-When using Dropbox for business \f[C]remote:\f[R] and
-\f[C]remote:path/to/file\f[R] will refer to your personal folder.
+When using Dropbox for business \f[V]remote:\f[R] and
+\f[V]remote:path/to/file\f[R] will refer to your personal folder.
 .PP
-If you wish to see Team Folders you must use a leading \f[C]/\f[R] in
-the path, so \f[C]rclone lsd remote:/\f[R] will refer to the root and
+If you wish to see Team Folders you must use a leading \f[V]/\f[R] in
+the path, so \f[V]rclone lsd remote:/\f[R] will refer to the root and
 show you all Team Folders and your User Folder.
 .PP
-You can then use team folders like this \f[C]remote:/TeamFolder\f[R] and
-\f[C]remote:/TeamFolder/path/to/file\f[R].
+You can then use team folders like this \f[V]remote:/TeamFolder\f[R] and
+\f[V]remote:/TeamFolder/path/to/file\f[R].
 .PP
-A leading \f[C]/\f[R] for a Dropbox personal account will do nothing,
+A leading \f[V]/\f[R] for a Dropbox personal account will do nothing,
 but it will take an extra HTTP transaction so it should be avoided.
 .SS Modification times and hashes
 .PP
@@ -44376,8 +44425,8 @@ time is to re-upload the file.
 This means that if you uploaded your data with an older version of
 rclone which didn\[aq]t support the v2 API and modified times, rclone
 will decide to upload all your old data to fix the modification times.
-If you don\[aq]t want this to happen use \f[C]--size-only\f[R] or
-\f[C]--checksum\f[R] flag to stop it.
+If you don\[aq]t want this to happen use \f[V]--size-only\f[R] or
+\f[V]--checksum\f[R] flag to stop it.
 .PP
 Dropbox supports its own hash
 type (https://www.dropbox.com/developers/reference/content-hash) which
@@ -44400,28 +44449,28 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 T{
 DEL
 T}@T{
 0x7F
 T}@T{
-\[u2421]
+␡
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -44444,7 +44493,7 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 .TE
 .PP
@@ -44465,7 +44514,7 @@ There are 3 modes rclone can use for uploads.
 In this mode rclone will not use upload batching.
 This was the default before rclone v1.55.
 It has the disadvantage that it is very likely to encounter
-\f[C]too_many_requests\f[R] errors like this
+\f[V]too_many_requests\f[R] errors like this
 .IP
 .nf
 \f[C]
@@ -44476,17 +44525,17 @@ NOTICE: too_many_requests/.: Too many requests or write operations. Trying again
 When rclone receives these it has to wait for 15s or sometimes 300s
 before continuing which really slows down transfers.
 .PP
-This will happen especially if \f[C]--transfers\f[R] is large, so this
+This will happen especially if \f[V]--transfers\f[R] is large, so this
 mode isn\[aq]t recommended except for compatibility or investigating
 problems.
 .SS --dropbox-batch-mode sync
 .PP
 In this mode rclone will batch up uploads to the size specified by
-\f[C]--dropbox-batch-size\f[R] and commit them together.
+\f[V]--dropbox-batch-size\f[R] and commit them together.
 .PP
-Using this mode means you can use a much higher \f[C]--transfers\f[R]
+Using this mode means you can use a much higher \f[V]--transfers\f[R]
 parameter (32 or 64 works fine) without receiving
-\f[C]too_many_requests\f[R] errors.
+\f[V]too_many_requests\f[R] errors.
 .PP
 This mode ensures full data integrity.
 .PP
@@ -44495,12 +44544,12 @@ finishes up the last batch using this mode.
 .SS --dropbox-batch-mode async
 .PP
 In this mode rclone will batch up uploads to the size specified by
-\f[C]--dropbox-batch-size\f[R] and commit them together.
+\f[V]--dropbox-batch-size\f[R] and commit them together.
 .PP
 However it will not wait for the status of the batch to be returned to
 the caller.
 This means rclone can use a much bigger batch size (much bigger than
-\f[C]--transfers\f[R]), at the cost of not being able to check the
+\f[V]--transfers\f[R]), at the cost of not being able to check the
 status of the upload.
 .PP
 This provides the maximum possible upload speed especially with lots of
@@ -44510,8 +44559,8 @@ properly using this mode.
 If you are using this mode then using \[dq]rclone check\[dq] after the
 transfer completes is recommended.
 Or you could do an initial transfer with
-\f[C]--dropbox-batch-mode async\f[R] then do a final transfer with
-\f[C]--dropbox-batch-mode sync\f[R] (the default).
+\f[V]--dropbox-batch-mode async\f[R] then do a final transfer with
+\f[V]--dropbox-batch-mode sync\f[R] (the default).
 .PP
 Note that there may be a pause when quitting rclone while rclone
 finishes up the last batch using this mode.
@@ -44647,7 +44696,8 @@ Required: false
 Instructs rclone to work on individual shared files.
 .PP
 In this mode rclone\[aq]s features are extremely limited - only list
-(ls, lsl, etc.) operations and read operations (e.g.
+(ls, lsl, etc.)
+operations and read operations (e.g.
 downloading) are supported in this mode.
 All other operations will be disabled.
 .PP
@@ -44848,12 +44898,12 @@ Required: false
 Note that Dropbox is case insensitive so you can\[aq]t have a file
 called \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .PP
-There are some file names such as \f[C]thumbs.db\f[R] which Dropbox
+There are some file names such as \f[V]thumbs.db\f[R] which Dropbox
 can\[aq]t store.
 There is a full list of them in the \[dq]Ignored Files\[dq] section of
 this document (https://www.dropbox.com/en/help/145).
 Rclone will issue an error message
-\f[C]File name disallowed - not uploading\f[R] if it attempts to upload
+\f[V]File name disallowed - not uploading\f[R] if it attempts to upload
 one of those file names, but the sync won\[aq]t fail.
 .PP
 Some errors may occur if you try to sync copyright-protected files
@@ -44861,18 +44911,18 @@ because Dropbox has its own copyright
 detector (https://techcrunch.com/2014/03/30/how-dropbox-knows-when-youre-sharing-copyrighted-stuff-without-actually-looking-at-your-stuff/)
 that prevents this sort of file being downloaded.
 This will return the error
-\f[C]ERROR : /path/to/your/file: Failed to copy: failed to open source object: path/restricted_content/.\f[R]
+\f[V]ERROR : /path/to/your/file: Failed to copy: failed to open source object: path/restricted_content/.\f[R]
 .PP
 If you have more than 10,000 files in a directory then
-\f[C]rclone purge dropbox:dir\f[R] will return the error
-\f[C]Failed to purge: There are too many files involved in this operation\f[R].
-As a work-around do an \f[C]rclone delete dropbox:dir\f[R] followed by
-an \f[C]rclone rmdir dropbox:dir\f[R].
+\f[V]rclone purge dropbox:dir\f[R] will return the error
+\f[V]Failed to purge: There are too many files involved in this operation\f[R].
+As a work-around do an \f[V]rclone delete dropbox:dir\f[R] followed by
+an \f[V]rclone rmdir dropbox:dir\f[R].
 .PP
-When using \f[C]rclone link\f[R] you\[aq]ll need to set
-\f[C]--expire\f[R] if using a non-personal account otherwise the
+When using \f[V]rclone link\f[R] you\[aq]ll need to set
+\f[V]--expire\f[R] if using a non-personal account otherwise the
 visibility may not be correct.
-(Note that \f[C]--expire\f[R] isn\[aq]t supported on personal accounts).
+(Note that \f[V]--expire\f[R] isn\[aq]t supported on personal accounts).
 See the forum
 discussion (https://forum.rclone.org/t/rclone-link-dropbox-permissions/23211)
 and the dropbox SDK
@@ -44890,52 +44940,52 @@ console (https://www.dropbox.com/developers/apps/create) with your
 Dropbox Account (It need not to be the same account as the Dropbox you
 want to access)
 .IP "2." 3
-Choose an API => Usually this should be \f[C]Dropbox API\f[R]
+Choose an API => Usually this should be \f[V]Dropbox API\f[R]
 .IP "3." 3
-Choose the type of access you want to use => \f[C]Full Dropbox\f[R] or
-\f[C]App Folder\f[R].
-If you want to use Team Folders, \f[C]Full Dropbox\f[R] is required (see
+Choose the type of access you want to use => \f[V]Full Dropbox\f[R] or
+\f[V]App Folder\f[R].
+If you want to use Team Folders, \f[V]Full Dropbox\f[R] is required (see
 here (https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/How-to-create-team-folder-inside-my-app-s-folder/m-p/601005/highlight/true#M27911)).
 .IP "4." 3
 Name your App.
-The app name is global, so you can\[aq]t use \f[C]rclone\f[R] for
+The app name is global, so you can\[aq]t use \f[V]rclone\f[R] for
 example
 .IP "5." 3
-Click the button \f[C]Create App\f[R]
+Click the button \f[V]Create App\f[R]
 .IP "6." 3
-Switch to the \f[C]Permissions\f[R] tab.
-Enable at least the following permissions: \f[C]account_info.read\f[R],
-\f[C]files.metadata.write\f[R], \f[C]files.content.write\f[R],
-\f[C]files.content.read\f[R], \f[C]sharing.write\f[R].
-The \f[C]files.metadata.read\f[R] and \f[C]sharing.read\f[R] checkboxes
+Switch to the \f[V]Permissions\f[R] tab.
+Enable at least the following permissions: \f[V]account_info.read\f[R],
+\f[V]files.metadata.write\f[R], \f[V]files.content.write\f[R],
+\f[V]files.content.read\f[R], \f[V]sharing.write\f[R].
+The \f[V]files.metadata.read\f[R] and \f[V]sharing.read\f[R] checkboxes
 will be marked too.
-Click \f[C]Submit\f[R]
+Click \f[V]Submit\f[R]
 .IP "7." 3
-Switch to the \f[C]Settings\f[R] tab.
-Fill \f[C]OAuth2 - Redirect URIs\f[R] as
-\f[C]http://localhost:53682/\f[R] and click on \f[C]Add\f[R]
+Switch to the \f[V]Settings\f[R] tab.
+Fill \f[V]OAuth2 - Redirect URIs\f[R] as
+\f[V]http://localhost:53682/\f[R] and click on \f[V]Add\f[R]
 .IP "8." 3
-Find the \f[C]App key\f[R] and \f[C]App secret\f[R] values on the
-\f[C]Settings\f[R] tab.
+Find the \f[V]App key\f[R] and \f[V]App secret\f[R] values on the
+\f[V]Settings\f[R] tab.
 Use these values in rclone config to add a new remote or edit an
 existing remote.
-The \f[C]App key\f[R] setting corresponds to \f[C]client_id\f[R] in
-rclone config, the \f[C]App secret\f[R] corresponds to
-\f[C]client_secret\f[R]
+The \f[V]App key\f[R] setting corresponds to \f[V]client_id\f[R] in
+rclone config, the \f[V]App secret\f[R] corresponds to
+\f[V]client_secret\f[R]
 .SH Enterprise File Fabric
 .PP
 This backend supports Storage Made Easy\[aq]s Enterprise File
-Fabric\[tm] (https://storagemadeeasy.com/about/) which provides a
-software solution to integrate and unify File and Object Storage
-accessible through a global file system.
+Fabric™ (https://storagemadeeasy.com/about/) which provides a software
+solution to integrate and unify File and Object Storage accessible
+through a global file system.
 .SS Configuration
 .PP
 The initial setup for the Enterprise File Fabric backend involves
 getting a token from the Enterprise File Fabric which you need to do in
 your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -45012,7 +45062,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Enterprise File Fabric
 .IP
@@ -45059,12 +45109,12 @@ be used in JSON strings.
 .PP
 Empty files aren\[aq]t supported by the Enterprise File Fabric.
 Rclone will therefore upload an empty file as a single space with a mime
-type of \f[C]application/vnd.rclone.empty.file\f[R] and files with that
+type of \f[V]application/vnd.rclone.empty.file\f[R] and files with that
 mime type are treated as empty.
 .SS Root folder ID
 .PP
-You can set the \f[C]root_folder_id\f[R] for rclone.
-This is the directory (identified by its \f[C]Folder ID\f[R]) that
+You can set the \f[V]root_folder_id\f[R] for rclone.
+This is the directory (identified by its \f[V]Folder ID\f[R]) that
 rclone considers to be the root of your Enterprise File Fabric.
 .PP
 Normally you will leave this blank and rclone will determine the correct
@@ -45073,10 +45123,10 @@ root to use itself.
 However you can set this to restrict rclone to a specific folder
 hierarchy.
 .PP
-In order to do this you will have to find the \f[C]Folder ID\f[R] of the
+In order to do this you will have to find the \f[V]Folder ID\f[R] of the
 directory you wish rclone to display.
 These aren\[aq]t displayed in the web interface, but you can use
-\f[C]rclone lsf\f[R] to find them, for example
+\f[V]rclone lsf\f[R] to find them, for example
 .IP
 .nf
 \f[C]
@@ -45090,7 +45140,7 @@ $ rclone lsf --dirs-only -Fip --csv filefabric:
 \f[R]
 .fi
 .PP
-The ID for \[dq]S3 Storage\[dq] would be \f[C]120673761\f[R].
+The ID for \[dq]S3 Storage\[dq] would be \f[V]120673761\f[R].
 .SS Standard options
 .PP
 Here are the Standard options specific to filefabric (Enterprise File
@@ -45262,10 +45312,10 @@ You can do this by providing your site subdomain, username, and
 password.
 Alternatively, you can authenticate using an API Key from
 Files.com (https://www.files.com/docs/sdk-and-apis/api-keys/).
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -45363,7 +45413,7 @@ rclone ls remote:
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote directory, deleting
+Sync \f[V]/home/local/directory\f[R] to the remote directory, deleting
 any excess files in the directory.
 .IP
 .nf
@@ -45464,6 +45514,550 @@ Env Var: RCLONE_FILESCOM_DESCRIPTION
 Type: string
 .IP \[bu] 2
 Required: false
+.SH FrostFS
+.PP
+Rclone FrostFS support is provided using the
+git.frostfs.info/TrueCloudLab/frostfs-sdk-go (https://git.frostfs.info/TrueCloudLab/frostfs-sdk-go)
+package
+.SS Configuration
+.PP
+To create an FrostFS configuration named \f[V]remote\f[R], run
+.IP
+.nf
+\f[C]
+rclone config
+\f[R]
+.fi
+.PP
+Rclone config guides you through an interactive setup process.
+A minimal rclone FrostFS remote definition only requires endpoint and
+path to FrostFS user wallet.
+.IP
+.nf
+\f[C]
+No remotes found, make a new one?
+n) New remote
+s) Set configuration password
+q) Quit config
+n/s/q> n
+
+Enter name for new remote.
+name> remote
+
+Option Storage.
+Type of storage to configure.
+Choose a number from below, or type in your own value.
+ 1 / 1Fichier
+   \[rs] (fichier)
+ 2 / Akamai NetStorage
+   \[rs] (netstorage)
+ 3 / Alias for an existing remote
+   \[rs] (alias)
+ 4 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, ArvanCloud, Ceph, ChinaMobile, Cloudflare, DigitalOcean, Dreamhost, GCS, HuaweiOBS, IBMCOS, IDrive, IONOS, LyveCloud, Leviia, Liara, Linode, Magalu, Minio, Netease, Petabox, RackCorp, Rclone, Scaleway, SeaweedFS, StackPath, Storj, Synology, TencentCOS, Wasabi, Qiniu and others
+   \[rs] (s3)
+ 5 / Backblaze B2
+   \[rs] (b2)
+ 6 / Better checksums for other remotes
+   \[rs] (hasher)
+ 7 / Box
+   \[rs] (box)
+ 8 / Cache a remote
+   \[rs] (cache)
+ 9 / Citrix Sharefile
+   \[rs] (sharefile)
+10 / Combine several remotes into one
+   \[rs] (combine)
+11 / Compress a remote
+   \[rs] (compress)
+12 / Distributed, decentralized object storage FrostFS
+   \[rs] (frostfs)
+13 / Dropbox
+   \[rs] (dropbox)
+14 / Encrypt/Decrypt a remote
+   \[rs] (crypt)
+15 / Enterprise File Fabric
+   \[rs] (filefabric)
+16 / FTP
+   \[rs] (ftp)
+17 / Files.com
+   \[rs] (filescom)
+18 / Gofile
+   \[rs] (gofile)
+19 / Google Cloud Storage (this is not Google Drive)
+   \[rs] (google cloud storage)
+20 / Google Drive
+   \[rs] (drive)
+21 / Google Photos
+   \[rs] (google photos)
+22 / HTTP
+   \[rs] (http)
+23 / Hadoop distributed file system
+   \[rs] (hdfs)
+24 / HiDrive
+   \[rs] (hidrive)
+25 / ImageKit.io
+   \[rs] (imagekit)
+26 / In memory object storage system.
+   \[rs] (memory)
+27 / Internet Archive
+   \[rs] (internetarchive)
+28 / Jottacloud
+   \[rs] (jottacloud)
+29 / Koofr, Digi Storage and other Koofr-compatible storage providers
+   \[rs] (koofr)
+30 / Linkbox
+   \[rs] (linkbox)
+31 / Local Disk
+   \[rs] (local)
+32 / Mail.ru Cloud
+   \[rs] (mailru)
+33 / Mega
+   \[rs] (mega)
+34 / Microsoft Azure Blob Storage
+   \[rs] (azureblob)
+35 / Microsoft Azure Files
+   \[rs] (azurefiles)
+36 / Microsoft OneDrive
+   \[rs] (onedrive)
+37 / OpenDrive
+   \[rs] (opendrive)
+38 / OpenStack Swift (Rackspace Cloud Files, Blomp Cloud Storage, Memset Memstore, OVH)
+   \[rs] (swift)
+39 / Oracle Cloud Infrastructure Object Storage
+   \[rs] (oracleobjectstorage)
+40 / Pcloud
+   \[rs] (pcloud)
+41 / PikPak
+   \[rs] (pikpak)
+42 / Pixeldrain Filesystem
+   \[rs] (pixeldrain)
+43 / Proton Drive
+   \[rs] (protondrive)
+44 / Put.io
+   \[rs] (putio)
+45 / QingCloud Object Storage
+   \[rs] (qingstor)
+46 / Quatrix by Maytech
+   \[rs] (quatrix)
+47 / SMB / CIFS
+   \[rs] (smb)
+48 / SSH/SFTP
+   \[rs] (sftp)
+49 / Sia Decentralized Cloud
+   \[rs] (sia)
+50 / Storj Decentralized Cloud Storage
+   \[rs] (storj)
+51 / Sugarsync
+   \[rs] (sugarsync)
+52 / Transparently chunk/split large files
+   \[rs] (chunker)
+53 / Uloz.to
+   \[rs] (ulozto)
+54 / Union merges the contents of several upstream fs
+   \[rs] (union)
+55 / Uptobox
+   \[rs] (uptobox)
+56 / WebDAV
+   \[rs] (webdav)
+57 / Yandex Disk
+   \[rs] (yandex)
+58 / Zoho
+   \[rs] (zoho)
+59 / premiumize.me
+   \[rs] (premiumizeme)
+60 / seafile
+   \[rs] (seafile)
+Storage> frostfs
+
+Option endpoint.
+Endpoints to connect to FrostFS node
+Choose a number from below, or type in your own value.
+ 1 / One endpoint.
+   \[rs] (s01.frostfs.devenv:8080)
+ 2 / Multiple endpoints to form pool.
+   \[rs] (s01.frostfs.devenv:8080 s02.frostfs.devenv:8080)
+ 3 / Multiple endpoints with priority (less value is higher priority). Until s01 is healthy all request will be send to it.
+   \[rs] (s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2)
+ 4 / Multiple endpoints with priority and weights. After s01 is unhealthy requests will be send to s02 and s03 in proportions 10% and 90% respectively.
+   \[rs] (s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1 s03.frostfs.devenv:8080,2,9)
+endpoint> s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+
+Option connection_timeout.
+FrostFS connection timeout
+Enter a value of type Duration. Press Enter for the default (4s).
+connection_timeout> 
+
+Option request_timeout.
+FrostFS request timeout
+Enter a value of type Duration. Press Enter for the default (4s).
+request_timeout> 
+
+Option rebalance_interval.
+FrostFS rebalance connections interval
+Enter a value of type Duration. Press Enter for the default (15s).
+rebalance_interval> 
+
+Option session_expiration.
+FrostFS session expiration epoch
+Enter a signed integer. Press Enter for the default (4294967295).
+session_expiration> 
+
+Option ape_cache_invalidation_duration.
+APE cache invalidation duration
+Enter a value of type Duration. Press Enter for the default (8s).
+ape_cache_invalidation_duration> 
+
+Option ape_cache_invalidation_timeout.
+APE cache invalidation timeout
+Enter a value of type Duration. Press Enter for the default (16s).
+ape_cache_invalidation_timeout> 
+
+Option ape_chain_check_interval.
+The interval for verifying that the APE chain is saved in FrostFS.
+Enter a value of type Duration. Press Enter for the default (500ms).
+ape_chain_check_interval> 
+
+Option rpc_endpoint.
+Endpoint to connect to Neo rpc node
+Enter a value. Press Enter to leave empty.
+rpc_endpoint> 
+
+Option wallet.
+Path to wallet
+Enter a value.
+wallet> /wallets/wallet.conf
+
+Option address.
+Address of account
+Enter a value. Press Enter to leave empty.
+address> 
+
+Option password.
+Password to decrypt wallet
+Enter a value. Press Enter to leave empty.
+password> 
+
+Option placement_policy.
+Placement policy for new containers
+Choose a number from below, or type in your own value of type string.
+Press Enter for the default (REP 3).
+ 1 / Container will have 3 replicas
+   \[rs] (REP 3)
+placement_policy> REP 1
+
+Option container_creation_policy.
+Container creation policy for new containers
+Choose a number from below, or type in your own value of type string.
+Press Enter for the default (private).
+ 1 / Public container, anyone can read and write
+   \[rs] (public-read-write)
+ 2 / Public container, owner can read and write, others can only read
+   \[rs] (public-read)
+ 3 / Private container, only owner has access to it
+   \[rs] (private)
+container_creation_policy> 
+
+Edit advanced config?
+y) Yes
+n) No (default)
+y/n> n
+
+Configuration complete.
+Options:
+- type: frostfs
+- endpoint: s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2
+- password: M\[at]zPGpWDravchenko/develop/go/playground/play_with_ape/cfg/wallet_akrav.js
+- placement_policy: REP 1
+Keep this \[dq]remote\[dq] remote?
+y) Yes this is OK (default)
+e) Edit this remote
+d) Delete this remote
+y/e/d> y
+\f[R]
+.fi
+.PP
+As a remote root directory, you can use either the container identifier
+or its user-friendly name.
+If you choose to use a container name, rclone will create a new
+container with that name when it\[aq]s used for the first time.
+.PP
+For example, both of the following commands would be valid if there was
+a \f[V]\[ti]/test-copy\f[R] directory and a container with the
+identifier \f[V]23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf\f[R]:
+.IP
+.nf
+\f[C]
+rclone copy \[ti]/test-copy remote:23fk3Bcw5mPZ4YtYkTLJbQebtM2WXHz4HL8FgsrTJkSf/test-copy
+rclone copy \[ti]/test-copy remote:container-name/test-copy
+\f[R]
+.fi
+.SS Standard options
+.PP
+Here are the Standard options specific to frostfs (Distributed,
+decentralized object storage FrostFS).
+.SS --frostfs-endpoint
+.PP
+Endpoints to connect to FrostFS node
+.PP
+Properties:
+.IP \[bu] 2
+Config: endpoint
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_ENDPOINT
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Required: true
+.IP \[bu] 2
+Examples:
+.RS 2
+.IP \[bu] 2
+\[dq]s01.frostfs.devenv:8080\[dq]
+.RS 2
+.IP \[bu] 2
+One endpoint.
+.RE
+.IP \[bu] 2
+\[dq]s01.frostfs.devenv:8080 s02.frostfs.devenv:8080\[dq]
+.RS 2
+.IP \[bu] 2
+Multiple endpoints to form pool.
+.RE
+.IP \[bu] 2
+\[dq]s01.frostfs.devenv:8080,1 s02.frostfs.devenv:8080,2\[dq]
+.RS 2
+.IP \[bu] 2
+Multiple endpoints with priority (lower value has higher priority).
+Until s01 is healthy, all requests will be sent to it.
+.RE
+.IP \[bu] 2
+\[dq]s01.frostfs.devenv:8080,1,1 s02.frostfs.devenv:8080,2,1
+s03.frostfs.devenv:8080,2,9\[dq]
+.RS 2
+.IP \[bu] 2
+Multiple endpoints with priority and weights.
+After the s01 endpoint is unhealthy, requests will be sent to the s02
+and s03 endpoints in proportions of 10% and 90%, respectively.
+.RE
+.RE
+.SS --frostfs-connection-timeout
+.PP
+FrostFS connection timeout
+.PP
+Properties:
+.IP \[bu] 2
+Config: connection_timeout
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_CONNECTION_TIMEOUT
+.IP \[bu] 2
+Type: Duration
+.IP \[bu] 2
+Default: 4s
+.SS --frostfs-request-timeout
+.PP
+FrostFS request timeout
+.PP
+Properties:
+.IP \[bu] 2
+Config: request_timeout
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_REQUEST_TIMEOUT
+.IP \[bu] 2
+Type: Duration
+.IP \[bu] 2
+Default: 12s
+.SS --frostfs-rebalance-interval
+.PP
+FrostFS rebalance connections interval
+.PP
+Properties:
+.IP \[bu] 2
+Config: rebalance_interval
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_REBALANCE_INTERVAL
+.IP \[bu] 2
+Type: Duration
+.IP \[bu] 2
+Default: 15s
+.SS --frostfs-session-expiration
+.PP
+FrostFS session expiration epoch
+.PP
+Properties:
+.IP \[bu] 2
+Config: session_expiration
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_SESSION_EXPIRATION
+.IP \[bu] 2
+Type: int
+.IP \[bu] 2
+Default: 4294967295
+.SS --frostfs-ape-cache-invalidation-duration
+.PP
+APE cache invalidation duration
+.PP
+Properties:
+.IP \[bu] 2
+Config: ape_cache_invalidation_duration
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_APE_CACHE_INVALIDATION_DURATION
+.IP \[bu] 2
+Type: Duration
+.IP \[bu] 2
+Default: 8s
+.SS --frostfs-ape-cache-invalidation-timeout
+.PP
+APE cache invalidation timeout
+.PP
+Properties:
+.IP \[bu] 2
+Config: ape_cache_invalidation_timeout
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_APE_CACHE_INVALIDATION_TIMEOUT
+.IP \[bu] 2
+Type: Duration
+.IP \[bu] 2
+Default: 24s
+.SS --frostfs-ape-chain-check-interval
+.PP
+The interval for verifying that the APE chain is saved in FrostFS.
+.PP
+Properties:
+.IP \[bu] 2
+Config: ape_chain_check_interval
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_APE_CHAIN_CHECK_INTERVAL
+.IP \[bu] 2
+Type: Duration
+.IP \[bu] 2
+Default: 500ms
+.SS --frostfs-rpc-endpoint
+.PP
+Endpoint to connect to Neo rpc node
+.PP
+Properties:
+.IP \[bu] 2
+Config: rpc_endpoint
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_RPC_ENDPOINT
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Required: false
+.SS --frostfs-wallet
+.PP
+Path to wallet
+.PP
+Properties:
+.IP \[bu] 2
+Config: wallet
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_WALLET
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Required: true
+.SS --frostfs-address
+.PP
+Address of account
+.PP
+Properties:
+.IP \[bu] 2
+Config: address
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_ADDRESS
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Required: false
+.SS --frostfs-password
+.PP
+Password to decrypt wallet
+.PP
+Properties:
+.IP \[bu] 2
+Config: password
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_PASSWORD
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Required: false
+.SS --frostfs-placement-policy
+.PP
+Placement policy for new containers
+.PP
+Properties:
+.IP \[bu] 2
+Config: placement_policy
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_PLACEMENT_POLICY
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]REP 3\[dq]
+.IP \[bu] 2
+Examples:
+.RS 2
+.IP \[bu] 2
+\[dq]REP 3\[dq]
+.RS 2
+.IP \[bu] 2
+Container will have 3 replicas
+.RE
+.RE
+.SS --frostfs-container-creation-policy
+.PP
+Container creation policy for new containers
+.PP
+Properties:
+.IP \[bu] 2
+Config: container_creation_policy
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_CONTAINER_CREATION_POLICY
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Default: \[dq]private\[dq]
+.IP \[bu] 2
+Examples:
+.RS 2
+.IP \[bu] 2
+\[dq]public-read-write\[dq]
+.RS 2
+.IP \[bu] 2
+Public container, anyone can read and write
+.RE
+.IP \[bu] 2
+\[dq]public-read\[dq]
+.RS 2
+.IP \[bu] 2
+Public container, owner can read and write, others can only read
+.RE
+.IP \[bu] 2
+\[dq]private\[dq]
+.RS 2
+.IP \[bu] 2
+Private container, only owner has access to it
+.RE
+.RE
+.SS Advanced options
+.PP
+Here are the Advanced options specific to frostfs (Distributed,
+decentralized object storage FrostFS).
+.SS --frostfs-description
+.PP
+Description of the remote.
+.PP
+Properties:
+.IP \[bu] 2
+Config: description
+.IP \[bu] 2
+Env Var: RCLONE_FROSTFS_DESCRIPTION
+.IP \[bu] 2
+Type: string
+.IP \[bu] 2
+Required: false
 .SH FTP
 .PP
 FTP is the File Transfer Protocol.
@@ -45473,13 +46067,13 @@ package.
 .PP
 Limitations of Rclone\[aq]s FTP backend
 .PP
-Paths are specified as \f[C]remote:path\f[R].
-If the path does not begin with a \f[C]/\f[R] it is relative to the home
+Paths are specified as \f[V]remote:path\f[R].
+If the path does not begin with a \f[V]/\f[R] it is relative to the home
 directory of the user.
-An empty path \f[C]remote:\f[R] refers to the user\[aq]s home directory.
+An empty path \f[V]remote:\f[R] refers to the user\[aq]s home directory.
 .SS Configuration
 .PP
-To create an FTP configuration named \f[C]remote\f[R], run
+To create an FTP configuration named \f[V]remote\f[R], run
 .IP
 .nf
 \f[C]
@@ -45552,7 +46146,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-To see all directories in the home directory of \f[C]remote\f[R]
+To see all directories in the home directory of \f[V]remote\f[R]
 .IP
 .nf
 \f[C]
@@ -45576,7 +46170,7 @@ rclone ls remote:path/to/directory
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote directory, deleting
+Sync \f[V]/home/local/directory\f[R] to the remote directory, deleting
 any excess files in the directory.
 .IP
 .nf
@@ -45621,14 +46215,14 @@ rclone lsf :ftp: --ftp-host=speedtest.tele2.net --ftp-user=anonymous --ftp-pass=
 rclone lsf :ftp,host=speedtest.tele2.net,user=anonymous,pass=IXs2wc8OJOz7SYLBk47Ji1rHTmxM:
 \f[R]
 .fi
-.SS Implicit TLS
+.SS Implicit TLSutil.go
 .PP
 Rlone FTP supports implicit FTP over TLS servers (FTPS).
 This has to be enabled in the FTP backend config for the remote, or with
-\f[C]--ftp-tls\f[R].
-The default FTPS port is \f[C]990\f[R], not \f[C]21\f[R] and can be set
-with \f[C]--ftp-port\f[R].
-.SS Restricted filename characters
+\f[V]--ftp-tls\f[R].
+The default FTPS port is \f[V]990\f[R], not \f[V]21\f[R] and can be set
+with \f[V]--ftp-port\f[R].
+util.go ### Restricted filename characters
 .PP
 In addition to the default restricted characters
 set (https://rclone.org/overview/#restricted-characters) the following
@@ -45653,7 +46247,7 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 .TE
 .PP
@@ -45671,12 +46265,12 @@ _
 T{
 proftpd
 T}@T{
-\f[C]*\f[R]
+\f[V]*\f[R]
 T}
 T{
 pureftpd
 T}@T{
-\f[C]\[rs] [ ]\f[R]
+\f[V]\[rs] [ ]\f[R]
 T}
 .TE
 .PP
@@ -45792,14 +46386,14 @@ Note that setting this is very likely to cause deadlocks so it should be
 used with care.
 .PP
 If you are doing a sync or copy then make sure concurrency is one more
-than the sum of \f[C]--transfers\f[R] and \f[C]--checkers\f[R].
+than the sum of \f[V]--transfers\f[R] and \f[V]--checkers\f[R].
 .PP
-If you use \f[C]--check-first\f[R] then it just needs to be one more
-than the maximum of \f[C]--checkers\f[R] and \f[C]--transfers\f[R].
+If you use \f[V]--check-first\f[R] then it just needs to be one more
+than the maximum of \f[V]--checkers\f[R] and \f[V]--transfers\f[R].
 .PP
-So for \f[C]concurrency 3\f[R] you\[aq]d use
-\f[C]--checkers 2 --transfers 2 --check-first\f[R] or
-\f[C]--checkers 1 --transfers 1\f[R].
+So for \f[V]concurrency 3\f[R] you\[aq]d use
+\f[V]--checkers 2 --transfers 2 --check-first\f[R] or
+\f[V]--checkers 1 --transfers 1\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -46059,11 +46653,11 @@ Type: string
 Required: false
 .SS Limitations
 .PP
-FTP servers acting as rclone remotes must support \f[C]passive\f[R]
+FTP servers acting as rclone remotes must support \f[V]passive\f[R]
 mode.
-The mode cannot be configured as \f[C]passive\f[R] is the only supported
+The mode cannot be configured as \f[V]passive\f[R] is the only supported
 one.
-Rclone\[aq]s FTP implementation is not compatible with \f[C]active\f[R]
+Rclone\[aq]s FTP implementation is not compatible with \f[V]active\f[R]
 mode as the library it uses doesn\[aq]t support
 it (https://github.com/jlaffaye/ftp/issues/29).
 This will likely never be supported due to security concerns.
@@ -46071,53 +46665,53 @@ This will likely never be supported due to security concerns.
 Rclone\[aq]s FTP backend does not support any checksums but can compare
 file sizes.
 .PP
-\f[C]rclone about\f[R] is not supported by the FTP backend.
+\f[V]rclone about\f[R] is not supported by the FTP backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
 about (https://rclone.org/overview/#optional-features) and rclone
 about (https://rclone.org/commands/rclone_about/)
 .PP
-The implementation of : \f[C]--dump headers\f[R],
-\f[C]--dump bodies\f[R], \f[C]--dump auth\f[R] for debugging isn\[aq]t
+The implementation of : \f[V]--dump headers\f[R],
+\f[V]--dump bodies\f[R], \f[V]--dump auth\f[R] for debugging isn\[aq]t
 the same as for rclone HTTP based backends - it has less fine grained
 control.
 .PP
-\f[C]--timeout\f[R] isn\[aq]t supported (but \f[C]--contimeout\f[R] is).
+\f[V]--timeout\f[R] isn\[aq]t supported (but \f[V]--contimeout\f[R] is).
 .PP
-\f[C]--bind\f[R] isn\[aq]t supported.
+\f[V]--bind\f[R] isn\[aq]t supported.
 .PP
 Rclone\[aq]s FTP backend could support server-side move but does not at
 present.
 .PP
-The \f[C]ftp_proxy\f[R] environment variable is not currently supported.
+The \f[V]ftp_proxy\f[R] environment variable is not currently supported.
 .SS Modification times
 .PP
 File modification time (timestamps) is supported to 1 second resolution
 for major FTP servers: ProFTPd, PureFTPd, VsFTPd, and FileZilla FTP
 server.
-The \f[C]VsFTPd\f[R] server has non-standard implementation of time
+The \f[V]VsFTPd\f[R] server has non-standard implementation of time
 related protocol commands and needs a special configuration setting:
-\f[C]writing_mdtm = true\f[R].
+\f[V]writing_mdtm = true\f[R].
 .PP
 Support for precise file time with other FTP servers varies depending on
 what protocol extensions they advertise.
-If all the \f[C]MLSD\f[R], \f[C]MDTM\f[R] and \f[C]MFTM\f[R] extensions
+If all the \f[V]MLSD\f[R], \f[V]MDTM\f[R] and \f[V]MFTM\f[R] extensions
 are present, rclone will use them together to provide precise time.
 Otherwise the times you see on the FTP server through rclone are those
 of the last file upload.
 .PP
 You can use the following command to check whether rclone can use
 precise time with your FTP server:
-\f[C]rclone backend features your_ftp_remote:\f[R] (the trailing colon
+\f[V]rclone backend features your_ftp_remote:\f[R] (the trailing colon
 is important).
-Look for the number in the line tagged by \f[C]Precision\f[R]
+Look for the number in the line tagged by \f[V]Precision\f[R]
 designating the remote time precision expressed as nanoseconds.
-A value of \f[C]1000000000\f[R] means that file time precision of 1
+A value of \f[V]1000000000\f[R] means that file time precision of 1
 second is available.
-A value of \f[C]3153600000000000000\f[R] (or another large number) means
+A value of \f[V]3153600000000000000\f[R] (or another large number) means
 \[dq]unsupported\[dq].
 .SH Gofile
 .PP
@@ -46134,7 +46728,7 @@ Note that if you wish to connect rclone to Gofile you will need a
 premium account.
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -46186,7 +46780,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories and files in the top level of your Gofile
 .IP
@@ -46207,7 +46801,7 @@ rclone copy /home/source remote:backup
 .PP
 Gofile supports modification times with a resolution of 1 second.
 .PP
-Gofile supports MD5 hashes, so you can use the \f[C]--checksum\f[R]
+Gofile supports MD5 hashes, so you can use the \f[V]--checksum\f[R]
 flag.
 .SS Restricted filename characters
 .PP
@@ -46231,63 +46825,63 @@ T{
 T}@T{
 0x21
 T}@T{
-\[uFF01]
+！
 T}
 T{
 \[dq]
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 *
 T}@T{
 0x2A
 T}@T{
-\[uFF0A]
+＊
 T}
 T{
 :
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 ?
 T}@T{
 0x3F
 T}@T{
-\[uFF1F]
+？
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 |
 T}@T{
 0x7C
 T}@T{
-\[uFF5C]
+｜
 T}
 .TE
 .PP
@@ -46311,7 +46905,7 @@ T{
 T}@T{
 0x2E
 T}@T{
-\[uFF0E]
+．
 T}
 .TE
 .PP
@@ -46320,17 +46914,17 @@ replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .SS Public Links
 .PP
-Gofile supports \f[C]rclone link\f[R] to make public links to files or
+Gofile supports \f[V]rclone link\f[R] to make public links to files or
 directories.
-If you specify a directory it will download as a \f[C]zip\f[R] file.
-You can use the \f[C]--expire\f[R] flag to specify the time the link
+If you specify a directory it will download as a \f[V]zip\f[R] file.
+You can use the \f[V]--expire\f[R] flag to specify the time the link
 should be valid.
-Note that \f[C]rclone link --unlink\f[R] removes all the public links
+Note that \f[V]rclone link --unlink\f[R] removes all the public links
 for a file.
 .SS Root folder ID
 .PP
-You can set the \f[C]root_folder_id\f[R] for rclone.
-This is the directory (identified by its \f[C]Folder ID\f[R]) that
+You can set the \f[V]root_folder_id\f[R] for rclone.
+This is the directory (identified by its \f[V]Folder ID\f[R]) that
 rclone considers to be the root of your Gofile drive.
 .PP
 Normally you will leave this blank and rclone will determine the correct
@@ -46339,7 +46933,7 @@ root to use itself and fill in the value in the config file.
 However you can set this to restrict rclone to a specific folder
 hierarchy.
 .PP
-In order to do this you will have to find the \f[C]Folder ID\f[R] of the
+In order to do this you will have to find the \f[V]Folder ID\f[R] of the
 directory you wish rclone to display.
 .PP
 You can do this with rclone
@@ -46353,7 +46947,7 @@ d50e356c-29ca-4b27-a3a7-494d91026e04;Videos/
 \f[R]
 .fi
 .PP
-The ID to use is the part before the \f[C];\f[R] so you could set
+The ID to use is the part before the \f[V];\f[R] so you could set
 .IP
 .nf
 \f[C]
@@ -46361,7 +46955,7 @@ root_folder_id = d6341f53-ee65-4f29-9f59-d11e8070b2a0
 \f[R]
 .fi
 .PP
-To restrict rclone to the \f[C]Files\f[R] directory.
+To restrict rclone to the \f[V]Files\f[R] directory.
 .SS Standard options
 .PP
 Here are the Standard options specific to gofile (Gofile).
@@ -46467,37 +47061,38 @@ character is a unicode character.
 Directories should not be cached for more than 24h otherwise files in
 the directory may not be downloadable.
 In practice this means when using a VFS based rclone command such as
-\f[C]rclone mount\f[R] you should make sure \f[C]--dir-cache-time\f[R]
-is less than \f[C]24h\f[R].
+\f[V]rclone mount\f[R] you should make sure \f[V]--dir-cache-time\f[R]
+is less than \f[V]24h\f[R].
 .PP
 Note that Gofile is currently limited to a total of 100,000 items.
 If you attempt to upload more than that you will get
-\f[C]error-limit-100000\f[R].
+\f[V]error-limit-100000\f[R].
 This limit may be lifted in the future.
 .SS Duplicated files
 .PP
 Gofile is capable of having files with duplicated file names.
-For instance two files called \f[C]hello.txt\f[R] in the same directory.
+For instance two files called \f[V]hello.txt\f[R] in the same directory.
 .PP
 Rclone cannot sync that to a normal file system but it can be fixed with
-the \f[C]rclone dedupe\f[R] command.
+the \f[V]rclone dedupe\f[R] command.
 .PP
 Duplicated files cause problems with the syncing and you will see
 messages in the log about duplicates.
 .PP
-Use \f[C]rclone dedupe\f[R] to fix duplicated files.
+Use \f[V]rclone dedupe\f[R] to fix duplicated files.
 .SH Google Cloud Storage
 .PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:bucket/path/to/dir\f[R].
+Paths are specified as \f[V]remote:bucket\f[R] (or \f[V]remote:\f[R] for
+the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:bucket/path/to/dir\f[R].
 .SS Configuration
 .PP
 The initial setup for google cloud storage involves getting a token from
 Google Cloud Storage which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -46641,11 +47236,11 @@ token as returned from Google if using web browser to automatically
 authenticate.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this it may require you
 to unblock it temporarily if you are running a host firewall, or use
 manual mode.
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this
+This remote is called \f[V]remote\f[R] and can now be used like this
 .PP
 See all the buckets in your project
 .IP
@@ -46671,7 +47266,7 @@ rclone ls remote:bucket
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote bucket, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote bucket, deleting any
 excess files in the bucket.
 .IP
 .nf
@@ -46692,7 +47287,7 @@ Accounts (https://cloud.google.com/iam/docs/service-accounts), please
 head to the Service
 Account (https://console.cloud.google.com/permissions/serviceaccounts)
 section of the Google Developer Console.
-Service Accounts behave just like normal \f[C]User\f[R] permissions in
+Service Accounts behave just like normal \f[V]User\f[R] permissions in
 Google Cloud Storage
 ACLs (https://cloud.google.com/storage/docs/access-control), so you can
 limit their access (e.g.
@@ -46702,17 +47297,17 @@ Account\[aq]s credentials will be downloaded onto your machines.
 These credentials are what rclone will use for authentication.
 .PP
 To use a Service Account instead of OAuth2 token flow, enter the path to
-your Service Account credentials at the \f[C]service_account_file\f[R]
+your Service Account credentials at the \f[V]service_account_file\f[R]
 prompt and rclone won\[aq]t use the browser based authentication flow.
 If you\[aq]d rather stuff the contents of the credentials file into the
-rclone config file, you can set \f[C]service_account_credentials\f[R]
+rclone config file, you can set \f[V]service_account_credentials\f[R]
 with the actual contents of the file instead, or set the equivalent
 environment variable.
 .SS Anonymous Access
 .PP
 For downloads of objects that permit public access you can configure
-rclone to use anonymous access by setting \f[C]anonymous\f[R] to
-\f[C]true\f[R].
+rclone to use anonymous access by setting \f[V]anonymous\f[R] to
+\f[V]true\f[R].
 With unauthorized access you can\[aq]t write or create files but only
 read or list those buckets and objects that have public read access.
 .SS Application Default Credentials
@@ -46731,13 +47326,13 @@ Note that in the case application default credentials are used, there is
 no need to explicitly configure a project number.
 .SS --fast-list
 .PP
-This remote supports \f[C]--fast-list\f[R] which allows you to use fewer
+This remote supports \f[V]--fast-list\f[R] which allows you to use fewer
 transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
 .SS Custom upload headers
 .PP
-You can set custom upload headers with the \f[C]--header-upload\f[R]
+You can set custom upload headers with the \f[V]--header-upload\f[R]
 flag.
 Google Cloud Storage supports the headers as described in the working
 with metadata
@@ -46757,25 +47352,25 @@ X-Goog-Storage-Class
 .IP \[bu] 2
 X-Goog-Meta-
 .PP
-Eg \f[C]--header-upload \[dq]Content-Type text/potato\[dq]\f[R]
+Eg \f[V]--header-upload \[dq]Content-Type text/potato\[dq]\f[R]
 .PP
 Note that the last of these is for setting custom metadata in the form
-\f[C]--header-upload \[dq]x-goog-meta-key: value\[dq]\f[R]
+\f[V]--header-upload \[dq]x-goog-meta-key: value\[dq]\f[R]
 .SS Modification times
 .PP
 Google Cloud Storage stores md5sum natively.
 Google\[aq]s gsutil (https://cloud.google.com/storage/docs/gsutil) tool
 stores modification time with one-second precision as
-\f[C]goog-reserved-file-mtime\f[R] in file metadata.
+\f[V]goog-reserved-file-mtime\f[R] in file metadata.
 .PP
 To ensure compatibility with gsutil, rclone stores modification time in
 2 separate metadata entries.
-\f[C]mtime\f[R] uses RFC3339 format with one-nanosecond precision.
-\f[C]goog-reserved-file-mtime\f[R] uses Unix timestamp format with
+\f[V]mtime\f[R] uses RFC3339 format with one-nanosecond precision.
+\f[V]goog-reserved-file-mtime\f[R] uses Unix timestamp format with
 one-second precision.
 To get modification time from object metadata, rclone reads the metadata
-in the following order: \f[C]mtime\f[R],
-\f[C]goog-reserved-file-mtime\f[R], object updated time.
+in the following order: \f[V]mtime\f[R],
+\f[V]goog-reserved-file-mtime\f[R], object updated time.
 .PP
 Note that rclone\[aq]s default modify window is 1ns.
 Files uploaded by gsutil only contain timestamps with one-second
@@ -46783,7 +47378,7 @@ precision.
 If you use rclone to sync files previously uploaded by gsutil, rclone
 will attempt to update modification time for all these files.
 To avoid these possibly unnecessary updates, use
-\f[C]--modify-window 1s\f[R].
+\f[V]--modify-window 1s\f[R].
 .SS Restricted filename characters
 .PP
 .TS
@@ -46802,28 +47397,28 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 LF
 T}@T{
 0x0A
 T}@T{
-\[u240A]
+␊
 T}
 T{
 CR
 T}@T{
 0x0D
 T}@T{
-\[u240D]
+␍
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 .TE
 .PP
@@ -46902,8 +47497,8 @@ Service Account Credentials JSON file path.
 Leave blank normally.
 Needed only if you want use SA instead of interactive login.
 .PP
-Leading \f[C]\[ti]\f[R] will be expanded in the file name as will
-environment variables such as \f[C]${RCLONE_CONFIG_DIR}\f[R].
+Leading \f[V]\[ti]\f[R] will be expanded in the file name as will
+environment variables such as \f[V]${RCLONE_CONFIG_DIR}\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -47232,7 +47827,7 @@ Netherlands
 \[dq]europe-west6\[dq]
 .RS 2
 .IP \[bu] 2
-Z\[:u]rich
+Zürich
 .RE
 .IP \[bu] 2
 \[dq]europe-central2\[dq]
@@ -47286,7 +47881,7 @@ Las Vegas
 \[dq]northamerica-northeast1\[dq]
 .RS 2
 .IP \[bu] 2
-Montr\['e]al
+Montréal
 .RE
 .IP \[bu] 2
 \[dq]northamerica-northeast2\[dq]
@@ -47298,7 +47893,7 @@ Toronto
 \[dq]southamerica-east1\[dq]
 .RS 2
 .IP \[bu] 2
-S\[~a]o Paulo
+São Paulo
 .RE
 .IP \[bu] 2
 \[dq]southamerica-west1\[dq]
@@ -47565,10 +48160,10 @@ Type: string
 Required: false
 .SS Limitations
 .PP
-\f[C]rclone about\f[R] is not supported by the Google Cloud Storage
+\f[V]rclone about\f[R] is not supported by the Google Cloud Storage
 backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -47576,17 +48171,17 @@ about (https://rclone.org/overview/#optional-features) and rclone
 about (https://rclone.org/commands/rclone_about/)
 .SH Google Drive
 .PP
-Paths are specified as \f[C]drive:path\f[R]
+Paths are specified as \f[V]drive:path\f[R]
 .PP
 Drive paths may be as deep as required, e.g.
-\f[C]drive:directory/subdirectory\f[R].
+\f[V]drive:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 The initial setup for drive involves getting a token from Google drive
 which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -47678,7 +48273,7 @@ token as returned from Google if using web browser to automatically
 authenticate.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and it may require you to
+This is on \f[V]http://127.0.0.1:53682/\f[R] and it may require you to
 unblock it temporarily if you are running a host firewall, or use manual
 mode.
 .PP
@@ -47716,7 +48311,7 @@ The scopes are defined
 here (https://developers.google.com/drive/v3/web/about-auth).
 .PP
 A comma-separated list is allowed e.g.
-\f[C]drive.readonly,drive.file\f[R].
+\f[V]drive.readonly,drive.file\f[R].
 .PP
 The scope are
 .SS drive
@@ -47755,8 +48350,8 @@ files or directories.
 .SS Root folder ID
 .PP
 This option has been moved to the advanced section.
-You can set the \f[C]root_folder_id\f[R] for rclone.
-This is the directory (identified by its \f[C]Folder ID\f[R]) that
+You can set the \f[V]root_folder_id\f[R] for rclone.
+This is the directory (identified by its \f[V]Folder ID\f[R]) that
 rclone considers to be the root of your drive.
 .PP
 Normally you will leave this blank and rclone will determine the correct
@@ -47767,15 +48362,15 @@ hierarchy or to access data within the \[dq]Computers\[dq] tab on the
 drive web interface (where files from Google\[aq]s Backup and Sync
 desktop program go).
 .PP
-In order to do this you will have to find the \f[C]Folder ID\f[R] of the
+In order to do this you will have to find the \f[V]Folder ID\f[R] of the
 directory you wish rclone to display.
 This will be the last segment of the URL when you open the relevant
 folder in the drive web interface.
 .PP
 So if the folder you want rclone to use has a URL which looks like
-\f[C]https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh\f[R]
-in the browser, then you use \f[C]1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh\f[R]
-as the \f[C]root_folder_id\f[R] in the config.
+\f[V]https://drive.google.com/drive/folders/1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh\f[R]
+in the browser, then you use \f[V]1XyfxxxxxxxxxxxxxxxxxxxxxxxxxKHCh\f[R]
+as the \f[V]root_folder_id\f[R] in the config.
 .PP
 \f[B]NB\f[R] folders under the \[dq]Computers\[dq] tab seem to be read
 only (drive gives a 500 error) when using rclone.
@@ -47793,11 +48388,11 @@ This is useful when you want to synchronise files onto machines that
 don\[aq]t have actively logged-in users, for example build machines.
 .PP
 To use a Service Account instead of OAuth2 token flow, enter the path to
-your Service Account credentials at the \f[C]service_account_file\f[R]
-prompt during \f[C]rclone config\f[R] and rclone won\[aq]t use the
+your Service Account credentials at the \f[V]service_account_file\f[R]
+prompt during \f[V]rclone config\f[R] and rclone won\[aq]t use the
 browser based authentication flow.
 If you\[aq]d rather stuff the contents of the credentials file into the
-rclone config file, you can set \f[C]service_account_credentials\f[R]
+rclone config file, you can set \f[V]service_account_credentials\f[R]
 with the actual contents of the file instead, or set the equivalent
 environment variable.
 .SS Use case - Google Workspace account and individual Drive
@@ -47858,10 +48453,10 @@ Client ID\[dq] for the newly created service account.
 It is a \[ti]21 character numerical string.
 .IP \[bu] 2
 In the next field, \[dq]OAuth Scopes\[dq], enter
-\f[C]https://www.googleapis.com/auth/drive\f[R] to grant read/write
+\f[V]https://www.googleapis.com/auth/drive\f[R] to grant read/write
 access to Google Drive specifically.
 You can also use
-\f[C]https://www.googleapis.com/auth/drive.readonly\f[R] for read only
+\f[V]https://www.googleapis.com/auth/drive.readonly\f[R] for read only
 access.
 .IP \[bu] 2
 Click \[dq]Authorise\[dq]
@@ -47884,34 +48479,34 @@ y/n>             # Auto config, n
 .fi
 .SS 4. Verify that it\[aq]s working
 .IP \[bu] 2
-\f[C]rclone -v --drive-impersonate foo\[at]example.com lsf gdrive:backup\f[R]
+\f[V]rclone -v --drive-impersonate foo\[at]example.com lsf gdrive:backup\f[R]
 .IP \[bu] 2
 The arguments do:
 .RS 2
 .IP \[bu] 2
-\f[C]-v\f[R] - verbose logging
+\f[V]-v\f[R] - verbose logging
 .IP \[bu] 2
-\f[C]--drive-impersonate foo\[at]example.com\f[R] - this is what does
+\f[V]--drive-impersonate foo\[at]example.com\f[R] - this is what does
 the magic, pretending to be user foo.
 .IP \[bu] 2
-\f[C]lsf\f[R] - list files in a parsing friendly way
+\f[V]lsf\f[R] - list files in a parsing friendly way
 .IP \[bu] 2
-\f[C]gdrive:backup\f[R] - use the remote called gdrive, work in the
+\f[V]gdrive:backup\f[R] - use the remote called gdrive, work in the
 folder named backup.
 .RE
 .PP
 Note: in case you configured a specific root folder on gdrive and rclone
 is unable to access the contents of that folder when using
-\f[C]--drive-impersonate\f[R], do this instead: - in the gdrive web
+\f[V]--drive-impersonate\f[R], do this instead: - in the gdrive web
 interface, share your root folder with the user/email of the new Service
 Account you created/selected at step 1 - use rclone without specifying
-the \f[C]--drive-impersonate\f[R] option, like this:
-\f[C]rclone -v lsf gdrive:backup\f[R]
+the \f[V]--drive-impersonate\f[R] option, like this:
+\f[V]rclone -v lsf gdrive:backup\f[R]
 .SS Shared drives (team drives)
 .PP
 If you want to configure the remote to point to a Google Shared Drive
-(previously known as Team Drives) then answer \f[C]y\f[R] to the
-question \f[C]Configure this as a Shared Drive (Team Drive)?\f[R].
+(previously known as Team Drives) then answer \f[V]y\f[R] to the
+question \f[V]Configure this as a Shared Drive (Team Drive)?\f[R].
 .PP
 This will fetch the list of Shared Drives from google and allow you to
 configure which one you want to use.
@@ -47950,18 +48545,18 @@ y/e/d> y
 .fi
 .SS --fast-list
 .PP
-This remote supports \f[C]--fast-list\f[R] which allows you to use fewer
+This remote supports \f[V]--fast-list\f[R] which allows you to use fewer
 transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
 .PP
-It does this by combining multiple \f[C]list\f[R] calls into a single
+It does this by combining multiple \f[V]list\f[R] calls into a single
 API request.
 .PP
-This works by combining many \f[C]\[aq]%s\[aq] in parents\f[R] filters
+This works by combining many \f[V]\[aq]%s\[aq] in parents\f[R] filters
 into one expression.
 To list the contents of directories a, b and c, the following requests
-will be send by the regular \f[C]List\f[R] function:
+will be send by the regular \f[V]List\f[R] function:
 .IP
 .nf
 \f[C]
@@ -47979,9 +48574,9 @@ trashed=false and (\[aq]a\[aq] in parents or \[aq]b\[aq] in parents or \[aq]c\[a
 \f[R]
 .fi
 .PP
-The implementation of \f[C]ListR\f[R] will put up to 50
-\f[C]parents\f[R] filters into one request.
-It will use the \f[C]--checkers\f[R] value to specify the number of
+The implementation of \f[V]ListR\f[R] will put up to 50
+\f[V]parents\f[R] filters into one request.
+It will use the \f[V]--checkers\f[R] value to specify the number of
 requests to run in parallel.
 .PP
 In tests, these batch requests were up to 20x faster than the regular
@@ -47996,15 +48591,15 @@ rclone lsjson -vv -R --checkers=6 gdrive:folder
 .PP
 small folder (220 directories, 700 files):
 .IP \[bu] 2
-without \f[C]--fast-list\f[R]: 38s
+without \f[V]--fast-list\f[R]: 38s
 .IP \[bu] 2
-with \f[C]--fast-list\f[R]: 10s
+with \f[V]--fast-list\f[R]: 10s
 .PP
 large folder (10600 directories, 39000 files):
 .IP \[bu] 2
-without \f[C]--fast-list\f[R]: 22:05 min
+without \f[V]--fast-list\f[R]: 22:05 min
 .IP \[bu] 2
-with \f[C]--fast-list\f[R]: 58s
+with \f[V]--fast-list\f[R]: 58s
 .SS Modification times and hashes
 .PP
 Google drive stores modification times accurate to 1 ms.
@@ -48018,8 +48613,8 @@ Only Invalid UTF-8 bytes will be
 replaced (https://rclone.org/overview/#invalid-utf8), as they can\[aq]t
 be used in JSON strings.
 .PP
-In contrast to other backends, \f[C]/\f[R] can also be used in names and
-\f[C].\f[R] or \f[C]..\f[R] are valid names.
+In contrast to other backends, \f[V]/\f[R] can also be used in names and
+\f[V].\f[R] or \f[V]..\f[R] are valid names.
 .SS Revisions
 .PP
 Google drive stores revisions of files.
@@ -48035,7 +48630,7 @@ They do not count towards a user storage quota.
 .PP
 By default rclone will send all files to the trash when deleting files.
 If deleting them permanently is required then use the
-\f[C]--drive-use-trash=false\f[R] flag, or set the equivalent
+\f[V]--drive-use-trash=false\f[R] flag, or set the equivalent
 environment variable.
 .SS Shortcuts
 .PP
@@ -48068,7 +48663,7 @@ destination file.
 .IP \[bu] 2
 When server-side copying the shortcut is copied, not the contents of the
 shortcut.
-(unless \f[C]--drive-copy-shortcut-content\f[R] is in use in which case
+(unless \f[V]--drive-copy-shortcut-content\f[R] is in use in which case
 the contents of the shortcut gets copied).
 .IP \[bu] 2
 When deleting the shortcut is deleted not the linked file.
@@ -48094,28 +48689,28 @@ destination folder
 When server-side copying the contents of the linked folder is copied,
 not the shortcut.
 .IP \[bu] 2
-When deleting with \f[C]rclone rmdir\f[R] or \f[C]rclone purge\f[R] the
+When deleting with \f[V]rclone rmdir\f[R] or \f[V]rclone purge\f[R] the
 shortcut is deleted not the linked folder.
 .IP \[bu] 2
-\f[B]NB\f[R] When deleting with \f[C]rclone remove\f[R] or
-\f[C]rclone mount\f[R] the contents of the linked folder will be
+\f[B]NB\f[R] When deleting with \f[V]rclone remove\f[R] or
+\f[V]rclone mount\f[R] the contents of the linked folder will be
 deleted.
 .PP
 The rclone backend (https://rclone.org/commands/rclone_backend/) command
 can be used to create shortcuts.
 .PP
 Shortcuts can be completely ignored with the
-\f[C]--drive-skip-shortcuts\f[R] flag or the corresponding
-\f[C]skip_shortcuts\f[R] configuration setting.
+\f[V]--drive-skip-shortcuts\f[R] flag or the corresponding
+\f[V]skip_shortcuts\f[R] configuration setting.
 .PP
 If you have shortcuts that lead to an infinite recursion in your drive
 (e.g.
-a shortcut pointing to a parent folder), \f[C]skip_shortcuts\f[R] might
+a shortcut pointing to a parent folder), \f[V]skip_shortcuts\f[R] might
 be mandatory to be able to copy the drive.
 .SS Emptying trash
 .PP
 If you wish to empty your trash you can use the
-\f[C]rclone cleanup remote:\f[R] command which will permanently delete
+\f[V]rclone cleanup remote:\f[R] command which will permanently delete
 all your trashed files.
 This command does not take any path arguments.
 .PP
@@ -48126,7 +48721,7 @@ No output is echoed, so there will be no confirmation even using -v or
 .SS Quota information
 .PP
 To view your current quota you can use the
-\f[C]rclone about remote:\f[R] command which will display your usage
+\f[V]rclone about remote:\f[R] command which will display your usage
 limit (quota), the usage in Google Drive, the size of all files in the
 Trash and the space used by other Google services such as Gmail.
 This command does not take any path arguments.
@@ -48135,8 +48730,8 @@ This command does not take any path arguments.
 Google documents can be exported from and uploaded to Google Drive.
 .PP
 When rclone downloads a Google doc it chooses a format to download
-depending upon the \f[C]--drive-export-formats\f[R] setting.
-By default the export formats are \f[C]docx,xlsx,pptx,svg\f[R] which are
+depending upon the \f[V]--drive-export-formats\f[R] setting.
+By default the export formats are \f[V]docx,xlsx,pptx,svg\f[R] which are
 a sensible default for an editable document.
 .PP
 When choosing a format, rclone runs down the list provided in order and
@@ -48145,29 +48740,29 @@ If the file can\[aq]t be exported to a format on the formats list, then
 rclone will choose a format from the default list.
 .PP
 If you prefer an archive copy then you might use
-\f[C]--drive-export-formats pdf\f[R], or if you prefer
+\f[V]--drive-export-formats pdf\f[R], or if you prefer
 openoffice/libreoffice formats you might use
-\f[C]--drive-export-formats ods,odt,odp\f[R].
+\f[V]--drive-export-formats ods,odt,odp\f[R].
 .PP
 Note that rclone adds the extension to the google doc, so if it is
-called \f[C]My Spreadsheet\f[R] on google docs, it will be exported as
-\f[C]My Spreadsheet.xlsx\f[R] or \f[C]My Spreadsheet.pdf\f[R] etc.
+called \f[V]My Spreadsheet\f[R] on google docs, it will be exported as
+\f[V]My Spreadsheet.xlsx\f[R] or \f[V]My Spreadsheet.pdf\f[R] etc.
 .PP
 When importing files into Google Drive, rclone will convert all files
-with an extension in \f[C]--drive-import-formats\f[R] to their
+with an extension in \f[V]--drive-import-formats\f[R] to their
 associated document type.
 rclone will not convert any files by default, since the conversion is
 lossy process.
 .PP
 The conversion must result in a file with the same extension when the
-\f[C]--drive-export-formats\f[R] rules are applied to the uploaded
+\f[V]--drive-export-formats\f[R] rules are applied to the uploaded
 document.
 .PP
 Here are some examples for allowed and prohibited conversions.
 .PP
 .TS
 tab(@);
-l l l l l.
+lw(17.2n) lw(17.2n) lw(12.3n) lw(14.7n) lw(8.6n).
 T{
 export-formats
 T}@T{
@@ -48258,10 +48853,10 @@ T}
 .TE
 .PP
 This limitation can be disabled by specifying
-\f[C]--drive-allow-import-name-change\f[R].
+\f[V]--drive-allow-import-name-change\f[R].
 When using this flag, rclone can convert multiple files types resulting
 in the same document type at once, e.g.
-with \f[C]--drive-import-formats docx,odt,txt\f[R], all files having
+with \f[V]--drive-import-formats docx,odt,txt\f[R], all files having
 these extension would result in a document represented as a docx file.
 This brings the additional risk of overwriting a document, if multiple
 files have the same stem.
@@ -48464,7 +49059,7 @@ Google documents can also be exported as link files.
 These files will open a browser window for the Google Docs website of
 that document when opened.
 The link file extension has to be specified as a
-\f[C]--drive-export-formats\f[R] parameter.
+\f[V]--drive-export-formats\f[R] parameter.
 They will match all available Google Documents.
 .PP
 .TS
@@ -48605,8 +49200,8 @@ Service Account Credentials JSON file path.
 Leave blank normally.
 Needed only if you want use SA instead of interactive login.
 .PP
-Leading \f[C]\[ti]\f[R] will be expanded in the file name as will
-environment variables such as \f[C]${RCLONE_CONFIG_DIR}\f[R].
+Leading \f[V]\[ti]\f[R] will be expanded in the file name as will
+environment variables such as \f[V]${RCLONE_CONFIG_DIR}\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -48740,7 +49335,7 @@ Default: false
 Send files to the trash instead of deleting permanently.
 .PP
 Defaults to true, namely sending files to the trash.
-Use \f[C]--drive-use-trash=false\f[R] to delete files permanently
+Use \f[V]--drive-use-trash=false\f[R] to delete files permanently
 instead.
 .PP
 Properties:
@@ -48848,9 +49443,9 @@ Instructs rclone to operate on your \[dq]Shared with me\[dq] folder
 (where Google Drive lets you access the files and folders others have
 shared with you).
 .PP
-This works both with the \[dq]list\[dq] (lsd, lsl, etc.) and the
-\[dq]copy\[dq] commands (copy, sync, etc.), and with all other commands
-too.
+This works both with the \[dq]list\[dq] (lsd, lsl, etc.)
+and the \[dq]copy\[dq] commands (copy, sync, etc.), and with all other
+commands too.
 .PP
 Properties:
 .IP \[bu] 2
@@ -50085,27 +50680,27 @@ lots of small files can take a long time.
 Server side copies are also subject to a separate rate limit.
 If you see User rate limit exceeded errors, wait at least 24 hours and
 retry.
-You can disable server-side copies with \f[C]--disable copy\f[R] to
+You can disable server-side copies with \f[V]--disable copy\f[R] to
 download and upload the files if you prefer.
 .SS Limitations of Google Docs
 .PP
-Google docs will appear as size -1 in \f[C]rclone ls\f[R],
-\f[C]rclone ncdu\f[R] etc, and as size 0 in anything which uses the VFS
+Google docs will appear as size -1 in \f[V]rclone ls\f[R],
+\f[V]rclone ncdu\f[R] etc, and as size 0 in anything which uses the VFS
 layer, e.g.
-\f[C]rclone mount\f[R] and \f[C]rclone serve\f[R].
+\f[V]rclone mount\f[R] and \f[V]rclone serve\f[R].
 When calculating directory totals, e.g.
-in \f[C]rclone size\f[R] and \f[C]rclone ncdu\f[R], they will be counted
+in \f[V]rclone size\f[R] and \f[V]rclone ncdu\f[R], they will be counted
 in as empty files.
 .PP
 This is because rclone can\[aq]t find out the size of the Google docs
 without downloading them.
 .PP
-Google docs will transfer correctly with \f[C]rclone sync\f[R],
-\f[C]rclone copy\f[R] etc as rclone knows to ignore the size when doing
+Google docs will transfer correctly with \f[V]rclone sync\f[R],
+\f[V]rclone copy\f[R] etc as rclone knows to ignore the size when doing
 the transfer.
 .PP
 However an unfortunate consequence of this is that you may not be able
-to download Google docs using \f[C]rclone mount\f[R].
+to download Google docs using \f[V]rclone mount\f[R].
 If it doesn\[aq]t work you will get a 0 sized file.
 If you try again the doc may gain its correct size and be downloadable.
 Whether it will work on not depends on the application accessing the
@@ -50120,14 +50715,14 @@ Drive unlike all the other remotes can have duplicated files.
 Duplicated files cause problems with the syncing and you will see
 messages in the log about duplicates.
 .PP
-Use \f[C]rclone dedupe\f[R] to fix duplicated files.
+Use \f[V]rclone dedupe\f[R] to fix duplicated files.
 .PP
 Note that this isn\[aq]t just a problem with rclone, even Google Photos
 on Android duplicates files on drive sometimes.
 .SS Rclone appears to be re-copying files it shouldn\[aq]t
 .PP
 The most likely cause of this is the duplicated file issue above - run
-\f[C]rclone dedupe\f[R] and check your logs for duplicate object or
+\f[V]rclone dedupe\f[R] and check your logs for duplicate object or
 directory messages.
 .PP
 This can also be caused by a delay/caching on google drive\[aq]s end
@@ -50189,16 +50784,16 @@ You will also have to add some
 scopes (https://developers.google.com/drive/api/guides/api-specific-auth),
 including
 .IP \[bu] 2
-\f[C]https://www.googleapis.com/auth/docs\f[R]
+\f[V]https://www.googleapis.com/auth/docs\f[R]
 .IP \[bu] 2
-\f[C]https://www.googleapis.com/auth/drive\f[R] in order to be able to
+\f[V]https://www.googleapis.com/auth/drive\f[R] in order to be able to
 edit, create and delete files with RClone.
 .IP \[bu] 2
-\f[C]https://www.googleapis.com/auth/drive.metadata.readonly\f[R] which
+\f[V]https://www.googleapis.com/auth/drive.metadata.readonly\f[R] which
 you may also want to add.
 .IP \[bu] 2
 If you want to add all at once, comma separated it would be
-\f[C]https://www.googleapis.com/auth/docs,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.metadata.readonly\f[R].
+\f[V]https://www.googleapis.com/auth/docs,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/drive.metadata.readonly\f[R].
 .IP " 6." 4
 After adding scopes, click \[dq]Save and continue\[dq] to add test
 users.
@@ -50238,12 +50833,12 @@ Provide the noted client ID and client secret to rclone.
 .PP
 Be aware that, due to the \[dq]enhanced security\[dq] recently
 introduced by Google, you are theoretically expected to \[dq]submit your
-app for verification\[dq] and then wait a few weeks(!) for their
-response; in practice, you can go right ahead and use the client ID and
-client secret with rclone, the only issue will be a very scary
-confirmation screen shown when you connect via your browser for rclone
-to be able to get its token-id (but as this only happens during the
-remote configuration, it\[aq]s not such a big deal).
+app for verification\[dq] and then wait a few weeks(!)
+for their response; in practice, you can go right ahead and use the
+client ID and client secret with rclone, the only issue will be a very
+scary confirmation screen shown when you connect via your browser for
+rclone to be able to get its token-id (but as this only happens during
+the remote configuration, it\[aq]s not such a big deal).
 Keeping the application in \[dq]Testing\[dq] will work as well, but the
 limitation is that any grants will expire after a week, which can be
 annoying to refresh constantly.
@@ -50275,9 +50870,9 @@ sure it is suitable for your use.
 .PP
 The initial setup for google cloud storage involves getting a token from
 Google Photos which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -50361,11 +50956,11 @@ token as returned from Google if using web browser to automatically
 authenticate.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this may require you to
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this may require you to
 unblock it temporarily if you are running a host firewall, or use manual
 mode.
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this
+This remote is called \f[V]remote\f[R] and can now be used like this
 .PP
 See all the albums in your photos
 .IP
@@ -50391,7 +50986,7 @@ rclone ls remote:album/newAlbum
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/images\f[R] to the Google Photos, removing any
+Sync \f[V]/home/local/images\f[R] to the Google Photos, removing any
 excess files in the album.
 .IP
 .nf
@@ -50404,16 +50999,16 @@ rclone sync --interactive /home/local/image remote:album/newAlbum
 As Google Photos is not a general purpose cloud storage system, the
 backend is laid out to help you navigate it.
 .PP
-The directories under \f[C]media\f[R] show different ways of
+The directories under \f[V]media\f[R] show different ways of
 categorizing the media.
 Each file will appear multiple times.
 So if you want to make a backup of your google photos you might choose
-to backup \f[C]remote:media/by-month\f[R].
-(\f[B]NB\f[R] \f[C]remote:media/by-day\f[R] is rather slow at the moment
+to backup \f[V]remote:media/by-month\f[R].
+(\f[B]NB\f[R] \f[V]remote:media/by-day\f[R] is rather slow at the moment
 so avoid for syncing.)
 .PP
 Note that all your photos and videos will appear somewhere under
-\f[C]media\f[R], but they may not appear under \f[C]album\f[R] unless
+\f[V]media\f[R], but they may not appear under \f[V]album\f[R] unless
 you\[aq]ve put them into albums.
 .IP
 .nf
@@ -50467,22 +51062,22 @@ you\[aq]ve put them into albums.
 \f[R]
 .fi
 .PP
-There are two writable parts of the tree, the \f[C]upload\f[R] directory
-and sub directories of the \f[C]album\f[R] directory.
+There are two writable parts of the tree, the \f[V]upload\f[R] directory
+and sub directories of the \f[V]album\f[R] directory.
 .PP
-The \f[C]upload\f[R] directory is for uploading files you don\[aq]t want
+The \f[V]upload\f[R] directory is for uploading files you don\[aq]t want
 to put into albums.
 This will be empty to start with and will contain the files you\[aq]ve
 uploaded for one rclone session only, becoming empty again when you
 restart rclone.
 The use case for this would be if you have a load of files you just want
 to once off dump into Google Photos.
-For repeated syncing, uploading to \f[C]album\f[R] will work better.
+For repeated syncing, uploading to \f[V]album\f[R] will work better.
 .PP
-Directories within the \f[C]album\f[R] directory are also writeable and
-you may create new directories (albums) under \f[C]album\f[R].
+Directories within the \f[V]album\f[R] directory are also writeable and
+you may create new directories (albums) under \f[V]album\f[R].
 If you copy files with a directory hierarchy in there then rclone will
-create albums with the \f[C]/\f[R] character in them.
+create albums with the \f[V]/\f[R] character in them.
 For example if you do
 .IP
 .nf
@@ -50525,10 +51120,10 @@ images/dir2/dir3
 file3.jpg
 .RE
 .PP
-This means that you can use the \f[C]album\f[R] path pretty much like a
+This means that you can use the \f[V]album\f[R] path pretty much like a
 normal filesystem and it is a good target for repeated syncing.
 .PP
-The \f[C]shared-album\f[R] directory shows albums shared with you or by
+The \f[V]shared-album\f[R] directory shows albums shared with you or by
 you.
 This is similar to the Sharing tab in the Google Photos web interface.
 .SS Standard options
@@ -50824,9 +51419,9 @@ stored in full resolution at \[dq]original quality\[dq] and
 The API does \f[B]not\f[R] offer a way to upload in \[dq]high
 quality\[dq] mode..
 .PP
-\f[C]rclone about\f[R] is not supported by the Google Photos backend.
+\f[V]rclone about\f[R] is not supported by the Google Photos backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -50840,11 +51435,12 @@ This is a limitation of the Google Photos API and is covered by bug
 #112096115 (https://issuetracker.google.com/issues/112096115).
 .PP
 \f[B]The current google API does not allow photos to be downloaded at
-original resolution. This is very important if you are, for example,
-relying on \[dq]Google Photos\[dq] as a backup of your photos. You will
-not be able to use rclone to redownload original images. You could use
-\[aq]google takeout\[aq] to recover the original photos as a last
-resort\f[R]
+original resolution.
+This is very important if you are, for example, relying on \[dq]Google
+Photos\[dq] as a backup of your photos.
+You will not be able to use rclone to redownload original images.
+You could use \[aq]google takeout\[aq] to recover the original photos as
+a last resort\f[R]
 .SS Downloading Videos
 .PP
 When videos are downloaded they are downloaded in a really compressed
@@ -50856,18 +51452,18 @@ This is covered by bug
 .PP
 If a file name is duplicated in a directory then rclone will add the
 file ID into its name.
-So two files called \f[C]file.jpg\f[R] would then appear as
-\f[C]file {123456}.jpg\f[R] and \f[C]file {ABCDEF}.jpg\f[R] (the actual
+So two files called \f[V]file.jpg\f[R] would then appear as
+\f[V]file {123456}.jpg\f[R] and \f[V]file {ABCDEF}.jpg\f[R] (the actual
 IDs are a lot longer alas!).
 .PP
 If you upload the same image (with the same binary data) twice then
 Google Photos will deduplicate it.
 However it will retain the filename from the first upload which may
 confuse rclone.
-For example if you uploaded an image to \f[C]upload\f[R] then uploaded
-the same image to \f[C]album/my_album\f[R] the filename of the image in
-\f[C]album/my_album\f[R] will be what it was uploaded with initially,
-not what you uploaded it with to \f[C]album\f[R].
+For example if you uploaded an image to \f[V]upload\f[R] then uploaded
+the same image to \f[V]album/my_album\f[R] the filename of the image in
+\f[V]album/my_album\f[R] will be what it was uploaded with initially,
+not what you uploaded it with to \f[V]album\f[R].
 In practise this shouldn\[aq]t cause too many problems.
 .SS Modification times
 .PP
@@ -50888,10 +51484,10 @@ existence check.
 It is possible to read the size of the media, but this needs an extra
 HTTP HEAD request per media item so is \f[B]very slow\f[R] and uses up a
 lot of transactions.
-This can be enabled with the \f[C]--gphotos-read-size\f[R] option or the
-\f[C]read_size = true\f[R] config parameter.
+This can be enabled with the \f[V]--gphotos-read-size\f[R] option or the
+\f[V]read_size = true\f[R] config parameter.
 .PP
-If you want to use the backend with \f[C]rclone mount\f[R] you may need
+If you want to use the backend with \f[V]rclone mount\f[R] you may need
 to enable this flag (depending on your OS and application using the
 photos) otherwise you may not be able to read media off the mount.
 You\[aq]ll need to experiment to see if it works for you without the
@@ -50910,7 +51506,7 @@ Photos API does not allow media to be deleted permanently so this media
 will still remain.
 See bug #109759781 (https://issuetracker.google.com/issues/109759781).
 .PP
-Rclone cannot delete files anywhere except under \f[C]album\f[R].
+Rclone cannot delete files anywhere except under \f[V]album\f[R].
 .SS Deleting albums
 .PP
 The Google Photos API does not support deleting albums - see bug
@@ -50929,16 +51525,16 @@ configuration instructions for that remote.
 You can also use a local pathname instead of a remote.
 Check that your base remote is working.
 .PP
-Let\[aq]s call the base remote \f[C]myRemote:path\f[R] here.
-Note that anything inside \f[C]myRemote:path\f[R] will be handled by
+Let\[aq]s call the base remote \f[V]myRemote:path\f[R] here.
+Note that anything inside \f[V]myRemote:path\f[R] will be handled by
 hasher and anything outside won\[aq]t.
 This means that if you are using a bucket based remote (S3, B2, Swift)
-then you should put the bucket in the remote \f[C]s3:bucket\f[R].
+then you should put the bucket in the remote \f[V]s3:bucket\f[R].
 .PP
 Now proceed to interactive or manual configuration.
 .SS Interactive configuration
 .PP
-Run \f[C]rclone config\f[R]:
+Run \f[V]rclone config\f[R]:
 .IP
 .nf
 \f[C]
@@ -50983,8 +51579,8 @@ y/e/d> y
 .fi
 .SS Manual configuration
 .PP
-Run \f[C]rclone config path\f[R] to see the path of current active
-config file, usually \f[C]YOURHOME/.config/rclone/rclone.conf\f[R].
+Run \f[V]rclone config path\f[R] to see the path of current active
+config file, usually \f[V]YOURHOME/.config/rclone/rclone.conf\f[R].
 Open it in your favorite text editor, find section for the base remote
 and create new section for hasher like in the following examples:
 .IP
@@ -51004,25 +51600,25 @@ max_age = 24h
 \f[R]
 .fi
 .PP
-Hasher takes basically the following parameters: - \f[C]remote\f[R] is
-required, - \f[C]hashes\f[R] is a comma separated list of supported
-checksums (by default \f[C]md5,sha1\f[R]), - \f[C]max_age\f[R] - maximum
-time to keep a checksum value in the cache, \f[C]0\f[R] will disable
-caching completely, \f[C]off\f[R] will cache \[dq]forever\[dq] (that is
+Hasher takes basically the following parameters: - \f[V]remote\f[R] is
+required, - \f[V]hashes\f[R] is a comma separated list of supported
+checksums (by default \f[V]md5,sha1\f[R]), - \f[V]max_age\f[R] - maximum
+time to keep a checksum value in the cache, \f[V]0\f[R] will disable
+caching completely, \f[V]off\f[R] will cache \[dq]forever\[dq] (that is
 until the files get changed).
 .PP
-Make sure the \f[C]remote\f[R] has \f[C]:\f[R] (colon) in.
+Make sure the \f[V]remote\f[R] has \f[V]:\f[R] (colon) in.
 If you specify the remote without a colon then rclone will use a local
 directory of that name.
-So if you use a remote of \f[C]/local/path\f[R] then rclone will handle
+So if you use a remote of \f[V]/local/path\f[R] then rclone will handle
 hashes for that directory.
-If you use \f[C]remote = name\f[R] literally then rclone will put files
-\f[B]in a directory called \f[CB]name\f[B] located under current
+If you use \f[V]remote = name\f[R] literally then rclone will put files
+\f[B]in a directory called \f[VB]name\f[B] located under current
 directory\f[R].
 .SS Usage
 .SS Basic operations
 .PP
-Now you can use it as \f[C]Hasher2:subdir/file\f[R] instead of base
+Now you can use it as \f[V]Hasher2:subdir/file\f[R] instead of base
 remote.
 Hasher will transparently update cache with new checksums when a file is
 fully read or overwritten, like:
@@ -51038,7 +51634,7 @@ rclone cat Hasher:path/to/file > /dev/null
 The way to refresh \f[B]all\f[R] cached checksums (even unsupported by
 the base backend) for a subtree is to \f[B]re-download\f[R] all files in
 the subtree.
-For example, use \f[C]hashsum --download\f[R] using \f[B]any\f[R]
+For example, use \f[V]hashsum --download\f[R] using \f[B]any\f[R]
 supported hashsum on the command line (we just care to re-read):
 .IP
 .nf
@@ -51060,8 +51656,8 @@ rclone backend drop Hasher:
 .fi
 .SS Pre-Seed from a SUM File
 .PP
-Hasher supports two backend commands: generic SUM file \f[C]import\f[R]
-and faster but less consistent \f[C]stickyimport\f[R].
+Hasher supports two backend commands: generic SUM file \f[V]import\f[R]
+and faster but less consistent \f[V]stickyimport\f[R].
 .IP
 .nf
 \f[C]
@@ -51071,12 +51667,12 @@ rclone backend import Hasher:dir/subdir SHA1 /path/to/SHA1SUM [--checkers 4]
 .PP
 Instead of SHA1 it can be any hash supported by the remote.
 The last argument can point to either a local or an
-\f[C]other-remote:path\f[R] text file in SUM format.
+\f[V]other-remote:path\f[R] text file in SUM format.
 The command will parse the SUM file, then walk down the path given by
 the first argument, snapshot current fingerprints and fill in the cache
 entries correspondingly.
 - Paths in the SUM file are treated as relative to
-\f[C]hasher:dir/subdir\f[R].
+\f[V]hasher:dir/subdir\f[R].
 - The command will \f[B]not\f[R] check that supplied values are correct.
 You \f[B]must know\f[R] what you are doing.
 - This is a one-time action.
@@ -51084,8 +51680,8 @@ The SUM file will not get \[dq]attached\[dq] to the remote.
 Cache entries can still be overwritten later, should the object\[aq]s
 fingerprint change.
 - The tree walk can take long depending on the tree size.
-You can increase \f[C]--checkers\f[R] to make it faster.
-Or use \f[C]stickyimport\f[R] if you don\[aq]t care about fingerprints
+You can increase \f[V]--checkers\f[R] to make it faster.
+Or use \f[V]stickyimport\f[R] if you don\[aq]t care about fingerprints
 and consistency.
 .IP
 .nf
@@ -51094,14 +51690,14 @@ rclone backend stickyimport hasher:path/to/data sha1 remote:/path/to/sum.sha1
 \f[R]
 .fi
 .PP
-\f[C]stickyimport\f[R] is similar to \f[C]import\f[R] but works much
+\f[V]stickyimport\f[R] is similar to \f[V]import\f[R] but works much
 faster because it does not need to stat existing files and skips initial
 tree walk.
 Instead of binding cache entries to file fingerprints it creates
 \f[I]sticky\f[R] entries bound to the file name alone ignoring size,
 modification time etc.
-Such hash entries can be replaced only by \f[C]purge\f[R],
-\f[C]delete\f[R], \f[C]backend drop\f[R] or by full re-read/re-write of
+Such hash entries can be replaced only by \f[V]purge\f[R],
+\f[V]delete\f[R], \f[V]backend drop\f[R] or by full re-read/re-write of
 the files.
 .SS Configuration reference
 .SS Standard options
@@ -51269,20 +51865,21 @@ remote:path/to/sum.md5
 This section explains how various rclone operations work on a hasher
 remote.
 .PP
-\f[B]Disclaimer. This section describes current implementation which can
-change in future rclone versions!.\f[R]
+\f[B]Disclaimer.
+This section describes current implementation which can change in future
+rclone versions!.\f[R]
 .SS Hashsum command
 .PP
-The \f[C]rclone hashsum\f[R] (or \f[C]md5sum\f[R] or \f[C]sha1sum\f[R])
+The \f[V]rclone hashsum\f[R] (or \f[V]md5sum\f[R] or \f[V]sha1sum\f[R])
 command will:
 .IP "1." 3
 if requested hash is supported by lower level, just pass it.
 .IP "2." 3
-if object size is below \f[C]auto_size\f[R] then download object and
+if object size is below \f[V]auto_size\f[R] then download object and
 calculate \f[I]requested\f[R] hashes on the fly.
 .IP "3." 3
 if unsupported and the size is big enough, build object
-\f[C]fingerprint\f[R] (including size, modtime if supported, first-found
+\f[V]fingerprint\f[R] (including size, modtime if supported, first-found
 \f[I]other\f[R] hash if any).
 .IP "4." 3
 if the strict match is found in cache for the requested remote, return
@@ -51297,33 +51894,33 @@ store in cache; return requested hash.
 .SS Other operations
 .IP \[bu] 2
 any time a hash is requested, follow the logic from 1-4 from
-\f[C]hashsum\f[R] above
+\f[V]hashsum\f[R] above
 .IP \[bu] 2
 whenever a file is uploaded or downloaded \f[B]in full\f[R], capture the
 stream to calculate all supported hashes on the fly and update database
 .IP \[bu] 2
-server-side \f[C]move\f[R] will update keys of existing cache entries
+server-side \f[V]move\f[R] will update keys of existing cache entries
 .IP \[bu] 2
-\f[C]deletefile\f[R] will remove a single cache entry
+\f[V]deletefile\f[R] will remove a single cache entry
 .IP \[bu] 2
-\f[C]purge\f[R] will remove all cache entries under the purged path
+\f[V]purge\f[R] will remove all cache entries under the purged path
 .PP
-Note that setting \f[C]max_age = 0\f[R] will disable checksum caching
+Note that setting \f[V]max_age = 0\f[R] will disable checksum caching
 completely.
 .PP
-If you set \f[C]max_age = off\f[R], checksums in cache will never age,
+If you set \f[V]max_age = off\f[R], checksums in cache will never age,
 unless you fully rewrite or delete the file.
 .SS Cache storage
 .PP
-Cached checksums are stored as \f[C]bolt\f[R] database files under
-rclone cache directory, usually \f[C]\[ti]/.cache/rclone/kv/\f[R].
+Cached checksums are stored as \f[V]bolt\f[R] database files under
+rclone cache directory, usually \f[V]\[ti]/.cache/rclone/kv/\f[R].
 Databases are maintained one per \f[I]base\f[R] backend, named like
-\f[C]BaseRemote\[ti]hasher.bolt\f[R].
-Checksums for multiple \f[C]alias\f[R]-es into a single base backend
+\f[V]BaseRemote\[ti]hasher.bolt\f[R].
+Checksums for multiple \f[V]alias\f[R]-es into a single base backend
 will be stored in the single database.
-All local paths are treated as aliases into the \f[C]local\f[R] backend
+All local paths are treated as aliases into the \f[V]local\f[R] backend
 (unless encrypted or chunked) and stored in
-\f[C]\[ti]/.cache/rclone/kv/local\[ti]hasher.bolt\f[R].
+\f[V]\[ti]/.cache/rclone/kv/local\[ti]hasher.bolt\f[R].
 Databases can be shared between multiple rclone processes.
 .SH HDFS
 .PP
@@ -51331,11 +51928,11 @@ HDFS (https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/Hdfs
 is a distributed file-system, part of the Apache
 Hadoop (https://hadoop.apache.org/) framework.
 .PP
-Paths are specified as \f[C]remote:\f[R] or
-\f[C]remote:path/to/dir\f[R].
+Paths are specified as \f[V]remote:\f[R] or
+\f[V]remote:path/to/dir\f[R].
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -51408,7 +52005,7 @@ e/n/d/r/c/s/q> q
 \f[R]
 .fi
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this
+This remote is called \f[V]remote\f[R] and can now be used like this
 .PP
 See all the top level directories
 .IP
@@ -51426,7 +52023,7 @@ rclone ls remote:directory
 \f[R]
 .fi
 .PP
-Sync the remote \f[C]directory\f[R] to \f[C]/home/local/directory\f[R],
+Sync the remote \f[V]directory\f[R] to \f[V]/home/local/directory\f[R],
 deleting any excess files.
 .IP
 .nf
@@ -51471,7 +52068,7 @@ username = root
 \f[R]
 .fi
 .PP
-You can stop this image with \f[C]docker kill rclone-hdfs\f[R]
+You can stop this image with \f[V]docker kill rclone-hdfs\f[R]
 (\f[B]NB\f[R] it does not use volumes, so all data uploaded will be
 lost.)
 .SS Modification times
@@ -51482,7 +52079,7 @@ Time accurate to 1 second is stored.
 No checksums are implemented.
 .SS Usage information
 .PP
-You can use the \f[C]rclone about remote:\f[R] command which will
+You can use the \f[V]rclone about remote:\f[R] command which will
 display filesystem size and current usage.
 .SS Restricted filename characters
 .PP
@@ -51506,7 +52103,7 @@ T{
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 .TE
 .PP
@@ -51640,22 +52237,22 @@ Type: string
 Required: false
 .SS Limitations
 .IP \[bu] 2
-No server-side \f[C]Move\f[R] or \f[C]DirMove\f[R].
+No server-side \f[V]Move\f[R] or \f[V]DirMove\f[R].
 .IP \[bu] 2
 Checksums not implemented.
 .SH HiDrive
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .PP
 The initial setup for hidrive involves getting a token from HiDrive
 which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -51722,11 +52319,11 @@ Note that rclone runs a webserver on your local machine to collect the
 token as returned from HiDrive.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-The webserver runs on \f[C]http://127.0.0.1:53682/\f[R].
-If local port \f[C]53682\f[R] is protected by a firewall you may need to
+The webserver runs on \f[V]http://127.0.0.1:53682/\f[R].
+If local port \f[V]53682\f[R] is protected by a firewall you may need to
 temporarily unblock the firewall to complete authorization.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your HiDrive root folder
 .IP
@@ -51767,7 +52364,7 @@ docs (https://rclone.org/docs/#configuration-encryption).
 .SS Invalid refresh token
 .PP
 As can be verified here (https://developer.hidrive.com/basics-flows/),
-each \f[C]refresh_token\f[R] (for Native Applications) is valid for 60
+each \f[V]refresh_token\f[R] (for Native Applications) is valid for 60
 days.
 If used to access HiDrivei, its validity will be automatically extended.
 .PP
@@ -51801,11 +52398,11 @@ which is used to verify the integrity of file contents after successful
 transfers.
 .SS Restricted filename characters
 .PP
-HiDrive cannot store files or folders that include \f[C]/\f[R] (0x2F) or
+HiDrive cannot store files or folders that include \f[V]/\f[R] (0x2F) or
 null-bytes (0x00) in their name.
 Any other characters can be used in the names of files or folders.
 Additionally, files or folders cannot be named either of the following:
-\f[C].\f[R] or \f[C]..\f[R]
+\f[V].\f[R] or \f[V]..\f[R]
 .PP
 Therefore rclone will automatically replace these characters, if files
 or folders are stored or accessed with such names.
@@ -51826,12 +52423,12 @@ may want to restrict this behaviour on systems with limited resources.
 .PP
 You can customize this behaviour using the following options:
 .IP \[bu] 2
-\f[C]chunk_size\f[R]: size of file parts
+\f[V]chunk_size\f[R]: size of file parts
 .IP \[bu] 2
-\f[C]upload_cutoff\f[R]: files larger or equal to this in size will use
+\f[V]upload_cutoff\f[R]: files larger or equal to this in size will use
 a chunked transfer
 .IP \[bu] 2
-\f[C]upload_concurrency\f[R]: number of file-parts to upload at the same
+\f[V]upload_concurrency\f[R]: number of file-parts to upload at the same
 time
 .PP
 See the below section about configuration options for more details.
@@ -51847,7 +52444,7 @@ account.
 However, you can set this to restrict rclone to a specific folder
 hierarchy.
 .PP
-This works by prepending the contents of the \f[C]root_prefix\f[R]
+This works by prepending the contents of the \f[V]root_prefix\f[R]
 option to any paths accessed by rclone.
 For example, the following two ways to access the home directory are
 equivalent:
@@ -51865,14 +52462,14 @@ See the below section about configuration options for more details.
 .PP
 By default, rclone will know the number of directory members contained
 in a directory.
-For example, \f[C]rclone lsd\f[R] uses this information.
+For example, \f[V]rclone lsd\f[R] uses this information.
 .PP
 The acquisition of this information will result in additional time costs
 for HiDrive\[aq]s API.
 When dealing with large directory structures, it may be desirable to
 circumvent this time cost, especially when this information is not
 explicitly needed.
-For this, the \f[C]disable_fetching_member_count\f[R] option can be
+For this, the \f[V]disable_fetching_member_count\f[R] option can be
 used.
 .PP
 See the below section about configuration options for more details.
@@ -52212,7 +52809,7 @@ hidrive-remote.
 This means symlinks cannot be individually removed, copied, or moved,
 except when removing, copying, or moving the parent folder.
 .PP
-\f[I]This does not affect the \f[CI].rclonelink\f[I]-files that rclone
+\f[I]This does not affect the \f[VI].rclonelink\f[I]-files that rclone
 uses to encode and store symbolic links.\f[R]
 .SS Sparse files
 .PP
@@ -52231,35 +52828,35 @@ This has been tested with common webservers such as Apache/Nginx/Caddy
 and will likely work with file listings from most web servers.
 (If it doesn\[aq]t then please file an issue, or send a pull request!)
 .PP
-Paths are specified as \f[C]remote:\f[R] or \f[C]remote:path\f[R].
+Paths are specified as \f[V]remote:\f[R] or \f[V]remote:path\f[R].
 .PP
-The \f[C]remote:\f[R] represents the configured url, and any path
+The \f[V]remote:\f[R] represents the configured url, and any path
 following it will be resolved relative to this url, according to the URL
 standard.
-This means with remote url \f[C]https://beta.rclone.org/branch\f[R] and
-path \f[C]fix\f[R], the resolved URL will be
-\f[C]https://beta.rclone.org/branch/fix\f[R], while with path
-\f[C]/fix\f[R] the resolved URL will be
-\f[C]https://beta.rclone.org/fix\f[R] as the absolute path is resolved
+This means with remote url \f[V]https://beta.rclone.org/branch\f[R] and
+path \f[V]fix\f[R], the resolved URL will be
+\f[V]https://beta.rclone.org/branch/fix\f[R], while with path
+\f[V]/fix\f[R] the resolved URL will be
+\f[V]https://beta.rclone.org/fix\f[R] as the absolute path is resolved
 from the root of the domain.
 .PP
-If the path following the \f[C]remote:\f[R] ends with \f[C]/\f[R] it
+If the path following the \f[V]remote:\f[R] ends with \f[V]/\f[R] it
 will be assumed to point to a directory.
-If the path does not end with \f[C]/\f[R], then a HEAD request is sent
+If the path does not end with \f[V]/\f[R], then a HEAD request is sent
 and the response used to decide if it it is treated as a file or a
-directory (run with \f[C]-vv\f[R] to see details).
-When --http-no-head is specified, a path without ending \f[C]/\f[R] is
+directory (run with \f[V]-vv\f[R] to see details).
+When --http-no-head is specified, a path without ending \f[V]/\f[R] is
 always assumed to be a file.
 If rclone incorrectly assumes the path is a file, the solution is to
-specify the path with ending \f[C]/\f[R].
-When you know the path is a directory, ending it with \f[C]/\f[R] is
+specify the path with ending \f[V]/\f[R].
+When you know the path is a directory, ending it with \f[V]/\f[R] is
 always better as it avoids the initial HEAD request.
 .PP
 To just download a single file it is easier to use
 copyurl (https://rclone.org/commands/rclone_copyurl/).
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -52317,7 +52914,7 @@ e/n/d/r/c/s/q> q
 \f[R]
 .fi
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this
+This remote is called \f[V]remote\f[R] and can now be used like this
 .PP
 See all the top level directories
 .IP
@@ -52335,7 +52932,7 @@ rclone ls remote:directory
 \f[R]
 .fi
 .PP
-Sync the remote \f[C]directory\f[R] to \f[C]/home/local/directory\f[R],
+Sync the remote \f[V]directory\f[R] to \f[V]/home/local/directory\f[R],
 deleting any excess files.
 .IP
 .nf
@@ -52550,9 +53147,9 @@ currently in use.
 It doesn\[aq]t return anything.
 .SS Limitations
 .PP
-\f[C]rclone about\f[R] is not supported by the HTTP backend.
+\f[V]rclone about\f[R] is not supported by the HTTP backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -52583,8 +53180,8 @@ Here is an example of making an imagekit configuration.
 Firstly create a ImageKit.io (https://imagekit.io/) account and choose a
 plan.
 .PP
-You will need to log in and get the \f[C]publicKey\f[R] and
-\f[C]privateKey\f[R] for your account from the developer section.
+You will need to log in and get the \f[V]publicKey\f[R] and
+\f[V]privateKey\f[R] for your account from the developer section.
 .PP
 Now run
 .IP
@@ -52730,7 +53327,7 @@ Required: true
 Here are the Advanced options specific to imagekit (ImageKit.io).
 .SS --imagekit-only-signed
 .PP
-If you have configured \f[C]Restrict unsigned image URLs\f[R] in your
+If you have configured \f[V]Restrict unsigned image URLs\f[R] in your
 dashboard settings, set this to true.
 .PP
 Properties:
@@ -52948,9 +53545,10 @@ Refer to IAS3 API
 documentation (https://archive.org/services/docs/api/ias3.html) for the
 API this backend uses.
 .PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:item/path/to/dir\f[R].
+Paths are specified as \f[V]remote:bucket\f[R] (or \f[V]remote:\f[R] for
+the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:item/path/to/dir\f[R].
 .PP
 Unlike S3, listing up all items uploaded by you isn\[aq]t supported.
 .PP
@@ -52972,7 +53570,7 @@ rclone ls remote:item
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote item, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote item, deleting any
 excess files in the item.
 .IP
 .nf
@@ -52995,10 +53593,10 @@ has a limit, and it may block you from uploading, or even deleting.
 You should avoid uploading a lot of small files for better behavior.
 .PP
 You can optionally wait for the server\[aq]s processing to finish, by
-setting non-zero value to \f[C]wait_archive\f[R] key.
+setting non-zero value to \f[V]wait_archive\f[R] key.
 By making it wait, rclone can do normal file comparison.
 Make sure to set a large enough value (e.g.
-\f[C]30m0s\f[R] for smaller files) as it can take a long time depending
+\f[V]30m0s\f[R] for smaller files) as it can take a long time depending
 on server\[aq]s queue.
 .SS About metadata
 .PP
@@ -53007,16 +53605,16 @@ file.
 The metadata will appear as file metadata on Internet Archive.
 However, some fields are reserved by both Internet Archive and rclone.
 .PP
-The following are reserved by Internet Archive: - \f[C]name\f[R] -
-\f[C]source\f[R] - \f[C]size\f[R] - \f[C]md5\f[R] - \f[C]crc32\f[R] -
-\f[C]sha1\f[R] - \f[C]format\f[R] - \f[C]old_version\f[R] -
-\f[C]viruscheck\f[R] - \f[C]summation\f[R]
+The following are reserved by Internet Archive: - \f[V]name\f[R] -
+\f[V]source\f[R] - \f[V]size\f[R] - \f[V]md5\f[R] - \f[V]crc32\f[R] -
+\f[V]sha1\f[R] - \f[V]format\f[R] - \f[V]old_version\f[R] -
+\f[V]viruscheck\f[R] - \f[V]summation\f[R]
 .PP
 Trying to set values to these keys is ignored with a warning.
-Only setting \f[C]mtime\f[R] is an exception.
+Only setting \f[V]mtime\f[R] is an exception.
 Doing so make it the identical behavior as setting ModTime.
 .PP
-rclone reserves all the keys starting with \f[C]rclone-\f[R].
+rclone reserves all the keys starting with \f[V]rclone-\f[R].
 Setting value for these keys will give you warnings, but values are set
 according to request.
 .PP
@@ -53029,7 +53627,7 @@ ones.
 .SS Filtering auto generated files
 .PP
 The Internet Archive automatically creates metadata files after upload.
-These can cause problems when doing an \f[C]rclone sync\f[R] as rclone
+These can cause problems when doing an \f[V]rclone sync\f[R] as rclone
 will try, and fail, to delete them.
 These metadata files are not changeable, as they are created by the
 Internet Archive automatically.
@@ -53044,7 +53642,7 @@ rclone sync ... --metadata-exclude \[dq]source=metadata\[dq] --metadata-exclude
 .fi
 .PP
 Which excludes from the sync any files which have the
-\f[C]source=metadata\f[R] or \f[C]format=Metadata\f[R] flags which are
+\f[V]source=metadata\f[R] or \f[V]format=Metadata\f[R] flags which are
 added to Internet Archive auto-created files.
 .SS Configuration
 .PP
@@ -53458,7 +54056,7 @@ jottacloud.com (https://www.jottacloud.com/), it also provides
 white-label solutions to different companies, such as: * Telia * Telia
 Cloud (cloud.telia.se) * Telia Sky (sky.telia.no) * Tele2 * Tele2 Cloud
 (mittcloud.tele2.se) * Onlime * Onlime Cloud Storage (onlime.dk) *
-Elkj\[/o]p (with subsidiaries): * Elkj\[/o]p Cloud (cloud.elkjop.no) *
+Elkjøp (with subsidiaries): * Elkjøp Cloud (cloud.elkjop.no) *
 Elgiganten Sweden (cloud.elgiganten.se) * Elgiganten Denmark
 (cloud.elgiganten.dk) * Giganti Cloud (cloud.gigantti.fi) * ELKO Cloud
 (cloud.elko.is)
@@ -53466,10 +54064,10 @@ Elgiganten Sweden (cloud.elgiganten.se) * Elgiganten Denmark
 Most of the white-label versions are supported by this backend, although
 may require different authentication setup - described below.
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Authentication types
 .PP
 Some of the whitelabel versions uses a different authentication method
@@ -53522,7 +54120,7 @@ individual tokens.
 .SS Legacy authentication
 .PP
 If you are using one of the whitelabel versions (e.g.
-from Elkj\[/o]p) you may not have the option to generate a CLI token.
+from Elkjøp) you may not have the option to generate a CLI token.
 In this case you\[aq]ll have to use the legacy authentication.
 To do this select yes when the setup asks for legacy authentication and
 enter your username and password.
@@ -53559,7 +54157,7 @@ authentication in the setup.
 The rest of the setup is identical to the default setup.
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R] with
+Here is an example of how to make a remote called \f[V]remote\f[R] with
 the default setup.
 First run:
 .IP
@@ -53660,7 +54258,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Jottacloud
 .IP
@@ -53718,7 +54316,7 @@ Rclone will only to a very limited degree support them.
 Generally you should avoid these, unless you know what you are doing.
 .SS --fast-list
 .PP
-This backend supports \f[C]--fast-list\f[R] which allows you to use
+This backend supports \f[V]--fast-list\f[R] which allows you to use
 fewer transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
@@ -53729,7 +54327,7 @@ long wait time before the first results are shown.
 .PP
 Note also that with rclone version 1.58 and newer, information about
 MIME types (https://rclone.org/overview/#mime-type) and metadata item
-utime are not available when using \f[C]--fast-list\f[R].
+utime are not available when using \f[V]--fast-list\f[R].
 .SS Modification times and hashes
 .PP
 Jottacloud allows modification times to be set on objects accurate to 1
@@ -53737,7 +54335,7 @@ second.
 These will be used to detect whether objects need syncing or not.
 .PP
 Jottacloud supports MD5 type hashes, so you can use the
-\f[C]--checksum\f[R] flag.
+\f[V]--checksum\f[R] flag.
 .PP
 Note that Jottacloud requires the MD5 hash before upload so if the
 source does not have an MD5 checksum then the file will be cached
@@ -53774,49 +54372,49 @@ T{
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 *
 T}@T{
 0x2A
 T}@T{
-\[uFF0A]
+＊
 T}
 T{
 :
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 ?
 T}@T{
 0x3F
 T}@T{
-\[uFF1F]
+？
 T}
 T{
 |
 T}@T{
 0x7C
 T}@T{
-\[uFF5C]
+｜
 T}
 .TE
 .PP
@@ -53840,7 +54438,7 @@ it.
 Currently rclone only supports retrieving the current version but older
 versions can be accessed via the Jottacloud Website.
 .PP
-Versioning can be disabled by \f[C]--jottacloud-no-versions\f[R] option.
+Versioning can be disabled by \f[V]--jottacloud-no-versions\f[R] option.
 This is achieved by deleting the remote file prior to uploading a new
 version.
 If the upload the fails no version of the file will be available in the
@@ -53848,7 +54446,7 @@ remote.
 .SS Quota information
 .PP
 To view your current quota you can use the
-\f[C]rclone about remote:\f[R] command which will display your usage
+\f[V]rclone about remote:\f[R] command which will display your usage
 limit (unless it is unlimited) and the current usage.
 .SS Standard options
 .PP
@@ -54108,7 +54706,7 @@ names.
 Rclone will map these names to and from an identical looking unicode
 equivalent.
 For example if a file has a ?
-in it will be mapped to \[uFF1F] instead.
+in it will be mapped to ？ instead.
 .PP
 Jottacloud only supports filenames up to 255 characters in length.
 .SS Troubleshooting
@@ -54119,20 +54717,20 @@ previously deleted paths to fail.
 Emptying the trash should help in such cases.
 .SH Koofr
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 The initial setup for Koofr involves creating an application password
 for rclone.
 You can do that by opening the Koofr web
 application (https://app.koofr.net/app/admin/preferences/password),
-giving the password a nice name like \f[C]rclone\f[R] and clicking on
+giving the password a nice name like \f[V]rclone\f[R] and clicking on
 generate.
 .PP
-Here is an example of how to make a remote called \f[C]koofr\f[R].
+Here is an example of how to make a remote called \f[V]koofr\f[R].
 First run:
 .IP
 .nf
@@ -54207,7 +54805,7 @@ You can choose to edit advanced config in order to enter your own
 service URL if you use an on-premise or white label Koofr instance, or
 choose an alternative mount instead of your primary storage.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Koofr
 .IP
@@ -54254,7 +54852,7 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -54426,7 +55024,7 @@ Digi Storage (https://www.digi.ro/servicii/online/digi-storage) is a
 cloud storage service run by Digi.ro (https://www.digi.ro/) that
 provides a Koofr API.
 .PP
-Here is an example of how to make a remote called \f[C]ds\f[R].
+Here is an example of how to make a remote called \f[V]ds\f[R].
 First run:
 .IP
 .nf
@@ -54501,7 +55099,7 @@ You may also want to use another, public or private storage provider
 that runs a Koofr API compatible service, by simply providing the base
 URL to connect to.
 .PP
-Here is an example of how to make a remote called \f[C]other\f[R].
+Here is an example of how to make a remote called \f[V]other\f[R].
 First run:
 .IP
 .nf
@@ -54672,9 +55270,9 @@ available on Windows and Mac OS.
 .SS Features highlights
 .IP \[bu] 2
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R]
+\f[V]remote:directory/subdirectory\f[R]
 .IP \[bu] 2
-Files have a \f[C]last modified time\f[R] property, directories
+Files have a \f[V]last modified time\f[R] property, directories
 don\[aq]t
 .IP \[bu] 2
 Deleted files are by default moved to the trash
@@ -54702,19 +55300,13 @@ First create a Mail.ru Cloud account and choose a tariff.
 You will need to log in and create an app password for rclone.
 Rclone \f[B]will not work\f[R] with your normal username and password -
 it will give an error like
-\f[C]oauth2: server response missing access_token\f[R].
+\f[V]oauth2: server response missing access_token\f[R].
 .IP \[bu] 2
 Click on your user icon in the top right
 .IP \[bu] 2
-Go to Security / \[dq]\[u041F]\[u0430]\[u0440]\[u043E]\[u043B]\[u044C]
-\[u0438]
-\[u0431]\[u0435]\[u0437]\[u043E]\[u043F]\[u0430]\[u0441]\[u043D]\[u043E]\[u0441]\[u0442]\[u044C]\[dq]
+Go to Security / \[dq]Пароль и безопасность\[dq]
 .IP \[bu] 2
-Click password for apps /
-\[dq]\[u041F]\[u0430]\[u0440]\[u043E]\[u043B]\[u0438]
-\[u0434]\[u043B]\[u044F]
-\[u0432]\[u043D]\[u0435]\[u0448]\[u043D]\[u0438]\[u0445]
-\[u043F]\[u0440]\[u0438]\[u043B]\[u043E]\[u0436]\[u0435]\[u043D]\[u0438]\[u0439]\[dq]
+Click password for apps / \[dq]Пароли для внешних приложений\[dq]
 .IP \[bu] 2
 Add the password - give it a name - eg \[dq]rclone\[dq]
 .IP \[bu] 2
@@ -54820,7 +55412,7 @@ rclone ls remote:directory
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote path, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote path, deleting any
 excess files in the path.
 .IP
 .nf
@@ -54847,13 +55439,13 @@ Removing a file or directory actually moves it to the trash, which is
 not visible to rclone but can be seen in a web browser.
 The trashed file still occupies part of total quota.
 If you wish to empty your trash and free some quota, you can use the
-\f[C]rclone cleanup remote:\f[R] command, which will permanently delete
+\f[V]rclone cleanup remote:\f[R] command, which will permanently delete
 all your trashed files.
 This command does not take any path arguments.
 .SS Quota information
 .PP
 To view your current quota you can use the
-\f[C]rclone about remote:\f[R] command which will display your usage
+\f[V]rclone about remote:\f[R] command which will display your usage
 limit (quota) and the current usage.
 .SS Restricted filename characters
 .PP
@@ -54877,56 +55469,56 @@ T{
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 *
 T}@T{
 0x2A
 T}@T{
-\[uFF0A]
+＊
 T}
 T{
 :
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 ?
 T}@T{
 0x3F
 T}@T{
-\[uFF1F]
+？
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 |
 T}@T{
 0x7C
 T}@T{
-\[uFF5C]
+｜
 T}
 .TE
 .PP
@@ -55321,13 +55913,13 @@ files without knowledge of the key used for encryption.
 This is an rclone backend for Mega which supports the file transfer
 features of Mega using the same client side encryption.
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -55380,9 +55972,9 @@ y/e/d> y
 .PP
 \f[B]NOTE:\f[R] The encryption keys need to have been already generated
 after a regular login via the browser, otherwise attempting to use the
-credentials in \f[C]rclone\f[R] will fail.
+credentials in \f[V]rclone\f[R] will fail.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Mega
 .IP
@@ -55428,14 +56020,14 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 .TE
 .PP
@@ -55450,7 +56042,7 @@ normal file system).
 Duplicated files cause problems with the syncing and you will see
 messages in the log about duplicates.
 .PP
-Use \f[C]rclone dedupe\f[R] to fix duplicated files.
+Use \f[V]rclone dedupe\f[R] to fix duplicated files.
 .SS Failure to log-in
 .SS Object not found
 .PP
@@ -55501,7 +56093,7 @@ We haven\[aq]t worked out the exact blocking rules but it seems to be
 related to fast paced, successive rclone commands.
 .PP
 For example, executing this command 90 times in a row
-\f[C]rclone link remote:file\f[R] will cause the remote to become
+\f[V]rclone link remote:file\f[R] will cause the remote to become
 \[dq]blocked\[dq].
 This is not an abnormal situation, for example if you wish to get the
 public links of a directory with hundred of files...
@@ -55509,9 +56101,9 @@ After more or less a week, the remote will remote accept rclone logins
 normally again.
 .PP
 You can mitigate this issue by mounting the remote it with
-\f[C]rclone mount\f[R].
+\f[V]rclone mount\f[R].
 This will log-in when mounting and a log-out when unmounting only.
-You can also run \f[C]rclone rcd\f[R] and then use \f[C]rclone rc\f[R]
+You can also run \f[V]rclone rcd\f[R] and then use \f[V]rclone rc\f[R]
 to run the commands over the API to avoid logging in each time.
 .PP
 Rclone does not currently close mega sessions (you can see them in the
@@ -55661,7 +56253,7 @@ Env Var: RCLONE_MEGA_DESCRIPTION
 Type: string
 .IP \[bu] 2
 Required: false
-.SS Process \f[C]killed\f[R]
+.SS Process \f[V]killed\f[R]
 .PP
 On accounts with large files or something else, memory usage can
 significantly increase when executing list/sync instructions.
@@ -55688,10 +56280,10 @@ It does not persist its data - use the local backend for that.
 The memory backend behaves like a bucket-based remote (e.g.
 like s3).
 Because it has no parameters you can just use it with the
-\f[C]:memory:\f[R] remote name.
+\f[V]:memory:\f[R] remote name.
 .SS Configuration
 .PP
-You can configure it as a remote like this with \f[C]rclone config\f[R]
+You can configure it as a remote like this with \f[V]rclone config\f[R]
 too if you want to:
 .IP
 .nf
@@ -55762,24 +56354,24 @@ Type: string
 Required: false
 .SH Akamai NetStorage
 .PP
-Paths are specified as \f[C]remote:\f[R] You may put subdirectories in
+Paths are specified as \f[V]remote:\f[R] You may put subdirectories in
 too, e.g.
-\f[C]remote:/path/to/dir\f[R].
+\f[V]remote:/path/to/dir\f[R].
 If you have a CP code you can use that as the folder after the domain
 such as <domain>/<cpcode>/<internal directories within cpcode>.
 .PP
 For example, this is commonly configured with or without a CP code: *
 \f[B]With a CP code\f[R].
-\f[C][your-domain-prefix]-nsu.akamaihd.net/123456/subdirectory/\f[R] *
+\f[V][your-domain-prefix]-nsu.akamaihd.net/123456/subdirectory/\f[R] *
 \f[B]Without a CP code\f[R].
-\f[C][your-domain-prefix]-nsu.akamaihd.net\f[R]
+\f[V][your-domain-prefix]-nsu.akamaihd.net\f[R]
 .PP
 See all buckets rclone lsd remote: The initial setup for Netstorage
 involves getting an account and secret.
-Use \f[C]rclone config\f[R] to walk you through the setup process.
+Use \f[V]rclone config\f[R] to walk you through the setup process.
 .SS Configuration
 .PP
-Here\[aq]s an example of how to make a remote called \f[C]ns1\f[R].
+Here\[aq]s an example of how to make a remote called \f[V]ns1\f[R].
 .IP "1." 3
 To begin the interactive configuration process, enter this command:
 .IP
@@ -55789,7 +56381,7 @@ rclone config
 \f[R]
 .fi
 .IP "2." 3
-Type \f[C]n\f[R] to create a new remote.
+Type \f[V]n\f[R] to create a new remote.
 .IP
 .nf
 \f[C]
@@ -55800,7 +56392,7 @@ e/n/d/q> n
 \f[R]
 .fi
 .IP "3." 3
-For this example, enter \f[C]ns1\f[R] when you reach the name> prompt.
+For this example, enter \f[V]ns1\f[R] when you reach the name> prompt.
 .IP
 .nf
 \f[C]
@@ -55808,7 +56400,7 @@ name> ns1
 \f[R]
 .fi
 .IP "4." 3
-Enter \f[C]netstorage\f[R] as the type of storage to configure.
+Enter \f[V]netstorage\f[R] as the type of storage to configure.
 .IP
 .nf
 \f[C]
@@ -55838,7 +56430,7 @@ protocol> 1
 .fi
 .IP "6." 3
 Specify your NetStorage host, CP code, and any necessary content paths
-using this format: \f[C]<domain>/<cpcode>/<content>/\f[R]
+using this format: \f[V]<domain>/<cpcode>/<content>/\f[R]
 .IP
 .nf
 \f[C]
@@ -55858,9 +56450,9 @@ account> username
 .IP "8." 3
 Set the Netstorage account secret/G2O key which will be used for
 authentication purposes.
-Select the \f[C]y\f[R] option to set your own password then enter your
+Select the \f[V]y\f[R] option to set your own password then enter your
 secret.
-Note: The secret is stored in the \f[C]rclone.conf\f[R] file with
+Note: The secret is stored in the \f[V]rclone.conf\f[R] file with
 hex-encoded encryption.
 .IP
 .nf
@@ -55893,7 +56485,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-This remote is called \f[C]ns1\f[R] and can now be used.
+This remote is called \f[V]ns1\f[R] and can now be used.
 .SS Example operations
 .PP
 Get started with rclone and NetStorage with these examples.
@@ -55939,7 +56531,7 @@ rclone move ns1:/974012/testing/notes.txt ns1:/974450/testing2/
 .SS Features
 .SS Symlink Support
 .PP
-The Netstorage backend changes the rclone \f[C]--links, -l\f[R]
+The Netstorage backend changes the rclone \f[V]--links, -l\f[R]
 behavior.
 When uploading, instead of creating the .rclonelink file, use the
 \[dq]symlink\[dq] API in order to create the corresponding symlink on
@@ -55993,7 +56585,7 @@ such as SFTP and the Content Management Shell (CMShell).
 Rclone will not guarantee correctness of operations with implicit
 directories which might have been created as a result of using an upload
 API directly.
-.SS \f[C]--fast-list\f[R] / ListR support
+.SS \f[V]--fast-list\f[R] / ListR support
 .PP
 NetStorage remote supports the ListR feature by using the \[dq]list\[dq]
 NetStorage API action to return a lexicographical list of all objects
@@ -56001,13 +56593,13 @@ within the specified CP code, recursing into subdirectories as
 they\[aq]re encountered.
 .IP \[bu] 2
 \f[B]Rclone will use the ListR method for some commands by default\f[R].
-Commands such as \f[C]lsf -R\f[R] will use ListR by default.
-To disable this, include the \f[C]--disable listR\f[R] option to use the
+Commands such as \f[V]lsf -R\f[R] will use ListR by default.
+To disable this, include the \f[V]--disable listR\f[R] option to use the
 non-recursive method of listing objects.
 .IP \[bu] 2
 \f[B]Rclone will not use the ListR method for some commands\f[R].
-Commands such as \f[C]sync\f[R] don\[aq]t use ListR by default.
-To force using the ListR method, include the \f[C]--fast-list\f[R]
+Commands such as \f[V]sync\f[R] don\[aq]t use ListR by default.
+To force using the ListR method, include the \f[V]--fast-list\f[R]
 option.
 .PP
 There are pros and cons of using the ListR method, refer to rclone
@@ -56047,7 +56639,7 @@ NetStorage).
 .PP
 Domain+path of NetStorage host to connect to.
 .PP
-Format should be \f[C]<domain>/<internal folders>\f[R]
+Format should be \f[V]<domain>/<internal folders>\f[R]
 .PP
 Properties:
 .IP \[bu] 2
@@ -56184,17 +56776,18 @@ The desired path location (including applicable sub-directories) ending
 in the object that will be the target of the symlink (for example,
 /links/mylink).
 Include the file extension for the object, if applicable.
-\f[C]rclone backend symlink <src> <path>\f[R]
+\f[V]rclone backend symlink <src> <path>\f[R]
 .SH Microsoft Azure Blob Storage
 .PP
-Paths are specified as \f[C]remote:container\f[R] (or \f[C]remote:\f[R]
-for the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:container/path/to/dir\f[R].
+Paths are specified as \f[V]remote:container\f[R] (or \f[V]remote:\f[R]
+for the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:container/path/to/dir\f[R].
 .SS Configuration
 .PP
 Here is an example of making a Microsoft Azure Blob Storage
 configuration.
-For a remote called \f[C]remote\f[R].
+For a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -56265,7 +56858,7 @@ rclone ls remote:container
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote container, deleting
+Sync \f[V]/home/local/directory\f[R] to the remote container, deleting
 any excess files in the container.
 .IP
 .nf
@@ -56275,24 +56868,24 @@ rclone sync --interactive /home/local/directory remote:container
 .fi
 .SS --fast-list
 .PP
-This remote supports \f[C]--fast-list\f[R] which allows you to use fewer
+This remote supports \f[V]--fast-list\f[R] which allows you to use fewer
 transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
 .SS Modification times and hashes
 .PP
 The modification time is stored as metadata on the object with the
-\f[C]mtime\f[R] key.
+\f[V]mtime\f[R] key.
 It is stored using RFC3339 Format time with nanosecond precision.
 The metadata is supplied during directory listings so there is no
 performance overhead to using it.
 .PP
-If you wish to use the Azure standard \f[C]LastModified\f[R] time stored
+If you wish to use the Azure standard \f[V]LastModified\f[R] time stored
 on the object as the modified time, then use the
-\f[C]--use-server-modtime\f[R] flag.
-Note that rclone can\[aq]t set \f[C]LastModified\f[R], so using the
-\f[C]--update\f[R] flag when syncing is recommended if using
-\f[C]--use-server-modtime\f[R].
+\f[V]--use-server-modtime\f[R] flag.
+Note that rclone can\[aq]t set \f[V]LastModified\f[R], so using the
+\f[V]--update\f[R] flag when syncing is recommended if using
+\f[V]--use-server-modtime\f[R].
 .PP
 MD5 hashes are stored with blobs.
 However blobs that were uploaded in chunks only have an MD5 if the
@@ -56301,7 +56894,7 @@ the local disk.
 .SS Performance
 .PP
 When uploading large files, increasing the value of
-\f[C]--azureblob-upload-concurrency\f[R] will increase performance at
+\f[V]--azureblob-upload-concurrency\f[R] will increase performance at
 the cost of using more memory.
 The default of 16 is set quite conservatively to use less memory.
 It maybe be necessary raise it to 64 or higher to fully utilize a 1
@@ -56328,14 +56921,14 @@ T{
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -56358,7 +56951,7 @@ T{
 T}@T{
 0x2E
 T}@T{
-\[uFF0E]
+．
 T}
 .TE
 .PP
@@ -56372,7 +56965,7 @@ Storage.
 Rclone tries them in the order of the sections below.
 .SS Env Auth
 .PP
-If the \f[C]env_auth\f[R] config parameter is \f[C]true\f[R] then rclone
+If the \f[V]env_auth\f[R] config parameter is \f[V]true\f[R] then rclone
 will pull credentials from the environment or runtime.
 .PP
 It tries these authentication methods in this order:
@@ -56386,7 +56979,7 @@ Azure CLI credentials (as used by the az tool)
 These are described in the following sections
 .SS Env Auth: 1. Environment Variables
 .PP
-If \f[C]env_auth\f[R] is set and environment variables are present
+If \f[V]env_auth\f[R] is set and environment variables are present
 rclone authenticates a service principal with a secret or certificate,
 or a user with a password, depending on which environment variable are
 set.
@@ -56395,30 +56988,30 @@ It reads configuration from these variables, in the following order:
 Service principal with client secret
 .RS 4
 .IP \[bu] 2
-\f[C]AZURE_TENANT_ID\f[R]: ID of the service principal\[aq]s tenant.
+\f[V]AZURE_TENANT_ID\f[R]: ID of the service principal\[aq]s tenant.
 Also called its \[dq]directory\[dq] ID.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_ID\f[R]: the service principal\[aq]s client ID
+\f[V]AZURE_CLIENT_ID\f[R]: the service principal\[aq]s client ID
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_SECRET\f[R]: one of the service principal\[aq]s client
+\f[V]AZURE_CLIENT_SECRET\f[R]: one of the service principal\[aq]s client
 secrets
 .RE
 .IP "2." 3
 Service principal with certificate
 .RS 4
 .IP \[bu] 2
-\f[C]AZURE_TENANT_ID\f[R]: ID of the service principal\[aq]s tenant.
+\f[V]AZURE_TENANT_ID\f[R]: ID of the service principal\[aq]s tenant.
 Also called its \[dq]directory\[dq] ID.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_ID\f[R]: the service principal\[aq]s client ID
+\f[V]AZURE_CLIENT_ID\f[R]: the service principal\[aq]s client ID
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_CERTIFICATE_PATH\f[R]: path to a PEM or PKCS12
+\f[V]AZURE_CLIENT_CERTIFICATE_PATH\f[R]: path to a PEM or PKCS12
 certificate file including the private key.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_CERTIFICATE_PASSWORD\f[R]: (optional) password for the
+\f[V]AZURE_CLIENT_CERTIFICATE_PASSWORD\f[R]: (optional) password for the
 certificate file.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_SEND_CERTIFICATE_CHAIN\f[R]: (optional) Specifies
+\f[V]AZURE_CLIENT_SEND_CERTIFICATE_CHAIN\f[R]: (optional) Specifies
 whether an authentication request will include an x5c header to support
 subject name / issuer based authentication.
 When set to \[dq]true\[dq] or \[dq]1\[dq], authentication requests
@@ -56428,29 +57021,29 @@ include the x5c header.
 User with username and password
 .RS 4
 .IP \[bu] 2
-\f[C]AZURE_TENANT_ID\f[R]: (optional) tenant to authenticate in.
+\f[V]AZURE_TENANT_ID\f[R]: (optional) tenant to authenticate in.
 Defaults to \[dq]organizations\[dq].
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_ID\f[R]: client ID of the application the user will
+\f[V]AZURE_CLIENT_ID\f[R]: client ID of the application the user will
 authenticate to
 .IP \[bu] 2
-\f[C]AZURE_USERNAME\f[R]: a username (usually an email address)
+\f[V]AZURE_USERNAME\f[R]: a username (usually an email address)
 .IP \[bu] 2
-\f[C]AZURE_PASSWORD\f[R]: the user\[aq]s password
+\f[V]AZURE_PASSWORD\f[R]: the user\[aq]s password
 .RE
 .IP "4." 3
 Workload Identity
 .RS 4
 .IP \[bu] 2
-\f[C]AZURE_TENANT_ID\f[R]: Tenant to authenticate in.
+\f[V]AZURE_TENANT_ID\f[R]: Tenant to authenticate in.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_ID\f[R]: Client ID of the application the user will
+\f[V]AZURE_CLIENT_ID\f[R]: Client ID of the application the user will
 authenticate to.
 .IP \[bu] 2
-\f[C]AZURE_FEDERATED_TOKEN_FILE\f[R]: Path to projected service account
+\f[V]AZURE_FEDERATED_TOKEN_FILE\f[R]: Path to projected service account
 token file.
 .IP \[bu] 2
-\f[C]AZURE_AUTHORITY_HOST\f[R]: Authority of an Azure Active Directory
+\f[V]AZURE_AUTHORITY_HOST\f[R]: Authority of an Azure Active Directory
 endpoint (default: login.microsoftonline.com).
 .RE
 .SS Env Auth: 2. Managed Service Identity Credentials
@@ -56461,12 +57054,12 @@ If the resource has no system-assigned but exactly one user-assigned
 identity, the user-assigned identity will be used by default.
 .PP
 If the resource has multiple user-assigned identities you will need to
-unset \f[C]env_auth\f[R] and set \f[C]use_msi\f[R] instead.
-See the \f[C]use_msi\f[R] section.
+unset \f[V]env_auth\f[R] and set \f[V]use_msi\f[R] instead.
+See the \f[V]use_msi\f[R] section.
 .SS Env Auth: 3. Azure CLI credentials (as used by the az tool)
 .PP
-Credentials created with the \f[C]az\f[R] tool can be picked up using
-\f[C]env_auth\f[R].
+Credentials created with the \f[V]az\f[R] tool can be picked up using
+\f[V]env_auth\f[R].
 .PP
 For example if you were to login with a service principal like this:
 .IP
@@ -56492,7 +57085,7 @@ rclone lsf --azureblob-env-auth --azureblob-account=ACCOUNT :azureblob:CONTAINER
 \f[R]
 .fi
 .PP
-Which is analogous to using the \f[C]az\f[R] tool:
+Which is analogous to using the \f[V]az\f[R] tool:
 .IP
 .nf
 \f[C]
@@ -56502,14 +57095,14 @@ az storage blob list --container-name CONTAINER --account-name ACCOUNT --auth-mo
 .SS Account and Shared Key
 .PP
 This is the most straight forward and least flexible way.
-Just fill in the \f[C]account\f[R] and \f[C]key\f[R] lines and leave the
+Just fill in the \f[V]account\f[R] and \f[V]key\f[R] lines and leave the
 rest blank.
 .SS SAS URL
 .PP
 This can be an account level SAS URL or container level SAS URL.
 .PP
-To use it leave \f[C]account\f[R] and \f[C]key\f[R] blank and fill in
-\f[C]sas_url\f[R].
+To use it leave \f[V]account\f[R] and \f[V]key\f[R] blank and fill in
+\f[V]sas_url\f[R].
 .PP
 An account level SAS URL or container level SAS URL can be obtained from
 the Azure portal or the Azure Storage Explorer.
@@ -56552,54 +57145,54 @@ untrusted environment such as a CI build server.
 If these variables are set, rclone will authenticate with a service
 principal with a client secret.
 .IP \[bu] 2
-\f[C]tenant\f[R]: ID of the service principal\[aq]s tenant.
+\f[V]tenant\f[R]: ID of the service principal\[aq]s tenant.
 Also called its \[dq]directory\[dq] ID.
 .IP \[bu] 2
-\f[C]client_id\f[R]: the service principal\[aq]s client ID
+\f[V]client_id\f[R]: the service principal\[aq]s client ID
 .IP \[bu] 2
-\f[C]client_secret\f[R]: one of the service principal\[aq]s client
+\f[V]client_secret\f[R]: one of the service principal\[aq]s client
 secrets
 .PP
 The credentials can also be placed in a file using the
-\f[C]service_principal_file\f[R] configuration option.
+\f[V]service_principal_file\f[R] configuration option.
 .SS Service principal with certificate
 .PP
 If these variables are set, rclone will authenticate with a service
 principal with certificate.
 .IP \[bu] 2
-\f[C]tenant\f[R]: ID of the service principal\[aq]s tenant.
+\f[V]tenant\f[R]: ID of the service principal\[aq]s tenant.
 Also called its \[dq]directory\[dq] ID.
 .IP \[bu] 2
-\f[C]client_id\f[R]: the service principal\[aq]s client ID
+\f[V]client_id\f[R]: the service principal\[aq]s client ID
 .IP \[bu] 2
-\f[C]client_certificate_path\f[R]: path to a PEM or PKCS12 certificate
+\f[V]client_certificate_path\f[R]: path to a PEM or PKCS12 certificate
 file including the private key.
 .IP \[bu] 2
-\f[C]client_certificate_password\f[R]: (optional) password for the
+\f[V]client_certificate_password\f[R]: (optional) password for the
 certificate file.
 .IP \[bu] 2
-\f[C]client_send_certificate_chain\f[R]: (optional) Specifies whether an
+\f[V]client_send_certificate_chain\f[R]: (optional) Specifies whether an
 authentication request will include an x5c header to support subject
 name / issuer based authentication.
 When set to \[dq]true\[dq] or \[dq]1\[dq], authentication requests
 include the x5c header.
 .PP
-\f[B]NB\f[R] \f[C]client_certificate_password\f[R] must be obscured -
+\f[B]NB\f[R] \f[V]client_certificate_password\f[R] must be obscured -
 see rclone obscure (https://rclone.org/commands/rclone_obscure/).
 .SS User with username and password
 .PP
 If these variables are set, rclone will authenticate with username and
 password.
 .IP \[bu] 2
-\f[C]tenant\f[R]: (optional) tenant to authenticate in.
+\f[V]tenant\f[R]: (optional) tenant to authenticate in.
 Defaults to \[dq]organizations\[dq].
 .IP \[bu] 2
-\f[C]client_id\f[R]: client ID of the application the user will
+\f[V]client_id\f[R]: client ID of the application the user will
 authenticate to
 .IP \[bu] 2
-\f[C]username\f[R]: a username (usually an email address)
+\f[V]username\f[R]: a username (usually an email address)
 .IP \[bu] 2
-\f[C]password\f[R]: the user\[aq]s password
+\f[V]password\f[R]: the user\[aq]s password
 .PP
 Microsoft doesn\[aq]t recommend this kind of authentication, because
 it\[aq]s less secure than other authentication flows.
@@ -56609,27 +57202,27 @@ user or admin consent.
 This credential can only authenticate work and school accounts; it
 can\[aq]t authenticate Microsoft accounts.
 .PP
-\f[B]NB\f[R] \f[C]password\f[R] must be obscured - see rclone
+\f[B]NB\f[R] \f[V]password\f[R] must be obscured - see rclone
 obscure (https://rclone.org/commands/rclone_obscure/).
 .SS Managed Service Identity Credentials
 .PP
-If \f[C]use_msi\f[R] is set then managed service identity credentials
+If \f[V]use_msi\f[R] is set then managed service identity credentials
 are used.
 This authentication only works when running in an Azure service.
-\f[C]env_auth\f[R] needs to be unset to use this.
+\f[V]env_auth\f[R] needs to be unset to use this.
 .PP
 However if you have multiple user identities to choose from these must
 be explicitly specified using exactly one of the
-\f[C]msi_object_id\f[R], \f[C]msi_client_id\f[R], or
-\f[C]msi_mi_res_id\f[R] parameters.
+\f[V]msi_object_id\f[R], \f[V]msi_client_id\f[R], or
+\f[V]msi_mi_res_id\f[R] parameters.
 .PP
-If none of \f[C]msi_object_id\f[R], \f[C]msi_client_id\f[R], or
-\f[C]msi_mi_res_id\f[R] is set, this is is equivalent to using
-\f[C]env_auth\f[R].
+If none of \f[V]msi_object_id\f[R], \f[V]msi_client_id\f[R], or
+\f[V]msi_mi_res_id\f[R] is set, this is is equivalent to using
+\f[V]env_auth\f[R].
 .SS Anonymous
 .PP
 If you want to access resources with public anonymous access then set
-\f[C]account\f[R] only.
+\f[V]account\f[R] only.
 You can do this without making an rclone config:
 .IP
 .nf
@@ -56650,7 +57243,7 @@ Set this to the Azure Storage Account Name in use.
 Leave blank to use SAS URL or Emulator, otherwise it needs to be set.
 .PP
 If this is blank and if env_auth is set it will be read from the
-environment variable \f[C]AZURE_STORAGE_ACCOUNT_NAME\f[R] if possible.
+environment variable \f[V]AZURE_STORAGE_ACCOUNT_NAME\f[R] if possible.
 .PP
 Properties:
 .IP \[bu] 2
@@ -56869,9 +57462,9 @@ data\[dq] (https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aa
 pages for more details.
 .PP
 It may be more convenient to put the credentials directly into the
-rclone config file under the \f[C]client_id\f[R], \f[C]tenant\f[R] and
-\f[C]client_secret\f[R] keys instead of setting
-\f[C]service_principal_file\f[R].
+rclone config file under the \f[V]client_id\f[R], \f[V]tenant\f[R] and
+\f[V]client_secret\f[R] keys instead of setting
+\f[V]service_principal_file\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -57324,7 +57917,7 @@ Type: string
 Required: false
 .SS Custom upload headers
 .PP
-You can set custom upload headers with the \f[C]--header-upload\f[R]
+You can set custom upload headers with the \f[V]--header-upload\f[R]
 flag.
 .IP \[bu] 2
 Cache-Control
@@ -57337,17 +57930,17 @@ Content-Language
 .IP \[bu] 2
 Content-Type
 .PP
-Eg \f[C]--header-upload \[dq]Content-Type: text/potato\[dq]\f[R]
+Eg \f[V]--header-upload \[dq]Content-Type: text/potato\[dq]\f[R]
 .SS Limitations
 .PP
 MD5 sums are only uploaded with chunked files if the source has an MD5
 sum.
 This will always be the case for a local to azure copy.
 .PP
-\f[C]rclone about\f[R] is not supported by the Microsoft Azure Blob
+\f[V]rclone about\f[R] is not supported by the Microsoft Azure Blob
 storage backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -57358,30 +57951,30 @@ about (https://rclone.org/commands/rclone_about/)
 You can run rclone with the storage emulator (usually
 \f[I]azurite\f[R]).
 .PP
-To do this, just set up a new remote with \f[C]rclone config\f[R]
+To do this, just set up a new remote with \f[V]rclone config\f[R]
 following the instructions in the introduction and set
-\f[C]use_emulator\f[R] in the advanced settings as \f[C]true\f[R].
+\f[V]use_emulator\f[R] in the advanced settings as \f[V]true\f[R].
 You do not need to provide a default account name nor an account key.
-But you can override them in the \f[C]account\f[R] and \f[C]key\f[R]
+But you can override them in the \f[V]account\f[R] and \f[V]key\f[R]
 options.
 (Prior to v1.61 they were hard coded to \f[I]azurite\f[R]\[aq]s
-\f[C]devstoreaccount1\f[R].)
+\f[V]devstoreaccount1\f[R].)
 .PP
 Also, if you want to access a storage emulator instance running on a
-different machine, you can override the \f[C]endpoint\f[R] parameter in
+different machine, you can override the \f[V]endpoint\f[R] parameter in
 the advanced settings, setting it to
-\f[C]http(s)://<host>:<port>/devstoreaccount1\f[R] (e.g.
-\f[C]http://10.254.2.5:10000/devstoreaccount1\f[R]).
+\f[V]http(s)://<host>:<port>/devstoreaccount1\f[R] (e.g.
+\f[V]http://10.254.2.5:10000/devstoreaccount1\f[R]).
 .SH Microsoft Azure Files Storage
 .PP
-Paths are specified as \f[C]remote:\f[R] You may put subdirectories in
+Paths are specified as \f[V]remote:\f[R] You may put subdirectories in
 too, e.g.
-\f[C]remote:path/to/dir\f[R].
+\f[V]remote:path/to/dir\f[R].
 .SS Configuration
 .PP
 Here is an example of making a Microsoft Azure Files Storage
 configuration.
-For a remote called \f[C]remote\f[R].
+For a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -57486,7 +58079,7 @@ rclone ls remote:
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote directory, deleting
+Sync \f[V]/home/local/directory\f[R] to the remote directory, deleting
 any excess files in the directory.
 .IP
 .nf
@@ -57496,12 +58089,12 @@ rclone sync --interactive /home/local/directory remote:dir
 .fi
 .SS Modified time
 .PP
-The modified time is stored as Azure standard \f[C]LastModified\f[R]
+The modified time is stored as Azure standard \f[V]LastModified\f[R]
 time on files
 .SS Performance
 .PP
 When uploading large files, increasing the value of
-\f[C]--azurefiles-upload-concurrency\f[R] will increase performance at
+\f[V]--azurefiles-upload-concurrency\f[R] will increase performance at
 the cost of using more memory.
 The default of 16 is set quite conservatively to use less memory.
 It maybe be necessary raise it to 64 or higher to fully utilize a 1
@@ -57528,56 +58121,56 @@ T{
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 *
 T}@T{
 0x2A
 T}@T{
-\[uFF0A]
+＊
 T}
 T{
 :
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 ?
 T}@T{
 0x3F
 T}@T{
-\[uFF1F]
+？
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 |
 T}@T{
 0x7C
 T}@T{
-\[uFF5C]
+｜
 T}
 .TE
 .PP
@@ -57600,7 +58193,7 @@ T{
 T}@T{
 0x2E
 T}@T{
-\[uFF0E]
+．
 T}
 .TE
 .PP
@@ -57619,7 +58212,7 @@ Storage.
 Rclone tries them in the order of the sections below.
 .SS Env Auth
 .PP
-If the \f[C]env_auth\f[R] config parameter is \f[C]true\f[R] then rclone
+If the \f[V]env_auth\f[R] config parameter is \f[V]true\f[R] then rclone
 will pull credentials from the environment or runtime.
 .PP
 It tries these authentication methods in this order:
@@ -57633,7 +58226,7 @@ Azure CLI credentials (as used by the az tool)
 These are described in the following sections
 .SS Env Auth: 1. Environment Variables
 .PP
-If \f[C]env_auth\f[R] is set and environment variables are present
+If \f[V]env_auth\f[R] is set and environment variables are present
 rclone authenticates a service principal with a secret or certificate,
 or a user with a password, depending on which environment variable are
 set.
@@ -57642,30 +58235,30 @@ It reads configuration from these variables, in the following order:
 Service principal with client secret
 .RS 4
 .IP \[bu] 2
-\f[C]AZURE_TENANT_ID\f[R]: ID of the service principal\[aq]s tenant.
+\f[V]AZURE_TENANT_ID\f[R]: ID of the service principal\[aq]s tenant.
 Also called its \[dq]directory\[dq] ID.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_ID\f[R]: the service principal\[aq]s client ID
+\f[V]AZURE_CLIENT_ID\f[R]: the service principal\[aq]s client ID
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_SECRET\f[R]: one of the service principal\[aq]s client
+\f[V]AZURE_CLIENT_SECRET\f[R]: one of the service principal\[aq]s client
 secrets
 .RE
 .IP "2." 3
 Service principal with certificate
 .RS 4
 .IP \[bu] 2
-\f[C]AZURE_TENANT_ID\f[R]: ID of the service principal\[aq]s tenant.
+\f[V]AZURE_TENANT_ID\f[R]: ID of the service principal\[aq]s tenant.
 Also called its \[dq]directory\[dq] ID.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_ID\f[R]: the service principal\[aq]s client ID
+\f[V]AZURE_CLIENT_ID\f[R]: the service principal\[aq]s client ID
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_CERTIFICATE_PATH\f[R]: path to a PEM or PKCS12
+\f[V]AZURE_CLIENT_CERTIFICATE_PATH\f[R]: path to a PEM or PKCS12
 certificate file including the private key.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_CERTIFICATE_PASSWORD\f[R]: (optional) password for the
+\f[V]AZURE_CLIENT_CERTIFICATE_PASSWORD\f[R]: (optional) password for the
 certificate file.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_SEND_CERTIFICATE_CHAIN\f[R]: (optional) Specifies
+\f[V]AZURE_CLIENT_SEND_CERTIFICATE_CHAIN\f[R]: (optional) Specifies
 whether an authentication request will include an x5c header to support
 subject name / issuer based authentication.
 When set to \[dq]true\[dq] or \[dq]1\[dq], authentication requests
@@ -57675,29 +58268,29 @@ include the x5c header.
 User with username and password
 .RS 4
 .IP \[bu] 2
-\f[C]AZURE_TENANT_ID\f[R]: (optional) tenant to authenticate in.
+\f[V]AZURE_TENANT_ID\f[R]: (optional) tenant to authenticate in.
 Defaults to \[dq]organizations\[dq].
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_ID\f[R]: client ID of the application the user will
+\f[V]AZURE_CLIENT_ID\f[R]: client ID of the application the user will
 authenticate to
 .IP \[bu] 2
-\f[C]AZURE_USERNAME\f[R]: a username (usually an email address)
+\f[V]AZURE_USERNAME\f[R]: a username (usually an email address)
 .IP \[bu] 2
-\f[C]AZURE_PASSWORD\f[R]: the user\[aq]s password
+\f[V]AZURE_PASSWORD\f[R]: the user\[aq]s password
 .RE
 .IP "4." 3
 Workload Identity
 .RS 4
 .IP \[bu] 2
-\f[C]AZURE_TENANT_ID\f[R]: Tenant to authenticate in.
+\f[V]AZURE_TENANT_ID\f[R]: Tenant to authenticate in.
 .IP \[bu] 2
-\f[C]AZURE_CLIENT_ID\f[R]: Client ID of the application the user will
+\f[V]AZURE_CLIENT_ID\f[R]: Client ID of the application the user will
 authenticate to.
 .IP \[bu] 2
-\f[C]AZURE_FEDERATED_TOKEN_FILE\f[R]: Path to projected service account
+\f[V]AZURE_FEDERATED_TOKEN_FILE\f[R]: Path to projected service account
 token file.
 .IP \[bu] 2
-\f[C]AZURE_AUTHORITY_HOST\f[R]: Authority of an Azure Active Directory
+\f[V]AZURE_AUTHORITY_HOST\f[R]: Authority of an Azure Active Directory
 endpoint (default: login.microsoftonline.com).
 .RE
 .SS Env Auth: 2. Managed Service Identity Credentials
@@ -57708,12 +58301,12 @@ If the resource has no system-assigned but exactly one user-assigned
 identity, the user-assigned identity will be used by default.
 .PP
 If the resource has multiple user-assigned identities you will need to
-unset \f[C]env_auth\f[R] and set \f[C]use_msi\f[R] instead.
-See the \f[C]use_msi\f[R] section.
+unset \f[V]env_auth\f[R] and set \f[V]use_msi\f[R] instead.
+See the \f[V]use_msi\f[R] section.
 .SS Env Auth: 3. Azure CLI credentials (as used by the az tool)
 .PP
-Credentials created with the \f[C]az\f[R] tool can be picked up using
-\f[C]env_auth\f[R].
+Credentials created with the \f[V]az\f[R] tool can be picked up using
+\f[V]env_auth\f[R].
 .PP
 For example if you were to login with a service principal like this:
 .IP
@@ -57741,69 +58334,69 @@ rclone lsf --azurefiles-env-auth --azurefiles-account=ACCOUNT :azurefiles:
 .SS Account and Shared Key
 .PP
 This is the most straight forward and least flexible way.
-Just fill in the \f[C]account\f[R] and \f[C]key\f[R] lines and leave the
+Just fill in the \f[V]account\f[R] and \f[V]key\f[R] lines and leave the
 rest blank.
 .SS SAS URL
 .PP
-To use it leave \f[C]account\f[R], \f[C]key\f[R] and
-\f[C]connection_string\f[R] blank and fill in \f[C]sas_url\f[R].
+To use it leave \f[V]account\f[R], \f[V]key\f[R] and
+\f[V]connection_string\f[R] blank and fill in \f[V]sas_url\f[R].
 .SS Connection String
 .PP
-To use it leave \f[C]account\f[R], \f[C]key\f[R] and \[dq]sas_url\[dq]
-blank and fill in \f[C]connection_string\f[R].
+To use it leave \f[V]account\f[R], \f[V]key\f[R] and \[dq]sas_url\[dq]
+blank and fill in \f[V]connection_string\f[R].
 .SS Service principal with client secret
 .PP
 If these variables are set, rclone will authenticate with a service
 principal with a client secret.
 .IP \[bu] 2
-\f[C]tenant\f[R]: ID of the service principal\[aq]s tenant.
+\f[V]tenant\f[R]: ID of the service principal\[aq]s tenant.
 Also called its \[dq]directory\[dq] ID.
 .IP \[bu] 2
-\f[C]client_id\f[R]: the service principal\[aq]s client ID
+\f[V]client_id\f[R]: the service principal\[aq]s client ID
 .IP \[bu] 2
-\f[C]client_secret\f[R]: one of the service principal\[aq]s client
+\f[V]client_secret\f[R]: one of the service principal\[aq]s client
 secrets
 .PP
 The credentials can also be placed in a file using the
-\f[C]service_principal_file\f[R] configuration option.
+\f[V]service_principal_file\f[R] configuration option.
 .SS Service principal with certificate
 .PP
 If these variables are set, rclone will authenticate with a service
 principal with certificate.
 .IP \[bu] 2
-\f[C]tenant\f[R]: ID of the service principal\[aq]s tenant.
+\f[V]tenant\f[R]: ID of the service principal\[aq]s tenant.
 Also called its \[dq]directory\[dq] ID.
 .IP \[bu] 2
-\f[C]client_id\f[R]: the service principal\[aq]s client ID
+\f[V]client_id\f[R]: the service principal\[aq]s client ID
 .IP \[bu] 2
-\f[C]client_certificate_path\f[R]: path to a PEM or PKCS12 certificate
+\f[V]client_certificate_path\f[R]: path to a PEM or PKCS12 certificate
 file including the private key.
 .IP \[bu] 2
-\f[C]client_certificate_password\f[R]: (optional) password for the
+\f[V]client_certificate_password\f[R]: (optional) password for the
 certificate file.
 .IP \[bu] 2
-\f[C]client_send_certificate_chain\f[R]: (optional) Specifies whether an
+\f[V]client_send_certificate_chain\f[R]: (optional) Specifies whether an
 authentication request will include an x5c header to support subject
 name / issuer based authentication.
 When set to \[dq]true\[dq] or \[dq]1\[dq], authentication requests
 include the x5c header.
 .PP
-\f[B]NB\f[R] \f[C]client_certificate_password\f[R] must be obscured -
+\f[B]NB\f[R] \f[V]client_certificate_password\f[R] must be obscured -
 see rclone obscure (https://rclone.org/commands/rclone_obscure/).
 .SS User with username and password
 .PP
 If these variables are set, rclone will authenticate with username and
 password.
 .IP \[bu] 2
-\f[C]tenant\f[R]: (optional) tenant to authenticate in.
+\f[V]tenant\f[R]: (optional) tenant to authenticate in.
 Defaults to \[dq]organizations\[dq].
 .IP \[bu] 2
-\f[C]client_id\f[R]: client ID of the application the user will
+\f[V]client_id\f[R]: client ID of the application the user will
 authenticate to
 .IP \[bu] 2
-\f[C]username\f[R]: a username (usually an email address)
+\f[V]username\f[R]: a username (usually an email address)
 .IP \[bu] 2
-\f[C]password\f[R]: the user\[aq]s password
+\f[V]password\f[R]: the user\[aq]s password
 .PP
 Microsoft doesn\[aq]t recommend this kind of authentication, because
 it\[aq]s less secure than other authentication flows.
@@ -57813,23 +58406,23 @@ user or admin consent.
 This credential can only authenticate work and school accounts; it
 can\[aq]t authenticate Microsoft accounts.
 .PP
-\f[B]NB\f[R] \f[C]password\f[R] must be obscured - see rclone
+\f[B]NB\f[R] \f[V]password\f[R] must be obscured - see rclone
 obscure (https://rclone.org/commands/rclone_obscure/).
 .SS Managed Service Identity Credentials
 .PP
-If \f[C]use_msi\f[R] is set then managed service identity credentials
+If \f[V]use_msi\f[R] is set then managed service identity credentials
 are used.
 This authentication only works when running in an Azure service.
-\f[C]env_auth\f[R] needs to be unset to use this.
+\f[V]env_auth\f[R] needs to be unset to use this.
 .PP
 However if you have multiple user identities to choose from these must
 be explicitly specified using exactly one of the
-\f[C]msi_object_id\f[R], \f[C]msi_client_id\f[R], or
-\f[C]msi_mi_res_id\f[R] parameters.
+\f[V]msi_object_id\f[R], \f[V]msi_client_id\f[R], or
+\f[V]msi_mi_res_id\f[R] parameters.
 .PP
-If none of \f[C]msi_object_id\f[R], \f[C]msi_client_id\f[R], or
-\f[C]msi_mi_res_id\f[R] is set, this is is equivalent to using
-\f[C]env_auth\f[R].
+If none of \f[V]msi_object_id\f[R], \f[V]msi_client_id\f[R], or
+\f[V]msi_mi_res_id\f[R] is set, this is is equivalent to using
+\f[V]env_auth\f[R].
 .SS Standard options
 .PP
 Here are the Standard options specific to azurefiles (Microsoft Azure
@@ -57844,7 +58437,7 @@ Leave blank to use SAS URL or connection string, otherwise it needs to
 be set.
 .PP
 If this is blank and if env_auth is set it will be read from the
-environment variable \f[C]AZURE_STORAGE_ACCOUNT_NAME\f[R] if possible.
+environment variable \f[V]AZURE_STORAGE_ACCOUNT_NAME\f[R] if possible.
 .PP
 Properties:
 .IP \[bu] 2
@@ -58094,9 +58687,9 @@ pages for more details.
 appreciated!
 .PP
 It may be more convenient to put the credentials directly into the
-rclone config file under the \f[C]client_id\f[R], \f[C]tenant\f[R] and
-\f[C]client_secret\f[R] keys instead of setting
-\f[C]service_principal_file\f[R].
+rclone config file under the \f[V]client_id\f[R], \f[V]tenant\f[R] and
+\f[V]client_secret\f[R] keys instead of setting
+\f[V]service_principal_file\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -58243,10 +58836,10 @@ When rclone doesn\[aq]t know it uses this value instead.
 This will be used when rclone is streaming data, the most common uses
 are:
 .IP \[bu] 2
-Uploading files with \f[C]--vfs-cache-mode off\f[R] with
-\f[C]rclone mount\f[R]
+Uploading files with \f[V]--vfs-cache-mode off\f[R] with
+\f[V]rclone mount\f[R]
 .IP \[bu] 2
-Using \f[C]rclone rcat\f[R]
+Using \f[V]rclone rcat\f[R]
 .IP \[bu] 2
 Copying files with unknown length
 .PP
@@ -58294,7 +58887,7 @@ Type: string
 Required: false
 .SS Custom upload headers
 .PP
-You can set custom upload headers with the \f[C]--header-upload\f[R]
+You can set custom upload headers with the \f[V]--header-upload\f[R]
 flag.
 .IP \[bu] 2
 Cache-Control
@@ -58307,7 +58900,7 @@ Content-Language
 .IP \[bu] 2
 Content-Type
 .PP
-Eg \f[C]--header-upload \[dq]Content-Type: text/potato\[dq]\f[R]
+Eg \f[V]--header-upload \[dq]Content-Type: text/potato\[dq]\f[R]
 .SS Limitations
 .PP
 MD5 sums are only uploaded with chunked files if the source has an MD5
@@ -58315,17 +58908,17 @@ sum.
 This will always be the case for a local to azure copy.
 .SH Microsoft OneDrive
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 The initial setup for OneDrive involves getting a token from Microsoft
 which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -58420,10 +59013,10 @@ Note that rclone runs a webserver on your local machine to collect the
 token as returned from Microsoft.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this it may require you
 to unblock it temporarily if you are running a host firewall.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your OneDrive
 .IP
@@ -58451,7 +59044,7 @@ rclone copy /home/source remote:backup
 .SS Getting your own Client ID and Key
 .PP
 rclone uses a default Client ID when talking to OneDrive, unless a
-custom \f[C]client_id\f[R] is specified in the config.
+custom \f[V]client_id\f[R] is specified in the config.
 The default Client ID and Key are shared by all rclone users when
 performing requests.
 .PP
@@ -58464,35 +59057,35 @@ To create your own Client ID, please follow these steps:
 .IP "1." 3
 Open
 https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade
-and then click \f[C]New registration\f[R].
+and then click \f[V]New registration\f[R].
 .IP "2." 3
 Enter a name for your app, choose account type
-\f[C]Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)\f[R],
-select \f[C]Web\f[R] in \f[C]Redirect URI\f[R], then type (do not copy
-and paste) \f[C]http://localhost:53682/\f[R] and click Register.
-Copy and keep the \f[C]Application (client) ID\f[R] under the app name
+\f[V]Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)\f[R],
+select \f[V]Web\f[R] in \f[V]Redirect URI\f[R], then type (do not copy
+and paste) \f[V]http://localhost:53682/\f[R] and click Register.
+Copy and keep the \f[V]Application (client) ID\f[R] under the app name
 for later use.
 .IP "3." 3
-Under \f[C]manage\f[R] select \f[C]Certificates & secrets\f[R], click
-\f[C]New client secret\f[R].
-Enter a description (can be anything) and set \f[C]Expires\f[R] to 24
+Under \f[V]manage\f[R] select \f[V]Certificates & secrets\f[R], click
+\f[V]New client secret\f[R].
+Enter a description (can be anything) and set \f[V]Expires\f[R] to 24
 months.
 Copy and keep that secret \f[I]Value\f[R] for later use (you
 \f[I]won\[aq]t\f[R] be able to see this value afterwards).
 .IP "4." 3
-Under \f[C]manage\f[R] select \f[C]API permissions\f[R], click
-\f[C]Add a permission\f[R] and select \f[C]Microsoft Graph\f[R] then
-select \f[C]delegated permissions\f[R].
+Under \f[V]manage\f[R] select \f[V]API permissions\f[R], click
+\f[V]Add a permission\f[R] and select \f[V]Microsoft Graph\f[R] then
+select \f[V]delegated permissions\f[R].
 .IP "5." 3
-Search and select the following permissions: \f[C]Files.Read\f[R],
-\f[C]Files.ReadWrite\f[R], \f[C]Files.Read.All\f[R],
-\f[C]Files.ReadWrite.All\f[R], \f[C]offline_access\f[R],
-\f[C]User.Read\f[R] and \f[C]Sites.Read.All\f[R] (if custom access
+Search and select the following permissions: \f[V]Files.Read\f[R],
+\f[V]Files.ReadWrite\f[R], \f[V]Files.Read.All\f[R],
+\f[V]Files.ReadWrite.All\f[R], \f[V]offline_access\f[R],
+\f[V]User.Read\f[R] and \f[V]Sites.Read.All\f[R] (if custom access
 scopes are configured, select the permissions accordingly).
-Once selected click \f[C]Add permissions\f[R] at the bottom.
+Once selected click \f[V]Add permissions\f[R] at the bottom.
 .PP
 Now the application is complete.
-Run \f[C]rclone config\f[R] to create or edit a OneDrive remote.
+Run \f[V]rclone config\f[R] to create or edit a OneDrive remote.
 Supply the app ID and password as Client ID and Secret, respectively.
 rclone will walk you through the remaining steps.
 .PP
@@ -58502,12 +59095,12 @@ See Microsoft
 Docs (https://docs.microsoft.com/en-us/graph/permissions-reference#files-permissions)
 for more information about the different scopes.
 .PP
-The \f[C]Sites.Read.All\f[R] permission is required if you need to
+The \f[V]Sites.Read.All\f[R] permission is required if you need to
 search SharePoint sites when configuring the
 remote (https://github.com/rclone/rclone/pull/5883).
 However, if that permission is not assigned, you need to exclude
-\f[C]Sites.Read.All\f[R] from your access scopes or set
-\f[C]disable_site_permission\f[R] option to true in the advanced
+\f[V]Sites.Read.All\f[R] from your access scopes or set
+\f[V]disable_site_permission\f[R] option to true in the advanced
 options.
 .SS Creating Client ID for OneDrive Business
 .PP
@@ -58523,18 +59116,18 @@ Make sure to create the App with your business account.
 .IP "2." 3
 Follow the steps above to create an App.
 However, we need a different account type here:
-\f[C]Accounts in this organizational directory only (*** - Single tenant)\f[R].
+\f[V]Accounts in this organizational directory only (*** - Single tenant)\f[R].
 Note that you can also change the account type after creating the App.
 .IP "3." 3
 Find the tenant
 ID (https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-to-find-tenant)
 of your organization.
 .IP "4." 3
-In the rclone config, set \f[C]auth_url\f[R] to
-\f[C]https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/authorize\f[R].
+In the rclone config, set \f[V]auth_url\f[R] to
+\f[V]https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/authorize\f[R].
 .IP "5." 3
-In the rclone config, set \f[C]token_url\f[R] to
-\f[C]https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/token\f[R].
+In the rclone config, set \f[V]token_url\f[R] to
+\f[V]https://login.microsoftonline.com/YOUR_TENANT_ID/oauth2/v2.0/token\f[R].
 .PP
 Note: If you have a special region, you may need a different host in
 step 4 and 5.
@@ -58550,26 +59143,26 @@ OneDrive Personal, OneDrive for Business and Sharepoint Server support
 QuickXorHash (https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash).
 .PP
 Before rclone 1.62 the default hash for Onedrive Personal was
-\f[C]SHA1\f[R].
+\f[V]SHA1\f[R].
 For rclone 1.62 and above the default for all Onedrive backends is
-\f[C]QuickXorHash\f[R].
+\f[V]QuickXorHash\f[R].
 .PP
-Starting from July 2023 \f[C]SHA1\f[R] support is being phased out in
-Onedrive Personal in favour of \f[C]QuickXorHash\f[R].
-If necessary the \f[C]--onedrive-hash-type\f[R] flag (or
-\f[C]hash_type\f[R] config option) can be used to select \f[C]SHA1\f[R]
+Starting from July 2023 \f[V]SHA1\f[R] support is being phased out in
+Onedrive Personal in favour of \f[V]QuickXorHash\f[R].
+If necessary the \f[V]--onedrive-hash-type\f[R] flag (or
+\f[V]hash_type\f[R] config option) can be used to select \f[V]SHA1\f[R]
 during the transition period if this is important your workflow.
 .PP
-For all types of OneDrive you can use the \f[C]--checksum\f[R] flag.
+For all types of OneDrive you can use the \f[V]--checksum\f[R] flag.
 .SS --fast-list
 .PP
-This remote supports \f[C]--fast-list\f[R] which allows you to use fewer
+This remote supports \f[V]--fast-list\f[R] which allows you to use fewer
 transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
 .PP
-This must be enabled with the \f[C]--onedrive-delta\f[R] flag (or
-\f[C]delta = true\f[R] in the config file) as it can cause performance
+This must be enabled with the \f[V]--onedrive-delta\f[R] flag (or
+\f[V]delta = true\f[R] in the config file) as it can cause performance
 degradation.
 .PP
 It does this by using the delta listing facilities of OneDrive which
@@ -58578,18 +59171,18 @@ This is much more efficient than listing directories recursively and is
 Microsoft\[aq]s recommended way of reading all the file information from
 a drive.
 .PP
-This can be useful with \f[C]rclone mount\f[R] and rclone rc vfs/refresh
+This can be useful with \f[V]rclone mount\f[R] and rclone rc vfs/refresh
 recursive=true (https://rclone.org/rc/#vfs-refresh)) to very quickly
 fill the mount with information about all the files.
 .PP
-The API used for the recursive listing (\f[C]ListR\f[R]) only supports
+The API used for the recursive listing (\f[V]ListR\f[R]) only supports
 listing from the root of the drive.
 This will become increasingly inefficient the further away you get from
 the root as rclone will have to discard files outside of the directory
 you are using.
 .PP
-Some commands (like \f[C]rclone lsf -R\f[R]) will use \f[C]ListR\f[R] by
-default - you can turn this off with \f[C]--disable ListR\f[R] if you
+Some commands (like \f[V]rclone lsf -R\f[R]) will use \f[V]ListR\f[R] by
+default - you can turn this off with \f[V]--disable ListR\f[R] if you
 need to.
 .SS Restricted filename characters
 .PP
@@ -58613,56 +59206,56 @@ T{
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 *
 T}@T{
 0x2A
 T}@T{
-\[uFF0A]
+＊
 T}
 T{
 :
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 ?
 T}@T{
 0x3F
 T}@T{
-\[uFF1F]
+？
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 |
 T}@T{
 0x7C
 T}@T{
-\[uFF5C]
+｜
 T}
 .TE
 .PP
@@ -58685,14 +59278,14 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 T{
 \&.
 T}@T{
 0x2E
 T}@T{
-\[uFF0E]
+．
 T}
 .TE
 .PP
@@ -58715,14 +59308,14 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 T{
 \[ti]
 T}@T{
 0x7E
 T}@T{
-\[uFF5E]
+～
 T}
 .TE
 .PP
@@ -59278,7 +59871,7 @@ Default: false
 .PP
 If set rclone will use delta listing to implement recursive listings.
 .PP
-If this flag is set the onedrive backend will advertise \f[C]ListR\f[R]
+If this flag is set the onedrive backend will advertise \f[V]ListR\f[R]
 support for recursive listings.
 .PP
 Setting this flag speeds up these things greatly:
@@ -59300,14 +59893,14 @@ So it will be correct but may not be very efficient.
 This is why this flag is not set as the default.
 .PP
 As a rule of thumb if nearly all of your data is under rclone\[aq]s root
-directory (the \f[C]root/directory\f[R] in
-\f[C]onedrive:root/directory\f[R]) then using this flag will be be a big
+directory (the \f[V]root/directory\f[R] in
+\f[V]onedrive:root/directory\f[R]) then using this flag will be be a big
 performance win.
 If your data is mostly not under the root then using this flag will be a
 big performance loss.
 .PP
 It is recommended if you are mounting your onedrive at the root (or near
-the root when using crypt) and using rclone \f[C]rc vfs/refresh\f[R].
+the root when using crypt) and using rclone \f[V]rc vfs/refresh\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -59406,16 +59999,16 @@ Much of the metadata is read-only, and there are some differences
 between OneDrive Personal and Business (see table below for details).
 .PP
 Permissions are also supported, if
-\f[C]--onedrive-metadata-permissions\f[R] is set.
-The accepted values for \f[C]--onedrive-metadata-permissions\f[R] are
-\[dq]\f[C]read\f[R]\[dq], \[dq]\f[C]write\f[R]\[dq],
-\[dq]\f[C]read,write\f[R]\[dq], and \[dq]\f[C]off\f[R]\[dq] (the
+\f[V]--onedrive-metadata-permissions\f[R] is set.
+The accepted values for \f[V]--onedrive-metadata-permissions\f[R] are
+\[dq]\f[V]read\f[R]\[dq], \[dq]\f[V]write\f[R]\[dq],
+\[dq]\f[V]read,write\f[R]\[dq], and \[dq]\f[V]off\f[R]\[dq] (the
 default).
-\[dq]\f[C]write\f[R]\[dq] supports adding new permissions, updating the
+\[dq]\f[V]write\f[R]\[dq] supports adding new permissions, updating the
 \[dq]role\[dq] of existing permissions, and removing permissions.
 Updating and removing require the Permission ID to be known, so it is
-recommended to use \[dq]\f[C]read,write\f[R]\[dq] instead of
-\[dq]\f[C]write\f[R]\[dq] if you wish to update/remove permissions.
+recommended to use \[dq]\f[V]read,write\f[R]\[dq] instead of
+\[dq]\f[V]write\f[R]\[dq] if you wish to update/remove permissions.
 .PP
 Permissions are read/written in JSON format using the same schema as the
 OneDrive
@@ -59499,20 +60092,20 @@ Example for OneDrive Business:
 To write permissions, pass in a \[dq]permissions\[dq] metadata key using
 this same format.
 The
-\f[C]--metadata-mapper\f[R] (https://rclone.org/docs/#metadata-mapper)
+\f[V]--metadata-mapper\f[R] (https://rclone.org/docs/#metadata-mapper)
 tool can be very helpful for this.
 .PP
 When adding permissions, an email address can be provided in the
-\f[C]User.ID\f[R] or \f[C]DisplayName\f[R] properties of
-\f[C]grantedTo\f[R] or \f[C]grantedToIdentities\f[R].
-Alternatively, an ObjectID can be provided in \f[C]User.ID\f[R].
+\f[V]User.ID\f[R] or \f[V]DisplayName\f[R] properties of
+\f[V]grantedTo\f[R] or \f[V]grantedToIdentities\f[R].
+Alternatively, an ObjectID can be provided in \f[V]User.ID\f[R].
 At least one valid recipient must be provided in order to add a
 permission for a user.
-Creating a Public Link is also supported, if \f[C]Link.Scope\f[R] is set
-to \f[C]\[dq]anonymous\[dq]\f[R].
+Creating a Public Link is also supported, if \f[V]Link.Scope\f[R] is set
+to \f[V]\[dq]anonymous\[dq]\f[R].
 .PP
 Example request to add a \[dq]read\[dq] permission with
-\f[C]--metadata-mapper\f[R]:
+\f[V]--metadata-mapper\f[R]:
 .IP
 .nf
 \f[C]
@@ -59528,20 +60121,21 @@ Note that adding a permission can fail if a conflicting permission
 already exists for the file/folder.
 .PP
 To update an existing permission, include both the Permission ID and the
-new \f[C]roles\f[R] to be assigned.
-\f[C]roles\f[R] is the only property that can be changed.
+new \f[V]roles\f[R] to be assigned.
+\f[V]roles\f[R] is the only property that can be changed.
 .PP
 To remove permissions, pass in a blob containing only the permissions
-you wish to keep (which can be empty, to remove all.) Note that the
-\f[C]owner\f[R] role will be ignored, as it cannot be removed.
+you wish to keep (which can be empty, to remove all.)
+Note that the \f[V]owner\f[R] role will be ignored, as it cannot be
+removed.
 .PP
 Note that both reading and writing permissions requires extra API calls,
 so if you don\[aq]t need to read or write permissions it is recommended
-to omit \f[C]--onedrive-metadata-permissions\f[R].
+to omit \f[V]--onedrive-metadata-permissions\f[R].
 .PP
 Metadata and permissions are supported for Folders (directories) as well
 as Files.
-Note that setting the \f[C]mtime\f[R] or \f[C]btime\f[R] on a Folder
+Note that setting the \f[V]mtime\f[R] or \f[V]btime\f[R] on a Folder
 requires one extra API call on OneDrive Business only.
 .PP
 OneDrive does not currently support User Metadata.
@@ -59778,7 +60372,7 @@ See the metadata (https://rclone.org/docs/#metadata) docs for more info.
 If you don\[aq]t use rclone for 90 days the refresh token will expire.
 This will result in authorization problems.
 This is easy to fix by running the
-\f[C]rclone config reconnect remote:\f[R] command to get a new token and
+\f[V]rclone config reconnect remote:\f[R] command to get a new token and
 refresh token.
 .SS Naming
 .PP
@@ -59791,8 +60385,8 @@ These can\[aq]t occur on Windows platforms, but on non-Windows platforms
 they are common.
 Rclone will map these names to and from an identical looking unicode
 equivalent.
-For example if a file has a \f[C]?\f[R] in it will be mapped to
-\f[C]\[uFF1F]\f[R] instead.
+For example if a file has a \f[V]?\f[R] in it will be mapped to
+\f[V]？\f[R] instead.
 .SS File sizes
 .PP
 The largest allowed file size is 250 GiB for both OneDrive Personal and
@@ -59809,7 +60403,7 @@ typically longer than the original ones.
 .PP
 OneDrive seems to be OK with at least 50,000 files in a folder, but at
 100,000 rclone will get errors listing the directory like
-\f[C]couldn\[cq]t list files: UnknownError:\f[R].
+\f[V]couldn\[cq]t list files: UnknownError:\f[R].
 See #2707 (https://github.com/rclone/rclone/issues/2707) for more info.
 .PP
 An official document about the limitations for different types of
@@ -59823,21 +60417,21 @@ This counts against a users quota.
 For example changing the modification time of a file creates a second
 version, so the file apparently uses twice the space.
 .PP
-For example the \f[C]copy\f[R] command is affected by this as rclone
+For example the \f[V]copy\f[R] command is affected by this as rclone
 copies the file and then afterwards sets the modification time to match
 the source file which uses another version.
 .PP
-You can use the \f[C]rclone cleanup\f[R] command (see below) to remove
+You can use the \f[V]rclone cleanup\f[R] command (see below) to remove
 all old versions.
 .PP
-Or you can set the \f[C]no_versions\f[R] parameter to \f[C]true\f[R] and
+Or you can set the \f[V]no_versions\f[R] parameter to \f[V]true\f[R] and
 rclone will remove versions after operations which create new versions.
 This takes extra transactions so only enable it if you need it.
 .PP
 \f[B]Note\f[R] At the time of writing Onedrive Personal creates versions
 (but not for setting the modification time) but the API for removing
 them returns \[dq]API not found\[dq] so cleanup and
-\f[C]no_versions\f[R] should not be used on Onedrive Personal.
+\f[V]no_versions\f[R] should not be used on Onedrive Personal.
 .SS Disabling versioning
 .PP
 Starting October 2018, users will no longer be able to disable
@@ -59850,22 +60444,22 @@ be run by a SharePoint admin.
 If you are an admin, you can run these commands in PowerShell to change
 that setting:
 .IP "1." 3
-\f[C]Install-Module -Name Microsoft.Online.SharePoint.PowerShell\f[R]
+\f[V]Install-Module -Name Microsoft.Online.SharePoint.PowerShell\f[R]
 (in case you haven\[aq]t installed this already)
 .IP "2." 3
-\f[C]Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking\f[R]
+\f[V]Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking\f[R]
 .IP "3." 3
-\f[C]Connect-SPOService -Url https://YOURSITE-admin.sharepoint.com -Credential YOU\[at]YOURSITE.COM\f[R]
-(replacing \f[C]YOURSITE\f[R], \f[C]YOU\f[R], \f[C]YOURSITE.COM\f[R]
+\f[V]Connect-SPOService -Url https://YOURSITE-admin.sharepoint.com -Credential YOU\[at]YOURSITE.COM\f[R]
+(replacing \f[V]YOURSITE\f[R], \f[V]YOU\f[R], \f[V]YOURSITE.COM\f[R]
 with the actual values; this will prompt for your credentials)
 .IP "4." 3
-\f[C]Set-SPOTenant -EnableMinimumVersionRequirement $False\f[R]
+\f[V]Set-SPOTenant -EnableMinimumVersionRequirement $False\f[R]
 .IP "5." 3
-\f[C]Disconnect-SPOService\f[R] (to disconnect from the server)
+\f[V]Disconnect-SPOService\f[R] (to disconnect from the server)
 .PP
-\f[I]Below are the steps for normal users to disable versioning. If you
-don\[aq]t see the \[dq]No Versioning\[dq] option, make sure the above
-requirements are met.\f[R]
+\f[I]Below are the steps for normal users to disable versioning.
+If you don\[aq]t see the \[dq]No Versioning\[dq] option, make sure the
+above requirements are met.\f[R]
 .PP
 User Weropol (https://github.com/Weropol) has found a method to disable
 versioning on OneDrive
@@ -59896,14 +60490,14 @@ Restore the versioning settings after using rclone.
 (Optional)
 .SS Cleanup
 .PP
-OneDrive supports \f[C]rclone cleanup\f[R] which causes rclone to look
+OneDrive supports \f[V]rclone cleanup\f[R] which causes rclone to look
 through every file under the path supplied and delete all version but
 the current version.
 Because this involves traversing all the files, then querying each file
 for versions it can be quite slow.
-Rclone does \f[C]--checkers\f[R] tests in parallel.
-The command also supports \f[C]--interactive\f[R]/\f[C]i\f[R] or
-\f[C]--dry-run\f[R] which is a great way to see what it would do.
+Rclone does \f[V]--checkers\f[R] tests in parallel.
+The command also supports \f[V]--interactive\f[R]/\f[V]i\f[R] or
+\f[V]--dry-run\f[R] which is a great way to see what it would do.
 .IP
 .nf
 \f[C]
@@ -59918,7 +60512,7 @@ rclone cleanup remote:path/subdir               # unconditionally remove all old
 .PP
 If you experience excessive throttling or is being blocked on SharePoint
 then it may help to set the user agent explicitly with a flag like this:
-\f[C]--user-agent \[dq]ISV|rclone.org|rclone/v1.55.1\[dq]\f[R]
+\f[V]--user-agent \[dq]ISV|rclone.org|rclone/v1.55.1\[dq]\f[R]
 .PP
 The specific details can be found in the Microsoft document: Avoid
 getting throttled or blocked in SharePoint
@@ -59960,13 +60554,14 @@ known (https://github.com/OneDrive/onedrive-api-docs/issues/1068) issue
 that Sharepoint (not OneDrive or OneDrive for Business) may return
 \[dq]item not found\[dq] errors when users try to replace or delete
 uploaded files; this seems to mainly affect Office files (.docx, .xlsx,
-etc.) and web files (.html, .aspx, etc.).
-As a workaround, you may use the \f[C]--backup-dir <BACKUP_DIR>\f[R]
+etc.)
+and web files (.html, .aspx, etc.).
+As a workaround, you may use the \f[V]--backup-dir <BACKUP_DIR>\f[R]
 command line argument so rclone moves the files to be replaced/deleted
 into a given backup directory (instead of directly replacing/deleting
 them).
 For example, to instruct rclone to move the files into the directory
-\f[C]rclone-backup-dir\f[R] on backend \f[C]mysharepoint\f[R], you may
+\f[V]rclone-backup-dir\f[R] on backend \f[V]mysharepoint\f[R], you may
 use:
 .IP
 .nf
@@ -60002,23 +60597,23 @@ Description: Due to a configuration change made by your administrator, or becaus
 .PP
 If you see the error above after enabling multi-factor authentication
 for your account, you can fix it by refreshing your OAuth refresh token.
-To do that, run \f[C]rclone config\f[R], and choose to edit your
+To do that, run \f[V]rclone config\f[R], and choose to edit your
 OneDrive backend.
 Then, you don\[aq]t need to actually make any changes until you reach
-this question: \f[C]Already have a token - refresh?\f[R].
-For this question, answer \f[C]y\f[R] and go through the process to
+this question: \f[V]Already have a token - refresh?\f[R].
+For this question, answer \f[V]y\f[R] and go through the process to
 refresh your token, just like the first time the backend is configured.
 After this, rclone should work again for this backend.
 .SS Invalid request when making public links
 .PP
-On Sharepoint and OneDrive for Business, \f[C]rclone link\f[R] may
+On Sharepoint and OneDrive for Business, \f[V]rclone link\f[R] may
 return an \[dq]Invalid request\[dq] error.
 A possible cause is that the organisation admin didn\[aq]t allow public
 links to be made for the organisation/sharepoint library.
 To fix the permissions as an admin, take a look at the docs:
 1 (https://docs.microsoft.com/en-us/sharepoint/turn-external-sharing-on-or-off),
 2 (https://support.microsoft.com/en-us/office/set-up-and-manage-access-requests-94b26e0b-2822-49d4-929a-8455698654b3).
-.SS Can not access \f[C]Shared\f[R] with me files
+.SS Can not access \f[V]Shared\f[R] with me files
 .PP
 Shared with me files is not supported by rclone
 currently (https://github.com/rclone/rclone/issues/4062), but there is a
@@ -60026,11 +60621,11 @@ workaround:
 .IP "1." 3
 Visit https://onedrive.live.com (https://onedrive.live.com/)
 .IP "2." 3
-Right click a item in \f[C]Shared\f[R], then click
-\f[C]Add shortcut to My files\f[R] in the context
+Right click a item in \f[V]Shared\f[R], then click
+\f[V]Add shortcut to My files\f[R] in the context
 [IMAGE: make_shortcut (https://user-images.githubusercontent.com/60313789/206118040-7e762b3b-aa61-41a1-8649-cc18889f3572.png)]
 .IP "3." 3
-The shortcut will appear in \f[C]My files\f[R], you can access it with
+The shortcut will appear in \f[V]My files\f[R], you can access it with
 rclone, it behaves like a normal folder/file.
 [IMAGE: in_my_files (https://i.imgur.com/0S8H3li.png)]
 [IMAGE: rclone_mount (https://i.imgur.com/2Iq66sW.png)]
@@ -60052,7 +60647,7 @@ the size displayed in the web interface.
 The downloaded file is smaller because it only contains a single frame
 (still photo) extracted from the Live Photo (movie) stored in OneDrive.
 .PP
-The different sizes will cause \f[C]rclone copy/sync\f[R] to repeatedly
+The different sizes will cause \f[V]rclone copy/sync\f[R] to repeatedly
 recopy unmodified photos something like this:
 .IP
 .nf
@@ -60063,12 +60658,12 @@ INFO  : 20230203_123826234_iOS.heic: Copied (replaced existing)
 \f[R]
 .fi
 .PP
-These recopies can be worked around by adding \f[C]--ignore-size\f[R].
+These recopies can be worked around by adding \f[V]--ignore-size\f[R].
 Please note that this workaround only syncs the still-picture not the
 movie clip, and relies on modification dates being correctly updated on
 all files in all situations.
 .PP
-The different sizes will also cause \f[C]rclone check\f[R] to report
+The different sizes will also cause \f[V]rclone check\f[R] to report
 size errors something like this:
 .IP
 .nf
@@ -60077,9 +60672,9 @@ ERROR : 20230203_123826234_iOS.heic: sizes differ
 \f[R]
 .fi
 .PP
-These check errors can be suppressed by adding \f[C]--ignore-size\f[R].
+These check errors can be suppressed by adding \f[V]--ignore-size\f[R].
 .PP
-The different sizes will also cause \f[C]rclone mount\f[R] to fail
+The different sizes will also cause \f[V]rclone mount\f[R] to fail
 downloading with an error something like this:
 .IP
 .nf
@@ -60088,7 +60683,7 @@ ERROR : 20230203_123826234_iOS.heic: ReadFileHandle.Read error: low level retry
 \f[R]
 .fi
 .PP
-or like this when using \f[C]--cache-mode=full\f[R]:
+or like this when using \f[V]--cache-mode=full\f[R]:
 .IP
 .nf
 \f[C]
@@ -60098,13 +60693,13 @@ ERROR : 20230203_123826234_iOS.heic: vfs cache: failed to download: vfs reader:
 .fi
 .SH OpenDrive
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -60200,70 +60795,70 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 T{
 \[dq]
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 *
 T}@T{
 0x2A
 T}@T{
-\[uFF0A]
+＊
 T}
 T{
 :
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 ?
 T}@T{
 0x3F
 T}@T{
-\[uFF1F]
+？
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 |
 T}@T{
 0x7C
 T}@T{
-\[uFF5C]
+｜
 T}
 .TE
 .PP
@@ -60287,35 +60882,35 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 T{
 HT
 T}@T{
 0x09
 T}@T{
-\[u2409]
+␉
 T}
 T{
 LF
 T}@T{
 0x0A
 T}@T{
-\[u240A]
+␊
 T}
 T{
 VT
 T}@T{
 0x0B
 T}@T{
-\[u240B]
+␋
 T}
 T{
 CR
 T}@T{
 0x0D
 T}@T{
-\[u240D]
+␍
 T}
 .TE
 .PP
@@ -60414,12 +61009,12 @@ These can\[aq]t occur on Windows platforms, but on non-Windows platforms
 they are common.
 Rclone will map these names to and from an identical looking unicode
 equivalent.
-For example if a file has a \f[C]?\f[R] in it will be mapped to
-\f[C]\[uFF1F]\f[R] instead.
+For example if a file has a \f[V]?\f[R] in it will be mapped to
+\f[V]？\f[R] instead.
 .PP
-\f[C]rclone about\f[R] is not supported by the OpenDrive backend.
+\f[V]rclone about\f[R] is not supported by the OpenDrive backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -60436,20 +61031,21 @@ FAQ (https://www.oracle.com/cloud/storage/object-storage/faq/)
 Oracle Object Storage
 Limits (https://docs.oracle.com/en-us/iaas/Content/Resources/Assets/whitepapers/oci-object-storage-best-practices.pdf)
 .PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:bucket/path/to/dir\f[R].
+Paths are specified as \f[V]remote:bucket\f[R] (or \f[V]remote:\f[R] for
+the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:bucket/path/to/dir\f[R].
 .PP
 Sample command to transfer local artifacts to remote:bucket in oracle
 object storage:
 .PP
-\f[C]rclone -vvv  --progress --stats-one-line --max-stats-groups 10 --log-format date,time,UTC,longfile --fast-list --buffer-size 256Mi --oos-no-check-bucket --oos-upload-cutoff 10Mi --multi-thread-cutoff 16Mi --multi-thread-streams 3000 --transfers 3000 --checkers 64  --retries 2  --oos-chunk-size 10Mi --oos-upload-concurrency 10000  --oos-attempt-resume-upload --oos-leave-parts-on-error sync ./artifacts  remote:bucket -vv\f[R]
+\f[V]rclone -vvv  --progress --stats-one-line --max-stats-groups 10 --log-format date,time,UTC,longfile --fast-list --buffer-size 256Mi --oos-no-check-bucket --oos-upload-cutoff 10Mi --multi-thread-cutoff 16Mi --multi-thread-streams 3000 --transfers 3000 --checkers 64  --retries 2  --oos-chunk-size 10Mi --oos-upload-concurrency 10000  --oos-attempt-resume-upload --oos-leave-parts-on-error sync ./artifacts  remote:bucket -vv\f[R]
 .SS Configuration
 .PP
 Here is an example of making an oracle object storage configuration.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -60737,7 +61333,7 @@ provider = no_auth
 .SS Modification times and hashes
 .PP
 The modification time is stored as metadata on the object as
-\f[C]opc-meta-mtime\f[R] as floating point since the epoch, accurate to
+\f[V]opc-meta-mtime\f[R] as floating point since the epoch, accurate to
 1 ns.
 .PP
 If the modification time needs to be updated rclone will attempt to
@@ -60747,7 +61343,7 @@ In the case the object is larger than 5Gb, the object will be uploaded
 rather than copied.
 .PP
 Note that reading this from the object takes an additional
-\f[C]HEAD\f[R] request as the metadata isn\[aq]t returned in object
+\f[V]HEAD\f[R] request as the metadata isn\[aq]t returned in object
 listings.
 .PP
 The MD5 hash algorithm is supported.
@@ -60760,16 +61356,16 @@ Note that files uploaded \f[I]both\f[R] with multipart upload
 \f[I]and\f[R] through crypt remotes do not have MD5 sums.
 .PP
 rclone switches from single part uploads to multipart uploads at the
-point specified by \f[C]--oos-upload-cutoff\f[R].
+point specified by \f[V]--oos-upload-cutoff\f[R].
 This can be a maximum of 5 GiB and a minimum of 0 (ie always upload
 multipart files).
 .PP
 The chunk sizes used in the multipart upload are specified by
-\f[C]--oos-chunk-size\f[R] and the number of chunks uploaded
-concurrently is specified by \f[C]--oos-upload-concurrency\f[R].
+\f[V]--oos-chunk-size\f[R] and the number of chunks uploaded
+concurrently is specified by \f[V]--oos-upload-concurrency\f[R].
 .PP
-Multipart uploads will use \f[C]--transfers\f[R] *
-\f[C]--oos-upload-concurrency\f[R] * \f[C]--oos-chunk-size\f[R] extra
+Multipart uploads will use \f[V]--transfers\f[R] *
+\f[V]--oos-upload-concurrency\f[R] * \f[V]--oos-chunk-size\f[R] extra
 memory.
 Single part uploads to not use extra memory.
 .PP
@@ -60777,8 +61373,8 @@ Single part transfers can be faster than multipart transfers or slower
 depending on your latency from oos - the more latency, the more likely
 single part transfers will be faster.
 .PP
-Increasing \f[C]--oos-upload-concurrency\f[R] will increase throughput
-(8 would be a sensible value) and increasing \f[C]--oos-chunk-size\f[R]
+Increasing \f[V]--oos-upload-concurrency\f[R] will increase throughput
+(8 would be a sensible value) and increasing \f[V]--oos-chunk-size\f[R]
 also increases throughput (16M would be sensible).
 Increasing either of these will use more memory.
 The default values are high enough to gain most of the possible
@@ -61549,9 +62145,10 @@ Default is 24 hrs.
 .SS Mounting Buckets (https://rclone.org/oracleobjectstorage/tutorial_mount/)
 .SH QingStor
 .PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:bucket/path/to/dir\f[R].
+Paths are specified as \f[V]remote:bucket\f[R] (or \f[V]remote:\f[R] for
+the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:bucket/path/to/dir\f[R].
 .SS Configuration
 .PP
 Here is an example of making an QingStor configuration.
@@ -61626,7 +62223,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this
+This remote is called \f[V]remote\f[R] and can now be used like this
 .PP
 See all buckets
 .IP
@@ -61652,7 +62249,7 @@ rclone ls remote:bucket
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote bucket, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote bucket, deleting any
 excess files in the bucket.
 .IP
 .nf
@@ -61662,7 +62259,7 @@ rclone sync --interactive /home/local/directory remote:bucket
 .fi
 .SS --fast-list
 .PP
-This remote supports \f[C]--fast-list\f[R] which allows you to use fewer
+This remote supports \f[V]--fast-list\f[R] which allows you to use fewer
 transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
@@ -61673,44 +62270,44 @@ upload files bigger than 5 GiB.
 Note that files uploaded with multipart upload don\[aq]t have an MD5SUM.
 .PP
 Note that incomplete multipart uploads older than 24 hours can be
-removed with \f[C]rclone cleanup remote:bucket\f[R] just for one bucket
-\f[C]rclone cleanup remote:\f[R] for all buckets.
+removed with \f[V]rclone cleanup remote:bucket\f[R] just for one bucket
+\f[V]rclone cleanup remote:\f[R] for all buckets.
 QingStor does not ever remove incomplete multipart uploads so it may be
 necessary to run this from time to time.
 .SS Buckets and Zone
 .PP
-With QingStor you can list buckets (\f[C]rclone lsd\f[R]) using any
+With QingStor you can list buckets (\f[V]rclone lsd\f[R]) using any
 zone, but you can only access the content of a bucket from the zone it
 was created in.
 If you attempt to access a bucket from the wrong zone, you will get an
 error,
-\f[C]incorrect zone, the bucket is not in \[aq]XXX\[aq] zone\f[R].
+\f[V]incorrect zone, the bucket is not in \[aq]XXX\[aq] zone\f[R].
 .SS Authentication
 .PP
-There are two ways to supply \f[C]rclone\f[R] with a set of QingStor
+There are two ways to supply \f[V]rclone\f[R] with a set of QingStor
 credentials.
 In order of precedence:
 .IP \[bu] 2
 Directly in the rclone configuration file (as configured by
-\f[C]rclone config\f[R])
+\f[V]rclone config\f[R])
 .RS 2
 .IP \[bu] 2
-set \f[C]access_key_id\f[R] and \f[C]secret_access_key\f[R]
+set \f[V]access_key_id\f[R] and \f[V]secret_access_key\f[R]
 .RE
 .IP \[bu] 2
 Runtime configuration:
 .RS 2
 .IP \[bu] 2
-set \f[C]env_auth\f[R] to \f[C]true\f[R] in the config file
+set \f[V]env_auth\f[R] to \f[V]true\f[R] in the config file
 .IP \[bu] 2
 Exporting the following environment variables before running
-\f[C]rclone\f[R]
+\f[V]rclone\f[R]
 .RS 2
 .IP \[bu] 2
-Access Key ID: \f[C]QS_ACCESS_KEY_ID\f[R] or \f[C]QS_ACCESS_KEY\f[R]
+Access Key ID: \f[V]QS_ACCESS_KEY_ID\f[R] or \f[V]QS_ACCESS_KEY\f[R]
 .IP \[bu] 2
-Secret Access Key: \f[C]QS_SECRET_ACCESS_KEY\f[R] or
-\f[C]QS_SECRET_KEY\f[R]
+Secret Access Key: \f[V]QS_SECRET_ACCESS_KEY\f[R] or
+\f[V]QS_SECRET_KEY\f[R]
 .RE
 .RE
 .SS Restricted filename characters
@@ -61956,9 +62553,9 @@ Type: string
 Required: false
 .SS Limitations
 .PP
-\f[C]rclone about\f[R] is not supported by the qingstor backend.
+\f[V]rclone about\f[R] is not supported by the qingstor backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -61969,14 +62566,14 @@ about (https://rclone.org/commands/rclone_about/)
 Quatrix by Maytech is Quatrix Secure Compliant File Sharing |
 Maytech (https://www.maytech.net/products/quatrix-business).
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.,
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .PP
 The initial setup for Quatrix involves getting an API Key from Quatrix.
 You can get the API key in the user\[aq]s profile at
-\f[C]https://<account>/profile/api-keys\f[R] or with the help of the API
+\f[V]https://<account>/profile/api-keys\f[R] or with the help of the API
 -
 https://docs.maytech.net/quatrix/quatrix-api/api-explorer#/API-Key/post_api_key_create.
 .PP
@@ -61984,7 +62581,7 @@ See complete Swagger documentation for Quatrix -
 https://docs.maytech.net/quatrix/quatrix-api/api-explorer
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -62028,7 +62625,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Quatrix
 .IP
@@ -62116,21 +62713,21 @@ microsecond.
 These will be used to detect whether objects need syncing or not.
 .PP
 Quatrix does not support hashes, so you cannot use the
-\f[C]--checksum\f[R] flag.
+\f[V]--checksum\f[R] flag.
 .SS Restricted filename characters
 .PP
 File names in Quatrix are case sensitive and have limitations like the
 maximum length of a filename is 255, and the minimum length is 1.
-A file name cannot be equal to \f[C].\f[R] or \f[C]..\f[R] nor contain
-\f[C]/\f[R] , \f[C]\[rs]\f[R] or non-printable ascii.
+A file name cannot be equal to \f[V].\f[R] or \f[V]..\f[R] nor contain
+\f[V]/\f[R] , \f[V]\[rs]\f[R] or non-printable ascii.
 .SS Transfers
 .PP
 For files above 50 MiB rclone will use a chunked transfer.
-Rclone will upload up to \f[C]--transfers\f[R] chunks at the same time
+Rclone will upload up to \f[V]--transfers\f[R] chunks at the same time
 (shared among all multipart uploads).
 Chunks are buffered in memory, and the minimal chunk size is 10_000_000
 bytes by default, and it can be changed in the advanced configuration,
-so increasing \f[C]--transfers\f[R] will increase the memory use.
+so increasing \f[V]--transfers\f[R] will increase the memory use.
 The chunk size has a maximum size limit, which is set to 100_000_000
 bytes by default and can be changed in the advanced configuration.
 The size of the uploaded chunk will dynamically change depending on the
@@ -62138,12 +62735,12 @@ upload speed.
 The total memory use equals the number of transfers multiplied by the
 minimal chunk size.
 In case there\[aq]s free memory allocated for the upload (which equals
-the difference of \f[C]maximal_summary_chunk_size\f[R] and
-\f[C]minimal_chunk_size\f[R] * \f[C]transfers\f[R]), the chunk size may
+the difference of \f[V]maximal_summary_chunk_size\f[R] and
+\f[V]minimal_chunk_size\f[R] * \f[V]transfers\f[R]), the chunk size may
 increase in case of high upload speed.
 As well as it can decrease in case of upload speed problems.
 If no free memory is available, all chunks will equal
-\f[C]minimal_chunk_size\f[R].
+\f[V]minimal_chunk_size\f[R].
 .SS Deleting files
 .PP
 Files you delete with rclone will end up in Trash and be stored there
@@ -62306,7 +62903,7 @@ their excellent support documentation (https://support.sia.tech/).
 .SS Introduction
 .PP
 Before you can use rclone with Sia, you will need to have a running copy
-of \f[C]Sia-UI\f[R] or \f[C]siad\f[R] (the Sia daemon) locally on your
+of \f[V]Sia-UI\f[R] or \f[V]siad\f[R] (the Sia daemon) locally on your
 computer or on local network (e.g.
 a NAS).
 Please follow the Get started (https://sia.tech/get-started) guide and
@@ -62317,7 +62914,7 @@ API (https://sia.tech/docs/) which is usually available on port
 \f[I]9980\f[R].
 By default you will run the daemon locally on the same computer so
 it\[aq]s safe to leave the API password blank (the API URL will be
-\f[C]http://127.0.0.1:9980\f[R] making external access impossible).
+\f[V]http://127.0.0.1:9980\f[R] making external access impossible).
 .PP
 However, if you want to access Sia daemon running on another node, for
 example due to memory constraints or because you want to share single
@@ -62327,39 +62924,39 @@ installed directly or in a docker
 container (https://github.com/SiaFoundation/siad/pkgs/container/siad)
 because Sia-UI does not support this mode natively.
 - Run it on externally accessible port, for example provide
-\f[C]--api-addr :9980\f[R] and \f[C]--disable-api-security\f[R]
+\f[V]--api-addr :9980\f[R] and \f[V]--disable-api-security\f[R]
 arguments on the daemon command line.
-- Enforce API password for the \f[C]siad\f[R] daemon via environment
-variable \f[C]SIA_API_PASSWORD\f[R] or text file named
-\f[C]apipassword\f[R] in the daemon directory.
-- Set rclone backend option \f[C]api_password\f[R] taking it from above
+- Enforce API password for the \f[V]siad\f[R] daemon via environment
+variable \f[V]SIA_API_PASSWORD\f[R] or text file named
+\f[V]apipassword\f[R] in the daemon directory.
+- Set rclone backend option \f[V]api_password\f[R] taking it from above
 locations.
 .PP
 Notes: 1.
 If your wallet is locked, rclone cannot unlock it automatically.
 You should either unlock it in advance by using Sia-UI or via command
-line \f[C]siac wallet unlock\f[R].
-Alternatively you can make \f[C]siad\f[R] unlock your wallet
+line \f[V]siac wallet unlock\f[R].
+Alternatively you can make \f[V]siad\f[R] unlock your wallet
 automatically upon startup by running it with environment variable
-\f[C]SIA_WALLET_PASSWORD\f[R].
+\f[V]SIA_WALLET_PASSWORD\f[R].
 2.
-If \f[C]siad\f[R] cannot find the \f[C]SIA_API_PASSWORD\f[R] variable or
-the \f[C]apipassword\f[R] file in the \f[C]SIA_DIR\f[R] directory, it
+If \f[V]siad\f[R] cannot find the \f[V]SIA_API_PASSWORD\f[R] variable or
+the \f[V]apipassword\f[R] file in the \f[V]SIA_DIR\f[R] directory, it
 will generate a random password and store in the text file named
-\f[C]apipassword\f[R] under \f[C]YOUR_HOME/.sia/\f[R] directory on Unix
+\f[V]apipassword\f[R] under \f[V]YOUR_HOME/.sia/\f[R] directory on Unix
 or
-\f[C]C:\[rs]Users\[rs]YOUR_HOME\[rs]AppData\[rs]Local\[rs]Sia\[rs]apipassword\f[R]
+\f[V]C:\[rs]Users\[rs]YOUR_HOME\[rs]AppData\[rs]Local\[rs]Sia\[rs]apipassword\f[R]
 on Windows.
 Remember this when you configure password in rclone.
 3.
-The only way to use \f[C]siad\f[R] without API password is to run it
+The only way to use \f[V]siad\f[R] without API password is to run it
 \f[B]on localhost\f[R] with command line argument
-\f[C]--authorize-api=false\f[R], but this is insecure and \f[B]strongly
+\f[V]--authorize-api=false\f[R], but this is insecure and \f[B]strongly
 discouraged\f[R].
 .SS Configuration
 .PP
-Here is an example of how to make a \f[C]sia\f[R] remote called
-\f[C]mySia\f[R].
+Here is an example of how to make a \f[V]sia\f[R] remote called
+\f[V]mySia\f[R].
 First, run:
 .IP
 .nf
@@ -62418,7 +63015,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Once configured, you can then use \f[C]rclone\f[R] like this:
+Once configured, you can then use \f[V]rclone\f[R] like this:
 .IP \[bu] 2
 List directories in top level of your Sia storage
 .IP
@@ -62536,7 +63133,7 @@ Modification times not supported
 .IP \[bu] 2
 Checksums not supported
 .IP \[bu] 2
-\f[C]rclone about\f[R] not supported
+\f[V]rclone about\f[R] not supported
 .IP \[bu] 2
 rclone can work only with \f[I]Siad\f[R] or \f[I]Sia-UI\f[R] at the
 moment, the \f[B]SkyNet daemon is not supported yet.\f[R]
@@ -62566,9 +63163,10 @@ Blomp Cloud Storage (https://www.blomp.com/cloud-storage/)
 IBM Bluemix Cloud ObjectStorage
 Swift (https://console.bluemix.net/docs/infrastructure/objectstorage-swift/index.html)
 .PP
-Paths are specified as \f[C]remote:container\f[R] (or \f[C]remote:\f[R]
-for the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:container/path/to/dir\f[R].
+Paths are specified as \f[V]remote:container\f[R] (or \f[V]remote:\f[R]
+for the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:container/path/to/dir\f[R].
 .SS Configuration
 .PP
 Here is an example of making a swift configuration.
@@ -62677,7 +63275,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this
+This remote is called \f[V]remote\f[R] and can now be used like this
 .PP
 See all containers
 .IP
@@ -62703,7 +63301,7 @@ rclone ls remote:container
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote container, deleting
+Sync \f[V]/home/local/directory\f[R] to the remote container, deleting
 any excess files in the container.
 .IP
 .nf
@@ -62731,8 +63329,8 @@ if [ -z \[dq]$OS_REGION_NAME\[dq] ]; then unset OS_REGION_NAME; fi
 .fi
 .PP
 The config file needs to look something like this where
-\f[C]$OS_USERNAME\f[R] represents the value of the \f[C]OS_USERNAME\f[R]
-variable - \f[C]123abc567xy\f[R] in the example above.
+\f[V]$OS_USERNAME\f[R] represents the value of the \f[V]OS_USERNAME\f[R]
+variable - \f[V]123abc567xy\f[R] in the example above.
 .IP
 .nf
 \f[C]
@@ -62745,15 +63343,15 @@ tenant = $OS_TENANT_NAME
 \f[R]
 .fi
 .PP
-Note that you may (or may not) need to set \f[C]region\f[R] too - try
+Note that you may (or may not) need to set \f[V]region\f[R] too - try
 without first.
 .SS Configuration from the environment
 .PP
 If you prefer you can configure rclone to use swift using a standard set
 of OpenStack environment variables.
 .PP
-When you run through the config, make sure you choose \f[C]true\f[R] for
-\f[C]env_auth\f[R] and leave everything else blank.
+When you run through the config, make sure you choose \f[V]true\f[R] for
+\f[V]env_auth\f[R] and leave everything else blank.
 .PP
 rclone will then set any empty config parameters from the environment
 using standard OpenStack environment variables.
@@ -62765,9 +63363,9 @@ in the docs for the swift library.
 If your OpenStack installation uses a non-standard authentication method
 that might not be yet supported by rclone or the underlying swift
 library, you can authenticate externally (e.g.
-calling manually the \f[C]openstack\f[R] commands to get a token).
+calling manually the \f[V]openstack\f[R] commands to get a token).
 Then, you just need to pass the two configuration variables
-\f[C]auth_token\f[R] and \f[C]storage_url\f[R].
+\f[V]auth_token\f[R] and \f[V]storage_url\f[R].
 If they are both provided, the other variables are ignored.
 rclone will not try to authenticate but instead assume it is already
 authenticated and use these two variables to access the OpenStack
@@ -62787,7 +63385,7 @@ rclone lsd myremote:
 .fi
 .SS --fast-list
 .PP
-This remote supports \f[C]--fast-list\f[R] which allows you to use fewer
+This remote supports \f[V]--fast-list\f[R] which allows you to use fewer
 transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
@@ -62802,13 +63400,13 @@ metadata.
 .PP
 For many operations, the time the object was last uploaded to the remote
 is sufficient to determine if it is \[dq]dirty\[dq].
-By using \f[C]--update\f[R] along with \f[C]--use-server-modtime\f[R],
+By using \f[V]--update\f[R] along with \f[V]--use-server-modtime\f[R],
 you can avoid the extra API call and simply upload files whose local
 modtime is newer than the time it was last uploaded.
 .SS Modification times and hashes
 .PP
 The modified time is stored as metadata on the object as
-\f[C]X-Object-Meta-Mtime\f[R] as floating point since the epoch accurate
+\f[V]X-Object-Meta-Mtime\f[R] as floating point since the epoch accurate
 to 1 ns.
 .PP
 This is a de facto standard (used in the official python-swiftclient
@@ -62833,14 +63431,14 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 .TE
 .PP
@@ -63273,9 +63871,9 @@ Default: 0
 .PP
 Above this size files will be chunked.
 .PP
-Above this size files will be chunked into a a \f[C]_segments\f[R]
-container or a \f[C].file-segments\f[R] directory.
-(See the \f[C]use_segments_container\f[R] option for more info).
+Above this size files will be chunked into a a \f[V]_segments\f[R]
+container or a \f[V].file-segments\f[R] directory.
+(See the \f[V]use_segments_container\f[R] option for more info).
 Default for this is 5 GiB which is its maximum value, which means only
 files above this size will be chunked.
 .PP
@@ -63295,15 +63893,15 @@ Default: 5Gi
 Don\[aq]t chunk files during streaming upload.
 .PP
 When doing streaming uploads (e.g.
-using \f[C]rcat\f[R] or \f[C]mount\f[R] with
-\f[C]--vfs-cache-mode off\f[R]) setting this flag will cause the swift
+using \f[V]rcat\f[R] or \f[V]mount\f[R] with
+\f[V]--vfs-cache-mode off\f[R]) setting this flag will cause the swift
 backend to not upload chunked files.
 .PP
 This will limit the maximum streamed upload size to 5 GiB.
 This is useful because non chunked files are easier to deal with and
 have an MD5SUM.
 .PP
-Rclone will still chunk files bigger than \f[C]chunk_size\f[R] when
+Rclone will still chunk files bigger than \f[V]chunk_size\f[R] when
 doing normal copy operations.
 .PP
 Properties:
@@ -63327,13 +63925,13 @@ doing a HEAD on the object.
 Since these need to be treated differently, this means rclone has to
 issue HEAD requests for objects for example when reading checksums.
 .PP
-When \f[C]no_large_objects\f[R] is set, rclone will assume that there
+When \f[V]no_large_objects\f[R] is set, rclone will assume that there
 are no static or dynamic large objects stored.
 This means it can stop doing the extra HEAD calls which in turn
 increases performance greatly especially when doing a swift to swift
-transfer with \f[C]--checksum\f[R] set.
+transfer with \f[V]--checksum\f[R] set.
 .PP
-Setting this option implies \f[C]no_chunk\f[R] and also that no files
+Setting this option implies \f[V]no_chunk\f[R] and also that no files
 will be uploaded in chunks, so files bigger than 5 GiB will just fail on
 upload.
 .PP
@@ -63356,27 +63954,27 @@ Default: false
 Choose destination for large object segments
 .PP
 Swift cannot transparently store files bigger than 5 GiB and rclone will
-chunk files larger than \f[C]chunk_size\f[R] (default 5 GiB) in order to
+chunk files larger than \f[V]chunk_size\f[R] (default 5 GiB) in order to
 upload them.
 .PP
-If this value is \f[C]true\f[R] the chunks will be stored in an
+If this value is \f[V]true\f[R] the chunks will be stored in an
 additional container named the same as the destination container but
-with \f[C]_segments\f[R] appended.
+with \f[V]_segments\f[R] appended.
 This means that there won\[aq]t be any duplicated data in the original
 container but having another container may not be acceptable.
 .PP
-If this value is \f[C]false\f[R] the chunks will be stored in a
-\f[C].file-segments\f[R] directory in the root of the container.
+If this value is \f[V]false\f[R] the chunks will be stored in a
+\f[V].file-segments\f[R] directory in the root of the container.
 This directory will be omitted when listing the container.
 Some providers (eg Blomp) require this mode as creating additional
 containers isn\[aq]t allowed.
-If it is desired to see the \f[C].file-segments\f[R] directory in the
-root then this flag must be set to \f[C]true\f[R].
+If it is desired to see the \f[V].file-segments\f[R] directory in the
+root then this flag must be set to \f[V]true\f[R].
 .PP
-If this value is \f[C]unset\f[R] (the default), then rclone will choose
+If this value is \f[V]unset\f[R] (the default), then rclone will choose
 the value to use.
-It will be \f[C]false\f[R] unless rclone detects any \f[C]auth_url\f[R]s
-that it knows need it to be \f[C]true\f[R].
+It will be \f[V]false\f[R] unless rclone detects any \f[V]auth_url\f[R]s
+that it knows need it to be \f[V]true\f[R].
 In this case you\[aq]ll see a message in the DEBUG log.
 .PP
 Properties:
@@ -63430,7 +64028,7 @@ Request\[dq] error rather than a more sensible error when the
 authentication fails for Swift.
 .PP
 So this most likely means your username / password is wrong.
-You can investigate further with the \f[C]--dump-bodies\f[R] flag.
+You can investigate further with the \f[V]--dump-bodies\f[R] flag.
 .PP
 This may also be caused by specifying the region when you shouldn\[aq]t
 have (e.g.
@@ -63441,9 +64039,9 @@ This is most likely caused by forgetting to specify your tenant when
 setting up a swift remote.
 .SS OVH Cloud Archive
 .PP
-To use rclone with OVH cloud archive, first use \f[C]rclone config\f[R]
-to set up a \f[C]swift\f[R] backend with OVH, choosing \f[C]pca\f[R] as
-the \f[C]storage_policy\f[R].
+To use rclone with OVH cloud archive, first use \f[V]rclone config\f[R]
+to set up a \f[V]swift\f[R] backend with OVH, choosing \f[V]pca\f[R] as
+the \f[V]storage_policy\f[R].
 .SS Uploading Objects
 .PP
 Uploading objects to OVH cloud archive is no different to object
@@ -63453,27 +64051,27 @@ Once uploaded the objects will show in a \[dq]Frozen\[dq] state within
 the OVH control panel.
 .SS Retrieving Objects
 .PP
-To retrieve objects use \f[C]rclone copy\f[R] as normal.
+To retrieve objects use \f[V]rclone copy\f[R] as normal.
 If the objects are in a frozen state then rclone will ask for them all
 to be unfrozen and it will wait at the end of the output with a message
 like the following:
 .PP
-\f[C]2019/03/23 13:06:33 NOTICE: Received retry after error - sleeping until 2019-03-23T13:16:33.481657164+01:00 (9m59.99985121s)\f[R]
+\f[V]2019/03/23 13:06:33 NOTICE: Received retry after error - sleeping until 2019-03-23T13:16:33.481657164+01:00 (9m59.99985121s)\f[R]
 .PP
 Rclone will wait for the time specified then retry the copy.
 .SH pCloud
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 The initial setup for pCloud involves getting a token from pCloud which
 you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -63536,10 +64134,10 @@ Note that rclone runs a webserver on your local machine to collect the
 token as returned from pCloud.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this it may require you
 to unblock it temporarily if you are running a host firewall.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your pCloud
 .IP
@@ -63573,7 +64171,7 @@ In order to set a Modification time pCloud requires the object be
 re-uploaded.
 .PP
 pCloud supports MD5 and SHA1 hashes in the US region, and SHA1 and
-SHA256 hashes in the EU region, so you can use the \f[C]--checksum\f[R]
+SHA256 hashes in the EU region, so you can use the \f[V]--checksum\f[R]
 flag.
 .SS Restricted filename characters
 .PP
@@ -63597,7 +64195,7 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -63608,19 +64206,19 @@ be used in JSON strings.
 .PP
 Deleted files will be moved to the trash.
 Your subscription level will determine how long items stay in the trash.
-\f[C]rclone cleanup\f[R] can be used to empty the trash.
+\f[V]rclone cleanup\f[R] can be used to empty the trash.
 .SS Emptying the trash
 .PP
-Due to an API limitation, the \f[C]rclone cleanup\f[R] command will only
+Due to an API limitation, the \f[V]rclone cleanup\f[R] command will only
 work if you set your username and password in the advanced options for
 this backend.
 Since we generally want to avoid storing user passwords in the rclone
 config file, we advise you to only set this up if you need the
-\f[C]rclone cleanup\f[R] command to work.
+\f[V]rclone cleanup\f[R] command to work.
 .SS Root folder ID
 .PP
-You can set the \f[C]root_folder_id\f[R] for rclone.
-This is the directory (identified by its \f[C]Folder ID\f[R]) that
+You can set the \f[V]root_folder_id\f[R] for rclone.
+This is the directory (identified by its \f[V]Folder ID\f[R]) that
 rclone considers to be the root of your pCloud drive.
 .PP
 Normally you will leave this blank and rclone will determine the correct
@@ -63629,15 +64227,15 @@ root to use itself.
 However you can set this to restrict rclone to a specific folder
 hierarchy.
 .PP
-In order to do this you will have to find the \f[C]Folder ID\f[R] of the
+In order to do this you will have to find the \f[V]Folder ID\f[R] of the
 directory you wish rclone to display.
-This will be the \f[C]folder\f[R] field of the URL when you open the
+This will be the \f[V]folder\f[R] field of the URL when you open the
 relevant folder in the pCloud web interface.
 .PP
 So if the folder you want rclone to use has a URL which looks like
-\f[C]https://my.pcloud.com/#page=filemanager&folder=5xxxxxxxx8&tpl=foldergrid\f[R]
-in the browser, then you use \f[C]5xxxxxxxx8\f[R] as the
-\f[C]root_folder_id\f[R] in the config.
+\f[V]https://my.pcloud.com/#page=filemanager&folder=5xxxxxxxx8&tpl=foldergrid\f[R]
+in the browser, then you use \f[V]5xxxxxxxx8\f[R] as the
+\f[V]root_folder_id\f[R] in the config.
 .SS Standard options
 .PP
 Here are the Standard options specific to pcloud (Pcloud).
@@ -63830,9 +64428,9 @@ Required: false
 .PP
 PikPak is a private cloud drive (https://mypikpak.com/).
 .PP
-Paths are specified as \f[C]remote:path\f[R], and may be as deep as
+Paths are specified as \f[V]remote:path\f[R], and may be as deep as
 required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 Here is an example of making a remote for PikPak.
@@ -63993,7 +64591,7 @@ Required: false
 Send files to the trash instead of deleting permanently.
 .PP
 Defaults to true, namely sending files to the trash.
-Use \f[C]--pikpak-use-trash=false\f[R] to delete files permanently
+Use \f[V]--pikpak-use-trash=false\f[R] to delete files permanently
 instead.
 .PP
 Properties:
@@ -64204,7 +64802,7 @@ PikPak supports MD5 hash, but sometimes given empty especially for
 user-uploaded files.
 .SS Deleted files still visible with trashed-only
 .PP
-Deleted files will still be visible with \f[C]--pikpak-trashed-only\f[R]
+Deleted files will still be visible with \f[V]--pikpak-trashed-only\f[R]
 even after the trash emptied.
 This goes away after few days.
 .SH Pixeldrain
@@ -64227,7 +64825,7 @@ available at this link: https://pixeldrain.com/d/me.
 .PP
 Go to the API keys page (https://pixeldrain.com/user/api_keys) on your
 account and generate a new API key for rclone.
-Then run \f[C]rclone config\f[R] and use the API key to create a new
+Then run \f[V]rclone config\f[R] and use the API key to create a new
 backend.
 .PP
 Example:
@@ -64303,14 +64901,14 @@ It is possible to gain read-only access to publicly shared directories
 through rclone.
 For this you only need a directory ID.
 The directory ID can be found in the URL of a shared directory, the URL
-will look like this \f[C]https://pixeldrain.com/d/abcd1234\f[R] where
-\f[C]abcd1234\f[R] is the directory ID.
+will look like this \f[V]https://pixeldrain.com/d/abcd1234\f[R] where
+\f[V]abcd1234\f[R] is the directory ID.
 Directory IDs in your own filesystem can also be listed with the
-\f[C]lsf\f[R] command:
+\f[V]lsf\f[R] command:
 .PP
-\f[C]rclone lsf Pixeldrain: --dirs-only -Fpi\f[R]
+\f[V]rclone lsf Pixeldrain: --dirs-only -Fpi\f[R]
 .PP
-This will print directories in your \f[C]Pixeldrain\f[R] home directory
+This will print directories in your \f[V]Pixeldrain\f[R] home directory
 and their public IDs.
 .PP
 Enter this directory ID in the rclone config and you will be able to
@@ -64440,17 +65038,17 @@ T}
 See the metadata (https://rclone.org/docs/#metadata) docs for more info.
 .SH premiumize.me
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 The initial setup for premiumize.me (https://premiumize.me/) involves
 getting a token from premiumize.me which you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -64510,10 +65108,10 @@ Note that rclone runs a webserver on your local machine to collect the
 token as returned from premiumize.me.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this it may require you
 to unblock it temporarily if you are running a host firewall.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your premiumize.me
 .IP
@@ -64541,8 +65139,8 @@ rclone copy /home/source remote:backup
 .SS Modification times and hashes
 .PP
 premiumize.me does not support modification times or hashes, therefore
-syncing will default to \f[C]--size-only\f[R] checking.
-Note that using \f[C]--update\f[R] will work.
+syncing will default to \f[V]--size-only\f[R] checking.
+Note that using \f[V]--update\f[R] will work.
 .SS Restricted filename characters
 .PP
 In addition to the default restricted characters
@@ -64565,14 +65163,14 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 \[dq]
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 .TE
 .PP
@@ -64707,10 +65305,10 @@ Required: false
 Note that premiumize.me is case insensitive so you can\[aq]t have a file
 called \[dq]Hello.doc\[dq] and one called \[dq]hello.doc\[dq].
 .PP
-premiumize.me file names can\[aq]t have the \f[C]\[rs]\f[R] or
-\f[C]\[dq]\f[R] characters in.
+premiumize.me file names can\[aq]t have the \f[V]\[rs]\f[R] or
+\f[V]\[dq]\f[R] characters in.
 rclone maps these to and from an identical looking unicode equivalents
-\f[C]\[uFF3C]\f[R] and \f[C]\[uFF02]\f[R]
+\f[V]＼\f[R] and \f[V]＂\f[R]
 .PP
 premiumize.me only supports filenames up to 255 characters in length.
 .SH Proton Drive
@@ -64733,13 +65331,13 @@ accounts it is not compatible with.
 Please post on the rclone forum (https://forum.rclone.org/) if you find
 an incompatibility.
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configurations
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -64796,9 +65394,9 @@ y/e/d> y
 .PP
 \f[B]NOTE:\f[R] The Proton Drive encryption keys need to have been
 already generated after a regular login via the browser, otherwise
-attempting to use the credentials in \f[C]rclone\f[R] will fail.
+attempting to use the credentials in \f[V]rclone\f[R] will fail.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Proton Drive
 .IP
@@ -65130,17 +65728,17 @@ There are likely quite a few errors in this library, as there isn\[aq]t
 official documentation available.
 .SH put.io
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 put.io paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 The initial setup for put.io involves getting a token from put.io which
 you need to do in your browser.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -65215,7 +65813,7 @@ token as returned from put.io if using web browser to automatically
 authenticate.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this it may require you
 to unblock it temporarily if you are running a host firewall, or use
 manual mode.
 .PP
@@ -65266,7 +65864,7 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -65388,7 +65986,7 @@ When you hit a limit, rclone automatically retries after waiting the
 amount of time requested by the server.
 .PP
 If you want to avoid ever hitting these limits, you may use the
-\f[C]--tpslimit\f[R] flag with a low number.
+\f[V]--tpslimit\f[R] flag with a low number.
 Note that the imposed limits may be different for different operations,
 and may change over time.
 .SH Proton Drive
@@ -65411,13 +66009,13 @@ accounts it is not compatible with.
 Please post on the rclone forum (https://forum.rclone.org/) if you find
 an incompatibility.
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configurations
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -65474,9 +66072,9 @@ y/e/d> y
 .PP
 \f[B]NOTE:\f[R] The Proton Drive encryption keys need to have been
 already generated after a regular login via the browser, otherwise
-attempting to use the credentials in \f[C]rclone\f[R] will fail.
+attempting to use the credentials in \f[V]rclone\f[R] will fail.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Proton Drive
 .IP
@@ -65820,11 +66418,11 @@ professional edition.
 There are two distinct modes you can setup your remote: - you point your
 remote to the \f[B]root of the server\f[R], meaning you don\[aq]t
 specify a library during the configuration: Paths are specified as
-\f[C]remote:library\f[R].
+\f[V]remote:library\f[R].
 You may put subdirectories in too, e.g.
-\f[C]remote:library/path/to/dir\f[R].
+\f[V]remote:library/path/to/dir\f[R].
 - you point your remote to a specific library during the configuration:
-Paths are specified as \f[C]remote:path/to/dir\f[R].
+Paths are specified as \f[V]remote:path/to/dir\f[R].
 \f[B]This is the recommended mode when using encrypted libraries\f[R].
 (\f[I]This mode is possibly slightly faster than the root mode\f[R])
 .SS Configuration in root mode
@@ -65911,7 +66509,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-This remote is called \f[C]seafile\f[R].
+This remote is called \f[V]seafile\f[R].
 It\[aq]s pointing to the root of your seafile server and can now be used
 like this:
 .PP
@@ -65939,7 +66537,7 @@ rclone ls seafile:library
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote library, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote library, deleting any
 excess files in the library.
 .IP
 .nf
@@ -66029,9 +66627,9 @@ y/e/d> y
 You\[aq]ll notice your password is blank in the configuration.
 It\[aq]s because we only need the password to authenticate you once.
 .PP
-You specified \f[C]My Library\f[R] during the configuration.
+You specified \f[V]My Library\f[R] during the configuration.
 The root of the remote is pointing at the root of the library
-\f[C]My Library\f[R]:
+\f[V]My Library\f[R]:
 .PP
 See all files in the library:
 .IP
@@ -66057,7 +66655,7 @@ rclone ls seafile:directory
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote library, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote library, deleting any
 excess files in the library.
 .IP
 .nf
@@ -66067,7 +66665,7 @@ rclone sync --interactive /home/local/directory seafile:
 .fi
 .SS --fast-list
 .PP
-Seafile version 7+ supports \f[C]--fast-list\f[R] which allows you to
+Seafile version 7+ supports \f[V]--fast-list\f[R] which allows you to
 use fewer transactions in exchange for more memory.
 See the rclone docs (https://rclone.org/docs/#fast-list) for more
 details.
@@ -66094,21 +66692,21 @@ T{
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 T{
 \[dq]
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -66150,7 +66748,7 @@ Versions below 6.0 are not supported.
 Versions between 6.0 and 6.3 haven\[aq]t been tested and might not work
 properly.
 .PP
-Each new version of \f[C]rclone\f[R] is automatically tested against the
+Each new version of \f[V]rclone\f[R] is automatically tested against the
 latest docker image (https://hub.docker.com/r/seafileltd/seafile-mc/) of
 the seafile community server.
 .SS Standard options
@@ -66327,16 +66925,16 @@ rsync.net
 SFTP runs over SSH v2 and is installed as standard with most modern SSH
 installations.
 .PP
-Paths are specified as \f[C]remote:path\f[R].
-If the path does not begin with a \f[C]/\f[R] it is relative to the home
+Paths are specified as \f[V]remote:path\f[R].
+If the path does not begin with a \f[V]/\f[R] it is relative to the home
 directory of the user.
-An empty path \f[C]remote:\f[R] refers to the user\[aq]s home directory.
-For example, \f[C]rclone lsd remote:\f[R] would list the home directory
+An empty path \f[V]remote:\f[R] refers to the user\[aq]s home directory.
+For example, \f[V]rclone lsd remote:\f[R] would list the home directory
 of the user configured in the rclone remote config
-(\f[C]i.e /home/sftpuser\f[R]).
-However, \f[C]rclone lsd remote:/\f[R] would list the root directory for
+(\f[V]i.e /home/sftpuser\f[R]).
+However, \f[V]rclone lsd remote:/\f[R] would list the root directory for
 remote machine (i.e.
-\f[C]/\f[R])
+\f[V]/\f[R])
 .PP
 Note that some SFTP servers will need the leading / - Synology is a good
 example of this.
@@ -66408,7 +67006,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-This remote is called \f[C]remote\f[R] and can now be used like this:
+This remote is called \f[V]remote\f[R] and can now be used like this:
 .PP
 See all directories in the home directory
 .IP
@@ -66442,7 +67040,7 @@ rclone ls remote:path/to/directory
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote directory, deleting
+Sync \f[V]/home/local/directory\f[R] to the remote directory, deleting
 any excess files in the directory.
 .IP
 .nf
@@ -66451,8 +67049,8 @@ rclone sync --interactive /home/local/directory remote:directory
 \f[R]
 .fi
 .PP
-Mount the remote path \f[C]/srv/www-data/\f[R] to the local path
-\f[C]/mnt/www-data\f[R]
+Mount the remote path \f[V]/srv/www-data/\f[R] to the local path
+\f[V]/mnt/www-data\f[R]
 .IP
 .nf
 \f[C]
@@ -66470,7 +67068,7 @@ Key file, including certificate signed keys
 ssh-agent
 .PP
 Key files should be PEM-encoded private key files.
-For instance \f[C]/home/$USER/.ssh/id_rsa\f[R].
+For instance \f[V]/home/$USER/.ssh/id_rsa\f[R].
 Only unencrypted OpenSSH or PEM encrypted files are supported.
 .PP
 The key file can be specified in either an external file (key_file) or
@@ -66493,18 +67091,18 @@ awk \[aq]{printf \[dq]%s\[rs]\[rs]n\[dq], $0}\[aq] < \[ti]/.ssh/id_rsa
 \f[R]
 .fi
 .PP
-If you don\[aq]t specify \f[C]pass\f[R], \f[C]key_file\f[R], or
-\f[C]key_pem\f[R] or \f[C]ask_password\f[R] then rclone will attempt to
+If you don\[aq]t specify \f[V]pass\f[R], \f[V]key_file\f[R], or
+\f[V]key_pem\f[R] or \f[V]ask_password\f[R] then rclone will attempt to
 contact an ssh-agent.
-You can also specify \f[C]key_use_agent\f[R] to force the usage of an
+You can also specify \f[V]key_use_agent\f[R] to force the usage of an
 ssh-agent.
-In this case \f[C]key_file\f[R] or \f[C]key_pem\f[R] can also be
+In this case \f[V]key_file\f[R] or \f[V]key_pem\f[R] can also be
 specified to force the usage of a specific key in the ssh-agent.
 .PP
 Using an ssh-agent is the only way to load encrypted OpenSSH keys at the
 moment.
 .PP
-If you set the \f[C]ask_password\f[R] option, rclone will prompt for a
+If you set the \f[V]ask_password\f[R] option, rclone will prompt for a
 password when needed and no password has been configured.
 .SS Certificate-signed keys
 .PP
@@ -66516,11 +67114,11 @@ If you have a certificate you may use it to sign your public key,
 creating a separate SSH user certificate that should be used instead of
 the plain public key extracted from the private key.
 Then you must provide the path to the user certificate public key file
-in \f[C]pubkey_file\f[R].
+in \f[V]pubkey_file\f[R].
 .PP
 Note: This is not the traditional public key paired with your private
-key, typically saved as \f[C]/home/$USER/.ssh/id_rsa.pub\f[R].
-Setting this path in \f[C]pubkey_file\f[R] will not work.
+key, typically saved as \f[V]/home/$USER/.ssh/id_rsa.pub\f[R].
+Setting this path in \f[V]pubkey_file\f[R] will not work.
 .PP
 Example:
 .IP
@@ -66554,13 +67152,13 @@ This can allow an attacker to replace a server with their own and if you
 use password authentication then this can lead to that password being
 exposed.
 .PP
-Host key matching, using standard \f[C]known_hosts\f[R] files can be
-turned on by enabling the \f[C]known_hosts_file\f[R] option.
-This can point to the file maintained by \f[C]OpenSSH\f[R] or can point
+Host key matching, using standard \f[V]known_hosts\f[R] files can be
+turned on by enabling the \f[V]known_hosts_file\f[R] option.
+This can point to the file maintained by \f[V]OpenSSH\f[R] or can point
 to a unique file.
 .PP
 e.g.
-using the OpenSSH \f[C]known_hosts\f[R] file:
+using the OpenSSH \f[V]known_hosts\f[R] file:
 .IP
 .nf
 \f[C]
@@ -66583,12 +67181,12 @@ ssh-keyscan -t dsa,rsa,ecdsa,ed25519 example.com >> known_hosts
 .PP
 There are some limitations:
 .IP \[bu] 2
-\f[C]rclone\f[R] will not \f[I]manage\f[R] this file for you.
+\f[V]rclone\f[R] will not \f[I]manage\f[R] this file for you.
 If the key is missing or wrong then the connection will be refused.
 .IP \[bu] 2
 If the server is set up for a certificate host key then the entry in the
-\f[C]known_hosts\f[R] file \f[I]must\f[R] be the
-\f[C]\[at]cert-authority\f[R] entry for the CA
+\f[V]known_hosts\f[R] file \f[I]must\f[R] be the
+\f[V]\[at]cert-authority\f[R] entry for the CA
 .PP
 If the host key provided by the server does not match the one in the
 file (or is missing) then the connection will be aborted and an error
@@ -66617,11 +67215,11 @@ NewFs: couldn\[aq]t connect SSH: ssh: handshake failed: ssh: no authorities for
 .fi
 .PP
 then it is likely the server has presented a CA signed host certificate
-and you will need to add the appropriate \f[C]\[at]cert-authority\f[R]
+and you will need to add the appropriate \f[V]\[at]cert-authority\f[R]
 entry.
 .PP
-The \f[C]known_hosts_file\f[R] setting can be set during
-\f[C]rclone config\f[R] as an advanced option.
+The \f[V]known_hosts_file\f[R] setting can be set during
+\f[V]rclone config\f[R] as an advanced option.
 .SS ssh-agent on macOS
 .PP
 Note that there seem to be various problems with using an ssh-agent on
@@ -66674,15 +67272,15 @@ something else is detected.
 If unable to even create a remote shell session, then shell command
 execution will be disabled entirely.
 The result is stored in the SFTP remote configuration, in option
-\f[C]shell_type\f[R], so that the auto-detection only have to be
+\f[V]shell_type\f[R], so that the auto-detection only have to be
 performed once.
 If you manually set a value for this option before first run, the
 auto-detection will be skipped, and if you set a different value later
 this will override any existing.
-Value \f[C]none\f[R] can be set to avoid any attempts at executing shell
+Value \f[V]none\f[R] can be set to avoid any attempts at executing shell
 commands, e.g.
 if this is not allowed on the server.
-If you have \f[C]shell_type = none\f[R] in the configuration then the
+If you have \f[V]shell_type = none\f[R] in the configuration then the
 ssh must not be set.
 .PP
 When the server is rclone serve
@@ -66692,7 +67290,7 @@ Windows.
 This server does not actually have a shell, but it accepts input
 commands matching the specific ones that the SFTP backend relies on for
 Unix shells, e.g.
-\f[C]md5sum\f[R] and \f[C]df\f[R].
+\f[V]md5sum\f[R] and \f[V]df\f[R].
 Also it handles the string escape rules used for Unix shell.
 Treating it as a Unix type shell from a SFTP remote will therefore
 always be correct, and support all features.
@@ -66705,8 +67303,8 @@ If you configure a sftp remote without a config file, e.g.
 an on the fly (https://rclone.org/docs/#backend-path-to-dir%5D) remote,
 rclone will have nowhere to store the result, and it will re-run the
 command on every access.
-To avoid this you should explicitly set the \f[C]shell_type\f[R] option
-to the correct value, or to \f[C]none\f[R] if you want to prevent rclone
+To avoid this you should explicitly set the \f[V]shell_type\f[R] option
+to the correct value, or to \f[V]none\f[R] if you want to prevent rclone
 from executing any remote shell commands.
 .PP
 It is also important to note that, since the shell type decides how
@@ -66727,10 +67325,10 @@ Currently MD5 and SHA-1 are supported.
 .PP
 Normally this requires an external utility being available on the
 server.
-By default rclone will try commands \f[C]md5sum\f[R], \f[C]md5\f[R] and
-\f[C]rclone md5sum\f[R] for MD5 checksums, and the first one found
+By default rclone will try commands \f[V]md5sum\f[R], \f[V]md5\f[R] and
+\f[V]rclone md5sum\f[R] for MD5 checksums, and the first one found
 usable will be picked.
-Same with \f[C]sha1sum\f[R], \f[C]sha1\f[R] and \f[C]rclone sha1sum\f[R]
+Same with \f[V]sha1sum\f[R], \f[V]sha1\f[R] and \f[V]rclone sha1sum\f[R]
 commands for SHA-1 checksums.
 These utilities normally need to be in the remote\[aq]s PATH to be
 found.
@@ -66743,7 +67341,7 @@ script block to produce the checksums when no external checksum commands
 are found (see shell access).
 This assumes PowerShell version 4.0 or newer.
 .PP
-The options \f[C]md5sum_command\f[R] and \f[C]sha1_command\f[R] can be
+The options \f[V]md5sum_command\f[R] and \f[V]sha1_command\f[R] can be
 used to customize the command to be executed for calculation of
 checksums.
 You can for example set a specific path to where md5sum and sha1sum
@@ -66758,26 +67356,26 @@ compatible format, which means if you have an rclone executable on the
 server it can be used.
 As mentioned above, they will be automatically picked up if found in
 PATH, but if not you can set something like
-\f[C]/path/to/rclone md5sum\f[R] as the value of option
-\f[C]md5sum_command\f[R] to make sure a specific executable is used.
+\f[V]/path/to/rclone md5sum\f[R] as the value of option
+\f[V]md5sum_command\f[R] to make sure a specific executable is used.
 .PP
 Remote checksumming is recommended and enabled by default.
 First time rclone is using a SFTP remote, if options
-\f[C]md5sum_command\f[R] or \f[C]sha1_command\f[R] are not set, it will
+\f[V]md5sum_command\f[R] or \f[V]sha1_command\f[R] are not set, it will
 check if any of the default commands for each of them, as described
 above, can be used.
 The result will be saved in the remote configuration, so next time it
 will use the same.
-Value \f[C]none\f[R] will be set if none of the default commands could
+Value \f[V]none\f[R] will be set if none of the default commands could
 be used for a specific algorithm, and this algorithm will not be
 supported by the remote.
 .PP
 Disabling the checksumming may be required if you are connecting to SFTP
 servers which are not under your control, and to which the execution of
 remote shell commands is prohibited.
-Set the configuration option \f[C]disable_hashcheck\f[R] to
-\f[C]true\f[R] to disable checksumming entirely, or set
-\f[C]shell_type\f[R] to \f[C]none\f[R] to disable all functionality
+Set the configuration option \f[V]disable_hashcheck\f[R] to
+\f[V]true\f[R] to disable checksumming entirely, or set
+\f[V]shell_type\f[R] to \f[V]none\f[R] to disable all functionality
 based on remote shell command execution.
 .SS Modification times and hashes
 .PP
@@ -66789,11 +67387,11 @@ Some SFTP servers disable setting/modifying the file modification time
 after upload (for example, certain configurations of ProFTPd with
 mod_sftp).
 If you are using one of these servers, you can set the option
-\f[C]set_modtime = false\f[R] in your RClone backend configuration to
+\f[V]set_modtime = false\f[R] in your RClone backend configuration to
 disable this behaviour.
 .SS About command
 .PP
-The \f[C]about\f[R] command returns the total space, free space, and
+The \f[V]about\f[R] command returns the total space, free space, and
 used space on the remote for the disk of the specified path on the
 remote or, if not set, the disk of the root on the remote.
 .PP
@@ -66803,11 +67401,11 @@ depends on the server.
 If the server implements the vendor-specific VFS statistics extension,
 which is normally the case with OpenSSH instances, it will be used.
 If not, but the same login has access to a Unix shell, where the
-\f[C]df\f[R] command is available (e.g.
+\f[V]df\f[R] command is available (e.g.
 in the remote\[aq]s PATH), then this will be used instead.
 If the server shell is PowerShell, probably with a Windows OpenSSH
 server, rclone will use a built-in shell command (see shell access).
-If none of the above is applicable, \f[C]about\f[R] will fail.
+If none of the above is applicable, \f[V]about\f[R] will fail.
 .SS Standard options
 .PP
 Here are the Standard options specific to sftp (SSH/SFTP).
@@ -66907,8 +67505,8 @@ Path to PEM-encoded private key file.
 .PP
 Leave blank or set key-use-agent to use ssh-agent.
 .PP
-Leading \f[C]\[ti]\f[R] will be expanded in the file name as will
-environment variables such as \f[C]${RCLONE_CONFIG_DIR}\f[R].
+Leading \f[V]\[ti]\f[R] will be expanded in the file name as will
+environment variables such as \f[V]${RCLONE_CONFIG_DIR}\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -66945,8 +67543,8 @@ Optional path to public key file.
 Set this if you have a signed certificate you want to use for
 authentication.
 .PP
-Leading \f[C]\[ti]\f[R] will be expanded in the file name as will
-environment variables such as \f[C]${RCLONE_CONFIG_DIR}\f[R].
+Leading \f[V]\[ti]\f[R] will be expanded in the file name as will
+environment variables such as \f[V]${RCLONE_CONFIG_DIR}\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -66965,7 +67563,7 @@ When key-file is also set, the \[dq].pub\[dq] file of the specified
 key-file is read and only the associated key is requested from the
 ssh-agent.
 This allows to avoid
-\f[C]Too many authentication failures for *username*\f[R] errors when
+\f[V]Too many authentication failures for *username*\f[R] errors when
 the ssh-agent contains many keys.
 .PP
 Properties:
@@ -67099,8 +67697,8 @@ Optional path to known_hosts file.
 .PP
 Set this value to enable server host key validation.
 .PP
-Leading \f[C]\[ti]\f[R] will be expanded in the file name as will
-environment variables such as \f[C]${RCLONE_CONFIG_DIR}\f[R].
+Leading \f[V]\[ti]\f[R] will be expanded in the file name as will
+environment variables such as \f[V]${RCLONE_CONFIG_DIR}\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -67484,14 +68082,14 @@ Note that setting this is very likely to cause deadlocks so it should be
 used with care.
 .PP
 If you are doing a sync or copy then make sure connections is one more
-than the sum of \f[C]--transfers\f[R] and \f[C]--checkers\f[R].
+than the sum of \f[V]--transfers\f[R] and \f[V]--checkers\f[R].
 .PP
-If you use \f[C]--check-first\f[R] then it just needs to be one more
-than the maximum of \f[C]--checkers\f[R] and \f[C]--transfers\f[R].
+If you use \f[V]--check-first\f[R] then it just needs to be one more
+than the maximum of \f[V]--checkers\f[R] and \f[V]--transfers\f[R].
 .PP
-So for \f[C]connections 3\f[R] you\[aq]d use
-\f[C]--checkers 2 --transfers 2 --check-first\f[R] or
-\f[C]--checkers 1 --transfers 1\f[R].
+So for \f[V]connections 3\f[R] you\[aq]d use
+\f[V]--checkers 2 --transfers 2 --check-first\f[R] or
+\f[V]--checkers 1 --transfers 1\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -67716,15 +68314,15 @@ Required: false
 On some SFTP servers (e.g.
 Synology) the paths are different for SSH and SFTP so the hashes
 can\[aq]t be calculated properly.
-For them using \f[C]disable_hashcheck\f[R] is a good idea.
+For them using \f[V]disable_hashcheck\f[R] is a good idea.
 .PP
 The only ssh agent supported under Windows is Putty\[aq]s pageant.
 .PP
 The Go SSH library disables the use of the aes128-cbc cipher by default,
 due to security concerns.
 This can be re-enabled on a per-connection basis by setting the
-\f[C]use_insecure_cipher\f[R] setting in the configuration file to
-\f[C]true\f[R].
+\f[V]use_insecure_cipher\f[R] setting in the configuration file to
+\f[V]true\f[R].
 Further details on the insecurity of this cipher can be found in this
 paper (http://www.isg.rhul.ac.uk/~kp/SandPfinal.pdf).
 .PP
@@ -67732,10 +68330,10 @@ SFTP isn\[aq]t supported under plan9 until this
 issue (https://github.com/pkg/sftp/issues/156) is fixed.
 .PP
 Note that since SFTP isn\[aq]t HTTP based the following flags don\[aq]t
-work with it: \f[C]--dump-headers\f[R], \f[C]--dump-bodies\f[R],
-\f[C]--dump-auth\f[R].
+work with it: \f[V]--dump-headers\f[R], \f[V]--dump-bodies\f[R],
+\f[V]--dump-auth\f[R].
 .PP
-Note that \f[C]--timeout\f[R] and \f[C]--contimeout\f[R] are both
+Note that \f[V]--timeout\f[R] and \f[V]--contimeout\f[R] are both
 supported.
 .SS rsync.net
 .PP
@@ -67758,28 +68356,29 @@ This relies on go-smb2
 library (https://github.com/hirochachacha/go-smb2/) for communication
 with SMB protocol.
 .PP
-Paths are specified as \f[C]remote:sharename\f[R] (or \f[C]remote:\f[R]
-for the \f[C]lsd\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:item/path/to/dir\f[R].
+Paths are specified as \f[V]remote:sharename\f[R] (or \f[V]remote:\f[R]
+for the \f[V]lsd\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:item/path/to/dir\f[R].
 .SS Notes
 .PP
 The first path segment must be the name of the share, which you entered
 when you started to share on Windows.
-On smbd, it\[aq]s the section title in \f[C]smb.conf\f[R] (usually in
-\f[C]/etc/samba/\f[R]) file.
+On smbd, it\[aq]s the section title in \f[V]smb.conf\f[R] (usually in
+\f[V]/etc/samba/\f[R]) file.
 You can find shares by querying the root if you\[aq]re unsure (e.g.
-\f[C]rclone lsd remote:\f[R]).
+\f[V]rclone lsd remote:\f[R]).
 .PP
 You can\[aq]t access to the shared printers from rclone, obviously.
 .PP
 You can\[aq]t use Anonymous access for logging in.
-You have to use the \f[C]guest\f[R] user with an empty password instead.
+You have to use the \f[V]guest\f[R] user with an empty password instead.
 The rclone client tries to avoid 8.3 names when uploading files by
 encoding trailing spaces and periods.
 Alternatively, the local
 backend (https://rclone.org/local/#paths-on-windows) on Windows can
 access SMB servers using UNC paths, by
-\f[C]\[rs]\[rs]server\[rs]share\f[R].
+\f[V]\[rs]\[rs]server\[rs]share\f[R].
 This doesn\[aq]t apply to non-Windows OSes, such as Linux and macOS.
 .SS Configuration
 .PP
@@ -68203,7 +68802,7 @@ Requires a running S3 gateway (either self-hosted or Storj-hosted).
 Limitations:
 .RS 2
 .IP \[bu] 2
-\f[I]Storj backend\f[R]: \f[C]rclone checksum\f[R] is not possible
+\f[I]Storj backend\f[R]: \f[V]rclone checksum\f[R] is not possible
 without download, as checksum metadata is not calculated during upload
 .IP \[bu] 2
 \f[I]S3 backend\f[R]: secret encryption key is shared with the gateway
@@ -68216,7 +68815,7 @@ Access Grant that someone else shared with you.
 Key (https://documentation.storj.io/getting-started/uploading-your-first-object/create-an-api-key)
 of a Storj project you are a member of.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -68382,7 +68981,7 @@ Required: false
 Satellite address.
 .PP
 Custom satellite address should match the format:
-\f[C]<nodeid>\[at]<address>:<port>\f[R].
+\f[V]<nodeid>\[at]<address>:<port>\f[R].
 .PP
 Properties:
 .IP \[bu] 2
@@ -68468,15 +69067,16 @@ Type: string
 Required: false
 .SS Usage
 .PP
-Paths are specified as \f[C]remote:bucket\f[R] (or \f[C]remote:\f[R] for
-the \f[C]lsf\f[R] command.) You may put subdirectories in too, e.g.
-\f[C]remote:bucket/path/to/dir\f[R].
+Paths are specified as \f[V]remote:bucket\f[R] (or \f[V]remote:\f[R] for
+the \f[V]lsf\f[R] command.)
+You may put subdirectories in too, e.g.
+\f[V]remote:bucket/path/to/dir\f[R].
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this.
+Once configured you can then use \f[V]rclone\f[R] like this.
 .SS Create a new bucket
 .PP
-Use the \f[C]mkdir\f[R] command to create new bucket, e.g.
-\f[C]bucket\f[R].
+Use the \f[V]mkdir\f[R] command to create new bucket, e.g.
+\f[V]bucket\f[R].
 .IP
 .nf
 \f[C]
@@ -68485,7 +69085,7 @@ rclone mkdir remote:bucket
 .fi
 .SS List all buckets
 .PP
-Use the \f[C]lsf\f[R] command to list all buckets.
+Use the \f[V]lsf\f[R] command to list all buckets.
 .IP
 .nf
 \f[C]
@@ -68493,10 +69093,10 @@ rclone lsf remote:
 \f[R]
 .fi
 .PP
-Note the colon (\f[C]:\f[R]) character at the end of the command line.
+Note the colon (\f[V]:\f[R]) character at the end of the command line.
 .SS Delete a bucket
 .PP
-Use the \f[C]rmdir\f[R] command to delete an empty bucket.
+Use the \f[V]rmdir\f[R] command to delete an empty bucket.
 .IP
 .nf
 \f[C]
@@ -68504,7 +69104,7 @@ rclone rmdir remote:bucket
 \f[R]
 .fi
 .PP
-Use the \f[C]purge\f[R] command to delete a non-empty bucket with all
+Use the \f[V]purge\f[R] command to delete a non-empty bucket with all
 its content.
 .IP
 .nf
@@ -68514,7 +69114,7 @@ rclone purge remote:bucket
 .fi
 .SS Upload objects
 .PP
-Use the \f[C]copy\f[R] command to upload an object.
+Use the \f[V]copy\f[R] command to upload an object.
 .IP
 .nf
 \f[C]
@@ -68522,7 +69122,7 @@ rclone copy --progress /home/local/directory/file.ext remote:bucket/path/to/dir/
 \f[R]
 .fi
 .PP
-The \f[C]--progress\f[R] flag is for displaying progress information.
+The \f[V]--progress\f[R] flag is for displaying progress information.
 Remove it if you don\[aq]t need this information.
 .PP
 Use a folder in the local path to upload all its objects.
@@ -68536,7 +69136,7 @@ rclone copy --progress /home/local/directory/ remote:bucket/path/to/dir/
 Only modified files will be copied.
 .SS List objects
 .PP
-Use the \f[C]ls\f[R] command to list recursively all objects in a
+Use the \f[V]ls\f[R] command to list recursively all objects in a
 bucket.
 .IP
 .nf
@@ -68554,7 +69154,7 @@ rclone ls remote:bucket/path/to/dir/
 \f[R]
 .fi
 .PP
-Use the \f[C]lsf\f[R] command to list non-recursively all objects in a
+Use the \f[V]lsf\f[R] command to list non-recursively all objects in a
 bucket or a folder.
 .IP
 .nf
@@ -68564,7 +69164,7 @@ rclone lsf remote:bucket/path/to/dir/
 .fi
 .SS Download objects
 .PP
-Use the \f[C]copy\f[R] command to download an object.
+Use the \f[V]copy\f[R] command to download an object.
 .IP
 .nf
 \f[C]
@@ -68572,7 +69172,7 @@ rclone copy --progress remote:bucket/path/to/dir/file.ext /home/local/directory/
 \f[R]
 .fi
 .PP
-The \f[C]--progress\f[R] flag is for displaying progress information.
+The \f[V]--progress\f[R] flag is for displaying progress information.
 Remove it if you don\[aq]t need this information.
 .PP
 Use a folder in the remote path to download all its objects.
@@ -68584,7 +69184,7 @@ rclone copy --progress remote:bucket/path/to/dir/ /home/local/directory/
 .fi
 .SS Delete objects
 .PP
-Use the \f[C]deletefile\f[R] command to delete a single object.
+Use the \f[V]deletefile\f[R] command to delete a single object.
 .IP
 .nf
 \f[C]
@@ -68592,7 +69192,7 @@ rclone deletefile remote:bucket/path/to/dir/file.ext
 \f[R]
 .fi
 .PP
-Use the \f[C]delete\f[R] command to delete all object in a folder.
+Use the \f[V]delete\f[R] command to delete all object in a folder.
 .IP
 .nf
 \f[C]
@@ -68601,7 +69201,7 @@ rclone delete remote:bucket/path/to/dir/
 .fi
 .SS Print the total size of objects
 .PP
-Use the \f[C]size\f[R] command to print the total size of objects in a
+Use the \f[V]size\f[R] command to print the total size of objects in a
 bucket or a folder.
 .IP
 .nf
@@ -68611,7 +69211,7 @@ rclone size remote:bucket/path/to/dir/
 .fi
 .SS Sync two Locations
 .PP
-Use the \f[C]sync\f[R] command to sync the source to the destination,
+Use the \f[V]sync\f[R] command to sync the source to the destination,
 changing the destination only, deleting any excess files.
 .IP
 .nf
@@ -68620,10 +69220,10 @@ rclone sync --interactive --progress /home/local/directory/ remote:bucket/path/t
 \f[R]
 .fi
 .PP
-The \f[C]--progress\f[R] flag is for displaying progress information.
+The \f[V]--progress\f[R] flag is for displaying progress information.
 Remove it if you don\[aq]t need this information.
 .PP
-Since this can cause data loss, test first with the \f[C]--dry-run\f[R]
+Since this can cause data loss, test first with the \f[V]--dry-run\f[R]
 flag to see exactly what would be copied and deleted.
 .PP
 The sync can be done also from Storj to the local file system.
@@ -68651,9 +69251,9 @@ rclone sync --interactive --progress s3:bucket/path/to/dir/ storj:bucket/path/to
 .fi
 .SS Limitations
 .PP
-\f[C]rclone about\f[R] is not supported by the rclone Storj backend.
+\f[V]rclone about\f[R] is not supported by the rclone Storj backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -68661,8 +69261,8 @@ about (https://rclone.org/overview/#optional-features) and rclone
 about (https://rclone.org/commands/rclone_about/)
 .SS Known issues
 .PP
-If you get errors like \f[C]too many open files\f[R] this usually
-happens when the default \f[C]ulimit\f[R] for system max open files is
+If you get errors like \f[V]too many open files\f[R] this usually
+happens when the default \f[V]ulimit\f[R] for system max open files is
 exceeded.
 Native Storj protocol opens a large number of TCP connections (each of
 which is counted as an open file).
@@ -68675,13 +69275,13 @@ If you do many transfers you eventually open a connection to most
 storage nodes (thousands of nodes).
 .PP
 To fix these, please raise your system limits.
-You can do this issuing a \f[C]ulimit -n 65536\f[R] just before you run
+You can do this issuing a \f[V]ulimit -n 65536\f[R] just before you run
 rclone.
 To change the limits more permanently you can add this to your shell
 startup script, e.g.
-\f[C]$HOME/.bashrc\f[R], or change the system-wide configuration,
-usually \f[C]/etc/sysctl.conf\f[R] and/or
-\f[C]/etc/security/limits.conf\f[R], but please refer to your operating
+\f[V]$HOME/.bashrc\f[R], or change the system-wide configuration,
+usually \f[V]/etc/sysctl.conf\f[R] and/or
+\f[V]/etc/security/limits.conf\f[R], but please refer to your operating
 system manual.
 .SH SugarSync
 .PP
@@ -68692,9 +69292,9 @@ backup, access, syncing, and sharing.
 .PP
 The initial setup for SugarSync involves getting a token from SugarSync
 which you can do with rclone.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -68762,7 +69362,7 @@ y/e/d> y
 Note that the config asks for your email and password but doesn\[aq]t
 store them, it only uses them to get the initial token.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories (sync folders) in top level of your SugarSync
 .IP
@@ -68788,10 +69388,10 @@ rclone copy /home/source remote:backup
 \f[R]
 .fi
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .PP
 \f[B]NB\f[R] you can\[aq]t create files in the top level folder you have
 to create a folder, which rclone will create as a \[dq]Sync Folder\[dq]
@@ -68799,8 +69399,8 @@ with SugarSync.
 .SS Modification times and hashes
 .PP
 SugarSync does not support modification times or hashes, therefore
-syncing will default to \f[C]--size-only\f[R] checking.
-Note that using \f[C]--update\f[R] will work as rclone can read the time
+syncing will default to \f[V]--size-only\f[R] checking.
+Note that using \f[V]--update\f[R] will work as rclone can read the time
 files were uploaded.
 .SS Restricted filename characters
 .PP
@@ -68815,8 +69415,8 @@ be used in XML strings.
 Deleted files will be moved to the \[dq]Deleted items\[dq] folder by
 default.
 .PP
-However you can supply the flag \f[C]--sugarsync-hard-delete\f[R] or set
-the config parameter \f[C]hard_delete = true\f[R] if you would like
+However you can supply the flag \f[V]--sugarsync-hard-delete\f[R] or set
+the config parameter \f[V]hard_delete = true\f[R] if you would like
 files to be deleted straight away.
 .SS Standard options
 .PP
@@ -69004,9 +69604,9 @@ Type: string
 Required: false
 .SS Limitations
 .PP
-\f[C]rclone about\f[R] is not supported by the SugarSync backend.
+\f[V]rclone about\f[R] is not supported by the SugarSync backend.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -69014,16 +69614,16 @@ about (https://rclone.org/overview/#optional-features) and rclone
 about (https://rclone.org/commands/rclone_about/)
 .SH Uloz.to
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .PP
 The initial setup for Uloz.to involves filling in the user credentials.
-\f[C]rclone config\f[R] walks you through it.
+\f[V]rclone config\f[R] walks you through it.
 .SS Configuration
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -69086,7 +69686,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List folders in root level folder:
 .IP
@@ -69129,7 +69729,7 @@ Timestamps are stored with microsecond precision.
 A server calculated MD5 hash of the file is verified upon upload.
 Afterwards, the backend only serves the client-side calculated hashes.
 Hashes can also be retrieved upon creating a file download link, but
-it\[aq]s impractical for \f[C]list\f[R]-like use cases.
+it\[aq]s impractical for \f[V]list\f[R]-like use cases.
 .SS Restricted filename characters
 .PP
 In addition to the default restricted characters
@@ -69152,7 +69752,7 @@ T{
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 .TE
 .PP
@@ -69163,7 +69763,7 @@ be used in JSON strings.
 .PP
 All files are currently uploaded using a single HTTP request, so for
 uploading large files a stable connection is necessary.
-Rclone will upload up to \f[C]--transfers\f[R] chunks at the same time
+Rclone will upload up to \f[V]--transfers\f[R] chunks at the same time
 (shared among all uploads).
 .SS Deleting files
 .PP
@@ -69174,8 +69774,8 @@ Trashed files are permanently deleted after 30 days in the recycle bin.
 Emptying the trash is currently not implemented in rclone.
 .SS Root folder ID
 .PP
-You can set the \f[C]root_folder_slug\f[R] for rclone.
-This is the folder (identified by its \f[C]Folder slug\f[R]) that rclone
+You can set the \f[V]root_folder_slug\f[R] for rclone.
+This is the folder (identified by its \f[V]Folder slug\f[R]) that rclone
 considers to be the root of your Uloz.to drive.
 .PP
 Normally you will leave this blank and rclone will determine the correct
@@ -69183,20 +69783,20 @@ root to use itself.
 However you can set this to restrict rclone to a specific folder
 hierarchy.
 .PP
-In order to do this you will have to find the \f[C]Folder slug\f[R] of
+In order to do this you will have to find the \f[V]Folder slug\f[R] of
 the folder you wish to use as root.
 This will be the last segment of the URL when you open the relevant
 folder in the Uloz.to web interface.
 .PP
 For example, for exploring a folder with URL
-\f[C]https://uloz.to/fm/my-files/foobar\f[R], \f[C]foobar\f[R] should be
+\f[V]https://uloz.to/fm/my-files/foobar\f[R], \f[V]foobar\f[R] should be
 used as the root slug.
 .PP
-\f[C]root_folder_slug\f[R] can be used alongside a specific path in the
+\f[V]root_folder_slug\f[R] can be used alongside a specific path in the
 remote path.
-For example, if your remote\[aq]s \f[C]root_folder_slug\f[R] corresponds
-to \f[C]/foo/bar\f[R], \f[C]remote:baz/qux\f[R] will refer to
-\f[C]ABSOLUTE_ULOZTO_ROOT/foo/bar/baz/qux\f[R].
+For example, if your remote\[aq]s \f[V]root_folder_slug\f[R] corresponds
+to \f[V]/foo/bar\f[R], \f[V]remote:baz/qux\f[R] will refer to
+\f[V]ABSOLUTE_ULOZTO_ROOT/foo/bar/baz/qux\f[R].
 .SS Standard options
 .PP
 Here are the Standard options specific to ulozto (Uloz.to).
@@ -69310,9 +69910,9 @@ Type: string
 Required: false
 .SS Limitations
 .PP
-Uloz.to file names can\[aq]t have the \f[C]\[rs]\f[R] character in.
+Uloz.to file names can\[aq]t have the \f[V]\[rs]\f[R] character in.
 rclone maps this to and from an identical looking unicode equivalent
-\f[C]\[uFF3C]\f[R] (U+FF3C Fullwidth Reverse Solidus).
+\f[V]＼\f[R] (U+FF3C Fullwidth Reverse Solidus).
 .PP
 Uloz.to only supports filenames up to 255 characters in length.
 .PP
@@ -69322,11 +69922,11 @@ Practical testing reveals that hitting the rate limit during normal use
 is very rare, although not impossible with higher number of concurrently
 uploaded files.
 .PP
-\f[C]rclone about\f[R] is not supported by the Uloz.to backend.
+\f[V]rclone about\f[R] is not supported by the Uloz.to backend.
 Although there\[aq]s an endpoint to retrieve the information for the UI,
 it\[aq]s not exposed in the API.
 Backends without this capability cannot determine free space for an
-rclone mount or use policy \f[C]mfs\f[R] (most free space) as a member
+rclone mount or use policy \f[V]mfs\f[R] (most free space) as a member
 of an rclone union remote.
 .PP
 See List of backends that do not support rclone
@@ -69338,17 +69938,17 @@ This is a Backend for Uptobox file storage service.
 Uptobox is closer to a one-click hoster than a traditional cloud storage
 provider and therefore not suitable for long term storage.
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 To configure an Uptobox backend you\[aq]ll need your personal api token.
 You\[aq]ll find it in your account
 settings (https://uptobox.com/my_account)
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R] with
+Here is an example of how to make a remote called \f[V]remote\f[R] with
 the default setup.
 First run:
 .IP
@@ -69407,7 +70007,7 @@ y/e/d>
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your Uptobox
 .IP
@@ -69435,7 +70035,7 @@ rclone copy /home/source remote:backup
 .SS Modification times and hashes
 .PP
 Uptobox supports neither modified times nor checksums.
-All timestamps will read as that set by \f[C]--default-time\f[R].
+All timestamps will read as that set by \f[V]--default-time\f[R].
 .SS Restricted filename characters
 .PP
 In addition to the default restricted characters
@@ -69458,14 +70058,14 @@ T{
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 \[ga]
 T}@T{
 0x41
 T}@T{
-\[uFF40]
+｀
 T}
 .TE
 .PP
@@ -69541,43 +70141,43 @@ Required: false
 Uptobox will delete inactive files that have not been accessed in 60
 days.
 .PP
-\f[C]rclone about\f[R] is not supported by this backend an overview of
+\f[V]rclone about\f[R] is not supported by this backend an overview of
 used space can however been seen in the uptobox web interface.
 .SH Union
 .PP
-The \f[C]union\f[R] backend joins several remotes together to make a
+The \f[V]union\f[R] backend joins several remotes together to make a
 single unified view of them.
 .PP
-During the initial setup with \f[C]rclone config\f[R] you will specify
+During the initial setup with \f[V]rclone config\f[R] you will specify
 the upstream remotes as a space separated list.
 The upstream remotes can either be a local paths or other remotes.
 .PP
-The attributes \f[C]:ro\f[R], \f[C]:nc\f[R] and \f[C]:writeback\f[R] can
+The attributes \f[V]:ro\f[R], \f[V]:nc\f[R] and \f[V]:writeback\f[R] can
 be attached to the end of the remote to tag the remote as \f[B]read
 only\f[R], \f[B]no create\f[R] or \f[B]writeback\f[R], e.g.
-\f[C]remote:directory/subdirectory:ro\f[R] or
-\f[C]remote:directory/subdirectory:nc\f[R].
+\f[V]remote:directory/subdirectory:ro\f[R] or
+\f[V]remote:directory/subdirectory:nc\f[R].
 .IP \[bu] 2
-\f[C]:ro\f[R] means files will only be read from here and never written
+\f[V]:ro\f[R] means files will only be read from here and never written
 .IP \[bu] 2
-\f[C]:nc\f[R] means new files or directories won\[aq]t be created here
+\f[V]:nc\f[R] means new files or directories won\[aq]t be created here
 .IP \[bu] 2
-\f[C]:writeback\f[R] means files found in different remotes will be
+\f[V]:writeback\f[R] means files found in different remotes will be
 written back here.
 See the writeback section for more info.
 .PP
 Subfolders can be used in upstream remotes.
-Assume a union remote named \f[C]backup\f[R] with the remotes
-\f[C]mydrive:private/backup\f[R].
-Invoking \f[C]rclone mkdir backup:desktop\f[R] is exactly the same as
-invoking \f[C]rclone mkdir mydrive:private/backup/desktop\f[R].
+Assume a union remote named \f[V]backup\f[R] with the remotes
+\f[V]mydrive:private/backup\f[R].
+Invoking \f[V]rclone mkdir backup:desktop\f[R] is exactly the same as
+invoking \f[V]rclone mkdir mydrive:private/backup/desktop\f[R].
 .PP
-There is no special handling of paths containing \f[C]..\f[R] segments.
-Invoking \f[C]rclone mkdir backup:../desktop\f[R] is exactly the same as
-invoking \f[C]rclone mkdir mydrive:private/backup/../desktop\f[R].
+There is no special handling of paths containing \f[V]..\f[R] segments.
+Invoking \f[V]rclone mkdir backup:../desktop\f[R] is exactly the same as
+invoking \f[V]rclone mkdir mydrive:private/backup/../desktop\f[R].
 .SS Configuration
 .PP
-Here is an example of how to make a union called \f[C]remote\f[R] for
+Here is an example of how to make a union called \f[V]remote\f[R] for
 local folders.
 First run:
 .IP
@@ -69647,10 +70247,10 @@ e/n/d/r/c/s/q> q
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
-List directories in top level in \f[C]remote1:dir1\f[R],
-\f[C]remote2:dir2\f[R] and \f[C]remote3:dir3\f[R]
+List directories in top level in \f[V]remote1:dir1\f[R],
+\f[V]remote2:dir2\f[R] and \f[V]remote3:dir3\f[R]
 .IP
 .nf
 \f[C]
@@ -69658,8 +70258,8 @@ rclone lsd remote:
 \f[R]
 .fi
 .PP
-List all the files in \f[C]remote1:dir1\f[R], \f[C]remote2:dir2\f[R] and
-\f[C]remote3:dir3\f[R]
+List all the files in \f[V]remote1:dir1\f[R], \f[V]remote2:dir2\f[R] and
+\f[V]remote3:dir3\f[R]
 .IP
 .nf
 \f[C]
@@ -69668,7 +70268,7 @@ rclone ls remote:
 .fi
 .PP
 Copy another local directory to the union directory called source, which
-will be placed into \f[C]remote3:dir3\f[R]
+will be placed into \f[V]remote3:dir3\f[R]
 .IP
 .nf
 \f[C]
@@ -69687,7 +70287,7 @@ Any policy can be assigned to a function or category though some may not
 be very useful in practice.
 For instance: \f[B]rand\f[R] (random) may be useful for file creation
 (create) but could lead to very odd behavior if used for
-\f[C]delete\f[R] if there were more than one copy of the file.
+\f[V]delete\f[R] if there were more than one copy of the file.
 .SS Function / Category classifications
 .PP
 .TS
@@ -69733,12 +70333,12 @@ T}
 .SS Path Preservation
 .PP
 Policies, as described below, are of two basic types.
-\f[C]path preserving\f[R] and \f[C]non-path preserving\f[R].
+\f[V]path preserving\f[R] and \f[V]non-path preserving\f[R].
 .PP
-All policies which start with \f[C]ep\f[R] (\f[B]epff\f[R],
+All policies which start with \f[V]ep\f[R] (\f[B]epff\f[R],
 \f[B]eplfs\f[R], \f[B]eplus\f[R], \f[B]epmfs\f[R], \f[B]eprand\f[R]) are
-\f[C]path preserving\f[R].
-\f[C]ep\f[R] stands for \f[C]existing path\f[R].
+\f[V]path preserving\f[R].
+\f[V]ep\f[R] stands for \f[V]existing path\f[R].
 .PP
 A path preserving policy will only consider upstreams where the relative
 path being accessed already exists.
@@ -69783,7 +70383,7 @@ T}
 .TE
 .PP
 To check if your upstream supports the field, run
-\f[C]rclone about remote: [flags]\f[R] and see if the required field
+\f[V]rclone about remote: [flags]\f[R] and see if the required field
 exists.
 .SS Filters
 .PP
@@ -69919,7 +70519,7 @@ T}
 .TE
 .SS Writeback
 .PP
-The tag \f[C]:writeback\f[R] on an upstream remote can be used to make a
+The tag \f[V]:writeback\f[R] on an upstream remote can be used to make a
 simple cache system like this:
 .IP
 .nf
@@ -69933,21 +70533,21 @@ upstreams = /local:writeback remote:dir
 \f[R]
 .fi
 .PP
-When files are opened for read, if the file is in \f[C]remote:dir\f[R]
-but not \f[C]/local\f[R] then rclone will copy the file entirely into
-\f[C]/local\f[R] before returning a reference to the file in
-\f[C]/local\f[R].
-The copy will be done with the equivalent of \f[C]rclone copy\f[R] so
-will use \f[C]--multi-thread-streams\f[R] if configured.
+When files are opened for read, if the file is in \f[V]remote:dir\f[R]
+but not \f[V]/local\f[R] then rclone will copy the file entirely into
+\f[V]/local\f[R] before returning a reference to the file in
+\f[V]/local\f[R].
+The copy will be done with the equivalent of \f[V]rclone copy\f[R] so
+will use \f[V]--multi-thread-streams\f[R] if configured.
 Any copies will be logged with an INFO log.
 .PP
 When files are written, they will be written to both
-\f[C]remote:dir\f[R] and \f[C]/local\f[R].
+\f[V]remote:dir\f[R] and \f[V]/local\f[R].
 .PP
-As many remotes as desired can be added to \f[C]upstreams\f[R] but there
-should only be one \f[C]:writeback\f[R] tag.
+As many remotes as desired can be added to \f[V]upstreams\f[R] but there
+should only be one \f[V]:writeback\f[R] tag.
 .PP
-Rclone does not manage the \f[C]:writeback\f[R] remote in any way other
+Rclone does not manage the \f[V]:writeback\f[R] remote in any way other
 than writing files back to it.
 So if you need to expire old files or manage the size then you will have
 to do this yourself.
@@ -70065,10 +70665,10 @@ Any metadata supported by the underlying remote is read and written.
 See the metadata (https://rclone.org/docs/#metadata) docs for more info.
 .SH WebDAV
 .PP
-Paths are specified as \f[C]remote:path\f[R]
+Paths are specified as \f[V]remote:path\f[R]
 .PP
 Paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Configuration
 .PP
 To configure the WebDAV remote you will need to have a URL for it, and a
@@ -70076,7 +70676,7 @@ username and password.
 If you know what kind of system you are connecting to then rclone can
 enable extra features.
 .PP
-Here is an example of how to make a remote called \f[C]remote\f[R].
+Here is an example of how to make a remote called \f[V]remote\f[R].
 First run:
 .IP
 .nf
@@ -70154,7 +70754,7 @@ y/e/d> y
 \f[R]
 .fi
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 List directories in top level of your WebDAV
 .IP
@@ -70466,28 +71066,28 @@ Required: false
 See below for notes on specific providers.
 .SS Fastmail Files
 .PP
-Use \f[C]https://webdav.fastmail.com/\f[R] or a subdirectory as the URL,
-and your Fastmail email \f[C]username\[at]domain.tld\f[R] as the
+Use \f[V]https://webdav.fastmail.com/\f[R] or a subdirectory as the URL,
+and your Fastmail email \f[V]username\[at]domain.tld\f[R] as the
 username.
 Follow this
 documentation (https://www.fastmail.help/hc/en-us/articles/360058752854-App-passwords)
-to create an app password with access to \f[C]Files (WebDAV)\f[R] and
+to create an app password with access to \f[V]Files (WebDAV)\f[R] and
 use this as the password.
 .PP
-Fastmail supports modified times using the \f[C]X-OC-Mtime\f[R] header.
+Fastmail supports modified times using the \f[V]X-OC-Mtime\f[R] header.
 .SS Owncloud
 .PP
 Click on the settings cog in the bottom right of the page and this will
 show the WebDAV URL that rclone needs in the config step.
 It will look something like
-\f[C]https://example.com/remote.php/webdav/\f[R].
+\f[V]https://example.com/remote.php/webdav/\f[R].
 .PP
-Owncloud supports modified times using the \f[C]X-OC-Mtime\f[R] header.
+Owncloud supports modified times using the \f[V]X-OC-Mtime\f[R] header.
 .SS Nextcloud
 .PP
 This is configured in an identical way to Owncloud.
 Note that Nextcloud initially did not support streaming of files
-(\f[C]rcat\f[R]) whereas Owncloud did, but
+(\f[V]rcat\f[R]) whereas Owncloud did, but
 this (https://github.com/nextcloud/nextcloud-snap/issues/365) seems to
 be fixed as of 2020-11-27 (tested with rclone v1.53.1 and Nextcloud
 Server v19).
@@ -70511,18 +71111,18 @@ Go here (https://onedrive.live.com/about/en-us/signin/) to open your
 OneDrive or to sign in
 .IP \[bu] 2
 Now take a look at your address bar, the URL should look like this:
-\f[C]https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/_layouts/15/onedrive.aspx\f[R]
+\f[V]https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/_layouts/15/onedrive.aspx\f[R]
 .PP
 You\[aq]ll only need this URL up to the email address.
 After that, you\[aq]ll most likely want to add \[dq]/Documents\[dq].
 That subdirectory contains the actual data stored on your OneDrive.
 .PP
-Add the remote to rclone like this: Configure the \f[C]url\f[R] as
-\f[C]https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/Documents\f[R]
-and use your normal account email and password for \f[C]user\f[R] and
-\f[C]pass\f[R].
+Add the remote to rclone like this: Configure the \f[V]url\f[R] as
+\f[V]https://[YOUR-DOMAIN]-my.sharepoint.com/personal/[YOUR-EMAIL]/Documents\f[R]
+and use your normal account email and password for \f[V]user\f[R] and
+\f[V]pass\f[R].
 If you have 2FA enabled, you have to generate an app password.
-Set the \f[C]vendor\f[R] to \f[C]sharepoint\f[R].
+Set the \f[V]vendor\f[R] to \f[V]sharepoint\f[R].
 .PP
 Your config file should look like this:
 .IP
@@ -70541,7 +71141,7 @@ pass = encryptedpassword
 Use this option in case your (hosted) Sharepoint is not tied to OneDrive
 accounts and uses NTLM authentication.
 .PP
-To get the \f[C]url\f[R] configuration, similarly to the above, first
+To get the \f[V]url\f[R] configuration, similarly to the above, first
 navigate to the desired directory in your browser to get the URL, then
 strip everything after the name of the opened directory.
 .PP
@@ -70551,10 +71151,10 @@ https://example.sharepoint.com/sites/12345/Documents/Forms/AllItems.aspx
 The configuration to use would be:
 https://example.sharepoint.com/sites/12345/Documents
 .PP
-Set the \f[C]vendor\f[R] to \f[C]sharepoint-ntlm\f[R].
+Set the \f[V]vendor\f[R] to \f[V]sharepoint-ntlm\f[R].
 .PP
 NTLM uses domain and user name combination for authentication, set
-\f[C]user\f[R] to \f[C]DOMAIN\[rs]username\f[R].
+\f[V]user\f[R] to \f[V]DOMAIN\[rs]username\f[R].
 .PP
 Your config file should look like this:
 .IP
@@ -70576,9 +71176,10 @@ compare if a file has been changed since the upload / which file is
 newer.
 .PP
 For Rclone calls copying files (especially Office files such as .docx,
-\&.xlsx, etc.) from/to SharePoint (like copy, sync, etc.), you should
-append these flags to ensure Rclone uses the \[dq]Last Modified\[dq]
-datetime property to compare your documents:
+\&.xlsx, etc.)
+from/to SharePoint (like copy, sync, etc.), you should append these
+flags to ensure Rclone uses the \[dq]Last Modified\[dq] datetime
+property to compare your documents:
 .IP
 .nf
 \f[C]
@@ -70591,7 +71192,7 @@ Use this option if you are hosting remotes over WebDAV provided by
 rclone.
 Read rclone serve webdav for more details.
 .PP
-rclone serve supports modified times using the \f[C]X-OC-Mtime\f[R]
+rclone serve supports modified times using the \f[V]X-OC-Mtime\f[R]
 header.
 .SS dCache
 .PP
@@ -70603,9 +71204,9 @@ Macaroons (https://www.dcache.org/manuals/workshop-2017-05-29-Umea/000-Final/anu
 and OpenID-Connect (https://en.wikipedia.org/wiki/OpenID_Connect) access
 tokens.
 .PP
-Configure as normal using the \f[C]other\f[R] type.
+Configure as normal using the \f[V]other\f[R] type.
 Don\[aq]t enter a username or password, instead enter your Macaroon as
-the \f[C]bearer_token\f[R].
+the \f[V]bearer_token\f[R].
 .PP
 The config will end up looking something like this.
 .IP
@@ -70639,7 +71240,7 @@ software package called
 oidc-agent (https://github.com/indigo-dc/oidc-agent).
 This is a command-line tool that facilitates obtaining an access token.
 Once installed and configured, an access token is obtained by running
-the \f[C]oidc-token\f[R] command.
+the \f[V]oidc-token\f[R] command.
 The following example shows a (shortened) access token obtained from the
 \f[I]XDC\f[R] OIDC Provider.
 .IP
@@ -70651,22 +71252,22 @@ paul\[at]celebrimbor:\[ti]$
 \f[R]
 .fi
 .PP
-\f[B]Note\f[R] Before the \f[C]oidc-token\f[R] command will work, the
+\f[B]Note\f[R] Before the \f[V]oidc-token\f[R] command will work, the
 refresh token must be loaded into the oidc agent.
-This is done with the \f[C]oidc-add\f[R] command (e.g.,
-\f[C]oidc-add XDC\f[R]).
+This is done with the \f[V]oidc-add\f[R] command (e.g.,
+\f[V]oidc-add XDC\f[R]).
 This is typically done once per login session.
 Full details on this and how to register oidc-agent with your OIDC
 Provider are provided in the oidc-agent
 documentation (https://indigo-dc.gitbooks.io/oidc-agent/).
 .PP
-The rclone \f[C]bearer_token_command\f[R] configuration option is used
+The rclone \f[V]bearer_token_command\f[R] configuration option is used
 to fetch the access token from oidc-agent.
 .PP
 Configure as a normal WebDAV endpoint, using the \[aq]other\[aq] vendor,
 leaving the username and password empty.
 When prompted, choose to edit the advanced config and enter the command
-to get a bearer token (e.g., \f[C]oidc-agent XDC\f[R]).
+to get a bearer token (e.g., \f[V]oidc-agent XDC\f[R]).
 .PP
 The following example config shows a WebDAV endpoint that uses
 oidc-agent to supply an access token from the \f[I]XDC\f[R] OIDC
@@ -70749,10 +71350,10 @@ Note that rclone runs a webserver on your local machine to collect the
 token as returned from Yandex Disk.
 This only runs from the moment it opens your browser to the moment you
 get back the verification code.
-This is on \f[C]http://127.0.0.1:53682/\f[R] and this it may require you
+This is on \f[V]http://127.0.0.1:53682/\f[R] and this it may require you
 to unblock it temporarily if you are running a host firewall.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 See top level directories
 .IP
@@ -70778,7 +71379,7 @@ rclone ls remote:directory
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote path, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote path, deleting any
 excess files in the path.
 .IP
 .nf
@@ -70788,24 +71389,24 @@ rclone sync --interactive /home/local/directory remote:directory
 .fi
 .PP
 Yandex paths may be as deep as required, e.g.
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Modification times and hashes
 .PP
 Modified times are supported and are stored accurate to 1 ns in custom
-metadata called \f[C]rclone_modified\f[R] in RFC3339 with nanoseconds
+metadata called \f[V]rclone_modified\f[R] in RFC3339 with nanoseconds
 format.
 .PP
 The MD5 hash algorithm is natively supported by Yandex Disk.
 .SS Emptying Trash
 .PP
 If you wish to empty your trash you can use the
-\f[C]rclone cleanup remote:\f[R] command which will permanently delete
+\f[V]rclone cleanup remote:\f[R] command which will permanently delete
 all your trashed files.
 This command does not take any path arguments.
 .SS Quota information
 .PP
 To view your current quota you can use the
-\f[C]rclone about remote:\f[R] command which will display your usage
+\f[V]rclone about remote:\f[R] command which will display your usage
 limit (quota) and the current usage.
 .SS Restricted filename characters
 .PP
@@ -70954,17 +71555,17 @@ Required: false
 .SS Limitations
 .PP
 When uploading very large files (bigger than about 5 GiB) you will need
-to increase the \f[C]--timeout\f[R] parameter.
+to increase the \f[V]--timeout\f[R] parameter.
 This is because Yandex pauses (perhaps to calculate the MD5SUM for the
 entire file) before returning confirmation that the file has been
 uploaded.
 The default handling of timeouts in rclone is to assume a 5 minute pause
 is an error and close the connection - you\[aq]ll see
-\f[C]net/http: timeout awaiting response headers\f[R] errors in the logs
+\f[V]net/http: timeout awaiting response headers\f[R] errors in the logs
 if this is happening.
 Setting the timeout to twice the max size of file in GiB should be
 enough, so if you want to upload a 30 GiB file set a timeout of
-\f[C]2 * 30 = 60m\f[R], that is \f[C]--timeout 60m\f[R].
+\f[V]2 * 30 = 60m\f[R], that is \f[V]--timeout 60m\f[R].
 .PP
 Having a Yandex Mail account is mandatory to use the Yandex.Disk
 subscription.
@@ -71062,11 +71663,11 @@ Rclone runs a webserver on your local computer to collect the
 authorization token from Zoho Workdrive.
 This is only from the moment your browser is opened until the token is
 returned.
-The webserver runs on \f[C]http://127.0.0.1:53682/\f[R].
-If local port \f[C]53682\f[R] is protected by a firewall you may need to
+The webserver runs on \f[V]http://127.0.0.1:53682/\f[R].
+If local port \f[V]53682\f[R] is protected by a firewall you may need to
 temporarily unblock the firewall to complete authorization.
 .PP
-Once configured you can then use \f[C]rclone\f[R] like this,
+Once configured you can then use \f[V]rclone\f[R] like this,
 .PP
 See top level directories
 .IP
@@ -71092,7 +71693,7 @@ rclone ls remote:directory
 \f[R]
 .fi
 .PP
-Sync \f[C]/home/local/directory\f[R] to the remote path, deleting any
+Sync \f[V]/home/local/directory\f[R] to the remote path, deleting any
 excess files in the path.
 .IP
 .nf
@@ -71102,7 +71703,7 @@ rclone sync --interactive /home/local/directory remote:directory
 .fi
 .PP
 Zoho paths may be as deep as required, eg
-\f[C]remote:directory/subdirectory\f[R].
+\f[V]remote:directory/subdirectory\f[R].
 .SS Modification times and hashes
 .PP
 Modified times are currently not supported for Zoho Workdrive
@@ -71111,7 +71712,7 @@ No hash algorithms are supported.
 .SS Usage information
 .PP
 To view your current quota you can use the
-\f[C]rclone about remote:\f[R] command which will display your current
+\f[V]rclone about remote:\f[R] command which will display your current
 usage.
 .SS Restricted filename characters
 .PP
@@ -71292,7 +71893,7 @@ Log in to the Zoho API Console (https://api-console.zoho.com)
 .IP "2." 3
 Create a new client of type \[dq]Server-based Application\[dq].
 The name and website don\[aq]t matter, but you must add the redirect URL
-\f[C]http://localhost:53682/\f[R].
+\f[V]http://localhost:53682/\f[R].
 .IP "3." 3
 Once the client is created, you can go to the settings tab and enable it
 in other regions.
@@ -71301,7 +71902,7 @@ The client id and client secret can now be used with rclone.
 .SH Local Filesystem
 .PP
 Local paths are specified as normal filesystem paths, e.g.
-\f[C]/path/to/wherever\f[R], so
+\f[V]/path/to/wherever\f[R], so
 .IP
 .nf
 \f[C]
@@ -71309,13 +71910,13 @@ rclone sync --interactive /home/source /tmp/destination
 \f[R]
 .fi
 .PP
-Will sync \f[C]/home/source\f[R] to \f[C]/tmp/destination\f[R].
+Will sync \f[V]/home/source\f[R] to \f[V]/tmp/destination\f[R].
 .SS Configuration
 .PP
 For consistencies sake one can also configure a remote of type
-\f[C]local\f[R] in the config file, and access the local filesystem
+\f[V]local\f[R] in the config file, and access the local filesystem
 using rclone remote paths, e.g.
-\f[C]remote:path/to/wherever\f[R], but it is probably easier not to.
+\f[V]remote:path/to/wherever\f[R], but it is probably easier not to.
 .SS Modification times
 .PP
 Rclone reads and writes the modification times using an accuracy
@@ -71329,16 +71930,15 @@ This is the normal case for Windows and OS X.
 There is a bit more uncertainty in the Linux world, but new
 distributions will have UTF-8 encoded files names.
 If you are using an old Linux filesystem with non UTF-8 file names (e.g.
-latin1) then you can use the \f[C]convmv\f[R] tool to convert the
+latin1) then you can use the \f[V]convmv\f[R] tool to convert the
 filesystem to UTF-8.
 This tool is available in most distributions\[aq] package managers.
 .PP
 If an invalid (non-UTF8) filename is read, the invalid characters will
 be replaced with a quoted representation of the invalid bytes.
-The name \f[C]gro\[rs]xdf\f[R] will be transferred as
-\f[C]gro\[u201B]DF\f[R].
-\f[C]rclone\f[R] will emit a debug message in this case (use
-\f[C]-v\f[R] to see), e.g.
+The name \f[V]gro\[rs]xdf\f[R] will be transferred as \f[V]gro‛DF\f[R].
+\f[V]rclone\f[R] will emit a debug message in this case (use
+\f[V]-v\f[R] to see), e.g.
 .IP
 .nf
 \f[C]
@@ -71350,7 +71950,7 @@ Local file system at .: Replacing invalid UTF-8 characters in \[dq]gro\[rs]xdf\[
 With the local backend, restrictions on the characters that are usable
 in file or directory names depend on the operating system.
 To check what rclone will replace by default on your system, run
-\f[C]rclone help flags local-encoding\f[R].
+\f[V]rclone help flags local-encoding\f[R].
 .PP
 On non Windows platforms the following characters are replaced when
 handling file names.
@@ -71371,14 +71971,14 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 .TE
 .PP
@@ -71402,287 +72002,287 @@ NUL
 T}@T{
 0x00
 T}@T{
-\[u2400]
+␀
 T}
 T{
 SOH
 T}@T{
 0x01
 T}@T{
-\[u2401]
+␁
 T}
 T{
 STX
 T}@T{
 0x02
 T}@T{
-\[u2402]
+␂
 T}
 T{
 ETX
 T}@T{
 0x03
 T}@T{
-\[u2403]
+␃
 T}
 T{
 EOT
 T}@T{
 0x04
 T}@T{
-\[u2404]
+␄
 T}
 T{
 ENQ
 T}@T{
 0x05
 T}@T{
-\[u2405]
+␅
 T}
 T{
 ACK
 T}@T{
 0x06
 T}@T{
-\[u2406]
+␆
 T}
 T{
 BEL
 T}@T{
 0x07
 T}@T{
-\[u2407]
+␇
 T}
 T{
 BS
 T}@T{
 0x08
 T}@T{
-\[u2408]
+␈
 T}
 T{
 HT
 T}@T{
 0x09
 T}@T{
-\[u2409]
+␉
 T}
 T{
 LF
 T}@T{
 0x0A
 T}@T{
-\[u240A]
+␊
 T}
 T{
 VT
 T}@T{
 0x0B
 T}@T{
-\[u240B]
+␋
 T}
 T{
 FF
 T}@T{
 0x0C
 T}@T{
-\[u240C]
+␌
 T}
 T{
 CR
 T}@T{
 0x0D
 T}@T{
-\[u240D]
+␍
 T}
 T{
 SO
 T}@T{
 0x0E
 T}@T{
-\[u240E]
+␎
 T}
 T{
 SI
 T}@T{
 0x0F
 T}@T{
-\[u240F]
+␏
 T}
 T{
 DLE
 T}@T{
 0x10
 T}@T{
-\[u2410]
+␐
 T}
 T{
 DC1
 T}@T{
 0x11
 T}@T{
-\[u2411]
+␑
 T}
 T{
 DC2
 T}@T{
 0x12
 T}@T{
-\[u2412]
+␒
 T}
 T{
 DC3
 T}@T{
 0x13
 T}@T{
-\[u2413]
+␓
 T}
 T{
 DC4
 T}@T{
 0x14
 T}@T{
-\[u2414]
+␔
 T}
 T{
 NAK
 T}@T{
 0x15
 T}@T{
-\[u2415]
+␕
 T}
 T{
 SYN
 T}@T{
 0x16
 T}@T{
-\[u2416]
+␖
 T}
 T{
 ETB
 T}@T{
 0x17
 T}@T{
-\[u2417]
+␗
 T}
 T{
 CAN
 T}@T{
 0x18
 T}@T{
-\[u2418]
+␘
 T}
 T{
 EM
 T}@T{
 0x19
 T}@T{
-\[u2419]
+␙
 T}
 T{
 SUB
 T}@T{
 0x1A
 T}@T{
-\[u241A]
+␚
 T}
 T{
 ESC
 T}@T{
 0x1B
 T}@T{
-\[u241B]
+␛
 T}
 T{
 FS
 T}@T{
 0x1C
 T}@T{
-\[u241C]
+␜
 T}
 T{
 GS
 T}@T{
 0x1D
 T}@T{
-\[u241D]
+␝
 T}
 T{
 RS
 T}@T{
 0x1E
 T}@T{
-\[u241E]
+␞
 T}
 T{
 US
 T}@T{
 0x1F
 T}@T{
-\[u241F]
+␟
 T}
 T{
 /
 T}@T{
 0x2F
 T}@T{
-\[uFF0F]
+／
 T}
 T{
 \[dq]
 T}@T{
 0x22
 T}@T{
-\[uFF02]
+＂
 T}
 T{
 *
 T}@T{
 0x2A
 T}@T{
-\[uFF0A]
+＊
 T}
 T{
 :
 T}@T{
 0x3A
 T}@T{
-\[uFF1A]
+：
 T}
 T{
 <
 T}@T{
 0x3C
 T}@T{
-\[uFF1C]
+＜
 T}
 T{
 >
 T}@T{
 0x3E
 T}@T{
-\[uFF1E]
+＞
 T}
 T{
 ?
 T}@T{
 0x3F
 T}@T{
-\[uFF1F]
+？
 T}
 T{
 \[rs]
 T}@T{
 0x5C
 T}@T{
-\[uFF3C]
+＼
 T}
 T{
 |
 T}@T{
 0x7C
 T}@T{
-\[uFF5C]
+｜
 T}
 .TE
 .PP
@@ -71705,14 +72305,14 @@ SP
 T}@T{
 0x20
 T}@T{
-\[u2420]
+␠
 T}
 T{
 \&.
 T}@T{
 0x2E
 T}@T{
-\[uFF0E]
+．
 T}
 .TE
 .PP
@@ -71724,25 +72324,25 @@ be converted to UTF-16.
 On Windows there are many ways of specifying a path to a file system
 resource.
 Local paths can be absolute, like
-\f[C]C:\[rs]path\[rs]to\[rs]wherever\f[R], or relative, like
-\f[C]..\[rs]wherever\f[R].
-Network paths in UNC format, \f[C]\[rs]\[rs]server\[rs]share\f[R], are
+\f[V]C:\[rs]path\[rs]to\[rs]wherever\f[R], or relative, like
+\f[V]..\[rs]wherever\f[R].
+Network paths in UNC format, \f[V]\[rs]\[rs]server\[rs]share\f[R], are
 also supported.
-Path separator can be either \f[C]\[rs]\f[R] (as in
-\f[C]C:\[rs]path\[rs]to\[rs]wherever\f[R]) or \f[C]/\f[R] (as in
-\f[C]C:/path/to/wherever\f[R]).
+Path separator can be either \f[V]\[rs]\f[R] (as in
+\f[V]C:\[rs]path\[rs]to\[rs]wherever\f[R]) or \f[V]/\f[R] (as in
+\f[V]C:/path/to/wherever\f[R]).
 Length of these paths are limited to 259 characters for files and 247
 characters for directories, but there is an alternative extended-length
 path format increasing the limit to (approximately) 32,767 characters.
 This format requires absolute paths and the use of prefix
-\f[C]\[rs]\[rs]?\[rs]\f[R], e.g.
-\f[C]\[rs]\[rs]?\[rs]D:\[rs]some\[rs]very\[rs]long\[rs]path\f[R].
+\f[V]\[rs]\[rs]?\[rs]\f[R], e.g.
+\f[V]\[rs]\[rs]?\[rs]D:\[rs]some\[rs]very\[rs]long\[rs]path\f[R].
 For convenience rclone will automatically convert regular paths into the
 corresponding extended-length paths, so in most cases you do not have to
 worry about this (read more below).
-Using the same prefix \f[C]\[rs]\[rs]?\[rs]\f[R] it is also possible to
+Using the same prefix \f[V]\[rs]\[rs]?\[rs]\f[R] it is also possible to
 specify path to volumes identified by their GUID, e.g.
-\f[C]\[rs]\[rs]?\[rs]Volume{b75e2c83-0000-0000-0000-602f00000000}\[rs]some\[rs]path\f[R].
+\f[V]\[rs]\[rs]?\[rs]Volume{b75e2c83-0000-0000-0000-602f00000000}\[rs]some\[rs]path\f[R].
 .SS Long paths
 .PP
 Rclone handles long paths automatically, by converting all paths to
@@ -71751,17 +72351,17 @@ format (https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-
 which allows paths up to 32,767 characters.
 .PP
 This conversion will ensure paths are absolute and prefix them with the
-\f[C]\[rs]\[rs]?\[rs]\f[R].
+\f[V]\[rs]\[rs]?\[rs]\f[R].
 This is why you will see that your paths, for instance
-\f[C].\[rs]files\f[R] is shown as path
-\f[C]\[rs]\[rs]?\[rs]C:\[rs]files\f[R] in the output, and
-\f[C]\[rs]\[rs]server\[rs]share\f[R] as
-\f[C]\[rs]\[rs]?\[rs]UNC\[rs]server\[rs]share\f[R].
+\f[V].\[rs]files\f[R] is shown as path
+\f[V]\[rs]\[rs]?\[rs]C:\[rs]files\f[R] in the output, and
+\f[V]\[rs]\[rs]server\[rs]share\f[R] as
+\f[V]\[rs]\[rs]?\[rs]UNC\[rs]server\[rs]share\f[R].
 .PP
 However, in rare cases this may cause problems with buggy file system
 drivers like EncFS (https://github.com/rclone/rclone/issues/261).
 To disable UNC conversion globally, add this to your
-\f[C].rclone.conf\f[R] file:
+\f[V].rclone.conf\f[R] file:
 .IP
 .nf
 \f[C]
@@ -71783,10 +72383,10 @@ nounc = true
 .PP
 And use rclone like this:
 .PP
-\f[C]rclone copy c:\[rs]src nounc:z:\[rs]dst\f[R]
+\f[V]rclone copy c:\[rs]src nounc:z:\[rs]dst\f[R]
 .PP
-This will use UNC paths on \f[C]c:\[rs]src\f[R] but not on
-\f[C]z:\[rs]dst\f[R].
+This will use UNC paths on \f[V]c:\[rs]src\f[R] but not on
+\f[V]z:\[rs]dst\f[R].
 Of course this will cause problems if the absolute path length of a file
 exceeds 259 characters on z, so only use this option if you have to.
 .SS Symlinks / Junction points
@@ -71794,10 +72394,10 @@ exceeds 259 characters on z, so only use this option if you have to.
 Normally rclone will ignore symlinks or junction points (which behave
 like symlinks under Windows).
 .PP
-If you supply \f[C]--copy-links\f[R] or \f[C]-L\f[R] then rclone will
+If you supply \f[V]--copy-links\f[R] or \f[V]-L\f[R] then rclone will
 follow the symlink and copy the pointed to file or directory.
-Note that this flag is incompatible with \f[C]--links\f[R] /
-\f[C]-l\f[R].
+Note that this flag is incompatible with \f[V]--links\f[R] /
+\f[V]-l\f[R].
 .PP
 This flag applies to all commands.
 .PP
@@ -71807,11 +72407,11 @@ For example, supposing you have a directory structure like this
 \f[C]
 $ tree /tmp/a
 /tmp/a
-\[u251C]\[u2500]\[u2500] b -> ../b
-\[u251C]\[u2500]\[u2500] expected -> ../expected
-\[u251C]\[u2500]\[u2500] one
-\[u2514]\[u2500]\[u2500] two
-    \[u2514]\[u2500]\[u2500] three
+├── b -> ../b
+├── expected -> ../expected
+├── one
+└── two
+    └── three
 \f[R]
 .fi
 .PP
@@ -71857,8 +72457,8 @@ For example, supposing you have a directory structure like this
 \f[C]
 $ tree /tmp/a
 /tmp/a
-\[u251C]\[u2500]\[u2500] file1 -> ./file4
-\[u2514]\[u2500]\[u2500] file2 -> /home/user/file3
+├── file1 -> ./file4
+└── file2 -> /home/user/file3
 \f[R]
 .fi
 .PP
@@ -71900,8 +72500,8 @@ $ rclone copy -l remote:/tmp/a/ /tmp/b/
 
 $ tree /tmp/b
 /tmp/b
-\[u251C]\[u2500]\[u2500] file1 -> ./file4
-\[u2514]\[u2500]\[u2500] file2 -> /home/user/file3
+├── file1 -> ./file4
+└── file2 -> /home/user/file3
 \f[R]
 .fi
 .PP
@@ -71913,13 +72513,13 @@ $ rclone copyto remote:/tmp/a/ /tmp/b/
 
 $ tree /tmp/b
 /tmp/b
-\[u251C]\[u2500]\[u2500] file1.rclonelink
-\[u2514]\[u2500]\[u2500] file2.rclonelink
+├── file1.rclonelink
+└── file2.rclonelink
 \f[R]
 .fi
 .PP
-If you want to copy a single file with \f[C]-l\f[R] then you must use
-the \f[C].rclonelink\f[R] suffix.
+If you want to copy a single file with \f[V]-l\f[R] then you must use
+the \f[V].rclonelink\f[R] suffix.
 .IP
 .nf
 \f[C]
@@ -71927,17 +72527,17 @@ $ rclone copy -l remote:/tmp/a/file1.rclonelink /tmp/c
 
 $ tree /tmp/c
 /tmp/c
-\[u2514]\[u2500]\[u2500] file1 -> ./file4
+└── file1 -> ./file4
 \f[R]
 .fi
 .PP
-Note that this flag is incompatible with \f[C]-copy-links\f[R] /
-\f[C]-L\f[R].
+Note that this flag is incompatible with \f[V]-copy-links\f[R] /
+\f[V]-L\f[R].
 .SS Restricting filesystems with --one-file-system
 .PP
 Normally rclone will recurse through filesystems as mounted.
 .PP
-However if you set \f[C]--one-file-system\f[R] or \f[C]-x\f[R] this
+However if you set \f[V]--one-file-system\f[R] or \f[V]-x\f[R] this
 tells rclone to stay in the filesystem specified by the root and not to
 recurse into different file systems.
 .PP
@@ -71946,17 +72546,17 @@ For example if you have a directory hierarchy like this
 .nf
 \f[C]
 root
-\[u251C]\[u2500]\[u2500] disk1     - disk1 mounted on the root
-\[br]\ \  \[u2514]\[u2500]\[u2500] file3 - stored on disk1
-\[u251C]\[u2500]\[u2500] disk2     - disk2 mounted on the root
-\[br]\ \  \[u2514]\[u2500]\[u2500] file4 - stored on disk12
-\[u251C]\[u2500]\[u2500] file1     - stored on the root disk
-\[u2514]\[u2500]\[u2500] file2     - stored on the root disk
+├── disk1     - disk1 mounted on the root
+│\ \  └── file3 - stored on disk1
+├── disk2     - disk2 mounted on the root
+│\ \  └── file4 - stored on disk12
+├── file1     - stored on the root disk
+└── file2     - stored on the root disk
 \f[R]
 .fi
 .PP
-Using \f[C]rclone --one-file-system copy root remote:\f[R] will only
-copy \f[C]file1\f[R] and \f[C]file2\f[R].
+Using \f[V]rclone --one-file-system copy root remote:\f[R] will only
+copy \f[V]file1\f[R] and \f[V]file2\f[R].
 Eg
 .IP
 .nf
@@ -71977,8 +72577,8 @@ $ rclone -q ls root
 \f[R]
 .fi
 .PP
-\f[B]NB\f[R] Rclone (like most unix tools such as \f[C]du\f[R],
-\f[C]rsync\f[R] and \f[C]tar\f[R]) treats a bind mount to the same
+\f[B]NB\f[R] Rclone (like most unix tools such as \f[V]du\f[R],
+\f[V]rsync\f[R] and \f[V]tar\f[R]) treats a bind mount to the same
 device as being on the same filesystem.
 .PP
 \f[B]NB\f[R] This flag is only available on Unix based systems.
@@ -72214,7 +72814,8 @@ will affect the other if subsequently modified.
 Cloning is usually preferable to copying, as it is much faster and is
 deduplicated by default (i.e.
 having two identical files does not consume more storage than having
-just one.) However, for use cases where data redundancy is preferable,
+just one.)
+However, for use cases where data redundancy is preferable,
 --local-no-clone can be used to disable cloning and force \[dq]deep\[dq]
 copies.
 .PP
@@ -72538,10 +73139,10 @@ Security fixes
 .RS 2
 .IP \[bu] 2
 local backend: CVE-2024-52522: fix permission and ownership on symlinks
-with \f[C]--links\f[R] and \f[C]--metadata\f[R] (Nick Craig-Wood)
+with \f[V]--links\f[R] and \f[V]--metadata\f[R] (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-Only affects users using \f[C]--metadata\f[R] and \f[C]--links\f[R] and
+Only affects users using \f[V]--metadata\f[R] and \f[V]--links\f[R] and
 copying files to the local backend
 .IP \[bu] 2
 See
@@ -72579,10 +73180,10 @@ doc fixes (Nick Craig-Wood, tgfisher, Alexandre Hamez, Randy Bush)
 Local
 .RS 2
 .IP \[bu] 2
-Fix permission and ownership on symlinks with \f[C]--links\f[R] and
-\f[C]--metadata\f[R] (Nick Craig-Wood)
+Fix permission and ownership on symlinks with \f[V]--links\f[R] and
+\f[V]--metadata\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--copy-links\f[R] on macOS when cloning (nielash)
+Fix \f[V]--copy-links\f[R] on macOS when cloning (nielash)
 .RE
 .IP \[bu] 2
 Onedrive
@@ -72603,7 +73204,7 @@ Craig-Wood)
 S3
 .RS 2
 .IP \[bu] 2
-Fix crash when using \f[C]--s3-download-url\f[R] after migration to
+Fix crash when using \f[V]--s3-download-url\f[R] after migration to
 SDKv2 (Nick Craig-Wood)
 .IP \[bu] 2
 Storj provider: fix server-side copy of files bigger than 5GB (Kaloyan
@@ -72625,15 +73226,15 @@ doc fixes (Nick Craig-Wood, Pawel Palucha)
 fs
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--dump filters\f[R] not always appearing (Nick Craig-Wood)
+Fix \f[V]--dump filters\f[R] not always appearing (Nick Craig-Wood)
 .IP \[bu] 2
-Fix setting \f[C]stringArray\f[R] config values from environment
+Fix setting \f[V]stringArray\f[R] config values from environment
 variables (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-rc: Fix default value of \f[C]--metrics-addr\f[R] (Nick Craig-Wood)
+rc: Fix default value of \f[V]--metrics-addr\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-serve docker: Add missing \f[C]vfs-read-chunk-streams\f[R] option in
+serve docker: Add missing \f[V]vfs-read-chunk-streams\f[R] option in
 docker volume driver (Divyam)
 .RE
 .IP \[bu] 2
@@ -72653,7 +73254,7 @@ Fix login issue where token retrieval fails (wiserain)
 S3
 .RS 2
 .IP \[bu] 2
-Fix rclone ignoring static credentials when \f[C]env_auth=true\f[R]
+Fix rclone ignoring static credentials when \f[V]env_auth=true\f[R]
 (Nick Craig-Wood)
 .RE
 .SS v1.68.0 - 2024-09-08
@@ -72709,7 +73310,7 @@ Disable wasm/js build due to go bug
 .IP \[bu] 2
 Enable custom linting rules with ruleguard via gocritic (albertony)
 .IP \[bu] 2
-Update logging statements to make \f[C]--use-json-log\f[R] work always
+Update logging statements to make \f[V]--use-json-log\f[R] work always
 (albertony)
 .IP \[bu] 2
 Adding new code quality tests and fixing the fallout (albertony)
@@ -72727,16 +73328,16 @@ Make listing of remotes more consistent (albertony)
 .IP \[bu] 2
 Make getting config values more consistent (albertony)
 .IP \[bu] 2
-Use \f[C]--password-command\f[R] to set config file password if supplied
+Use \f[V]--password-command\f[R] to set config file password if supplied
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 doc fixes (albertony, crystalstall, David Seifert, Eng Zer Jun, Ernie
 Hershey, Florian Klink, John Oxley, kapitainsky, Mathieu Moreau, Nick
-Craig-Wood, nipil, P\['e]tr Bozs\['o], Russ Bubley, Sam Harrison,
-Thearas, URenko, Will Miles, yuval-cloudinary)
+Craig-Wood, nipil, Pétr Bozsó, Russ Bubley, Sam Harrison, Thearas,
+URenko, Will Miles, yuval-cloudinary)
 .IP \[bu] 2
-fs: Allow semicolons as well as spaces in \f[C]--bwlimit\f[R] timetable
+fs: Allow semicolons as well as spaces in \f[V]--bwlimit\f[R] timetable
 parsing (Kyle Reynolds)
 .IP \[bu] 2
 help
@@ -72748,7 +73349,7 @@ Make help command output less distracting (albertony)
 .RE
 .IP \[bu] 2
 lib/encoder: Add Raw encoding for use where no encoding at all is
-required, eg \f[C]--local-encoding Raw\f[R] (URenko)
+required, eg \f[V]--local-encoding Raw\f[R] (URenko)
 .IP \[bu] 2
 listremotes: Added options for filtering, ordering and json output
 (albertony)
@@ -72756,10 +73357,10 @@ listremotes: Added options for filtering, ordering and json output
 nfsmount
 .RS 2
 .IP \[bu] 2
-Make the \f[C]--sudo\f[R] flag work for umount as well as mount (Nick
+Make the \f[V]--sudo\f[R] flag work for umount as well as mount (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]-o tcp\f[R] option to NFS mount options to fix mounting under
+Add \f[V]-o tcp\f[R] option to NFS mount options to fix mounting under
 Linux (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -72781,10 +73382,10 @@ the upload queue (Nick Craig-Wood)
 Add vfs/queue-set-expiry (https://rclone.org/rc/#vfs-queue-set-expiry)
 to adjust expiry of items in the VFS queue (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--unix-socket\f[R] option to \f[C]rc\f[R] command (Florian
+Add \f[V]--unix-socket\f[R] option to \f[V]rc\f[R] command (Florian
 Klink)
 .IP \[bu] 2
-Prevent unmount rc command from sending a \f[C]STOPPING=1\f[R] sd-notify
+Prevent unmount rc command from sending a \f[V]STOPPING=1\f[R] sd-notify
 message (AThePeanut4)
 .RE
 .IP \[bu] 2
@@ -72797,7 +73398,7 @@ serve dlna
 .IP \[bu] 2
 Also look at \[dq]Subs\[dq] subdirectory (Florian Klink)
 .IP \[bu] 2
-Don\[aq]t swallow \f[C]video.{idx,sub}\f[R] (Florian Klink)
+Don\[aq]t swallow \f[V]video.{idx,sub}\f[R] (Florian Klink)
 .IP \[bu] 2
 Set more correct mime type (Florian Klink)
 .RE
@@ -72806,7 +73407,7 @@ serve nfs
 .RS 2
 .IP \[bu] 2
 Implement on disk cache for file handles selected with
-\f[C]--nfs-cache-type\f[R] (Nick Craig-Wood)
+\f[V]--nfs-cache-type\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Add tracing to filesystem calls (Nick Craig-Wood)
 .IP \[bu] 2
@@ -72821,9 +73422,9 @@ Fix incorrect user id and group id exported to NFS (Nick Craig-Wood)
 serve s3
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--auth-proxy\f[R] (Sawjan Gurung)
+Implement \f[V]--auth-proxy\f[R] (Sawjan Gurung)
 .IP \[bu] 2
-Update to AWS SDKv2 by updating \f[C]github.com/rclone/gofakes3\f[R]
+Update to AWS SDKv2 by updating \f[V]github.com/rclone/gofakes3\f[R]
 (Nick Craig-Wood)
 .RE
 .RE
@@ -72860,11 +73461,11 @@ Fix encoding of root path fix (URenko)
 Add server-side copy (using clone) with xattrs on macOS (nielash)
 .RS 2
 .IP \[bu] 2
-\f[C]--local-no-clone\f[R] flag to disable cloning for server-side
+\f[V]--local-no-clone\f[R] flag to disable cloning for server-side
 copies (nielash)
 .RE
 .IP \[bu] 2
-Support setting custom \f[C]--metadata\f[R] during server-side Copy
+Support setting custom \f[V]--metadata\f[R] during server-side Copy
 (nielash)
 .RE
 .IP \[bu] 2
@@ -72918,9 +73519,9 @@ Fix nil pointer error when uploading small files (Nick Craig-Wood)
 Pcloud
 .RS 2
 .IP \[bu] 2
-Implement \f[C]SetModTime\f[R] (Georg Welzel)
+Implement \f[V]SetModTime\f[R] (Georg Welzel)
 .IP \[bu] 2
-Implement \f[C]OpenWriterAt\f[R] feature to enable multipart uploads
+Implement \f[V]OpenWriterAt\f[R] feature to enable multipart uploads
 (Georg Welzel)
 .RE
 .IP \[bu] 2
@@ -72931,9 +73532,9 @@ Improve data consistency by ensuring async tasks complete (wiserain)
 .IP \[bu] 2
 Implement custom hash to replace wrong sha1 (wiserain)
 .IP \[bu] 2
-Fix error with \f[C]copyto\f[R] command (wiserain)
+Fix error with \f[V]copyto\f[R] command (wiserain)
 .IP \[bu] 2
-Optimize file move by removing unnecessary \f[C]readMetaData()\f[R] call
+Optimize file move by removing unnecessary \f[V]readMetaData()\f[R] call
 (wiserain)
 .IP \[bu] 2
 Non-buffered hash calculation for local source files (wiserain)
@@ -72951,7 +73552,7 @@ S3
 Update to using AWS SDK v2 (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-Add \f[C]--s3-sdk-log-mode\f[R] to control SDKv2 debugging (Nick
+Add \f[V]--s3-sdk-log-mode\f[R] to control SDKv2 debugging (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -72963,7 +73564,7 @@ Allow restoring from intelligent-tiering storage class (Pawel Palucha)
 SFTP
 .RS 2
 .IP \[bu] 2
-Use \f[C]uint32\f[R] for mtime to save memory (Tomasz Melcer)
+Use \f[V]uint32\f[R] for mtime to save memory (Tomasz Melcer)
 .IP \[bu] 2
 Ignore useless errors when closing the connection pool (Nick Craig-Wood)
 .IP \[bu] 2
@@ -72975,7 +73576,7 @@ Swift
 .IP \[bu] 2
 Add workarounds for bad listings in Ceph RGW (Paul Collins)
 .IP \[bu] 2
-Add total/free space info in \f[C]about\f[R] command.
+Add total/free space info in \f[V]about\f[R] command.
 (fsantagostinobietti)
 .RE
 .IP \[bu] 2
@@ -72988,7 +73589,7 @@ Fix upload of > 2GB files on 32 bit platforms (Tobias Markus)
 WebDAV
 .RS 2
 .IP \[bu] 2
-Add \f[C]--webdav-unix-socket-path\f[R] to connect to a unix socket
+Add \f[V]--webdav-unix-socket-path\f[R] to connect to a unix socket
 (Florian Klink)
 .RE
 .IP \[bu] 2
@@ -72996,7 +73597,7 @@ Yandex
 .RS 2
 .IP \[bu] 2
 Implement custom user agent to help with upload speeds (Sebastian
-B\[:u]nger)
+Bünger)
 .RE
 .IP \[bu] 2
 Zoho
@@ -73038,11 +73639,11 @@ Reynolds)
 build
 .RS 2
 .IP \[bu] 2
-Fix \f[C]CVE-2023-45288\f[R] by upgrading \f[C]golang.org/x/net\f[R]
+Fix \f[V]CVE-2023-45288\f[R] by upgrading \f[V]golang.org/x/net\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]CVE-2024-35255\f[R] by upgrading
-\f[C]github.com/Azure/azure-sdk-for-go/sdk/azidentity\f[R] to 1.6.0
+Fix \f[V]CVE-2024-35255\f[R] by upgrading
+\f[V]github.com/Azure/azure-sdk-for-go/sdk/azidentity\f[R] to 1.6.0
 (dependabot)
 .IP \[bu] 2
 Convert source files with CRLF to LF (albertony)
@@ -73050,17 +73651,16 @@ Convert source files with CRLF to LF (albertony)
 Update all dependencies (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-doc updates (albertony, Alex Garel, Dave Nicolson, Dominik Joe
-Pant\[u016F]\[u010D]ek, Eric Wolf, Erisa A, Evan Harris, Evan McBeth,
-Gachoud Philippe, hidewrong, jakzoe, jumbi77, kapitainsky, Kyle
-Reynolds, Lewis Hook, Nick Craig-Wood, overallteach, pawsey-kbuckley,
-Pieter van Oostrum, psychopatt, racerole, static-moonlight, Warrentheo,
-yudrywet, yumeiyin )
+doc updates (albertony, Alex Garel, Dave Nicolson, Dominik Joe Pantůček,
+Eric Wolf, Erisa A, Evan Harris, Evan McBeth, Gachoud Philippe,
+hidewrong, jakzoe, jumbi77, kapitainsky, Kyle Reynolds, Lewis Hook, Nick
+Craig-Wood, overallteach, pawsey-kbuckley, Pieter van Oostrum,
+psychopatt, racerole, static-moonlight, Warrentheo, yudrywet, yumeiyin )
 .IP \[bu] 2
 ncdu: Do not quit on Esc to aid usability (Katia Esposito)
 .IP \[bu] 2
-rcserver: Set \f[C]ModTime\f[R] for dirs and files served by
-\f[C]--rc-serve\f[R] (Nikita Shoshin)
+rcserver: Set \f[V]ModTime\f[R] for dirs and files served by
+\f[V]--rc-serve\f[R] (Nikita Shoshin)
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -73069,19 +73669,19 @@ Bug Fixes
 bisync: Add integration tests against all backends and fix many many
 problems (nielash)
 .IP \[bu] 2
-config: Fix default value for \f[C]description\f[R] (Nick Craig-Wood)
+config: Fix default value for \f[V]description\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-copy: Fix \f[C]nil\f[R] pointer dereference when corrupted on transfer
-with \f[C]nil\f[R] dst (nielash)
+copy: Fix \f[V]nil\f[R] pointer dereference when corrupted on transfer
+with \f[V]nil\f[R] dst (nielash)
 .IP \[bu] 2
 fs
 .RS 2
 .IP \[bu] 2
-Improve JSON Unmarshalling for \f[C]Duration\f[R] types (Kyle Reynolds)
+Improve JSON Unmarshalling for \f[V]Duration\f[R] types (Kyle Reynolds)
 .IP \[bu] 2
 Close the CPU profile on exit (guangwu)
 .IP \[bu] 2
-Replace \f[C]/bin/bash\f[R] with \f[C]/usr/bin/env bash\f[R] (Florian
+Replace \f[V]/bin/bash\f[R] with \f[V]/usr/bin/env bash\f[R] (Florian
 Klink)
 .RE
 .IP \[bu] 2
@@ -73090,16 +73690,16 @@ oauthutil: Clear client secret if client ID is set (Michael Terry)
 operations
 .RS 2
 .IP \[bu] 2
-Rework \f[C]rcat\f[R] so that it doesn\[aq]t call the
-\f[C]--metadata-mapper\f[R] twice (Nick Craig-Wood)
+Rework \f[V]rcat\f[R] so that it doesn\[aq]t call the
+\f[V]--metadata-mapper\f[R] twice (Nick Craig-Wood)
 .IP \[bu] 2
-Ensure \f[C]SrcFsType\f[R] is set correctly when using
-\f[C]--metadata-mapper\f[R] (Nick Craig-Wood)
+Ensure \f[V]SrcFsType\f[R] is set correctly when using
+\f[V]--metadata-mapper\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix \[dq]optional feature not implemented\[dq] error with a crypted sftp
 bug (Nick Craig-Wood)
 .IP \[bu] 2
-Fix very long file names when using copy with \f[C]--partial\f[R] (Nick
+Fix very long file names when using copy with \f[V]--partial\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix retries downloading too much data with certain backends (Nick
@@ -73107,7 +73707,7 @@ Craig-Wood)
 .IP \[bu] 2
 Fix move when dst is nil and fdst is case-insensitive (nielash)
 .IP \[bu] 2
-Fix lsjson \f[C]--encrypted\f[R] when using \f[C]--crypt-XXX\f[R]
+Fix lsjson \f[V]--encrypted\f[R] when using \f[V]--crypt-XXX\f[R]
 parameters (Nick Craig-Wood)
 .IP \[bu] 2
 Fix missing metadata for multipart transfers to local disk (Nick
@@ -73121,28 +73721,28 @@ Fix hashing problem in integration tests (Nick Craig-Wood)
 rc
 .RS 2
 .IP \[bu] 2
-Fix stats groups being ignored in \f[C]operations/check\f[R] (Nick
+Fix stats groups being ignored in \f[V]operations/check\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix incorrect \f[C]Content-Type\f[R] in HTTP API (Kyle Reynolds)
+Fix incorrect \f[V]Content-Type\f[R] in HTTP API (Kyle Reynolds)
 .RE
 .IP \[bu] 2
 serve s3
 .RS 2
 .IP \[bu] 2
-Fix \f[C]Last-Modified\f[R] header format (Butanediol)
+Fix \f[V]Last-Modified\f[R] header format (Butanediol)
 .IP \[bu] 2
 Fix in-memory metadata storing wrong modtime (nielash)
 .IP \[bu] 2
 Fix XML of error message (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-serve webdav: Fix webdav with \f[C]--baseurl\f[R] under Windows (Nick
+serve webdav: Fix webdav with \f[V]--baseurl\f[R] under Windows (Nick
 Craig-Wood)
 .IP \[bu] 2
-serve dlna: Make \f[C]BrowseMetadata\f[R] more compliant (albertony)
+serve dlna: Make \f[V]BrowseMetadata\f[R] more compliant (albertony)
 .IP \[bu] 2
-serve http: Added \f[C]Content-Length\f[R] header when HTML directory is
+serve http: Added \f[V]Content-Length\f[R] header when HTML directory is
 served (Sunny)
 .IP \[bu] 2
 sync
@@ -73160,7 +73760,7 @@ Fix management of empty directories to make it more accurate (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix creation of empty directories when
-\f[C]--create-empty-src-dirs=false\f[R] (Nick Craig-Wood)
+\f[V]--create-empty-src-dirs=false\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix directory modification times not being set (Nick Craig-Wood)
 .IP \[bu] 2
@@ -73173,13 +73773,13 @@ implemented (Nick Craig-Wood)
 .IP \[bu] 2
 test info: Improve cleanup of temp files (Kyle Reynolds)
 .IP \[bu] 2
-touch: Fix using \f[C]-R\f[R] on certain backends (Nick Craig-Wood)
+touch: Fix using \f[V]-R\f[R] on certain backends (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Mount
 .RS 2
 .IP \[bu] 2
-Add \f[C]--direct-io\f[R] flag to force uncached access (Nick
+Add \f[V]--direct-io\f[R] flag to force uncached access (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -73194,11 +73794,11 @@ Fix renaming a directory (nielash)
 Local
 .RS 2
 .IP \[bu] 2
-Add \f[C]--local-time-type\f[R] to use
-\f[C]mtime\f[R]/\f[C]atime\f[R]/\f[C]btime\f[R]/\f[C]ctime\f[R] as the
+Add \f[V]--local-time-type\f[R] to use
+\f[V]mtime\f[R]/\f[V]atime\f[R]/\f[V]btime\f[R]/\f[V]ctime\f[R] as the
 time (Nick Craig-Wood)
 .IP \[bu] 2
-Allow \f[C]SeBackupPrivilege\f[R] and/or \f[C]SeRestorePrivilege\f[R] to
+Allow \f[V]SeBackupPrivilege\f[R] and/or \f[V]SeRestorePrivilege\f[R] to
 work on Windows (Charles Hamilton)
 .RE
 .IP \[bu] 2
@@ -73248,17 +73848,17 @@ Make errors setting permissions into no retry errors (Nick Craig-Wood)
 .IP \[bu] 2
 Fix description being overwritten on server side moves (Nick Craig-Wood)
 .IP \[bu] 2
-Allow setting metadata to fail if \f[C]failok\f[R] flag is set (Nick
+Allow setting metadata to fail if \f[V]failok\f[R] flag is set (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix panic when using \f[C]--metadata-mapper\f[R] on large google doc
+Fix panic when using \f[V]--metadata-mapper\f[R] on large google doc
 files (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Dropbox
 .RS 2
 .IP \[bu] 2
-Add \f[C]--dropbox-root-namespace\f[R] to override the root namespace
+Add \f[V]--dropbox-root-namespace\f[R] to override the root namespace
 (Bill Fraser)
 .RE
 .IP \[bu] 2
@@ -73277,7 +73877,7 @@ Fix f.String() not including subpath (nielash)
 Http
 .RS 2
 .IP \[bu] 2
-Add \f[C]--http-no-escape\f[R] to not escape URL metacharacters in path
+Add \f[V]--http-no-escape\f[R] to not escape URL metacharacters in path
 names (Kyle Reynolds)
 .RE
 .IP \[bu] 2
@@ -73317,7 +73917,7 @@ Fix incorrect list entries when rooted at subdirectory (nielash)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--onedrive-hard-delete\f[R] to permanently delete files (Nick
+Add \f[V]--onedrive-hard-delete\f[R] to permanently delete files (Nick
 Craig-Wood)
 .IP \[bu] 2
 Make server-side copy work in more scenarios (YukiUnHappy)
@@ -73325,7 +73925,7 @@ Make server-side copy work in more scenarios (YukiUnHappy)
 Fix \[dq]unauthenticated: Unauthenticated\[dq] errors when downloading
 (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--metadata-mapper\f[R] being called twice if writing
+Fix \f[V]--metadata-mapper\f[R] being called twice if writing
 permissions (nielash)
 .IP \[bu] 2
 Set all metadata permissions and return error summary instead of
@@ -73339,7 +73939,7 @@ Fix references to deprecated permissions properties (nielash)
 .IP \[bu] 2
 Add support for group permissions (nielash)
 .IP \[bu] 2
-Allow setting permissions to fail if \f[C]failok\f[R] flag is set (Nick
+Allow setting permissions to fail if \f[V]failok\f[R] flag is set (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -73358,7 +73958,7 @@ Implement configurable chunk size for multipart upload (wiserain)
 Protondrive
 .RS 2
 .IP \[bu] 2
-Don\[aq]t auth with an empty access token (Micha\[/l] Dzienisiewicz)
+Don\[aq]t auth with an empty access token (Michał Dzienisiewicz)
 .RE
 .IP \[bu] 2
 Qingstor
@@ -73376,7 +73976,7 @@ Fix f.String() not including subpath (nielash)
 S3
 .RS 2
 .IP \[bu] 2
-Add new AWS region \f[C]il-central-1\f[R] Tel Aviv (yoelvini)
+Add new AWS region \f[V]il-central-1\f[R] Tel Aviv (yoelvini)
 .IP \[bu] 2
 Update Scaleway\[aq]s configuration options (Alexandre Lavigne)
 .IP \[bu] 2
@@ -73387,20 +73987,20 @@ Fix encoding issue with dir path comparison (nielash)
 .IP \[bu] 2
 Fix 405 error on HEAD for delete marker with versionId (nielash)
 .IP \[bu] 2
-Validate \f[C]--s3-copy-cutoff\f[R] size before copy (hoyho)
+Validate \f[V]--s3-copy-cutoff\f[R] size before copy (hoyho)
 .RE
 .IP \[bu] 2
 SFTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--sftp-connections\f[R] to limit the maximum number of
+Add \f[V]--sftp-connections\f[R] to limit the maximum number of
 connections (Tomasz Melcer)
 .RE
 .IP \[bu] 2
 Storj
 .RS 2
 .IP \[bu] 2
-Update \f[C]storj.io/uplink\f[R] to latest release (JT Olio)
+Update \f[V]storj.io/uplink\f[R] to latest release (JT Olio)
 .IP \[bu] 2
 Update bio on request (Nick Craig-Wood)
 .RE
@@ -73408,7 +74008,7 @@ Update bio on request (Nick Craig-Wood)
 Swift
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--swift-use-segments-container\f[R] to allow >5G files on
+Implement \f[V]--swift-use-segments-container\f[R] to allow >5G files on
 Blomp (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -73425,9 +74025,8 @@ WebDAV
 Fix setting modification times erasing checksums on owncloud and
 nextcloud (nielash)
 .IP \[bu] 2
-owncloud: Add \f[C]--webdav-owncloud-exclude-mounts\f[R] which allows
-excluding mounted folders when listing remote resources (Thomas
-M\[:u]ller)
+owncloud: Add \f[V]--webdav-owncloud-exclude-mounts\f[R] which allows
+excluding mounted folders when listing remote resources (Thomas Müller)
 .RE
 .IP \[bu] 2
 Zoho
@@ -73460,16 +74059,16 @@ This can be disabled with
 --no-update-dir-modtime (https://rclone.org/docs/#no-update-dir-modtime)
 .IP \[bu] 2
 See the overview (https://rclone.org/overview/#features) and look for
-the \f[C]D\f[R] flags in the \f[C]ModTime\f[R] column to see which
+the \f[V]D\f[R] flags in the \f[V]ModTime\f[R] column to see which
 backends support it.
 .RE
 .IP \[bu] 2
 Rclone will now sync directory metadata if the backend supports it when
-\f[C]-M\f[R]/\f[C]--metadata\f[R] is in use.
+\f[V]-M\f[R]/\f[V]--metadata\f[R] is in use.
 .RS 2
 .IP \[bu] 2
 See the overview (https://rclone.org/overview/#features) and look for
-the \f[C]D\f[R] flags in the \f[C]Metadata\f[R] column to see which
+the \f[V]D\f[R] flags in the \f[V]Metadata\f[R] column to see which
 backends support it.
 .RE
 .IP \[bu] 2
@@ -73499,12 +74098,12 @@ build
 Update to go1.22 and make go1.20 the minimum required version (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]CVE-2024-24786\f[R] by upgrading
-\f[C]google.golang.org/protobuf\f[R] (Nick Craig-Wood)
+Fix \f[V]CVE-2024-24786\f[R] by upgrading
+\f[V]google.golang.org/protobuf\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-check: Respect \f[C]--no-unicode-normalization\f[R] and
-\f[C]--ignore-case-sync\f[R] for \f[C]--checkfile\f[R] (nielash)
+check: Respect \f[V]--no-unicode-normalization\f[R] and
+\f[V]--ignore-case-sync\f[R] for \f[V]--checkfile\f[R] (nielash)
 .IP \[bu] 2
 cmd: Much improved shell auto completion which reduces the size of the
 completion file and works faster (Nick Craig-Wood)
@@ -73518,7 +74117,7 @@ fs: Add more detailed logging for file includes/excludes (Kyle Reynolds)
 lsf
 .RS 2
 .IP \[bu] 2
-Add \f[C]--time-format\f[R] flag (nielash)
+Add \f[V]--time-format\f[R] flag (nielash)
 .IP \[bu] 2
 Make metadata appear for directories (Nick Craig-Wood)
 .RE
@@ -73528,13 +74127,13 @@ lsjson: Make metadata appear for directories (Nick Craig-Wood)
 rc
 .RS 2
 .IP \[bu] 2
-Add \f[C]srcFs\f[R] and \f[C]dstFs\f[R] to \f[C]core/stats\f[R] and
-\f[C]core/transferred\f[R] stats (Nick Craig-Wood)
+Add \f[V]srcFs\f[R] and \f[V]dstFs\f[R] to \f[V]core/stats\f[R] and
+\f[V]core/transferred\f[R] stats (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]operations/hashsum\f[R] to the rc as \f[C]rclone hashsum\f[R]
+Add \f[V]operations/hashsum\f[R] to the rc as \f[V]rclone hashsum\f[R]
 equivalent (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]config/paths\f[R] to the rc as \f[C]rclone config paths\f[R]
+Add \f[V]config/paths\f[R] to the rc as \f[V]rclone config paths\f[R]
 equivalent (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -73558,7 +74157,7 @@ Bug Fixes
 backend
 .RS 2
 .IP \[bu] 2
-Make backends which use oauth implement the \f[C]Shutdown\f[R] and
+Make backends which use oauth implement the \f[V]Shutdown\f[R] and
 shutdown the oauth properly (rkonfj)
 .RE
 .IP \[bu] 2
@@ -73568,12 +74167,12 @@ bisync
 Handle unicode and case normalization consistently (nielash)
 .IP \[bu] 2
 Partial uploads known issue on
-\f[C]local\f[R]/\f[C]ftp\f[R]/\f[C]sftp\f[R] has been resolved (unless
-using \f[C]--inplace\f[R]) (nielash)
+\f[V]local\f[R]/\f[V]ftp\f[R]/\f[V]sftp\f[R] has been resolved (unless
+using \f[V]--inplace\f[R]) (nielash)
 .IP \[bu] 2
 Fixed handling of unicode normalization and case insensitivity, support
-for \f[C]--fix-case\f[R] (https://rclone.org/docs/#fix-case),
-\f[C]--ignore-case-sync\f[R], \f[C]--no-unicode-normalization\f[R]
+for \f[V]--fix-case\f[R] (https://rclone.org/docs/#fix-case),
+\f[V]--ignore-case-sync\f[R], \f[V]--no-unicode-normalization\f[R]
 (nielash)
 .IP \[bu] 2
 Bisync no longer fails to find the correct listing file when configs are
@@ -73586,7 +74185,7 @@ nfsmount
 .IP \[bu] 2
 Fix exit after external unmount (nielash)
 .IP \[bu] 2
-Fix \f[C]--volname\f[R] being ignored (nielash)
+Fix \f[V]--volname\f[R] being ignored (nielash)
 .RE
 .IP \[bu] 2
 operations
@@ -73611,7 +74210,7 @@ serve nfs: Fix writing files via Finder on macOS (nielash)
 .IP \[bu] 2
 serve restic: Fix error handling (Michael Eischer)
 .IP \[bu] 2
-serve webdav: Fix \f[C]--baseurl\f[R] without leading / (Nick
+serve webdav: Fix \f[V]--baseurl\f[R] without leading / (Nick
 Craig-Wood)
 .IP \[bu] 2
 stats: Fix race between ResetCounters and stopAverageLoop called from
@@ -73620,9 +74219,9 @@ time.AfterFunc (Nick Craig-Wood)
 sync
 .RS 2
 .IP \[bu] 2
-\f[C]--fix-case\f[R] flag to rename case insensitive dest (nielash)
+\f[V]--fix-case\f[R] flag to rename case insensitive dest (nielash)
 .IP \[bu] 2
-Use operations.DirMove instead of sync.MoveDir for \f[C]--fix-case\f[R]
+Use operations.DirMove instead of sync.MoveDir for \f[V]--fix-case\f[R]
 (nielash)
 .RE
 .IP \[bu] 2
@@ -73633,7 +74232,7 @@ rather than having 2 separate libraries (Anagh Kumar Baranwal)
 Mount
 .RS 2
 .IP \[bu] 2
-Fix macOS not noticing errors with \f[C]--daemon\f[R] (Nick Craig-Wood)
+Fix macOS not noticing errors with \f[V]--daemon\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Notice daemon dying much quicker (Nick Craig-Wood)
 .RE
@@ -73650,7 +74249,7 @@ Bisync
 Copies and deletes are now handled in one operation instead of two
 (nielash)
 .IP \[bu] 2
-\f[C]--track-renames\f[R] and \f[C]--backup-dir\f[R] are now supported
+\f[V]--track-renames\f[R] and \f[V]--backup-dir\f[R] are now supported
 (nielash)
 .IP \[bu] 2
 Final listings are now generated from sync results, to avoid needing to
@@ -73666,24 +74265,24 @@ next time.
 (nielash)
 .IP \[bu] 2
 A few basic terminal colors are now supported, controllable with
-\f[C]--color\f[R] (https://rclone.org/docs/#color-when)
-(\f[C]AUTO\f[R]|\f[C]NEVER\f[R]|\f[C]ALWAYS\f[R]) (nielash)
+\f[V]--color\f[R] (https://rclone.org/docs/#color-when)
+(\f[V]AUTO\f[R]|\f[V]NEVER\f[R]|\f[V]ALWAYS\f[R]) (nielash)
 .IP \[bu] 2
 Initial listing snapshots of Path1 and Path2 are now generated
 concurrently, using the same \[dq]march\[dq] infrastructure as
-\f[C]check\f[R] and \f[C]sync\f[R], for performance improvements and
+\f[V]check\f[R] and \f[V]sync\f[R], for performance improvements and
 less risk of error.
 (nielash)
 .IP \[bu] 2
-\f[C]--resync\f[R] is now much more efficient (especially for users of
-\f[C]--create-empty-src-dirs\f[R]) (nielash)
+\f[V]--resync\f[R] is now much more efficient (especially for users of
+\f[V]--create-empty-src-dirs\f[R]) (nielash)
 .IP \[bu] 2
 Google Docs (and other files of unknown size) are now supported (with
-the same options as in \f[C]sync\f[R]) (nielash)
+the same options as in \f[V]sync\f[R]) (nielash)
 .IP \[bu] 2
 Equality checks before a sync conflict rename now fall back to
-\f[C]cryptcheck\f[R] (when possible) or \f[C]--download\f[R], (nielash)
-instead of of \f[C]--size-only\f[R], when \f[C]check\f[R] is not
+\f[V]cryptcheck\f[R] (when possible) or \f[V]--download\f[R], (nielash)
+instead of of \f[V]--size-only\f[R], when \f[V]check\f[R] is not
 available.
 .IP \[bu] 2
 Bisync now fully supports comparing based on any combination of size,
@@ -73692,30 +74291,31 @@ modtime support.
 (nielash)
 .IP \[bu] 2
 Bisync now supports a \[dq]Graceful Shutdown\[dq] mode to cleanly cancel
-a run early without requiring \f[C]--resync\f[R].
+a run early without requiring \f[V]--resync\f[R].
 (nielash)
 .IP \[bu] 2
-New \f[C]--recover\f[R] flag allows robust recovery in the event of
-interruptions, without requiring \f[C]--resync\f[R].
+New \f[V]--recover\f[R] flag allows robust recovery in the event of
+interruptions, without requiring \f[V]--resync\f[R].
 (nielash)
 .IP \[bu] 2
-A new \f[C]--max-lock\f[R] setting allows lock files to automatically
+A new \f[V]--max-lock\f[R] setting allows lock files to automatically
 renew and expire, for better automatic recovery when a run is
 interrupted.
 (nielash)
 .IP \[bu] 2
 Bisync now supports auto-resolving sync conflicts and customizing rename
-behavior with new \f[C]--conflict-resolve\f[R],
-\f[C]--conflict-loser\f[R], and \f[C]--conflict-suffix\f[R] flags.
+behavior with new \f[V]--conflict-resolve\f[R],
+\f[V]--conflict-loser\f[R], and \f[V]--conflict-suffix\f[R] flags.
 (nielash)
 .IP \[bu] 2
-A new \f[C]--resync-mode\f[R] flag allows more control over which
-version of a file gets kept during a \f[C]--resync\f[R].
+A new \f[V]--resync-mode\f[R] flag allows more control over which
+version of a file gets kept during a \f[V]--resync\f[R].
 (nielash)
 .IP \[bu] 2
 Bisync now supports
-\f[C]--retries\f[R] (https://rclone.org/docs/#retries-int) and
-\f[C]--retries-sleep\f[R] (when \f[C]--resilient\f[R] is set.) (nielash)
+\f[V]--retries\f[R] (https://rclone.org/docs/#retries-int) and
+\f[V]--retries-sleep\f[R] (when \f[V]--resilient\f[R] is set.)
+(nielash)
 .IP \[bu] 2
 Clarify file operation directions in dry-run logs (Kyle Reynolds)
 .RE
@@ -73763,13 +74363,13 @@ Add missing error check spotted by linter (Nick Craig-Wood)
 Azure Blob
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--azureblob-delete-snapshots\f[R] (Nick Craig-Wood)
+Implement \f[V]--azureblob-delete-snapshots\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 B2
 .RS 2
 .IP \[bu] 2
-Clarify exactly what \f[C]--b2-download-auth-duration\f[R] does in the
+Clarify exactly what \f[V]--b2-download-auth-duration\f[R] does in the
 docs (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -73870,7 +74470,7 @@ Fix moving file/folder within the same parent dir (nielash)
 Oracle Object Storage
 .RS 2
 .IP \[bu] 2
-Support \f[C]backend restore\f[R] command (Nikhil Ahuja)
+Support \f[V]backend restore\f[R] command (Nikhil Ahuja)
 .IP \[bu] 2
 Support workload identity authentication for OKE (Anders Swanson)
 .RE
@@ -73884,7 +74484,7 @@ Fix encoding of Root method (Nick Craig-Wood)
 Quatrix
 .RS 2
 .IP \[bu] 2
-Fix \f[C]Content-Range\f[R] header (Volodymyr)
+Fix \f[V]Content-Range\f[R] header (Volodymyr)
 .IP \[bu] 2
 Add option to skip project folders (Oksana Zhykina)
 .IP \[bu] 2
@@ -73895,11 +74495,11 @@ Craig-Wood)
 S3
 .RS 2
 .IP \[bu] 2
-Add \f[C]--s3-version-deleted\f[R] to show delete markers in listings
+Add \f[V]--s3-version-deleted\f[R] to show delete markers in listings
 when using versions.
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add IPv6 support with option \f[C]--s3-use-dual-stack\f[R] (Anthony
+Add IPv6 support with option \f[V]--s3-use-dual-stack\f[R] (Anthony
 Metzidis)
 .IP \[bu] 2
 Copy parts in parallel when doing chunked server side copy (Nick
@@ -73915,7 +74515,7 @@ Craig-Wood)
 Seafile
 .RS 2
 .IP \[bu] 2
-Fix download/upload error when \f[C]FILE_SERVER_ROOT\f[R] is relative
+Fix download/upload error when \f[V]FILE_SERVER_ROOT\f[R] is relative
 (DanielEgbers)
 .IP \[bu] 2
 Fix Root to return correct directory when pointing to a file (Nick
@@ -73953,9 +74553,9 @@ WebDAV
 .IP \[bu] 2
 Reduce priority of chunks upload log (Gabriel Ramos)
 .IP \[bu] 2
-owncloud: Add config \f[C]owncloud_exclude_shares\f[R] which allows to
+owncloud: Add config \f[V]owncloud_exclude_shares\f[R] which allows to
 exclude shared files and folders when listing remote resources (Thomas
-M\[:u]ller)
+Müller)
 .RE
 .SS v1.65.2 - 2024-01-24
 .PP
@@ -73973,7 +74573,7 @@ Budhraja)
 VFS
 .RS 2
 .IP \[bu] 2
-Fix stale data when using \f[C]--vfs-cache-mode\f[R] full (Nick
+Fix stale data when using \f[V]--vfs-cache-mode\f[R] full (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -74007,13 +74607,13 @@ accounting: fix stats to show server side transfers (Nick Craig-Wood)
 doc fixes (albertony, ben-ba, Eli Orzitzer, emyarod, keongalvin,
 rarspace01)
 .IP \[bu] 2
-nfsmount: Compile for all unix oses, add \f[C]--sudo\f[R] and fix
+nfsmount: Compile for all unix oses, add \f[V]--sudo\f[R] and fix
 error/option handling (Nick Craig-Wood)
 .IP \[bu] 2
 operations: Fix files moved by rclone move not being counted as
 transfers (Nick Craig-Wood)
 .IP \[bu] 2
-oauthutil: Avoid panic when \f[C]*token\f[R] and \f[C]*ts.token\f[R] are
+oauthutil: Avoid panic when \f[V]*token\f[R] and \f[V]*ts.token\f[R] are
 the same (rkonfj)
 .IP \[bu] 2
 serve s3: Fix listing oddities (Nick Craig-Wood)
@@ -74022,7 +74622,7 @@ serve s3: Fix listing oddities (Nick Craig-Wood)
 VFS
 .RS 2
 .IP \[bu] 2
-Note that \f[C]--vfs-refresh\f[R] runs in the background (Nick
+Note that \f[V]--vfs-refresh\f[R] runs in the background (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -74079,7 +74679,7 @@ Fix invalid memory address error when MaxAge == 0 (nielash)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Fix error listing: unknown object type \f[C]<nil>\f[R] (Nick Craig-Wood)
+Fix error listing: unknown object type \f[V]<nil>\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix \[dq]unauthenticated: Unauthenticated\[dq] errors when uploading
 (Nick Craig-Wood)
@@ -74134,13 +74734,13 @@ Linkbox (viktor, Nick Craig-Wood)
 New commands
 .RS 2
 .IP \[bu] 2
-\f[C]serve s3\f[R]: Let rclone act as an S3 compatible server (Mikubill,
+\f[V]serve s3\f[R]: Let rclone act as an S3 compatible server (Mikubill,
 Artur Neumann, Saw-jan, Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]nfsmount\f[R]: mount command to provide mount mechanism on macOS
+\f[V]nfsmount\f[R]: mount command to provide mount mechanism on macOS
 without FUSE (Saleh Dindar)
 .IP \[bu] 2
-\f[C]serve nfs\f[R]: to serve a remote for use by \f[C]nfsmount\f[R]
+\f[V]serve nfs\f[R]: to serve a remote for use by \f[V]nfsmount\f[R]
 (Saleh Dindar)
 .RE
 .IP \[bu] 2
@@ -74158,37 +74758,37 @@ Refactor version info and icon resource handling on windows (albertony)
 .RE
 .IP \[bu] 2
 doc updates (albertony, alfish2000, asdffdsazqqq, Dimitri Papadopoulos,
-Herby Gillot, Joda St\[:o]\[ss]er, Manoj Ghosh, Nick Craig-Wood)
+Herby Gillot, Joda Stößer, Manoj Ghosh, Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--metadata-mapper\f[R] to transform metatadata with a
+Implement \f[V]--metadata-mapper\f[R] to transform metatadata with a
 user supplied program (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]ChunkWriterDoesntSeek\f[R] feature flag and set it for b2 (Nick
+Add \f[V]ChunkWriterDoesntSeek\f[R] feature flag and set it for b2 (Nick
 Craig-Wood)
 .IP \[bu] 2
 lib/http: Export basic go string functions for use in
-\f[C]--template\f[R] (Gabriel Espinoza)
+\f[V]--template\f[R] (Gabriel Espinoza)
 .IP \[bu] 2
-makefile: Use POSIX compatible install arguments (Mina Gali\['c])
+makefile: Use POSIX compatible install arguments (Mina Galić)
 .IP \[bu] 2
 operations
 .RS 2
 .IP \[bu] 2
 Use less memory when doing multithread uploads (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--partial-suffix\f[R] to control extension of temporary
+Implement \f[V]--partial-suffix\f[R] to control extension of temporary
 file names (Volodymyr)
 .RE
 .IP \[bu] 2
 rc
 .RS 2
 .IP \[bu] 2
-Add \f[C]operations/check\f[R] to the rc API (Nick Craig-Wood)
+Add \f[V]operations/check\f[R] to the rc API (Nick Craig-Wood)
 .IP \[bu] 2
 Always report an error as JSON (Nick Craig-Wood)
 .IP \[bu] 2
-Set \f[C]Last-Modified\f[R] header for files served by
-\f[C]--rc-serve\f[R] (Nikita Shoshin)
+Set \f[V]Last-Modified\f[R] header for files served by
+\f[V]--rc-serve\f[R] (Nikita Shoshin)
 .RE
 .IP \[bu] 2
 size: Dont show duplicate object count when less than 1k (albertony)
@@ -74197,10 +74797,9 @@ size: Dont show duplicate object count when less than 1k (albertony)
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-fshttp: Fix \f[C]--contimeout\f[R] being ignored
-(\[u4F60]\[u77E5]\[u9053]\[u672A]\[u6765]\[u5417])
+fshttp: Fix \f[V]--contimeout\f[R] being ignored (你知道未来吗)
 .IP \[bu] 2
-march: Fix excessive parallelism when using \f[C]--no-traverse\f[R]
+march: Fix excessive parallelism when using \f[V]--no-traverse\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
 ncdu: Fix crash when re-entering changed directory after rescan (Nick
@@ -74213,7 +74812,7 @@ Fix overwrite of destination when multi-thread transfer fails (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix invalid UTF-8 when truncating file names when not using
-\f[C]--inplace\f[R] (Nick Craig-Wood)
+\f[V]--inplace\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 serve dnla: Fix crash on graceful exit (wuxingzhong)
@@ -74229,7 +74828,7 @@ Disable mount for freebsd and alias cmount as mount on that platform
 VFS
 .RS 2
 .IP \[bu] 2
-Add \f[C]--vfs-refresh\f[R] flag to read all the directories on start
+Add \f[V]--vfs-refresh\f[R] flag to read all the directories on start
 (Beyond Meat)
 .IP \[bu] 2
 Implement Name() method in WriteFileHandle and ReadFileHandle (Saleh
@@ -74259,7 +74858,7 @@ B2
 Implement \[dq]rclone backend lifecycle\[dq] to read and set bucket
 lifecycles (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--b2-lifecycle\f[R] to control lifecycle when creating
+Implement \f[V]--b2-lifecycle\f[R] to control lifecycle when creating
 buckets (Nick Craig-Wood)
 .IP \[bu] 2
 Fix listing all buckets when not needed (Nick Craig-Wood)
@@ -74268,7 +74867,7 @@ Fix multi-thread upload with copyto going to wrong name (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix server side chunked copy when file size was exactly
-\f[C]--b2-copy-cutoff\f[R] (Nick Craig-Wood)
+\f[V]--b2-copy-cutoff\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix streaming chunked files an exact multiple of chunk size (Nick
 Craig-Wood)
@@ -74292,10 +74891,10 @@ Add read/write metadata support (Nick Craig-Wood)
 .IP \[bu] 2
 Add support for SHA-1 and SHA-256 checksums (rinsuki)
 .IP \[bu] 2
-Add \f[C]--drive-show-all-gdocs\f[R] to allow unexportable gdocs to be
+Add \f[V]--drive-show-all-gdocs\f[R] to allow unexportable gdocs to be
 server side copied (Nick Craig-Wood)
 .IP \[bu] 2
-Add a note that \f[C]--drive-scope\f[R] accepts comma-separated list of
+Add a note that \f[V]--drive-scope\f[R] accepts comma-separated list of
 scopes (Keigo Imai)
 .IP \[bu] 2
 Fix error updating created time metadata on existing object (Nick
@@ -74339,7 +74938,7 @@ HTTP
 Implement set backend command to update running backend (Nick
 Craig-Wood)
 .IP \[bu] 2
-Enable methods used with WebDAV (Alen \[vS]iljak)
+Enable methods used with WebDAV (Alen Šiljak)
 .RE
 .IP \[bu] 2
 Jottacloud
@@ -74351,11 +74950,11 @@ Add support for reading and writing metadata (albertony)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Implement ListR method which gives \f[C]--fast-list\f[R] support (Nick
+Implement ListR method which gives \f[V]--fast-list\f[R] support (Nick
 Craig-Wood)
 .RS 2
 .IP \[bu] 2
-This must be enabled with the \f[C]--onedrive-delta\f[R] flag
+This must be enabled with the \f[V]--onedrive-delta\f[R] flag
 .RE
 .RE
 .IP \[bu] 2
@@ -74380,7 +74979,7 @@ Fix no error being returned when creating a bucket we don\[aq]t own
 Emit a debug message if anonymous credentials are in use (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-disable-multipart-uploads\f[R] flag (Nick Craig-Wood)
+Add \f[V]--s3-disable-multipart-uploads\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 Detect looping when using gcs and versions (Nick Craig-Wood)
 .RE
@@ -74388,15 +74987,15 @@ Detect looping when using gcs and versions (Nick Craig-Wood)
 SFTP
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--sftp-copy-is-hardlink\f[R] to server side copy as
+Implement \f[V]--sftp-copy-is-hardlink\f[R] to server side copy as
 hardlink (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Smb
 .RS 2
 .IP \[bu] 2
-Fix incorrect \f[C]about\f[R] size by switching to
-\f[C]github.com/cloudsoda/go-smb2\f[R] fork (Nick Craig-Wood)
+Fix incorrect \f[V]about\f[R] size by switching to
+\f[V]github.com/cloudsoda/go-smb2\f[R] fork (Nick Craig-Wood)
 .IP \[bu] 2
 Fix modtime of multithread uploads by setting PartialUploads (Nick
 Craig-Wood)
@@ -74405,7 +75004,7 @@ Craig-Wood)
 WebDAV
 .RS 2
 .IP \[bu] 2
-Added an rclone vendor to work with \f[C]rclone serve webdav\f[R]
+Added an rclone vendor to work with \f[V]rclone serve webdav\f[R]
 (Adithya Kumar)
 .RE
 .SS v1.64.2 - 2023-10-19
@@ -74427,7 +75026,7 @@ See commits (https://github.com/rclone/rclone/compare/v1.64.0...v1.64.1)
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-cmd: Make \f[C]--progress\f[R] output logs in the same format as without
+cmd: Make \f[V]--progress\f[R] output logs in the same format as without
 (Nick Craig-Wood)
 .IP \[bu] 2
 docs fixes (Dimitri Papadopoulos Orfanos, Herby Gillot, Manoj Ghosh,
@@ -74487,14 +75086,14 @@ Fix server side copies greater than 4GB (Nick Craig-Wood)
 .IP \[bu] 2
 Fix chunked streaming uploads (Nick Craig-Wood)
 .IP \[bu] 2
-Reduce default \f[C]--b2-upload-concurrency\f[R] to 4 to reduce memory
+Reduce default \f[V]--b2-upload-concurrency\f[R] to 4 to reduce memory
 usage (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Onedrive
 .RS 2
 .IP \[bu] 2
-Fix the configurator to allow \f[C]/teams/ID\f[R] in the config (Nick
+Fix the configurator to allow \f[V]/teams/ID\f[R] in the config (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -74557,8 +75156,8 @@ Mackenzie-Owen)
 Multi-thread transfers are now available when transferring to:
 .RS 2
 .IP \[bu] 2
-\f[C]local\f[R], \f[C]s3\f[R], \f[C]azureblob\f[R], \f[C]b2\f[R],
-\f[C]oracleobjectstorage\f[R] and \f[C]smb\f[R]
+\f[V]local\f[R], \f[V]s3\f[R], \f[V]azureblob\f[R], \f[V]b2\f[R],
+\f[V]oracleobjectstorage\f[R] and \f[V]smb\f[R]
 .RE
 .IP \[bu] 2
 This greatly improves transfer speed between two network sources.
@@ -74574,7 +75173,7 @@ for more info
 New commands
 .RS 2
 .IP \[bu] 2
-\f[C]rclone config redacted\f[R] support mechanism for showing redacted
+\f[V]rclone config redacted\f[R] support mechanism for showing redacted
 config (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -74591,82 +75190,81 @@ Craig-Wood)
 bisync
 .RS 2
 .IP \[bu] 2
-Add new \f[C]--ignore-listing-checksum\f[R] flag to distinguish from
-\f[C]--ignore-checksum\f[R] (nielash)
+Add new \f[V]--ignore-listing-checksum\f[R] flag to distinguish from
+\f[V]--ignore-checksum\f[R] (nielash)
 .IP \[bu] 2
-Add experimental \f[C]--resilient\f[R] mode to allow recovery from
+Add experimental \f[V]--resilient\f[R] mode to allow recovery from
 self-correctable errors (nielash)
 .IP \[bu] 2
-Add support for \f[C]--create-empty-src-dirs\f[R] (nielash)
+Add support for \f[V]--create-empty-src-dirs\f[R] (nielash)
 .IP \[bu] 2
 Dry runs no longer commit filter changes (nielash)
 .IP \[bu] 2
-Enforce \f[C]--check-access\f[R] during \f[C]--resync\f[R] (nielash)
+Enforce \f[V]--check-access\f[R] during \f[V]--resync\f[R] (nielash)
 .IP \[bu] 2
 Apply filters correctly during deletes (nielash)
 .IP \[bu] 2
 Equality check before renaming (leave identical files alone) (nielash)
 .IP \[bu] 2
-Fix \f[C]dryRun\f[R] rc parameter being ignored (nielash)
+Fix \f[V]dryRun\f[R] rc parameter being ignored (nielash)
 .RE
 .IP \[bu] 2
 build
 .RS 2
 .IP \[bu] 2
-Update to \f[C]go1.21\f[R] and make \f[C]go1.19\f[R] the minimum
+Update to \f[V]go1.21\f[R] and make \f[V]go1.19\f[R] the minimum
 required version (Anagh Kumar Baranwal, Nick Craig-Wood)
 .IP \[bu] 2
 Update dependencies (Nick Craig-Wood)
 .IP \[bu] 2
 Add snap installation (hideo aoyama)
 .IP \[bu] 2
-Change Winget Releaser job to \f[C]ubuntu-latest\f[R] (sitiom)
+Change Winget Releaser job to \f[V]ubuntu-latest\f[R] (sitiom)
 .RE
 .IP \[bu] 2
 cmd: Refactor and use sysdnotify in more commands (eNV25)
 .IP \[bu] 2
-config: Add \f[C]--multi-thread-chunk-size\f[R] flag (Vitor Gomes)
+config: Add \f[V]--multi-thread-chunk-size\f[R] flag (Vitor Gomes)
 .IP \[bu] 2
-doc updates (antoinetran, Benjamin, Bj\[/o]rn Smith, Dean Attali,
+doc updates (antoinetran, Benjamin, Bjørn Smith, Dean Attali,
 gabriel-suela, James Braza, Justin Hellings, kapitainsky, Mahad,
-Masamune3210, Nick Craig-Wood, Nihaal Sangha, Niklas Hamb\[:u]chen,
-Raymond Berger, r-ricci, Sawada Tsunayoshi, Tiago Boeing, Vladislav
-Vorobev)
+Masamune3210, Nick Craig-Wood, Nihaal Sangha, Niklas Hambüchen, Raymond
+Berger, r-ricci, Sawada Tsunayoshi, Tiago Boeing, Vladislav Vorobev)
 .IP \[bu] 2
 fs
 .RS 2
 .IP \[bu] 2
 Use atomic types everywhere (Roberto Ricci)
 .IP \[bu] 2
-When \f[C]--max-transfer\f[R] limit is reached exit with code (10)
+When \f[V]--max-transfer\f[R] limit is reached exit with code (10)
 (kapitainsky)
 .IP \[bu] 2
 Add rclone completion powershell - basic implementation only (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
-http servers: Allow CORS to be set with \f[C]--allow-origin\f[R] flag
+http servers: Allow CORS to be set with \f[V]--allow-origin\f[R] flag
 (yuudi)
 .IP \[bu] 2
-lib/rest: Remove unnecessary \f[C]nil\f[R] check (Eng Zer Jun)
+lib/rest: Remove unnecessary \f[V]nil\f[R] check (Eng Zer Jun)
 .IP \[bu] 2
 ncdu: Add keybinding to rescan filesystem (eNV25)
 .IP \[bu] 2
 rc
 .RS 2
 .IP \[bu] 2
-Add \f[C]executeId\f[R] to job listings (yuudi)
+Add \f[V]executeId\f[R] to job listings (yuudi)
 .IP \[bu] 2
-Add \f[C]core/du\f[R] to measure local disk usage (Nick Craig-Wood)
+Add \f[V]core/du\f[R] to measure local disk usage (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]operations/settier\f[R] to API (Drew Stinnett)
+Add \f[V]operations/settier\f[R] to API (Drew Stinnett)
 .RE
 .IP \[bu] 2
-rclone test info: Add \f[C]--check-base32768\f[R] flag to check can
+rclone test info: Add \f[V]--check-base32768\f[R] flag to check can
 store all base32768 characters (Nick Craig-Wood)
 .IP \[bu] 2
 rmdirs: Remove directories concurrently controlled by
-\f[C]--checkers\f[R] (Nick Craig-Wood)
+\f[V]--checkers\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -74675,10 +75273,10 @@ Bug Fixes
 accounting: Don\[aq]t stop calculating average transfer speed until the
 operation is complete (Jacob Hands)
 .IP \[bu] 2
-fs: Fix \f[C]transferTime\f[R] not being set in JSON logs (Jacob Hands)
+fs: Fix \f[V]transferTime\f[R] not being set in JSON logs (Jacob Hands)
 .IP \[bu] 2
-fshttp: Fix \f[C]--bind 0.0.0.0\f[R] allowing IPv6 and
-\f[C]--bind ::0\f[R] allowing IPv4 (Nick Craig-Wood)
+fshttp: Fix \f[V]--bind 0.0.0.0\f[R] allowing IPv6 and
+\f[V]--bind ::0\f[R] allowing IPv4 (Nick Craig-Wood)
 .IP \[bu] 2
 operations: Fix overlapping check on case insensitive file systems (Nick
 Craig-Wood)
@@ -74689,14 +75287,14 @@ Craig-Wood)
 serve ftp: Fix race condition when using the auth proxy (Nick
 Craig-Wood)
 .IP \[bu] 2
-serve sftp: Fix hash calculations with \f[C]--vfs-cache-mode full\f[R]
+serve sftp: Fix hash calculations with \f[V]--vfs-cache-mode full\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
 serve webdav: Fix error: Expecting fs.Object or fs.Directory, got
-\f[C]nil\f[R] (Nick Craig-Wood)
+\f[V]nil\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-sync: Fix lockup with \f[C]--cutoff-mode=soft\f[R] and
-\f[C]--max-duration\f[R] (Nick Craig-Wood)
+sync: Fix lockup with \f[V]--cutoff-mode=soft\f[R] and
+\f[V]--max-duration\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Mount
@@ -74708,7 +75306,7 @@ fix: Mount parsing for linux (Anagh Kumar Baranwal)
 VFS
 .RS 2
 .IP \[bu] 2
-Add \f[C]--vfs-cache-min-free-space\f[R] to control minimum free space
+Add \f[V]--vfs-cache-min-free-space\f[R] to control minimum free space
 on the disk containing the cache (Nick Craig-Wood)
 .IP \[bu] 2
 Added cache cleaner for directories to reduce memory usage (Anagh Kumar
@@ -74731,7 +75329,7 @@ Rmdir return an error if the path is not a dir (zjx20)
 Azure Blob
 .RS 2
 .IP \[bu] 2
-Implement \f[C]OpenChunkWriter\f[R] and multi-thread uploads (Nick
+Implement \f[V]OpenChunkWriter\f[R] and multi-thread uploads (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix creation of directory markers (Nick Craig-Wood)
@@ -74742,7 +75340,7 @@ Fix purging with directory markers (Nick Craig-Wood)
 B2
 .RS 2
 .IP \[bu] 2
-Implement \f[C]OpenChunkWriter\f[R] and multi-thread uploads (Nick
+Implement \f[V]OpenChunkWriter\f[R] and multi-thread uploads (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix rclone link when object path contains special characters (Alishan
@@ -74754,7 +75352,7 @@ Box
 .IP \[bu] 2
 Add polling support (David Sze)
 .IP \[bu] 2
-Add \f[C]--box-impersonate\f[R] to impersonate a user ID (Nick
+Add \f[V]--box-impersonate\f[R] to impersonate a user ID (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix unhelpful decoding of error messages into decimal numbers (Nick
@@ -74777,14 +75375,14 @@ Fix ChangeNotify (Nick Craig-Wood)
 Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--drive-fast-list-bug-fix\f[R] to control ListR bug workaround
+Add \f[V]--drive-fast-list-bug-fix\f[R] to control ListR bug workaround
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Fichier
 .RS 2
 .IP \[bu] 2
-Implement \f[C]DirMove\f[R] (Nick Craig-Wood)
+Implement \f[V]DirMove\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix error code parsing (alexia)
 .RE
@@ -74827,26 +75425,26 @@ Oracleobjectstorage
 .IP \[bu] 2
 Use rclone\[aq]s rate limiter in multipart transfers (Manoj Ghosh)
 .IP \[bu] 2
-Implement \f[C]OpenChunkWriter\f[R] and multi-thread uploads (Manoj
+Implement \f[V]OpenChunkWriter\f[R] and multi-thread uploads (Manoj
 Ghosh)
 .RE
 .IP \[bu] 2
 S3
 .RS 2
 .IP \[bu] 2
-Refactor multipart upload to use \f[C]OpenChunkWriter\f[R] and
-\f[C]ChunkWriter\f[R] (Vitor Gomes)
+Refactor multipart upload to use \f[V]OpenChunkWriter\f[R] and
+\f[V]ChunkWriter\f[R] (Vitor Gomes)
 .IP \[bu] 2
-Factor generic multipart upload into \f[C]lib/multipart\f[R] (Nick
+Factor generic multipart upload into \f[V]lib/multipart\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix purging of root directory with \f[C]--s3-directory-markers\f[R]
+Fix purging of root directory with \f[V]--s3-directory-markers\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]rclone backend set\f[R] command to update the running config
+Add \f[V]rclone backend set\f[R] command to update the running config
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]rclone backend restore-status\f[R] command (Nick Craig-Wood)
+Add \f[V]rclone backend restore-status\f[R] command (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 SFTP
@@ -74855,14 +75453,14 @@ SFTP
 Stop uploads re-using the same ssh connection to improve performance
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--sftp-ssh\f[R] to specify an external ssh binary to use (Nick
+Add \f[V]--sftp-ssh\f[R] to specify an external ssh binary to use (Nick
 Craig-Wood)
 .IP \[bu] 2
 Add socks_proxy support for SOCKS5 proxies (Zach)
 .IP \[bu] 2
-Support dynamic \f[C]--sftp-path-override\f[R] (nielash)
+Support dynamic \f[V]--sftp-path-override\f[R] (nielash)
 .IP \[bu] 2
-Fix spurious warning when using \f[C]--sftp-ssh\f[R] (Nick Craig-Wood)
+Fix spurious warning when using \f[V]--sftp-ssh\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Smb
@@ -74880,14 +75478,14 @@ Performance improvement for large file uploads (Kaloyan Raev)
 Swift
 .RS 2
 .IP \[bu] 2
-Fix HEADing 0-length objects when \f[C]--swift-no-large-objects\f[R] set
+Fix HEADing 0-length objects when \f[V]--swift-no-large-objects\f[R] set
 (Julian Lepinski)
 .RE
 .IP \[bu] 2
 Union
 .RS 2
 .IP \[bu] 2
-Add \f[C]:writback\f[R] to act as a simple cache (Nick Craig-Wood)
+Add \f[V]:writback\f[R] to act as a simple cache (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 WebDAV
@@ -74912,15 +75510,15 @@ Bug Fixes
 build: Fix macos builds for versions < 12 (Anagh Kumar Baranwal)
 .IP \[bu] 2
 dirtree: Fix performance with large directories of directories and
-\f[C]--fast-list\f[R] (Nick Craig-Wood)
+\f[V]--fast-list\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 operations
 .RS 2
 .IP \[bu] 2
-Fix deadlock when using \f[C]lsd\f[R]/\f[C]ls\f[R] with
-\f[C]--progress\f[R] (Nick Craig-Wood)
+Fix deadlock when using \f[V]lsd\f[R]/\f[V]ls\f[R] with
+\f[V]--progress\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C].rclonelink\f[R] files not being converted back to symlinks
+Fix \f[V].rclonelink\f[R] files not being converted back to symlinks
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -74984,8 +75582,8 @@ Fastmail (https://rclone.org/webdav/#fastmail-files) (Arnavion)
 Major changes
 .RS 2
 .IP \[bu] 2
-Files will be copied to a temporary name ending in \f[C].partial\f[R]
-when copying to \f[C]local\f[R],\f[C]ftp\f[R],\f[C]sftp\f[R] then
+Files will be copied to a temporary name ending in \f[V].partial\f[R]
+when copying to \f[V]local\f[R],\f[V]ftp\f[R],\f[V]sftp\f[R] then
 renamed at the end of the transfer.
 (Janne Hellsten, Nick Craig-Wood)
 .RS 2
@@ -74997,12 +75595,12 @@ It can be disabled with the --inplace (https://rclone.org/docs/#inplace)
 flag.
 .IP \[bu] 2
 This behaviour will also happen if the backend is wrapped, for example
-\f[C]sftp\f[R] wrapped with \f[C]crypt\f[R].
+\f[V]sftp\f[R] wrapped with \f[V]crypt\f[R].
 .RE
 .IP \[bu] 2
 The s3 (https://rclone.org/s3/#s3-directory-markers), azureblob and gcs
 backends now support directory markers so empty directories are
-supported (J\[u0101]nis Bebr\[u012B]tis, Nick Craig-Wood)
+supported (Jānis Bebrītis, Nick Craig-Wood)
 .IP \[bu] 2
 The --default-time (https://rclone.org/docs/#default-time-time) flag now
 controls the unknown modification time of files/dirs (Nick Craig-Wood)
@@ -75011,7 +75609,7 @@ controls the unknown modification time of files/dirs (Nick Craig-Wood)
 If a file or directory does not have a modification time rclone can read
 then rclone will display this fixed time instead.
 .IP \[bu] 2
-For the old behaviour use \f[C]--default-time 0s\f[R] which will set
+For the old behaviour use \f[V]--default-time 0s\f[R] which will set
 this time to the time rclone started up.
 .RE
 .RE
@@ -75027,7 +75625,7 @@ Modernise linters in use and fixup all affected code (albertony)
 Push docker beta to GHCR (GitHub container registry) (Richard Tweed)
 .RE
 .IP \[bu] 2
-cat: Add \f[C]--separator\f[R] option to cat command (Loren Gordon)
+cat: Add \f[V]--separator\f[R] option to cat command (Loren Gordon)
 .IP \[bu] 2
 config
 .RS 2
@@ -75036,7 +75634,7 @@ Do not remove/overwrite other files during config file save (albertony)
 .IP \[bu] 2
 Do not overwrite config file symbolic link (albertony)
 .IP \[bu] 2
-Stop \f[C]config create\f[R] making invalid config files (Nick
+Stop \f[V]config create\f[R] making invalid config files (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -75048,41 +75646,41 @@ Rintze Zelle, Stanislav Gromov, Tareq Sharafy, URenko, yuudi, Zach Kipp)
 fs
 .RS 2
 .IP \[bu] 2
-Add \f[C]size\f[R] to JSON logs when moving or copying an object (Nick
+Add \f[V]size\f[R] to JSON logs when moving or copying an object (Nick
 Craig-Wood)
 .IP \[bu] 2
-Allow boolean features to be enabled with \f[C]--disable !Feature\f[R]
+Allow boolean features to be enabled with \f[V]--disable !Feature\f[R]
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-genautocomplete: Rename to \f[C]completion\f[R] with alias to the old
+genautocomplete: Rename to \f[V]completion\f[R] with alias to the old
 name (Nick Craig-Wood)
 .IP \[bu] 2
-librclone: Added example on using \f[C]librclone\f[R] with Go (alankrit)
+librclone: Added example on using \f[V]librclone\f[R] with Go (alankrit)
 .IP \[bu] 2
-lsjson: Make \f[C]--stat\f[R] more efficient (Nick Craig-Wood)
+lsjson: Make \f[V]--stat\f[R] more efficient (Nick Craig-Wood)
 .IP \[bu] 2
 operations
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--multi-thread-write-buffer-size\f[R] for speed
+Implement \f[V]--multi-thread-write-buffer-size\f[R] for speed
 improvements on downloads (Paulo Schreiner)
 .IP \[bu] 2
-Reopen downloads on error when using \f[C]check --download\f[R] and
-\f[C]cat\f[R] (Nick Craig-Wood)
+Reopen downloads on error when using \f[V]check --download\f[R] and
+\f[V]cat\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-rc: \f[C]config/listremotes\f[R] includes remotes defined with
+rc: \f[V]config/listremotes\f[R] includes remotes defined with
 environment variables (kapitainsky)
 .IP \[bu] 2
-selfupdate: Obey \f[C]--no-check-certificate\f[R] flag (Nick Craig-Wood)
+selfupdate: Obey \f[V]--no-check-certificate\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 serve restic: Trigger systemd notify (Shyim)
 .IP \[bu] 2
 serve webdav: Implement owncloud checksum and modtime extensions
 (WeidiDeng)
 .IP \[bu] 2
-sync: \f[C]--suffix-keep-extension\f[R] preserve 2 part extensions like
+sync: \f[V]--suffix-keep-extension\f[R] preserve 2 part extensions like
 \&.tar.gz (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -75092,23 +75690,23 @@ Bug Fixes
 accounting
 .RS 2
 .IP \[bu] 2
-Fix Prometheus metrics to be the same as \f[C]core/stats\f[R] (Nick
+Fix Prometheus metrics to be the same as \f[V]core/stats\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 Bwlimit signal handler should always start (Sam Lai)
 .RE
 .IP \[bu] 2
-bisync: Fix \f[C]maxDelete\f[R] parameter being ignored via the rc (Nick
+bisync: Fix \f[V]maxDelete\f[R] parameter being ignored via the rc (Nick
 Craig-Wood)
 .IP \[bu] 2
 cmd/ncdu: Fix screen corruption when logging (eNV25)
 .IP \[bu] 2
-filter: Fix deadlock with errors on \f[C]--files-from\f[R] (douchen)
+filter: Fix deadlock with errors on \f[V]--files-from\f[R] (douchen)
 .IP \[bu] 2
 fs
 .RS 2
 .IP \[bu] 2
-Fix interaction between \f[C]--progress\f[R] and \f[C]--interactive\f[R]
+Fix interaction between \f[V]--progress\f[R] and \f[V]--interactive\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
 Fix infinite recursive call in pacer ModifyCalculator (fixes issue
@@ -75123,12 +75721,12 @@ lib/rest: Fix problems re-using HTTP connections (Nick Craig-Wood)
 rc
 .RS 2
 .IP \[bu] 2
-Fix \f[C]operations/stat\f[R] with trailing \f[C]/\f[R] (Nick
+Fix \f[V]operations/stat\f[R] with trailing \f[V]/\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix missing \f[C]--rc\f[R] flags (Nick Craig-Wood)
+Fix missing \f[V]--rc\f[R] flags (Nick Craig-Wood)
 .IP \[bu] 2
-Fix output of Time values in \f[C]options/get\f[R] (Nick Craig-Wood)
+Fix output of Time values in \f[V]options/get\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 serve dlna: Fix potential data race (Nick Craig-Wood)
@@ -75139,7 +75737,7 @@ version: Fix reported os/kernel version for windows (albertony)
 Mount
 .RS 2
 .IP \[bu] 2
-Add \f[C]--mount-case-insensitive\f[R] to force the mount to be case
+Add \f[V]--mount-case-insensitive\f[R] to force the mount to be case
 insensitive (Nick Craig-Wood)
 .IP \[bu] 2
 Removed unnecessary byte slice allocation for reads (Anagh Kumar
@@ -75182,13 +75780,13 @@ Fix backends being Shutdown too early when startup takes a long time
 Local
 .RS 2
 .IP \[bu] 2
-Fix filtering of symlinks with \f[C]-l\f[R]/\f[C]--links\f[R] flag (Nick
+Fix filtering of symlinks with \f[V]-l\f[R]/\f[V]--links\f[R] flag (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix /path/to/file.rclonelink when \f[C]-l\f[R]/\f[C]--links\f[R] is in
+Fix /path/to/file.rclonelink when \f[V]-l\f[R]/\f[V]--links\f[R] is in
 use (Nick Craig-Wood)
 .IP \[bu] 2
-Fix crash with \f[C]--metadata\f[R] on Android (Nick Craig-Wood)
+Fix crash with \f[V]--metadata\f[R] on Android (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Cache
@@ -75201,10 +75799,10 @@ Craig-Wood)
 Crypt
 .RS 2
 .IP \[bu] 2
-Add \f[C]--crypt-suffix\f[R] option to set a custom suffix for encrypted
+Add \f[V]--crypt-suffix\f[R] option to set a custom suffix for encrypted
 files (jladbrook)
 .IP \[bu] 2
-Add \f[C]--crypt-pass-bad-blocks\f[R] to allow corrupted file output
+Add \f[V]--crypt-pass-bad-blocks\f[R] to allow corrupted file output
 (Nick Craig-Wood)
 .IP \[bu] 2
 Fix reading 0 length files (Nick Craig-Wood)
@@ -75213,7 +75811,7 @@ Try not to return \[dq]unexpected EOF\[dq] error (Nick Craig-Wood)
 .IP \[bu] 2
 Reduce allocations (albertony)
 .IP \[bu] 2
-Recommend Dropbox for \f[C]base32768\f[R] encoding (Nick Craig-Wood)
+Recommend Dropbox for \f[V]base32768\f[R] encoding (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Azure Blob
@@ -75240,7 +75838,7 @@ Fix goroutine stack overflow on bad object (Nick Craig-Wood)
 Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--drive-env-auth\f[R] to get IAM credentials from runtime
+Add \f[V]--drive-env-auth\f[R] to get IAM credentials from runtime
 (Peter Brunner)
 .IP \[bu] 2
 Update drive service account guide (Juang, Yi-Lin)
@@ -75255,7 +75853,7 @@ Fix incorrect remote after Update on object (Nick Craig-Wood)
 Dropbox
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--dropbox-pacer-min-sleep\f[R] flag (Nick Craig-Wood)
+Implement \f[V]--dropbox-pacer-min-sleep\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 Fix the dropbox batcher stalling (Misty)
 .RE
@@ -75263,14 +75861,14 @@ Fix the dropbox batcher stalling (Misty)
 Fichier
 .RS 2
 .IP \[bu] 2
-Add \f[C]--ficicher-cdn\f[R] option to use the CDN for download (Nick
+Add \f[V]--ficicher-cdn\f[R] option to use the CDN for download (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
 FTP
 .RS 2
 .IP \[bu] 2
-Lower log message priority when \f[C]SetModTime\f[R] is not supported to
+Lower log message priority when \f[V]SetModTime\f[R] is not supported to
 debug (Tobias Gion)
 .IP \[bu] 2
 Fix \[dq]unsupported LIST line\[dq] errors on startup (Nick Craig-Wood)
@@ -75282,9 +75880,9 @@ Fix \[dq]501 Not a valid pathname.\[dq] errors when creating directories
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Empty directory markers (J\[u0101]nis Bebr\[u012B]tis, Nick Craig-Wood)
+Empty directory markers (Jānis Bebrītis, Nick Craig-Wood)
 .IP \[bu] 2
-Added \f[C]--gcs-user-project\f[R] needed for requester pays
+Added \f[V]--gcs-user-project\f[R] needed for requester pays
 (Christopher Merry)
 .RE
 .IP \[bu] 2
@@ -75292,7 +75890,7 @@ HTTP
 .RS 2
 .IP \[bu] 2
 Add client certificate user auth middleware.
-This can auth \f[C]serve restic\f[R] from the username in the client
+This can auth \f[V]serve restic\f[R] from the username in the client
 cert.
 (Peter Fern)
 .RE
@@ -75307,12 +75905,12 @@ disabled (albertony)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--onedrive-av-override\f[R] flag to download files flagged as
+Add \f[V]--onedrive-av-override\f[R] flag to download files flagged as
 virus (Nick Craig-Wood)
 .IP \[bu] 2
 Fix quickxorhash on 32 bit architectures (Nick Craig-Wood)
 .IP \[bu] 2
-Report any list errors during \f[C]rclone cleanup\f[R] (albertony)
+Report any list errors during \f[V]rclone cleanup\f[R] (albertony)
 .RE
 .IP \[bu] 2
 Putio
@@ -75330,11 +75928,11 @@ Fix server side copy failures (400 errors) (Nick Craig-Wood)
 S3
 .RS 2
 .IP \[bu] 2
-Empty directory markers (J\[u0101]nis Bebr\[u012B]tis, Nick Craig-Wood)
+Empty directory markers (Jānis Bebrītis, Nick Craig-Wood)
 .IP \[bu] 2
 Update Scaleway storage classes (Brian Starkey)
 .IP \[bu] 2
-Fix \f[C]--s3-versions\f[R] on individual objects (Nick Craig-Wood)
+Fix \f[V]--s3-versions\f[R] on individual objects (Nick Craig-Wood)
 .IP \[bu] 2
 Fix hang on aborting multipart upload with iDrive e2 (Nick Craig-Wood)
 .IP \[bu] 2
@@ -75351,10 +75949,10 @@ Fix Qiniu KODO quirks virtualHostStyle is false (zzq)
 SFTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--sftp-host-key-algorithms\f[R] to allow specifying SSH host
+Add \f[V]--sftp-host-key-algorithms\f[R] to allow specifying SSH host
 key algorithms (Joel)
 .IP \[bu] 2
-Fix using \f[C]--sftp-key-use-agent\f[R] and \f[C]--sftp-key-file\f[R]
+Fix using \f[V]--sftp-key-use-agent\f[R] and \f[V]--sftp-key-file\f[R]
 together needing private key file (Arnav Singh)
 .IP \[bu] 2
 Fix move to allow overwriting existing files (Nick Craig-Wood)
@@ -75405,7 +76003,7 @@ Allow errors to be unwrapped for inspection (Nick Craig-Wood)
 Uptobox
 .RS 2
 .IP \[bu] 2
-Add \f[C]--uptobox-private\f[R] flag to make all uploaded files private
+Add \f[V]--uptobox-private\f[R] flag to make all uploaded files private
 (Nick Craig-Wood)
 .IP \[bu] 2
 Fix improper regex (Aaron Gokaslan)
@@ -75422,7 +76020,7 @@ nextcloud: Add support for chunked uploads (Paul)
 .IP \[bu] 2
 Set modtime using propset for owncloud and nextcloud (WeidiDeng)
 .IP \[bu] 2
-Make pacer minSleep configurable with \f[C]--webdav-pacer-min-sleep\f[R]
+Make pacer minSleep configurable with \f[V]--webdav-pacer-min-sleep\f[R]
 (ed)
 .IP \[bu] 2
 Fix server side copy/move not overwriting (WeidiDeng)
@@ -75440,7 +76038,7 @@ Fix 400 Bad Request on transfer failure (Nick Craig-Wood)
 Zoho
 .RS 2
 .IP \[bu] 2
-Fix downloads with \f[C]Range:\f[R] header returning the wrong data
+Fix downloads with \f[V]Range:\f[R] header returning the wrong data
 (Nick Craig-Wood)
 .RE
 .SS v1.62.2 - 2023-03-16
@@ -75509,20 +76107,20 @@ fs
 Added multiple ca certificate support.
 (alankrit)
 .IP \[bu] 2
-Add \f[C]--max-delete-size\f[R] a delete size threshold (Leandro
+Add \f[V]--max-delete-size\f[R] a delete size threshold (Leandro
 Sacchet)
 .RE
 .IP \[bu] 2
-fspath: Allow the symbols \f[C]\[at]\f[R] and \f[C]+\f[R] in remote
+fspath: Allow the symbols \f[V]\[at]\f[R] and \f[V]+\f[R] in remote
 names (albertony)
 .IP \[bu] 2
 lib/terminal: Enable windows console virtual terminal sequences
 processing (ANSI/VT100 colors) (albertony)
 .IP \[bu] 2
-move: If \f[C]--check-first\f[R] and \f[C]--order-by\f[R] are set then
+move: If \f[V]--check-first\f[R] and \f[V]--order-by\f[R] are set then
 delete with perfect ordering (Nick Craig-Wood)
 .IP \[bu] 2
-serve http: Support \f[C]--auth-proxy\f[R] (Matthias Baur)
+serve http: Support \f[V]--auth-proxy\f[R] (Matthias Baur)
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -75561,20 +76159,20 @@ deletefile: Return error code 4 if file does not exist (Nick Craig-Wood)
 docker: Fix volume plugin does not remount volume on docker restart
 (logopk)
 .IP \[bu] 2
-fs: Fix race conditions in \f[C]--max-delete\f[R] and
-\f[C]--max-delete-size\f[R] (Nick Craig-Wood)
+fs: Fix race conditions in \f[V]--max-delete\f[R] and
+\f[V]--max-delete-size\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 lib/oauthutil: Handle fatal errors better (Alex Chen)
 .IP \[bu] 2
-mount2: Fix \f[C]--allow-non-empty\f[R] (Nick Craig-Wood)
+mount2: Fix \f[V]--allow-non-empty\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-operations: Fix concurrency: use \f[C]--checkers\f[R] unless
+operations: Fix concurrency: use \f[V]--checkers\f[R] unless
 transferring files (Nick Craig-Wood)
 .IP \[bu] 2
 serve ftp: Fix timestamps older than 1 year in listings (Nick
 Craig-Wood)
 .IP \[bu] 2
-sync: Fix concurrency: use \f[C]--checkers\f[R] unless transferring
+sync: Fix concurrency: use \f[V]--checkers\f[R] unless transferring
 files (Nick Craig-Wood)
 .IP \[bu] 2
 tree
@@ -75595,12 +76193,12 @@ Mount
 Fix creating and renaming files on case insensitive backends (Nick
 Craig-Wood)
 .IP \[bu] 2
-Do not treat \f[C]\[rs]\[rs]?\[rs]\f[R] prefixed paths as network share
+Do not treat \f[V]\[rs]\[rs]?\[rs]\f[R] prefixed paths as network share
 paths on windows (albertony)
 .IP \[bu] 2
 Fix check for empty mount point on Linux (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--allow-non-empty\f[R] (Nick Craig-Wood)
+Fix \f[V]--allow-non-empty\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Avoid incorrect or premature overlap check on windows (albertony)
 .IP \[bu] 2
@@ -75623,7 +76221,7 @@ Craig-Wood)
 Local
 .RS 2
 .IP \[bu] 2
-Fix \f[C]%!w(<nil>)\f[R] in \[dq]failed to read directory\[dq] error
+Fix \f[V]%!w(<nil>)\f[R] in \[dq]failed to read directory\[dq] error
 (Marks Polakovs)
 .IP \[bu] 2
 Fix exclusion of dangling symlinks with -L/--copy-links (Nick
@@ -75633,7 +76231,7 @@ Craig-Wood)
 Crypt
 .RS 2
 .IP \[bu] 2
-Obey \f[C]--ignore-checksum\f[R] (Nick Craig-Wood)
+Obey \f[V]--ignore-checksum\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix for unencrypted directory names on case insensitive remotes (Ole
 Frost)
@@ -75654,10 +76252,10 @@ Fix uploading files bigger than 1TiB (Nick Craig-Wood)
 Drive
 .RS 2
 .IP \[bu] 2
-Note that \f[C]--drive-acknowledge-abuse\f[R] needs SA Manager
+Note that \f[V]--drive-acknowledge-abuse\f[R] needs SA Manager
 permission (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]--drive-stop-on-upload-limit\f[R] to respond to
+Make \f[V]--drive-stop-on-upload-limit\f[R] to respond to
 storageQuotaExceeded (Ninh Pham)
 .RE
 .IP \[bu] 2
@@ -75668,21 +76266,21 @@ Retry 426 errors (Nick Craig-Wood)
 .IP \[bu] 2
 Retry errors when initiating downloads (Nick Craig-Wood)
 .IP \[bu] 2
-Revert to upstream \f[C]github.com/jlaffaye/ftp\f[R] now fix is merged
+Revert to upstream \f[V]github.com/jlaffaye/ftp\f[R] now fix is merged
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Add \f[C]--gcs-env-auth\f[R] to pick up IAM credentials from
+Add \f[V]--gcs-env-auth\f[R] to pick up IAM credentials from
 env/instance (Peter Brunner)
 .RE
 .IP \[bu] 2
 Mega
 .RS 2
 .IP \[bu] 2
-Add \f[C]--mega-use-https\f[R] flag (NodudeWasTaken)
+Add \f[V]--mega-use-https\f[R] flag (NodudeWasTaken)
 .RE
 .IP \[bu] 2
 Onedrive
@@ -75691,7 +76289,7 @@ Onedrive
 Default onedrive personal to QuickXorHash as Microsoft is removing SHA1
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--onedrive-hash-type\f[R] to change the hash in use (Nick
+Add \f[V]--onedrive-hash-type\f[R] to change the hash in use (Nick
 Craig-Wood)
 .IP \[bu] 2
 Improve speed of QuickXorHash (LXY)
@@ -75703,7 +76301,7 @@ Oracle Object Storage
 Speed up operations by using S3 pacer and setting minsleep to 10ms
 (Manoj Ghosh)
 .IP \[bu] 2
-Expose the \f[C]storage_tier\f[R] option in config (Manoj Ghosh)
+Expose the \f[V]storage_tier\f[R] option in config (Manoj Ghosh)
 .IP \[bu] 2
 Bring your own encryption keys (Manoj Ghosh)
 .RE
@@ -75711,16 +76309,16 @@ Bring your own encryption keys (Manoj Ghosh)
 S3
 .RS 2
 .IP \[bu] 2
-Check multipart upload ETag when \f[C]--s3-no-head\f[R] is in use (Nick
+Check multipart upload ETag when \f[V]--s3-no-head\f[R] is in use (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-sts-endpoint\f[R] to specify STS endpoint (Nick
+Add \f[V]--s3-sts-endpoint\f[R] to specify STS endpoint (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix incorrect tier support for StorJ and IDrive when pointing at a file
 (Ole Frost)
 .IP \[bu] 2
-Fix AWS STS failing if \f[C]--s3-endpoint\f[R] is set (Nick Craig-Wood)
+Fix AWS STS failing if \f[V]--s3-endpoint\f[R] is set (Nick Craig-Wood)
 .IP \[bu] 2
 Make purge remove directory markers too (Nick Craig-Wood)
 .RE
@@ -75749,9 +76347,9 @@ Check smb connection is closed (happyxhw)
 Storj
 .RS 2
 .IP \[bu] 2
-Implement \f[C]rclone link\f[R] (Kaloyan Raev)
+Implement \f[V]rclone link\f[R] (Kaloyan Raev)
 .IP \[bu] 2
-Implement \f[C]rclone purge\f[R] (Kaloyan Raev)
+Implement \f[V]rclone purge\f[R] (Kaloyan Raev)
 .IP \[bu] 2
 Update satellite urls and labels (Kaloyan Raev)
 .RE
@@ -75780,13 +76378,13 @@ Fix unescaped HTML (Nick Craig-Wood)
 lib/http: Shutdown all servers on exit to remove unix socket (Nick
 Craig-Wood)
 .IP \[bu] 2
-rc: Fix \f[C]--rc-addr\f[R] flag (which is an alternate for
-\f[C]--url\f[R]) (Anagh Kumar Baranwal)
+rc: Fix \f[V]--rc-addr\f[R] flag (which is an alternate for
+\f[V]--url\f[R]) (Anagh Kumar Baranwal)
 .IP \[bu] 2
 serve restic
 .RS 2
 .IP \[bu] 2
-Don\[aq]t serve via http if serving via \f[C]--stdio\f[R] (Nick
+Don\[aq]t serve via http if serving via \f[V]--stdio\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix immediate exit when not using stdio (Nick Craig-Wood)
@@ -75795,7 +76393,7 @@ Fix immediate exit when not using stdio (Nick Craig-Wood)
 serve webdav
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--baseurl\f[R] handling after \f[C]lib/http\f[R] refactor (Nick
+Fix \f[V]--baseurl\f[R] handling after \f[V]lib/http\f[R] refactor (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix running duplicate Serve call (Nick Craig-Wood)
@@ -75833,7 +76431,7 @@ New Features
 .IP \[bu] 2
 build: Add vulnerability testing using govulncheck (albertony)
 .IP \[bu] 2
-cmd: Enable \f[C]SIGINFO\f[R] (Ctrl-T) handler on FreeBSD, NetBSD,
+cmd: Enable \f[V]SIGINFO\f[R] (Ctrl-T) handler on FreeBSD, NetBSD,
 OpenBSD and Dragonfly BSD (x3-apptech)
 .IP \[bu] 2
 config: Add config/setpath (https://rclone.org/rc/#config-setpath) for
@@ -75867,10 +76465,10 @@ and friends (Nick Craig-Wood)
 fs
 .RS 2
 .IP \[bu] 2
-Make all duration flags take \f[C]y\f[R], \f[C]M\f[R], \f[C]w\f[R],
-\f[C]d\f[R] etc suffixes (Nick Craig-Wood)
+Make all duration flags take \f[V]y\f[R], \f[V]M\f[R], \f[V]w\f[R],
+\f[V]d\f[R] etc suffixes (Nick Craig-Wood)
 .IP \[bu] 2
-Add global flag \f[C]--color\f[R] to control terminal colors (Kevin
+Add global flag \f[V]--color\f[R] to control terminal colors (Kevin
 Verstaen)
 .RE
 .IP \[bu] 2
@@ -75879,7 +76477,7 @@ fspath: Allow unicode numbers and letters in remote names (albertony)
 lib/file: Improve error message for creating dir on non-existent network
 host on windows (albertony)
 .IP \[bu] 2
-lib/http: Finish port of rclone servers to \f[C]lib/http\f[R] (Tom
+lib/http: Finish port of rclone servers to \f[V]lib/http\f[R] (Tom
 Mombourquette, Nick Craig-Wood)
 .IP \[bu] 2
 lib/oauthutil: Improved usability of config flows needing web browser
@@ -75901,30 +76499,30 @@ Percent (https://rclone.org/rc/#debug-set-gc-percent) & Memory Limit (go
 .IP \[bu] 2
 rcat: Preserve metadata when Copy falls back to Rcat (Nick Craig-Wood)
 .IP \[bu] 2
-rcd: Refactor rclone rc server to use \f[C]lib/http\f[R] (Nick
+rcd: Refactor rclone rc server to use \f[V]lib/http\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 rcserver: Avoid generating default credentials with htpasswd (Kamui)
 .IP \[bu] 2
-restic: Refactor to use \f[C]lib/http\f[R] (Nolan Woods)
+restic: Refactor to use \f[V]lib/http\f[R] (Nolan Woods)
 .IP \[bu] 2
 serve http: Support unix sockets and multiple listeners (Tom
 Mombourquette)
 .IP \[bu] 2
-serve webdav: Refactor to use \f[C]lib/http\f[R] (Nick Craig-Wood)
+serve webdav: Refactor to use \f[V]lib/http\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-test: Replace defer cleanup with \f[C]t.Cleanup\f[R] (Eng Zer Jun)
+test: Replace defer cleanup with \f[V]t.Cleanup\f[R] (Eng Zer Jun)
 .IP \[bu] 2
-test memory: Read metadata if \f[C]-M\f[R] flag is specified (Nick
+test memory: Read metadata if \f[V]-M\f[R] flag is specified (Nick
 Craig-Wood)
 .IP \[bu] 2
-wasm: Comply with \f[C]wasm_exec.js\f[R] licence terms (Matthew Vernon)
+wasm: Comply with \f[V]wasm_exec.js\f[R] licence terms (Matthew Vernon)
 .RE
 .IP \[bu] 2
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-build: Update \f[C]golang.org/x/net/http2\f[R] to fix GO-2022-1144 (Nick
+build: Update \f[V]golang.org/x/net/http2\f[R] to fix GO-2022-1144 (Nick
 Craig-Wood)
 .IP \[bu] 2
 restic: Fix typo in docs \[aq]remove\[aq] should be \[aq]remote\[aq]
@@ -75947,8 +76545,8 @@ VFS
 Windows: fix slow opening of exe files by not truncating files when not
 necessary (Nick Craig-Wood)
 .IP \[bu] 2
-Fix IO Error opening a file with \f[C]O_CREATE|O_RDONLY\f[R] in
-\f[C]--vfs-cache-mode\f[R] not full (Nick Craig-Wood)
+Fix IO Error opening a file with \f[V]O_CREATE|O_RDONLY\f[R] in
+\f[V]--vfs-cache-mode\f[R] not full (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Crypt
@@ -75972,10 +76570,10 @@ Thanks to Stonebranch (https://www.stonebranch.com/) for sponsoring this
 work.
 .RE
 .IP \[bu] 2
-Add \f[C]--azureblob-no-check-container\f[R] to assume container exists
+Add \f[V]--azureblob-no-check-container\f[R] to assume container exists
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--use-server-modtime\f[R] support (Abdullah Saglam)
+Add \f[V]--use-server-modtime\f[R] support (Abdullah Saglam)
 .IP \[bu] 2
 Add support for custom upload headers (rkettelerij)
 .IP \[bu] 2
@@ -75984,7 +76582,7 @@ Allow emulator account/key override (Roel Arents)
 Support simple \[dq]environment credentials\[dq] (Nathaniel Wesley
 Filardo)
 .IP \[bu] 2
-Ignore \f[C]AuthorizationFailure\f[R] when trying to create a create a
+Ignore \f[V]AuthorizationFailure\f[R] when trying to create a create a
 container (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -76007,18 +76605,18 @@ FTP
 Update help text of implicit/explicit TLS options to refer to FTPS
 instead of FTP (ycdtosa)
 .IP \[bu] 2
-Improve performance to speed up \f[C]--files-from\f[R] and
-\f[C]NewObject\f[R] (Anthony Pessy)
+Improve performance to speed up \f[V]--files-from\f[R] and
+\f[V]NewObject\f[R] (Anthony Pessy)
 .RE
 .IP \[bu] 2
 HTTP
 .RS 2
 .IP \[bu] 2
-Parse GET responses when \f[C]no_head\f[R] is set (Arnie97)
+Parse GET responses when \f[V]no_head\f[R] is set (Arnie97)
 .IP \[bu] 2
-Do not update object size based on \f[C]Range\f[R] requests (Arnie97)
+Do not update object size based on \f[V]Range\f[R] requests (Arnie97)
 .IP \[bu] 2
-Support \f[C]Content-Range\f[R] response header (Arnie97)
+Support \f[V]Content-Range\f[R] response header (Arnie97)
 .RE
 .IP \[bu] 2
 Onedrive
@@ -76032,17 +76630,17 @@ S3
 .IP \[bu] 2
 Add Liara LOS to provider list (MohammadReza)
 .IP \[bu] 2
-Add DigitalOcean Spaces regions \f[C]sfo3\f[R], \f[C]fra1\f[R],
-\f[C]syd1\f[R] (Jack)
+Add DigitalOcean Spaces regions \f[V]sfo3\f[R], \f[V]fra1\f[R],
+\f[V]syd1\f[R] (Jack)
 .IP \[bu] 2
-Avoid privileged \f[C]GetBucketLocation\f[R] to resolve s3 region
+Avoid privileged \f[V]GetBucketLocation\f[R] to resolve s3 region
 (Anthony Pessy)
 .IP \[bu] 2
-Stop setting object and bucket ACL to \f[C]private\f[R] if it is an
+Stop setting object and bucket ACL to \f[V]private\f[R] if it is an
 empty string (Philip Harvey)
 .IP \[bu] 2
 If bucket or object ACL is empty string then don\[aq]t add
-\f[C]X-Amz-Acl:\f[R] header (Nick Craig-Wood)
+\f[V]X-Amz-Acl:\f[R] header (Nick Craig-Wood)
 .IP \[bu] 2
 Reduce memory consumption for s3 objects (Erik Agterdenbos)
 .IP \[bu] 2
@@ -76052,8 +76650,8 @@ Fix nil pointer exception when using Versions (Nick Craig-Wood)
 .IP \[bu] 2
 Fix excess memory usage when using versions (Nick Craig-Wood)
 .IP \[bu] 2
-Ignore versionIDs from uploads unless using \f[C]--s3-versions\f[R] or
-\f[C]--s3-versions-at\f[R] (Nick Craig-Wood)
+Ignore versionIDs from uploads unless using \f[V]--s3-versions\f[R] or
+\f[V]--s3-versions-at\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 SFTP
@@ -76087,8 +76685,8 @@ Bug Fixes
 .IP \[bu] 2
 lib/cache: Fix alias backend shutting down too soon (Nick Craig-Wood)
 .IP \[bu] 2
-wasm: Fix walltime link error by adding up-to-date wasm_exec.js
-(Jo\[~a]o Henrique Franco)
+wasm: Fix walltime link error by adding up-to-date wasm_exec.js (João
+Henrique Franco)
 .IP \[bu] 2
 docs
 .RS 2
@@ -76107,10 +76705,9 @@ Faq: how to use a proxy server that requires a username and password
 .IP \[bu] 2
 Oracle-object-storage: doc fix (Manoj Ghosh)
 .IP \[bu] 2
-Fix typo \f[C]remove\f[R] in rclone_serve_restic command (Joda
-St\[:o]\[ss]er)
+Fix typo \f[V]remove\f[R] in rclone_serve_restic command (Joda Stößer)
 .IP \[bu] 2
-Fix character that was incorrectly interpreted as markdown (Cl\['e]ment
+Fix character that was incorrectly interpreted as markdown (Clément
 Notin)
 .RE
 .RE
@@ -76141,7 +76738,7 @@ Allow timestamps to be before the epoch 1970-01-01 (Nick Craig-Wood)
 S3
 .RS 2
 .IP \[bu] 2
-Add provider quirk \f[C]--s3-might-gzip\f[R] to fix corrupted on
+Add provider quirk \f[V]--s3-might-gzip\f[R] to fix corrupted on
 transfer: sizes differ (Nick Craig-Wood)
 .IP \[bu] 2
 Allow Storj to server side copy since it seems to work now (Nick
@@ -76155,7 +76752,7 @@ Add additional Wasabi locations (techknowlogick)
 Smb
 .RS 2
 .IP \[bu] 2
-Fix \f[C]Failed to sync: context canceled\f[R] at the end of syncs (Nick
+Fix \f[V]Failed to sync: context canceled\f[R] at the end of syncs (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -76201,30 +76798,30 @@ Install.sh: fix arm-v7 download (Ole Frost)
 fs: Warn the user when using an existing remote name without a colon
 (Nick Craig-Wood)
 .IP \[bu] 2
-httplib: Add \f[C]--xxx-min-tls-version\f[R] option to select minimum
+httplib: Add \f[V]--xxx-min-tls-version\f[R] option to select minimum
 TLS version for HTTP servers (Robert Newson)
 .IP \[bu] 2
-librclone: Add PHP bindings and test program (Jordi Gonzalez Mu\[~n]oz)
+librclone: Add PHP bindings and test program (Jordi Gonzalez Muñoz)
 .IP \[bu] 2
 operations
 .RS 2
 .IP \[bu] 2
-Add \f[C]--server-side-across-configs\f[R] global flag for any backend
+Add \f[V]--server-side-across-configs\f[R] global flag for any backend
 (Nick Craig-Wood)
 .IP \[bu] 2
-Optimise \f[C]--copy-dest\f[R] and \f[C]--compare-dest\f[R] (Nick
+Optimise \f[V]--copy-dest\f[R] and \f[V]--compare-dest\f[R] (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
-rc: add \f[C]job/stopgroup\f[R] to stop group (Evan Spensley)
+rc: add \f[V]job/stopgroup\f[R] to stop group (Evan Spensley)
 .IP \[bu] 2
 serve dlna
 .RS 2
 .IP \[bu] 2
-Add \f[C]--announce-interval\f[R] to control SSDP Announce Interval
+Add \f[V]--announce-interval\f[R] to control SSDP Announce Interval
 (YanceyChiew)
 .IP \[bu] 2
-Add \f[C]--interface\f[R] to Specify SSDP interface names line (Simon
+Add \f[V]--interface\f[R] to Specify SSDP interface names line (Simon
 Bos)
 .IP \[bu] 2
 Add support for more external subtitles (YanceyChiew)
@@ -76232,12 +76829,12 @@ Add support for more external subtitles (YanceyChiew)
 Add verification of addresses (YanceyChiew)
 .RE
 .IP \[bu] 2
-sync: Optimise \f[C]--copy-dest\f[R] and \f[C]--compare-dest\f[R] (Nick
+sync: Optimise \f[V]--copy-dest\f[R] and \f[V]--compare-dest\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-doc updates (albertony, Alexander Knorr, anonion, Jo\[~a]o Henrique
-Franco, Josh Soref, Lorenzo Milesi, Marco Molteni, Mark Trolley, Ole
-Frost, partev, Ryan Morey, Tom Mombourquette, YFdyh000)
+doc updates (albertony, Alexander Knorr, anonion, João Henrique Franco,
+Josh Soref, Lorenzo Milesi, Marco Molteni, Mark Trolley, Ole Frost,
+partev, Ryan Morey, Tom Mombourquette, YFdyh000)
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -76246,18 +76843,18 @@ Bug Fixes
 filter
 .RS 2
 .IP \[bu] 2
-Fix incorrect filtering with \f[C]UseFilter\f[R] context flag and
+Fix incorrect filtering with \f[V]UseFilter\f[R] context flag and
 wrapping backends (Nick Craig-Wood)
 .IP \[bu] 2
-Make sure we check \f[C]--files-from\f[R] when looking for a single file
+Make sure we check \f[V]--files-from\f[R] when looking for a single file
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 rc
 .RS 2
 .IP \[bu] 2
-Fix \f[C]mount/listmounts\f[R] not returning the full Fs entered in
-\f[C]mount/mount\f[R] (Tom Mombourquette)
+Fix \f[V]mount/listmounts\f[R] not returning the full Fs entered in
+\f[V]mount/mount\f[R] (Tom Mombourquette)
 .IP \[bu] 2
 Handle external unmount when mounting (Isaac Aymerich)
 .IP \[bu] 2
@@ -76272,7 +76869,7 @@ sync: Update docs and error messages to reflect fixes to overlap checks
 VFS
 .RS 2
 .IP \[bu] 2
-Reduce memory use by embedding \f[C]sync.Cond\f[R] (Nick Craig-Wood)
+Reduce memory use by embedding \f[V]sync.Cond\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Reduce memory usage by re-ordering commonly used structures (Nick
 Craig-Wood)
@@ -76301,15 +76898,15 @@ Fix error handling to not use or return nil objects (Nick Craig-Wood)
 Drive
 .RS 2
 .IP \[bu] 2
-Make \f[C]--drive-stop-on-upload-limit\f[R] obey quota exceeded error
+Make \f[V]--drive-stop-on-upload-limit\f[R] obey quota exceeded error
 (Steve Kowalik)
 .RE
 .IP \[bu] 2
 FTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--ftp-force-list-hidden\f[R] option to show hidden items
-(\[/O]yvind Heddeland Instefjord)
+Add \f[V]--ftp-force-list-hidden\f[R] option to show hidden items
+(Øyvind Heddeland Instefjord)
 .IP \[bu] 2
 Fix hang when using ExplicitTLS to certain servers.
 (Nick Craig-Wood)
@@ -76318,7 +76915,7 @@ Fix hang when using ExplicitTLS to certain servers.
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Add \f[C]--gcs-endpoint\f[R] flag and config parameter (Nick Craig-Wood)
+Add \f[V]--gcs-endpoint\f[R] flag and config parameter (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Hubic
@@ -76339,31 +76936,31 @@ Craig-Wood)
 S3
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--s3-versions\f[R] flag to show old versions of objects
+Implement \f[V]--s3-versions\f[R] flag to show old versions of objects
 if enabled (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--s3-version-at\f[R] flag to show versions of objects at
+Implement \f[V]--s3-version-at\f[R] flag to show versions of objects at
 a particular time (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]backend versioning\f[R] command to get/set bucket
+Implement \f[V]backend versioning\f[R] command to get/set bucket
 versioning (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]Purge\f[R] to purge versions and
-\f[C]backend cleanup-hidden\f[R] (Nick Craig-Wood)
+Implement \f[V]Purge\f[R] to purge versions and
+\f[V]backend cleanup-hidden\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-decompress\f[R] flag to decompress gzip-encoded files
+Add \f[V]--s3-decompress\f[R] flag to decompress gzip-encoded files
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-sse-customer-key-base64\f[R] to supply keys with binary
+Add \f[V]--s3-sse-customer-key-base64\f[R] to supply keys with binary
 data (Richard Bateman)
 .IP \[bu] 2
 Try to keep the maximum precision in ModTime with
-\f[C]--user-server-modtime\f[R] (Nick Craig-Wood)
+\f[V]--user-server-modtime\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Drop binary metadata with an ERROR message as it can\[aq]t be stored
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-no-system-metadata\f[R] to suppress read and write of
+Add \f[V]--s3-no-system-metadata\f[R] to suppress read and write of
 system metadata (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -76376,7 +76973,7 @@ Fix directory creation races (Lesmiscore)
 Swift
 .RS 2
 .IP \[bu] 2
-Add \f[C]--swift-no-large-objects\f[R] to reduce HEAD requests (Nick
+Add \f[V]--swift-no-large-objects\f[R] to reduce HEAD requests (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -76450,7 +77047,7 @@ sync: Add accidentally missed filter-sensitivity to --backup-dir option
 Combine
 .RS 2
 .IP \[bu] 2
-Fix docs showing \f[C]remote=\f[R] instead of \f[C]upstreams=\f[R] (Nick
+Fix docs showing \f[V]remote=\f[R] instead of \f[V]upstreams=\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 Throw error if duplicate directory name is specified (Nick Craig-Wood)
@@ -76554,13 +77151,13 @@ Metadata framework (https://rclone.org/docs/#metadata) to read and write
 system and user metadata on backends (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-Implemented initially for \f[C]local\f[R], \f[C]s3\f[R] and
-\f[C]internetarchive\f[R] backends
+Implemented initially for \f[V]local\f[R], \f[V]s3\f[R] and
+\f[V]internetarchive\f[R] backends
 .IP \[bu] 2
-\f[C]--metadata\f[R]/\f[C]-M\f[R] flag to control whether metadata is
+\f[V]--metadata\f[R]/\f[V]-M\f[R] flag to control whether metadata is
 copied
 .IP \[bu] 2
-\f[C]--metadata-set\f[R] flag to specify metadata for uploads
+\f[V]--metadata-set\f[R] flag to specify metadata for uploads
 .IP \[bu] 2
 Thanks to Manz Solutions (https://manz-solutions.at/) for sponsoring
 this work.
@@ -76577,7 +77174,7 @@ Craig-Wood)
 .IP \[bu] 2
 All windows binaries now no longer CGO (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]linux/arm/v6\f[R] to docker images (Nick Craig-Wood)
+Add \f[V]linux/arm/v6\f[R] to docker images (Nick Craig-Wood)
 .IP \[bu] 2
 A huge number of fixes found with staticcheck (https://staticcheck.io/)
 (albertony)
@@ -76585,17 +77182,17 @@ A huge number of fixes found with staticcheck (https://staticcheck.io/)
 Configurable version suffix independent of version number (albertony)
 .RE
 .IP \[bu] 2
-check: Implement \f[C]--no-traverse\f[R] and
-\f[C]--no-unicode-normalization\f[R] (Nick Craig-Wood)
+check: Implement \f[V]--no-traverse\f[R] and
+\f[V]--no-unicode-normalization\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 config: Readability improvements (albertony)
 .IP \[bu] 2
-copyurl: Add \f[C]--header-filename\f[R] to honor the HTTP header
+copyurl: Add \f[V]--header-filename\f[R] to honor the HTTP header
 filename directive (J-P Treen)
 .IP \[bu] 2
-filter: Allow multiple \f[C]--exclude-if-present\f[R] flags (albertony)
+filter: Allow multiple \f[V]--exclude-if-present\f[R] flags (albertony)
 .IP \[bu] 2
-fshttp: Add \f[C]--disable-http-keep-alives\f[R] to disable HTTP Keep
+fshttp: Add \f[V]--disable-http-keep-alives\f[R] to disable HTTP Keep
 Alives (Nick Craig-Wood)
 .IP \[bu] 2
 install.sh
@@ -76604,15 +77201,15 @@ install.sh
 Set the modes on the files and/or directories on macOS (Michael C
 Tiernan - MIT-Research Computing Project)
 .IP \[bu] 2
-Pre verify sudo authorization \f[C]-v\f[R] before calling curl.
+Pre verify sudo authorization \f[V]-v\f[R] before calling curl.
 (Michael C Tiernan - MIT-Research Computing Project)
 .RE
 .IP \[bu] 2
 lib/encoder: Add Semicolon encoding (Nick Craig-Wood)
 .IP \[bu] 2
-lsf: Add metadata support with \f[C]M\f[R] flag (Nick Craig-Wood)
+lsf: Add metadata support with \f[V]M\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
-lsjson: Add \f[C]--metadata\f[R]/\f[C]-M\f[R] flag (Nick Craig-Wood)
+lsjson: Add \f[V]--metadata\f[R]/\f[V]-M\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 ncdu
 .RS 2
@@ -76635,26 +77232,26 @@ Use correct src/dst in some log messages (zzr93)
 .IP \[bu] 2
 rcat: Check checksums by default like copy does (Nick Craig-Wood)
 .IP \[bu] 2
-selfupdate: Replace deprecated \f[C]x/crypto/openpgp\f[R] package with
-\f[C]ProtonMail/go-crypto\f[R] (albertony)
+selfupdate: Replace deprecated \f[V]x/crypto/openpgp\f[R] package with
+\f[V]ProtonMail/go-crypto\f[R] (albertony)
 .IP \[bu] 2
-serve ftp: Check \f[C]--passive-port\f[R] arguments are correct (Nick
+serve ftp: Check \f[V]--passive-port\f[R] arguments are correct (Nick
 Craig-Wood)
 .IP \[bu] 2
 size: Warn about inaccurate results when objects with unknown size
 (albertony)
 .IP \[bu] 2
-sync: Overlap check is now filter-sensitive so \f[C]--backup-dir\f[R]
+sync: Overlap check is now filter-sensitive so \f[V]--backup-dir\f[R]
 can be in the root provided it is filtered (Nick)
 .IP \[bu] 2
 test info: Check file name lengths using 1,2,3,4 byte unicode characters
 (Nick Craig-Wood)
 .IP \[bu] 2
-test makefile(s): \f[C]--sparse\f[R], \f[C]--zero\f[R],
-\f[C]--pattern\f[R], \f[C]--ascii\f[R], \f[C]--chargen\f[R] flags to
+test makefile(s): \f[V]--sparse\f[R], \f[V]--zero\f[R],
+\f[V]--pattern\f[R], \f[V]--ascii\f[R], \f[V]--chargen\f[R] flags to
 control file contents (Nick Craig-Wood)
 .IP \[bu] 2
-Make sure we call the \f[C]Shutdown\f[R] method on backends (Martin
+Make sure we call the \f[V]Shutdown\f[R] method on backends (Martin
 Czygan)
 .RE
 .IP \[bu] 2
@@ -76670,10 +77267,10 @@ ncdu: Fix issue where dir size is summed when file sizes are -1
 sync/copy/move
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--fast-list\f[R] \f[C]--create-empty-src-dirs\f[R] and
-\f[C]--exclude\f[R] (Nick Craig-Wood)
+Fix \f[V]--fast-list\f[R] \f[V]--create-empty-src-dirs\f[R] and
+\f[V]--exclude\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--max-duration\f[R] and \f[C]--cutoff-mode soft\f[R] (Nick
+Fix \f[V]--max-duration\f[R] and \f[V]--cutoff-mode soft\f[R] (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -76686,21 +77283,21 @@ size/timestamp changing) (albertony)
 Mount
 .RS 2
 .IP \[bu] 2
-Support \f[C]windows/arm64\f[R] (may still be problems - see
+Support \f[V]windows/arm64\f[R] (may still be problems - see
 #5828 (https://github.com/rclone/rclone/issues/5828)) (Nick Craig-Wood)
 .IP \[bu] 2
 Log IO errors at ERROR level (Nick Craig-Wood)
 .IP \[bu] 2
-Ignore \f[C]_netdev\f[R] mount argument (Hugal31)
+Ignore \f[V]_netdev\f[R] mount argument (Hugal31)
 .RE
 .IP \[bu] 2
 VFS
 .RS 2
 .IP \[bu] 2
-Add \f[C]--vfs-fast-fingerprint\f[R] for less accurate but faster
+Add \f[V]--vfs-fast-fingerprint\f[R] for less accurate but faster
 fingerprints (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--vfs-disk-space-total-size\f[R] option to manually set the
+Add \f[V]--vfs-disk-space-total-size\f[R] option to manually set the
 total disk space (Claudio Maradonna)
 .IP \[bu] 2
 vfscache: Fix fatal error: sync: unlock of unlocked mutex error (Nick
@@ -76710,7 +77307,7 @@ Craig-Wood)
 Local
 .RS 2
 .IP \[bu] 2
-Fix parsing of \f[C]--local-nounc\f[R] flag (Nick Craig-Wood)
+Fix parsing of \f[V]--local-nounc\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 Add Metadata support (Nick Craig-Wood)
 .RE
@@ -76737,7 +77334,7 @@ Allow remote emulator (azurite) (Lorenzo Maiorfi)
 B2
 .RS 2
 .IP \[bu] 2
-Add \f[C]--b2-version-at\f[R] flag to show file versions at time
+Add \f[V]--b2-version-at\f[R] flag to show file versions at time
 specified (SwazRGB)
 .IP \[bu] 2
 Use chunksize lib to determine chunksize dynamically (Derek Battams)
@@ -76758,16 +77355,16 @@ Support metadata (Nick Craig-Wood)
 Drive
 .RS 2
 .IP \[bu] 2
-Make \f[C]backend config -o config\f[R] add a combined
-\f[C]AllDrives:\f[R] remote (Nick Craig-Wood)
+Make \f[V]backend config -o config\f[R] add a combined
+\f[V]AllDrives:\f[R] remote (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]--drive-shared-with-me\f[R] work with shared drives (Nick
+Make \f[V]--drive-shared-with-me\f[R] work with shared drives (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--drive-resource-key\f[R] for accessing link-shared files (Nick
+Add \f[V]--drive-resource-key\f[R] for accessing link-shared files (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add backend commands \f[C]exportformats\f[R] and \f[C]importformats\f[R]
+Add backend commands \f[V]exportformats\f[R] and \f[V]importformats\f[R]
 for debugging (Nick Craig-Wood)
 .IP \[bu] 2
 Fix 404 errors on copy/server side copy objects from public folder (Nick
@@ -76775,7 +77372,7 @@ Craig-Wood)
 .IP \[bu] 2
 Update Internal OAuth consent screen docs (Phil Shackleton)
 .IP \[bu] 2
-Moved \f[C]root_folder_id\f[R] to advanced section (Abhiraj)
+Moved \f[V]root_folder_id\f[R] to advanced section (Abhiraj)
 .RE
 .IP \[bu] 2
 Dropbox
@@ -76799,19 +77396,19 @@ Parse api error codes and them accordingly (buengese)
 FTP
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]disable_utf8\f[R] option (Jason Zheng)
+Add support for \f[V]disable_utf8\f[R] option (Jason Zheng)
 .IP \[bu] 2
-Revert to upstream \f[C]github.com/jlaffaye/ftp\f[R] from our fork (Nick
+Revert to upstream \f[V]github.com/jlaffaye/ftp\f[R] from our fork (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Add \f[C]--gcs-no-check-bucket\f[R] to minimise transactions and perms
+Add \f[V]--gcs-no-check-bucket\f[R] to minimise transactions and perms
 (Nick Gooding)
 .IP \[bu] 2
-Add \f[C]--gcs-decompress\f[R] flag to decompress gzip-encoded files
+Add \f[V]--gcs-decompress\f[R] flag to decompress gzip-encoded files
 (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
@@ -76861,7 +77458,7 @@ Gallagher)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--poll-interval\f[R] for onedrive (Hugo Laloge)
+Implement \f[V]--poll-interval\f[R] for onedrive (Hugo Laloge)
 .IP \[bu] 2
 Add access scopes option (Sven Gerber)
 .RE
@@ -76903,13 +77500,13 @@ Add support for about and hashsum on windows server (albertony)
 Use vendor-specific VFS statistics extension for about if available
 (albertony)
 .IP \[bu] 2
-Add \f[C]--sftp-chunk-size\f[R] to control packets sizes for high
+Add \f[V]--sftp-chunk-size\f[R] to control packets sizes for high
 latency links (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--sftp-concurrency\f[R] to improve high latency transfers (Nick
+Add \f[V]--sftp-concurrency\f[R] to improve high latency transfers (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--sftp-set-env\f[R] option to set environment variables (Nick
+Add \f[V]--sftp-set-env\f[R] option to set environment variables (Nick
 Craig-Wood)
 .IP \[bu] 2
 Add Hetzner Storage Boxes to supported sftp backends (Anthrazz)
@@ -76925,7 +77522,7 @@ van Velzen)
 Union
 .RS 2
 .IP \[bu] 2
-Add \f[C]min_free_space\f[R] option for \f[C]lfs\f[R]/\f[C]eplfs\f[R]
+Add \f[V]min_free_space\f[R] option for \f[V]lfs\f[R]/\f[V]eplfs\f[R]
 policies (Nick Craig-Wood)
 .IP \[bu] 2
 Fix uploading files to union of all bucket based remotes (Nick
@@ -76934,7 +77531,7 @@ Craig-Wood)
 Fix get free space for remotes which don\[aq]t support it (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]eplus\f[R] policy to select correct entry for existing files
+Fix \f[V]eplus\f[R] policy to select correct entry for existing files
 (Nick Craig-Wood)
 .IP \[bu] 2
 Support metadata (Nick Craig-Wood)
@@ -76973,17 +77570,17 @@ Bug Fixes
 build: Update github.com/billziss-gh to github.com/winfsp (Nick
 Craig-Wood)
 .IP \[bu] 2
-filter: Fix timezone of \f[C]--min-age\f[R]/\f[C]-max-age\f[R] from UTC
+filter: Fix timezone of \f[V]--min-age\f[R]/\f[V]-max-age\f[R] from UTC
 to local as documented (Nick Craig-Wood)
 .IP \[bu] 2
-rc/js: Correct RC method names (S\[u01A1]n Tr\[u1EA7]n-Nguy\[u1EC5]n)
+rc/js: Correct RC method names (Sơn Trần-Nguyễn)
 .IP \[bu] 2
 docs
 .RS 2
 .IP \[bu] 2
 Fix some links to command pages (albertony)
 .IP \[bu] 2
-Add \f[C]--multi-thread-streams\f[R] note to \f[C]--transfers\f[R].
+Add \f[V]--multi-thread-streams\f[R] note to \f[V]--transfers\f[R].
 (Zsolt Ero)
 .RE
 .RE
@@ -76991,7 +77588,7 @@ Add \f[C]--multi-thread-streams\f[R] note to \f[C]--transfers\f[R].
 Mount
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--devname\f[R] and fusermount: unknown option \[aq]fsname\[aq]
+Fix \f[V]--devname\f[R] and fusermount: unknown option \[aq]fsname\[aq]
 when mounting via rc (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -77104,7 +77701,7 @@ New Features
 build
 .RS 2
 .IP \[bu] 2
-Add \f[C]windows/arm64\f[R] build (\f[C]rclone mount\f[R] not supported
+Add \f[V]windows/arm64\f[R] build (\f[V]rclone mount\f[R] not supported
 yet) (Nick Craig-Wood)
 .IP \[bu] 2
 Raise minimum go version to go1.15 (Nick Craig-Wood)
@@ -77117,11 +77714,11 @@ dedupe: Add quit as a choice in interactive mode (albertony)
 dlna: Change icons to the newest ones.
 (Alain Nussbaumer)
 .IP \[bu] 2
-filter: Add \f[C]{{ regexp }}\f[R]
+filter: Add \f[V]{{ regexp }}\f[R]
 syntax (https://rclone.org/filtering/#regexp) to pattern matches (Nick
 Craig-Wood)
 .IP \[bu] 2
-fshttp: Add prometheus metrics for HTTP status code (Micha\[/l] Matczuk)
+fshttp: Add prometheus metrics for HTTP status code (Michał Matczuk)
 .IP \[bu] 2
 hashsum: Support creating hash from data received on stdin (albertony)
 .IP \[bu] 2
@@ -77138,8 +77735,8 @@ operations: Add server-side moves to stats (Ole Frost)
 .IP \[bu] 2
 rc: Allow user to disable authentication for web gui (negative0)
 .IP \[bu] 2
-tree: Remove obsolete \f[C]--human\f[R] replaced by global
-\f[C]--human-readable\f[R] (albertony)
+tree: Remove obsolete \f[V]--human\f[R] replaced by global
+\f[V]--human-readable\f[R] (albertony)
 .IP \[bu] 2
 version: Report correct friendly-name for newer Windows 10/11 versions
 (albertony)
@@ -77154,11 +77751,11 @@ build
 Fix ARM architecture version in .deb packages after nfpm change (Nick
 Craig-Wood)
 .IP \[bu] 2
-Hard fork \f[C]github.com/jlaffaye/ftp\f[R] to fix
-\f[C]go get github.com/rclone/rclone\f[R] (Nick Craig-Wood)
+Hard fork \f[V]github.com/jlaffaye/ftp\f[R] to fix
+\f[V]go get github.com/rclone/rclone\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-oauthutil: Fix crash when webbrowser requests \f[C]/robots.txt\f[R]
+oauthutil: Fix crash when webbrowser requests \f[V]/robots.txt\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
 operations: Fix goroutine leak in case of copy retry (Ankur Gupta)
@@ -77166,17 +77763,17 @@ operations: Fix goroutine leak in case of copy retry (Ankur Gupta)
 rc:
 .RS 2
 .IP \[bu] 2
-Fix \f[C]operations/publiclink\f[R] default for \f[C]expires\f[R]
+Fix \f[V]operations/publiclink\f[R] default for \f[V]expires\f[R]
 parameter (Nick Craig-Wood)
 .IP \[bu] 2
-Fix missing computation of \f[C]transferQueueSize\f[R] when summing up
+Fix missing computation of \f[V]transferQueueSize\f[R] when summing up
 statistics group (Carlo Mion)
 .IP \[bu] 2
-Fix missing \f[C]StatsInfo\f[R] fields in the computation of the group
+Fix missing \f[V]StatsInfo\f[R] fields in the computation of the group
 sum (Carlo Mion)
 .RE
 .IP \[bu] 2
-sync: Fix \f[C]--max-duration\f[R] so it doesn\[aq]t retry when the
+sync: Fix \f[V]--max-duration\f[R] so it doesn\[aq]t retry when the
 duration is exceeded (Nick Craig-Wood)
 .IP \[bu] 2
 touch: Fix issue where a directory is created instead of a file
@@ -77186,18 +77783,18 @@ touch: Fix issue where a directory is created instead of a file
 Mount
 .RS 2
 .IP \[bu] 2
-Add \f[C]--devname\f[R] to set the device name sent to FUSE for mount
+Add \f[V]--devname\f[R] to set the device name sent to FUSE for mount
 display (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 VFS
 .RS 2
 .IP \[bu] 2
-Add \f[C]vfs/stats\f[R] remote control to show statistics (Nick
+Add \f[V]vfs/stats\f[R] remote control to show statistics (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix
-\f[C]failed to _ensure cache internal error: downloaders is nil error\f[R]
+\f[V]failed to _ensure cache internal error: downloaders is nil error\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
 Fix handling of special characters in file names (Bumsu Hyeon)
@@ -77213,20 +77810,20 @@ Craig-Wood)
 Crypt
 .RS 2
 .IP \[bu] 2
-Add \f[C]base64\f[R] and \f[C]base32768\f[R] filename encoding options
+Add \f[V]base64\f[R] and \f[V]base32768\f[R] filename encoding options
 (Max Sum, Sinan Tan)
 .RE
 .IP \[bu] 2
 Azure Blob
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--azureblob-upload-concurrency\f[R] parameter to speed
+Implement \f[V]--azureblob-upload-concurrency\f[R] parameter to speed
 uploads (Nick Craig-Wood)
 .IP \[bu] 2
-Remove 100MB upper limit on \f[C]chunk_size\f[R] as it is no longer
+Remove 100MB upper limit on \f[V]chunk_size\f[R] as it is no longer
 needed (Nick Craig-Wood)
 .IP \[bu] 2
-Raise \f[C]--azureblob-upload-concurrency\f[R] to 16 by default (Nick
+Raise \f[V]--azureblob-upload-concurrency\f[R] to 16 by default (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix crash with SAS URL and no container (Nick Craig-Wood)
@@ -77243,7 +77840,7 @@ Fix memory leak (Nick Craig-Wood)
 Drive
 .RS 2
 .IP \[bu] 2
-Added \f[C]--drive-copy-shortcut-content\f[R] (Abhiraj)
+Added \f[V]--drive-copy-shortcut-content\f[R] (Abhiraj)
 .IP \[bu] 2
 Disable OAuth OOB flow (copy a token) due to Google deprecation (Nick
 Craig-Wood)
@@ -77253,9 +77850,9 @@ See the deprecation
 note (https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html#disallowed-oob).
 .RE
 .IP \[bu] 2
-Add \f[C]--drive-skip-dangling-shortcuts\f[R] flag (Nick Craig-Wood)
+Add \f[V]--drive-skip-dangling-shortcuts\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
-When using a link type \f[C]--drive-export-formats\f[R] shows all doc
+When using a link type \f[V]--drive-export-formats\f[R] shows all doc
 types (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -77277,7 +77874,7 @@ Implemented About functionality (Gourav T)
 FTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--ftp-ask-password\f[R] to prompt for password when needed
+Add \f[V]--ftp-ask-password\f[R] to prompt for password when needed
 (Borna Butkovic)
 .RE
 .IP \[bu] 2
@@ -77349,14 +77946,14 @@ Fix int32 overflow on arm32 (Ivan Andreev)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Add config option for oauth scope \f[C]Sites.Read.All\f[R] (Charlie
+Add config option for oauth scope \f[V]Sites.Read.All\f[R] (Charlie
 Jiang)
 .IP \[bu] 2
 Minor optimization of quickxorhash (Isaac Levy)
 .IP \[bu] 2
-Add \f[C]--onedrive-root-folder-id\f[R] flag (Nick Craig-Wood)
+Add \f[V]--onedrive-root-folder-id\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
-Do not retry on \f[C]400 pathIsTooLong\f[R] error (ctrl-q)
+Do not retry on \f[V]400 pathIsTooLong\f[R] error (ctrl-q)
 .RE
 .IP \[bu] 2
 Pcloud
@@ -77370,18 +77967,18 @@ Fix pre-1970 time stamps (Nick Craig-Wood)
 S3
 .RS 2
 .IP \[bu] 2
-Use \f[C]ListObjectsV2\f[R] for faster listings (Felix Bu\[u0308]nemann)
+Use \f[V]ListObjectsV2\f[R] for faster listings (Felix Bünemann)
 .RS 2
 .IP \[bu] 2
-Fallback to \f[C]ListObject\f[R] v1 on unsupported providers (Nick
+Fallback to \f[V]ListObject\f[R] v1 on unsupported providers (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
-Use the \f[C]ETag\f[R] on multipart transfers to verify the transfer was
+Use the \f[V]ETag\f[R] on multipart transfers to verify the transfer was
 OK (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-Add \f[C]--s3-use-multipart-etag\f[R] provider quirk to disable this on
+Add \f[V]--s3-use-multipart-etag\f[R] provider quirk to disable this on
 unsupported providers (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -77394,17 +77991,17 @@ Seagate Lyve Cloud storage (Nick Craig-Wood)
 .IP \[bu] 2
 SeaweedFS (Chris Lu)
 .IP \[bu] 2
-Storj Shared gateways (M\['a]rton Elek, Nick Craig-Wood)
+Storj Shared gateways (Márton Elek, Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Add Wasabi AP Northeast 2 endpoint info (lindwurm)
 .IP \[bu] 2
-Add \f[C]GLACIER_IR\f[R] storage class (Yunhai Luo)
+Add \f[V]GLACIER_IR\f[R] storage class (Yunhai Luo)
 .IP \[bu] 2
-Document \f[C]Content-MD5\f[R] workaround for object-lock enabled
+Document \f[V]Content-MD5\f[R] workaround for object-lock enabled
 buckets (Paulo Martins)
 .IP \[bu] 2
-Fix multipart upload with \f[C]--no-head\f[R] flag (Nick Craig-Wood)
+Fix multipart upload with \f[V]--no-head\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 Simplify content length processing in s3 with download url (Logeshwaran
 Murugesan)
@@ -77413,7 +78010,7 @@ Murugesan)
 SFTP
 .RS 2
 .IP \[bu] 2
-Add rclone to list of supported \f[C]md5sum\f[R]/\f[C]sha1sum\f[R]
+Add rclone to list of supported \f[V]md5sum\f[R]/\f[V]sha1sum\f[R]
 commands to look for (albertony)
 .IP \[bu] 2
 Refactor so we only have one way of running remote commands (Nick
@@ -77425,7 +78022,7 @@ Craig-Wood)
 Fix unnecessary seeking when uploading and downloading files (Nick
 Craig-Wood)
 .IP \[bu] 2
-Update docs on how to create \f[C]known_hosts\f[R] file (Nick
+Update docs on how to create \f[V]known_hosts\f[R] file (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -77437,7 +78034,7 @@ Rename tardigrade backend to storj backend (Nick Craig-Wood)
 Implement server side Move for files (Nick Craig-Wood)
 .IP \[bu] 2
 Update docs to explain differences between s3 and this backend (Elek,
-M\['a]rton)
+Márton)
 .RE
 .IP \[bu] 2
 Swift
@@ -77450,7 +78047,7 @@ Craig-Wood)
 Union
 .RS 2
 .IP \[bu] 2
-Fix treatment of remotes with \f[C]//\f[R] in (Nick Craig-Wood)
+Fix treatment of remotes with \f[V]//\f[R] in (Nick Craig-Wood)
 .IP \[bu] 2
 Fix deadlock when one part of a multi-upload fails (Nick Craig-Wood)
 .IP \[bu] 2
@@ -77480,7 +78077,7 @@ New commands
 .RS 2
 .IP \[bu] 2
 lsjson --stat: to get info about a single file/dir and
-\f[C]operations/stat\f[R] api (Nick Craig-Wood)
+\f[V]operations/stat\f[R] api (Nick Craig-Wood)
 .IP \[bu] 2
 config paths: show configured paths (albertony)
 .RE
@@ -77507,7 +78104,7 @@ Support hyphen in remote name from environment variable (albertony)
 .IP \[bu] 2
 Make temporary directory user-configurable (albertony)
 .IP \[bu] 2
-Convert \f[C]--cache-dir\f[R] value to an absolute path (albertony)
+Convert \f[V]--cache-dir\f[R] value to an absolute path (albertony)
 .IP \[bu] 2
 Do not override MIME types from OS defaults (albertony)
 .RE
@@ -77524,7 +78121,7 @@ Mention make for building and cmount tag for macos (Alex Chen)
 \&...and many more contributions to numerous to mention!
 .RE
 .IP \[bu] 2
-fs: Move with \f[C]--ignore-existing\f[R] will not delete skipped files
+fs: Move with \f[V]--ignore-existing\f[R] will not delete skipped files
 (Nathan Collins)
 .IP \[bu] 2
 hashsum
@@ -77532,7 +78129,7 @@ hashsum
 .IP \[bu] 2
 Treat hash values in sum file as case insensitive (Ivan Andreev)
 .IP \[bu] 2
-Don\[aq]t put \f[C]ERROR\f[R] or \f[C]UNSUPPORTED\f[R] in output (Ivan
+Don\[aq]t put \f[V]ERROR\f[R] or \f[V]UNSUPPORTED\f[R] in output (Ivan
 Andreev)
 .RE
 .IP \[bu] 2
@@ -77549,19 +78146,19 @@ lib/kv: Add key-value database api (Ivan Andreev)
 librclone
 .RS 2
 .IP \[bu] 2
-Add \f[C]RcloneFreeString\f[R] function (albertony)
+Add \f[V]RcloneFreeString\f[R] function (albertony)
 .IP \[bu] 2
 Free strings in python example (albertony)
 .RE
 .IP \[bu] 2
 log: Optionally print pid in logs (Ivan Andreev)
 .IP \[bu] 2
-ls: Introduce \f[C]--human-readable\f[R] global option to print
+ls: Introduce \f[V]--human-readable\f[R] global option to print
 human-readable sizes (albertony)
 .IP \[bu] 2
-ncdu: Introduce key \f[C]u\f[R] to toggle human-readable (albertony)
+ncdu: Introduce key \f[V]u\f[R] to toggle human-readable (albertony)
 .IP \[bu] 2
-operations: Add \f[C]rmdirs -v\f[R] output (Justin Winokur)
+operations: Add \f[V]rmdirs -v\f[R] output (Justin Winokur)
 .IP \[bu] 2
 serve sftp
 .RS 2
@@ -77582,7 +78179,7 @@ Build docker plugin for multiple platforms (Thomas Stachl)
 size: Include human-readable count (albertony)
 .IP \[bu] 2
 touch: Add support for touching files in directory, with recursive
-option, filtering and \f[C]--dry-run\f[R]/\f[C]-i\f[R] (albertony)
+option, filtering and \f[V]--dry-run\f[R]/\f[V]-i\f[R] (albertony)
 .IP \[bu] 2
 tree: Option to print human-readable sizes removed in favor of global
 option (albertony)
@@ -77623,7 +78220,7 @@ VFS
 .IP \[bu] 2
 Ensure names used in cache path are legal on current OS (albertony)
 .IP \[bu] 2
-Ignore \f[C]ECLOSED\f[R] when truncating file handles to fix
+Ignore \f[V]ECLOSED\f[R] when truncating file handles to fix
 intermittent bad file descriptor error (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -77637,16 +78234,16 @@ lib (albertony)
 Crypt
 .RS 2
 .IP \[bu] 2
-Return wrapped object even with \f[C]--crypt-no-data-encryption\f[R]
+Return wrapped object even with \f[V]--crypt-no-data-encryption\f[R]
 (Ivan Andreev)
 .IP \[bu] 2
-Fix uploads with \f[C]--crypt-no-data-encryption\f[R] (Nick Craig-Wood)
+Fix uploads with \f[V]--crypt-no-data-encryption\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Azure Blob
 .RS 2
 .IP \[bu] 2
-Add \f[C]--azureblob-no-head-object\f[R] (Tatsuya Noyori)
+Add \f[V]--azureblob-no-head-object\f[R] (Tatsuya Noyori)
 .RE
 .IP \[bu] 2
 Box
@@ -77657,16 +78254,16 @@ Craig-Wood)
 .IP \[bu] 2
 When doing cleanup delete as much as possible (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--box-list-chunk\f[R] to control listing chunk size (Nick
+Add \f[V]--box-list-chunk\f[R] to control listing chunk size (Nick
 Craig-Wood)
 .IP \[bu] 2
-Delete items in parallel in cleanup using \f[C]--checkers\f[R] threads
+Delete items in parallel in cleanup using \f[V]--checkers\f[R] threads
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--box-owned-by\f[R] to only show items owned by the login
+Add \f[V]--box-owned-by\f[R] to only show items owned by the login
 passed (Nick Craig-Wood)
 .IP \[bu] 2
-Retry \f[C]operation_blocked_temporary\f[R] errors (Nick Craig-Wood)
+Retry \f[V]operation_blocked_temporary\f[R] errors (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Chunker
@@ -77682,16 +78279,16 @@ Speed up directory listings by constraining the API listing using the
 current filters (fotile96, Ivan Andreev)
 .IP \[bu] 2
 Fix buffering for single request upload for files smaller than
-\f[C]--drive-upload-cutoff\f[R] (YenForYang)
+\f[V]--drive-upload-cutoff\f[R] (YenForYang)
 .IP \[bu] 2
-Add \f[C]-o config\f[R] option to \f[C]backend drives\f[R] to make
+Add \f[V]-o config\f[R] option to \f[V]backend drives\f[R] to make
 config for all shared drives (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Dropbox
 .RS 2
 .IP \[bu] 2
-Add \f[C]--dropbox-batch-commit-timeout\f[R] to control batch timeout
+Add \f[V]--dropbox-batch-commit-timeout\f[R] to control batch timeout
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -77728,16 +78325,16 @@ Shukla)
 Jottacloud
 .RS 2
 .IP \[bu] 2
-Implement \f[C]SetModTime\f[R] to support modtime-only changes
+Implement \f[V]SetModTime\f[R] to support modtime-only changes
 (albertony)
 .IP \[bu] 2
-Improved error handling with \f[C]SetModTime\f[R] and corrupt files in
+Improved error handling with \f[V]SetModTime\f[R] and corrupt files in
 general (albertony)
 .IP \[bu] 2
-Add support for \f[C]UserInfo\f[R] (\f[C]rclone config userinfo\f[R])
+Add support for \f[V]UserInfo\f[R] (\f[V]rclone config userinfo\f[R])
 feature (albertony)
 .IP \[bu] 2
-Return direct download link from \f[C]rclone link\f[R] command
+Return direct download link from \f[V]rclone link\f[R] command
 (albertony)
 .RE
 .IP \[bu] 2
@@ -77775,7 +78372,7 @@ Use a combination of SDK retries and rclone retries (Nick Craig-Wood)
 Fix IAM Role for Service Account not working and other auth problems
 (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]shared_credentials_file\f[R] auth after reverting incorrect fix
+Fix \f[V]shared_credentials_file\f[R] auth after reverting incorrect fix
 (Nick Craig-Wood)
 .IP \[bu] 2
 Fix corrupted on transfer: sizes differ 0 vs xxxx with Ceph (Nick
@@ -77838,9 +78435,9 @@ accounting: Fix maximum bwlimit by scaling scale max token bucket size
 .IP \[bu] 2
 rc: Fix speed does not update in core/stats (negative0)
 .IP \[bu] 2
-selfupdate: Fix \f[C]--quiet\f[R] option, not quite quiet (yedamo)
+selfupdate: Fix \f[V]--quiet\f[R] option, not quite quiet (yedamo)
 .IP \[bu] 2
-serve http: Fix \f[C]serve http\f[R] exiting directly after starting
+serve http: Fix \f[V]serve http\f[R] exiting directly after starting
 (Cnly)
 .IP \[bu] 2
 build
@@ -77855,7 +78452,7 @@ Update Go to 1.16 and NDK to 22b for android/any (x0b)
 Mount
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--daemon\f[R] mode (Ivan Andreev)
+Fix \f[V]--daemon\f[R] mode (Ivan Andreev)
 .RE
 .IP \[bu] 2
 VFS
@@ -77912,7 +78509,7 @@ SFTP
 .RS 2
 .IP \[bu] 2
 Remove spurious error message on
-\f[C]--sftp-disable-concurrent-reads\f[R] (Nick Craig-Wood)
+\f[V]--sftp-disable-concurrent-reads\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Sugarsync
@@ -77944,7 +78541,7 @@ checksum (https://rclone.org/commands/rclone_checksum/) to check files
 against a file of checksums (Ivan Andreev)
 .RS 2
 .IP \[bu] 2
-this is also available as \f[C]rclone md5sum -C\f[R] etc
+this is also available as \f[V]rclone md5sum -C\f[R] etc
 .RE
 .IP \[bu] 2
 config touch (https://rclone.org/commands/rclone_config_touch/): ensure
@@ -77958,9 +78555,9 @@ command to help debugging changenotify (Nick Craig-Wood)
 Deprecations
 .RS 2
 .IP \[bu] 2
-\f[C]dbhashsum\f[R]: Remove command deprecated a year ago (Ivan Andreev)
+\f[V]dbhashsum\f[R]: Remove command deprecated a year ago (Ivan Andreev)
 .IP \[bu] 2
-\f[C]cache\f[R]: Deprecate cache backend (Ivan Andreev)
+\f[V]cache\f[R]: Deprecate cache backend (Ivan Andreev)
 .RE
 .IP \[bu] 2
 New Features
@@ -77993,9 +78590,9 @@ Also supports Android and gomobile
 fs
 .RS 2
 .IP \[bu] 2
-Add \f[C]--disable-http2\f[R] for global http2 disable (Nick Craig-Wood)
+Add \f[V]--disable-http2\f[R] for global http2 disable (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]--dump\f[R] imply \f[C]-vv\f[R] (Alex Chen)
+Make \f[V]--dump\f[R] imply \f[V]-vv\f[R] (Alex Chen)
 .IP \[bu] 2
 Use binary prefixes for size and rate units (albertony)
 .IP \[bu] 2
@@ -78037,7 +78634,7 @@ Delay load config file (albertony)
 Replace defaultConfig with a thread-safe in-memory implementation (Chris
 Macklin)
 .IP \[bu] 2
-Allow \f[C]config create\f[R] and friends to take \f[C]key=value\f[R]
+Allow \f[V]config create\f[R] and friends to take \f[V]key=value\f[R]
 parameters (Nick Craig-Wood)
 .IP \[bu] 2
 Fixed issues with flags/options set by environment vars.
@@ -78050,7 +78647,7 @@ lib/http - provides an abstraction for a central http server that
 services can bind routes to (Nolan Woods)
 .RS 2
 .IP \[bu] 2
-Add \f[C]--template\f[R] config and flags to serve/data (Nolan Woods)
+Add \f[V]--template\f[R] config and flags to serve/data (Nolan Woods)
 .IP \[bu] 2
 Add default 404 handler (Nolan Woods)
 .RE
@@ -78060,18 +78657,18 @@ link: Use \[dq]off\[dq] value for unset expiry (Nick Craig-Wood)
 oauthutil: Raise fatal error if token expired without refresh token
 (Alex Chen)
 .IP \[bu] 2
-rcat: Add \f[C]--size\f[R] flag for more efficient uploads of known size
+rcat: Add \f[V]--size\f[R] flag for more efficient uploads of known size
 (Nazar Mishturak)
 .IP \[bu] 2
-serve sftp: Add \f[C]--stdio\f[R] flag to serve via stdio (Tom)
+serve sftp: Add \f[V]--stdio\f[R] flag to serve via stdio (Tom)
 .IP \[bu] 2
-sync: Don\[aq]t warn about \f[C]--no-traverse\f[R] when
-\f[C]--files-from\f[R] is set (Nick Gaya)
+sync: Don\[aq]t warn about \f[V]--no-traverse\f[R] when
+\f[V]--files-from\f[R] is set (Nick Gaya)
 .IP \[bu] 2
-\f[C]test makefiles\f[R]
+\f[V]test makefiles\f[R]
 .RS 2
 .IP \[bu] 2
-Add \f[C]--seed\f[R] flag and make data generated repeatable (Nick
+Add \f[V]--seed\f[R] flag and make data generated repeatable (Nick
 Craig-Wood)
 .IP \[bu] 2
 Add log levels and speed summary (Nick Craig-Wood)
@@ -78101,7 +78698,7 @@ ncdu: Update termbox-go library to fix crash (Nick Craig-Wood)
 oauthutil: Fix old authorize result not recognised (Cnly)
 .IP \[bu] 2
 operations: Don\[aq]t update timestamps of files in
-\f[C]--compare-dest\f[R] (Nick Gaya)
+\f[V]--compare-dest\f[R] (Nick Gaya)
 .IP \[bu] 2
 selfupdate: fix archive name on macos (Ivan Andreev)
 .RE
@@ -78115,7 +78712,7 @@ Refactor before adding serve docker (Antoine GIRARD)
 VFS
 .RS 2
 .IP \[bu] 2
-Add cache reset for \f[C]--vfs-cache-max-size\f[R] handling at cache
+Add cache reset for \f[V]--vfs-cache-max-size\f[R] handling at cache
 poll interval (Leo Luan)
 .IP \[bu] 2
 Fix modtime changing when reading file into cache (Nick Craig-Wood)
@@ -78134,8 +78731,8 @@ Local
 Always use readlink to read symlink size for better compatibility (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--local-unicode-normalization\f[R] (and remove
-\f[C]--local-no-unicode-normalization\f[R]) (Nick Craig-Wood)
+Add \f[V]--local-unicode-normalization\f[R] (and remove
+\f[V]--local-no-unicode-normalization\f[R]) (Nick Craig-Wood)
 .IP \[bu] 2
 Skip entries removed concurrently with List() (Ivan Andreev)
 .RE
@@ -78143,7 +78740,7 @@ Skip entries removed concurrently with List() (Ivan Andreev)
 Crypt
 .RS 2
 .IP \[bu] 2
-Support timestamped filenames from \f[C]--b2-versions\f[R] (Dominik
+Support timestamped filenames from \f[V]--b2-versions\f[R] (Dominik
 Mydlil)
 .RE
 .IP \[bu] 2
@@ -78178,7 +78775,7 @@ Fix some google docs being treated as files (Nick Craig-Wood)
 Dropbox
 .RS 2
 .IP \[bu] 2
-Add \f[C]--dropbox-batch-mode\f[R] flag to speed up uploading (Nick
+Add \f[V]--dropbox-batch-mode\f[R] flag to speed up uploading (Nick
 Craig-Wood)
 .RS 2
 .IP \[bu] 2
@@ -78186,7 +78783,7 @@ Read the batch mode (https://rclone.org/dropbox/#batch-mode) docs for
 more info
 .RE
 .IP \[bu] 2
-Set visibility in link sharing when \f[C]--expire\f[R] is set (Nick
+Set visibility in link sharing when \f[V]--expire\f[R] is set (Nick
 Craig-Wood)
 .IP \[bu] 2
 Simplify chunked uploads (Alexey Ivanov)
@@ -78258,7 +78855,7 @@ Add no versions option (buengese)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Add \f[C]list_chunk option\f[R] (Nick Gaya)
+Add \f[V]list_chunk option\f[R] (Nick Gaya)
 .IP \[bu] 2
 Also report root error if unable to cancel multipart upload (Cnly)
 .IP \[bu] 2
@@ -78270,7 +78867,7 @@ Make link return direct download link (Xuanchen Wu)
 S3
 .RS 2
 .IP \[bu] 2
-Add \f[C]--s3-no-head-object\f[R] (Tatsuya Noyori)
+Add \f[V]--s3-no-head-object\f[R] (Tatsuya Noyori)
 .IP \[bu] 2
 Remove WebIdentityRoleProvider to fix crash on auth (Nick Craig-Wood)
 .IP \[bu] 2
@@ -78289,7 +78886,7 @@ Fix performance regression by re-enabling concurrent writes (Nick
 Craig-Wood)
 .IP \[bu] 2
 Expand tilde and environment variables in configured
-\f[C]known_hosts_file\f[R] (albertony)
+\f[V]known_hosts_file\f[R] (albertony)
 .RE
 .IP \[bu] 2
 Tardigrade
@@ -78299,7 +78896,7 @@ Upgrade to uplink v1.4.6 (Caleb Case)
 .IP \[bu] 2
 Use negative offset (Caleb Case)
 .IP \[bu] 2
-Add warning about \f[C]too many open files\f[R] (acsfer)
+Add warning about \f[V]too many open files\f[R] (acsfer)
 .RE
 .IP \[bu] 2
 WebDAV
@@ -78419,7 +79016,7 @@ Andreev)
 .RS 2
 .IP \[bu] 2
 Allows rclone to update itself in-place or via a package (using
-\f[C]--package\f[R] flag)
+\f[V]--package\f[R] flag)
 .IP \[bu] 2
 Reads cryptographically signed signatures for non beta releases
 .IP \[bu] 2
@@ -78430,13 +79027,13 @@ test (https://rclone.org/commands/rclone_test/) - these are test
 commands - use with care!
 .RS 2
 .IP \[bu] 2
-\f[C]histogram\f[R] - Makes a histogram of file name characters.
+\f[V]histogram\f[R] - Makes a histogram of file name characters.
 .IP \[bu] 2
-\f[C]info\f[R] - Discovers file name or other limitations for paths.
+\f[V]info\f[R] - Discovers file name or other limitations for paths.
 .IP \[bu] 2
-\f[C]makefiles\f[R] - Make a random file hierarchy for testing.
+\f[V]makefiles\f[R] - Make a random file hierarchy for testing.
 .IP \[bu] 2
-\f[C]memory\f[R] - Load all the objects at remote:path into memory and
+\f[V]memory\f[R] - Load all the objects at remote:path into memory and
 report memory stats.
 .RE
 .RE
@@ -78450,8 +79047,8 @@ Connection strings (https://rclone.org/docs/#connection-strings)
 Config parameters can now be passed as part of the remote name as a
 connection string.
 .IP \[bu] 2
-For example, to do the equivalent of \f[C]--drive-shared-with-me\f[R]
-use \f[C]drive,shared_with_me:\f[R]
+For example, to do the equivalent of \f[V]--drive-shared-with-me\f[R]
+use \f[V]drive,shared_with_me:\f[R]
 .IP \[bu] 2
 Make sure we don\[aq]t save on the fly remote config to the config file
 (Nick Craig-Wood)
@@ -78481,7 +79078,7 @@ Make a macOS ARM64 build to support Apple Silicon (Nick Craig-Wood)
 .IP \[bu] 2
 Install macfuse 4.x instead of osxfuse 3.x (Nick Craig-Wood)
 .IP \[bu] 2
-Use \f[C]GO386=softfloat\f[R] instead of deprecated \f[C]GO386=387\f[R]
+Use \f[V]GO386=softfloat\f[R] instead of deprecated \f[V]GO386=387\f[R]
 for 386 builds (Nick Craig-Wood)
 .IP \[bu] 2
 Disable IOS builds for the time being (Nick Craig-Wood)
@@ -78502,7 +79099,7 @@ Wrap config library in an interface (Fionera)
 .IP \[bu] 2
 Make config file system pluggable (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]--config \[dq]\[dq]\f[R] or \f[C]\[dq]/notfound\[dq]\f[R] for in
+\f[V]--config \[dq]\[dq]\f[R] or \f[V]\[dq]/notfound\[dq]\f[R] for in
 memory config only (Nick Craig-Wood)
 .IP \[bu] 2
 Clear fs cache of stale entries when altering config (Nick Craig-Wood)
@@ -78510,20 +79107,20 @@ Clear fs cache of stale entries when altering config (Nick Craig-Wood)
 .IP \[bu] 2
 copyurl: Add option to print resulting auto-filename (albertony)
 .IP \[bu] 2
-delete: Make \f[C]--rmdirs\f[R] obey the filters (Nick Craig-Wood)
+delete: Make \f[V]--rmdirs\f[R] obey the filters (Nick Craig-Wood)
 .IP \[bu] 2
 docs - many fixes and reworks from edwardxml, albertony, pvalls, Ivan
 Andreev, Evan Harris, buengese, Alexey Tabakman
 .IP \[bu] 2
 encoder/filename - add SCSU as tables (Klaus Post)
 .IP \[bu] 2
-Add multiple paths support to \f[C]--compare-dest\f[R] and
-\f[C]--copy-dest\f[R] flag (K265)
+Add multiple paths support to \f[V]--compare-dest\f[R] and
+\f[V]--copy-dest\f[R] flag (K265)
 .IP \[bu] 2
-filter: Make \f[C]--exclude \[dq]dir/\[dq]\f[R] equivalent to
-\f[C]--exclude \[dq]dir/**\[dq]\f[R] (Nick Craig-Wood)
+filter: Make \f[V]--exclude \[dq]dir/\[dq]\f[R] equivalent to
+\f[V]--exclude \[dq]dir/**\[dq]\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-fshttp: Add DSCP support with \f[C]--dscp\f[R] for QoS with
+fshttp: Add DSCP support with \f[V]--dscp\f[R] for QoS with
 differentiated services (Max Sum)
 .IP \[bu] 2
 lib/cache: Add Delete and DeletePrefix methods (Nick Craig-Wood)
@@ -78548,29 +79145,29 @@ rc
 Add string alternatives for setting options over the rc (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]options/local\f[R] to see the options configured in the context
+Add \f[V]options/local\f[R] to see the options configured in the context
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]_config\f[R] parameter to set global config for just this rc
+Add \f[V]_config\f[R] parameter to set global config for just this rc
 call (Nick Craig-Wood)
 .IP \[bu] 2
-Implement passing filter config with \f[C]_filter\f[R] parameter (Nick
+Implement passing filter config with \f[V]_filter\f[R] parameter (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]fscache/clear\f[R] and \f[C]fscache/entries\f[R] to control the
+Add \f[V]fscache/clear\f[R] and \f[V]fscache/entries\f[R] to control the
 fs cache (Nick Craig-Wood)
 .IP \[bu] 2
-Avoid +Inf value for speed in \f[C]core/stats\f[R] (albertony)
+Avoid +Inf value for speed in \f[V]core/stats\f[R] (albertony)
 .IP \[bu] 2
-Add a full set of stats to \f[C]core/stats\f[R] (Nick Craig-Wood)
+Add a full set of stats to \f[V]core/stats\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Allow \f[C]fs=\f[R] params to be a JSON blob (Nick Craig-Wood)
+Allow \f[V]fs=\f[R] params to be a JSON blob (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-rcd: Added systemd notification during the \f[C]rclone rcd\f[R] command.
+rcd: Added systemd notification during the \f[V]rclone rcd\f[R] command.
 (Naveen Honest Raj)
 .IP \[bu] 2
-rmdirs: Make \f[C]--rmdirs\f[R] obey the filters (Nick Craig-Wood)
+rmdirs: Make \f[V]--rmdirs\f[R] obey the filters (Nick Craig-Wood)
 .IP \[bu] 2
 version: Show build tags and type of executable (Ivan Andreev)
 .RE
@@ -78580,10 +79177,10 @@ Bug Fixes
 .IP \[bu] 2
 install.sh: make it fail on download errors (Ivan Andreev)
 .IP \[bu] 2
-Fix excessive retries missing \f[C]--max-duration\f[R] timeout (Nick
+Fix excessive retries missing \f[V]--max-duration\f[R] timeout (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix crash when \f[C]--low-level-retries=0\f[R] (Nick Craig-Wood)
+Fix crash when \f[V]--low-level-retries=0\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix failed token refresh on mounts created via the rc (Nick Craig-Wood)
 .IP \[bu] 2
@@ -78626,7 +79223,7 @@ Craig-Wood)
 VFS
 .RS 2
 .IP \[bu] 2
-\f[C]--vfs-used-is-size\f[R] to report used space using recursive scan
+\f[V]--vfs-used-is-size\f[R] to report used space using recursive scan
 (tYYGH)
 .IP \[bu] 2
 Don\[aq]t set modification time if it was already correct (Nick
@@ -78640,7 +79237,7 @@ Fix modtimes not updating when writing via cache (Nick Craig-Wood)
 Fix modtimes changing by fractional seconds after upload (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix modtime set if \f[C]--vfs-cache-mode writes\f[R]/\f[C]full\f[R] and
+Fix modtime set if \f[V]--vfs-cache-mode writes\f[R]/\f[V]full\f[R] and
 no write (Nick Craig-Wood)
 .IP \[bu] 2
 Rename files in cache and cancel uploads on directory rename (Nick
@@ -78653,9 +79250,9 @@ Craig-Wood)
 Local
 .RS 2
 .IP \[bu] 2
-Add flag \f[C]--local-no-preallocate\f[R] (David Sze)
+Add flag \f[V]--local-no-preallocate\f[R] (David Sze)
 .IP \[bu] 2
-Make \f[C]nounc\f[R] an advanced option except on Windows (albertony)
+Make \f[V]nounc\f[R] an advanced option except on Windows (albertony)
 .IP \[bu] 2
 Don\[aq]t ignore preallocate disk full errors (Nick Craig-Wood)
 .RE
@@ -78663,7 +79260,7 @@ Don\[aq]t ignore preallocate disk full errors (Nick Craig-Wood)
 Cache
 .RS 2
 .IP \[bu] 2
-Add \f[C]--fs-cache-expire-duration\f[R] to control the fs cache (Nick
+Add \f[V]--fs-cache-expire-duration\f[R] to control the fs cache (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -78716,7 +79313,7 @@ Dropbox
 .IP \[bu] 2
 Add polling for changes support (Robert Thomas)
 .IP \[bu] 2
-Make \f[C]--timeout 0\f[R] work properly (Nick Craig-Wood)
+Make \f[V]--timeout 0\f[R] work properly (Nick Craig-Wood)
 .IP \[bu] 2
 Raise priority of rate limited message to INFO to make it more
 noticeable (Nick Craig-Wood)
@@ -78735,12 +79332,12 @@ FTP
 .IP \[bu] 2
 Implement Shutdown method (Nick Craig-Wood)
 .IP \[bu] 2
-Close idle connections after \f[C]--ftp-idle-timeout\f[R] (1m by
+Close idle connections after \f[V]--ftp-idle-timeout\f[R] (1m by
 default) (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]--timeout 0\f[R] work properly (Nick Craig-Wood)
+Make \f[V]--timeout 0\f[R] work properly (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--ftp-close-timeout\f[R] flag for use with awkward ftp servers
+Add \f[V]--ftp-close-timeout\f[R] flag for use with awkward ftp servers
 (Nick Craig-Wood)
 .IP \[bu] 2
 Retry connections and logins on 421 errors (Nick Craig-Wood)
@@ -78755,26 +79352,26 @@ Fix permissions for when directory is created (Lucas Messenger)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Make \f[C]--timeout 0\f[R] work properly (Nick Craig-Wood)
+Make \f[V]--timeout 0\f[R] work properly (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 S3
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--s3-profile\f[R] which wasn\[aq]t working (Nick Craig-Wood)
+Fix \f[V]--s3-profile\f[R] which wasn\[aq]t working (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 SFTP
 .RS 2
 .IP \[bu] 2
-Close idle connections after \f[C]--sftp-idle-timeout\f[R] (1m by
+Close idle connections after \f[V]--sftp-idle-timeout\f[R] (1m by
 default) (Nick Craig-Wood)
 .IP \[bu] 2
 Fix \[dq]file not found\[dq] errors for read once servers (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix SetModTime stat failed: object not found with
-\f[C]--sftp-set-modtime=false\f[R] (Nick Craig-Wood)
+\f[V]--sftp-set-modtime=false\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Swift
@@ -78818,13 +79415,13 @@ Check that purged directory really exists (Ivan Andreev)
 Yandex
 .RS 2
 .IP \[bu] 2
-Make \f[C]--timeout 0\f[R] work properly (Nick Craig-Wood)
+Make \f[V]--timeout 0\f[R] work properly (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Zoho
 .RS 2
 .IP \[bu] 2
-Replace client id - you will need to \f[C]rclone config reconnect\f[R]
+Replace client id - you will need to \f[V]rclone config reconnect\f[R]
 after this (buengese)
 .IP \[bu] 2
 Add forgotten setupRegion() to NewFs - this finally fixes regions other
@@ -78960,7 +79557,7 @@ This will enable passing of global config via the rc
 This work was sponsored by Digitalis (https://digitalis.io/)
 .RE
 .IP \[bu] 2
-Add \f[C]--bwlimit\f[R] for upload and download (Nick Craig-Wood)
+Add \f[V]--bwlimit\f[R] for upload and download (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
 Obey bwlimit in http Transport for better limiting
@@ -78976,10 +79573,10 @@ Don\[aq]t compile systemd log integration for non unix systems (Benjamin
 Gustin)
 .RE
 .IP \[bu] 2
-Add a \f[C]--download\f[R] flag to md5sum/sha1sum/hashsum to force
+Add a \f[V]--download\f[R] flag to md5sum/sha1sum/hashsum to force
 rclone to download and hash files locally (lostheli)
 .IP \[bu] 2
-Add \f[C]--progress-terminal-title\f[R] to print ETA to terminal title
+Add \f[V]--progress-terminal-title\f[R] to print ETA to terminal title
 (LaSombra)
 .IP \[bu] 2
 Make backend env vars show in help as the defaults for backend flags
@@ -78994,10 +79591,10 @@ Raise minimum go version to go1.12 (Nick Craig-Wood)
 dedupe
 .RS 2
 .IP \[bu] 2
-Add \f[C]--by-hash\f[R] to dedupe on content hash not file name (Nick
+Add \f[V]--by-hash\f[R] to dedupe on content hash not file name (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--dedupe-mode list\f[R] to just list dupes, changing nothing
+Add \f[V]--dedupe-mode list\f[R] to just list dupes, changing nothing
 (Nick Craig-Wood)
 .IP \[bu] 2
 Add warning if used on a remote which can\[aq]t have duplicate names
@@ -79009,14 +79606,14 @@ fs
 .IP \[bu] 2
 Add Shutdown optional method for backends (Nick Craig-Wood)
 .IP \[bu] 2
-When using \f[C]--files-from\f[R] check files concurrently (zhucan)
+When using \f[V]--files-from\f[R] check files concurrently (zhucan)
 .IP \[bu] 2
-Accumulate stats when using \f[C]--dry-run\f[R] (Ingo Weiss)
+Accumulate stats when using \f[V]--dry-run\f[R] (Ingo Weiss)
 .IP \[bu] 2
-Always show stats when using \f[C]--dry-run\f[R] or
-\f[C]--interactive\f[R] (Nick Craig-Wood)
+Always show stats when using \f[V]--dry-run\f[R] or
+\f[V]--interactive\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Add support for flag \f[C]--no-console\f[R] on windows to hide the
+Add support for flag \f[V]--no-console\f[R] on windows to hide the
 console window (albertony)
 .RE
 .IP \[bu] 2
@@ -79027,18 +79624,18 @@ ncdu
 .IP \[bu] 2
 Highlight read errors instead of aborting (Claudio Bantaloukas)
 .IP \[bu] 2
-Add sort by average size in directory (Adam Pl\['a]nsk\['y])
+Add sort by average size in directory (Adam Plánský)
 .IP \[bu] 2
 Add toggle option for average s3ize in directory - key \[aq]a\[aq] (Adam
-Pl\['a]nsk\['y])
+Plánský)
 .IP \[bu] 2
-Add empty folder flag into ncdu browser (Adam Pl\['a]nsk\['y])
+Add empty folder flag into ncdu browser (Adam Plánský)
 .IP \[bu] 2
-Add \f[C]!\f[R] (error) and \f[C].\f[R] (unreadable) file flags to go
-with \f[C]e\f[R] (empty) (Nick Craig-Wood)
+Add \f[V]!\f[R] (error) and \f[V].\f[R] (unreadable) file flags to go
+with \f[V]e\f[R] (empty) (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-obscure: Make \f[C]rclone obscure -\f[R] ignore newline at end of line
+obscure: Make \f[V]rclone obscure -\f[R] ignore newline at end of line
 (Nick Craig-Wood)
 .IP \[bu] 2
 operations
@@ -79047,7 +79644,7 @@ operations
 Add logs when need to upload files to set mod times (Nick Craig-Wood)
 .IP \[bu] 2
 Move and copy log name of the destination object in verbose (Adam
-Pl\['a]nsk\['y])
+Plánský)
 .IP \[bu] 2
 Add size if known to skipped items and JSON log (Nick Craig-Wood)
 .RE
@@ -79096,7 +79693,7 @@ Fix parsing of ..
 when joining remotes (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-log: Fix enabling systemd logging when using \f[C]--log-file\f[R] (Nick
+log: Fix enabling systemd logging when using \f[V]--log-file\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 check
@@ -79111,19 +79708,19 @@ move: Fix data loss when source and destination are the same object
 operations
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--cutoff-mode\f[R] hard not cutting off immediately (Nick
+Fix \f[V]--cutoff-mode\f[R] hard not cutting off immediately (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--immutable\f[R] error message (Nick Craig-Wood)
+Fix \f[V]--immutable\f[R] error message (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 sync
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--cutoff-mode\f[R] soft & cautious so it doesn\[aq]t end the
+Fix \f[V]--cutoff-mode\f[R] soft & cautious so it doesn\[aq]t end the
 transfer early (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--immutable\f[R] errors retrying many times (Nick Craig-Wood)
+Fix \f[V]--immutable\f[R] errors retrying many times (Nick Craig-Wood)
 .RE
 .RE
 .IP \[bu] 2
@@ -79146,7 +79743,7 @@ CokeMine, David, Dov Murik, Durval Menezes, Evan Harris, gtorelly
 .IP \[bu] 2
 Ilyess Bachiri, Janne Johansson, Kerry Su, Marcin Zelent,
 .IP \[bu] 2
-Martin Michlmayr, Milly, S\[u01A1]n Tr\[u1EA7]n-Nguy\[u1EC5]n
+Martin Michlmayr, Milly, Sơn Trần-Nguyễn
 .RE
 .RE
 .IP \[bu] 2
@@ -79158,7 +79755,7 @@ Update systemd status with cache stats (Hekmon)
 Disable bazil/fuse based mount on macOS (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-Make \f[C]rclone mount\f[R] actually run \f[C]rclone cmount\f[R] under
+Make \f[V]rclone mount\f[R] actually run \f[V]rclone cmount\f[R] under
 macOS (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -79184,8 +79781,8 @@ Craig-Wood)
 Fix \[dq]file already exists\[dq] error for stale cache files (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix file leaks with \f[C]--vfs-cache-mode\f[R] full and
-\f[C]--buffer-size 0\f[R] (Nick Craig-Wood)
+Fix file leaks with \f[V]--vfs-cache-mode\f[R] full and
+\f[V]--buffer-size 0\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix invalid cache path on windows when using :backend: as remote
 (albertony)
@@ -79197,7 +79794,7 @@ Local
 Continue listing files/folders when a circular symlink is detected
 (Manish Gupta)
 .IP \[bu] 2
-New flag \f[C]--local-zero-size-links\f[R] to fix sync on some virtual
+New flag \f[V]--local-zero-size-links\f[R] to fix sync on some virtual
 filesystems (Riccardo Iaconelli)
 .RE
 .IP \[bu] 2
@@ -79218,7 +79815,7 @@ Fix setting of mime types (Nick Craig-Wood)
 Fix crash when listing outside a SAS URL\[aq]s root (Nick Craig-Wood)
 .IP \[bu] 2
 Delete archive tier blobs before update if
-\f[C]--azureblob-archive-tier-delete\f[R] (Nick Craig-Wood)
+\f[V]--azureblob-archive-tier-delete\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix crash on startup (Nick Craig-Wood)
 .IP \[bu] 2
@@ -79234,7 +79831,7 @@ B2
 Make NewObject use less expensive API calls (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-This will improve \f[C]--files-from\f[R] and \f[C]restic serve\f[R] in
+This will improve \f[V]--files-from\f[R] and \f[V]restic serve\f[R] in
 particular
 .RE
 .IP \[bu] 2
@@ -79263,10 +79860,10 @@ Fix case-insensitive NewObject, test metadata detection (Ivan Andreev)
 Drive
 .RS 2
 .IP \[bu] 2
-Implement \f[C]rclone backend copyid\f[R] command for copying files by
+Implement \f[V]rclone backend copyid\f[R] command for copying files by
 ID (Nick Craig-Wood)
 .IP \[bu] 2
-Added flag \f[C]--drive-stop-on-download-limit\f[R] to stop transfers
+Added flag \f[V]--drive-stop-on-download-limit\f[R] to stop transfers
 when the download limit is exceeded (Anagh Kumar Baranwal)
 .IP \[bu] 2
 Implement CleanUp workaround for team drives (buengese)
@@ -79285,7 +79882,7 @@ Add support for viewing shared files and folders (buengese)
 .IP \[bu] 2
 Enable short lived access tokens (Nick Craig-Wood)
 .IP \[bu] 2
-Implement IDer on Objects so \f[C]rclone lsf\f[R] etc can read the IDs
+Implement IDer on Objects so \f[V]rclone lsf\f[R] etc can read the IDs
 (buengese)
 .IP \[bu] 2
 Set Features ReadMimeType to false as Object.MimeType not supported
@@ -79307,10 +79904,10 @@ Craig-Wood)
 FTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--ftp-disable-msld\f[R] option to ignore MLSD for really old
+Add \f[V]--ftp-disable-msld\f[R] option to ignore MLSD for really old
 servers (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]--tpslimit apply\f[R] (Nick Craig-Wood)
+Make \f[V]--tpslimit apply\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Google Cloud Storage
@@ -79321,14 +79918,14 @@ Storage class object header support (Laurens Janssen)
 Fix anonymous client to use rclone\[aq]s HTTP client (Nick Craig-Wood)
 .IP \[bu] 2
 Fix
-\f[C]Entry doesn\[aq]t belong in directory \[dq]\[dq] (same as directory) - ignoring\f[R]
+\f[V]Entry doesn\[aq]t belong in directory \[dq]\[dq] (same as directory) - ignoring\f[R]
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Googlephotos
 .RS 2
 .IP \[bu] 2
-New flag \f[C]--gphotos-include-archived\f[R] to show archived photos as
+New flag \f[V]--gphotos-include-archived\f[R] to show archived photos as
 well (Nicolas Rueff)
 .RE
 .IP \[bu] 2
@@ -79337,7 +79934,7 @@ Jottacloud
 .IP \[bu] 2
 Don\[aq]t erroneously report support for writing mime types (buengese)
 .IP \[bu] 2
-Add support for Telia Cloud (Patrik Nordl\['e]n)
+Add support for Telia Cloud (Patrik Nordlén)
 .RE
 .IP \[bu] 2
 Mailru
@@ -79414,7 +80011,7 @@ Fix rclone cleanup (Nick Craig-Wood)
 S3
 .RS 2
 .IP \[bu] 2
-Added \f[C]--s3-disable-http2\f[R] to disable http/2 (Anagh Kumar
+Added \f[V]--s3-disable-http2\f[R] to disable http/2 (Anagh Kumar
 Baranwal)
 .IP \[bu] 2
 Complete SSE-C implementation (Nick Craig-Wood)
@@ -79426,7 +80023,7 @@ Add MD5 metadata to objects uploaded with SSE-AWS/SSE-C (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
-Add \f[C]--s3-no-head parameter\f[R] to minimise transactions on upload
+Add \f[V]--s3-no-head parameter\f[R] to minimise transactions on upload
 (Nick Craig-Wood)
 .IP \[bu] 2
 Update docs with a Reducing Costs section (Nick Craig-Wood)
@@ -79457,9 +80054,9 @@ Implement Shutdown method (Nick Craig-Wood)
 .IP \[bu] 2
 Implement keyboard interactive authentication (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]--tpslimit\f[R] apply (Nick Craig-Wood)
+Make \f[V]--tpslimit\f[R] apply (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--sftp-use-fstat\f[R] for unusual SFTP servers (Nick
+Implement \f[V]--sftp-use-fstat\f[R] for unusual SFTP servers (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -79474,12 +80071,10 @@ Fix finding directories in a case insensitive way (Nick Craig-Wood)
 Swift
 .RS 2
 .IP \[bu] 2
-Fix deletion of parts of Static Large Object (SLO) (Nguy\[u1EC5]n
-H\[u1EEF]u Lu\[^a]n)
+Fix deletion of parts of Static Large Object (SLO) (Nguyễn Hữu Luân)
 .IP \[bu] 2
 Ensure partially uploaded large files are uploaded unless
-\f[C]--swift-leave-parts-on-error\f[R] (Nguy\[u1EC5]n H\[u1EEF]u
-Lu\[^a]n)
+\f[V]--swift-leave-parts-on-error\f[R] (Nguyễn Hữu Luân)
 .RE
 .IP \[bu] 2
 Tardigrade
@@ -79556,7 +80151,7 @@ Craig-Wood)
 Mount
 .RS 2
 .IP \[bu] 2
-Add optional \f[C]brew\f[R] tag to throw an error when using mount in
+Add optional \f[V]brew\f[R] tag to throw an error when using mount in
 the binaries installed via Homebrew (Anagh Kumar Baranwal)
 .IP \[bu] 2
 Add \[dq].\[dq] and \[dq]..\[dq] to directories to match cmount and
@@ -79621,7 +80216,7 @@ random: Fix incorrect use of math/rand instead of crypto/rand
 CVE-2020-28924 (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-Passwords you have generated with \f[C]rclone config\f[R] may be
+Passwords you have generated with \f[V]rclone config\f[R] may be
 insecure
 .IP \[bu] 2
 See issue #4783 (https://github.com/rclone/rclone/issues/4783) for more
@@ -79869,7 +80464,7 @@ flag to limit speeds of individual file transfers (Nick Craig-Wood)
 Transfers are sorted by start time in the stats and progress output (Max
 Sum)
 .IP \[bu] 2
-Make sure backends expand \f[C]\[ti]\f[R] and environment vars in file
+Make sure backends expand \f[V]\[ti]\f[R] and environment vars in file
 names they use (Nick Craig-Wood)
 .IP \[bu] 2
 Add --refresh-times (https://rclone.org/docs/#refresh-times) flag to set
@@ -79887,7 +80482,7 @@ Craig-Wood)
 .IP \[bu] 2
 Add ARMv7 to the supported builds (Nick Craig-Wood)
 .IP \[bu] 2
-Enable \f[C]rclone cmount\f[R] on macOS (Nick Craig-Wood)
+Enable \f[V]rclone cmount\f[R] on macOS (Nick Craig-Wood)
 .IP \[bu] 2
 Make rclone build with gccgo (Nick Craig-Wood)
 .IP \[bu] 2
@@ -79912,37 +80507,37 @@ Allow installation and use of plugins and test plugins with rclone-webui
 Add reverse proxy pluginsHandler for serving plugins (Chaitanya
 Bankanhal)
 .IP \[bu] 2
-Add \f[C]mount/listmounts\f[R] option for listing current mounts
+Add \f[V]mount/listmounts\f[R] option for listing current mounts
 (Chaitanya Bankanhal)
 .IP \[bu] 2
-Add \f[C]operations/uploadfile\f[R] to upload a file through rc using
+Add \f[V]operations/uploadfile\f[R] to upload a file through rc using
 encoding multipart/form-data (Chaitanya Bankanhal)
 .IP \[bu] 2
-Add \f[C]core/command\f[R] to execute rclone terminal commands.
+Add \f[V]core/command\f[R] to execute rclone terminal commands.
 (Chaitanya Bankanhal)
 .RE
 .IP \[bu] 2
-\f[C]rclone check\f[R]
+\f[V]rclone check\f[R]
 .RS 2
 .IP \[bu] 2
 Add reporting of filenames for same/missing/changed (Nick Craig-Wood)
 .IP \[bu] 2
 Make check command obey
-\f[C]--dry-run\f[R]/\f[C]-i\f[R]/\f[C]--interactive\f[R] (Nick
+\f[V]--dry-run\f[R]/\f[V]-i\f[R]/\f[V]--interactive\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Make check do \f[C]--checkers\f[R] files concurrently (Nick Craig-Wood)
+Make check do \f[V]--checkers\f[R] files concurrently (Nick Craig-Wood)
 .IP \[bu] 2
-Retry downloads if they fail when using the \f[C]--download\f[R] flag
+Retry downloads if they fail when using the \f[V]--download\f[R] flag
 (Nick Craig-Wood)
 .IP \[bu] 2
 Make it show stats by default (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-\f[C]rclone obscure\f[R]: Allow obscure command to accept password on
+\f[V]rclone obscure\f[R]: Allow obscure command to accept password on
 STDIN (David Ibarra)
 .IP \[bu] 2
-\f[C]rclone config\f[R]
+\f[V]rclone config\f[R]
 .RS 2
 .IP \[bu] 2
 Set RCLONE_CONFIG_DIR for use in config files and subprocesses (Nick
@@ -79952,22 +80547,22 @@ Reject remote names starting with a dash.
 (jtagcat)
 .RE
 .IP \[bu] 2
-\f[C]rclone cryptcheck\f[R]: Add reporting of filenames for
+\f[V]rclone cryptcheck\f[R]: Add reporting of filenames for
 same/missing/changed (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]rclone dedupe\f[R]: Make it obey the \f[C]--size-only\f[R] flag for
+\f[V]rclone dedupe\f[R]: Make it obey the \f[V]--size-only\f[R] flag for
 duplicate detection (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]rclone link\f[R]: Add \f[C]--expire\f[R] and \f[C]--unlink\f[R]
+\f[V]rclone link\f[R]: Add \f[V]--expire\f[R] and \f[V]--unlink\f[R]
 flags (Roman Kredentser)
 .IP \[bu] 2
-\f[C]rclone mkdir\f[R]: Warn when using mkdir on remotes which can\[aq]t
+\f[V]rclone mkdir\f[R]: Warn when using mkdir on remotes which can\[aq]t
 have empty directories (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]rclone rc\f[R]: Allow JSON parameters to simplify command line
+\f[V]rclone rc\f[R]: Allow JSON parameters to simplify command line
 usage (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]rclone serve ftp\f[R]
+\f[V]rclone serve ftp\f[R]
 .RS 2
 .IP \[bu] 2
 Don\[aq]t compile on < go1.13 after dependency update (Nick Craig-Wood)
@@ -79978,18 +80573,18 @@ Use refactored goftp.io/server library for binary shrink (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
-\f[C]rclone serve restic\f[R]: Expose interfaces so that rclone can be
+\f[V]rclone serve restic\f[R]: Expose interfaces so that rclone can be
 used as a library from within restic (Jack)
 .IP \[bu] 2
-\f[C]rclone sync\f[R]: Add \f[C]--track-renames-strategy leaf\f[R] (Nick
+\f[V]rclone sync\f[R]: Add \f[V]--track-renames-strategy leaf\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-\f[C]rclone touch\f[R]: Add ability to set nanosecond resolution times
+\f[V]rclone touch\f[R]: Add ability to set nanosecond resolution times
 (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]rclone tree\f[R]: Remove \f[C]-i\f[R] shorthand for
-\f[C]--noindent\f[R] as it conflicts with
-\f[C]-i\f[R]/\f[C]--interactive\f[R] (Nick Craig-Wood)
+\f[V]rclone tree\f[R]: Remove \f[V]-i\f[R] shorthand for
+\f[V]--noindent\f[R] as it conflicts with
+\f[V]-i\f[R]/\f[V]--interactive\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -79998,7 +80593,7 @@ Bug Fixes
 accounting
 .RS 2
 .IP \[bu] 2
-Fix documentation for \f[C]speed\f[R]/\f[C]speedAvg\f[R] (Nick
+Fix documentation for \f[V]speed\f[R]/\f[V]speedAvg\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix elapsed time not show actual time since beginning (Chaitanya
@@ -80013,10 +80608,10 @@ build
 Fix file handle leak in GitHub release tool (Garrett Squire)
 .RE
 .IP \[bu] 2
-\f[C]rclone check\f[R]: Fix successful retries with \f[C]--download\f[R]
+\f[V]rclone check\f[R]: Fix successful retries with \f[V]--download\f[R]
 counting errors (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]rclone dedupe\f[R]: Fix logging to be easier to understand (Nick
+\f[V]rclone dedupe\f[R]: Fix logging to be easier to understand (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -80026,8 +80621,8 @@ Mount
 Warn macOS users that mount implementation is changing (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-to test the new implementation use \f[C]rclone cmount\f[R] instead of
-\f[C]rclone mount\f[R]
+to test the new implementation use \f[V]rclone cmount\f[R] instead of
+\f[V]rclone mount\f[R]
 .IP \[bu] 2
 this is because the library rclone uses has dropped macOS support
 .RE
@@ -80037,12 +80632,12 @@ rc interface
 .IP \[bu] 2
 Add call for unmount all (Chaitanya Bankanhal)
 .IP \[bu] 2
-Make \f[C]mount/mount\f[R] remote control take vfsOpt option (Nick
+Make \f[V]mount/mount\f[R] remote control take vfsOpt option (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add mountOpt to \f[C]mount/mount\f[R] (Nick Craig-Wood)
+Add mountOpt to \f[V]mount/mount\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Add VFS and Mount options to \f[C]mount/listmounts\f[R] (Nick
+Add VFS and Mount options to \f[V]mount/listmounts\f[R] (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -80054,8 +80649,8 @@ Always supply stat information in Readdir (Nick Craig-Wood)
 Add support for reading unknown length files using direct IO (Windows)
 (Nick Craig-Wood)
 .IP \[bu] 2
-Fix On Windows don\[aq]t add \f[C]-o uid/gid=-1\f[R] if user supplies
-\f[C]-o uid/gid\f[R].
+Fix On Windows don\[aq]t add \f[V]-o uid/gid=-1\f[R] if user supplies
+\f[V]-o uid/gid\f[R].
 (Nick Craig-Wood)
 .IP \[bu] 2
 Fix macOS losing directory contents in cmount (Nick Craig-Wood)
@@ -80066,14 +80661,14 @@ Fix volume name broken in recent refactor (Nick Craig-Wood)
 VFS
 .RS 2
 .IP \[bu] 2
-Implement partial reads for \f[C]--vfs-cache-mode full\f[R] (Nick
+Implement partial reads for \f[V]--vfs-cache-mode full\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--vfs-writeback\f[R] option to delay writes back to cloud
+Add \f[V]--vfs-writeback\f[R] option to delay writes back to cloud
 storage (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--vfs-read-ahead\f[R] parameter for use with
-\f[C]--vfs-cache-mode full\f[R] (Nick Craig-Wood)
+Add \f[V]--vfs-read-ahead\f[R] parameter for use with
+\f[V]--vfs-cache-mode full\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Restart pending uploads on restart of the cache (Nick Craig-Wood)
 .IP \[bu] 2
@@ -80084,10 +80679,10 @@ Craig-Wood)
 .IP \[bu] 2
 Change modtime of file before upload to current (Rob Calistri)
 .IP \[bu] 2
-Recommend \f[C]--vfs-cache-modes writes\f[R] on backends which can\[aq]t
+Recommend \f[V]--vfs-cache-modes writes\f[R] on backends which can\[aq]t
 stream (Nick Craig-Wood)
 .IP \[bu] 2
-Add an optional \f[C]fs\f[R] parameter to vfs rc methods (Nick
+Add an optional \f[V]fs\f[R] parameter to vfs rc methods (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix errors when using > 260 char files in the cache in Windows (Nick
@@ -80098,22 +80693,22 @@ Fix renaming of items while they are being uploaded (Nick Craig-Wood)
 Fix very high load caused by slow directory listings (Nick Craig-Wood)
 .IP \[bu] 2
 Fix renamed files not being uploaded with
-\f[C]--vfs-cache-mode minimal\f[R] (Nick Craig-Wood)
+\f[V]--vfs-cache-mode minimal\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix directory locking caused by slow directory listings (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix saving from chrome without \f[C]--vfs-cache-mode writes\f[R] (Nick
+Fix saving from chrome without \f[V]--vfs-cache-mode writes\f[R] (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
 Local
 .RS 2
 .IP \[bu] 2
-Add \f[C]--local-no-updated\f[R] to provide a consistent view of
+Add \f[V]--local-no-updated\f[R] to provide a consistent view of
 changing objects (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--local-no-set-modtime\f[R] option to prevent modtime changes
+Add \f[V]--local-no-set-modtime\f[R] option to prevent modtime changes
 (tyhuber1)
 .IP \[bu] 2
 Fix race conditions updating and reading Object metadata (Nick
@@ -80131,7 +80726,7 @@ Fix dedupe on caches wrapping drives (Nick Craig-Wood)
 Crypt
 .RS 2
 .IP \[bu] 2
-Add \f[C]--crypt-server-side-across-configs\f[R] flag (Nick Craig-Wood)
+Add \f[V]--crypt-server-side-across-configs\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 Make any created backends be cached to fix rc problems (Nick Craig-Wood)
 .RE
@@ -80182,18 +80777,18 @@ Make any created backends be cached to fix rc problems (Nick Craig-Wood)
 Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]rclone backend drives\f[R] to list shared drives (teamdrives)
+Add \f[V]rclone backend drives\f[R] to list shared drives (teamdrives)
 (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]rclone backend untrash\f[R] (Nick Craig-Wood)
+Implement \f[V]rclone backend untrash\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Work around drive bug which didn\[aq]t set modtime of copied docs (Nick
 Craig-Wood)
 .IP \[bu] 2
-Added \f[C]--drive-starred-only\f[R] to only show starred files (Jay
+Added \f[V]--drive-starred-only\f[R] to only show starred files (Jay
 McEntire)
 .IP \[bu] 2
-Deprecate \f[C]--drive-alternate-export\f[R] as it is no longer needed
+Deprecate \f[V]--drive-alternate-export\f[R] as it is no longer needed
 (themylogin)
 .IP \[bu] 2
 Fix duplication of Google docs on server-side copy (Nick Craig-Wood)
@@ -80208,7 +80803,7 @@ Dropbox
 Add copyright detector info in limitations section in the docs (Alex
 Guerrero)
 .IP \[bu] 2
-Fix \f[C]rclone link\f[R] by removing expires parameter (Nick
+Fix \f[V]rclone link\f[R] by removing expires parameter (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -80224,7 +80819,7 @@ FTP
 .IP \[bu] 2
 Add explicit TLS support (Heiko Bornholdt)
 .IP \[bu] 2
-Add support for \f[C]--dump bodies\f[R] and \f[C]--dump auth\f[R] for
+Add support for \f[V]--dump bodies\f[R] and \f[V]--dump auth\f[R] for
 debugging (Nick Craig-Wood)
 .IP \[bu] 2
 Fix interoperation with pure-ftpd (Nick Craig-Wood)
@@ -80233,7 +80828,7 @@ Fix interoperation with pure-ftpd (Nick Craig-Wood)
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Add support for anonymous access (Kai L\[:u]ke)
+Add support for anonymous access (Kai Lüke)
 .RE
 .IP \[bu] 2
 Jottacloud
@@ -80253,14 +80848,14 @@ Rework cancel of multipart uploads on rclone exit (Nick Craig-Wood)
 .IP \[bu] 2
 Implement rclone cleanup (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--onedrive-no-versions\f[R] flag to remove old versions (Nick
+Add \f[V]--onedrive-no-versions\f[R] flag to remove old versions (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
 Pcloud
 .RS 2
 .IP \[bu] 2
-Implement \f[C]rclone link\f[R] for public link creation (buengese)
+Implement \f[V]rclone link\f[R] for public link creation (buengese)
 .RE
 .IP \[bu] 2
 Qingstor
@@ -80277,23 +80872,23 @@ Preserve metadata when doing multipart copy (Nick Craig-Wood)
 Cancel in progress multipart uploads and copies on rclone exit (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]rclone link\f[R] for public link sharing (Roman Kredentser)
+Add \f[V]rclone link\f[R] for public link sharing (Roman Kredentser)
 .IP \[bu] 2
-Add \f[C]rclone backend restore\f[R] command to restore objects from
+Add \f[V]rclone backend restore\f[R] command to restore objects from
 GLACIER (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]rclone cleanup\f[R] and \f[C]rclone backend cleanup\f[R] to
+Add \f[V]rclone cleanup\f[R] and \f[V]rclone backend cleanup\f[R] to
 clean unfinished multipart uploads (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]rclone backend list-multipart-uploads\f[R] to list unfinished
+Add \f[V]rclone backend list-multipart-uploads\f[R] to list unfinished
 multipart uploads (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-max-upload-parts\f[R] support (Kamil Trzci\[u0144]ski)
+Add \f[V]--s3-max-upload-parts\f[R] support (Kamil Trzciński)
 .IP \[bu] 2
-Add \f[C]--s3-no-check-bucket\f[R] for minimising rclone transactions
+Add \f[V]--s3-no-check-bucket\f[R] for minimising rclone transactions
 and perms (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-profile\f[R] and \f[C]--s3-shared-credentials-file\f[R]
+Add \f[V]--s3-profile\f[R] and \f[V]--s3-shared-credentials-file\f[R]
 options (Nick Craig-Wood)
 .IP \[bu] 2
 Use regional s3 us-east-1 endpoint (David)
@@ -80302,7 +80897,7 @@ Add Scaleway provider (Vincent Feltz)
 .IP \[bu] 2
 Update IBM COS endpoints (Egor Margineanu)
 .IP \[bu] 2
-Reduce the default \f[C]--s3-copy-cutoff\f[R] to < 5GB for Backblaze S3
+Reduce the default \f[V]--s3-copy-cutoff\f[R] to < 5GB for Backblaze S3
 compatibility (Nick Craig-Wood)
 .IP \[bu] 2
 Fix detection of bucket existing (Nick Craig-Wood)
@@ -80314,7 +80909,7 @@ SFTP
 Use the absolute path instead of the relative path for listing for
 improved compatibility (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--sftp-subsystem\f[R] and \f[C]--sftp-server-command\f[R]
+Add \f[V]--sftp-subsystem\f[R] and \f[V]--sftp-server-command\f[R]
 options (aus)
 .RE
 .IP \[bu] 2
@@ -80599,46 +81194,46 @@ New commands
 backend: command for backend-specific commands (see backends) (Nick
 Craig-Wood)
 .IP \[bu] 2
-cachestats: Deprecate in favour of \f[C]rclone backend stats cache:\f[R]
+cachestats: Deprecate in favour of \f[V]rclone backend stats cache:\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
-dbhashsum: Deprecate in favour of \f[C]rclone hashsum DropboxHash\f[R]
+dbhashsum: Deprecate in favour of \f[V]rclone hashsum DropboxHash\f[R]
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 New Features
 .RS 2
 .IP \[bu] 2
-Add \f[C]--header-download\f[R] and \f[C]--header-upload\f[R] flags for
+Add \f[V]--header-download\f[R] and \f[V]--header-upload\f[R] flags for
 setting HTTP headers when uploading/downloading (Tim Gallant)
 .IP \[bu] 2
-Add \f[C]--header\f[R] flag to add HTTP headers to every HTTP
+Add \f[V]--header\f[R] flag to add HTTP headers to every HTTP
 transaction (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--check-first\f[R] to do all checking before starting transfers
+Add \f[V]--check-first\f[R] to do all checking before starting transfers
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--track-renames-strategy\f[R] for configurable matching
-criteria for \f[C]--track-renames\f[R] (Bernd Schoolmann)
+Add \f[V]--track-renames-strategy\f[R] for configurable matching
+criteria for \f[V]--track-renames\f[R] (Bernd Schoolmann)
 .IP \[bu] 2
-Add \f[C]--cutoff-mode\f[R] hard,soft,cautious (Shing Kit Chan &
+Add \f[V]--cutoff-mode\f[R] hard,soft,cautious (Shing Kit Chan &
 Franklyn Tackitt)
 .IP \[bu] 2
 Filter flags (e.g.
-\f[C]--files-from -\f[R]) can read from stdin (fishbullet)
+\f[V]--files-from -\f[R]) can read from stdin (fishbullet)
 .IP \[bu] 2
-Add \f[C]--error-on-no-transfer\f[R] option (Jon Fautley)
+Add \f[V]--error-on-no-transfer\f[R] option (Jon Fautley)
 .IP \[bu] 2
-Implement \f[C]--order-by xxx,mixed\f[R] for copying some small and some
+Implement \f[V]--order-by xxx,mixed\f[R] for copying some small and some
 big files (Nick Craig-Wood)
 .IP \[bu] 2
-Allow \f[C]--max-backlog\f[R] to be negative meaning as large as
+Allow \f[V]--max-backlog\f[R] to be negative meaning as large as
 possible (Nick Craig-Wood)
 .IP \[bu] 2
-Added \f[C]--no-unicode-normalization\f[R] flag to allow Unicode
+Added \f[V]--no-unicode-normalization\f[R] flag to allow Unicode
 filenames to remain unique (Ben Zenker)
 .IP \[bu] 2
-Allow \f[C]--min-age\f[R]/\f[C]--max-age\f[R] to take a date as well as
+Allow \f[V]--min-age\f[R]/\f[V]--max-age\f[R] to take a date as well as
 a duration (Nick Craig-Wood)
 .IP \[bu] 2
 Add rename statistics for file and directory renames (Nick Craig-Wood)
@@ -80647,8 +81242,8 @@ Add statistics output to JSON log (reddi)
 .IP \[bu] 2
 Make stats be printed on non-zero exit code (Nick Craig-Wood)
 .IP \[bu] 2
-When running \f[C]--password-command\f[R] allow use of stdin
-(S\['e]bastien Gross)
+When running \f[V]--password-command\f[R] allow use of stdin (Sébastien
+Gross)
 .IP \[bu] 2
 Stop empty strings being a valid remote path (Nick Craig-Wood)
 .IP \[bu] 2
@@ -80659,7 +81254,7 @@ build
 .IP \[bu] 2
 Update to use go1.14 for the build (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]-trimpath\f[R] to release build for reproduceable builds (Nick
+Add \f[V]-trimpath\f[R] to release build for reproduceable builds (Nick
 Craig-Wood)
 .IP \[bu] 2
 Remove GOOS and GOARCH from Dockerfile (Brandon Philips)
@@ -80671,37 +81266,37 @@ config
 Fsync the config file after writing to save more reliably (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--obscure\f[R] and \f[C]--no-obscure\f[R] flags to
-\f[C]config create\f[R]/\f[C]update\f[R] (Nick Craig-Wood)
+Add \f[V]--obscure\f[R] and \f[V]--no-obscure\f[R] flags to
+\f[V]config create\f[R]/\f[V]update\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]config show\f[R] take \f[C]remote:\f[R] as well as
-\f[C]remote\f[R] (Nick Craig-Wood)
+Make \f[V]config show\f[R] take \f[V]remote:\f[R] as well as
+\f[V]remote\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-copyurl: Add \f[C]--no-clobber\f[R] flag (Denis)
+copyurl: Add \f[V]--no-clobber\f[R] flag (Denis)
 .IP \[bu] 2
-delete: Added \f[C]--rmdirs\f[R] flag to delete directories as well
+delete: Added \f[V]--rmdirs\f[R] flag to delete directories as well
 (Kush)
 .IP \[bu] 2
-filter: Added \f[C]--files-from-raw\f[R] flag (Ankur Gupta)
+filter: Added \f[V]--files-from-raw\f[R] flag (Ankur Gupta)
 .IP \[bu] 2
 genautocomplete: Add support for fish shell (Matan Rosenberg)
 .IP \[bu] 2
 log: Add support for syslog LOCAL facilities (Patryk Jakuszew)
 .IP \[bu] 2
-lsjson: Add \f[C]--hash-type\f[R] parameter and use it in lsf to speed
+lsjson: Add \f[V]--hash-type\f[R] parameter and use it in lsf to speed
 up hashing (Nick Craig-Wood)
 .IP \[bu] 2
 rc
 .RS 2
 .IP \[bu] 2
-Add \f[C]-o\f[R]/\f[C]--opt\f[R] and \f[C]-a\f[R]/\f[C]--arg\f[R] for
+Add \f[V]-o\f[R]/\f[V]--opt\f[R] and \f[V]-a\f[R]/\f[V]--arg\f[R] for
 more structured input (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]backend/command\f[R] for running backend-specific
+Implement \f[V]backend/command\f[R] for running backend-specific
 commands remotely (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]mount/mount\f[R] command for starting \f[C]rclone mount\f[R]
+Add \f[V]mount/mount\f[R] command for starting \f[V]rclone mount\f[R]
 via the API (Chaitanya)
 .RE
 .IP \[bu] 2
@@ -80710,15 +81305,15 @@ rcd: Add Prometheus metrics support (Gary Kim)
 serve http
 .RS 2
 .IP \[bu] 2
-Added a \f[C]--template\f[R] flag for user defined markup (calistri)
+Added a \f[V]--template\f[R] flag for user defined markup (calistri)
 .IP \[bu] 2
 Add Last-Modified headers to files and directories (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 serve sftp: Add support for multiple host keys by repeating
-\f[C]--key\f[R] flag (Maxime Suret)
+\f[V]--key\f[R] flag (Maxime Suret)
 .IP \[bu] 2
-touch: Add \f[C]--localtime\f[R] flag to make \f[C]--timestamp\f[R]
+touch: Add \f[V]--localtime\f[R] flag to make \f[V]--timestamp\f[R]
 localtime not UTC (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -80728,8 +81323,8 @@ Bug Fixes
 accounting
 .RS 2
 .IP \[bu] 2
-Restore \[dq]Max number of stats groups reached\[dq] log line
-(Micha\[/l] Matczuk)
+Restore \[dq]Max number of stats groups reached\[dq] log line (Michał
+Matczuk)
 .IP \[bu] 2
 Correct exitcode on Transfer Limit Exceeded flag.
 (Anuar Serdaliyev)
@@ -80747,7 +81342,7 @@ dedupe: Stop dedupe deleting files with identical IDs (Nick Craig-Wood)
 oauth
 .RS 2
 .IP \[bu] 2
-Use custom http client so that \f[C]--no-check-certificate\f[R] is
+Use custom http client so that \f[V]--no-check-certificate\f[R] is
 honored by oauth token fetch (Mark Spieth)
 .IP \[bu] 2
 Replace deprecated oauth2.NoContext (Lars Lehtonen)
@@ -80759,9 +81354,9 @@ operations
 Fix setting the timestamp on Windows for multithread copy (Nick
 Craig-Wood)
 .IP \[bu] 2
-Make rcat obey \f[C]--ignore-checksum\f[R] (Nick Craig-Wood)
+Make rcat obey \f[V]--ignore-checksum\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]--max-transfer\f[R] more accurate (Nick Craig-Wood)
+Make \f[V]--max-transfer\f[R] more accurate (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 rc
@@ -80789,7 +81384,7 @@ sync
 .RS 2
 .IP \[bu] 2
 Fix incorrect \[dq]nothing to transfer\[dq] message using
-\f[C]--delete-before\f[R] (Nick Craig-Wood)
+\f[V]--delete-before\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Only create empty directories when they don\[aq]t exist on the remote
 (Ishuah Kariuki)
@@ -80799,13 +81394,13 @@ Only create empty directories when they don\[aq]t exist on the remote
 Mount
 .RS 2
 .IP \[bu] 2
-Add \f[C]--async-read\f[R] flag to disable asynchronous reads (Nick
+Add \f[V]--async-read\f[R] flag to disable asynchronous reads (Nick
 Craig-Wood)
 .IP \[bu] 2
-Ignore \f[C]--allow-root\f[R] flag with a warning as it has been removed
+Ignore \f[V]--allow-root\f[R] flag with a warning as it has been removed
 upstream (Nick Craig-Wood)
 .IP \[bu] 2
-Warn if \f[C]--allow-non-empty\f[R] used on Windows and clarify docs
+Warn if \f[V]--allow-non-empty\f[R] used on Windows and clarify docs
 (Nick Craig-Wood)
 .IP \[bu] 2
 Constrain to go1.13 or above otherwise bazil.org/fuse fails to compile
@@ -80825,7 +81420,7 @@ Use ReaddirPlus on Windows to improve directory listing performance
 Send a hint as to whether the filesystem is case insensitive or not
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add rc command \f[C]mount/types\f[R] (Nick Craig-Wood)
+Add rc command \f[V]mount/types\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Change maximum leaf name length to 1024 bytes (Nick Craig-Wood)
 .RE
@@ -80833,13 +81428,13 @@ Change maximum leaf name length to 1024 bytes (Nick Craig-Wood)
 VFS
 .RS 2
 .IP \[bu] 2
-Add \f[C]--vfs-read-wait\f[R] and \f[C]--vfs-write-wait\f[R] flags to
+Add \f[V]--vfs-read-wait\f[R] and \f[V]--vfs-write-wait\f[R] flags to
 control time waiting for a sequential read/write (Nick Craig-Wood)
 .IP \[bu] 2
-Change default \f[C]--vfs-read-wait\f[R] to 20ms (it was 5ms and not
+Change default \f[V]--vfs-read-wait\f[R] to 20ms (it was 5ms and not
 configurable) (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]df\f[R] output more consistent on a rclone mount.
+Make \f[V]df\f[R] output more consistent on a rclone mount.
 (Yves G)
 .IP \[bu] 2
 Report 1PB free for unknown disk sizes (Nick Craig-Wood)
@@ -80871,10 +81466,10 @@ Local
 Speed up multi thread downloads by using sparse files on Windows (Nick
 Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--local-no-sparse\f[R] flag for disabling sparse files
+Implement \f[V]--local-no-sparse\f[R] flag for disabling sparse files
 (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]rclone backend noop\f[R] for testing purposes (Nick
+Implement \f[V]rclone backend noop\f[R] for testing purposes (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix \[dq]file not found\[dq] errors on post transfer Hash calculation
@@ -80884,7 +81479,7 @@ Fix \[dq]file not found\[dq] errors on post transfer Hash calculation
 Cache
 .RS 2
 .IP \[bu] 2
-Implement \f[C]rclone backend stats\f[R] command (Nick Craig-Wood)
+Implement \f[V]rclone backend stats\f[R] command (Nick Craig-Wood)
 .IP \[bu] 2
 Fix Server Side Copy with Temp Upload (Brandon McNama)
 .IP \[bu] 2
@@ -80896,7 +81491,7 @@ Move methods used for testing into test file (greatroar)
 .IP \[bu] 2
 Add Pin and Unpin and canonicalised lookup (Nick Craig-Wood)
 .IP \[bu] 2
-Use proper import path go.etcd.io/bbolt (Robert-Andr\['e] Mauchin)
+Use proper import path go.etcd.io/bbolt (Robert-André Mauchin)
 .RE
 .IP \[bu] 2
 Crypt
@@ -80910,8 +81505,8 @@ This allows encrypted Jottacloud uploads without using local disk
 This means encrypted s3/b2 uploads will now have hashes
 .RE
 .IP \[bu] 2
-Added \f[C]rclone backend decode\f[R]/\f[C]encode\f[R] commands to
-replicate functionality of \f[C]cryptdecode\f[R] (Anagh Kumar Baranwal)
+Added \f[V]rclone backend decode\f[R]/\f[V]encode\f[R] commands to
+replicate functionality of \f[V]cryptdecode\f[R] (Anagh Kumar Baranwal)
 .IP \[bu] 2
 Get rid of the unused Cipher interface as it obfuscated the code (Nick
 Craig-Wood)
@@ -80920,17 +81515,17 @@ Craig-Wood)
 Azure Blob
 .RS 2
 .IP \[bu] 2
-Implement streaming of unknown sized files so \f[C]rcat\f[R] is now
+Implement streaming of unknown sized files so \f[V]rcat\f[R] is now
 supported (Nick Craig-Wood)
 .IP \[bu] 2
 Implement memory pooling to control memory use (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--azureblob-disable-checksum\f[R] flag (Nick Craig-Wood)
+Add \f[V]--azureblob-disable-checksum\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
-Retry \f[C]InvalidBlobOrBlock\f[R] error as it may indicate block
+Retry \f[V]InvalidBlobOrBlock\f[R] error as it may indicate block
 concurrency problems (Nick Craig-Wood)
 .IP \[bu] 2
-Remove unused \f[C]Object.parseTimeString()\f[R] (Lars Lehtonen)
+Remove unused \f[V]Object.parseTimeString()\f[R] (Lars Lehtonen)
 .IP \[bu] 2
 Fix permission error on SAS URL limited to container (Nick Craig-Wood)
 .RE
@@ -80938,21 +81533,21 @@ Fix permission error on SAS URL limited to container (Nick Craig-Wood)
 B2
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
 Ignore directory markers at the root also (Nick Craig-Wood)
 .IP \[bu] 2
 Force the case of the SHA1 to lowercase (Nick Craig-Wood)
 .IP \[bu] 2
-Remove unused \f[C]largeUpload.clearUploadURL()\f[R] (Lars Lehtonen)
+Remove unused \f[V]largeUpload.clearUploadURL()\f[R] (Lars Lehtonen)
 .RE
 .IP \[bu] 2
 Box
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
 Implement About to read size used (Nick Craig-Wood)
 .IP \[bu] 2
@@ -80967,24 +81562,24 @@ Remove unnecessary iat from jws claims (David)
 Drive
 .RS 2
 .IP \[bu] 2
-Follow shortcuts by default, skip with \f[C]--drive-skip-shortcuts\f[R]
+Follow shortcuts by default, skip with \f[V]--drive-skip-shortcuts\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]rclone backend shortcut\f[R] command for creating
+Implement \f[V]rclone backend shortcut\f[R] command for creating
 shortcuts (Nick Craig-Wood)
 .IP \[bu] 2
-Added \f[C]rclone backend\f[R] command to change
-\f[C]service_account_file\f[R] and \f[C]chunk_size\f[R] (Anagh Kumar
+Added \f[V]rclone backend\f[R] command to change
+\f[V]service_account_file\f[R] and \f[V]chunk_size\f[R] (Anagh Kumar
 Baranwal)
 .IP \[bu] 2
-Fix missing files when using \f[C]--fast-list\f[R] and
-\f[C]--drive-shared-with-me\f[R] (Nick Craig-Wood)
+Fix missing files when using \f[V]--fast-list\f[R] and
+\f[V]--drive-shared-with-me\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Fix duplicate items when using \f[C]--drive-shared-with-me\f[R] (Nick
+Fix duplicate items when using \f[V]--drive-shared-with-me\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Extend \f[C]--drive-stop-on-upload-limit\f[R] to respond to
-\f[C]teamDriveFileLimitExceeded\f[R].
+Extend \f[V]--drive-stop-on-upload-limit\f[R] to respond to
+\f[V]teamDriveFileLimitExceeded\f[R].
 (harry)
 .IP \[bu] 2
 Don\[aq]t delete files with multiple parents to avoid data loss (Nick
@@ -80998,14 +81593,14 @@ Dropbox
 .IP \[bu] 2
 Make error insufficient space to be fatal (harry)
 .IP \[bu] 2
-Add info about required redirect url (Elan Ruusam\[:a]e)
+Add info about required redirect url (Elan Ruusamäe)
 .RE
 .IP \[bu] 2
 Fichier
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
 Implement custom pacer to deal with the new rate limiting (buengese)
 .RE
@@ -81028,10 +81623,10 @@ Work around pureftp sending spurious 150 messages (Nick Craig-Wood)
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Nick Craig-Wood)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]ARCHIVE\f[R] storage class to help (Adam Stroud)
+Add \f[V]ARCHIVE\f[R] storage class to help (Adam Stroud)
 .IP \[bu] 2
 Ignore directory markers at the root (Nick Craig-Wood)
 .RE
@@ -81041,8 +81636,8 @@ Googlephotos
 .IP \[bu] 2
 Make the start year configurable (Daven)
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
 Create feature/favorites directory (Brandon Philips)
 .IP \[bu] 2
@@ -81061,12 +81656,12 @@ Improved directory listing with new template from Caddy project
 Jottacloud
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--jottacloud-trashed-only\f[R] (buengese)
+Implement \f[V]--jottacloud-trashed-only\f[R] (buengese)
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
-Use \f[C]RawURLEncoding\f[R] when decoding base64 encoded login token
+Use \f[V]RawURLEncoding\f[R] when decoding base64 encoded login token
 (buengese)
 .IP \[bu] 2
 Implement cleanup (buengese)
@@ -81085,11 +81680,11 @@ Describe 2FA requirements (valery1707)
 Onedrive
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--onedrive-server-side-across-configs\f[R] (Nick
+Implement \f[V]--onedrive-server-side-across-configs\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
 Fix occasional 416 errors on multipart uploads (Nick Craig-Wood)
 .IP \[bu] 2
@@ -81097,14 +81692,14 @@ Added maximum chunk size limit warning in the docs (Harry)
 .IP \[bu] 2
 Fix missing drive on config (Nick Craig-Wood)
 .IP \[bu] 2
-Make error \f[C]quotaLimitReached\f[R] to be fatal (harry)
+Make error \f[V]quotaLimitReached\f[R] to be fatal (harry)
 .RE
 .IP \[bu] 2
 Opendrive
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .RE
 .IP \[bu] 2
 Pcloud
@@ -81113,8 +81708,8 @@ Pcloud
 Added support for interchangeable root folder for pCloud backend (Sunil
 Patra)
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
 Fix initial config \[dq]Auth state doesn\[aq]t match\[dq] message (Nick
 Craig-Wood)
@@ -81123,8 +81718,8 @@ Craig-Wood)
 Premiumizeme
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
 Prune unused functions (Lars Lehtonen)
 .RE
@@ -81132,8 +81727,8 @@ Prune unused functions (Lars Lehtonen)
 Putio
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Nick Craig-Wood)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Make downloading files use the rclone http Client (Nick Craig-Wood)
 .IP \[bu] 2
@@ -81143,12 +81738,12 @@ Fix parsing of remotes with leading and trailing / (Nick Craig-Wood)
 Qingstor
 .RS 2
 .IP \[bu] 2
-Make \f[C]rclone cleanup\f[R] remove pending multipart uploads older
+Make \f[V]rclone cleanup\f[R] remove pending multipart uploads older
 than 24h (Nick Craig-Wood)
 .IP \[bu] 2
 Try harder to cancel failed multipart uploads (Nick Craig-Wood)
 .IP \[bu] 2
-Prune \f[C]multiUploader.list()\f[R] (Lars Lehtonen)
+Prune \f[V]multiUploader.list()\f[R] (Lars Lehtonen)
 .IP \[bu] 2
 Lint fix (Lars Lehtonen)
 .RE
@@ -81156,28 +81751,28 @@ Lint fix (Lars Lehtonen)
 S3
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
 Use memory pool for buffer allocations (Maciej Zimnoch)
 .IP \[bu] 2
 Add SSE-C support for AWS, Ceph, and MinIO (Jack Anderson)
 .IP \[bu] 2
-Fail fast multipart upload (Micha\[/l] Matczuk)
+Fail fast multipart upload (Michał Matczuk)
 .IP \[bu] 2
 Report errors on bucket creation (mkdir) correctly (Nick Craig-Wood)
 .IP \[bu] 2
 Specify that Minio supports URL encoding in listings (Nick Craig-Wood)
 .IP \[bu] 2
-Added 500 as retryErrorCode (Micha\[/l] Matczuk)
+Added 500 as retryErrorCode (Michał Matczuk)
 .IP \[bu] 2
-Use \f[C]--low-level-retries\f[R] as the number of SDK retries
-(Aleksandar Jankovi\['c])
+Use \f[V]--low-level-retries\f[R] as the number of SDK retries
+(Aleksandar Janković)
 .IP \[bu] 2
 Fix multipart abort context (Aleksandar Jankovic)
 .IP \[bu] 2
-Replace deprecated \f[C]session.New()\f[R] with
-\f[C]session.NewSession()\f[R] (Lars Lehtonen)
+Replace deprecated \f[V]session.New()\f[R] with
+\f[V]session.NewSession()\f[R] (Lars Lehtonen)
 .IP \[bu] 2
 Use the provided size parameter when allocating a new memory pool
 (Joachim Brandon LeBlanc)
@@ -81187,11 +81782,11 @@ retries (Nick Craig-Wood)
 .IP \[bu] 2
 Ignore directory markers at the root also (Nick Craig-Wood)
 .IP \[bu] 2
-Use single memory pool (Micha\[/l] Matczuk)
+Use single memory pool (Michał Matczuk)
 .IP \[bu] 2
-Do not resize buf on put to memBuf (Micha\[/l] Matczuk)
+Do not resize buf on put to memBuf (Michał Matczuk)
 .IP \[bu] 2
-Improve docs for \f[C]--s3-disable-checksum\f[R] (Nick Craig-Wood)
+Improve docs for \f[V]--s3-disable-checksum\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Don\[aq]t leak memory or tokens in edge cases for multipart upload (Nick
 Craig-Wood)
@@ -81206,31 +81801,31 @@ Implement 2FA (Fred)
 SFTP
 .RS 2
 .IP \[bu] 2
-Added \f[C]--sftp-pem-key\f[R] to support inline key files (calisro)
+Added \f[V]--sftp-pem-key\f[R] to support inline key files (calisro)
 .IP \[bu] 2
 Fix post transfer copies failing with 0 size when using
-\f[C]set_modtime=false\f[R] (Nick Craig-Wood)
+\f[V]set_modtime=false\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Sharefile
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .RE
 .IP \[bu] 2
 Sugarsync
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .RE
 .IP \[bu] 2
 Swift
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Nick Craig-Wood)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix cosmetic issue in error message (Martin Michlmayr)
 .RE
@@ -81250,20 +81845,20 @@ Enable ListR when upstreams contain local (Max Sum)
 WebDAV
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .IP \[bu] 2
-Fix \f[C]X-OC-Mtime\f[R] header for Transip compatibility (Nick
+Fix \f[V]X-OC-Mtime\f[R] header for Transip compatibility (Nick
 Craig-Wood)
 .IP \[bu] 2
-Report full and consistent usage with \f[C]about\f[R] (Yves G)
+Report full and consistent usage with \f[V]about\f[R] (Yves G)
 .RE
 .IP \[bu] 2
 Yandex
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]--header-upload\f[R] and
-\f[C]--header-download\f[R] (Tim Gallant)
+Add support for \f[V]--header-upload\f[R] and
+\f[V]--header-download\f[R] (Tim Gallant)
 .RE
 .SS v1.51.0 - 2020-02-01
 .IP \[bu] 2
@@ -81278,7 +81873,7 @@ Sugarsync (https://rclone.org/sugarsync/) (Nick Craig-Wood)
 New Features
 .RS 2
 .IP \[bu] 2
-Adjust all backends to have \f[C]--backend-encoding\f[R] parameter (Nick
+Adjust all backends to have \f[V]--backend-encoding\f[R] parameter (Nick
 Craig-Wood)
 .RS 2
 .IP \[bu] 2
@@ -81286,16 +81881,16 @@ this enables the encoding for special characters to be adjusted or
 disabled
 .RE
 .IP \[bu] 2
-Add \f[C]--max-duration\f[R] flag to control the maximum duration of a
+Add \f[V]--max-duration\f[R] flag to control the maximum duration of a
 transfer session (boosh)
 .IP \[bu] 2
-Add \f[C]--expect-continue-timeout\f[R] flag, default 1s (Nick
+Add \f[V]--expect-continue-timeout\f[R] flag, default 1s (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--no-check-dest\f[R] flag for copying without testing the
+Add \f[V]--no-check-dest\f[R] flag for copying without testing the
 destination (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--order-by\f[R] flag to order transfers (Nick Craig-Wood)
+Implement \f[V]--order-by\f[R] flag to order transfers (Nick Craig-Wood)
 .IP \[bu] 2
 accounting
 .RS 2
@@ -81321,7 +81916,7 @@ Kim)
 config
 .RS 2
 .IP \[bu] 2
-Add \f[C]--password-command\f[R] to allow dynamic config password (Damon
+Add \f[V]--password-command\f[R] to allow dynamic config password (Damon
 Permezel)
 .IP \[bu] 2
 Give config questions default values (Nick Craig-Wood)
@@ -81329,17 +81924,17 @@ Give config questions default values (Nick Craig-Wood)
 Check a remote exists when creating a new one (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-copyurl: Add \f[C]--stdout\f[R] flag to write to stdout (Nick
+copyurl: Add \f[V]--stdout\f[R] flag to write to stdout (Nick
 Craig-Wood)
 .IP \[bu] 2
 dedupe: Implement keep smallest too (Nick Craig-Wood)
 .IP \[bu] 2
-hashsum: Add flag \f[C]--base64\f[R] flag (landall)
+hashsum: Add flag \f[V]--base64\f[R] flag (landall)
 .IP \[bu] 2
 lsf: Speed up on s3/swift/etc by not reading mimetype by default (Nick
 Craig-Wood)
 .IP \[bu] 2
-lsjson: Add \f[C]--no-mimetype\f[R] flag (Nick Craig-Wood)
+lsjson: Add \f[V]--no-mimetype\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 rc: Add methods to turn on blocking and mutex profiling (Nick
 Craig-Wood)
@@ -81369,12 +81964,12 @@ Fix error count shown as checks (Cnly)
 .IP \[bu] 2
 Clear finished transfer in stats-reset (Maciej Zimnoch)
 .IP \[bu] 2
-Added StatsInfo locking in statsGroups sum function (Micha\[/l] Matczuk)
+Added StatsInfo locking in statsGroups sum function (Michał Matczuk)
 .RE
 .IP \[bu] 2
 asyncreader: Fix EOF error (buengese)
 .IP \[bu] 2
-check: Fix \f[C]--one-way\f[R] recursing more directories than it needs
+check: Fix \f[V]--one-way\f[R] recursing more directories than it needs
 to (Nick Craig-Wood)
 .IP \[bu] 2
 chunkedreader: Disable hash calculation for first segment (Nick
@@ -81403,7 +81998,7 @@ Fix dedupe continuing on errors like insufficientFilePersimmon
 .IP \[bu] 2
 Clear accounting before low level retry (Maciej Zimnoch)
 .IP \[bu] 2
-Write debug message when hashes could not be checked (Ole Sch\[:u]tt)
+Write debug message when hashes could not be checked (Ole Schütt)
 .IP \[bu] 2
 Move interface assertion to tests to remove pflag dependency (Nick
 Craig-Wood)
@@ -81468,10 +82063,10 @@ When renaming files in the cache, rename the cache item in memory too
 (Nick Craig-Wood)
 .IP \[bu] 2
 Fix open file renaming on drive when using
-\f[C]--vfs-cache-mode writes\f[R] (Nick Craig-Wood)
+\f[V]--vfs-cache-mode writes\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix incorrect modtime for mv into mount with
-\f[C]--vfs-cache-modes writes\f[R] (Nick Craig-Wood)
+\f[V]--vfs-cache-modes writes\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 On rename, rename in cache too if the file exists (Anagh Kumar Baranwal)
 .RE
@@ -81491,7 +82086,7 @@ Cache
 Follow move of upstream library github.com/coreos/bbolt
 github.com/etcd-io/bbolt (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]fatal error: concurrent map writes\f[R] (Nick Craig-Wood)
+Fix \f[V]fatal error: concurrent map writes\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Crypt
@@ -81511,16 +82106,16 @@ Reduce length of temporary suffix (Ivan Andreev)
 Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--drive-stop-on-upload-limit\f[R] flag to stop syncs when
+Add \f[V]--drive-stop-on-upload-limit\f[R] flag to stop syncs when
 upload limit reached (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--drive-use-shared-date\f[R] to use date file was shared
+Add \f[V]--drive-use-shared-date\f[R] to use date file was shared
 instead of modified date (Garry McNulty)
 .IP \[bu] 2
 Make sure invalid auth for teamdrives always reports an error (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--fast-list\f[R] when using appDataFolder (Nick Craig-Wood)
+Fix \f[V]--fast-list\f[R] when using appDataFolder (Nick Craig-Wood)
 .IP \[bu] 2
 Use multipart resumable uploads for streaming and uploads in mount (Nick
 Craig-Wood)
@@ -81533,7 +82128,7 @@ Hide dangerous config from the configurator (Nick Craig-Wood)
 Dropbox
 .RS 2
 .IP \[bu] 2
-Treat \f[C]insufficient_space\f[R] errors as non retriable errors (Nick
+Treat \f[V]insufficient_space\f[R] errors as non retriable errors (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -81565,7 +82160,7 @@ Add support \[dq]Retry-After\[dq] header (Motonori IWAMURO)
 Opendrive
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--opendrive-chunk-size\f[R] (Nick Craig-Wood)
+Implement \f[V]--opendrive-chunk-size\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 S3
@@ -81573,7 +82168,7 @@ S3
 .IP \[bu] 2
 Re-implement multipart upload to fix memory issues (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-copy-cutoff\f[R] for size to switch to multipart copy
+Add \f[V]--s3-copy-cutoff\f[R] for size to switch to multipart copy
 (Nick Craig-Wood)
 .IP \[bu] 2
 Add new region Asia Pacific (Hong Kong) (Outvi V)
@@ -81581,7 +82176,7 @@ Add new region Asia Pacific (Hong Kong) (Outvi V)
 Reduce memory usage streaming files by reducing max stream upload size
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-list-chunk\f[R] option for bucket listing (Thomas
+Add \f[V]--s3-list-chunk\f[R] option for bucket listing (Thomas
 Kriechbaumer)
 .IP \[bu] 2
 Force path style bucket access to off for AWS deprecation (Nick
@@ -81593,7 +82188,7 @@ Add StackPath Object Storage Support (Dave Koston)
 .IP \[bu] 2
 Fix ExpiryWindow value (Aleksandar Jankovic)
 .IP \[bu] 2
-Fix DisableChecksum condition (Aleksandar Jankovi\['c])
+Fix DisableChecksum condition (Aleksandar Janković)
 .IP \[bu] 2
 Fix URL decoding of NextMarker (Nick Craig-Wood)
 .RE
@@ -81601,7 +82196,7 @@ Fix URL decoding of NextMarker (Nick Craig-Wood)
 SFTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--sftp-skip-links\f[R] to skip symlinks and non regular files
+Add \f[V]--sftp-skip-links\f[R] to skip symlinks and non regular files
 (Nick Craig-Wood)
 .IP \[bu] 2
 Retry Creation of Connection (Sebastian Brandt)
@@ -81618,7 +82213,7 @@ Swift
 .IP \[bu] 2
 Reserve segments of dynamic large object when delete objects in
 container what was enabled versioning.
-(Nguy\[u1EC5]n H\[u1EEF]u Lu\[^a]n)
+(Nguyễn Hữu Luân)
 .IP \[bu] 2
 Fix parsing of X-Object-Manifest (Nick Craig-Wood)
 .IP \[bu] 2
@@ -81656,8 +82251,8 @@ Fix --drive-root-folder-id with team/shared drives (Nick Craig-Wood)
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-hash: Fix accidentally changed hash names for \f[C]DropboxHash\f[R] and
-\f[C]CRC-32\f[R] (Nick Craig-Wood)
+hash: Fix accidentally changed hash names for \f[V]DropboxHash\f[R] and
+\f[V]CRC-32\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 fshttp: Fix error reporting on tpslimit token bucket errors (Nick
 Craig-Wood)
@@ -81694,7 +82289,7 @@ Mail.ru Cloud (https://rclone.org/mailru/) (Ivan Andreev)
 New Features
 .RS 2
 .IP \[bu] 2
-encodings (Fabian M\[:o]ller & Nick Craig-Wood)
+encodings (Fabian Möller & Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
 All backends now use file name encoding to ensure any file name can be
@@ -81749,7 +82344,7 @@ Add sample WebDAV server Docker Compose manifest.
 copyurl
 .RS 2
 .IP \[bu] 2
-Add \f[C]--auto-filename\f[R] flag for using file name from URL in
+Add \f[V]--auto-filename\f[R] flag for using file name from URL in
 destination path (Denis)
 .RE
 .IP \[bu] 2
@@ -81774,13 +82369,13 @@ Bug Fixes
 sync
 .RS 2
 .IP \[bu] 2
-Make \f[C]--update\f[R]/\f[C]-u\f[R] not transfer files that haven\[aq]t
+Make \f[V]--update\f[R]/\f[V]-u\f[R] not transfer files that haven\[aq]t
 changed (Nick Craig-Wood)
 .IP \[bu] 2
 Free objects after they come out of the transfer pipe to save memory
 (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--files-from without --no-traverse\f[R] doing a recursive scan
+Fix \f[V]--files-from without --no-traverse\f[R] doing a recursive scan
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -81821,7 +82416,7 @@ Craig-Wood)
 Make autocomplete compatible with bash\[aq]s posix mode for macOS (Danil
 Semelenov)
 .IP \[bu] 2
-Make \f[C]--progress\f[R] work in git bash on Windows (Nick Craig-Wood)
+Make \f[V]--progress\f[R] work in git bash on Windows (Nick Craig-Wood)
 .IP \[bu] 2
 Fix \[aq]compopt: command not found\[aq] on autocomplete on macOS (Danil
 Semelenov)
@@ -81835,12 +82430,12 @@ Craig-Wood)
 .IP \[bu] 2
 Check config names more carefully and report errors (Nick Craig-Wood)
 .IP \[bu] 2
-Remove error: can\[aq]t use \f[C]--size-only\f[R] and
-\f[C]--ignore-size\f[R] together.
+Remove error: can\[aq]t use \f[V]--size-only\f[R] and
+\f[V]--ignore-size\f[R] together.
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-filter: Prevent mixing options when \f[C]--files-from\f[R] is in use
+filter: Prevent mixing options when \f[V]--files-from\f[R] is in use
 (Michele Caci)
 .IP \[bu] 2
 serve sftp: Fix crash on unsupported operations (e.g.
@@ -81866,7 +82461,7 @@ Craig-Wood)
 VFS
 .RS 2
 .IP \[bu] 2
-Add flag \f[C]--vfs-case-insensitive\f[R] for windows/macOS mounts (Ivan
+Add flag \f[V]--vfs-case-insensitive\f[R] for windows/macOS mounts (Ivan
 Andreev)
 .IP \[bu] 2
 Make objects of unknown size readable through the VFS (Nick Craig-Wood)
@@ -81890,7 +82485,7 @@ Disable logging to the Windows event log (Nick Craig-Wood)
 B2
 .RS 2
 .IP \[bu] 2
-Remove \f[C]unverified:\f[R] prefix on sha1 to improve interop (e.g.
+Remove \f[V]unverified:\f[R] prefix on sha1 to improve interop (e.g.
 with CyberDuck) (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -81908,8 +82503,8 @@ Craig-Wood)
 .IP \[bu] 2
 Make sure that drive root ID is always canonical (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--drive-shared-with-me\f[R] from the root with lsand
-\f[C]--fast-list\f[R] (Nick Craig-Wood)
+Fix \f[V]--drive-shared-with-me\f[R] from the root with lsand
+\f[V]--fast-list\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Fix ChangeNotify polling for shared drives (Nick Craig-Wood)
 .IP \[bu] 2
@@ -81941,7 +82536,7 @@ HTTP
 .IP \[bu] 2
 HEAD directory entries in parallel to speedup (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--http-no-head\f[R] to stop rclone doing HEAD in listings (Nick
+Add \f[V]--http-no-head\f[R] to stop rclone doing HEAD in listings (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -81963,7 +82558,7 @@ Only ask for URL encoded directory listings if we need them on Ceph
 .IP \[bu] 2
 Add option for multipart failure behaviour (Aleksandar Jankovic)
 .IP \[bu] 2
-Support for multipart copy (\[u5E84]\[u5929]\[u7FFC])
+Support for multipart copy (庄天翼)
 .IP \[bu] 2
 Fix nil pointer reference if no metadata returned for object (Nick
 Craig-Wood)
@@ -81972,12 +82567,12 @@ Craig-Wood)
 SFTP
 .RS 2
 .IP \[bu] 2
-Fix \f[C]--sftp-ask-password\f[R] trying to contact the ssh agent (Nick
+Fix \f[V]--sftp-ask-password\f[R] trying to contact the ssh agent (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix hashes of files with backslashes (Nick Craig-Wood)
 .IP \[bu] 2
-Include more ciphers with \f[C]--sftp-use-insecure-cipher\f[R] (Carlos
+Include more ciphers with \f[V]--sftp-use-insecure-cipher\f[R] (Carlos
 Ferreyra)
 .RE
 .IP \[bu] 2
@@ -82049,11 +82644,11 @@ Bug Fixes
 .RS 2
 .IP \[bu] 2
 accounting: Fix locking in Transfer to avoid deadlock with
-\f[C]--progress\f[R] (Nick Craig-Wood)
+\f[V]--progress\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 docs: Fix template argument for mktemp in install.sh (Cnly)
 .IP \[bu] 2
-operations: Fix \f[C]-u\f[R]/\f[C]--update\f[R] with google photos /
+operations: Fix \f[V]-u\f[R]/\f[V]--update\f[R] with google photos /
 files of unknown size (Nick Craig-Wood)
 .IP \[bu] 2
 rc: Fix docs for config/create /update /password (Nick Craig-Wood)
@@ -82106,23 +82701,23 @@ New Features
 .IP \[bu] 2
 Experimental web GUI (https://rclone.org/gui/) (Chaitanya Bankanhal)
 .IP \[bu] 2
-Implement \f[C]--compare-dest\f[R] & \f[C]--copy-dest\f[R] (yparitcher)
+Implement \f[V]--compare-dest\f[R] & \f[V]--copy-dest\f[R] (yparitcher)
 .IP \[bu] 2
-Implement \f[C]--suffix\f[R] without \f[C]--backup-dir\f[R] for backup
+Implement \f[V]--suffix\f[R] without \f[V]--backup-dir\f[R] for backup
 to current dir (yparitcher)
 .IP \[bu] 2
-\f[C]config reconnect\f[R] to re-login (re-run the oauth login) for the
+\f[V]config reconnect\f[R] to re-login (re-run the oauth login) for the
 backend.
 (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]config userinfo\f[R] to discover which user you are logged in as.
+\f[V]config userinfo\f[R] to discover which user you are logged in as.
 (Nick Craig-Wood)
 .IP \[bu] 2
-\f[C]config disconnect\f[R] to disconnect you (log out) from the
+\f[V]config disconnect\f[R] to disconnect you (log out) from the
 backend.
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--use-json-log\f[R] for JSON logging (justinalin)
+Add \f[V]--use-json-log\f[R] for JSON logging (justinalin)
 .IP \[bu] 2
 Add context propagation to rclone (Aleksandar Jankovic)
 .IP \[bu] 2
@@ -82145,10 +82740,10 @@ operations:
 .IP \[bu] 2
 Run hashing operations in parallel (Nick Craig-Wood)
 .IP \[bu] 2
-Don\[aq]t calculate checksums when using \f[C]--ignore-checksum\f[R]
+Don\[aq]t calculate checksums when using \f[V]--ignore-checksum\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
-Check transfer hashes when using \f[C]--size-only\f[R] mode (Nick
+Check transfer hashes when using \f[V]--size-only\f[R] mode (Nick
 Craig-Wood)
 .IP \[bu] 2
 Disable multi thread copy for local to local copies (Nick Craig-Wood)
@@ -82183,7 +82778,7 @@ rcd
 .IP \[bu] 2
 Auto-login for web-gui (Chaitanya Bankanhal)
 .IP \[bu] 2
-Implement \f[C]--baseurl\f[R] for rcd and web-gui (Chaitanya Bankanhal)
+Implement \f[V]--baseurl\f[R] for rcd and web-gui (Chaitanya Bankanhal)
 .RE
 .IP \[bu] 2
 serve dlna
@@ -82203,12 +82798,12 @@ serve ftp
 .IP \[bu] 2
 Refactor to bring into line with other serve commands (Nick Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--auth-proxy\f[R] (Nick Craig-Wood)
+Implement \f[V]--auth-proxy\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
-serve http: Implement \f[C]--baseurl\f[R] (Nick Craig-Wood)
+serve http: Implement \f[V]--baseurl\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-serve restic: Implement \f[C]--baseurl\f[R] (Nick Craig-Wood)
+serve restic: Implement \f[V]--baseurl\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 serve sftp
 .RS 2
@@ -82221,9 +82816,9 @@ Fix detection of whether server is authorized (Nick Craig-Wood)
 serve webdav
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--baseurl\f[R] (Nick Craig-Wood)
+Implement \f[V]--baseurl\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
-Support \f[C]--auth-proxy\f[R] (Nick Craig-Wood)
+Support \f[V]--auth-proxy\f[R] (Nick Craig-Wood)
 .RE
 .RE
 .IP \[bu] 2
@@ -82234,7 +82829,7 @@ Make \[dq]bad record MAC\[dq] a retriable error (Nick Craig-Wood)
 .IP \[bu] 2
 copyurl: Fix copying files that return HTTP errors (Nick Craig-Wood)
 .IP \[bu] 2
-march: Fix checking sub-directories when using \f[C]--no-traverse\f[R]
+march: Fix checking sub-directories when using \f[V]--no-traverse\f[R]
 (buengese)
 .IP \[bu] 2
 rc
@@ -82246,7 +82841,7 @@ marshalability (Nick Craig-Wood)
 Move job expire flags to rc to fix initialization problem (Nick
 Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--loopback\f[R] with rc/list and others (Nick Craig-Wood)
+Fix \f[V]--loopback\f[R] with rc/list and others (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 rcat: Fix slowdown on systems with multiple hashes (Nick Craig-Wood)
@@ -82258,7 +82853,7 @@ rcd: Fix permissions problems on cache directory with web gui download
 Mount
 .RS 2
 .IP \[bu] 2
-Default \f[C]--daemon-timeout\f[R] to 15 minutes on macOS and FreeBSD
+Default \f[V]--daemon-timeout\f[R] to 15 minutes on macOS and FreeBSD
 (Nick Craig-Wood)
 .IP \[bu] 2
 Update docs to show mounting from root OK for bucket-based (Nick
@@ -82272,22 +82867,22 @@ VFS
 .IP \[bu] 2
 Make write without cache more efficient (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--vfs-cache-mode minimal\f[R] and \f[C]writes\f[R] ignoring
+Fix \f[V]--vfs-cache-mode minimal\f[R] and \f[V]writes\f[R] ignoring
 cached files (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Local
 .RS 2
 .IP \[bu] 2
-Add \f[C]--local-case-sensitive\f[R] and
-\f[C]--local-case-insensitive\f[R] (Nick Craig-Wood)
+Add \f[V]--local-case-sensitive\f[R] and
+\f[V]--local-case-insensitive\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Avoid polluting page cache when uploading local files to remote backends
-(Micha\[/l] Matczuk)
+(Michał Matczuk)
 .IP \[bu] 2
 Don\[aq]t calculate any hashes by default (Nick Craig-Wood)
 .IP \[bu] 2
-Fadvise run syscall on a dedicated go routine (Micha\[/l] Matczuk)
+Fadvise run syscall on a dedicated go routine (Michał Matczuk)
 .RE
 .IP \[bu] 2
 Azure Blob
@@ -82318,7 +82913,7 @@ Fix server-side copy of big files (Nick Craig-Wood)
 .IP \[bu] 2
 Update API for teamdrive use (Nick Craig-Wood)
 .IP \[bu] 2
-Add error for purge with \f[C]--drive-trashed-only\f[R] (ginvine)
+Add error for purge with \f[V]--drive-trashed-only\f[R] (ginvine)
 .RE
 .IP \[bu] 2
 Fichier
@@ -82338,7 +82933,7 @@ Make all operations work from the root (Nick Craig-Wood)
 HTTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--http-headers\f[R] flag for setting arbitrary headers (Nick
+Add \f[V]--http-headers\f[R] flag for setting arbitrary headers (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -82413,10 +83008,10 @@ Fix segments leak during failed large file uploads.
 WebDAV
 .RS 2
 .IP \[bu] 2
-Add \f[C]--webdav-bearer-token-command\f[R] (Nick Craig-Wood)
+Add \f[V]--webdav-bearer-token-command\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Refresh token when it expires with
-\f[C]--webdav-bearer-token-command\f[R] (Nick Craig-Wood)
+\f[V]--webdav-bearer-token-command\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Add docs for using bearer_token_command with oidc-agent (Paul Millar)
 .RE
@@ -82434,8 +83029,8 @@ New Features
 Multi threaded downloads to local storage (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-controlled with \f[C]--multi-thread-cutoff\f[R] and
-\f[C]--multi-thread-streams\f[R]
+controlled with \f[V]--multi-thread-cutoff\f[R] and
+\f[V]--multi-thread-streams\f[R]
 .RE
 .IP \[bu] 2
 Use rclone.conf from rclone executable directory to enable portable use
@@ -82448,11 +83043,11 @@ this is common on bucket-based remotes, e.g.
 s3, gcs
 .RE
 .IP \[bu] 2
-Add \f[C]--ignore-case-sync\f[R] for forced case insensitivity
+Add \f[V]--ignore-case-sync\f[R] for forced case insensitivity
 (garry415)
 .IP \[bu] 2
-Implement \f[C]--stats-one-line-date\f[R] and
-\f[C]--stats-one-line-date-format\f[R] (Peter Berbec)
+Implement \f[V]--stats-one-line-date\f[R] and
+\f[V]--stats-one-line-date-format\f[R] (Peter Berbec)
 .IP \[bu] 2
 Log an ERROR for all commands which exit with non-zero status (Nick
 Craig-Wood)
@@ -82468,7 +83063,7 @@ build: Drop support for go1.8 (Nick Craig-Wood)
 config: Make config create/update encrypt passwords where necessary
 (Nick Craig-Wood)
 .IP \[bu] 2
-copyurl: Honor \f[C]--no-check-certificate\f[R] (Stefan Breunig)
+copyurl: Honor \f[V]--no-check-certificate\f[R] (Stefan Breunig)
 .IP \[bu] 2
 install: Linux skip man pages if no mandb (didil)
 .IP \[bu] 2
@@ -82488,7 +83083,7 @@ Craig-Wood)
 rc
 .RS 2
 .IP \[bu] 2
-Add \f[C]--loopback\f[R] flag to run commands directly without a server
+Add \f[V]--loopback\f[R] flag to run commands directly without a server
 (Nick Craig-Wood)
 .IP \[bu] 2
 Add operations/fsinfo: Return information about the remote (Nick
@@ -82504,11 +83099,11 @@ jobs: Make job expiry timeouts configurable (Aleksandar Jankovic)
 .IP \[bu] 2
 serve dlna reworked and improved (Dan Walters)
 .IP \[bu] 2
-serve ftp: add \f[C]--ftp-public-ip\f[R] flag to specify public IP
+serve ftp: add \f[V]--ftp-public-ip\f[R] flag to specify public IP
 (calistri)
 .IP \[bu] 2
-serve restic: Add support for \f[C]--private-repos\f[R] in
-\f[C]serve restic\f[R] (Florian Apolloner)
+serve restic: Add support for \f[V]--private-repos\f[R] in
+\f[V]serve restic\f[R] (Florian Apolloner)
 .IP \[bu] 2
 serve webdav: Combine serve webdav and serve http (Gary Kim)
 .IP \[bu] 2
@@ -82518,15 +83113,15 @@ size: Ignore negative sizes when calculating total (Garry McNulty)
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-Make move and copy individual files obey \f[C]--backup-dir\f[R] (Nick
+Make move and copy individual files obey \f[V]--backup-dir\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-If \f[C]--ignore-checksum\f[R] is in effect, don\[aq]t calculate
+If \f[V]--ignore-checksum\f[R] is in effect, don\[aq]t calculate
 checksum (Nick Craig-Wood)
 .IP \[bu] 2
 moveto: Fix case-insensitive same remote move (Gary Kim)
 .IP \[bu] 2
-rc: Fix serving bucket-based objects with \f[C]--rc-serve\f[R] (Nick
+rc: Fix serving bucket-based objects with \f[V]--rc-serve\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 serve webdav: Fix serveDir not being updated with changes from webdav
@@ -82585,10 +83180,10 @@ Fix move and copy from TeamDrive to GDrive (Fionera)
 Add notes that cleanup works in the background on drive (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--drive-server-side-across-configs\f[R] to default back to old
+Add \f[V]--drive-server-side-across-configs\f[R] to default back to old
 server-side copy semantics by default (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--drive-size-as-quota\f[R] to show storage quota usage for file
+Add \f[V]--drive-size-as-quota\f[R] to show storage quota usage for file
 size (Garry McNulty)
 .RE
 .IP \[bu] 2
@@ -82599,7 +83194,7 @@ Add FTP List timeout (Jeff Quinn)
 .IP \[bu] 2
 Add FTP over TLS support (Gary Kim)
 .IP \[bu] 2
-Add \f[C]--ftp-no-check-certificate\f[R] option for FTPS (Gary Kim)
+Add \f[V]--ftp-no-check-certificate\f[R] option for FTPS (Gary Kim)
 .RE
 .IP \[bu] 2
 Google Cloud Storage
@@ -82631,7 +83226,7 @@ S3
 .RS 2
 .IP \[bu] 2
 Support S3 Accelerated endpoints with
-\f[C]--s3-use-accelerate-endpoint\f[R] (Nick Craig-Wood)
+\f[V]--s3-use-accelerate-endpoint\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Add config info for Wasabi\[aq]s EU Central endpoint (Robert Marko)
 .IP \[bu] 2
@@ -82643,7 +83238,7 @@ SFTP
 .IP \[bu] 2
 Add About support (Gary Kim)
 .IP \[bu] 2
-Fix about parsing of \f[C]df\f[R] results so it can cope with -ve
+Fix about parsing of \f[V]df\f[R] results so it can cope with -ve
 results (Nick Craig-Wood)
 .IP \[bu] 2
 Send custom client version and debug server version (Nick Craig-Wood)
@@ -82674,41 +83269,41 @@ this means rclone will restart transfers if the source has an error
 this is most useful for downloads or cloud to cloud copies
 .RE
 .IP \[bu] 2
-Use \f[C]--fast-list\f[R] for listing operations where it won\[aq]t use
+Use \f[V]--fast-list\f[R] for listing operations where it won\[aq]t use
 more memory (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
 this should speed up the following operations on remotes which support
-\f[C]ListR\f[R]
+\f[V]ListR\f[R]
 .IP \[bu] 2
-\f[C]dedupe\f[R], \f[C]serve restic\f[R] \f[C]lsf\f[R], \f[C]ls\f[R],
-\f[C]lsl\f[R], \f[C]lsjson\f[R], \f[C]lsd\f[R], \f[C]md5sum\f[R],
-\f[C]sha1sum\f[R], \f[C]hashsum\f[R], \f[C]size\f[R], \f[C]delete\f[R],
-\f[C]cat\f[R], \f[C]settier\f[R]
+\f[V]dedupe\f[R], \f[V]serve restic\f[R] \f[V]lsf\f[R], \f[V]ls\f[R],
+\f[V]lsl\f[R], \f[V]lsjson\f[R], \f[V]lsd\f[R], \f[V]md5sum\f[R],
+\f[V]sha1sum\f[R], \f[V]hashsum\f[R], \f[V]size\f[R], \f[V]delete\f[R],
+\f[V]cat\f[R], \f[V]settier\f[R]
 .IP \[bu] 2
-use \f[C]--disable ListR\f[R] to get old behaviour if required
+use \f[V]--disable ListR\f[R] to get old behaviour if required
 .RE
 .IP \[bu] 2
-Make \f[C]--files-from\f[R] traverse the destination unless
-\f[C]--no-traverse\f[R] is set (Nick Craig-Wood)
+Make \f[V]--files-from\f[R] traverse the destination unless
+\f[V]--no-traverse\f[R] is set (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-this fixes \f[C]--files-from\f[R] with Google drive and excessive API
+this fixes \f[V]--files-from\f[R] with Google drive and excessive API
 use in general.
 .RE
 .IP \[bu] 2
-Make server-side copy account bytes and obey \f[C]--max-transfer\f[R]
+Make server-side copy account bytes and obey \f[V]--max-transfer\f[R]
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--create-empty-src-dirs\f[R] flag and default to not creating
+Add \f[V]--create-empty-src-dirs\f[R] flag and default to not creating
 empty dirs (ishuah)
 .IP \[bu] 2
 Add client side TLS/SSL flags
-\f[C]--ca-cert\f[R]/\f[C]--client-cert\f[R]/\f[C]--client-key\f[R] (Nick
+\f[V]--ca-cert\f[R]/\f[V]--client-cert\f[R]/\f[V]--client-key\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Implement \f[C]--suffix-keep-extension\f[R] for use with
-\f[C]--suffix\f[R] (Nick Craig-Wood)
+Implement \f[V]--suffix-keep-extension\f[R] for use with
+\f[V]--suffix\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 build:
 .RS 2
@@ -82725,17 +83320,17 @@ compatibility (Dan Walters)
 lsf: Add \[aq]e\[aq] format to show encrypted names and \[aq]o\[aq] for
 original IDs (Nick Craig-Wood)
 .IP \[bu] 2
-lsjson: Added \f[C]--files-only\f[R] and \f[C]--dirs-only\f[R] flags
+lsjson: Added \f[V]--files-only\f[R] and \f[V]--dirs-only\f[R] flags
 (calistri)
 .IP \[bu] 2
 rc: Implement operations/publiclink the equivalent of
-\f[C]rclone link\f[R] (Nick Craig-Wood)
+\f[V]rclone link\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-accounting: Fix total ETA when \f[C]--stats-unit bits\f[R] is in effect
+accounting: Fix total ETA when \f[V]--stats-unit bits\f[R] is in effect
 (Nick Craig-Wood)
 .IP \[bu] 2
 Bash TAB completion
@@ -82746,7 +83341,7 @@ Craig-Wood)
 .IP \[bu] 2
 Fix for remotes with underscores in their names (Six)
 .IP \[bu] 2
-Fix completion of remotes (Florian Gamb\[:o]ck)
+Fix completion of remotes (Florian Gamböck)
 .IP \[bu] 2
 Fix autocompletion of remote paths with spaces (Danil Semelenov)
 .RE
@@ -82788,19 +83383,19 @@ Allow manual configuration of backblaze downloadUrl (Vince)
 .IP \[bu] 2
 Ignore already_hidden error on remove (Nick Craig-Wood)
 .IP \[bu] 2
-Ignore malformed \f[C]src_last_modified_millis\f[R] (Nick Craig-Wood)
+Ignore malformed \f[V]src_last_modified_millis\f[R] (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--skip-checksum-gphotos\f[R] to ignore incorrect checksums on
+Add \f[V]--skip-checksum-gphotos\f[R] to ignore incorrect checksums on
 Google Photos (Nick Craig-Wood)
 .IP \[bu] 2
 Allow server-side move/copy between different remotes.
 (Fionera)
 .IP \[bu] 2
-Add docs on team drives and \f[C]--fast-list\f[R] eventual consistency
+Add docs on team drives and \f[V]--fast-list\f[R] eventual consistency
 (Nestar47)
 .IP \[bu] 2
 Fix imports of text files (Nick Craig-Wood)
@@ -82819,7 +83414,7 @@ Retry blank errors to fix long listings (Nick Craig-Wood)
 FTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--ftp-concurrency\f[R] to limit maximum number of connections
+Add \f[V]--ftp-concurrency\f[R] to limit maximum number of connections
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -82834,7 +83429,7 @@ Allow bucket policy only buckets (Nick Craig-Wood)
 HTTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--http-no-slash\f[R] for websites with directories with no
+Add \f[V]--http-no-slash\f[R] for websites with directories with no
 slashes (Nick Craig-Wood)
 .IP \[bu] 2
 Remove duplicates from listings (Nick Craig-Wood)
@@ -82845,7 +83440,7 @@ Fix socket leak on 404 errors (Nick Craig-Wood)
 Jottacloud
 .RS 2
 .IP \[bu] 2
-Fix token refresh (Sebastian B\[:u]nger)
+Fix token refresh (Sebastian Bünger)
 .IP \[bu] 2
 Add device registration (Oliver Heyme)
 .RE
@@ -82858,7 +83453,7 @@ Implement graceful cancel of multipart uploads if rclone is interrupted
 .IP \[bu] 2
 Always add trailing colon to path when addressing items, (Cnly)
 .IP \[bu] 2
-Return errors instead of panic for invalid uploads (Fabian M\[:o]ller)
+Return errors instead of panic for invalid uploads (Fabian Möller)
 .RE
 .IP \[bu] 2
 S3
@@ -82913,7 +83508,7 @@ serve dlna: serves a remove via DLNA for the local network (nicolov)
 New Features
 .RS 2
 .IP \[bu] 2
-copy, move: Restore deprecated \f[C]--no-traverse\f[R] flag (Nick
+copy, move: Restore deprecated \f[V]--no-traverse\f[R] flag (Nick
 Craig-Wood)
 .RS 2
 .IP \[bu] 2
@@ -82932,11 +83527,11 @@ Buffer recycling library to replace sync.Pool
 .IP \[bu] 2
 Optionally use memory mapped memory for better memory shrinking
 .IP \[bu] 2
-Enable with \f[C]--use-mmap\f[R] if having memory problems - not default
+Enable with \f[V]--use-mmap\f[R] if having memory problems - not default
 yet
 .RE
 .IP \[bu] 2
-Parallelise reading of files specified by \f[C]--files-from\f[R] (Nick
+Parallelise reading of files specified by \f[V]--files-from\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 check: Add stats showing total files matched.
@@ -82947,10 +83542,10 @@ Allow rename/delete open files under Windows (Nick Craig-Wood)
 lsjson: Use exactly the correct number of decimal places in the seconds
 (Nick Craig-Wood)
 .IP \[bu] 2
-Add cookie support with cmdline switch \f[C]--use-cookies\f[R] for all
+Add cookie support with cmdline switch \f[V]--use-cookies\f[R] for all
 HTTP based remotes (qip)
 .IP \[bu] 2
-Warn if \f[C]--checksum\f[R] is set but there are no hashes available
+Warn if \f[V]--checksum\f[R] is set but there are no hashes available
 (Nick Craig-Wood)
 .IP \[bu] 2
 Rework rate limiting (pacer) to be more accurate and allow bursting
@@ -82959,7 +83554,7 @@ Rework rate limiting (pacer) to be more accurate and allow bursting
 Improve error reporting for too many/few arguments in commands (Nick
 Craig-Wood)
 .IP \[bu] 2
-listremotes: Remove \f[C]-l\f[R] short flag as it conflicts with the new
+listremotes: Remove \f[V]-l\f[R] short flag as it conflicts with the new
 global flag (weetmuts)
 .IP \[bu] 2
 Make http serving with auth generate INFO messages on auth fail (Nick
@@ -82971,12 +83566,12 @@ Bug Fixes
 .IP \[bu] 2
 Fix layout of stats (Nick Craig-Wood)
 .IP \[bu] 2
-Fix \f[C]--progress\f[R] crash under Windows Jenkins (Nick Craig-Wood)
+Fix \f[V]--progress\f[R] crash under Windows Jenkins (Nick Craig-Wood)
 .IP \[bu] 2
 Fix transfer of google/onedrive docs by calling Rcat in Copy when size
 is -1 (Cnly)
 .IP \[bu] 2
-copyurl: Fix checking of \f[C]--dry-run\f[R] (Denis Skovpen)
+copyurl: Fix checking of \f[V]--dry-run\f[R] (Denis Skovpen)
 .RE
 .IP \[bu] 2
 Mount
@@ -82998,10 +83593,10 @@ Craig-Wood)
 now all backends except b2 support renaming directories
 .RE
 .IP \[bu] 2
-Implement \f[C]--vfs-cache-max-size\f[R] to limit the total size of the
+Implement \f[V]--vfs-cache-max-size\f[R] to limit the total size of the
 cache (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--dir-perms\f[R] and \f[C]--file-perms\f[R] flags to set
+Add \f[V]--dir-perms\f[R] and \f[V]--file-perms\f[R] flags to set
 default permissions (Nick Craig-Wood)
 .IP \[bu] 2
 Fix deadlock on concurrent operations on a directory (Nick Craig-Wood)
@@ -83012,22 +83607,22 @@ Craig-Wood)
 Fix renaming/deleting open files with cache mode \[dq]writes\[dq] under
 Windows (Nick Craig-Wood)
 .IP \[bu] 2
-Fix panic on rename with \f[C]--dry-run\f[R] set (Nick Craig-Wood)
+Fix panic on rename with \f[V]--dry-run\f[R] set (Nick Craig-Wood)
 .IP \[bu] 2
-Fix vfs/refresh with recurse=true needing the \f[C]--fast-list\f[R] flag
+Fix vfs/refresh with recurse=true needing the \f[V]--fast-list\f[R] flag
 .RE
 .IP \[bu] 2
 Local
 .RS 2
 .IP \[bu] 2
-Add support for \f[C]-l\f[R]/\f[C]--links\f[R] (symbolic link
+Add support for \f[V]-l\f[R]/\f[V]--links\f[R] (symbolic link
 translation) (yair\[at]unicorn)
 .RS 2
 .IP \[bu] 2
-this works by showing links as \f[C]link.rclonelink\f[R] - see local
+this works by showing links as \f[V]link.rclonelink\f[R] - see local
 backend docs for more info
 .IP \[bu] 2
-this errors if used with \f[C]-L\f[R]/\f[C]--copy-links\f[R]
+this errors if used with \f[V]-L\f[R]/\f[V]--copy-links\f[R]
 .RE
 .IP \[bu] 2
 Fix renaming/deleting open files on Windows (Nick Craig-Wood)
@@ -83045,8 +83640,8 @@ Azure Blob
 .IP \[bu] 2
 Allow building azureblob backend on *BSD (themylogin)
 .IP \[bu] 2
-Use the rclone HTTP client to support \f[C]--dump headers\f[R],
-\f[C]--tpslimit\f[R], etc.
+Use the rclone HTTP client to support \f[V]--dump headers\f[R],
+\f[V]--tpslimit\f[R], etc.
 (Nick Craig-Wood)
 .IP \[bu] 2
 Use the s3 pacer for 0 delay in non error conditions (Nick Craig-Wood)
@@ -83069,7 +83664,7 @@ before this, rclone would use the authorised bucket regardless of what
 you put on the command line
 .RE
 .IP \[bu] 2
-Added \f[C]--b2-disable-checksum\f[R] flag (Wojciech Smigielski)
+Added \f[V]--b2-disable-checksum\f[R] flag (Wojciech Smigielski)
 .RS 2
 .IP \[bu] 2
 this enables large files to be uploaded without a SHA-1 hash for speed
@@ -83086,17 +83681,17 @@ Set default pacer to 100ms for 10 tps (Nick Craig-Wood)
 This fits the Google defaults much better and reduces the 403 errors
 massively
 .IP \[bu] 2
-Add \f[C]--drive-pacer-min-sleep\f[R] and \f[C]--drive-pacer-burst\f[R]
+Add \f[V]--drive-pacer-min-sleep\f[R] and \f[V]--drive-pacer-burst\f[R]
 to control the pacer
 .RE
 .IP \[bu] 2
 Improve ChangeNotify support for items with multiple parents (Fabian
-M\[:o]ller)
+Möller)
 .IP \[bu] 2
 Fix ListR for items with multiple parents - this fixes oddities with
-\f[C]vfs/refresh\f[R] (Fabian M\[:o]ller)
+\f[V]vfs/refresh\f[R] (Fabian Möller)
 .IP \[bu] 2
-Fix using \f[C]--drive-impersonate\f[R] and appfolders (Nick Craig-Wood)
+Fix using \f[V]--drive-impersonate\f[R] and appfolders (Nick Craig-Wood)
 .IP \[bu] 2
 Fix google docs in rclone mount for some (not all) applications (Nick
 Craig-Wood)
@@ -83131,7 +83726,7 @@ HTTP
 Add an example with username and password which is supported but
 wasn\[aq]t documented (Nick Craig-Wood)
 .IP \[bu] 2
-Fix backend with \f[C]--files-from\f[R] and nonexistent files (Nick
+Fix backend with \f[V]--files-from\f[R] and nonexistent files (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -83148,9 +83743,9 @@ Jottacloud
 Resume and deduplication support (Oliver Heyme)
 .IP \[bu] 2
 Use token auth for all API requests Don\[aq]t store password anymore
-(Sebastian B\[:u]nger)
+(Sebastian Bünger)
 .IP \[bu] 2
-Add support for 2-factor authentication (Sebastian B\[:u]nger)
+Add support for 2-factor authentication (Sebastian Bünger)
 .RE
 .IP \[bu] 2
 Mega
@@ -83182,26 +83777,26 @@ Fix go routine leak on multipart upload errors (Nick Craig-Wood)
 .IP \[bu] 2
 Add upload chunk size/concurrency/cutoff control (Nick Craig-Wood)
 .IP \[bu] 2
-Default \f[C]--qingstor-upload-concurrency\f[R] to 1 to work around bug
+Default \f[V]--qingstor-upload-concurrency\f[R] to 1 to work around bug
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 S3
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--s3-upload-cutoff\f[R] for single part uploads below
+Implement \f[V]--s3-upload-cutoff\f[R] for single part uploads below
 this (Nick Craig-Wood)
 .IP \[bu] 2
-Change \f[C]--s3-upload-concurrency\f[R] default to 4 to increase
+Change \f[V]--s3-upload-concurrency\f[R] default to 4 to increase
 performance (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-bucket-acl\f[R] to control bucket ACL (Nick Craig-Wood)
+Add \f[V]--s3-bucket-acl\f[R] to control bucket ACL (Nick Craig-Wood)
 .IP \[bu] 2
 Auto detect region for buckets on operation failure (Nick Craig-Wood)
 .IP \[bu] 2
 Add GLACIER storage class (William Cocker)
 .IP \[bu] 2
-Add Scaleway to s3 documentation (R\['e]my L\['e]one)
+Add Scaleway to s3 documentation (Rémy Léone)
 .IP \[bu] 2
 Add AWS endpoint eu-north-1 (weetmuts)
 .RE
@@ -83209,11 +83804,11 @@ Add AWS endpoint eu-north-1 (weetmuts)
 SFTP
 .RS 2
 .IP \[bu] 2
-Add support for PEM encrypted private keys (Fabian M\[:o]ller)
+Add support for PEM encrypted private keys (Fabian Möller)
 .IP \[bu] 2
-Add option to force the usage of an ssh-agent (Fabian M\[:o]ller)
+Add option to force the usage of an ssh-agent (Fabian Möller)
 .IP \[bu] 2
-Perform environment variable expansion on key-file (Fabian M\[:o]ller)
+Perform environment variable expansion on key-file (Fabian Möller)
 .IP \[bu] 2
 Fix rmdir on Windows based servers (e.g.
 CrushFTP) (Nick Craig-Wood)
@@ -83227,7 +83822,7 @@ Fix error on dangling symlinks (Nick Craig-Wood)
 Swift
 .RS 2
 .IP \[bu] 2
-Add \f[C]--swift-no-chunk\f[R] to disable segmented uploads in
+Add \f[V]--swift-no-chunk\f[R] to disable segmented uploads in
 rcat/mount (Nick Craig-Wood)
 .IP \[bu] 2
 Introduce application credential auth support (kayrus)
@@ -83272,7 +83867,7 @@ New backends
 .RS 2
 .IP \[bu] 2
 The Yandex backend was re-written - see below for details (Sebastian
-B\[:u]nger)
+Bünger)
 .RE
 .IP \[bu] 2
 New commands
@@ -83288,7 +83883,7 @@ The remote control API (rc) was greatly expanded to allow full control
 over rclone (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
-sensitive operations require authorization or the \f[C]--rc-no-auth\f[R]
+sensitive operations require authorization or the \f[V]--rc-no-auth\f[R]
 flag
 .IP \[bu] 2
 config/* operations to configure rclone
@@ -83300,7 +83895,7 @@ copy file, list directory
 .IP \[bu] 2
 sync/* for sync, copy and move
 .IP \[bu] 2
-\f[C]--rc-files\f[R] flag to serve files on the rc http server
+\f[V]--rc-files\f[R] flag to serve files on the rc http server
 .RS 2
 .IP \[bu] 2
 this is for building web native GUIs for rclone
@@ -83308,7 +83903,7 @@ this is for building web native GUIs for rclone
 .IP \[bu] 2
 Optionally serving objects on the rc http server
 .IP \[bu] 2
-Ensure rclone fails to start up if the \f[C]--rc\f[R] port is in use
+Ensure rclone fails to start up if the \f[V]--rc\f[R] port is in use
 already
 .IP \[bu] 2
 See the rc docs (https://rclone.org/rc/) for more info
@@ -83317,7 +83912,7 @@ See the rc docs (https://rclone.org/rc/) for more info
 sync/copy/move
 .RS 2
 .IP \[bu] 2
-Make \f[C]--files-from\f[R] only read the objects specified and
+Make \f[V]--files-from\f[R] only read the objects specified and
 don\[aq]t scan directories (Nick Craig-Wood)
 .RS 2
 .IP \[bu] 2
@@ -83325,17 +83920,17 @@ This is a huge speed improvement for destinations with lots of files
 .RE
 .RE
 .IP \[bu] 2
-filter: Add \f[C]--ignore-case\f[R] flag (Nick Craig-Wood)
+filter: Add \f[V]--ignore-case\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 ncdu: Add remove function (\[aq]d\[aq] key) (Henning Surmeier)
 .IP \[bu] 2
 rc command
 .RS 2
 .IP \[bu] 2
-Add \f[C]--json\f[R] flag for structured JSON input (Nick Craig-Wood)
+Add \f[V]--json\f[R] flag for structured JSON input (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--user\f[R] and \f[C]--pass\f[R] flags and interpret
-\f[C]--rc-user\f[R], \f[C]--rc-pass\f[R], \f[C]--rc-addr\f[R] (Nick
+Add \f[V]--user\f[R] and \f[V]--pass\f[R] flags and interpret
+\f[V]--rc-user\f[R], \f[V]--rc-pass\f[R], \f[V]--rc-addr\f[R] (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -83354,7 +83949,7 @@ retries (Nick Craig-Wood)
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-cmd: Make \f[C]--progress\f[R] update the stats correctly at the end
+cmd: Make \f[V]--progress\f[R] update the stats correctly at the end
 (Nick Craig-Wood)
 .IP \[bu] 2
 config: Create config directory on save if it is missing (Nick
@@ -83362,7 +83957,7 @@ Craig-Wood)
 .IP \[bu] 2
 dedupe: Check for existing filename before renaming a dupe file (ssaqua)
 .IP \[bu] 2
-move: Don\[aq]t create directories with \f[C]--dry-run\f[R] (Nick
+move: Don\[aq]t create directories with \f[V]--dry-run\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 operations: Fix Purge and Rmdirs when dir is not the root (Nick
@@ -83375,7 +83970,7 @@ serve http/webdav/restic: Ensure rclone exits if the port is in use
 Mount
 .RS 2
 .IP \[bu] 2
-Make \f[C]--volname\f[R] work for Windows and macOS (Nick Craig-Wood)
+Make \f[V]--volname\f[R] work for Windows and macOS (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Azure Blob
@@ -83399,13 +83994,13 @@ Add dropbox impersonate support (Jake Coggiano)
 Jottacloud
 .RS 2
 .IP \[bu] 2
-Fix bug in \f[C]--fast-list\f[R] handing of empty folders (albertony)
+Fix bug in \f[V]--fast-list\f[R] handing of empty folders (albertony)
 .RE
 .IP \[bu] 2
 Opendrive
 .RS 2
 .IP \[bu] 2
-Fix transfer of files with \f[C]+\f[R] and \f[C]&\f[R] in (Nick
+Fix transfer of files with \f[V]+\f[R] and \f[V]&\f[R] in (Nick
 Craig-Wood)
 .IP \[bu] 2
 Fix retries of upload chunks (Nick Craig-Wood)
@@ -83440,8 +84035,8 @@ WebDAV
 .IP \[bu] 2
 Add Content-Type to PUT requests (Nick Craig-Wood)
 .IP \[bu] 2
-Fix config parsing so \f[C]--webdav-user\f[R] and
-\f[C]--webdav-pass\f[R] flags work (Nick Craig-Wood)
+Fix config parsing so \f[V]--webdav-user\f[R] and
+\f[V]--webdav-pass\f[R] flags work (Nick Craig-Wood)
 .IP \[bu] 2
 Add RFC3339 date format (Ralf Hemberger)
 .RE
@@ -83449,18 +84044,17 @@ Add RFC3339 date format (Ralf Hemberger)
 Yandex
 .RS 2
 .IP \[bu] 2
-The yandex backend was re-written (Sebastian B\[:u]nger)
+The yandex backend was re-written (Sebastian Bünger)
 .RS 2
 .IP \[bu] 2
-This implements low level retries (Sebastian B\[:u]nger)
+This implements low level retries (Sebastian Bünger)
 .IP \[bu] 2
 Copy, Move, DirMove, PublicLink and About optional interfaces (Sebastian
-B\[:u]nger)
+Bünger)
 .IP \[bu] 2
-Improved general error handling (Sebastian B\[:u]nger)
+Improved general error handling (Sebastian Bünger)
 .IP \[bu] 2
-Removed ListR for now due to inconsistent behaviour (Sebastian
-B\[:u]nger)
+Removed ListR for now due to inconsistent behaviour (Sebastian Bünger)
 .RE
 .RE
 .SS v1.44 - 2018-10-15
@@ -83490,11 +84084,11 @@ Show URL of backend help page when starting config (Nick Craig-Wood)
 .IP \[bu] 2
 stats: Long names now split in center (Joanna Marek)
 .IP \[bu] 2
-Add \f[C]--log-format\f[R] flag for more control over log output (dcpu)
+Add \f[V]--log-format\f[R] flag for more control over log output (dcpu)
 .IP \[bu] 2
 rc: Add support for OPTIONS and basic CORS (frenos)
 .IP \[bu] 2
-stats: show FatalErrors and NoRetryErrors in stats (C\['e]dric Connes)
+stats: show FatalErrors and NoRetryErrors in stats (Cédric Connes)
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -83503,9 +84097,9 @@ Bug Fixes
 Fix -P not ending with a new line (Nick Craig-Wood)
 .IP \[bu] 2
 config: don\[aq]t create default config dir when user supplies
-\f[C]--config\f[R] (albertony)
+\f[V]--config\f[R] (albertony)
 .IP \[bu] 2
-Don\[aq]t print non-ASCII characters with \f[C]--progress\f[R] on
+Don\[aq]t print non-ASCII characters with \f[V]--progress\f[R] on
 windows (Nick Craig-Wood)
 .IP \[bu] 2
 Correct logs for excluded items (ssaqua)
@@ -83522,12 +84116,12 @@ VFS
 .IP \[bu] 2
 Fix race condition detected by serve ftp tests (Nick Craig-Wood)
 .IP \[bu] 2
-Add vfs/poll-interval rc command (Fabian M\[:o]ller)
+Add vfs/poll-interval rc command (Fabian Möller)
 .IP \[bu] 2
 Enable rename for nearly all remotes using server-side Move or Copy
 (Nick Craig-Wood)
 .IP \[bu] 2
-Reduce directory cache cleared by poll-interval (Fabian M\[:o]ller)
+Reduce directory cache cleared by poll-interval (Fabian Möller)
 .IP \[bu] 2
 Remove EXPERIMENTAL tags (Nick Craig-Wood)
 .RE
@@ -83535,7 +84129,7 @@ Remove EXPERIMENTAL tags (Nick Craig-Wood)
 Local
 .RS 2
 .IP \[bu] 2
-Skip bad symlinks in dir listing with -L enabled (C\['e]dric Connes)
+Skip bad symlinks in dir listing with -L enabled (Cédric Connes)
 .IP \[bu] 2
 Preallocate files on Windows to reduce fragmentation (Nick Craig-Wood)
 .IP \[bu] 2
@@ -83545,21 +84139,20 @@ Preallocate files on linux with fallocate(2) (Nick Craig-Wood)
 Cache
 .RS 2
 .IP \[bu] 2
-Add cache/fetch rc function (Fabian M\[:o]ller)
+Add cache/fetch rc function (Fabian Möller)
 .IP \[bu] 2
-Fix worker scale down (Fabian M\[:o]ller)
+Fix worker scale down (Fabian Möller)
 .IP \[bu] 2
 Improve performance by not sending info requests for cached chunks
 (dcpu)
 .IP \[bu] 2
-Fix error return value of cache/fetch rc method (Fabian M\[:o]ller)
+Fix error return value of cache/fetch rc method (Fabian Möller)
 .IP \[bu] 2
 Documentation fix for cache-chunk-total-size (Anagh Kumar Baranwal)
 .IP \[bu] 2
-Preserve leading / in wrapped remote path (Fabian M\[:o]ller)
+Preserve leading / in wrapped remote path (Fabian Möller)
 .IP \[bu] 2
-Add plex_insecure option to skip certificate validation (Fabian
-M\[:o]ller)
+Add plex_insecure option to skip certificate validation (Fabian Möller)
 .IP \[bu] 2
 Remove entries that no longer exist in the source (dcpu)
 .RE
@@ -83567,7 +84160,7 @@ Remove entries that no longer exist in the source (dcpu)
 Crypt
 .RS 2
 .IP \[bu] 2
-Preserve leading / in wrapped remote path (Fabian M\[:o]ller)
+Preserve leading / in wrapped remote path (Fabian Möller)
 .RE
 .IP \[bu] 2
 Alias
@@ -83579,7 +84172,7 @@ Fix handling of Windows network paths (Nick Craig-Wood)
 Azure Blob
 .RS 2
 .IP \[bu] 2
-Add \f[C]--azureblob-list-chunk\f[R] parameter (Santiago Rodr\['i]guez)
+Add \f[V]--azureblob-list-chunk\f[R] parameter (Santiago Rodríguez)
 .IP \[bu] 2
 Implemented settier command support on azureblob remote.
 (sandeepkru)
@@ -83592,31 +84185,31 @@ Box
 .RS 2
 .IP \[bu] 2
 Implement link sharing.
-(Sebastian B\[:u]nger)
+(Sebastian Bünger)
 .RE
 .IP \[bu] 2
 Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--drive-import-formats\f[R] - google docs can now be imported
-(Fabian M\[:o]ller)
+Add \f[V]--drive-import-formats\f[R] - google docs can now be imported
+(Fabian Möller)
 .RS 2
 .IP \[bu] 2
-Rewrite mime type and extension handling (Fabian M\[:o]ller)
+Rewrite mime type and extension handling (Fabian Möller)
 .IP \[bu] 2
-Add document links (Fabian M\[:o]ller)
+Add document links (Fabian Möller)
 .IP \[bu] 2
-Add support for multipart document extensions (Fabian M\[:o]ller)
+Add support for multipart document extensions (Fabian Möller)
 .IP \[bu] 2
-Add support for apps-script to json export (Fabian M\[:o]ller)
+Add support for apps-script to json export (Fabian Möller)
 .IP \[bu] 2
-Fix escaped chars in documents during list (Fabian M\[:o]ller)
+Fix escaped chars in documents during list (Fabian Möller)
 .RE
 .IP \[bu] 2
-Add \f[C]--drive-v2-download-min-size\f[R] a workaround for slow
-downloads (Fabian M\[:o]ller)
+Add \f[V]--drive-v2-download-min-size\f[R] a workaround for slow
+downloads (Fabian Möller)
 .IP \[bu] 2
-Improve directory notifications in ChangeNotify (Fabian M\[:o]ller)
+Improve directory notifications in ChangeNotify (Fabian Möller)
 .IP \[bu] 2
 When listing team drives in config, continue on failure (Nick
 Craig-Wood)
@@ -83632,7 +84225,7 @@ Craig-Wood)
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Fix service_account_file being ignored (Fabian M\[:o]ller)
+Fix service_account_file being ignored (Fabian Möller)
 .RE
 .IP \[bu] 2
 Jottacloud
@@ -83640,15 +84233,15 @@ Jottacloud
 .IP \[bu] 2
 Minor improvement in quota info (omit if unlimited) (albertony)
 .IP \[bu] 2
-Add \f[C]--fast-list\f[R] support (albertony)
+Add \f[V]--fast-list\f[R] support (albertony)
 .IP \[bu] 2
-Add permanent delete support: \f[C]--jottacloud-hard-delete\f[R]
+Add permanent delete support: \f[V]--jottacloud-hard-delete\f[R]
 (albertony)
 .IP \[bu] 2
 Add link sharing support (albertony)
 .IP \[bu] 2
 Fix handling of reserved characters.
-(Sebastian B\[:u]nger)
+(Sebastian Bünger)
 .IP \[bu] 2
 Fix socket leak on Object.Remove (Nick Craig-Wood)
 .RE
@@ -83683,7 +84276,7 @@ Use custom pacer, to retry operations when reasonable (Craig Miskell)
 Use configured server-side-encryption and storage class options when
 calling CopyObject() (Paul Kohout)
 .IP \[bu] 2
-Make \f[C]--s3-v2-auth\f[R] flag (Nick Craig-Wood)
+Make \f[V]--s3-v2-auth\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 Fix v2 auth on files with spaces (Nick Craig-Wood)
 .RE
@@ -83694,12 +84287,12 @@ Union
 Implement union backend which reads from multiple backends (Felix
 Brucker)
 .IP \[bu] 2
-Implement optional interfaces (Move, DirMove, Copy, etc.) (Nick
-Craig-Wood)
+Implement optional interfaces (Move, DirMove, Copy, etc.)
+(Nick Craig-Wood)
 .IP \[bu] 2
-Fix ChangeNotify to support multiple remotes (Fabian M\[:o]ller)
+Fix ChangeNotify to support multiple remotes (Fabian Möller)
 .IP \[bu] 2
-Fix \f[C]--backup-dir\f[R] on union backend (Nick Craig-Wood)
+Fix \f[V]--backup-dir\f[R] on union backend (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 WebDAV
@@ -83727,9 +84320,9 @@ Point release to fix hubic and azureblob backends.
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-ncdu: Return error instead of log.Fatal in Show (Fabian M\[:o]ller)
+ncdu: Return error instead of log.Fatal in Show (Fabian Möller)
 .IP \[bu] 2
-cmd: Fix crash with \f[C]--progress\f[R] and \f[C]--stats 0\f[R] (Nick
+cmd: Fix crash with \f[V]--progress\f[R] and \f[V]--stats 0\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
 docs: Tidy website display (Anagh Kumar Baranwal)
@@ -83755,7 +84348,7 @@ Craig-Wood)
 New backends
 .RS 2
 .IP \[bu] 2
-Jottacloud (Sebastian B\[:u]nger)
+Jottacloud (Sebastian Bünger)
 .RE
 .IP \[bu] 2
 New commands
@@ -83783,21 +84376,21 @@ Allow on the fly remotes with :backend: syntax
 Stats revamp
 .RS 2
 .IP \[bu] 2
-Add \f[C]--progress\f[R]/\f[C]-P\f[R] flag to show interactive progress
+Add \f[V]--progress\f[R]/\f[V]-P\f[R] flag to show interactive progress
 (Nick Craig-Wood)
 .IP \[bu] 2
 Show the total progress of the sync in the stats (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--stats-one-line\f[R] flag for single line stats (Nick
+Add \f[V]--stats-one-line\f[R] flag for single line stats (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
-Added weekday schedule into \f[C]--bwlimit\f[R] (Mateusz)
+Added weekday schedule into \f[V]--bwlimit\f[R] (Mateusz)
 .IP \[bu] 2
-lsjson: Add option to show the original object IDs (Fabian M\[:o]ller)
+lsjson: Add option to show the original object IDs (Fabian Möller)
 .IP \[bu] 2
 serve webdav: Make Content-Type without reading the file and add
-\f[C]--etag-hash\f[R] (Nick Craig-Wood)
+\f[V]--etag-hash\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 build
 .RS 2
@@ -83813,7 +84406,7 @@ rc
 Added core/stats to return the stats (reddi1)
 .RE
 .IP \[bu] 2
-\f[C]version --check\f[R]: Prints the current release and beta versions
+\f[V]version --check\f[R]: Prints the current release and beta versions
 (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -83830,16 +84423,16 @@ Fix moving average speed for file stats (Nick Craig-Wood)
 .IP \[bu] 2
 config: Fix error reading password from piped input (Nick Craig-Wood)
 .IP \[bu] 2
-move: Fix \f[C]--delete-empty-src-dirs\f[R] flag to delete all empty
+move: Fix \f[V]--delete-empty-src-dirs\f[R] flag to delete all empty
 dirs on move (ishuah)
 .RE
 .IP \[bu] 2
 Mount
 .RS 2
 .IP \[bu] 2
-Implement \f[C]--daemon-timeout\f[R] flag for OSXFUSE (Nick Craig-Wood)
+Implement \f[V]--daemon-timeout\f[R] flag for OSXFUSE (Nick Craig-Wood)
 .IP \[bu] 2
-Fix mount \f[C]--daemon\f[R] not working with encrypted config (Alex
+Fix mount \f[V]--daemon\f[R] not working with encrypted config (Alex
 Chen)
 .IP \[bu] 2
 Clip the number of blocks to 2\[ha]32-1 on macOS - fixes borg backup
@@ -83849,19 +84442,19 @@ Clip the number of blocks to 2\[ha]32-1 on macOS - fixes borg backup
 VFS
 .RS 2
 .IP \[bu] 2
-Enable vfs-read-chunk-size by default (Fabian M\[:o]ller)
+Enable vfs-read-chunk-size by default (Fabian Möller)
 .IP \[bu] 2
-Add the vfs/refresh rc command (Fabian M\[:o]ller)
+Add the vfs/refresh rc command (Fabian Möller)
 .IP \[bu] 2
-Add non recursive mode to vfs/refresh rc command (Fabian M\[:o]ller)
+Add non recursive mode to vfs/refresh rc command (Fabian Möller)
 .IP \[bu] 2
-Try to seek buffer on read only files (Fabian M\[:o]ller)
+Try to seek buffer on read only files (Fabian Möller)
 .RE
 .IP \[bu] 2
 Local
 .RS 2
 .IP \[bu] 2
-Fix crash when deprecated \f[C]--local-no-unicode-normalization\f[R] is
+Fix crash when deprecated \f[V]--local-no-unicode-normalization\f[R] is
 supplied (Nick Craig-Wood)
 .IP \[bu] 2
 Fix mkdir error when trying to copy files to the root of a drive on
@@ -83918,19 +84511,18 @@ Box
 .IP \[bu] 2
 Fix upload of > 2GB files on 32 bit platforms (Nick Craig-Wood)
 .IP \[bu] 2
-Make \f[C]--box-commit-retries\f[R] flag defaulting to 100 to fix large
+Make \f[V]--box-commit-retries\f[R] flag defaulting to 100 to fix large
 uploads (Nick Craig-Wood)
 .RE
 .IP \[bu] 2
 Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--drive-keep-revision-forever\f[R] flag (lewapm)
+Add \f[V]--drive-keep-revision-forever\f[R] flag (lewapm)
 .IP \[bu] 2
-Handle gdocs when filtering file names in list (Fabian M\[:o]ller)
+Handle gdocs when filtering file names in list (Fabian Möller)
 .IP \[bu] 2
-Support using \f[C]--fast-list\f[R] for large speedups (Fabian
-M\[:o]ller)
+Support using \f[V]--fast-list\f[R] for large speedups (Fabian Möller)
 .RE
 .IP \[bu] 2
 FTP
@@ -83942,7 +84534,7 @@ Fix Put mkParentDir failed: 521 for BunnyCDN (Nick Craig-Wood)
 Google Cloud Storage
 .RS 2
 .IP \[bu] 2
-Fix index out of range error with \f[C]--fast-list\f[R] (Nick
+Fix index out of range error with \f[V]--fast-list\f[R] (Nick
 Craig-Wood)
 .RE
 .IP \[bu] 2
@@ -83958,10 +84550,10 @@ Calculate missing MD5s (Oliver Heyme)
 Docs, fixes and tests for MD5 calculation (Nick Craig-Wood)
 .IP \[bu] 2
 Add optional MimeTyper interface.
-(Sebastian B\[:u]nger)
+(Sebastian Bünger)
 .IP \[bu] 2
-Implement optional About interface (for \f[C]df\f[R] support).
-(Sebastian B\[:u]nger)
+Implement optional About interface (for \f[V]df\f[R] support).
+(Sebastian Bünger)
 .RE
 .IP \[bu] 2
 Mega
@@ -83969,7 +84561,7 @@ Mega
 .IP \[bu] 2
 Wait for events instead of arbitrary sleeping (Nick Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--mega-hard-delete\f[R] flag (Nick Craig-Wood)
+Add \f[V]--mega-hard-delete\f[R] flag (Nick Craig-Wood)
 .IP \[bu] 2
 Fix failed logins with upper case chars in email (Nick Craig-Wood)
 .RE
@@ -83999,10 +84591,10 @@ Remove leading / from paths (Nick Craig-Wood)
 S3
 .RS 2
 .IP \[bu] 2
-Fix index out of range error with \f[C]--fast-list\f[R] (Nick
+Fix index out of range error with \f[V]--fast-list\f[R] (Nick
 Craig-Wood)
 .IP \[bu] 2
-Add \f[C]--s3-force-path-style\f[R] (Nick Craig-Wood)
+Add \f[V]--s3-force-path-style\f[R] (Nick Craig-Wood)
 .IP \[bu] 2
 Add support for KMS Key ID (bsteiss)
 .IP \[bu] 2
@@ -84012,9 +84604,9 @@ Remove leading / from paths (Nick Craig-Wood)
 Swift
 .RS 2
 .IP \[bu] 2
-Add \f[C]storage_policy\f[R] (Ruben Vandamme)
+Add \f[V]storage_policy\f[R] (Ruben Vandamme)
 .IP \[bu] 2
-Make it so just \f[C]storage_url\f[R] or \f[C]auth_token\f[R] can be
+Make it so just \f[V]storage_url\f[R] or \f[V]auth_token\f[R] can be
 overridden (Nick Craig-Wood)
 .IP \[bu] 2
 Fix server-side copy bug for unusual file names (Nick Craig-Wood)
@@ -84065,21 +84657,21 @@ New Features
 .RS 2
 .IP \[bu] 2
 copy, move: Copy single files directly, don\[aq]t use
-\f[C]--files-from\f[R] work-around
+\f[V]--files-from\f[R] work-around
 .RS 2
 .IP \[bu] 2
 this makes them much more efficient
 .RE
 .IP \[bu] 2
-Implement \f[C]--max-transfer\f[R] flag to quit transferring at a limit
+Implement \f[V]--max-transfer\f[R] flag to quit transferring at a limit
 .RS 2
 .IP \[bu] 2
-make exit code 8 for \f[C]--max-transfer\f[R] exceeded
+make exit code 8 for \f[V]--max-transfer\f[R] exceeded
 .RE
 .IP \[bu] 2
 copy: copy empty source directories to destination (Ishuah Kariuki)
 .IP \[bu] 2
-check: Add \f[C]--one-way\f[R] flag (Kasper Byrdal Nielsen)
+check: Add \f[V]--one-way\f[R] flag (Kasper Byrdal Nielsen)
 .IP \[bu] 2
 Add siginfo handler for macOS for ctrl-T stats (kubatasiemski)
 .IP \[bu] 2
@@ -84088,7 +84680,7 @@ rc
 .IP \[bu] 2
 add core/gc to run a garbage collection on demand
 .IP \[bu] 2
-enable go profiling by default on the \f[C]--rc\f[R] port
+enable go profiling by default on the \f[V]--rc\f[R] port
 .IP \[bu] 2
 return error from remote on failure
 .RE
@@ -84096,9 +84688,9 @@ return error from remote on failure
 lsf
 .RS 2
 .IP \[bu] 2
-Add \f[C]--absolute\f[R] flag to add a leading / onto path names
+Add \f[V]--absolute\f[R] flag to add a leading / onto path names
 .IP \[bu] 2
-Add \f[C]--csv\f[R] flag for compliant CSV output
+Add \f[V]--csv\f[R] flag for compliant CSV output
 .IP \[bu] 2
 Add \[aq]m\[aq] format specifier to show the MimeType
 .IP \[bu] 2
@@ -84113,7 +84705,7 @@ Add MimeType to the output
 Add ID field to output to show Object ID
 .RE
 .IP \[bu] 2
-Add \f[C]--retries-sleep\f[R] flag (Benjamin Joseph Dag)
+Add \f[V]--retries-sleep\f[R] flag (Benjamin Joseph Dag)
 .IP \[bu] 2
 Oauth tidy up web page and error handling (Henning Surmeier)
 .RE
@@ -84121,7 +84713,7 @@ Oauth tidy up web page and error handling (Henning Surmeier)
 Bug Fixes
 .RS 2
 .IP \[bu] 2
-Password prompt output with \f[C]--log-file\f[R] fixed for unix (Filip
+Password prompt output with \f[V]--log-file\f[R] fixed for unix (Filip
 Bartodziej)
 .IP \[bu] 2
 Calculate ModifyWindow each time on the fly to fix various problems
@@ -84142,23 +84734,23 @@ Ensure atexit gets run on interrupt
 macOS enhancements
 .RS 2
 .IP \[bu] 2
-Make \f[C]--noappledouble\f[R] \f[C]--noapplexattr\f[R]
+Make \f[V]--noappledouble\f[R] \f[V]--noapplexattr\f[R]
 .IP \[bu] 2
-Add \f[C]--volname\f[R] flag and remove special chars from it
+Add \f[V]--volname\f[R] flag and remove special chars from it
 .IP \[bu] 2
 Make Get/List/Set/Remove xattr return ENOSYS for efficiency
 .IP \[bu] 2
-Make \f[C]--daemon\f[R] work for macOS without CGO
+Make \f[V]--daemon\f[R] work for macOS without CGO
 .RE
 .RE
 .IP \[bu] 2
 VFS
 .RS 2
 .IP \[bu] 2
-Add \f[C]--vfs-read-chunk-size\f[R] and
-\f[C]--vfs-read-chunk-size-limit\f[R] (Fabian M\[:o]ller)
+Add \f[V]--vfs-read-chunk-size\f[R] and
+\f[V]--vfs-read-chunk-size-limit\f[R] (Fabian Möller)
 .IP \[bu] 2
-Fix ChangeNotify for new or changed folders (Fabian M\[:o]ller)
+Fix ChangeNotify for new or changed folders (Fabian Möller)
 .RE
 .IP \[bu] 2
 Local
@@ -84167,7 +84759,7 @@ Local
 Fix symlink/junction point directory handling under Windows
 .RS 2
 .IP \[bu] 2
-\f[B]NB\f[R] you will need to add \f[C]-L\f[R] to your command line to
+\f[B]NB\f[R] you will need to add \f[V]-L\f[R] to your command line to
 copy files with reparse points
 .RE
 .RE
@@ -84202,7 +84794,7 @@ Dropbox
 .RS 2
 .IP \[bu] 2
 Make Dropbox for business folders accessible using an initial
-\f[C]/\f[R] in the path
+\f[V]/\f[R] in the path
 .RE
 .IP \[bu] 2
 Google Cloud Storage
@@ -84214,15 +84806,15 @@ Low level retry all operations if necessary
 Google Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--drive-acknowledge-abuse\f[R] to download flagged files
+Add \f[V]--drive-acknowledge-abuse\f[R] to download flagged files
 .IP \[bu] 2
-Add \f[C]--drive-alternate-export\f[R] to fix large doc export
+Add \f[V]--drive-alternate-export\f[R] to fix large doc export
 .IP \[bu] 2
 Don\[aq]t attempt to choose Team Drives when using rclone config create
 .IP \[bu] 2
 Fix change list polling with team drives
 .IP \[bu] 2
-Fix ChangeNotify for folders (Fabian M\[:o]ller)
+Fix ChangeNotify for folders (Fabian Möller)
 .IP \[bu] 2
 Fix about (and df on a mount) for team drives
 .RE
@@ -84236,16 +84828,16 @@ Errorhandler for onedrive for business requests (Henning Surmeier)
 S3
 .RS 2
 .IP \[bu] 2
-Adjust upload concurrency with \f[C]--s3-upload-concurrency\f[R]
+Adjust upload concurrency with \f[V]--s3-upload-concurrency\f[R]
 (themylogin)
 .IP \[bu] 2
-Fix \f[C]--s3-chunk-size\f[R] which was always using the minimum
+Fix \f[V]--s3-chunk-size\f[R] which was always using the minimum
 .RE
 .IP \[bu] 2
 SFTP
 .RS 2
 .IP \[bu] 2
-Add \f[C]--ssh-path-override\f[R] flag (Piotr Oleszczyk)
+Add \f[V]--ssh-path-override\f[R] flag (Piotr Oleszczyk)
 .IP \[bu] 2
 Fix slow downloads for long latency connections
 .RE
@@ -84318,7 +84910,7 @@ Drop support for go1.6
 Release
 .RS 2
 .IP \[bu] 2
-Fix \f[C]make tarball\f[R] (Chih-Hsuan Yen)
+Fix \f[V]make tarball\f[R] (Chih-Hsuan Yen)
 .RE
 .IP \[bu] 2
 Bug Fixes
@@ -84339,9 +84931,9 @@ Mount
 .RS 2
 .IP \[bu] 2
 Use About to return the correct disk total/used/free (e.g.
-in \f[C]df\f[R])
+in \f[V]df\f[R])
 .IP \[bu] 2
-Set \f[C]--attr-timeout default\f[R] to \f[C]1s\f[R] - fixes:
+Set \f[V]--attr-timeout default\f[R] to \f[V]1s\f[R] - fixes:
 .RS 2
 .IP \[bu] 2
 rclone using too much memory
@@ -84351,13 +84943,13 @@ rclone not serving files to samba
 excessive time listing directories
 .RE
 .IP \[bu] 2
-Fix \f[C]df -i\f[R] (upstream fix)
+Fix \f[V]df -i\f[R] (upstream fix)
 .RE
 .IP \[bu] 2
 VFS
 .RS 2
 .IP \[bu] 2
-Filter files \f[C].\f[R] and \f[C]..\f[R] from directory listing
+Filter files \f[V].\f[R] and \f[V]..\f[R] from directory listing
 .IP \[bu] 2
 Only make the VFS cache if --vfs-cache-mode > Off
 .RE
@@ -84453,7 +85045,7 @@ S3
 .IP \[bu] 2
 Look in S3 named profile files for credentials
 .IP \[bu] 2
-Add \f[C]--s3-disable-checksum\f[R] to disable checksum uploading (Chris
+Add \f[V]--s3-disable-checksum\f[R] to disable checksum uploading (Chris
 Redekop)
 .IP \[bu] 2
 Hierarchical configuration support (Giri Badanahatti)
@@ -84500,13 +85092,13 @@ New backends
 .RS 2
 .IP \[bu] 2
 Alias backend to create aliases for existing remote names (Fabian
-M\[:o]ller)
+Möller)
 .RE
 .IP \[bu] 2
 New commands
 .RS 2
 .IP \[bu] 2
-\f[C]lsf\f[R]: list for parsing purposes (Jakub Tasiemski)
+\f[V]lsf\f[R]: list for parsing purposes (Jakub Tasiemski)
 .RS 2
 .IP \[bu] 2
 by default this is a simple non recursive list of files and directories
@@ -84514,7 +85106,7 @@ by default this is a simple non recursive list of files and directories
 it can be configured to add more info in an easy to parse way
 .RE
 .IP \[bu] 2
-\f[C]serve restic\f[R]: for serving a remote as a Restic REST endpoint
+\f[V]serve restic\f[R]: for serving a remote as a Restic REST endpoint
 .RS 2
 .IP \[bu] 2
 This enables restic to use any backends that rclone can access
@@ -84522,7 +85114,7 @@ This enables restic to use any backends that rclone can access
 Thanks Alexander Neumann for help, patches and review
 .RE
 .IP \[bu] 2
-\f[C]rc\f[R]: enable the remote control of a running rclone
+\f[V]rc\f[R]: enable the remote control of a running rclone
 .RS 2
 .IP \[bu] 2
 The running rclone must be started with --rc and related flags.
@@ -84535,16 +85127,16 @@ cache.
 New Features
 .RS 2
 .IP \[bu] 2
-\f[C]--max-delete\f[R] flag to add a delete threshold (Bj\[/o]rn Erik
+\f[V]--max-delete\f[R] flag to add a delete threshold (Bjørn Erik
 Pedersen)
 .IP \[bu] 2
 All backends now support RangeOption for ranged Open
 .RS 2
 .IP \[bu] 2
-\f[C]cat\f[R]: Use RangeOption for limited fetches to make more
+\f[V]cat\f[R]: Use RangeOption for limited fetches to make more
 efficient
 .IP \[bu] 2
-\f[C]cryptcheck\f[R]: make reading of nonce more efficient with
+\f[V]cryptcheck\f[R]: make reading of nonce more efficient with
 RangeOption
 .RE
 .IP \[bu] 2
@@ -84553,20 +85145,20 @@ serve http/webdav/restic
 .IP \[bu] 2
 support SSL/TLS
 .IP \[bu] 2
-add \f[C]--user\f[R] \f[C]--pass\f[R] and \f[C]--htpasswd\f[R] for
+add \f[V]--user\f[R] \f[V]--pass\f[R] and \f[V]--htpasswd\f[R] for
 authentication
 .RE
 .IP \[bu] 2
-\f[C]copy\f[R]/\f[C]move\f[R]: detect file size change during copy/move
+\f[V]copy\f[R]/\f[V]move\f[R]: detect file size change during copy/move
 and abort transfer (ishuah)
 .IP \[bu] 2
-\f[C]cryptdecode\f[R]: added option to return encrypted file names.
+\f[V]cryptdecode\f[R]: added option to return encrypted file names.
 (ishuah)
 .IP \[bu] 2
-\f[C]lsjson\f[R]: add \f[C]--encrypted\f[R] to show encrypted name
+\f[V]lsjson\f[R]: add \f[V]--encrypted\f[R] to show encrypted name
 (Jakub Tasiemski)
 .IP \[bu] 2
-Add \f[C]--stats-file-name-length\f[R] to specify the printed file name
+Add \f[V]--stats-file-name-length\f[R] to specify the printed file name
 length for stats (Will Gunn)
 .RE
 .IP \[bu] 2
@@ -84610,29 +85202,29 @@ on first access
 .IP \[bu] 2
 config: retry saving the config after failure (Mateusz)
 .IP \[bu] 2
-sync: when using \f[C]--backup-dir\f[R] don\[aq]t delete files if we
+sync: when using \f[V]--backup-dir\f[R] don\[aq]t delete files if we
 can\[aq]t set their modtime
 .RS 2
 .IP \[bu] 2
-this fixes odd behaviour with Dropbox and \f[C]--backup-dir\f[R]
+this fixes odd behaviour with Dropbox and \f[V]--backup-dir\f[R]
 .RE
 .IP \[bu] 2
 fshttp: fix idle timeouts for HTTP connections
 .IP \[bu] 2
-\f[C]serve http\f[R]: fix serving files with : in - fixes
+\f[V]serve http\f[R]: fix serving files with : in - fixes
 .IP \[bu] 2
-Fix \f[C]--exclude-if-present\f[R] to ignore directories which it
+Fix \f[V]--exclude-if-present\f[R] to ignore directories which it
 doesn\[aq]t have permission for (Iakov Davydov)
 .IP \[bu] 2
 Make accounting work properly with crypt and b2
 .IP \[bu] 2
-remove \f[C]--no-traverse\f[R] flag because it is obsolete
+remove \f[V]--no-traverse\f[R] flag because it is obsolete
 .RE
 .IP \[bu] 2
 Mount
 .RS 2
 .IP \[bu] 2
-Add \f[C]--attr-timeout\f[R] flag to control attribute caching in kernel
+Add \f[V]--attr-timeout\f[R] flag to control attribute caching in kernel
 .RS 2
 .IP \[bu] 2
 this now defaults to 0 which is correct but less efficient
@@ -84642,7 +85234,7 @@ docs (https://rclone.org/commands/rclone_mount/#attribute-caching) for
 more info
 .RE
 .IP \[bu] 2
-Add \f[C]--daemon\f[R] flag to allow mount to run in the background
+Add \f[V]--daemon\f[R] flag to allow mount to run in the background
 (ishuah)
 .IP \[bu] 2
 Fix: Return ENOSYS rather than EIO on attempted link
@@ -84661,14 +85253,14 @@ Many bugs fixed in the VFS layer - see below
 VFS
 .RS 2
 .IP \[bu] 2
-Many fixes for \f[C]--vfs-cache-mode\f[R] writes and above
+Many fixes for \f[V]--vfs-cache-mode\f[R] writes and above
 .RS 2
 .IP \[bu] 2
 Update cached copy if we know it has changed (fixes stale data)
 .IP \[bu] 2
 Clean path names before using them in the cache
 .IP \[bu] 2
-Disable cache cleaner if \f[C]--vfs-cache-poll-interval=0\f[R]
+Disable cache cleaner if \f[V]--vfs-cache-poll-interval=0\f[R]
 .IP \[bu] 2
 Fill and clean the cache immediately on startup
 .RE
@@ -84708,7 +85300,7 @@ Reduce log level for Plex api
 .IP \[bu] 2
 Fix dir cache issue
 .IP \[bu] 2
-Implement \f[C]--cache-db-wait-time\f[R] flag
+Implement \f[V]--cache-db-wait-time\f[R] flag
 .IP \[bu] 2
 Improve efficiency with RangeOption and RangeSeek
 .IP \[bu] 2
@@ -84776,17 +85368,17 @@ this makes rclone do one less request per invocation
 Google Drive
 .RS 2
 .IP \[bu] 2
-Migrate to api v3 (Fabian M\[:o]ller)
+Migrate to api v3 (Fabian Möller)
 .IP \[bu] 2
 Add scope configuration and root folder selection
 .IP \[bu] 2
-Add \f[C]--drive-impersonate\f[R] for service accounts
+Add \f[V]--drive-impersonate\f[R] for service accounts
 .RS 2
 .IP \[bu] 2
 thanks to everyone who tested, explored and contributed docs
 .RE
 .IP \[bu] 2
-Add \f[C]--drive-use-created-date\f[R] to use created date as modified
+Add \f[V]--drive-use-created-date\f[R] to use created date as modified
 date (nbuchanan)
 .IP \[bu] 2
 Request the export formats only when required
@@ -84799,7 +85391,7 @@ Fix finding paths with latin1 chars (a workaround for a drive bug)
 .IP \[bu] 2
 Fix copying of a single Google doc file
 .IP \[bu] 2
-Fix \f[C]--drive-auth-owner-only\f[R] to look in all directories
+Fix \f[V]--drive-auth-owner-only\f[R] to look in all directories
 .RE
 .IP \[bu] 2
 HTTP
@@ -84864,11 +85456,11 @@ SFTP
 .IP \[bu] 2
 Add option to disable remote hash check command execution (Jon Fautley)
 .IP \[bu] 2
-Add \f[C]--sftp-ask-password\f[R] flag to prompt for password when
+Add \f[V]--sftp-ask-password\f[R] flag to prompt for password when
 needed (Leo R.
 Lundgren)
 .IP \[bu] 2
-Add \f[C]set_modtime\f[R] configuration option
+Add \f[V]set_modtime\f[R] configuration option
 .IP \[bu] 2
 Fix following of symlinks
 .IP \[bu] 2
@@ -85008,7 +85600,7 @@ this requires caching files on the disk (see --cache-dir)
 As this is a new feature, use with care
 .RE
 .IP \[bu] 2
-Use sdnotify to signal systemd the mount is ready (Fabian M\[:o]ller)
+Use sdnotify to signal systemd the mount is ready (Fabian Möller)
 .IP \[bu] 2
 Check if directory is not empty before mounting (Ernest Borowski)
 .RE
@@ -85103,7 +85695,7 @@ crypt
 .IP \[bu] 2
 Option to encrypt directory names or leave them intact
 .IP \[bu] 2
-Implement DirChangeNotify (Fabian M\[:o]ller)
+Implement DirChangeNotify (Fabian Möller)
 .RE
 .IP \[bu] 2
 onedrive
@@ -85129,43 +85721,43 @@ QingStor from QingCloud (thanks wuyu)
 New commands
 .RS 2
 .IP \[bu] 2
-\f[C]rcat\f[R] - read from standard input and stream upload
+\f[V]rcat\f[R] - read from standard input and stream upload
 .IP \[bu] 2
-\f[C]tree\f[R] - shows a nicely formatted recursive listing
+\f[V]tree\f[R] - shows a nicely formatted recursive listing
 .IP \[bu] 2
-\f[C]cryptdecode\f[R] - decode encrypted file names (thanks ishuah)
+\f[V]cryptdecode\f[R] - decode encrypted file names (thanks ishuah)
 .IP \[bu] 2
-\f[C]config show\f[R] - print the config file
+\f[V]config show\f[R] - print the config file
 .IP \[bu] 2
-\f[C]config file\f[R] - print the config file location
+\f[V]config file\f[R] - print the config file location
 .RE
 .IP \[bu] 2
 New Features
 .RS 2
 .IP \[bu] 2
-Empty directories are deleted on \f[C]sync\f[R]
+Empty directories are deleted on \f[V]sync\f[R]
 .IP \[bu] 2
-\f[C]dedupe\f[R] - implement merging of duplicate directories
+\f[V]dedupe\f[R] - implement merging of duplicate directories
 .IP \[bu] 2
-\f[C]check\f[R] and \f[C]cryptcheck\f[R] made more consistent and use
+\f[V]check\f[R] and \f[V]cryptcheck\f[R] made more consistent and use
 less memory
 .IP \[bu] 2
-\f[C]cleanup\f[R] for remaining remotes (thanks ishuah)
+\f[V]cleanup\f[R] for remaining remotes (thanks ishuah)
 .IP \[bu] 2
-\f[C]--immutable\f[R] for ensuring that files don\[aq]t change (thanks
+\f[V]--immutable\f[R] for ensuring that files don\[aq]t change (thanks
 Jacob McNamee)
 .IP \[bu] 2
-\f[C]--user-agent\f[R] option (thanks Alex McGrath Kraak)
+\f[V]--user-agent\f[R] option (thanks Alex McGrath Kraak)
 .IP \[bu] 2
-\f[C]--disable\f[R] flag to disable optional features
+\f[V]--disable\f[R] flag to disable optional features
 .IP \[bu] 2
-\f[C]--bind\f[R] flag for choosing the local addr on outgoing
+\f[V]--bind\f[R] flag for choosing the local addr on outgoing
 connections
 .IP \[bu] 2
 Support for zsh auto-completion (thanks bpicode)
 .IP \[bu] 2
 Stop normalizing file names but do a normalized compare in
-\f[C]sync\f[R]
+\f[V]sync\f[R]
 .RE
 .IP \[bu] 2
 Compile
@@ -85181,11 +85773,11 @@ Bug Fixes
 .IP \[bu] 2
 Improve retriable error detection which makes multipart uploads better
 .IP \[bu] 2
-Make \f[C]check\f[R] obey \f[C]--ignore-size\f[R]
+Make \f[V]check\f[R] obey \f[V]--ignore-size\f[R]
 .IP \[bu] 2
 Fix bwlimit toggle in conjunction with schedules (thanks cbruegg)
 .IP \[bu] 2
-\f[C]config\f[R] ensures newly written config is on the same mount
+\f[V]config\f[R] ensures newly written config is on the same mount
 .RE
 .IP \[bu] 2
 Local
@@ -85193,14 +85785,14 @@ Local
 .IP \[bu] 2
 Revert to copy when moving file across file system boundaries
 .IP \[bu] 2
-\f[C]--skip-links\f[R] to suppress symlink warnings (thanks Zhiming
+\f[V]--skip-links\f[R] to suppress symlink warnings (thanks Zhiming
 Wang)
 .RE
 .IP \[bu] 2
 Mount
 .RS 2
 .IP \[bu] 2
-Reuse \f[C]rcat\f[R] internals to support uploads from all remotes
+Reuse \f[V]rcat\f[R] internals to support uploads from all remotes
 .RE
 .IP \[bu] 2
 Dropbox
@@ -85214,13 +85806,13 @@ Stop using deprecated API methods
 Swift
 .RS 2
 .IP \[bu] 2
-Fix server-side copy to empty container with \f[C]--fast-list\f[R]
+Fix server-side copy to empty container with \f[V]--fast-list\f[R]
 .RE
 .IP \[bu] 2
 Google Drive
 .RS 2
 .IP \[bu] 2
-Change the default for \f[C]--drive-use-trash\f[R] to \f[C]true\f[R]
+Change the default for \f[V]--drive-use-trash\f[R] to \f[V]true\f[R]
 .RE
 .IP \[bu] 2
 S3
@@ -85240,14 +85832,14 @@ Fix SHA1 mismatch when downloading files with no SHA1
 .IP \[bu] 2
 Calculate missing hashes on the fly instead of spooling
 .IP \[bu] 2
-\f[C]--b2-hard-delete\f[R] to permanently delete (not hide) files
+\f[V]--b2-hard-delete\f[R] to permanently delete (not hide) files
 (thanks John Papandriopoulos)
 .RE
 .IP \[bu] 2
 Hubic
 .RS 2
 .IP \[bu] 2
-Fix creating containers - no longer have to use the \f[C]default\f[R]
+Fix creating containers - no longer have to use the \f[V]default\f[R]
 container
 .RE
 .IP \[bu] 2
@@ -85256,7 +85848,7 @@ Swift
 .IP \[bu] 2
 Optionally configure from a standard set of OpenStack environment vars
 .IP \[bu] 2
-Add \f[C]endpoint_type\f[R] config
+Add \f[V]endpoint_type\f[R] config
 .RE
 .IP \[bu] 2
 Google Cloud Storage
@@ -85273,7 +85865,7 @@ Implement connection pooling for multiple ssh connections
 Limit new connections per second
 .IP \[bu] 2
 Add support for MD5 and SHA1 hashes where available (thanks Christian
-Br\[:u]ggemann)
+Brüggemann)
 .RE
 .IP \[bu] 2
 HTTP
@@ -85281,7 +85873,7 @@ HTTP
 .IP \[bu] 2
 Fix URL encoding issues
 .IP \[bu] 2
-Fix directories with \f[C]:\f[R] in
+Fix directories with \f[V]:\f[R] in
 .IP \[bu] 2
 Fix panic with URL encoded content
 .RE
@@ -85329,7 +85921,7 @@ This involved a major re-write of all the listing code
 Add --tpslimit and --tpslimit-burst to limit transactions per second
 .RS 2
 .IP \[bu] 2
-this is useful in conjunction with \f[C]rclone mount\f[R] to limit
+this is useful in conjunction with \f[V]rclone mount\f[R] to limit
 external apps
 .RE
 .IP \[bu] 2
@@ -85386,8 +85978,8 @@ Zissimopoulos for much help
 .IP \[bu] 2
 Compare checksums on upload/download via FUSE
 .IP \[bu] 2
-Unmount when program ends with SIGINT (Ctrl+C) or SIGTERM -
-J\['e]r\[^o]me Vizcaino
+Unmount when program ends with SIGINT (Ctrl+C) or SIGTERM - Jérôme
+Vizcaino
 .IP \[bu] 2
 On read only open of file, make open pending until first read
 .IP \[bu] 2
@@ -85444,7 +86036,7 @@ Add missing seek to start on retries of chunked uploads
 .IP \[bu] 2
 Fix stats accounting for upload
 .IP \[bu] 2
-Convert / in names to a unicode equivalent (\[uFF0F])
+Convert / in names to a unicode equivalent (／)
 .IP \[bu] 2
 Poll for Google Drive changes when mounted
 .RE
@@ -85497,7 +86089,7 @@ Can only set by uploading the file again
 .IP \[bu] 2
 If you uploaded with an old rclone, rclone may upload everything again
 .IP \[bu] 2
-Use \f[C]--size-only\f[R] or \f[C]--checksum\f[R] to avoid this
+Use \f[V]--size-only\f[R] or \f[V]--checksum\f[R] to avoid this
 .RE
 .IP \[bu] 2
 Now supports the Dropbox content hashing scheme
@@ -85565,7 +86157,7 @@ on capable platforms
 .IP \[bu] 2
 Implement --backup-dir and --suffix
 .IP \[bu] 2
-Implement --track-renames (initial implementation by Bj\[/o]rn Erik
+Implement --track-renames (initial implementation by Bjørn Erik
 Pedersen)
 .IP \[bu] 2
 Add time-based bandwidth limits (Lukas Loesche)
@@ -85709,7 +86301,7 @@ Fix \[dq]Ignoring unknown object\[dq] when downloading
 .IP \[bu] 2
 Add --drive-list-chunk
 .IP \[bu] 2
-Add --drive-skip-gdocs (K\['a]roly Ol\['a]h)
+Add --drive-skip-gdocs (Károly Oláh)
 .RE
 .IP \[bu] 2
 OneDrive
@@ -85769,7 +86361,7 @@ Allow repeated --include/--exclude/--filter options
 Only show transfer stats on commands which transfer stuff
 .RS 2
 .IP \[bu] 2
-show stats on any command using the \f[C]--stats\f[R] flag
+show stats on any command using the \f[V]--stats\f[R] flag
 .RE
 .IP \[bu] 2
 Allow overlapping directories in move when server-side dir move is
@@ -85859,7 +86451,7 @@ Create destination directory on Move()
 New Features
 .RS 2
 .IP \[bu] 2
-Stop single file and \f[C]--files-from\f[R] operations iterating through
+Stop single file and \f[V]--files-from\f[R] operations iterating through
 the source bucket.
 .IP \[bu] 2
 Stop removing failed upload to cloud storage remotes
@@ -85869,14 +86461,14 @@ Make ContentType be preserved for cloud to cloud copies
 Add support to toggle bandwidth limits via SIGUSR2 - thanks Marco
 Paganini
 .IP \[bu] 2
-\f[C]rclone check\f[R] shows count of hashes that couldn\[aq]t be
+\f[V]rclone check\f[R] shows count of hashes that couldn\[aq]t be
 checked
 .IP \[bu] 2
-\f[C]rclone listremotes\f[R] command
+\f[V]rclone listremotes\f[R] command
 .IP \[bu] 2
 Support linux/arm64 build - thanks Fredrik Fornwall
 .IP \[bu] 2
-Remove \f[C]Authorization:\f[R] lines from \f[C]--dump-headers\f[R]
+Remove \f[V]Authorization:\f[R] lines from \f[V]--dump-headers\f[R]
 output
 .RE
 .IP \[bu] 2
@@ -85885,7 +86477,7 @@ Bug Fixes
 .IP \[bu] 2
 Ignore files with control characters in the names
 .IP \[bu] 2
-Fix \f[C]rclone move\f[R] command
+Fix \f[V]rclone move\f[R] command
 .RS 2
 .IP \[bu] 2
 Delete src files which already existed in dst
@@ -85893,36 +86485,36 @@ Delete src files which already existed in dst
 Fix deletion of src file when dst file older
 .RE
 .IP \[bu] 2
-Fix \f[C]rclone check\f[R] on encrypted file systems
+Fix \f[V]rclone check\f[R] on encrypted file systems
 .IP \[bu] 2
 Make failed uploads not count as \[dq]Transferred\[dq]
 .IP \[bu] 2
-Make sure high level retries show with \f[C]-q\f[R]
+Make sure high level retries show with \f[V]-q\f[R]
 .IP \[bu] 2
 Use a vendor directory with godep for repeatable builds
 .RE
 .IP \[bu] 2
-\f[C]rclone mount\f[R] - FUSE
+\f[V]rclone mount\f[R] - FUSE
 .RS 2
 .IP \[bu] 2
 Implement FUSE mount options
 .RS 2
 .IP \[bu] 2
-\f[C]--no-modtime\f[R], \f[C]--debug-fuse\f[R], \f[C]--read-only\f[R],
-\f[C]--allow-non-empty\f[R], \f[C]--allow-root\f[R],
-\f[C]--allow-other\f[R]
+\f[V]--no-modtime\f[R], \f[V]--debug-fuse\f[R], \f[V]--read-only\f[R],
+\f[V]--allow-non-empty\f[R], \f[V]--allow-root\f[R],
+\f[V]--allow-other\f[R]
 .IP \[bu] 2
-\f[C]--default-permissions\f[R], \f[C]--write-back-cache\f[R],
-\f[C]--max-read-ahead\f[R], \f[C]--umask\f[R], \f[C]--uid\f[R],
-\f[C]--gid\f[R]
+\f[V]--default-permissions\f[R], \f[V]--write-back-cache\f[R],
+\f[V]--max-read-ahead\f[R], \f[V]--umask\f[R], \f[V]--uid\f[R],
+\f[V]--gid\f[R]
 .RE
 .IP \[bu] 2
-Add \f[C]--dir-cache-time\f[R] to control caching of directory entries
+Add \f[V]--dir-cache-time\f[R] to control caching of directory entries
 .IP \[bu] 2
 Implement seek for files opened for read (useful for video players)
 .RS 2
 .IP \[bu] 2
-with \f[C]-no-seek\f[R] flag to disable
+with \f[V]-no-seek\f[R] flag to disable
 .RE
 .IP \[bu] 2
 Fix crash on 32 bit ARM (alignment of 64 bit counter)
@@ -85939,7 +86531,7 @@ Don\[aq]t show encrypted password in configurator to stop confusion
 Amazon Drive
 .RS 2
 .IP \[bu] 2
-New wait for upload option \f[C]--acd-upload-wait-per-gb\f[R]
+New wait for upload option \f[V]--acd-upload-wait-per-gb\f[R]
 .RS 2
 .IP \[bu] 2
 upload timeouts scale by file size and can be disabled
@@ -85949,13 +86541,13 @@ Add 502 Bad Gateway to list of errors we retry
 .IP \[bu] 2
 Fix overwriting a file with a zero length file
 .IP \[bu] 2
-Fix ACD file size warning limit - thanks Felix B\[:u]nemann
+Fix ACD file size warning limit - thanks Felix Bünemann
 .RE
 .IP \[bu] 2
 Local
 .RS 2
 .IP \[bu] 2
-Unix: implement \f[C]-x\f[R]/\f[C]--one-file-system\f[R] to stay on a
+Unix: implement \f[V]-x\f[R]/\f[V]--one-file-system\f[R] to stay on a
 single file system
 .RS 2
 .IP \[bu] 2
@@ -85988,7 +86580,7 @@ S3
 Command line and config file support for
 .RS 2
 .IP \[bu] 2
-Setting/overriding ACL - thanks Radek \[vS]enfeld
+Setting/overriding ACL - thanks Radek Šenfeld
 .IP \[bu] 2
 Setting storage class - thanks Asko Tamm
 .RE
@@ -85999,7 +86591,7 @@ Drive
 .IP \[bu] 2
 Make exponential backoff work exactly as per Google specification
 .IP \[bu] 2
-add \f[C].epub\f[R], \f[C].odp\f[R] and \f[C].tsv\f[R] as export
+add \f[V].epub\f[R], \f[V].odp\f[R] and \f[V].tsv\f[R] as export
 formats.
 .RE
 .IP \[bu] 2
@@ -86036,7 +86628,7 @@ rclone genautocomplete - command to make a bash completion script for
 rclone
 .RE
 .IP \[bu] 2
-Editing a remote using \f[C]rclone config\f[R] now goes through the
+Editing a remote using \f[V]rclone config\f[R] now goes through the
 wizard
 .IP \[bu] 2
 Compile with go 1.7 - this fixes rclone on macOS Sierra and on 386
@@ -86054,7 +86646,7 @@ Document how to make your own client_id
 s3
 .RS 2
 .IP \[bu] 2
-User-configurable Amazon S3 ACL (thanks Radek \[vS]enfeld)
+User-configurable Amazon S3 ACL (thanks Radek Šenfeld)
 .RE
 .IP \[bu] 2
 b2
@@ -86073,7 +86665,7 @@ onedrive
 .RS 2
 .IP \[bu] 2
 Fix URL escaping in file names - e.g.
-uploading files with \f[C]+\f[R] in them.
+uploading files with \f[V]+\f[R] in them.
 .RE
 .IP \[bu] 2
 amazon cloud drive
@@ -86186,7 +86778,7 @@ Make error handling compliant with B2 integrations notes.
 .IP \[bu] 2
 Fix handling of token expiry.
 .IP \[bu] 2
-Implement --b2-test-mode to set \f[C]X-Bz-Test-Mode\f[R] header.
+Implement --b2-test-mode to set \f[V]X-Bz-Test-Mode\f[R] header.
 .IP \[bu] 2
 Set cutoff for chunked upload to 200MB as per B2 guidelines.
 .IP \[bu] 2
@@ -86225,9 +86817,9 @@ Log -v output to stdout by default
 .IP \[bu] 2
 Display the transfer stats in more human-readable form
 .IP \[bu] 2
-Make 0 size files specifiable with \f[C]--max-size 0b\f[R]
+Make 0 size files specifiable with \f[V]--max-size 0b\f[R]
 .IP \[bu] 2
-Add \f[C]b\f[R] suffix so we can specify bytes in --bwlimit, --min-size,
+Add \f[V]b\f[R] suffix so we can specify bytes in --bwlimit, --min-size,
 etc.
 .IP \[bu] 2
 Use \[dq]password:\[dq] instead of \[dq]password>\[dq] prompt - thanks
@@ -86299,33 +86891,33 @@ Add domain option for openstack (v3 auth) - thanks Fabian Ruff
 New Features
 .RS 2
 .IP \[bu] 2
-Implement \f[C]-I, --ignore-times\f[R] for unconditional upload
+Implement \f[V]-I, --ignore-times\f[R] for unconditional upload
 .IP \[bu] 2
-Improve \f[C]dedupe\f[R]command
+Improve \f[V]dedupe\f[R]command
 .RS 2
 .IP \[bu] 2
 Now removes identical copies without asking
 .IP \[bu] 2
-Now obeys \f[C]--dry-run\f[R]
+Now obeys \f[V]--dry-run\f[R]
 .IP \[bu] 2
-Implement \f[C]--dedupe-mode\f[R] for non interactive running
+Implement \f[V]--dedupe-mode\f[R] for non interactive running
 .RS 2
 .IP \[bu] 2
-\f[C]--dedupe-mode interactive\f[R] - interactive the default.
+\f[V]--dedupe-mode interactive\f[R] - interactive the default.
 .IP \[bu] 2
-\f[C]--dedupe-mode skip\f[R] - removes identical files then skips
+\f[V]--dedupe-mode skip\f[R] - removes identical files then skips
 anything left.
 .IP \[bu] 2
-\f[C]--dedupe-mode first\f[R] - removes identical files then keeps the
+\f[V]--dedupe-mode first\f[R] - removes identical files then keeps the
 first one.
 .IP \[bu] 2
-\f[C]--dedupe-mode newest\f[R] - removes identical files then keeps the
+\f[V]--dedupe-mode newest\f[R] - removes identical files then keeps the
 newest one.
 .IP \[bu] 2
-\f[C]--dedupe-mode oldest\f[R] - removes identical files then keeps the
+\f[V]--dedupe-mode oldest\f[R] - removes identical files then keeps the
 oldest one.
 .IP \[bu] 2
-\f[C]--dedupe-mode rename\f[R] - removes identical files then renames
+\f[V]--dedupe-mode rename\f[R] - removes identical files then renames
 the rest to be different.
 .RE
 .RE
@@ -86334,7 +86926,7 @@ the rest to be different.
 Bug fixes
 .RS 2
 .IP \[bu] 2
-Make rclone check obey the \f[C]--size-only\f[R] flag.
+Make rclone check obey the \f[V]--size-only\f[R] flag.
 .IP \[bu] 2
 Use \[dq]application/octet-stream\[dq] if discovered mime type is
 invalid.
@@ -86367,7 +86959,7 @@ It will upload new files to update the modification times
 .IP \[bu] 2
 (there isn\[aq]t an API to just set the mod time.)
 .IP \[bu] 2
-If you want the old behaviour use \f[C]--size-only\f[R].
+If you want the old behaviour use \f[V]--size-only\f[R].
 .RE
 .IP \[bu] 2
 Update API to new version
@@ -86393,28 +86985,28 @@ New Features
 .IP \[bu] 2
 Configuration file encryption - thanks Klaus Post
 .IP \[bu] 2
-Improve \f[C]rclone config\f[R] adding more help and making it easier to
+Improve \f[V]rclone config\f[R] adding more help and making it easier to
 understand
 .IP \[bu] 2
-Implement \f[C]-u\f[R]/\f[C]--update\f[R] so creation times can be used
+Implement \f[V]-u\f[R]/\f[V]--update\f[R] so creation times can be used
 on all remotes
 .IP \[bu] 2
-Implement \f[C]--low-level-retries\f[R] flag
+Implement \f[V]--low-level-retries\f[R] flag
 .IP \[bu] 2
 Optionally disable gzip compression on downloads with
-\f[C]--no-gzip-encoding\f[R]
+\f[V]--no-gzip-encoding\f[R]
 .RE
 .IP \[bu] 2
 Bug fixes
 .RS 2
 .IP \[bu] 2
-Don\[aq]t make directories if \f[C]--dry-run\f[R] set
+Don\[aq]t make directories if \f[V]--dry-run\f[R] set
 .IP \[bu] 2
-Fix and document the \f[C]move\f[R] command
+Fix and document the \f[V]move\f[R] command
 .IP \[bu] 2
-Fix redirecting stderr on unix-like OSes when using \f[C]--log-file\f[R]
+Fix redirecting stderr on unix-like OSes when using \f[V]--log-file\f[R]
 .IP \[bu] 2
-Fix \f[C]delete\f[R] command to wait until all finished - fixes missing
+Fix \f[V]delete\f[R] command to wait until all finished - fixes missing
 deletes.
 .RE
 .IP \[bu] 2
@@ -86422,7 +87014,7 @@ Backblaze B2
 .RS 2
 .IP \[bu] 2
 Use one upload URL per go routine fixes
-\f[C]more than one upload using auth token\f[R]
+\f[V]more than one upload using auth token\f[R]
 .IP \[bu] 2
 Add pacing, retries and reauthentication - fixes token expiry problems
 .IP \[bu] 2
@@ -86445,7 +87037,7 @@ Swift
 .IP \[bu] 2
 Fix uploading of chunked files with non ASCII characters
 .IP \[bu] 2
-Allow setting of \f[C]storage_url\f[R] in the config - thanks Xavier
+Allow setting of \f[V]storage_url\f[R] in the config - thanks Xavier
 Lucas
 .RE
 .IP \[bu] 2
@@ -86469,28 +87061,28 @@ Retry on more things to make directory listings more reliable
 New Features
 .RS 2
 .IP \[bu] 2
-Easier headless configuration with \f[C]rclone authorize\f[R]
+Easier headless configuration with \f[V]rclone authorize\f[R]
 .IP \[bu] 2
 Add support for multiple hash types - we now check SHA1 as well as MD5
 hashes.
 .IP \[bu] 2
-\f[C]delete\f[R] command which does obey the filters (unlike
-\f[C]purge\f[R])
+\f[V]delete\f[R] command which does obey the filters (unlike
+\f[V]purge\f[R])
 .IP \[bu] 2
-\f[C]dedupe\f[R] command to deduplicate a remote.
+\f[V]dedupe\f[R] command to deduplicate a remote.
 Useful with Google Drive.
 .IP \[bu] 2
-Add \f[C]--ignore-existing\f[R] flag to skip all files that exist on
+Add \f[V]--ignore-existing\f[R] flag to skip all files that exist on
 destination.
 .IP \[bu] 2
-Add \f[C]--delete-before\f[R], \f[C]--delete-during\f[R],
-\f[C]--delete-after\f[R] flags.
+Add \f[V]--delete-before\f[R], \f[V]--delete-during\f[R],
+\f[V]--delete-after\f[R] flags.
 .IP \[bu] 2
-Add \f[C]--memprofile\f[R] flag to debug memory use.
+Add \f[V]--memprofile\f[R] flag to debug memory use.
 .IP \[bu] 2
 Warn the user about files with same name but different case
 .IP \[bu] 2
-Make \f[C]--include\f[R] rules add their implicit exclude * at the end
+Make \f[V]--include\f[R] rules add their implicit exclude * at the end
 of the filter list
 .IP \[bu] 2
 Deprecate compiling with go1.3
@@ -86517,8 +87109,8 @@ SHA1 hashes now checked by rclone core
 Drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--drive-auth-owner-only\f[R] to only consider files owned by
-the user - thanks Bj\[:o]rn Harrtell
+Add \f[V]--drive-auth-owner-only\f[R] to only consider files owned by
+the user - thanks Björn Harrtell
 .IP \[bu] 2
 Export Google documents
 .RE
@@ -86538,7 +87130,7 @@ Fix upload from unprivileged user.
 S3
 .RS 2
 .IP \[bu] 2
-Fix updating of mod times of files with \f[C]+\f[R] in.
+Fix updating of mod times of files with \f[V]+\f[R] in.
 .RE
 .IP \[bu] 2
 Local
@@ -86555,8 +87147,7 @@ Yandex storage backend - thank you Dmitry Burdeev (\[dq]dibu\[dq])
 .IP \[bu] 2
 Implement Backblaze B2 storage backend
 .IP \[bu] 2
-Add --min-age and --max-age flags - thank you Adriano Aur\['e]lio
-Meirelles
+Add --min-age and --max-age flags - thank you Adriano Aurélio Meirelles
 .IP \[bu] 2
 Make ls/lsl/md5sum/size/check obey includes and excludes
 .RE
@@ -86604,7 +87195,7 @@ Fix deletion of some excluded files without --delete-excluded
 .IP \[bu] 2
 This could have deleted files unexpectedly on sync
 .IP \[bu] 2
-Always check first with \f[C]--dry-run\f[R]!
+Always check first with \f[V]--dry-run\f[R]!
 .RE
 .RE
 .IP \[bu] 2
@@ -86633,7 +87224,7 @@ New features
 .IP \[bu] 2
 Add support for Microsoft OneDrive
 .IP \[bu] 2
-Add \f[C]--no-check-certificate\f[R] option to disable server
+Add \f[V]--no-check-certificate\f[R] option to disable server
 certificate verification
 .IP \[bu] 2
 Add async readahead buffer for faster transfer of big files
@@ -86673,7 +87264,7 @@ Don\[aq]t delete the bucket if fs wasn\[aq]t at root
 New features
 .RS 2
 .IP \[bu] 2
-Implement \f[C]rclone size\f[R] for measuring remotes
+Implement \f[V]rclone size\f[R] for measuring remotes
 .RE
 .IP \[bu] 2
 Fixes
@@ -86683,7 +87274,7 @@ Fix headless config for drive and gcs
 .IP \[bu] 2
 Tell the user they should try again if the webserver method failed
 .IP \[bu] 2
-Improve output of \f[C]--dump-headers\f[R]
+Improve output of \f[V]--dump-headers\f[R]
 .RE
 .IP \[bu] 2
 S3
@@ -86808,7 +87399,7 @@ Issue an error message when trying to upload bad file name
 drive
 .RS 2
 .IP \[bu] 2
-Add \f[C]--drive-use-trash\f[R] flag so rclone trashes instead of
+Add \f[V]--drive-use-trash\f[R] flag so rclone trashes instead of
 deletes
 .IP \[bu] 2
 Add \[dq]Forbidden to download\[dq] message for files with no
@@ -87056,12 +87647,12 @@ Project started
 .SS Limitations
 .SS Directory timestamps aren\[aq]t preserved on some backends
 .PP
-As of \f[C]v1.66\f[R], rclone supports syncing directory modtimes, if
+As of \f[V]v1.66\f[R], rclone supports syncing directory modtimes, if
 the backend supports it.
 Some backends do not support it -- see
 overview (https://rclone.org/overview/) for a complete list.
 Additionally, note that empty directories are not synced by default
-(this can be enabled with \f[C]--create-empty-src-dirs\f[R].)
+(this can be enabled with \f[V]--create-empty-src-dirs\f[R].)
 .SS Rclone struggles with millions of files in a directory/bucket
 .PP
 Currently rclone loads each directory/bucket entirely into memory before
@@ -87080,7 +87671,7 @@ S3/GCS/Swift/B2) do not have a concept of directories.
 Rclone therefore cannot create directories in them which means that
 empty directories on a bucket-based remote will tend to disappear.
 .PP
-Some software creates empty keys ending in \f[C]/\f[R] as directory
+Some software creates empty keys ending in \f[V]/\f[R] as directory
 markers.
 Rclone doesn\[aq]t do this as it potentially creates more objects and
 costs more.
@@ -87099,12 +87690,13 @@ issues (https://github.com/rclone/rclone/issues?q=is%3Aopen+is%3Aissue+milestone
 .PP
 Yes they do.
 All the rclone commands (e.g.
-\f[C]sync\f[R], \f[C]copy\f[R], etc.) will work on all the remote
-storage systems.
+\f[V]sync\f[R], \f[V]copy\f[R], etc.)
+will work on all the remote storage systems.
 .SS Can I copy the config from one machine to another
 .PP
-Sure! Rclone stores all of its config in a single file.
-If you want to find this file, run \f[C]rclone config file\f[R] which
+Sure!
+Rclone stores all of its config in a single file.
+If you want to find this file, run \f[V]rclone config file\f[R] which
 will tell you where it is.
 .PP
 See the remote setup docs (https://rclone.org/remote_setup/) for more
@@ -87190,20 +87782,20 @@ Yes.
 rclone will follow the standard environment variables for proxies,
 similar to cURL and other programs.
 .PP
-In general the variables are called \f[C]http_proxy\f[R] (for services
-reached over \f[C]http\f[R]) and \f[C]https_proxy\f[R] (for services
-reached over \f[C]https\f[R]).
-Most public services will be using \f[C]https\f[R], but you may wish to
+In general the variables are called \f[V]http_proxy\f[R] (for services
+reached over \f[V]http\f[R]) and \f[V]https_proxy\f[R] (for services
+reached over \f[V]https\f[R]).
+Most public services will be using \f[V]https\f[R], but you may wish to
 set both.
 .PP
-The content of the variable is \f[C]protocol://server:port\f[R].
+The content of the variable is \f[V]protocol://server:port\f[R].
 The protocol value is the one used to talk to the proxy server, itself,
-and is commonly either \f[C]http\f[R] or \f[C]socks5\f[R].
+and is commonly either \f[V]http\f[R] or \f[V]socks5\f[R].
 .PP
 Slightly annoyingly, there is no \f[I]standard\f[R] for the name; some
-applications may use \f[C]http_proxy\f[R] but another one
-\f[C]HTTP_PROXY\f[R].
-The \f[C]Go\f[R] libraries used by \f[C]rclone\f[R] will try both
+applications may use \f[V]http_proxy\f[R] but another one
+\f[V]HTTP_PROXY\f[R].
+The \f[V]Go\f[R] libraries used by \f[V]rclone\f[R] will try both
 variations, but you may wish to set all possibilities.
 So, on Linux, you may end up with code similar to
 .IP
@@ -87227,7 +87819,7 @@ export HTTPS_PROXY=$http_proxy
 \f[R]
 .fi
 .PP
-The \f[C]NO_PROXY\f[R] allows you to disable the proxy for specific
+The \f[V]NO_PROXY\f[R] allows you to disable the proxy for specific
 hosts.
 Hosts must be comma separated, and can contain domains or parts.
 For instance \[dq]foo.com\[dq] also matches \[dq]bar.foo.com\[dq].
@@ -87241,12 +87833,12 @@ export NO_PROXY=$no_proxy
 \f[R]
 .fi
 .PP
-Note that the FTP backend does not support \f[C]ftp_proxy\f[R] yet.
+Note that the FTP backend does not support \f[V]ftp_proxy\f[R] yet.
 .SS Rclone gives x509: failed to load system roots and no roots provided error
 .PP
-This means that \f[C]rclone\f[R] can\[aq]t find the SSL root
+This means that \f[V]rclone\f[R] can\[aq]t find the SSL root
 certificates.
-Likely you are running \f[C]rclone\f[R] on a NAS with a cut-down Linux
+Likely you are running \f[V]rclone\f[R] on a NAS with a cut-down Linux
 OS, or possibly on Solaris.
 .PP
 Rclone (via the Go runtime) tries to load the root certificates from
@@ -87272,13 +87864,13 @@ ntpclient -s -h pool.ntp.org
 \f[R]
 .fi
 .PP
-The two environment variables \f[C]SSL_CERT_FILE\f[R] and
-\f[C]SSL_CERT_DIR\f[R], mentioned in the x509
+The two environment variables \f[V]SSL_CERT_FILE\f[R] and
+\f[V]SSL_CERT_DIR\f[R], mentioned in the x509
 package (https://godoc.org/crypto/x509), provide an additional way to
 provide the SSL root certificates.
 .PP
-Note that you may need to add the \f[C]--insecure\f[R] option to the
-\f[C]curl\f[R] command line if it doesn\[aq]t work without.
+Note that you may need to add the \f[V]--insecure\f[R] option to the
+\f[V]curl\f[R] command line if it doesn\[aq]t work without.
 .IP
 .nf
 \f[C]
@@ -87312,18 +87904,18 @@ dig www.googleapis.com \[at]8.8.8.8 # resolve with Google\[aq]s DNS server
 \f[R]
 .fi
 .PP
-If you are using \f[C]systemd-resolved\f[R] (default on Arch Linux),
+If you are using \f[V]systemd-resolved\f[R] (default on Arch Linux),
 ensure it is at version 233 or higher.
 Previous releases contain a bug which causes not all domains to be
 resolved properly.
 .PP
 The Go resolver decision can be influenced with the
-\f[C]GODEBUG=netdns=...\f[R] environment variable.
+\f[V]GODEBUG=netdns=...\f[R] environment variable.
 This also allows to resolve certain issues with DNS resolution.
 On Windows or MacOS systems, try forcing use of the internal Go resolver
-by setting \f[C]GODEBUG=netdns=go\f[R] at runtime.
+by setting \f[V]GODEBUG=netdns=go\f[R] at runtime.
 On other systems (Linux, *BSD, etc) try forcing use of the system name
-resolver by setting \f[C]GODEBUG=netdns=cgo\f[R] (and recompile rclone
+resolver by setting \f[V]GODEBUG=netdns=cgo\f[R] (and recompile rclone
 from source with CGO enabled if necessary).
 See the name resolution section in the go
 docs (https://golang.org/pkg/net/#hdr-Name_Resolution).
@@ -87363,7 +87955,7 @@ the heap size has doubled.
 .PP
 However it is possible to tune the garbage collector to use less memory
 by setting GOGC (https://dave.cheney.net/tag/gogc) to a lower value, say
-\f[C]export GOGC=20\f[R].
+\f[V]export GOGC=20\f[R].
 This will make the garbage collector work harder, reducing memory size
 at the expense of CPU usage.
 .PP
@@ -87377,10 +87969,10 @@ which involves a bit of scripting.
 .SS Rclone changes fullwidth Unicode punctuation marks in file names
 .PP
 For example: On a Windows system, you have a file with name
-\f[C]Test\[uFF1A]1.jpg\f[R], where \f[C]\[uFF1A]\f[R] is the Unicode
-fullwidth colon symbol.
+\f[V]Test：1.jpg\f[R], where \f[V]：\f[R] is the Unicode fullwidth colon
+symbol.
 When using rclone to copy this to your Google Drive, you will notice
-that the file gets renamed to \f[C]Test:1.jpg\f[R], where \f[C]:\f[R] is
+that the file gets renamed to \f[V]Test:1.jpg\f[R], where \f[V]:\f[R] is
 the regular (halfwidth) colon.
 .PP
 The reason for such renames is the way rclone handles different
@@ -87430,7 +88022,7 @@ Nick Craig-Wood <nick@craig-wood.com>
 .SS Contributors
 .PP
 {{< rem
-\f[C]email addresses removed from here need to be added to bin/.ignore-emails to make sure update-authors.py doesn\[aq]t immediately put them back in again.\f[R]
+\f[V]email addresses removed from here need to be added to bin/.ignore-emails to make sure update-authors.py doesn\[aq]t immediately put them back in again.\f[R]
 >}}
 .IP \[bu] 2
 Alex Couper <amcouper@gmail.com>
@@ -87445,7 +88037,7 @@ Klaus Post <klauspost@gmail.com>
 .IP \[bu] 2
 Sergey Tolmachev <tolsi.ru@gmail.com>
 .IP \[bu] 2
-Adriano Aur\['e]lio Meirelles <adriano@atinge.com>
+Adriano Aurélio Meirelles <adriano@atinge.com>
 .IP \[bu] 2
 C.
 Bess <cbess@users.noreply.github.com>
@@ -87454,7 +88046,7 @@ Dmitry Burdeev <dibu28@gmail.com>
 .IP \[bu] 2
 Joseph Spurrier <github@josephspurrier.com>
 .IP \[bu] 2
-Bj\[:o]rn Harrtell <bjorn@wololo.org>
+Björn Harrtell <bjorn@wololo.org>
 .IP \[bu] 2
 Xavier Lucas <xavier.lucas@corp.ovh.com>
 .IP \[bu] 2
@@ -87484,7 +88076,7 @@ Weichinger <office@oops.co.at>
 .IP \[bu] 2
 Per Cederberg <cederberg@gmail.com>
 .IP \[bu] 2
-Radek \[vS]enfeld <rush@logic.cz>
+Radek Šenfeld <rush@logic.cz>
 .IP \[bu] 2
 Fredrik Fornwall <fredrik@fornwall.net>
 .IP \[bu] 2
@@ -87496,7 +88088,7 @@ Tomasz Mazur <tmazur90@gmail.com>
 .IP \[bu] 2
 Marco Paganini <paganini@paganini.net>
 .IP \[bu] 2
-Felix B\[:u]nemann <buenemann@louis.info>
+Felix Bünemann <buenemann@louis.info>
 .IP \[bu] 2
 Durval Menezes <jmrclone@durval.com>
 .IP \[bu] 2
@@ -87512,7 +88104,7 @@ Thibault Molleman <thibaultmol@users.noreply.github.com>
 .IP \[bu] 2
 Scott McGillivray <scott.mcgillivray@gmail.com>
 .IP \[bu] 2
-Bj\[/o]rn Erik Pedersen <bjorn.erik.pedersen@gmail.com>
+Bjørn Erik Pedersen <bjorn.erik.pedersen@gmail.com>
 .IP \[bu] 2
 Lukas Loesche <lukas@mesosphere.io>
 .IP \[bu] 2
@@ -87525,7 +88117,7 @@ Brandur <brandur@mutelight.org>
 .IP \[bu] 2
 Dario Giovannetti <dev@dariogiovannetti.net>
 .IP \[bu] 2
-K\['a]roly Ol\['a]h <okaresz@aol.com>
+Károly Oláh <okaresz@aol.com>
 .IP \[bu] 2
 Jon Yergatian <jon@macfanatic.ca>
 .IP \[bu] 2
@@ -87535,7 +88127,7 @@ Dedsec1 <Dedsec1@users.noreply.github.com>
 .IP \[bu] 2
 Hisham Zarka <hzarka@gmail.com>
 .IP \[bu] 2
-J\['e]r\[^o]me Vizcaino <jerome.vizcaino@gmail.com>
+Jérôme Vizcaino <jerome.vizcaino@gmail.com>
 .IP \[bu] 2
 Mike Tesch <mjt6129@rit.edu>
 .IP \[bu] 2
@@ -87575,7 +88167,7 @@ Sjur Fredriksen <sjurtf@ifi.uio.no>
 .IP \[bu] 2
 Ruwbin <hubus12345@gmail.com>
 .IP \[bu] 2
-Fabian M\[:o]ller <fabianm88@gmail.com> <f.moeller@nynex.de>
+Fabian Möller <fabianm88@gmail.com> <f.moeller@nynex.de>
 .IP \[bu] 2
 Edward Q.
 Bridges <github@eqbridges.com>
@@ -87603,7 +88195,7 @@ wuyu <wuyu@yunify.com>
 .IP \[bu] 2
 Andrei Dragomir <adragomi@adobe.com>
 .IP \[bu] 2
-Christian Br\[:u]ggemann <mail@cbruegg.com>
+Christian Brüggemann <mail@cbruegg.com>
 .IP \[bu] 2
 Alex McGrath Kraak <amkdude@gmail.com>
 .IP \[bu] 2
@@ -87783,7 +88375,7 @@ reddi1 <xreddi@gmail.com>
 .IP \[bu] 2
 Matt Tucker <matthewtckr@gmail.com>
 .IP \[bu] 2
-Sebastian B\[:u]nger <buengese@gmail.com> <buengese@protonmail.com>
+Sebastian Bünger <buengese@gmail.com> <buengese@protonmail.com>
 .IP \[bu] 2
 Martin Polden <mpolden@mpolden.no>
 .IP \[bu] 2
@@ -87793,7 +88385,7 @@ Denis <deniskovpen@gmail.com>
 .IP \[bu] 2
 bsteiss <35940619+bsteiss@users.noreply.github.com>
 .IP \[bu] 2
-C\['e]dric Connes <cedric.connes@gmail.com>
+Cédric Connes <cedric.connes@gmail.com>
 .IP \[bu] 2
 Dr.
 Tobias Quathamer <toddy15@users.noreply.github.com>
@@ -87810,7 +88402,7 @@ Anagh Kumar Baranwal <6824881+darthShadow@users.noreply.github.com>
 .IP \[bu] 2
 Felix Brucker <felix@felixbrucker.com>
 .IP \[bu] 2
-Santiago Rodr\['i]guez <scollazo@users.noreply.github.com>
+Santiago Rodríguez <scollazo@users.noreply.github.com>
 .IP \[bu] 2
 Craig Miskell <craig.miskell@fluxfederation.com>
 .IP \[bu] 2
@@ -87864,7 +88456,7 @@ Mark Otway <mark@otway.com>
 .IP \[bu] 2
 William Cocker <37018962+WilliamCocker@users.noreply.github.com>
 .IP \[bu] 2
-Fran\[,c]ois Leurent <131.js@cloudyks.org>
+François Leurent <131.js@cloudyks.org>
 .IP \[bu] 2
 Arkadius Stefanski <arkste@gmail.com>
 .IP \[bu] 2
@@ -87886,7 +88478,7 @@ Matt Robinson <brimstone@the.narro.ws>
 .IP \[bu] 2
 kayrus <kay.diam@gmail.com>
 .IP \[bu] 2
-R\['e]my L\['e]one <remy.leone@gmail.com>
+Rémy Léone <remy.leone@gmail.com>
 .IP \[bu] 2
 Wojciech Smigielski <wojciech.hieronim.smigielski@gmail.com>
 .IP \[bu] 2
@@ -87910,7 +88502,7 @@ Dr.Rx <david.rey@nventive.com>
 .IP \[bu] 2
 marcintustin <marcintustin@users.noreply.github.com>
 .IP \[bu] 2
-jaKa Mo\[u010D]nik <jaka@koofr.net>
+jaKa Močnik <jaka@koofr.net>
 .IP \[bu] 2
 Fionera <fionera@fionera.de>
 .IP \[bu] 2
@@ -87951,7 +88543,7 @@ forgems <forgems@gmail.com>
 .IP \[bu] 2
 Florian Apolloner <florian@apolloner.eu>
 .IP \[bu] 2
-Aleksandar Jankovi\['c] <office@ajankovic.com>
+Aleksandar Janković <office@ajankovic.com>
 <ajankovic@users.noreply.github.com>
 .IP \[bu] 2
 Maran <maran@protonmail.com>
@@ -87980,7 +88572,7 @@ justina777 <chiahuei.lin@gmail.com>
 .IP \[bu] 2
 Chaitanya Bankanhal <bchaitanya15@gmail.com>
 .IP \[bu] 2
-Micha\[/l] Matczuk <michal@scylladb.com>
+Michał Matczuk <michal@scylladb.com>
 .IP \[bu] 2
 Macavirus <macavirus@zoho.com>
 .IP \[bu] 2
@@ -88010,7 +88602,7 @@ Anthony Rusdi <33247310+antrusd@users.noreply.github.com>
 .IP \[bu] 2
 Richard Patel <me@terorie.dev>
 .IP \[bu] 2
-\[u5E84]\[u5929]\[u7FFC] <zty0826@gmail.com>
+庄天翼 <zty0826@gmail.com>
 .IP \[bu] 2
 SwitchJS <dev@switchjs.com>
 .IP \[bu] 2
@@ -88066,7 +88658,7 @@ Thomas Kriechbaumer <thomas@kriechbaumer.name>
 .IP \[bu] 2
 Tennix <tennix@users.noreply.github.com>
 .IP \[bu] 2
-Ole Sch\[:u]tt <ole@schuett.name>
+Ole Schütt <ole@schuett.name>
 .IP \[bu] 2
 Kuang-che Wu <kcwu@csie.org>
 .IP \[bu] 2
@@ -88110,7 +88702,7 @@ Shing Kit Chan <chanshingkit@gmail.com>
 .IP \[bu] 2
 Franklyn Tackitt <franklyn@tackitt.net>
 .IP \[bu] 2
-Robert-Andr\['e] Mauchin <zebob.m@gmail.com>
+Robert-André Mauchin <zebob.m@gmail.com>
 .IP \[bu] 2
 evileye <48332831+ibiruai@users.noreply.github.com>
 .IP \[bu] 2
@@ -88124,7 +88716,7 @@ greatroar <\[at]>
 .IP \[bu] 2
 Bernd Schoolmann <mail@quexten.com>
 .IP \[bu] 2
-Elan Ruusam\[:a]e <glen@pld-linux.org>
+Elan Ruusamäe <glen@pld-linux.org>
 .IP \[bu] 2
 Max Sum <max@lolyculture.com>
 .IP \[bu] 2
@@ -88160,7 +88752,7 @@ ElonH <elonhhuang@gmail.com>
 .IP \[bu] 2
 Fred <fred@creativeprojects.tech>
 .IP \[bu] 2
-S\['e]bastien Gross <renard@users.noreply.github.com>
+Sébastien Gross <renard@users.noreply.github.com>
 .IP \[bu] 2
 Maxime Suret <11944422+msuret@users.noreply.github.com>
 .IP \[bu] 2
@@ -88182,7 +88774,7 @@ edwardxml <56691903+edwardxml@users.noreply.github.com>
 .IP \[bu] 2
 Roman Kredentser <shareed2k@gmail.com>
 .IP \[bu] 2
-Kamil Trzci\[u0144]ski <ayufan@ayufan.eu>
+Kamil Trzciński <ayufan@ayufan.eu>
 .IP \[bu] 2
 Zac Rubin <z-0@users.noreply.github.com>
 .IP \[bu] 2
@@ -88198,7 +88790,7 @@ Petri Salminen <petri@salminen.dev>
 .IP \[bu] 2
 Tim Burke <tim.burke@gmail.com>
 .IP \[bu] 2
-Kai L\[:u]ke <kai@kinvolk.io>
+Kai Lüke <kai@kinvolk.io>
 .IP \[bu] 2
 Garrett Squire <github@garrettsquire.com>
 .IP \[bu] 2
@@ -88264,7 +88856,7 @@ David <david@staron.nl>
 .IP \[bu] 2
 Ingo <ingo@hoffmann.cx>
 .IP \[bu] 2
-Adam Pl\['a]nsk\['y] <adamplansky@users.noreply.github.com>
+Adam Plánský <adamplansky@users.noreply.github.com>
 <adamplansky@gmail.com>
 .IP \[bu] 2
 Manish Gupta <manishgupta.ait@gmail.com>
@@ -88313,11 +88905,11 @@ Denis Neuling <denisneuling@gmail.com>
 .IP \[bu] 2
 Janne Johansson <icepic.dz@gmail.com>
 .IP \[bu] 2
-Patrik Nordl\['e]n <patriki@gmail.com>
+Patrik Nordlén <patriki@gmail.com>
 .IP \[bu] 2
 CokeMine <aptx4561@gmail.com>
 .IP \[bu] 2
-S\[u01A1]n Tr\[u1EA7]n-Nguy\[u1EC5]n <github@sntran.com>
+Sơn Trần-Nguyễn <github@sntran.com>
 .IP \[bu] 2
 lluuaapp <266615+lluuaapp@users.noreply.github.com>
 .IP \[bu] 2
@@ -88467,7 +89059,7 @@ Jonta <359397+Jonta@users.noreply.github.com>
 .IP \[bu] 2
 YenForYang <YenForYang@users.noreply.github.com>
 .IP \[bu] 2
-SimJoSt / Joda St\[:o]\[ss]er <git@simjo.st>
+SimJoSt / Joda Stößer <git@simjo.st>
 .IP \[bu] 2
 Logeshwaran <waranlogesh@gmail.com>
 .IP \[bu] 2
@@ -88493,9 +89085,9 @@ David Liu <david.yx.liu@oracle.com>
 .IP \[bu] 2
 Chris Nelson <stuff@cjnaz.com>
 .IP \[bu] 2
-Felix Bu\[u0308]nemann <felix.buenemann@gmail.com>
+Felix Bünemann <felix.buenemann@gmail.com>
 .IP \[bu] 2
-At\['i]lio Ant\[^o]nio <atiliodadalto@hotmail.com>
+Atílio Antônio <atiliodadalto@hotmail.com>
 .IP \[bu] 2
 Carlo Mion <mion00@gmail.com>
 .IP \[bu] 2
@@ -88557,7 +89149,7 @@ Eng Zer Jun <engzerjun@gmail.com>
 .IP \[bu] 2
 Abhiraj <abhiraj.official15@gmail.com>
 .IP \[bu] 2
-M\['a]rton Elek <elek@apache.org> <elek@users.noreply.github.com>
+Márton Elek <elek@apache.org> <elek@users.noreply.github.com>
 .IP \[bu] 2
 Vincent Murphy <vdm@vdm.ie>
 .IP \[bu] 2
@@ -88591,7 +89183,7 @@ ehsantdy <ehsan.tadayon@arvancloud.com> <ehsantadayon85@gmail.com>
 .IP \[bu] 2
 SwazRGB <65694696+swazrgb@users.noreply.github.com>
 .IP \[bu] 2
-Mateusz Puczyn\[u0301]ski <mati6095@gmail.com>
+Mateusz Puczyński <mati6095@gmail.com>
 .IP \[bu] 2
 Michael C Tiernan - MIT-Research Computing Project <mtiernan@mit.edu>
 .IP \[bu] 2
@@ -88676,13 +89268,13 @@ Yen Hu <61753151+0x59656e@users.noreply.github.com>
 .IP \[bu] 2
 Steve Kowalik <steven@wedontsleep.org>
 .IP \[bu] 2
-Jordi Gonzalez Mu\[~n]oz <jordigonzm@gmail.com>
+Jordi Gonzalez Muñoz <jordigonzm@gmail.com>
 .IP \[bu] 2
 Joram Schrijver <i@joram.io>
 .IP \[bu] 2
 Mark Trolley <marktrolley@gmail.com>
 .IP \[bu] 2
-Jo\[~a]o Henrique Franco <joaohenrique.franco@gmail.com>
+João Henrique Franco <joaohenrique.franco@gmail.com>
 .IP \[bu] 2
 anonion <aman207@users.noreply.github.com>
 .IP \[bu] 2
@@ -88693,7 +89285,7 @@ Simon Bos <simonbos9@gmail.com>
 YFdyh000 <yfdyh000@gmail.com> * Josh Soref
 <2119212+jsoref@users.noreply.github.com>
 .IP \[bu] 2
-\[/O]yvind Heddeland Instefjord <instefjord@outlook.com>
+Øyvind Heddeland Instefjord <instefjord@outlook.com>
 .IP \[bu] 2
 Dmitry Deniskin <110819396+ddeniskin@users.noreply.github.com>
 .IP \[bu] 2
@@ -88730,7 +89322,7 @@ Philip Harvey <pharvey@battelleecology.org>
 .IP \[bu] 2
 dgouju <dgouju@users.noreply.github.com>
 .IP \[bu] 2
-Cl\['e]ment Notin <clement.notin@gmail.com>
+Clément Notin <clement.notin@gmail.com>
 .IP \[bu] 2
 x3-apptech <66947598+x3-apptech@users.noreply.github.com>
 .IP \[bu] 2
@@ -88858,7 +89450,7 @@ dlitster <davidlitster@gmail.com>
 .IP \[bu] 2
 Tobias Gion <tobias@gion.io>
 .IP \[bu] 2
-J\[u0101]nis Bebr\[u012B]tis <janis.bebritis@wunder.io>
+Jānis Bebrītis <janis.bebritis@wunder.io>
 .IP \[bu] 2
 Adam K <github.com@ak.tidy.email>
 .IP \[bu] 2
@@ -88919,7 +89511,7 @@ Tiago Boeing <contato@tiagoboeing.com>
 .IP \[bu] 2
 Edwin Mackenzie-Owen <edwin.mowen@gmail.com>
 .IP \[bu] 2
-Niklas Hamb\[:u]chen <mail@nh2.me>
+Niklas Hambüchen <mail@nh2.me>
 .IP \[bu] 2
 yuudi <yuudi@users.noreply.github.com>
 .IP \[bu] 2
@@ -88951,7 +89543,7 @@ hideo aoyama <100831251+boukendesho@users.noreply.github.com>
 .IP \[bu] 2
 Roberto Ricci <io@r-ricci.it>
 .IP \[bu] 2
-Bj\[/o]rn Smith <bjornsmith@gmail.com>
+Bjørn Smith <bjornsmith@gmail.com>
 .IP \[bu] 2
 Alishan Ladhani <8869764+aladh@users.noreply.github.com>
 .IP \[bu] 2
@@ -89021,11 +89613,11 @@ viktor <viktor@yakovchuk.net>
 .IP \[bu] 2
 moongdal <moongdal@tutanota.com>
 .IP \[bu] 2
-Mina Gali\['c] <freebsd@igalic.co>
+Mina Galić <freebsd@igalic.co>
 .IP \[bu] 2
-Alen \[vS]iljak <dev@alensiljak.eu.org>
+Alen Šiljak <dev@alensiljak.eu.org>
 .IP \[bu] 2
-\[u4F60]\[u77E5]\[u9053]\[u672A]\[u6765]\[u5417] <rkonfj@gmail.com>
+你知道未来吗 <rkonfj@gmail.com>
 .IP \[bu] 2
 Abhinav Dhiman <8640877+ahnv@users.noreply.github.com>
 .IP \[bu] 2
@@ -89055,7 +89647,7 @@ Kyle Reynolds <kylereynoldsdev@gmail.com>
 .IP \[bu] 2
 Michael Eischer <michael.eischer@gmx.de>
 .IP \[bu] 2
-Thomas M\[:u]ller <1005065+DeepDiver1975@users.noreply.github.com>
+Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
 .IP \[bu] 2
 DanielEgbers <27849724+DanielEgbers@users.noreply.github.com>
 .IP \[bu] 2
@@ -89131,7 +89723,7 @@ JT Olio <jt@olio.lol>
 .IP \[bu] 2
 Evan McBeth <64177332+AtomicRobotMan0101@users.noreply.github.com>
 .IP \[bu] 2
-Dominik Joe Pant\[u016F]\[u010D]ek <dominik.pantucek@trustica.cz>
+Dominik Joe Pantůček <dominik.pantucek@trustica.cz>
 .IP \[bu] 2
 yumeiyin <155420652+yumeiyin@users.noreply.github.com>
 .IP \[bu] 2
@@ -89143,7 +89735,7 @@ Charles Hamilton <52973156+chamilton-ccn@users.noreply.github.com>
 .IP \[bu] 2
 Tomasz Melcer <tomasz@melcer.pl>
 .IP \[bu] 2
-Micha\[/l] Dzienisiewicz <michal.piotr.dz@gmail.com>
+Michał Dzienisiewicz <michal.piotr.dz@gmail.com>
 .IP \[bu] 2
 Florian Klink <flokli@flokli.de>
 .IP \[bu] 2
@@ -89177,7 +89769,7 @@ Fornax <wimbrand96@gmail.com>
 .IP \[bu] 2
 Sam Harrison <sam.harrison@files.com>
 .IP \[bu] 2
-P\['e]ter Bozs\['o] <3806723+peterbozso@users.noreply.github.com>
+Péter Bozsó <3806723+peterbozso@users.noreply.github.com>
 .IP \[bu] 2
 Georg Welzel <gwelzel@mailbox.org>
 .IP \[bu] 2
@@ -89221,7 +89813,7 @@ There you can file bug reports or contribute with pull requests.
 .PP
 You can also follow Nick on twitter for rclone announcements:
 .IP \[bu] 2
-[\[at]njcw](https://twitter.com/njcw)
+\[at]njcw (https://twitter.com/njcw)
 .SS Email
 .PP
 Or if all else fails or you want to ask something private or