Bug 175509 - Gedit fails to search and replace strings with backslashes
Summary: Gedit fails to search and replace strings with backslashes
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit   
(Show other bugs)
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-12-12 02:41 UTC by Kristian Harms
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-14 15:45:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Kristian Harms 2005-12-12 02:41:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; nb-NO; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7

Description of problem:
I noticed the problem when editing a Latex file, meaning it ended in .tex and was displayed in Gedit using the Latex syntax highlighting mode.  I have not tested whether the bug appears for other types of files in Gedit, but I suspect that it does.

The problem relates to text containing backslashes, e.g. the string \rightarrow, and being able to do search and replace on this.  The bug has several aspects, which are pointed out explicitly in the "steps to reproduce section" below.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Make a .tex file and let it contain the word \rightarrow at various places.
2. In Gedit, select one of the instances of \rightarrow and click the Replace button (or choose to search and replace in some of the other ways available); note that the selected text \rightarrow is already entered into the search field, which is correct behaviour.
3. Click the Search button.
4. At his point, Gedit should jump to one of the instances of \rightarrow, or perhaps remain at the already selected one. The observed behaviour is however quite different:  It claims that it could not find the selected text. This is aspect number 1 of the bug.
5. Since we have some experience with programming, formal languages and escape sequences, we guess that perhaps Gedit gives some metacharacter meaning to the backslash (which b.t.w. is no excuse), and so we add another backslash at the start of the Search field, so it now reads \\rightarrow.
6. Clicking Search now finds the various instances of \rightarrow in the file we're editing. This behaviour is aspect number 2 of the bug, since no-where in the file is the text \\rightarrow present.
7. Anyway, sensing we're on track to getting the search&replace job done, we push ahead by entering some text in the "replace with" field, e.g. "hello".
8. We click Find, it jumps to the next instance of \\rightarrow
9. We click Replace, and it should now replace the highlighted "\rightarrow" by "hello", but it doesn't!  This is aspect number 3.
10. The hightlight nevertheless jumps to the next instance of \rightarrow in the file.
11. We click Replace some more, and notice that sometimes the Replace button doesn't even depress or react (apart from getting that dotted line box around the text, indicating it received keyboard focus). After some experimenting, we see that the pattern is that if the mouse has left and re-entered the area of the button before between the two successive click, it works, but if it has stayed within the area of the button between the two successive clicks, the button doesn't work.  This is aspect number 4 of the bug.  (It might even be an entirely different bug, I don't know.)
12. In desperation, we click Replace All.  Astonishingly, it works!

Some more aspects of the bug can be displayed following another path:

13. We have a Latex file with some instances of the text "A -> B" in it, and we want to replace this ad-hoc right-pointing arrow with a proper arrow.
14. We select one of the instances of "->" and hit the Replace button in Gedit, noting that the selected text appears correctly in the the Search field.
15. We write \rightarrow in the Replace With field.
16. We hit the Search button, and notice that one of the instances of -> is correctly selected.
17. We hit the Replace button, and note that the instance of -> does in fact get replaced, though not by \rightarrow but instead by the text ightarrow, with additionally a linebreak added immediately in front of "ightarrow".  This is aspect number 5 of the bug. (Hitting the "Replace All" button behaves the same way.)

Actual Results:  (Actual results are embedded in the steps to reproduce section above.)

Expected Results:  (Expected results are embedded in the steps to reproduce section above.)

Additional info:

I also had a brief chat with someone using current rawhide (12th of december, 2005), and he at least had some of the same problems, though we didn't have time to do any thorough testing of his Gedit.

Comment 1 Christian Iseli 2007-01-22 11:36:39 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?


Comment 2 Ray Strode [halfline] 2007-08-14 15:45:50 UTC
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.

Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.

Thank you in advance.

(this message is mass message)

Note You need to log in before you can comment on or make changes to this bug.