Comments you submit will be routed for moderation. If you have an account, please log in first.

Opened 6 years ago

Closed 5 years ago

#19 closed enhancement (fixed)

previous message in thread requester

Reported by: opiopi Owned by: tboeckel
Priority: normal Milestone: YAM 2.7
Component: user interface Version:
Severity: trivial Keywords:
Cc: OS Platform:
Blocked By: Blocking:
Release Notes:

Description (last modified by tboeckel)

if i click on "previous message in thread a requester" pop up and ask "In order to follow the thread, YAM has to load all indices..." with the options Yes and No.

if i click "No" but the index is already loaded then YAM switch to the previous message.

More user friendly would be if YAM first search in loaded indexes for a previous message and only if not found pop up the above mentioned requester.

Moved from SF:

Attachments (0)

Change History (8)

comment:1 Changed 6 years ago by damato

  • Priority changed from major to undecided
  • Severity set to major

comment:2 Changed 6 years ago by damato

  • Component changed from stable build to undefined

comment:3 Changed 6 years ago by damato

  • Cc yamos-svn@… removed

comment:4 Changed 6 years ago by damato

  • Component changed from undefined to user interface
  • Milestone set to YAM 2.7
  • Priority changed from undecided to normal
  • Reporter changed from opiopi@… to Opi
  • Status changed from new to accepted

comment:5 Changed 6 years ago by damato

  • Reporter changed from Opi to opiopi

comment:6 Changed 5 years ago by tboeckel

  • Description modified (diff)
  • Status changed from accepted to pending

While reading this ticket again I asked myself the question if loading a flushed/not yet loaded index is really that "expensive" in terms of memory and time that YAM has to ask the user about this.

When outdated mails are to be deleted automatically there is also no question whether to load an index or not. It is loaded to determine which mails are too old and which have to be kept. No matter what.

Since YAM will flush recently unused indices automatically this ticket becomes even worse, because if YAM loaded all indices on startup this might be no longer true after i.e. 30 minutes. YAM also doesn't ask whether to load an index or not if the user changes the current folder. The index will be loaded, because it is needed then.

So my suggestion is to drop that question completely and simply perform the search on all folders. Sooner or later YAM must be able to keep all indices in memory, even if that is for a short time only. And since indices will be flushed automatically there is no reason not to load the indices automatically without acknowledgement from my point of view.

Any objections if we remove that question completely?

comment:7 Changed 5 years ago by tboeckel

  • Owner changed from somebody to tboeckel
  • Severity changed from major to trivial
  • Status changed from pending to assigned

Since I got no reply so far I suppose nobody objects if I remove the confirmation requester.

comment:8 Changed 5 years ago by tboeckel

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [5572]) * YAM_MA.c, locale/ removed the confirmation requester when a global

search over all mail folders for a threaded answer has to be performed.
Since YAM periodically flushes all indices the confirmation is more annoying
than helpful. See #19 for details. This closes #19.

Add Comment

Modify Ticket

as closed The owner will remain tboeckel.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • Frank Weber(Reporter)
  • Thore Böckelmann(Owner, Participant)