By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 914 - Can't disable Recent Documents mechanism
Summary: Can't disable Recent Documents mechanism
Status: CONFIRMED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdelibs (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Other
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency treegraph
 
Reported: 2012-03-12 18:41 CDT by Darrell
Modified: 2018-08-30 02:52 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments
Patch to allow setting recent documents list size to zero (484 bytes, patch)
2012-03-12 18:41 CDT, Darrell
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2012-03-12 18:41:12 CDT
Created attachment 487 [details]
Patch to allow setting recent documents list size to zero

Users are unable to directly disable the number of recent documents to maintain. The option is configurable in Panels/Menus. The list size number is retained in the user's kdeglobals:

[RecentDocuments]
MaxEntries=

The spinner won't allow a user to set a list size  to anything below 10. That can be fixed by patching tdebase/kcontrol/kicker/menutab.ui:537 from 10 to 0.

Patch attached.

After applying that patch, setting the list size to zero does not provide a way to disable the tracking process or prevent the list. TDE still keeps at least one document in $TDEHOME/apps/share/RecentDocuments.

When set to zero:

* TDE should not create the RecentDocuments directory.
* TDE should not create any *.desktop applink files.
* The Recent Documents menu option should be ghosted in the "Optional Menus" list.
Comment 1 Darrell 2012-03-13 11:27:08 CDT
Patch to allow setting list number to zero merged in GIT hash df5d0a61401e5a477660c2676f14a53a760510d9. This patch only partially resolves the bug report.
Comment 2 Timothy Pearson 2012-07-26 11:46:00 CDT
Setting to confirmed as there is no unapplied patch available for this report.
Comment 3 Darrell 2012-09-18 17:34:59 CDT
I have been tinkering with this hoping to find a patch. Not yet. :(

I notice two anamolies:

1. Using the GUI, changing MaxEntries does not take effect until Trinity is restarted. The change does not occur in real-time.

2. When MaxEntries is configured to zero, Trinity nonetheless always maintains one file in $TDEHOME/share/apps/RecentDocuments. Just one, the most recent.

In addition to fixing No. 1, seems to me when a user changes MaxEntries to a smaller number, Trinity should automatically delete the older excessive number of files in $TDEHOME/share/apps/RecentDocuments.

Of course, when MaxEntries is configured to zero, Trinity should not be storing any data at all.