From afa10afd7d90bdc5cac55677ed56e2ff74694823 Mon Sep 17 00:00:00 2001 From: SebastianMC Date: Mon, 26 Sep 2022 19:06:20 +0200 Subject: [PATCH] 13 - Feature request: Sort by modification date, treating folder and files equally - syntax reference update --- docs/syntax-reference.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/syntax-reference.md b/docs/syntax-reference.md index 6c6618a..6f465fc 100644 --- a/docs/syntax-reference.md +++ b/docs/syntax-reference.md @@ -20,7 +20,11 @@ - `< advanced modified` - by modified time, the long untouched item goes first. For folders, their modification date is derived from the most recently modified direct child file. For extremely large vaults use with caution, as the sorting needs to scan all files inside a folder to determine the folder's modified date - `> advanced modified` - by modified time reverse, the most recently modified item goes first. For folders, their modification date is derived from the most recently modified direct child file. - For extremely large vaults use with caution, as the sorting needs to scan all files inside a folder to determine the folder's modified date + For extremely large vaults use with caution, as the sorting needs to scan all files inside a folder to determine the folder's modified date +- `< advanced created` - by created time, the oldest item goes first. For folders, their creation date is derived from the oldest direct child file. + For extremely large vaults use with caution, as the sorting needs to scan all files inside a folder to determine the folder's created date +- `> advanced created` - by created time reverse, the newest item goes first. For folders, their creation date is derived from the newest direct child file. + For extremely large vaults use with caution, as the sorting needs to scan all files inside a folder to determine the folder's created date #### At group level only (aka secondary sorting rule)