-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addon activates global search & indexer #370
Comments
We use it for Task Followup(email followup) feature? what do you recommend |
Two thoughts.
I disable indexing because it causing large delays due to disk I/O and rely on google for my searching. Derek
|
I think exchangecalendar should touch this setting under no circumstances; if the user has disabled global indexing, there is probably reason for it. Showing a warning in the addon's settings that "Task Followup" won't work without global indexing is enough in my opinion. This issue makes exchangecalendar completely unusable for me, as I have subscribed some very high-volume mailing lists, and global indexing makes thunderbird use 100% CPU all the time when you have a few 100k mails... |
@NeoRaider yeah global indexing will be set disabled, when the follow up is not needed |
I have version 3.5.0 of the extension and I verified that the changes in the patch were present in exchangeSettings.dtd but I still see the problem. If exchangecalendar is enabled, global indexing is enabled. Only disabling the add-on allows me to turn global indexing off and retain the setting. |
Confirm this behavior with 3.8.0-beta2. |
I confirm that this problem is also present with version 3.8.0-beta3. |
Hi, |
I finally tracked down my inability to turn off Tbird's global search indexer to this addon. Verified that this addon is the cause by starting a new profile and testing just with this addon enabled and disabled. When disabled I can turn off the global search indexer when the addon is enabled the search indexer automatically becomes re-activated after a restart.
The text was updated successfully, but these errors were encountered: