On Tue, 2003-07-22 at 17:37, guenther wrote: > > > I just wondered (nope, not using alarm normally): > > > > > > As these processes have to be running for notifying the user, shouldn't > > > they be launched on login? > > > > > > As they are not running on login, the user will not be notified unless > > > he actually runs Evolution -- at least for a short time. > > > > if you start evolution on a GNOME session, when closing the session, the > > list of running programs is saved, so the alarm daemon should be started > > if it was running when the session was ended. > > Well, as I said, I am just wondering. I don't use alarms ATM. > > Neither did I ever save my session when logging out. I only manually > added gkrellm to the session to start on login. I don't like > automatically recreating all running apps and I even close my apps > before logging out... > I also close all my apps before logging out, but I don't kill the other processes, so this saves any daemon/component that is running for the next session.
> > > Isn't it working that way for you? > > That said: Nope, no process with substring 'evo' after login. > > Is this planned to be automagical or is the user intended to always save > sessions? IMHO that should be more clear -- otherwise users might count > on being alarmed although they won't. > I think this should work on any X session, that is, in KDE at least. I'm not sure of this though. > Maybe I am just not getting the point... > the other way to be sure to have it always started is the "old way", to start evolution-alarm-notify on your .xinitrc/.xsession files. cheers _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
