After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 105615 - Search/replace should remember settings
Search/replace should remember settings
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI
1.0.x
Other All
: Normal enhancement
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2003-02-09 00:42 UTC by Steve White
Modified: 2010-06-30 08:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Steve White 2003-02-09 00:42:51 UTC 
Search / Replace settings should be remembered between invocations.

This includes:

Ignore case
Match whole words only
plain text / regular expression
etc

It is really annoying to have to click on "Ignore case" repeatedly when
you're doing a lot of searches.
Comment 1 HLHJ 2008-02-07 23:12:20 UTC 
This would be very useful, especially if the search-in-range/search-in-entire-workbook option could also be remembered.
Comment 2 Walther 2010-06-29 15:11:31 UTC 
Oh god. SEVEN YEARS!?

I came to make this exact same bug report/feature request, as I need to perform many searches (and having to select "Current sheet only" every time is tiring, not to mention the search time goes up ten-fold when I forget to set it!)

Is there any hope for this functionality to be implemented? Just don't destroy the dialog on dismiss, keep it hidden until the next Search invocation. Would that help?

Using version 1.10.6 ...
Comment 3 HLHJ 2010-06-29 19:30:31 UTC 
Bug 52221 may be related in implementation.
Bug 100541 is related in user interface.
Comment 4 Andreas J. Guelzow 2010-06-30 08:34:48 UTC 
In 1.10.8 and later you can save default settings for this dialog. So if you always search in the selection only it will remember that.

I think that should satisfy this request.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 5 Andreas J. Guelzow 2010-06-30 08:35:31 UTC 
By the way, 7 years makes this a pretty recent bug!