Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
E
evolution-data-server
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • evolution-data-server
  • Issues
  • #219

Closed
Open
Opened May 06, 2020 by Michał Górny@mgorny

Search folder content rebuilt after a change in it

I'm sorry but I can't pinpoint the exact version when this changed but the refreshing of search folders have become much more aggressively recently and this is really frustrating compared to the previous behavior.

I have a search folder to collect unread messages from various other folders. Previously, Evolution used to add new messages there but not to remove old (i.e. already read) messages until I've refreshed manually or switched folders. The current version is aggressively removing read messages a little time after I switch to the next unread message.

This is frustrating for me because I sometimes accidentally jump to the next message. If the old one gets marked as read already, I sometimes no longer manage to jump back before it is removed and I have to look for it in other folders. What's even worse, since there is some delay I sometimes race against Evolution and end up losing both the previous and the next message (if some lag causes Evolution to mark it read before trying to jump back).

Edited May 18, 2020 by Milan Crha
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/evolution-data-server#219