76398 - when reading a newsgroup, the "Get Msg" button should contain the current newsgroup

Status: NEW

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[(not reading, please use [e-mail] instead)]

when reading news on a newsgroup, the "Get Msg" button will get the new articles
from the server.

but the current newsgroup doesn't show up when you click on the twisty on the
"Get Msg" button.

can we make it so we dynamically add the current newsgroup to the list of
accounts that show up when you do click on the twisty that shows up on the "Get
Msg" button?

we should make it so doing "Get All New Messages" gets the new messages for the
current newsgroup group (if it doesn't already).

Comment 1

[[e-mail] (gone - use [e-mail] instead)]

Section two of the URL above states: * The "Get Msg" dropdown menu only shows
MAIL accounts, not News accounts.  (You don't get messages from a news account,
you get them from a newsgroup. Showing all the newsgroups a user is subscribed
to in the menu would make it very long.)

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

But what Seth suggests sounds good ;-)

Comment 3

[Ninoschka Baca]

This makes sense to me. I wonder how it would look?

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

Seems like you'd almost have to implement the newsgroup name as the abbreviated
version, for instance (n.p.m.mail-news) or something.  The full name might be
too long of a string for that widget.

Comment 5

[Håkan Waara]

Instead of adding each newsgroup, can't you have it list all the sub-newsgroups
of a news-server?

Like this:

> Get-Msg
[e-mail]
[e-mail]
news.chello.se
news.mozilla.org

Adding all the newsgroups would make the list too long.

Comment 6

[(not reading, please use [e-mail] instead)]

it would only show the current newsgroup (if you were reading news), not all the
newsgroups.

the "Get Msg" list should reflect what the get msg button does.  and when
reading a newsgroup, clicking on it gets new articles on the current group.

Comment 7

[jglick]

Adding only the currently selected newsgroup to the "Get Msg" button menu is 
fine with me.  Note: the File: "Get New Messages for-->" flyout menu would also 
need to be changed.

>we should make it so doing "Get All New Messages" gets the new messages for the
>current newsgroup group (if it doesn't already).
Yes.  I think it already does.  "Get Msg" button should do this to if a 
newsgroup is selected.

cc'ing Bhuvan and Scott P since they were part of the original decision.

Comment 8

[scottputterman]

Adding the current newsgroup sounds reasonable to me.

Comment 9

[Matthew T (active 1999-2002)]

> Note: the File: "Get New Messages for-->" flyout menu would also need to be
> changed.

If it does, that's a separate bug. They should be using the same overlay, 
surely.

Comment 10

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 11

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 13

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 14

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 15

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 16

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 17

[Karsten Düsterloh]

Still valid RFE, although it needs some thought first.