On Wed, 2001-10-31 at 14:30, Richard Bellavance wrote:
> The good news is that it's started on Evo launch now.
>
> The bad news is that it wants to run so bad, it's not killed upon exit
> :-)
It is intended to keep on running. You may have alarms that trigger
even when Evolution is not running.
On Wed, 2001-10-31 at 15:38, Luis Villa wrote:
> I'm not 100% certain but I'm fairly sure this is by design, so that if
> you get an alarm after you've closed evo you'll still get the alarm.
> Someone might have a more authoritative answer on that than I do.
That makes sense.
Sorry about the ele
I'm not 100% certain but I'm fairly sure this is by design, so that if
you get an alarm after you've closed evo you'll still get the alarm.
Someone might have a more authoritative answer on that than I do.
Luis
On Wed, 2001-10-31 at 15:30, Richard Bellavance wrote:
> The good news is that it's s
The good news is that it's started on Evo launch now.
The bad news is that it wants to run so bad, it's not killed upon exit
:-)
'killev' does make it go away, though.
Seriously, kudos to the whole Evo team, it's shaping up really nicely,
and I can't wait for the 1.0 release !
Richard.
--
Ric
That should be fixed as of very late last night.
Luis
On Tue, 2001-10-30 at 20:09, Cengiz Alaettinoglu wrote:
> evolution-alarm-notify somehow does not get started until I click on the
> clendar folder.
>
> Also, in a threaded view, if you do cntr-h, cntr-d, the current message
> advances by 1
evolution-alarm-notify somehow does not get started until I click on the
clendar folder.
Also, in a threaded view, if you do cntr-h, cntr-d, the current message
advances by 1 which is typically one of the deleted messages of the
thread I wanted to skip. It would be nicer (imho) if it skipped the
