From 9dbfd9d8523104785969c9283c1db09b3d044851 Mon Sep 17 00:00:00 2001 From: shaurya Date: Wed, 26 Aug 2026 22:12:57 +0530 Subject: [PATCH] docs: fix broken links and wrong s3 directory bucket flag name Several documentation links pointed at anchors or paths that no longer resolve, and the S3 directory buckets section named the config option and flag in the plural, which does not match the backend. Co-authored-by: shaurya <19599684+no-hup@users.noreply.github.com> Co-authored-by: no-hup --- docs/content/bisync.md | 4 ++-- docs/content/docs.md | 3 ++- docs/content/s3.md | 6 +++--- docs/content/sftp.md | 2 +- 4 files changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/content/bisync.md b/docs/content/bisync.md index a7dff19ee..6198378cd 100644 --- a/docs/content/bisync.md +++ b/docs/content/bisync.md @@ -1961,7 +1961,7 @@ and far less prone to critical errors / undetected changes - 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. - A few basic terminal colors are now supported, controllable with -[`--color`](/docs/#color) (`AUTO`|`NEVER`|`ALWAYS`) +[`--color`](/docs/#color-autoneveralways) (`AUTO`|`NEVER`|`ALWAYS`) - Initial listing snapshots of Path1 and Path2 are now generated concurrently, using the same "march" infrastructure as `check` and `sync`, for performance improvements and less @@ -1991,7 +1991,7 @@ behavior with new [`--conflict-resolve`](#conflict-resolve), [`--conflict-suffix`](#conflict-suffix) flags. - A new [`--resync-mode`](#resync-mode) flag allows more control over which version of a file gets kept during a `--resync`. -- Bisync now supports [`--retries`](/docs/#retries-int) and [`--retries-sleep`](/docs/#retries-sleep-time) +- Bisync now supports [`--retries`](/docs/#retries-int) and [`--retries-sleep`](/docs/#retries-sleep-duration) (when [`--resilient`](#resilient) is set.) ### `v1.64` diff --git a/docs/content/docs.md b/docs/content/docs.md index 14d563c32..ec57c4899 100644 --- a/docs/content/docs.md +++ b/docs/content/docs.md @@ -1043,7 +1043,8 @@ will use this much memory for buffering. When using `mount` or `cmount` each open file descriptor will use this much memory for buffering. -See the [mount](/commands/rclone_mount/#file-buffering) documentation for more details. +See the [mount](/commands/rclone_mount/#vfs-file-buffering) documentation for +more details. Set to `0` to disable the buffering for the minimum memory usage. diff --git a/docs/content/s3.md b/docs/content/s3.md index 32d970ff4..98962229d 100644 --- a/docs/content/s3.md +++ b/docs/content/s3.md @@ -4839,15 +4839,15 @@ section above. From rclone v1.69 [Directory Buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/directory-buckets-overview.html) are supported. -You will need to set the `directory_buckets = true` config parameter -or use `--s3-directory-buckets`. +You will need to set the `directory_bucket = true` config parameter +or use `--s3-directory-bucket`. Note that rclone cannot yet: - Create directory buckets - List directory buckets -See [the --s3-directory-buckets flag](#s3-directory-buckets) for more info +See [the --s3-directory-bucket flag](#s3-directory-bucket) for more info ### AWS Snowball Edge diff --git a/docs/content/sftp.md b/docs/content/sftp.md index 8dd730f62..f15188483 100644 --- a/docs/content/sftp.md +++ b/docs/content/sftp.md @@ -442,7 +442,7 @@ correct, and support all features. 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 [on the fly](/docs/#backend-path-to-dir]) +without a config file, e.g. an [on the fly](/docs/#backend-path-to-dir) 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 `shell_type` option to the correct value,