I was using the following regex in replace mode:
\"\{.*\}\"
\"\{\}\"
It worked ok last year, but now that I compare again it does not work. Tested also in v4.2b CompareIt.
Looks like a date-dependent bug, maybe protection side effects are at work.
Curly brackets do not seem to be recognized as literals.
Basically I need to omit GUIDs in comparison
CompareIt 4.1.2171 regular expressions
Re: CompareIt 4.1.2171 regular expressions
It does work for me in tests. If second line is your Replace expression, you can try to change it to empty line.
Try using some simple test file - maybe something else in your file could be a reason for fail?
Do you see yellow icons marking RegExps replacements at all? Maybe you are using another profile?
Try using some simple test file - maybe something else in your file could be a reason for fail?
Do you see yellow icons marking RegExps replacements at all? Maybe you are using another profile?
Re: CompareIt 4.1.2171 regular expressions
It looks like the substitution works if it is the _only_ difference in the line.
In case the is a second difference after matching expression (GUID) (this second is a no-matching expression) then
both are flagged as difference (in red color). So it is probably a display problem, rather than substitution problem
In case the is a second difference after matching expression (GUID) (this second is a no-matching expression) then
both are flagged as difference (in red color). So it is probably a display problem, rather than substitution problem
Re: CompareIt 4.1.2171 regular expressions
Yes, that's a known bug\feature - regexps and other rules are used when comparing lines to each other, however when highlighting changes within lines almost nothing can be ignored.
Re: CompareIt 4.1.2171 regular expressions
How difficult it is to fix this one?
Meaning, if it is in a month, then it is too late for me.
Meaning, if it is in a month, then it is too late for me.
Re: CompareIt 4.1.2171 regular expressions
Yes, I'm afraid that will not be fixed in near time.