GNOME Bugzilla – Bug 735305
File History - can't get rid Files in History List - Windows Gnumeric V 1.12.17
Last modified: 2014-12-30 02:00:25 UTC
I have used both the Help within the Application, and the Manual on the web site. Both indicate there is a setting for 'Length of File History'. In fact the Preferences for 'Length of File History' in V 1.12.17 do not have a setting for the number of files to keep. There appears to be no way to clear the history(all or single files). How can I get the History down to a manageable list?
OK, This kind of reeks, but the only way I can remove a file from the History List is to either(1) delete the file, (2) move the file to another location, or(3) Delete the file! I have remarked this a CRITICAL because there really SHOULD be a way within the user interface to compress the File History. Either with a plugin or within the program itself.
This is the official gtk history of used files. Under Linux Mint I can just clear the history from the desktop menu.
Please have a look at the description of 'critical'.
I don't use Linus Mint. My original bug report title really does indicate Windows, gnumeric V 1.12.17. There is not a way to clear the history form the WINDOWS DESKTOP Gnumeric menu. If there were, I would not have filed this as a WINDOWS bug. Or maybe you can tell me where to look for a 'clear history' switch in the WINDOWS version menu system. Yeah, I looked at 'critical', and decided it was critical to me on my WINDOWS PLATFORM. I shouldn't have to RENAME, MOVE, OR DELETE a file to get it off the File History list! So you change it from critical to normal or what ever. It is a critical issue to me as a recent WINDOWS user of Gnumeric.
I am discontinuing the Windows builds. See http://www.gnumeric.org
Bummer! I just recently installed it and outside of this bug(IMO) it is a very good application. Why are you discontinuing the Windows builds? Any particular reason?
Ok, I looked there again. That note was not there about two hours ago. Sorry to see it go! If I knew Gtk+ I would give it a try. So I will continue to use it as is until it doesn't work anymore.
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.