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 2338 - TDEFileReplace: Does not display line breaks in Search or Replace text box widgets
Summary: TDEFileReplace: Does not display line breaks in Search or Replace text box wi...
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeutils (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 enhancement
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2015-01-29 20:12 CST by Darrell
Modified: 2018-05-27 10:48 CDT (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2015-01-29 20:12:42 CST
When I want to modify more than one line in multiple files, such as all of my TDE build scripts, I open one build script in kate. I copy the affected lines and paste into the Search text box in tdefilereplace. I again paste the text into the Replace text box, but in the Replace text box I edit the text as desired for the changes.

The deficiency is the text box widgets do not display non text characters, specifically line breaks. All I see is a corresponding space, which renders manual editing of the Replace text box a challenge.

Whether non text characters should display as the default is not as important as the ability to at least display the characters. Especially because multiple lines appear in both text boxes as a single line.

Perhaps the only issue here is simply to display line breaks rather than all non text characters. The common symbol used is the pilcrow. Or perhaps the text box widgets should be able to display multiple lines as multiple lines rather than a single line.

This report is related to bug 2334.
Comment 1 Darrell 2015-02-04 12:13:45 CST
Although filed as an enhancement request, this could be viewed as a bug. Seems closely related to bug 2339.