Monterey Messages App: Selecting Multiple Texts in Messages App

[southerndoc]

When I moved from Catalina to Big Sur, I noticed that the Messages app no longer allows one to select multiple messages for deletion. As someone who receives numerous texts throughout the day, it became aggravating to delete messages on my computer as opposed to deleting in iOS (which still allows selecting multiple messages). Perhaps I've overlooked how to select multiple messages, and if so, I would appreciate if someone points me how to do it in Big Sur.

Does Monterey bring back the ability to select multiple messages?

 

[Ritsuka]

You can use the usual key modifiers: cmd-click to manually select multiple messages, or select a message, and shift-click on another down below or up to select a contiguous number of messages.

 

[southerndoc]

You can use the usual key modifiers: cmd-click to manually select multiple messages, or select a message, and shift-click on another down below or up to select a contiguous number of messages.

Those don't work with Big Sur.

 

[Ritsuka]

But they do work on Monterey

 

[Ritsuka]

And on Big Sur too, I just tried.

 

[southerndoc]

And on Big Sur too, I just tried.

Sorry, my original post said selecting multiple messages. After your post that you can do it in Big Sur, I realized that I should have said message recipients and not messages.

I can select multiple messages within a thread. I'm trying to mass delete conversations. The names that appear on the left of the window (sidebar area). I want to delete multiple threads/conversations/recipients at one time instead of deleting each one individually.

Sorry for the confusion.

 

[Ritsuka]

Yup it's not possible to delete multiple conversations.

 

[IzzyMandelbaum]

Yup it's not possible to delete multiple conversations.

It's 2022 and you still can't delete multiple conversations at once..that in my opinion is something Apple should have allowed a LONG time ago and it's ridiculous that you still can't.

 

[tgrutkow]

Does anyone have a new answer to this question? Has it been fixed? Is there a workaround?