After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 614896 - delete a collapsed conversation with one delete command
delete a collapsed conversation with one delete command
Status: RESOLVED DUPLICATE of bug 262328
Product: evolution
Classification: Applications
Component: Mailer
3.6.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 663978 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-04-05 17:57 UTC by acampolonghi
Modified: 2017-11-30 11:55 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description acampolonghi 2010-04-05 17:57:46 UTC
Would be really usefull to be able to delete a collapsed conversation with one delete command. Now I have to select all the conversation messages.


Distribution: Ubuntu 9.10 (karmic)
Gnome Release: 2.28.1 2009-11-03 (Ubuntu)
BugBuddy Version: 2.28.0
Comment 1 Akhil Laddha 2011-11-14 03:57:00 UTC
*** Bug 663978 has been marked as a duplicate of this bug. ***
Comment 2 Máirín Duffy 2012-06-11 03:32:53 UTC
Just want to pile onto this bug. I have some threads that are 100's of messages long and I have no interest in the topic (but lots of interest in other threads on the list) and it is really a hassle to have to try to search the thread subject and delete all that way, especially when the search terms I used to try to search the thread subject match other important emails that I then end up deleting overzealously and have to work to recover....

Please please please consider this as a feature. :)
Comment 3 Matthew Barnes 2012-06-11 03:43:06 UTC
You can already select an entire message thread with Folder -> Select Message Thread (Ctrl+H).  It works whether the thread is collapsed or not.  Then press Delete.

I don't really see the need for a dedicated command when it's already just two steps.
Comment 4 Máirín Duffy 2012-06-11 04:04:24 UTC
Ah, sweet, I will try that out! (I was looking for something like this under Edit, Message, or View and didn't think to look under folder.) Thanks!
Comment 5 Máirín Duffy 2012-06-11 04:09:24 UTC
Hi Matt, so that doesn't work so well. When you have several such threads, it quickly becomes tedious because you hit Ctrl+H and delete, then the scrollbar jumps to the bottom of the window, when perhaps the thread you were trying to delete was a ways up. I would imagine it would be a lot less jarring / unwieldy to jump to the next thread that was immediately after the deleted thread.

Worth filing another bug?
Comment 6 Matthew Barnes 2012-06-11 04:15:23 UTC
I'd say so.  Smarter behavior after deleting a group of messages in general, whether a full thread or not, would be desirable.  If you could provide one or two specific cases and expected behaviors, that would be helpful.
Comment 7 Máirín Duffy 2012-06-11 14:16:17 UTC
Hi Matt, I just filed bug 677862, so I think maybe this could be closed or set to dependent on that one?
Comment 8 Máirín Duffy 2012-06-11 18:47:04 UTC
Okay after trying to use the Ctrl+H trick for a day I've run into another issue -

There was a long-winded thread I did Ctrl+H and delete on last night. Today, it's resurfaced again with fresh emails, about 10 of them, but I killed the 'parent node' of the conversation, so they aren't getting threaded by Evo even though they are all replies to the same thread. So the Ctrl+H trick doesn't work. :( Another bug?
Comment 9 Matthew Barnes 2012-06-11 19:02:21 UTC
Well, Select Message Thread (Ctrl+H) followed by Delete does exactly what it says and nothing more.  It sounds like you were expecting newly-received messages in that same thread to be automatically marked for deletion or something?

We don't have an "ignore thread" capability at the moment, though it may be possible to simulate by adding a filter on incoming messages.  But that would be a pain to do every time a discussion thread gets out of hand.
Comment 10 Máirín Duffy 2012-06-11 19:06:11 UTC
Hi Matt, I think you misunderstood what I was saying, which I apologize for not explaining very well -

I wasn't expecting new messages in the thread to be deleting automatically. Rather, I was expecting 'Select Message thread' to continue to work, even though I deleted some of the 'parent nodes' of the thread already. Does that make sense? Evo should be able to link the 10 or so new messages as being part of the same thread from the message id's and subject lines (which are identical) I would think, but it doesn't seem to understand they are from the same thread, so since I 'broke' the thread by deleting the parent node I can't select messages from that thread anymore.

Does that make sense?
Comment 11 Matthew Barnes 2012-06-11 19:26:48 UTC
Oh okay, I think I understand now.

I could see an argument for associating messages in a thread regardless of whether the parent is marked for deletion or not.

To be honest I don't use threading much myself because I find it confusing, so I'm not sure if using the thread ID of a deleted parent message would violate some unwritten threading convention.  To me it makes sense to use it.

I guess I can play around with some other mailers and see how they behave.
Comment 12 Milan Crha 2017-11-30 11:55:47 UTC
This is covered with a change in bug #262328, thus I mark this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 262328 ***