On Tue, 2011-01-04 at 11:36 -0700, Jeremy Nickurak wrote: > My feeling is the root cause of this is closely tied to the missing UI > for deciding what is and isn't in the messaging menu (currently > managed by a config file in ~/.local/indicators/messaging/blacklist, > or something similarly obscure :) ). There's similarly a missing UI > for deciding which of these things should be a part of the sign-on > session. If evolution (or a notification-only client) could be > naturally be a part of the session startup, living in the indicator, > and not going away when the client windows are closed, we'd be a lot > better off. Addressing sessions XOR window-closing will probably just > further confuse the issue (making it look more like it's doing what's > expected, but not actually doing so). The idea from the UI-size of things is that individual application's preferences should have a configuration item for whether they are shown in the messaging menu or not. It does have the problem of needing run the application to remove it, but it is a more natural place to look for changing how the application behaves. In general, the messaging menu is a only a place to gather what data applications want to display. I think that there is probably some room for a TweakUI type tool that would allow for fine-grained configuration of the messaging menu. Not shipped by default but for people who'd like more detailed control. Just FYI, the configuration is slightly different than you described (I realize you weren't going for accuracy, but for the archive): http://askubuntu.com/questions/3832/how-to-remove-envelope-from-indicator-applet-without-uninstalling-the-indicator-m/15616#15616 --Ted
Attachment:
signature.asc
Description: This is a digitally signed message part