Skip to content

Commit 200333f

Browse files
committed
13 - Feature request: Sort by modification date, treating folder and files equally
- README.md update, adjusted one of examples to use the `> advanced modified` sorting method
1 parent afa10af commit 200333f

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

README.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -359,8 +359,9 @@ the result is:
359359

360360
### Example 12: Apply same sorting to all folders in the vault
361361

362-
Apply the alphabetical sorting to all folders in the Vault. The alphabetical sorting treats the folders and files equally
363-
(which is different from the standard Obsidian sort, which groups folders in the top of File Explorer)
362+
Apply the same advanced modified date sorting to all folders in the Vault. The advanced modified sorting treats the folders
363+
and files equally (which is different from the standard Obsidian sort, which groups folders in the top of File Explorer)
364+
The modified date for a folder is derived from its newest direct child file (if any), otherwise a folder is considered old
364365

365366
This involves the wildcard suffix syntax `*` which means _apply the sorting rule to the specified folder
366367
and all of its subfolders, including descendants. In other words, this is imposing a deep inheritance
@@ -371,7 +372,7 @@ Applying the wildcard suffix to root folder path `/*` actually means _apply the
371372
---
372373
sorting-spec: |
373374
target-folder: /*
374-
< a-z
375+
> advanced modified
375376
---
376377
```
377378

0 commit comments

Comments
 (0)