#49 Option to hide nagstamon if everything is ok

Joachim Breitner

This is a clone of 2972096 (https://sourceforge.net/tracker/?func=detail&aid=2972096&group_id=236865&atid=1101373), which was automatically being closed without an actual fix existing, and it seems that I do not have the permission to re-open that bug. I’m still using nagstamon and I am still very convinced that for me, a nagstamon that is only visible when something is wrong, is much more useful. Thus I again updated my patch to the latest version, including recreating the changes to the .ui (and manually cleaning up the mess that glade does when editing such a file). Hoping that maybe the patch can be applied after all or, if not, it might provide useful to others, I am attaching it here.

For reference, the corresponding Debian bug report is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579001


  • HenriWahl

    In my opinion nothing changed since the conversation on bug report http://sourceforge.net/tracker/?func=detail&aid=2972096&group_id=236865&atid=1101373 so I just repeat that I see no benefit in a hidden and single instance Nagstamon, more likely a danger and inconvinience. Thank you for your work but I am sorry to say I cannot merge it.

  • Hi,

    what do you mean single instance – immediately after you mentioned that people use different config files I extended the patch so that you can still run more than one instance, with different config files. Or do you want to run multiple nagstamon instances for the same configuration file?

    I was under the impression that the only thing holding you back is the worry that nagstamon might crash. It hasn’t crashed here, and anyways, if that happens then it’s a fixable bug, isn’t it?

    And, just to avoid misunderstandings: Of course the patch adds the feature optionally, with it being off by default.