View Issue Details

IDProjectCategoryView StatusLast Update
0002575ScribusUsabilitypublic2021-11-09 21:39
Reporterintrigeri Assigned Tocbradney  
Status closedResolutionwon't fix 
PlatformppcOSDebianOS Versionsarge
Product Version1.3.1cvs 
Summary0002575: [OBSOLETE?] Search/replace dialog should warn when trying to replace by the same text
DescriptionIt would be nice, when the user tries to search for some text and replace it exactly by the same, to warn him/her.
TagsNo tags attached.


related to 0002332 new Add regular expression capability to Search/Replace 
child of 0012755 new Metabug: Search & Replace (1.5.x svn) 



2005-09-17 03:21

reporter   ~0006615

I'm not entirely sure I understand why that's an issue, really.


2006-05-07 20:35

developer   ~0011070

I disagree with this warning. I don't think it is necessary at all. It can happen we have to change attributes to a certain string... it is then obvious we need to replace that string by the same string. It is expected that when working in that dialog, we have to be cautious, no matter what the change will be.


2019-12-16 19:37

manager   ~0047285


if nobody sees a use case, i think that we can close this.
(it's stupid to replace some text by itself, but i don't see why a warning would be needed... the result will be what the user expects.)

Issue History

Date Modified Username Field Change
2005-09-16 22:37 intrigeri New Issue
2005-09-17 03:21 ringerc Note Added: 0006615
2005-09-17 03:21 ringerc Priority normal => low
2005-09-17 03:21 ringerc Severity tweak => trivial
2005-09-17 03:21 ringerc Status new => acknowledged
2006-04-14 11:25 mhanski Relationship added related to 0002332
2006-05-07 20:35 louisdesjardins Note Added: 0011070
2014-10-08 00:13 Kunda Relationship added child of 0012755
2019-12-16 19:37 ale Note Added: 0047285
2019-12-17 09:13 ale Summary Search/replace dialog should warn when trying to replace by the same text => [OBSOLETE?] Search/replace dialog should warn when trying to replace by the same text
2019-12-17 09:13 ale Patch => No
2021-11-01 19:01 cbradney Assigned To => cbradney
2021-11-01 19:01 cbradney Status acknowledged => resolved
2021-11-01 19:01 cbradney Resolution open => won't fix
2021-11-09 21:39 cbradney Status resolved => closed