topic Regular expression search and replace in SAS EG is broken in SAS Enterprise Guide

Regular expression search and replace in SAS EG is broken

ScottBass — Thu, 04 May 2017 05:30:01 GMT

EG 6.1 M1 (6.100.0.4025) (32-bit)

I pasted a bunch of text from Excel (list of variable names, one per line) into EG.

I now want to make them comment headers for each code block.

So, I tried: Cntl-H, Find text = ^, Replace with = \* , tick Regular expression search, click Replace All (or Replace in Selection).

Error message "Cannot find the string "^" ".

Tried the same using the "right arrow/play button" pulldown for ^ Start of line. Same error.

Also tried: Find text = $, Replace with = ; . Same error.

Workaround: paste into Textpad, search and replace (F8), do the same thing as above, it works fine. Paste back into EG.

(In Textpad, Find text = ^(.*)$, Replace text = \* \1 ; does it all in one search and replace, which is kind of cool.)

Can anyone comment 1) if they also experience this issue in EG 6.x, and 2) is it fixed in later releases?

Re: Regular expression search and replace in SAS EG is broken

ballardw — Thu, 04 May 2017 15:21:05 GMT

The regular expression parser in the editor seems to be only a subset of regular expressions.

Part of the issue with the search and replace in the editor is that it has to handle the non-regular expressions as well.

You might be able to use

Search for \n

Replace \n/*

for the start of a line

or search \n

replace */\n for end of line

but generally I would find the editor Ctrl-/ on a block or line of text easier.

Re: Regular expression search and replace in SAS EG is broken

CaseySmith — Sat, 06 May 2017 03:08:49 GMT

You are actually running into two limitations of the Find/Replace dialog in the EG editor...

1) It doesn't currently handle zero-width regular expression matches (such as lone ^ and $). If you use those anchors in regular expressions that return greater-than-zero-width matches, it'll find the matches just fine.

2) It doesn't currently allow regular expression substitutions in the replacement text. (ex. a capture)

We are aware of both of these limitations (which still exist in the latest version of EG) and hope to be able to address them in a future release.

Casey