Closed Bug 279898 Opened 20 years ago Closed 15 years ago

[RFE] middle-clicking (or ctrl+click) on a newsgroup/folder name should mark all messages as read

Categories

(Thunderbird :: Mail Window Front End, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: pascalc, Unassigned)

Details

One thing I'd love to have is the possibility to mark a whole folder/newsgroup
as read with a middle-click on its name.

I have subscribed to more than 50 newsgroups in Thunderbrid and sometimes I just
don't read some of them for a period of time and I right-click/select mark as
read for 15 or 20 newsgroups every day. I'd like to middle-click on the
newsgroup name (or a folder name for the Mail part of thunderbird) to mark it
quickly as read.
An alternative approach would be to add a "Unread" column similar to that in the 
thread pane for a message, which you could click on to mark the group read.
Summary: [RFE] midle-clicking (or ctrl+click) on a newsgroup/folder name should mark all messages as read → [RFE] middle-clicking (or ctrl+click) on a newsgroup/folder name should mark all messages as read
both are kind of clunky.  try selecting the newsgroup and hitting shift + c.  ;)
Oh man - ever since moving to Thunderbird on Linux from Mozilla 1.7.12 on an older Linux, the missing Shift-Ctrl-C has been killing me.  I finally decided to see if anyone had filed a bug on this yet, only to see Ryan's comment here.  I'm saved.  Thank you for posting the info.  The correct keyboard shortcut has been impossible to find via google over the past 2 months and the mouse-clicks were killing me.
QA Contact: front-end
I would ideally like to be able to select a *folder* that contains unread messages in the folder pane and press 'm' to mark the folder read, just as pressing 'm' when a *message* is selected toggles the read/unread status of the message.
Assignee: mscott → nobody
->WONTFIX, as middle click is now open in new tab
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.