Using `n` should move between topics by recency
When cycling through unread topics using n, this is not always sorted by the order in the topic list, ie. by most recent new message to a topic.
For discussion on related issues, see the topic in # zulip-terminal starting Improve algorithm for 'next unread topic' (n) #T1333 #T1356.
This behavior should be noticeable compared to when using the web app.
Using 'Explore' mode may be useful to ensure you don't keep marking messages lots of messages read during manual testing.
hey @neiljp can i work on this issue
@sahith-ch , are you working on this?
Yes am working on it
@zulipbot claim
Welcome to Zulip, @K-Preetham-Reddy! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
- Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
- Unwatch this repository, so that you don't get 100 emails a day.
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!