Re: [Evolution] [Feature request] Evolution should fetch new mail notifications even when the app is closed
Hi, On Sat, 2019-03-02 at 01:50 +0100, juo...@joasis.lt wrote: > With 3.30.5 version of Evolution new mail notifications show up at > the > startup of the app which I think is quite pointless and distracting > because new email messages are cleary visible in the opened window. That's only "pointless" if you have enabled "Edit > Preferences > Mail Preferences > General > Start up > Check for new messages on start"? [...] > I strongly believe that Evolution should at least have an option to > enable background notifications. It could probably be achieved by > implementing such feature in evolution-data-server. Also see https://bugzilla.gnome.org/show_bug.cgi?id=764513 Cheers, andre -- Andre Klapper | ak...@gmx.net https://blogs.gnome.org/aklapper/ ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] [Feature request] Evolution should fetch new mail notifications even when the app is closed
Hello everyone, With 3.30.5 version of Evolution new mail notifications show up at the startup of the app which I think is quite pointless and distracting because new email messages are cleary visible in the opened window. One might argue that the correct use of Evolution notications would be to leave the app opened and minimized. That brings me to my question: is that the best way to stay up-to-date with new email messages? Most email and messaging apps on Android, iOS and other platforms have a default behavior to provide notifications even when the app itself is closed. To me it makes a lot of sense: generally I'm not interested in opening the mail app unless I get a new email notification. Keeping the app opened may result in one of the following problems: 1) It clutters the alt+tab window. 2) Placing it in separate workspace makes workspace navigation cumbersome, 3) User might accidentally close the app without knowing it. I strongly believe that Evolution should at least have an option to enable background notifications. It could probably be achieved by implementing such feature in evolution-data-server. The lack of it is currently the sole reason I use Geary as my main email app. Background apps have been a controversial topic in GNOME dev community. However, what I'm suggesting is not against the guidelines as described here in "Running in the background" section: https://wiki.gnome.org/Initiatives/StatusIconMigration/Guidelines Development of evolution-on (https://github.com/acidrain42/evolution-on ) and evolution-tray (http://gnome.eu.org/index.php/Evolution_Tray) plugns seemingly stopped years ago and not necessarily in agreement with current programming guidelines (e.g., use of tray icons is discouraged: https://blogs.gnome.org/aday/2017/08/31/status-icons-and-gnome/). Let me know what you think. Best regards, Juozas ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] [EXTERNAL]Re: Any plugin to snooze/defer an email?
That is correct - the OP meant incoming email. I came to rely on it heavily with the Boomerang plugin and also, for my personal email, with gmail snooze. However, I've switched to using the create task or create appointment function. Changes my workflow a bit, but it does the job. On Thu, 2019-02-28 at 15:14 +, Patrick O'Callaghan wrote: > On Thu, 2019-02-28 at 09:06 -0500, Adam Tauno Williams wrote: > > Aside: A way does exist to do this, manually. Compose the message > > and > > save-to-draft, don't send. Then one can go the Drafts folder, open > > the > > message, and send it at any given time. I personally use the > > Drafts > > feature frequently. > > I think the OP meant snooze applied to incoming messages. At least in > the case of Gmail, that's what it does. The mail is effectively > deferred until a later time, and then shows up in the Inbox. It's > still > visible of course, so the deferment is a scheduled activity that just > changes its status. As you say, there's no standard way of doing this > and I can see it being a mess to implement in a robust way. > > But isn't that what Tasks are for? On receiving the mail, use it to > create a Task. That seems to cover the use case as far as I can see. > Maybe there's a case for creating a quick way to do this and calling > it > Snooze. > > poc > > ___ > evolution-list mailing list > evolution-list@gnome.org > To change your list options or unsubscribe, visit ... > https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.gnome.org_mailman_listinfo_evolution-2Dlist=DwICAg=SAbiaX0r7qzgR-m0orrYZqJBC6x6dhYqv2k9zfIfhj4=WKYDpvK91PHpzn2PwDnlNg=vsATT1HIPHXEwmkiMXnfLz9SWDXSKJ0p9ZMiXyhzKhA=cUOaiXW2M_Thj4B3LB8VAQ-EvQeB--H-sAXH_u7dtxo= ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
