13 - Feature request: Sort by modification date, treating folder and files equally
- syntax reference update
This commit is contained in:
parent
72550fc01d
commit
afa10afd7d
|
@ -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)
|
||||
|
||||
|
|
Loading…
Reference in New Issue