The discussion revolves around a new search feature in Discourse that allows users to order search results by the date they last read topics using the order:read modifier (shortcut r). sam announced the update, explaining that typing docker r in the search field will prioritize topics the user has recently read. However, meglio encountered confusion, as the results weren’t ordered as expected. martin clarified that pressing Enter after the search term is required. sam acknowledged a bug in full-page search that may have caused the issue and mentioned a fix in progress. meglio also suggested that users need clearer visual feedback to confirm that modifiers like r are recognized and to understand valid search options. sam responded by noting that l and r are power-user features and mentioned a fix for edge cases in the code.
We just landed a change to search (and filter) that lets you easily find your recently read.
Some of you know about order:latest (shortcut l), which allows you to order by the date the post was created.
The new sort order:read (shortcut r) allows you to order the results based on topics you recently read.
So if you happened to read about a topic about Docker in the past month and need to quickly bring it up, typing docker r in the search field will find it.
Ah okay, but there should be a visual indication in the list about how the results are ordered, no? And in general, how do I know that Discourse understood my “r” as a modifier? There should be some visual indication.
What if I forgot what modifiers are valid, are using an invalid one, and there is no way to find out that my letter in the request does not have any special meaning.
Do you mind opening a new feature request on this … this is the same issue “l” alias had forever. l and r are power user features order:read takes longer to type.
