/rageshake command shouldn't cause timeline to jump to latest message #21065
Assignees
Labels
A-Slash-Commands
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
T-Enhancement
Comments
dbkr
added
A-Slash-Commands
O-Uncommon
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Your use case
What would you like to do?
Normally cause sending new message to jump to latest message, but in the case of /rageshake, not change the timeline view
Why would you like to do it?
Because a /rageshake doesn't actually send anything to the timeline and it's convenient to be able to rageshake in the moment of experiencing an issue without finishing reading back log of messages. When the timeline jumps, I lose my place in the backlog, which is especially problematic when catching up on a week of messages in an active room.
How would you like to achieve it?
Make the /rageshake command an exception to "jump to latest message in timeline on sending message".
The text was updated successfully, but these errors were encountered: