[DOCS] Make it more obvious that $:/DefaultTiddlers setting can handle filter-expressions #8729
Conversation
|
Confirmed: pmario has already signed the Contributor License Agreement (see contributing.md) |
| There are two ways default tiddlers can be defined: | ||
|
|
||
| * A [[title-list|Title List]] eg: `TiddlerTitles` and `[[Titles with spaces]]` | ||
| * Filter expressions, using [[filter operators|Filter Operators]] eg: `[tag[HelloThere]]` | ||
|
|
||
| At startup, the text of the system tiddler [[$:/DefaultTiddlers]] is retrieved and evaluated as a [[filter expression|Filter Expression]]. The resulting list of titles is then inserted into the [[story river|Story River]]. |
There was a problem hiding this comment.
I feel that we already explain here that a filter expression can be used to specify the default tiddlers. Perhaps we should consider rewriting this paragraph to further emphasize that, rather than add the paragraph above?
There was a problem hiding this comment.
Perhaps we should consider rewriting this paragraph to further emphasize that, rather than add the paragraph above?
The paragraph has been there for years and extracting the information that DefaultTiddlers can handle filter expressions is not obvious and hard to find, as can be seen at the discussion at Talk
A bullet-list attracts attention to the points that are important. I did not want to remove the paragraph, because I think its OK to explain functions in different ways for different users.
But English is not my main language. So I would be happy for an example.
…e filter-expressions
pmario
force-pushed
the
docs-make-it-more-obvious-that-defaulttiddlers-setting-can-handle-filter-expressions-20241104160223730
branch
from
0466011
to
7aacf9b
Compare
Make it more obvious that $:/DefaultTiddlers setting can handle filter-expressions
Edit: Fixing some typos