PowerGREPPowerGREP

PowerGREP Version History

Don't let the long lists of issues on this page make you think our products have a lot of problems. Quite to the contrary. All the bugs listed below are bugs that we have fixed. Many of these are corner cases reported by only one or perhaps a handful of our customers. Other software companies often don't spend any effort addressing such issues, much less list them publicly. We take pride in producing high quality software, and often release free updates to ensure you won't have any problems with our software.

Your purchase also comes with one year of free major upgrades. So don't worry if there might be a new major upgrade around the corner just because it's been a while since the last major upgrade. If there is one around the corner, you'll get it free, without having to ask. (But you can keep the old version if you prefer.)

If you ever hit a snag with PowerGREP, check here if you have the latest version. If you do, simply report the issue via email and we'll help you out as soon as we can.

Subscribe to the Just Great Software email newsletter or the Just Great Software RSS newsfeed if you'd like us to notify you of any product updates and other developments.

PowerGREP 4.7.0 – 24 September 2015

Improvements:

  • Installer no longer asks to accept the license agreement if you already have PowerGREP 4.x.x installed.
  • Installer now puts a single shortcut directly in the Start menu which better fits the Start menu on Windows 10.
  • Windows 10: New look for the menus and toolbars on Windows 10 to add a bit more contrast to PowerGREP's user interface.

Bug fixes:

  • Action: Collect data actions that operated on files in proprietary formats and that collected matches into multiple files or specified an order for the collected matches failed with an access violation error for each file upon execution (but not when previewing).
  • Action: List files action that use "filter files" but do not use a search term in the main part of the action reported an access violation error for each file on the Results panel.
  • File Selector: Selecting a different folder via the Path box did not update include files and exclude files boxes when not using the same mask for all folders.
  • Results: Open matched files in EditPad does not open all matched files when EditPad is not yet running.
  • Results: Search-and-replace for multiple terms with "list only sections matching all terms" turned on (incorrectly) listed replacements in sections that matched only some terms even though (correctly) those replacements were not actually made.
  • Results: Searching incrementally through the contents of the Results panel using toolbar at the bottom, then clearing the results, and then changing something on the search toolbar triggered an access violation.
  • View|Dual Monitor: The floating window took up the size of the entire second monitor, which caused it to appear behind the taskbar if the taskbar was on that monitor.

See also: PowerGREP 4.7.0 release notes

PowerGREP 4.6.5 – 4 May 2015

Bug fixes:

  • Communication with the conversion manager and the undo manager could fail if PowerGREP was using more than 4 GB of RAM.
  • Occasional random crashes when a single 64-bit PowerGREP instance was using more than 4 GB of memory (or an immediate crash on startup when the AllocationPreference registry key forces memory to be allocated from the top down).
  • Placeholders: %MATCHSTART% counts from zero instead of one and %MATCHSTARTZ% counts from -1 instead of zero; resolved by changing the documentation for %MATCHSTART% and removing %MATCHSTARTZ%; %MATCHSTART:+1% can be used to start counting from one; the same goes for %MATCHSTOP% and group placeholders like %GROUP1START%.
  • Regex: Certain combinations of nested capturing and non-capturing groups triggered an access violation when attempting to execute the action.
  • Regex: Syntax highlighting indicated numbered backreferences that use the syntax for named backreferences as errors even though PowerGREP allows such backreferences (as long as there is a group with the specified number).
  • Windows 8 and 8.1: The edges of the panels on the main window are now gray like they are on previous versions of Windows, instead of blue.

See also: PowerGREP 4.6.5 release notes

PowerGREP 4.6.4 – 26 January 2015

Improvement:

  • Archive Formats: RPM files using LZMA instead of GZIP compression are now supported.

Bug fixes:

  • File Selector: Loading a file selection that had individual files marked in multiple folders and running a search and expanding those folders on the File Selector panel for the first time after running the search made PowerGREP think the folders contained only the marked files.
  • File Selector: Loading a file selection that was created outside PowerGREP and that did not have its folder and file elements sorted alphabetically by their name attributes caused PowerGREP to act as if the out-of-order files and folders did not exist.
  • Search type: Delimited literal text consisting of search and replace pairs triggered an access violation when attempting to execute the action (4.6.3 only).

See also: PowerGREP 4.6.4 release notes

PowerGREP 4.6.3 – 17 December 2014

Improvements:

  • Rename Files: Check whether the path produced by the replacement text is syntactically valid and show an error if it is not rather than attempting to rename the file to an obviously invalid path.

Bug fixes:

  • Action: Collect data actions that use file sectioning with "collect/replace whole sections" or "invert search results" turned on now correctly substitute placeholders in the text to be collected.
  • Conversion manager would lock up and tie up one CPU core when the cache was not large enough to hold all files, causing PowerGREP to show errors about being unable to connect to the conversion manager.
  • Create Portable Installation: Creating a portable install via the Help menu of a hard drive install failed to copy the file PowerGREP4IFilter.exe.
  • Editor|Save As did not update the window caption.
  • Preferences|Action: Delete files to the Window Recycle Bin option was not saved to the preferences, causing it to be turned on when restarting PowerGREP.
  • Preferences|Text Encoding: Deleting all text encoding definitions and clicking OK made the Preferences dialog inaccessible.

See also: PowerGREP 4.6.3 release notes

PowerGREP 4.6.2 – 8 September 2014

Improvements:

  • Action: Changing the search type from a list to a single item and then back without editing the item restores the previous list, allowing accidental changes to the search type to be undone.
  • Action: Changing the search type from a list to a single item now keeps the item that was selected in the list (if it is not blank) instead of keeping the first enabled non-blank item in the list.
  • HTML meta tag detection now ignores meta tags that specify impossible character sets.

Bug fixes:

  • File Formats: IFilter conversion process crashed if a file format was configured to use an IFilter and an IFilter DLL was registered for it and the DLL could not be loaded (4.6.x only). This happened for DOCX files on a clean install of Windows 7.
  • File Selector: Delimited file masks were not handled correctly if the second or following file mask had a literal space inside the file mask.

See also: PowerGREP 4.6.2 release notes

PowerGREP 4.6.1 – 9 June 2014

Improvement:

  • Preferences, File Formats: IFilter file masks now include *.od[bcfgimpst] so that PowerGREP will use the OpenOffice or LibreOffice IFilter for OpenDocument Format files if you have OpenOffice or LibreOffice installed.

Bug fixes:

  • Archive Formats: ISO images using the UDF file system were not searched through (4.3.0).
  • Archive Formats: RPM archives were not searched through (4.3.0).
  • File Formats: PowerGREP did not always search through or show all sheets in XLS files with graphs and multiple sheets.
  • PowerGREP crashed at startup if the first or only syntax coloring scheme or the first or only file navigation scheme in %APPDATA%\JGsoft\PowerGREP 4 did not define any file masks.
  • Regular expressions in the form of (?<=lookbehind).* performed very poorly when the "dot matches newlines" option was off.
  • Results: Replacements that had a line break immediately before the last character in the replacement were displayed without that final character. Only the display on the Results panel was affected. Actual replacements were made correctly.

See also: PowerGREP 4.6.1 release notes

PowerGREP 4.6.0 – 26 November 2013

Improvements:

  • File Formats: IFilter conversion is now done in a separate process so that crashes or hangs in 3rd party IFilter DLLs do not bring down PowerGREP; it also allows multiple files to be converted simultaneously.
  • File Formats: XLS and XLSX text conversion no longer adds trailing blank rows and columns.
  • Help: Better workaround for the bug in IE 9 that causes 64-bit applications to crash when using HTML Help, allowing PowerGREP to show the correct help topics instead of the first page of the help file.
  • Preferences|General: Adding PowerGREP to the right-click of folders in Windows Explorer now also adds it to the right-click menu of the folder background (empty area in a folder view) in Windows Explorer.
  • RegexBuddy: Portable installs of PowerGREP can now integrate with portable installs of RegexBuddy 4.
  • RegexBuddy: When sending a list of regexes to RegexBuddy, make RegexBuddy activate the one selected in PowerGREP rather than the first one. Requires RegexBuddy 4.0.0 or later.

Bug fixes:

  • Action: File name search fails with an access violation when it needs to copy or move zipped documents.
  • Archives: Errors that occur while creating or updating archives are now handled correctly.
  • File Formats: IFilter conversion crashed if the file was inside an archive and your preferences were set such that the file would only need IFilter conversion if it was either binary or plain text; IFilter conversion worked correctly if the file was not inside an archive or if your preferences for that type of file were set to always use IFilter conversion.
  • File Formats: Some XLS and XLSX files caused the converter process to crash.
  • Forum continued to use the old proxy settings until you restarted PowerGREP if you changed the proxy settings after having successfully connected to the forum.
  • Library: Double-clicking the blank space below the last item in the list caused a harmless access violation error.

See also: PowerGREP 4.6.0 release notes

PowerGREP 4.5.1 – 7 June 2013

Bug fixes:

  • Action: Setting "target file creation" to "copy all searched files" caused PowerGREP to move instead of copy all files that were searched through but in which no replacements were made.
  • Action: Toggling "invert search results" for search-and-replace actions did not correctly update the replacement text shown in the main part of the action when the search type for the main part of the action was a list.
  • Encoding: XML files with XML declarations that specify an invalid or unsupported encoding are no longer skipped with an error about the encoding when the "detect XML encoding" option is turn on in Preferences, Encoding; they are now processed as if the files didn't have an XML declaration at all.
  • File Formats: Portable installs of PowerGREP failed to search through files in proprietary formats unless either the conversion cache folder was set to the default for portable installs ("Conversion Cache" subfolder of PowerGREP's installation folder) or both cache sizes were set to zero in the File Formats section in the Preferences.
  • Installer: Create Portable Installation failed if the user does not have sufficient access rights for a normal installation.
  • Regex: Regular expressions starting with \Z or starting with a lookbehind followed by \Z that could not find a match before the final line break in the file (because of the lookbehind or whatever follows \Z) caused PowerGREP to hang if the file ended with a line break.

See also: PowerGREP 4.5.1 release notes

PowerGREP 4.5.0 – 20 March 2013

Improvements:

  • Action: Do not highlight matching brackets in literal text as doing so may confuse the user into thinking they have a special meaning, which they don't.
  • File Selector: Automatically add and remove drive letters as they are added and removed in Windows.
  • Forum: SOCKS proxy server support.
  • Results: Make/Revert Replacements commands now show a progress meter when processing more than one file.
  • Results: Make/Revert Replacements in All Files are now disabled for actions that produce more search matches than PowerGREP can hold in memory at a time, because PowerGREP won't be able to make or revert the replacements that didn't fit into memory.
  • Results: Setting the same bookmark at the same position removes it; setting a different bookmark at the same position sets it and removes the old bookmark.
  • Results|Export: Exported HTML files now include a Content-Type meta tag to indicate the character set.

Bug fixes:

  • Action: Insert File now converts line breaks to CRLF to make sure that loading a list with delimited search terms works correctly even if the file uses a different line break style.
  • Action: Paste Escaped does nothing when the clipboard holds text copied by the same PowerGREP instance.
  • Action: Search-and-replace or search-and-delete with the 3 options "file sectioning", "invert search results", and "context type" turned on caused the replacements to be made incorrectly.
  • Command line: Specifying an empty string "" as the encoding caused PowerGREP to crash.
  • File Formats: Excel converter no longer crashes on files that are open in Excel.
  • File Formats: Files in proprietary formats that could not be converted because another application has a lock on them are no longer added to the conversion cache as files that cannot be converted; when you try to search the file again PowerGREP will attempt the conversion again instead of saying the file could not be converted previously.
  • File Formats: PowerGREP sometimes crashed with an out of memory error when trying to decode a WordPerfect document.
  • Insert path placeholders: Example column is empty until you edit the example path.
  • Preferences, File Formats: Maximum cache size while not running caused the cache to be trimmed each time an action that searched through files in proprietary formats completed running instead of only when closing PowerGREP if you did not open a file in a proprietary format in PowerGREP's built-in editor.
  • Preferences, File Formats: The file masks you specified for "Only use IFilter for..." and "Never use IFilter for..." were only used after you clicked OK in the Preferences. Next time you restarted PowerGREP it would use the default file masks, even though the Preferences dialog remembered your file masks.
  • Regex: Zero-repeated groups like (group){0} were matched as if they were optional groups like (group){0,1}.
  • Results: Double-clicking context or a context number in the results of a search-and-replace correctly opened the target file in PowerGREP's built-in editor, but did not always correctly select the context that was double-clicked.
  • Results: Making or reverting replacements did not update the highlighting if the replacements were made in copies of the files rather than in the original files, and the file the replacements were made or reverted in was not open on the Editor panel.
  • WINE: Running PowerGREP on Linux using WINE caused access violation errors when interacting with the files and folders tree on the File Selector panel.

See also: PowerGREP 4.5.0 release notes

PowerGREP 4.4.0 – 1 November 2012

New features:

  • Placeholders: %FILEN% placeholder that is incremented for each file searched through, allowing unique sequential IDs to be generated for each file.
  • Placeholders: %GUID% inserts a newly generated GUID into the replacement text; each replacement will get a different GUID.

Improvements:

  • 64-bit: Indicate x86, x64, or WOW64 in the About box to indicate whether you're running the 32-bit version on 32-bit Windows, the 64-bit version on 64-bit Windows, or the 32-bit version on 64-bit Windows.
  • File Selector: The Search Archives option is now remembered when you restart PowerGREP, even if you turn off the option to remember the file selection in the File Selector section in the Preferences.
  • Import File Listing dialog now automatically gets scrollbars if it is too large to fit on the screen, which may happen when using large fonts or a small screen.
  • Undo History: Disable commands that work on a selection in the undo history when the Undo History panel is closed.
  • Windows 8: Uninstall shortcut is no longer pinned to the start screen by the installer (but it won't unpin any shortcuts that were previously pinned).

Bug fixes:

  • Action: Collect data actions that used line breaks as the delimiter between matches stopped adding those line breaks if a file used a different encoding than the previous file processed by the same thread.
  • Archives: "List files" actions without a search term failed to delete, copy, or move files found inside archives.
  • Command Line: /delimitprefix, /delimitsearch, and /delimitreplace now interpret the strings "Line break", "Tab", and "None" in the same way the drop-down lists on the Action panel interpret them: as an actual line break, tab, or a blank string.
  • Placeholders: Path placeholders in the search term did not work correctly if the search was case insensitive and the part of the path represented by the placeholder contained uppercase letters.
  • Preferences, General: Removing folder associations did not work.
  • Results: Alt+F6 key combinations for replacing and reverting matches had no effect on the Results panel.
  • Sequence: Executing a sequence and then executing a separate action and then double-clicking a step in the sequence to load its results sometimes caused access violation errors in the File Selector when expanding folders that had results in the separate action but not in the sequence step.
  • Undo History: Ctrl+A when the undo history list has keyboard focus now selects all items in the undo history instead of selecting the whole contents of the file on the Editor panel.
  • Windows 8: Toolbar combo boxes did not properly display their drop-down arrows.

See also: PowerGREP 4.4.0 release notes

PowerGREP 4.3.3 – 30 April 2012

Bug fixes:

  • Actions that wrote search matches from multiple files to the same target file such as "merge files" actions failed with a "stream read error" (4.3.x only).
  • Renaming a file in an archive to a name already used by another file in the archive now removes the other file from the archive rather than resulting in two files with the same name in the archive (previous 4.x.x).
  • Renaming files in archives failed with an "incorrect function error" (4.3.x only). This broke "rename files" actions as well as actions that modified files inside archives and stored backup copies inside the same archives.

See also: PowerGREP 4.3.3 release notes

PowerGREP 4.3.2 – 5 April 2012

Bug fixes:

  • Archives: PowerGREP 4.3.0 and 4.3.1 failed to decompress files that were too large to be kept in memory.
  • Installer: License key was not installed when installing PowerGREP 4.3.0 or 4.3.1 silently.

See also: PowerGREP 4.3.2 release notes

PowerGREP 4.3.1 – 24 February 2012

Improvements:

  • Results: Opening a compressed file in an external editor did not add the file's extension to the name of the temporary file that it is decompressed to (added in 4.2.2 so that editors that look at the file extension see the proper extension; broken in 4.3.0).
  • Results: PowerGREP now adds an error to the results when it skips password-protected .docx and .pptx files, as it already did for .xlsx files.

Bug fixes:

  • Preferences|Results: Setting the maximum memory usage to display search results between 2048 MB and 4095 MB caused PowerGREP to claim to have run out of memory when finding the first search match.
  • Results: PowerGREP sometimes incorrectly handled files that were converted with an IFilter (e.g. Word documents) causing inconsistent search results when repeatedly searching through the same set of files.
  • View|Office 2003: Switching to or from the Office 2003 display style worked only once during each PowerGREP session (4.3.0 only).

See also: PowerGREP 4.3.1 release notes

PowerGREP 4.3.0 – 16 February 2012

New features:

  • 64-bit: PowerGREP's installer now automatically installs a 64-bit version of PowerGREP on 64-bit Windows. This allows PowerGREP to use all of your PC's available RAM, and allows the IFilter system to be used on 64-bit Windows.
  • Archives: Disk images of FAT volumes such as floppy disks.
  • Archives: Files and tarballs compressed with XZ (*.xz) (read and write).
  • Archives: ZIPX archives using the PPMd and LZMA compression methods used by the latest version of WinZip. PowerGREP will read ZIP and ZIPX archives using the Deflate, PPMd, and LZMA compression methods. PowerGREP will use the Deflate method when creating ZIP files, and the PPMd method when creating ZIPX files. The extensions for the ZIP and ZIPX formats can be configured separately in the preferences.
  • Preferences, Action: Option to use a certain amount of RAM to keep temporary files in memory instead of writing them to the Temp folder, speeding up actions that use temporary files (such as searching through archives).

Improvements:

  • Archives: Aborting an action while PowerGREP is decompressing or compressing a large archive now aborts the (de)compression operation cleanly and immediately.
  • Archives: Do not unzip all files from an archive at once if they are too large to fit into the RAM space for temporary files and the archive is not in a format that uses solid archives.
  • Dockable panels: New mechanism for docking panels makes it easier to position panels exactly where you want. Instead of moving the mouse pointer to an invisible area next to the edge of another panel, you now move the mouse pointer to icons that appear in the center of the panel that you're dragging over.
  • Forum: The button to delete messages is now labeled Cancel for messages that are being edited, to make it more obvious that this button deletes the edited message, but leaves the original message in place.
  • Results: Show an explanation on the Results panel during the globbing process so new users don't wonder why the search is stuck at 0% for a long time.
  • Uninstalling PowerGREP now deletes the conversion cache folder and the temporary files folder.

Bug fixes:

  • Action: Setting "file sectioning" to anything but "whole file" or "line by line" and then changing "action type" to "simple search" now properly changes the file sectioning to "line by line" instead of using the previously selected option that became unavailable in the interface.
  • Action: The text cursor in the Replace and Comments boxes did not change to reflect insert and overwrite mode.
  • Archives: *.tar.bz2 and *.tar.gz files were treated as single compressed files instead of as compressed tar archives when the *.bz2 and *.gz extensions were specified for the single compressed BZip2 and GZip formats (as they are by default).
  • Archives: Attempting to add a read-only file to an archive resulted in an "access denied" error even though read access is available.
  • Archives: Zero-length files are not extracted.
  • Command line: /save parameter failed to save the results unless the file had a .pgr or .pgsr extension.
  • Editor: Search matches were highlighted incorrectly (highlighting was offset from the actual matches) after a search-and-replace using multiple search terms with "non-overlapping search" turned off.
  • Editor: Syntax highlighting colors are incorrect when highlighting search matches in a file and different color palettes have been selected for the Editor and the Results.
  • File Formats: PowerGREP failed to terminate the XLS converter process after certain crashes in the converter, showing an access violation error on the Results panel, and causing errors saying "cannot send file to the converter process" on the following XLS and XLSX files.
  • File Selector: Marking a folder with a red X and marking a folder inside that folder with a green tick should search through the folder with the green tick. The File Selector panel indicated this correctly, but the actual search did not always go down folders marked with a red X.
  • File Selector: Right-clicking on an archive and selecting Edit File now opens Windows Explorer with the archive selected instead of opening Windows Explorer at the My Documents folder.
  • Results: Shift+Ctrl+E does not open the file selected in the Results in EditPad.
  • Undo manager kept archive files open longer than needed, preventing archives that were created or modified by an action in the undo history from being deleted or modified again unless the action was undone first.

See also: PowerGREP 4.3.0 release notes

PowerGREP 4.2.4 – 17 October 2011

Bug fixes:

  • Command line: error messages for invalid backup and target parameters now mention the actual parameter instead of the placeholder %s.
  • File Formats: Improved decoding of XLS and XLSX files allowing files to be decoded that PowerGREP previously failed to decode.
  • Results: Closing PowerGREP while it was still updating the results display caused it to crash after closing.
  • Results: Indentation was lost when results were partially updated (e.g. when results are automatically updated during a search-and-replace showing match and replacement on separate lines with matches grouped per file).
  • Results: Under certain circumstances PowerGREP would lock up while updating the display of a large set of search results.

See also: PowerGREP 4.2.4 release notes

PowerGREP 4.2.3 – 26 August 2011

Improvements:

  • Command line: /file, /fileexclude, /folder, /folderrecurse, and /folderexclude no longer ignore files and folders that do not exist but now mark them in the file selector just as happens when you open a .pgf file that references files or folders that no longer exist. Syntactically invalid paths now cause an error.
  • Command line: /silent now checks whether the target type specified with the /target parameter is valid for the previously specified action type and shows an error message if it is not.
  • Command line: Parameters such as /replace that change the action type now imply a /target parameter if the target type specified earlier on the command line is invalid for the new action type, or if no target type is specified and the action type requires one.
  • Editor: Ctrl+Left Shift and Ctrl+Right Shift toggle the direction of the text to left-to-right or right-to-left when a keyboard for a right-to-left language is installed (though not necessarily active).
  • Text Layout|Cursors: Cursor shape now has two flag options. One makes the flag indicate the direction of the input language (as in Notepad), the other the direction of the text the cursor is at (as PowerGREP 4 did previously).

Bug fix:

  • PowerGREP 4.2.2 did not display itself correctly when run via a remote desktop connection.

See also: PowerGREP 4.2.3 release notes

PowerGREP 4.2.2 – 20 July 2011

New features:

  • Command line: /file and /fileexclude parameters to mark individual files to be included in or excluded from the action.

Improvements:

  • File Selector/Results: Move Files and Copy Files commands now preserve the target and backup settings between PowerGREP sessions, including the target and backup location histories.
  • File Selector: Ignore unquoted spaces before and after each file mask in the Include Files and Exclude Files boxes.
  • Results: Edit with EditPad command now works with EditPad Lite 7 and EditPad Pro 7. It still works with EditPad Pro 4, 5, and 6, but gives preference to version 7 if you run more than one version.
  • Results: Increased the timeout for the PDF and XLS converters so larger files can be converted.
  • Results: Opening a compressed file in an external editor now adds the file's extension to the name of the temporary file that it is decompressed to so that editors that look at the file extension see the proper extension.
  • Results: Right-clicking in the results but not on a highlighted match and selecting Edit with EditPad Pro should select the line or block of context in EditPad just like it does with the built-in editor when double-clicking.
  • Results: Search toolbar should also search through the bottom half of the Results panel with the results details or errors.

Bug fixes:

  • Action: File name search actions did not properly trap errors when copying and moving files.
  • Action: Loading an action that uses a very long delimited list of literal text caused PowerGREP to appear to hang if the search type was previously set to regular expression before loading the action.
  • Action: Search-and-replace actions that modify original files and create backup files failed on zipped documents with an error about being unable to create the backup.
  • Action: Searching through empty files caused access violation errors to be listed in the results.
  • Action: Target type "save list of matching files to target files" did not work for the action type "file name search".
  • Action: Turning on "filter files" without entering a search term to filter with caused the action to fail with an access violation error instead of showing a helpful message about the blank search text like PowerGREP does for the other parts of the action.
  • Archive Formats: .gz files that consist of multiple concatenated .gz files are now correctly decompressed as a single file like gunzip does rather than failing with a CRC error.
  • Creating a portable installation via the Help menu did not copy over PowerGREP4PDF.exe and PowerGREP4XLS.exe which PowerGREP needs to convert PDF and Excel files.
  • Editor: Replacing or reverting matches in hexadecimal mode failed with an access violation.
  • File Formats: Improved decoding of XLS and XLSX files allowing files to be decoded that PowerGREP previously failed to decode.
  • File Selector: Keep the same file or folder selected when the search completes and the File Selector is updated with the results.
  • Preferences, Results Colors: Double-clicking in the results sample no longer results in an access violation but simply selects the word you double-clicked on.
  • Regex: ^ and $ matched after and before U+2026 which they shouldn't, and didn't match before and after U+0085 which they should (4.x.x only).
  • Results: Search options did not show tick marks to indicate which ones are active.
  • Results: Updating results after running an action or loading a .pgr file took far too long when tens of thousands of files needed to be sorted.
  • Undo manager: Undo manager locked up when PowerGREP added an undoable action that modified files on a drive that could not be monitored for directory changes. This caused PowerGREP itself to also lock up until the undo manager was killed via the task manager.

See also: PowerGREP 4.2.2 release notes

PowerGREP 4.2.1 – 25 February 2011

New feature:

  • Editor: Ctrl+] to go to the matching bracket, Ctrl+[ to select between matching brackets, and Ctrl+Shift+] to insert a matching bracket.

Improvements:

  • Action: Right-click menu for the edit box for headers and footers in collected files.
  • Print: Text Layout Configuration now lists printer fonts when activated from the print preview and "allow bitmapped fonts" is turned on.
  • Rich text is no longer placed on the clipboard for selections larger than 1 megabyte.
  • Toolbar controls now show tooltips when another toolbar control has keyboard focus.

Bug fixes:

  • Action: Lists of regular expressions that included a regex that consisted of nothing but a comment were not handled correctly; now such regexes are ignored like blank list items.
  • Action: The (...) button for the target location did not work when the target type was set to "path placeholders".
  • Action: The mode modifiers (?i) and (?-i) were ignored in regular expressions that (aside from the mode modifier) consits entirely of literal text.
  • Action: Using the "line by line" sectioning and "invert search results" caused an AV when used with the "simple search" action type.
  • Copying the hexadecimal representation of bytes and pasting them as text now works correctly for bytes >= 0x80.
  • File Formats: Non-ASCII characters in WordPerfect documents were either mixed up or missing in PowerGREP's text conversion; now PowerGREP supports all 14 WordPerfect character sets supported by WordPerfect X5.
  • Keyboard: On keyboards that use the AltGr key, pressing AltGr and E, F, N, O, P, or S did nothing.
  • Preferences, Text Encoding: ASCII+&htmlchar; encoding now correctly inserts and replaces non-ASCII characters in target files.
  • Preferences, Text Encoding: If "detect HTML charset meta tag" was on and the file did not actually contain a meta tag, PowerGREP always detected UTF-8 and UTF-16 files without a BOM as well as ASCII files using Unicode escapes, even if those two options were turned off.
  • Preferences, Text Encoding: The "ASCII + NCR" encodings did not work correctly with small files that fit into memory entirely, causing the NCR references to remain untranslated.
  • Preferences, Text Encoding: VIQR encoding no longer crashes on files that contain bytes > 126 (which never occur in a proper VIQR file).
  • Preferences, Text Layout: Setting "add X pixels of extra space between lines" to a non-zero value sometimes caused part of the text to be positioned incorrectly.
  • Rich text copied by PowerGREP can now be pasted in Outlook Express.

See also: PowerGREP 4.2.1 release notes

PowerGREP 4.2.0 – 12 January 2011

New features:

  • Action Type: File name search: Search through the names of files instead of their contents (like rename files but without a replacement text).
  • Command line: /folderexclude parameter to mark folders to be excluded from the action, complementing the existing /folder and /folderrecurse parameters.
  • Command line: /searchtextfile and /searchbytesfile parameters to load a delimited list of search terms from a file, similar to grep -f.
  • Path placeholders: %FILENAMENOGZ% is the same as %FILENAMENOEXT% if the file has a .gz or .bz2 extension, or the same as %FILENAME% if it does not have such an extension.
  • Preferences, Action: Option to ingore the read-only flag on files.
  • Preferences, Editor: Add detailed automatic folding points from the file navigation scheme.
  • Sequence: Check All and Uncheck All commands in the right-click menu to activate or deactivate all the steps in the sequence.
  • View, Lock Toolbars: Prevent moving the toolbars by accident.

Improvements:

  • Action: %MATCHTERMN%, %MATCHFILETERMN% and %MATCHSECTIONTERMN% are now supported in the search term too.
  • Action: Backreferences in replacement text that refer to capturing groups that do not exist are now highlighted as errors.
  • Action: Turning on "match whole sections only" now automatically turns on "collect/replace whole sections" to make it obvious that matching whole sections causes them to be collected and replaced as a whole as well.
  • File Selector/Results: Exploring a file's folder now selects the file in Windows Explorer.
  • Sequence: If multiple actions in the sequence modify the same file, create only one backup copy of that file. This allows "single" backup options to work correctly with sequences and avoids needless backups of intermediate steps with "multiple" backup options.
  • Undo History: Undo items for sequences store the file selection if the sequence has steps that use the File Selector instead of their own file selection, so the Use Action or Sequence item can restore the file selection to the File Selector.

Bug fixes:

  • Action: Action date, file date, and file size placeholder values were off by one.
  • Action: Backreferences in regular expressions to named capturing groups that were carried over from other parts of the action were highlighted as errors even though they worked correctly.
  • Action: Execute and Quick toolbar buttons did not always show the correct caption after starting PowerGREP or after restoring a saved layout.
  • Action: Grouping unique matches failed to group all the occurrences of the first match that was found.
  • Action: History menu for the filter files part of the action was not assigned, causing an access violation error when clicking the triangle button.
  • Action: Literal text searches using placeholders in the search term did not work correctly if the search was not case sensitive.
  • Action: Placeholders did not work when used in a regular expression.
  • Action: Renaming a file that only changed its case caused the file to be renamed or moved into its backup location instead of being renamed; if backups were disabled, nothing happened.
  • Action: Splitting files using a regular expression did not correctly split binary files. Some bytes 0x80 and above were replaced with question marks in the target files.
  • Action: The read-only attribute on existing target files was ignored, causing files to be overwritten anyway when the option to make backups is turned on, and causing PowerGREP to silently fail to make replacements in read-only files when the option to make backups is turned off.
  • Command line: /save result.pgsr saved only the results of the last step in the sequence instead of the results of the entire sequence.
  • File Selector: Compound file formats like CHM files could not be excluded using the Exclude Files file masks.
  • File Selector: Refreshing the file selection (automatically or on command) did not update files or folders that were renamed to the same name with a change in case only.
  • Preferences, Syntax Colors: Changes in syntax coloring file masks lost their effect when restarting PowerGREP unless the preferences screen was OK'd again.
  • Results, Print: The last bit of text was missing from the printout.
  • Sequence: If a step bases its file selection on another step, changing the number of the other step did not update that number in the list of steps, even though the step was correctly updated in the actual sequence.
  • Undo History: Errors caused by invalid archives should not cause the undo manager to stop working.

See also: PowerGREP 4.2.0 release notes

PowerGREP 4.1.3 – 23 September 2010

Improvements:

  • File Formats: Excel files are now decoded using a separate process so that PowerGREP doesn't crash when the XLS decoder crashes.
  • File Formats: PDF files are now decoded using a separate process so that multiple PDF files can be decoded in parallel when PowerGREP is configured to use more than one thread for grepping.
  • Results, Editor: Ctrl+F uses the word under the cursor as the default search term.
  • Results, Export: RTF file format support.
  • Windows 7: Show progress meter on the taskbar button.

Bug fixes:

  • Action: Backreferences using the placeholder syntax %GROUP1% were always highlighted as errors in regular expressions even though they worked correctly.
  • Action: Ctrl+P and Ctrl+Shift+P shortcuts for inserting path and match placeholders had no effect.
  • Action: Literal text search terms that had multiple placeholders and literal text between two placeholders ignored the text between the placeholders.
  • File Selector: Using double quotes to keep file names with commas and semicolons together did not work in PowerGREP 4 as it did in PowerGREP 3.
  • Preferences, Editor: Setting the backup type to "no backups" made it impossible to overwrite files using the Save or Save As items in the Editor menu.
  • Results: PowerGREP 4.1.2 sometimes crashed while building the results.
  • Results: PowerGREP became unresponsive for extended periods of time while executing actions that require identical matches to be grouped and grouping the matches found in a file takes longer than finding the matches in a file. This can happen when there is a large number of unique matches in the overall search but only a small number of matches in each file.
  • Results: Updating match results now works when the action is paused.

See also: PowerGREP 4.1.3 release notes

PowerGREP 4.1.2 – 12 August 2010

Improvements:

  • Archives: Improved handling of errors caused by invalid archives.
  • File Formats: New decoder for Microsoft Excel that supports the XLS and XLSX formats and should be more reliable than the old decoder.
  • Library: Ctrl+F, F3 and Shift+F3 can now be used to search through the library.
  • PowerGREP can now use up to 4 GB of memory per instance on 64-bit versions of Windows. Previously this was 2 GB.
  • Preferences, Text Encoding: HTML meta tag check for determining the file's encoding now supports the new HTML5 charset meta tag.
  • Results: Aborting an action now takes no longer than 10 seconds. Any threads still busy 10 seconds after clicking the abort button are killed.
  • Vista & 7: PowerGREP now correctly scales itself when the font size has been increased by more than 125% (i.e. the display resolution is set to more than 120 DPI).

Bug fixes:

  • Action: Changing the search type between "delimited" and "list" caused an internal inconsistency in the action definition which sometimes caused errors when attempting to save or execute the action (since version 4.1.0 which splits up or recomposes the delimited search terms).
  • Action: Displaying extra context after matches did not work when using sections as context.
  • Action: Filtering out files did not work in version 4.1.1. All files were searched..
  • Archives: Zipped documents were skipped if the folder containing them wasn't previously globbed and the IFilter option was turned off.
  • Editor: Editing a file with highlighted search matches caused the matches to be shifted incorrectly (4.1.1 only).
  • Editor: Making replacements using backreferences via the Search toolbar on the Editor panel failed with an AV.
  • File Formats: PowerGREP now correctly searches plain text files that have a .wri extension or are otherwise configured to be read as a Microsoft Write files.
  • File Selector, Search Only through Files with Results never searched through any files.
  • File Selector: Importing file listings ignored UNC paths with spaces in the server or share name.
  • Preferences were not loaded when silently executing an action from the command line.
  • Results: Clearing the results while the results display is being updated releases the results without clearing the results display, causing errors when trying to click on the results.

See also: PowerGREP 4.1.2 release notes

PowerGREP 4.1.1 – 8 July 2010

New feature:

  • Command line: /nocache parameter that can be used on combination with /silent to temporarily disable the conversion cache. Files in proprietary formats will be reconverted even if they were cached before, and won't be added to the cache. The conversion manager will not be used.

New examples in the help file:

  • Put anchors around URLs that are not already inside a tag or anchor.
  • Rename files based on HTML title tags. Shows how you can use the rename files "action type" with the "filter files" feature to use part of a file's contents to rename a file.
  • Sequence to update files from 2010 to 2011: copy files under a new name, then search-and-replace the targets.

Improvements:

  • IFilters are now always called from PowerGREP's main thread. Some IFilters do not always work correctly unless they're called from the application's main thread. This includes the Office 2007 IFilters, causing Office 2007 files to be skipped as binary files if the option to use the IFilter is turned on.
  • Preferences, File Formats: Setting the maximum size of the conversion cache while PowerGREP is running to zero now completely disables the PowerGREP conversion manager.
  • Preferences, File Formats: The default IFilter options now has "decode binary files" turned on and "only use IFilter for" set to *.ppt so that PowerPoint files will be searched using the IFilter.
  • Results: Threads that become unresponsive are no longer forcibly terminated after one minute. While this feature (introduced in PowerGREP 4.0.0) was intended to make PowerGREP more reliable by making sure it doesn't lock up if it gets stuck on a particular file, it seems to have actually made PowerGREP less stable. Threads that are forcibly terminated cannot clean up after themselves.
  • Uninstaller now cleans up the settings stored in %APPDATA%\JGsoft\PowerGREP 4.

Bug fixes:

  • Action, Extra processing: Group placeholders that specified placeholder options such as %GROUP1:L% did not work correctly.
  • Action: Collecting search matches into target files with "group identical matches" turned on resulted in a double BOM being written if the target file was a Unicode file configured to have a BOM.
  • Action: Creating target files using path placeholders failed for the second and following files if the target folder did not yet exist.
  • Action: List only sections matching all terms did not work correctly.
  • Action: Setting "order of collected matches" to sort the files in a particular way when collecting search matches into a single target file caused PowerGREP to fail to write anything to the target file.
  • Action: Using the Preview or Rename (but not not Quick Rename) buttons to run a "rename files" action caused PowerGREP to leak 64K of memory for each file that needed to be renamed.
  • Command line: When using the /silent parameter to execute an action that is set to not create backup copies when overwriting files PowerGREP 4.1.0 crashed after completing the action unless the /noundo parameter was also used. Now /noundo is implied when the action does not create backups.
  • File Selector: Including or excluding files did not work correctly when using more than one traditional file mask and a file mask containing a backslash was listed before another file mask not containing a backslash.
  • File Selector: The Path box ignored UNC paths with spaces in the server or share name.
  • PowerGREP is now more conservative with memory when searching through very large files. Previously this was based on available memory. Now there is a fixed 50 MB limit. This makes sure PowerGREP doesn't run out of memory when multiple threads open multiple very large files at the same time.
  • Results: Storing the results of a search-and-replace or search-and-delete action is much too slow when collecting context.
  • Text copied to the clipboard by PowerGREP 4.1.0 could not be pasted into applications that support rich text if the copied text did not have any changes in syntax coloring.

See also: PowerGREP 4.1.1 release notes

PowerGREP 4.1.0 – 14 May 2010

New features:

  • Command line: /context parameter to specify whether to use sections or lines as context, or no context at all.
  • Command line: /contextextra parameter to specify extra context before and after.
  • Command line: /noundo parameter to skip saving the undo history even when backup files are created.
  • Command line: /noundomanager parameter to save the undo history directly to a file without using the undo manager.
  • Command line: /reuse parameter to reuse a previous PowerGREP instance, if there is one, and if it isn't busy.
  • Copying text to the clipboard now includes an additional rich text clipboard format that preserves PowerGREP's syntax coloring and match highlighting when pasted into a rich text editor or word processor.
  • Preferences, Editor: Option to allow next/previous match commands to advance to the next/previous file.

Improvements:

  • Action: Changing the search type from "delimited" to "list" or back splits up or recomposes the delimited search terms.
  • Command line: When using the /silent parameter PowerGREP no longer adds the action to the undo history if the action is set to not create backup copies when overwriting files. Previously, all actions that create or overwrite files were added.
  • File Selector: Tooltip for folders now indicate the total size of the files in the folder in addition to the number of files in the folder.
  • Preferences, File Selector: The default permanent exclusion mask (on new PowerGREP installs) is now the regex \.bak\d*$;\.~[^.]*$;^Backup [0-9]+ of;^Working copy of which better matches the names of backup files created by PowerGREP. A file or folder simply called "backup" is no longer excluded by default.
  • Results, Export: Allow any encoding supported by PowerGREP to be chosen.
  • Results: Check memory usage while a file is being processed rather than only when PowerGREP is done with a file to prevent out of memory errors if a single file has more matches than PowerGREP can display.
  • Results: Display a detailed error message for out of memory exceptions (when PowerGREP really runs out of memory unexpectedly rather than hitting the memory usage limit set in the preferences).
  • Results: Pressing Enter when the cursor is over a file name or a match opens the file in the default editor, just like double-clicking does.
  • The keyboard shortcut for Redo was changed to Ctrl+Y to be more in line with other Windows applications; the old Ctrl+R keyboard shortcut still works.

New examples in the help file:

  • Extra processing on the whole target file rather than on individual search matches.
  • Split and merge log files by date.

Bug fixes:

  • Action: Executing a search-and-replace or search-and-delete action with the "collect/replace whole sections" option turned on failed with an access violation error. Preview and Quick Execute did work correctly.
  • Action: Search histories (black triangle above boxes for search terms) did not persist when closing and restarting PowerGREP.
  • Action: The "copy all searched files" target type caused the action to fail if no replacements were made in some of the searched files.
  • Action: The "copy modified files" and "copy all searched files" target types failed if a zipped document such as a DOCX or XLSX file was marked (green tick) directly in the File Selector.
  • Action: Using Quick Execute for "split files" actions or "collect files" actions using "path placeholders" for "target file creation" caused matches to be written without delimiters regardless of the "between collected text" setting if "order of collected matches" was set to "no particular order".
  • Archive: PowerGREP failed to open gzip archives that include the file name of the original file.
  • Editor: Next/Previous File did not move through the files in the order they have on the Results panel and did not skip files without matches when those aren't being shown on the Results panel.
  • File Selector: Files and folders tree did not adjust itself to the width of the File Selector panel when the file masks and time settings were hidden.
  • File Selector: The Path box ignored UNC paths with characters other than letters, digits, or dollar signs in the server or share name.
  • Results, Clear: Clearing the results did not clear the bottom area with errors or match details.
  • Results/Editor: F3 keyboard shortcuts for quick searches on the Results and Editor panels were not handled correctly or at all depending on which part of PowerGREP had keyboard focus.
  • Results: Replacements were not displayed for matches that spanned multiple lines or blocks of context when showing matches with context, in original order, separating match and replacement.

See also: PowerGREP 4.1.0 release notes

PowerGREP 4.0.6 – 23 March 2010

Bug fixes:

  • Action: Executing an action using the "list files" action type and the "save results into a single file" target type caused the action to fail with an access violation error after all files were found. PowerGREP failed to save the list of files into the target file.
  • Archives: Actions that searched through files in an archive and modified some of the files it searched through caused the files that were searched through but not modified to be damaged in the archive.
  • Creating a portable installation via the item in the Help menu did not copy over the required file 7z.dll.
  • File Selector: PowerGREP hung when expanding drives that do not support ReadDirectoryChangesW such as drives created by ExpanDrive.
  • Incremental search on the Results and Editor search bars did not properly reset its origin when moving the cursor.

See also: PowerGREP 4.0.6 release notes

PowerGREP 4.0.5 – 9 March 2010

Bug fixes:

  • Archives: PowerGREP did not search through archives that are inside folders inside other archives unless those folders inside those archives were previously expanded in the File Selector.
  • File Selector: Importing a file listing that included the root of a drive caused PowerGREP to lock up.
  • IFilter: The option "use IFilter to decode the compound document into plain text" (archive formats preferences) caused compound documents for which an IFilter is available to be treated as binary files by PowerGREP if the option "decode binary files using IFilter" (file formats preferences) was turned off. Now the option "decode binary files using IFilter" is ignored for compound documents.
  • IFilter: The second time PowerGREP checked whether an IFilter is available for a particular file type that doesn't have an IFilter an error "string list does not allow duplicates" occurred (4.0.4 only).

See also: PowerGREP 4.0.5 release notes

PowerGREP 3.5.8 – 9 March 2010

Bug fix:

  • Archives: PowerGREP did not search through archives that are inside folders inside other archives unless those folders inside those archives were previously expanded in the File Selector

PowerGREP 4.0.4 – 2 March 2010

Improvements:

  • Archives are now created after the grepping process for most actions so each archive is written at most once. This saves time and allows newly created 7-zip archives to be solid. It does increase memory and temporary file usage.
  • Literal line breaks in regular expressions (inserted by pressing Enter, as opposed to typing \r\n) now match a line break in any style (Windows, UNIX, or Mac) rather than only a Windows-style line break.

Bug fixes:

  • Action: Check All and Uncheck All items in the context menu of lists of search terms did not correctly select or deselect the search terms even though they correctly updated the checkboxes.
  • Action: Search-and-replace and search-and-delete actions did not skip files read through an IFilter. Such files should be skipped as the IFilter system is read-only.
  • Action: Search-and-replace using a (delimited) list of search terms with "non-overlapping search" turned off failed with an access violation if one of the search terms did not find any matches.
  • Editor, Save As: Saving a huge file under a new name correctly saved the file but corrupted PowerGREP's view of the file if parts of the file after the first insertion or deletion in the file were swapped out to disk when saving.
  • File masks with multiple adjacent spaces matched only a single space for each block of spaces in the file mask.
  • File Selector: Folder totals were not indicated after executing an action.
  • Preferences, Editor: Selecting a different text layout had no effect.
  • Preferences, Editor: The list of file navigation schemes wasn't properly cleared causing schemes to be listed repeatedly and triggering "index out of bounds" errors when selecting a duplicate.
  • Results: Double-clicking a (green) highlighted replacement opened the source file instead of the target file if a non-overlapping search caused the replacement to be made after another match was already replaced further down in the file.
  • Undo: If an action renamed a file adding or removing a .bz2 or .gz extension thus compressing or decompressing the file then undoing that action renamed the file back without undoing the compression or decompression.

See also: PowerGREP 4.0.4 release notes

PowerGREP 3.5.7 – 2 March 2010

Improvement:

  • Literal line breaks in regular expressions (inserted by pressing Enter, as opposed to typing \r\n) now match a line break in any style (Windows, UNIX, or Mac) rather than only a Windows-style line break.

Bug fix:

  • Editor, Save As: Saving a huge file under a new name correctly saved the file but corrupted PowerGREP's view of the file if parts of the file after the first insertion or deletion in the file were swapped out to disk when saving.

PowerGREP 4.0.3 – 18 February 2010

Bug fixes:

  • Action: Regular expressions in the form of (?:a|bb(?:cc))d failed to compile.
  • Action: The "nothing" choice for "between collected text" wasn't saved into PowerGREP Action files, causing it to revert to "line break" when loading the action.

PowerGREP 4.0.2 – 12 February 2010

Bug fixes:

  • Preferences, File Selector: Remembering the names of the File Selection and Action files last opened caused PowerGREP to crash at startup if it was closed with no .pga file loaded on the Action panel.
  • Sequence: Changing or deleting a step of which the results were still being shown on the Results or Editor panels caused PowerGREP to crash.

PowerGREP 3.5.6 – 12 February 2010

Improvements:

  • File Selector: Updating the list of included/excluded files when typing into the File Selector panel is no longer slowed down by folders containing lots of files, if those folders are collapsed.
  • Help|Upgrade Now allows you to purchase a major upgrade without having to look up your user ID.

Bug fixes:

  • Action: Using placeholders mixed with literal text with the search type set to literal text caused PowerGREP to mangle the literal text.
  • Conversion manager: Portable installations of PowerGREP defaulted the conversion cache folder to the Windows temp folder instead of a folder on the portable device.
  • File Selector: Turning off "same masks for all folders" did not disable the file mask controls when a folder that was not marked to be included in the search was selected, causing errors when changing file mask settings for such a folder.
  • Match placeholders: %MATCH% and %GROUP1% were replaced with nothing instead of the matched text when using file sectioning.
  • Preferences, Operation: The default backup type was not used when starting PowerGREP and the option to remember the last used action was turned off.
  • RegexBuddy: Right-clicking on the Section Search box to invoke RegexBuddy with "file sectioning" set to "search for sections" and the sectioning search type set to "list of regular expressions" caused an access violation error.
  • Undo Manager: Executing an action from the command line with the /quit parameter sometimes caused the undo manager to crash if the action only needed a very short time (seconds or less) to execute.
  • Windows 98/ME: PowerGREP Failed to save the state of its toolbars and panels.

PowerGREP 4.0.1 – 11 February 2010

Improvement:

  • Library: The sample library is now loaded automatically the first time you run PowerGREP 4.

Bug fixes:

  • Assistant: Popup hint for the "folders and files" tree also appeared in the Assistant if the tree was clicked on.
  • Beta version timeout of 1 March 2010 was not removed from the final release.
  • Forum: Clicking on a header in the list of conversations or messages before connecting to the forum caused a harmless access violation error.
  • Forum: F1 key did not show the forum reference.

PowerGREP 4.0.0 – 9 February 2010

PowerGREP 4 is a major upgrade and comes with a very long list of new features and improvements. Per our upgrade policy this major upgrade comes with an upgrade fee for anyone who purchased PowerGREP before 9 February 2009. The page for buying the upgrade lists the most important new features and enhancements. The version history you're looking at now shows everything that has changed.

New features:

  • Action Type: Delete search matches. Though this can be achieved with a search-and-replace with a blank replacement text, "delete search matches" is more convenient when using a delimited list of search terms, so there's no need to append a search pair delimiter to each search term.
  • Action Type: Merge files: Like a collect data action, but saves the entire file rather than just search matches. Can be used without a search text. Can be used with a replacement text to determine the target file.
  • Action Type: Quick Search: Like Display Search Matches, but with far fewer options to simplify the user interface
  • Action Type: Rename Files. Search and replace through file names rather than through file contents. Renaming files allows you to automatically zip or unzip files by renaming file.ext to archive.zip::file.ext or vice versa. By filtering files based on their contents using a regular expression with a named capturing group, you can use text from the file in the file's name by using a backreference to the named capturing group from the filter.
  • Action Type: Split Files: Works like a collect data action that always collects the entire search match (or the entire section if that option is used). Instead of the text to be collected, the "replacement text" is the path to the file where the match or section should be saved.
  • Action: Backup destination type "subfolder of original folder" that puts the backup file in a subfolder of the folder containing the file being overwritten.
  • Action: Collect data action type now has the option to only list files matching all search terms
  • Action: Collect data target type: path placeholders. This differs from the "save one file for each searched file" target type + "path placeholders" target destination combination in that the "path placeholders" target type can combine text collected from several files into a single file if the path placeholders resolve to the same target file for multiple source files, while "save one file for each searched file" would overwrite that file repeatedly, collecting only text from the last file searched.
  • Action: Collect data: Specify headers and footers to be collected for each input file and/or each output file; specify different text to be inserted between matches from the same file and matches from different files. These settings replace the "delimiter for collected items" setting, which is now "nothing", "line break", or "same text between all collected text" for the "between "collected text" setting.
  • Action: Copy and paste items under the downward pointing arrow button above the Search box to copy the entire search term or list of search terms, along with any replacement text.
  • Action: Delete duplicates option for the delete search matches action type to delete only the second and following matches of each search term, or te delete only duplicate matches (comparing the matched text). Matches that turn out not to be duplicates are shown in the results as being replaced with themselves.
  • Action: Display search matches action type now has the ability to create target files. Though this can be achieved with a "collect data" action with a blank text to be collected, "display search matches" is more convenient when using a delimited list of search terms, so there's no need to append a search pair delimiter to each search term.
  • Action: Filter files to halt processing on files that (don't) match one or more search terms or grab various parts of a file to use in the regular expression or replacement text via named capture.
  • Action: List Files now has an option to save a list of full paths, relative paths, or file names only into the target file.
  • Action: Lists: Check All and Uncheck All commands in the right-click menu for the checkboxes in lists of search terms.
  • Action: Lists: Cut, copy, and paste commands for search terms in a list of search terms to cut/copy/paste the label, search term, and replacement text (if any) all at once.
  • Action: Paste Escaped context menu item to paste the text on the clipboard with any regular expression metacharacters in it automatically escaped.
  • Archives: 7-zip (read and write)
  • Archives: ARJ (read only)
  • Archives: CAB files (Microsoft cabinet) (read only)
  • Archives: CD and DVD disk images using the ISO and UDF file systems (read only)
  • Archives: DEB packages (read only)
  • Archives: Files compressed with GZip (*.gz) and BZip2 (*.bz2) (read and write)
  • Archives: LHA and LZH (read only)
  • Archives: RAR (read only)
  • Archives: RPM packages (read only)
  • Archives: TAR files, including .tgz, .tar.gz and .tar.bz2 (read and write)
  • Archives: WIM files (Windows Imaging) (read only)
  • Assistant: Right-click on the assistant or use the General section in the Preferences to choose whether the assistant displays the hint for the control the mouse is pointing to or the control that has keyboard focus. When the mouse is over the assistant, it always displays the control that has keyboard focus.
  • Assistant: Right-click on the assistant to select a different font or font size. Can also be set in the General section in the Preferences.
  • Command line parameter to mark a single file for searching, so PowerGREP can be added to the right-click menu of files as well as folders.
  • Command line parameter to run PowerGREP silently.
  • Context: Context can be configured independently from file sectioning. E.g. when sections are very large, you can choose to show just one line of context for each match, instead of the whole section. To get PowerGREP 3's results, set the "context type" to "use sections for context".
  • Context: Context type that does not show any kind of context; speeds up the search and reduces memory consumption for searches with large numbers of matches. Use this option when you want to see matches in the results, but don't want to see any context information.
  • Context: Expand to whole lines option that displays lines with line numbers as context, regardless of the context or sectioning type.
  • Context: Fixed record length. This context type is particularly useful for binary files. Set the length to the number of bytes your hex editor displays on a single row to get the same view in the results in PowerGREP.
  • Context: Show extra context before and/or after the match. You can specify how many extra lines, sections, or context blocks depending on the context type and whether context is expanded to whole lines.
  • Editor: Code folding, manual and automatic based on indentation or file navigation scheme.
  • Editor: Make All Replacements and Revert All Replacements to process all replacements in the file at once.
  • Editor: Make and revert replacements by double-clicking on highlighted matches.
  • Editor: Next/Previous File buttons that jump to the next file with search results, using the sort order as used in the results.
  • Editor: Search toolbar for searching through the open file.
  • File Formats: *.kmz extension is now part of the default file mask for the "zipped documents" archive format. A .kmz file is a compressed .kml file used by applications such as Google Earth.
  • File Formats: CHM (read only archive format).
  • File Formats: Office 2007 files (.docx, .xlsx, .pptx, etc.) can now be processed as text instead of as XML by turning on the IFilter option for "zipped documents" in the Archive Formats preferences.
  • File Formats: Option to use IFilter to convert files in proprietary formats to text using the same method as the search functionality built into Windows.
  • File Formats: Text in PowerPoint (*.ppt) slides can now be searched through by using the IFilter.
  • File Formats: Unicode characters in MS Word documents can now be read correctly by turning on the IFilter option for *.doc files.
  • File Formats: When a proprietary format is configured to be decoded, you can now choose whether a file that fails conversion should be skipped or should be searched as binary data.
  • File Selector: Copy or move the selected files, files with matches, or files without matches to a different folder or .zip archive.
  • File Selector: Delete files.
  • File Selector: Exclude files with search results.
  • File Selector: Hovering the mouse pointer over a file displays additional information such as the file's size and last modification date.
  • File Selector: Import File List to get a list of files from arbitrary text files to include or exclude those files from the action. The import command can be saved as part of the file selection so it will be repeated each time the action is executed.
  • File Selector: Limit the search to files with a file size in a certain range.
  • File Selector: Network can now be marked to search all network servers listed in the File Selector. If no network servers are listed at all, PowerGREP will scan the network when executing the action.
  • File Selector: Network servers can now be marked to search all (visible) shares on the server.
  • File Selector: Show Folders menu item and button to show only folders in the File Selector, to make it easier to work with folders containing very large numbers of files. If Search Archives is on, archives are shown too, as PowerGREP treats those as compressed folders.
  • Forum
  • Library: Store file selections and sequences.
  • Library: Store search terms without a complete action. These can be added and used via the black drop-down arrow next to the Search labels on the Action panel.
  • Placeholders: %MATCHCOUNT%: Number of occurrences of each match when grouping identical matches.
  • Placeholders: Basic arithmetic on numeric placeholders; e.g. %MATCHNZ:*2+10% numbers matches 10, 12, 14, 16, etc. Also works on placeholders like %MATCH% that normally hold text rather than numbers, but only when their text can be converted into a number.
  • Placeholders: Date and time. Right-click on the Search box on the Action panel and select Match Placeholders for a list.
  • Placeholders: File size. Right-click on the Search box on the Action panel and select Match Placeholders for a list.
  • Placeholders: Insert match placeholders by picking them from a list and easily set padding, case, and arithmetic options.
  • Placeholders: Number of the match counted separately for each search term when the search type is a list. %MATCHTERMN%, %MATCHFILETERMN%, and %MATCHSECTIONTERMN% count matches for the overall action, per file, and per section separately for each search term. They correspond with %MATCHN%, %MATCHFILEN%, and %MATCHSECTIONN% which count matches for all search terms combined.
  • Preferences, Action: Configure the folder PowerGREP uses for temporary files, instead of the system temp folder. Set this to use a drive that's faster than the drive Windows is installed on, or to make sure not to leave any traces on that drive.
  • Preferences, Action: Option to use a separate search thread for each disk drive so all disks are searched at the same time, even if the number of disks exceeds the number of CPU cores.
  • Preferences, Action: Option to use a separate search thread for each network server so all servers are searched at the same time, even if the number of servers exceeds the number of CPU cores.
  • Preferences, Action: Specify how many search threads to use, up to the number of CPU cores in the PC.
  • Preferences, Editor: Backup option not to create backups.
  • Preferences, Editor: Fully configurable backup setting, including destination folders, etc.
  • Preferences, Editor: Option to make the Next/Previous Match/File buttons on the Editor panel select the same match or file on the Results panel.
  • Preferences, External Editors: %LINESTOP% and %COLSTOP% command line placeholders that indicate the end of the match.
  • Preferences, External Editors: (...) buttons to browse for an executable and a working folder.
  • Preferences, External Editors: Option to show Open All Files command for an external editor if all files in the results match the extensions supported by the editor.
  • Preferences, File Selector: Separate masks for files and for folders to exclude them from all actions.
  • Preferences, General: Add or remove the "Search with PowerGREP" items in the right-click menu for folders in Windows Explorer.
  • Preferences, General: Send To menu item for PowerGREP, allowing both files and folders to be marked for searching.
  • Preferences, Results: Highlight matches produced by different search terms in different colors (dubbed fountain colors).
  • Preferences: Paragraph symbols have been replaced with line break indicators that indicate the type of line break (CRLF, LF, etc.). They are also affected by syntax highlighting now.
  • Preferences: Text layout choices for the action, results and file editors: complex (bidirectional editing using Uniscribe), left to right (like PowerGREP 3), forced monospaced, and forced monospaced ideographs. Allow a proportionally spaced font to be selected in any case.
  • Results/Editor: Back and forward mouse buttons now move to the previous or next match in the results.
  • Results: Align matches with context display option that displays matches with context, and indents each line so all the matches line up vertically. Use this option in combination with sorting matches alphabetically to get a concordance display. The matches will only line up correctly when turning of word wrap and using a monospaced layout for the results (configurable in the preferences).
  • Results: Bookmark files or matches in the results.
  • Results: Delete selected files or files that were found to have or not to have matches during the last PowerGREP action.
  • Results: Fold menu items to fold or unfold the results of one file or all files.
  • Results: Group search matches per unique match, then per unique file (i.e. get a list of files per search match).
  • Results: Include file in or Exclude file from the next action.
  • Results: Locate in File Selector command to select the file the cursor points at in the File Selector.
  • Results: Make and revert replacements directly on the Results pane, without using the editor.
  • Results: Next/Previous File buttons for quickly jumping between files in the results.
  • Results: Next/Previous Match buttons, just like in the Editor, can be made visible on the toolbar via the small arrow at the right hand edge on the toolbar.m
  • Results: Pause button to temporarily pause an action. The results (so far) of paused actions can be inspected. Paused actions can then be resumed or aborted.
  • Results: Search toolbar for searching through the text of the results.
  • Results: Second and following lines of multi-line matches and context are now lined up with the first line when showing context numbers.
  • Results: Sort files in order searched through. PowerGREP 3 searched files in alphabetical order, so there was no need for an option to show the files in the order searched through, as the A..Z option already covered that. PowerGREP 4 searches through multiple drives and files concurrently, which causes files to be added to the results in a non-deterministic order. If you sort files in the order they are searched through, new search results are always added to the top or bottom. If you sort files alphabetically, new search results are mixed with old results to maintain alphabetic order, just as it happens when sorting files by number of matches or by last modification date.
  • Results: Target file names only display option. Only available for rename, collect data, and search-and-replace actions. Displays a list of target files that were created.
  • Right-to-left language support.
  • Sequence: Perform any number and any kind of PowerGREP actions in sequence. Each action can be restricted to files that matched, or did not match, in one of the previous actions.
  • Text Encoding: EUC-JP, EUC-KR, EUC-CN, EUC-TW.
  • Text Encoding: ISO 2022.
  • View: Save custom layouts.

Improvements:

  • Action: Lists: Ctrl+Click on the Add button to add a duplicate of the selected search term, instead of adding a blank search term.
  • Action: When changing the search type to a list, start with a list with the current regular expression rather than an empty list.
  • Archives: ZIP archives containing files larger than 4 GB (64-bit ZIP files).
  • Clicking on a panel's tab or caption bar now activates the first or main control on that panel.
  • Command line parameters for target, backup, and results options can now be specified as strings instead of integers.
  • Editor: Closing a file without saving and then opening again now shows the file without the changes to highlighting made to the unsaved Make and Revert Replacement commands.
  • Editor: Make Replacement and Revert Replacement now immediately update the match on the Results display.
  • Editor: Make Replacement and Revert Replacement now make/revert all replacements inside the selected text if there is a selection, rather than just the one under the cursor.
  • Editor: Undoing and redoing Make and Revert Replacement now also updates the highlighting as the commands themselves do.
  • Editor: When the editor needs to close a file because it will be overwritten by the action, the prompt now shows Pause and Abort buttons to pause or abort the action, instead of the Cancel button (which aborted the action). Save and Don't Save buttons are still available.
  • File Formats: Google Adwords Editor *.aea and *.aes extensions are now part of the default file mask for the "zipped documents" archive format
  • File Formats: The *.epub extension is now part of the default file mask for the "zipped documents" archive format.
  • File Selector: If no files or folders are marked in the tree of files and folders, but some files or folders are selected, automatically mark those files when executing the action instead of complaining that no files are marked. The files and folders that were marked automatically are also unmarked automatically when the action completes. This way you can easily select some files to search through them without having to use the system of marking and unmarking files and folders.
  • File Selector: Long lists of file extensions are now processed almost as fast as a single extension, resulting in a noticeable speed increase when globbing tens of thousands of files against a dozen or more extensions. The file extensions applied to each file aren't just the Include Files and Exclude Files settings in the File Selector, but also the file masks used in the Encoding, File Formats, and Archive Formats preferences.
  • File Selector: Path box should not try to resolve network paths until both the server and share name have been typed in, and should not repeatedly try to resolve shares that can't be found. This prevents unnecessary delays, as Windows takes a long time to determine that a network share does not exist.
  • File Selector: Select multiple files at once, so they can all be marked with one button click.
  • File Selector: Support Unicode file names.
  • File Selector: The *folder\* file mask syntax for selecting all files in a particular folder now also works with archives.
  • Results/Editor: Highlight the active line even when the edit boxes don't have keyboard focus.
  • Results: Attempting to write the same target file twice in a single action that does not combine targets is now be treated as an error instead of overwriting the file.
  • Results: Display the number of unique matches in each file for quick collect actions that group identical matches.
  • Results: Dynamic limit of the maximum number of matches that can be displayed, based on actual memory usage, rather than a fixed limit of 100,000 matches. The memory limit can be configured in the Results Preferences.
  • Results: Opening results in an external editor should select context or a line if that's what was clicked on in the results, similar to what happens when double-clicking the results to open the editor.
  • Results: Print selection checkbox in the print preview is now enabled if you select part of the results before clicking the Print button.
  • Results: When collecting data from files in proprietary formats with the option to collect one results file for each file searched through, append a .txt extension to the target file name. E.g. save somefile.pdf.txt instead of somefile.pdf so the user doesn't end up with a plain text file with a .pdf extension.
  • Stop PowerGREP from locking up when something goes wrong with a particular file by killing off unresponsive worker threads after one minute, and list the file that the thread locked up on among the errors on the Results panel.

See also: PowerGREP 4.0.0 release notes

PowerGREP 3.5.5 – 6 September 2009

This release fixes one bug that was present in PowerGREP 3.5.3 and 3.5.4. It caused PowerGREP to lock up when loading the undo history if the most recent item in the undo history listed a very large number of files. This could happen when starting PowerGREP, or after executing any action that modifies a large number of files.

PowerGREP 3.5.4 – 26 August 2009

Bug fixes:

  • Action: Searching for delimited literal text with the "whole words only" and/or "match whole section" options turned on sometimes found search matches that don't appear in the list of search terms (3.5.3 only).
  • Editor: Syntax coloring first appeared but then disappeared when viewing a file with highlighted matches that uses syntax coloring (3.5.3 only).
  • Results: Displaying file names without search matches but with totals now shows the number of groups if "group identical matches" was checked on the Action panel.

PowerGREP 3.5.3 – 17 August 2009

New feature:

  • RegexMagic integration: Invoke RegexMagic on the Action panel to generate regular expressions.

Improvements:

  • Action: Alt+S now moves keyboard focus to the main search box, if it is already visible. (If not, press Ctrl+F3 first.)
  • Directory change notifications no longer cause PowerGREP to check whether directories still exist, which could degrade a PC's performance if an application touches very large numbers of files while you have several PowerGREP instances open.

Bug fixes:

  • Action: PowerGREP 3 failed to open PowerGREP Action files saved with PowerGREP 2 with an access violation error if the file did not specify a valid folder to search through.
  • Action: Searching for delimited literal text with thousands of items with the "whole words only" and/or "match whole section" options turned on was orders of magnitude slower than searching for the exact same items with those two options turned off.
  • Action: The "whole words only" setting was used for all search types even though it is only visible for literal text search types.
  • Action: Using a list of regular expressions for the "search and collect sections" file sectioning type with a "section collect" text that is not a single backreference caused an access violation during execution instead of a descriptive error preventing execution.
  • Action: Using path placeholders such as %FILE% and %PATH% for target files did not work with .zip archives.
  • File Selector: Pasting in a path to a file or folder that exists but is permanently excluded in the File Selector Preferences caused PowerGREP to crash with an access violation.
  • File Selector/Results: Right-clicking on a file and selecting Edit, Explore Folder showed an error message instead of exploring the folder if the folder had a comma in its name.
  • GREP: The "single *.~*" backup naming style did not work, causing PowerGREP not to update any files.
  • Regex: Regexes that consisted solely of lookbehind statements failed with an access violation error.
  • Results: Displaying the results of a "display search matches" action showing matches with context and sorted alphabetically with the option to show matches and replacements on separate lines, an extraneous line without the search match was shown after each line with a search match.

PowerGREP 3.5.2 – 11 March 2009

Improvement:

  • File Selector: Turning "search archives" on or off now updates the tick marks in the files and folders tree immediately.

Bug fix:

  • PowerGREP 3.5.1 would hang trying to convert certain .doc files that previous versions handled just fine.

PowerGREP 3.5.1 – 5 January 2009

Improvements:

  • Action: If an item in a list of search terms has a label but no search text, use the label as the search text.
  • Action: Minimum size of the list control is now larger when using large fonts and large toolbar icons.
  • File Selector: If you type or paste a short path name such as c:\Progra~1\ into the Path field, it is now converted into a long path name. Previously, the short path name was added as a separate folder to the tree.
  • Portable installation: Lists of files previously opened files now survive changing drive letters.
  • Regex: The limit at which PowerGREP's regex engine aborts a match attempt because the regex is too complex (catastrophic backtracking) now adapts to the length of the match. Catastrophic backtracking detection previously aborted a regex like ^.*?(a+|d{7}) if the match to be found was very large (500,000 or more characters). This regex does do a serious amount of backtracking, because the lazy dot is followed by a complex group. However, all that backtracking is linear, not at all catastrophic.

Bug fixes:

  • Action: Lists of regular expressions in which the first regex started with a lookbehind did not work correctly. A regular expression such as (?<=ab)c|(?<=de)f would fail to match for the same reason.
  • Action: Search-and-replace actions using a list of free-spacing regular expressions failed to run with an access violation error.
  • Command line: Empty command line parameters (two double quotes with nothing between them) caused PowerGREP to display an access violation error.
  • Favorites: The names of second-level and deeper folders in the favorites were not displayed correctly in the Favorites menu.
  • Moving whole zip files in a find files action caused an access violation error after the first file was moved.
  • Placeholders: Alpha-counted placeholders such as %MATCHFILENA% started counting from B instead of from A. (If there are are more than 26 matches, match Z will be followed by BA, BB, BC, etc. If you want the first 26 matches to be AA to AZ instead of A to Z, use %MATCHFILENA:2A% instead to pad the count to a length of two letters.)
  • Placeholders: Lowercase alpha-counted placeholders such as %matchfilena% inserted uppercase letters instead of lowercase ones.
  • PowerGREP could not read certain PDF files created with version 8 of Adobe's PDF creation software.
  • Results: If a search-and-replace produced more than 100,000 search matches, and you didn't do a "Quick Replace", PowerGREP would crash with an access violation.
  • XLS files that are actually tab-delimited or comma-delimited plain text files caused a "File is not an Excel file" error in PowerGREP, even though Excel opens them fine. PowerGREP now first checks if an XLS file is plain text, before attempting to convert it.

PowerGREP 3.5.0 – 13 May 2008

Improvements:

  • Conversion manager: PowerGREP will now launch the conversion manager only when it's needed, rather than when starting PowerGREP.
  • File Formats: PowerGREP now sets the file date on files inside compound documents to the same date as the overall document file.
  • File Selector/Results: Keyboard mnemonics (underlined letters) for the default items in the Edit File submenu. You can assign mnemonics to your custom editors by placing an ampersand before the character you want to use as the mnemonic. E.g. "&My Editor" makes M the mnemonic.
  • Results, Export: When exporting to HTML, file references that are clickable in PowerGREP are now also clickable in the HTML output.
  • Results: Use base64Binary instead of hexBinary to save match data into .pgr files, resulting in a 33% size savings for match data.

Bug fixes:

  • Action: Searching for a list of thousands of search terms resulted in far greater memory usages than a search for a single regular expression that produces the same number of matches. Saving the results also resulted in excessively large .pgr files.
  • Action: Searching for delimited literal text with thousands of items is much slower than searching for the exact same items using the delimited regular expressions option.
  • Action: Selecting "Tab" as the delimiter between the search text and the replacement text caused PowerGREP to use the three letters "Tab" as the delimiter instead of a tab character.
  • Conversion manager: The conversion manager would stay in memory after the last PowerGREP instance was closed if PowerGREP had never searched through a file that needs conversion since it was first installed.
  • Editor, Print: Trying to print a file with highlighted matches caused an "invalid class typecast" error.
  • Editor: Opening a binary file while the editor was in text mode, or vice versa, caused an access violation error (3.4.2 only).
  • File Formats: PowerGREP did not always search through compound documents when the folder containing them was marked with "Include File or Folder" instead of "Include Folder and Subfolders". (PowerGREP did not automatically glob inside the compressed document if it was included by non-recursively marking its parent folder. If the document had been globbed previously, then it was searched.)
  • File Formats: Search-and-replace actions did not correctly treat compressed documents like Office 2007 and OpenOffice files as compound files to be copied and backed up as a whole. E.g. backup files were created for each file inside the DOCX file, and saved inside the DOCX, causing Office to report the file as corrupted. The whole DOCX file should be backed up instead.
  • File Formats: When doing a "find files" action without any search text and "search archives" turned on, PowerGREP would list all XML files inside Office 2007 and OpenOffice files rather than the DOCX or ODF file itself.
  • File Selector/Results: Right-clicking on a file inside a .zip archive now offers the option to explore the folder the .zip archive is in rather than the .zip archive itself (which doesn't work).
  • Results, Export: Exporting to HTML left the characters <, > and & in place after the HTML entity if these characters occurred at the start of a match.
  • Results: PowerGREP did not correctly grep regular expressions that contained only literal text and one or more \uFFFF code points above \u007F.
  • Results: When the option to automatically fold files was turned on in the preferences, and files were being sorted by totals or file date, the results would flicker. Each time the results were updated, they would be briefly shown unfolded, and then folded.

PowerGREP 3.4.2 – 18 January 2008

New features:

  • Action: Hexadecimal escapes like \xFF in the replacement text to insert non-printable characters.
  • Action: Unicode escapes \uFFFF and \x{FFFF} in the replacement text to insert characters that cannot be typed on the keyboard.
  • Command Line: Search through files found in a previously saved search with /markresults previousresults.pgr. This parameter has the same effect as the Mark Files with Results command in the File Selector menu.
  • Regex: Forward references (i.e. a backreference to a group defined after it) are now supported. E.g. (\2two|(one))+ will match oneonetwo instead of triggering an error.
  • Setup: Create Portable Installation directly from the self-extracting setup. The Install on Removable Drive menu item in the Help menu was renamed for consistency.

Improvements:

  • File Selector/Results: Right-clicking on an .xml file inside a .docx file now shows the option to open the .docx file in Word 2007.
  • Results: When you group matches per unique match and double-click on a match to see in which files it was found, the Edit button will now be enabled an open the file the cursor points to in the match details instead of being disabled.

Bug fixes:

  • Action: %SECTIONN% was numbered starting from zero instead of one.
  • Action: Extra processing that reinserted the extra processing search match into the replacement (e.g. by using $0) sometimes caused PowerGREP to skip extra processing matches.
  • Action: If you turned on the "invert results" checkbox for a find files action without using file sectioning, Action|Save did not save the invert results option into the .pga file.
  • Action: Pressing F1 while the Comments edit box had keyboard focus caused PowerGREP to crash.
  • Action: Starting a search with the "search type" set to "delimited regular expressions" but the actual search terms being all literal text caused an access violation.
  • File Formats: Numbers in Excel spreadsheets will now be formatted like they are in Excel rather than always with 2 decimals and thousand separators.
  • File Formats: PowerGREP will no longer lock up if it fails to convert an Excel file.
  • File Selector: When using regular expressions for file masks, the comma in a quantifier like {1,3} was seen as a delimiter between file masks.
  • Files saved by PowerGREP 3.4.0 and 3.4.1 indicated version 3.3 instead of 3.4 of the XML schema. This did not cause any problems in PowerGREP 3.4.0 and 3.4.1, but prevented PowerGREP 3.3.x from detecting it was opening files saved with a newer version.
  • Path Placeholders: Paths with initial folders subtracted like %PATH-2% were not recognized as placeholders.
  • Results: File headers were not shown if the display type was "file names only" and the totals option was anything except to show the totals with the file header (3.4.x only).
  • Results: Loading a .pgr file that had search matches in a .zip or .jar file that no longer exists sometimes caused an access violation error.
  • Vista: The Edit submenu when right-clicking on a file did not show the default application associated with the file.

PowerGREP 3.4.1 – 18 July 2007

Bug fixes:

  • Conversion Manager: If the file PowerGREP Conversion Cache.dat could not be found in the folder configured as PowerGREP's conversion cache, PowerGREP 3.4.0 would delete everything in that folder. PowerGREP 3.4.1 will leave the folder's contents alone.
  • Conversion Manager: The folder to use as the conversion cache was not properly initialized when running PowerGREP 3.4.0 for the first time, causing PowerGREP's installation folder to be used.
  • Conversion Manager: The combination of the above two conversion manager bugs caused PowerGREP to delete all files in its installation folder. Our apologies to anyone who lost data saved in PowerGREP's installation folder due to this unfortunate bug.
  • Conversion Manager: The conversion cache index was not properly read back when the conversion manager was started the next time, effectively causing the cache to be lost when all PowerGREP instances were closed. This bug also caused the conversion manager to use excessive amounts of memory in certain situations.
  • Conversion Manager: If the running cache size was set to zero, PowerGREP was unable to convert PDF files.
  • Core: Performing a search-and-replace using literal text (rather than binary data) through a binary file, caused the replacement to be inserted using two bytes per character instead of one byte (3.3.3 and 3.4.0 only).
  • Editor: Saving a file caused an access violation. This did not prevent the file from being saved, but did prevent the file and its backup from being added to the Undo History. (3.4.0 only).
  • Regex: ((?:abc)+) was optimized into (abc)+ which is not the same (the former captures all iterations; the latter only the last one) (3.4.0 only).
  • Regex: In free-spacing mode, PowerGREP did not allow whitespace between a quantifier and the ? or + that follows it to make the quantifier lazy or possessive.
  • Regex: In free-spacing mode, PowerGREP did not properly handle space between a token and quantifiers using the curly braces syntax.
  • Regex: Octal escapes inside character classes caused an access violation.

PowerGREP 3.4.0 – 25 June 2007

New features:

  • File Selector: Refresh command that refreshes the list of available drive letters, marks all folders as needing to be globbed again, and immediately updates all expanded folder tree nodes.
  • Preferences, Encoding: Option to detect encoding based on the HTML Content-Type meta tag.
  • Preferences, Encoding: Option to preserve the presence/absence of the BOM in Unicode files.
  • Preferences, File Formats: Extensions of files to be treated as zip archives (*.zip, *.jar, etc.) and files to be treated as zip documents (*.docx, *.xlsx, *.odf, etc.) can now be configured.
  • Preferences, File Formats: Option to configure the extensions of file masks that determine which conversion filter will be used for which files.
  • Preferences, File Formats: Option to disable specific conversion filters (PDF, Word, Excel).
  • Preferences, File Formats: Option to specify a folder where converted PDF, Word and Excel files should be cached, along with a maximum size of the cache. Using the cache speeds up searching through PDF, Word and Excel files that were previously searched through with PowerGREP. The cache is shared between all running instances of PowerGREP.
  • Regex: Character class subtraction, as supported by XML schema and the .NET framework.
  • Regex: Free-spacing regex search type and (?x:) free-spacing mode modifier.
  • Regex: POSIX character classes.
  • Regex: \Q..\E escape sequence for escaping a string of metacharacters.
  • Regex: \cA through \cZ ASCII control characters Ctrl+A through Ctrl+Z; equivalent of \x01 through \x1A; can be used inside and outside character classes.
  • Regex: \p{Arabic} through \p{Yi} tokens for matching any character in a particular Unicode script; \p{IsArabic} syntax also supported.
  • Regex: \p{InBasicLatin} through \p{InSpecials} tokens for matching any character in a particular Unicode block; \p{IsBasicLatin} and \p{BasicLatin} alternatives also supported; BasicLatin can also be written as Basic_Latin, Basic-Latin and Basic Latin.
  • Results: "Totals" option to show the number of matches per file and the clickable file header on one line. This halves the number of lines needed when not showing match details (e.g. after a "quick execute"), and leaves the total visible when collapsing file nodes.
  • Results: "Totals" option to show totals both at the top and the bottom.

Improvements:

  • Command line: More accurate and explanatory error messages when using invalid command line parameters.
  • EditPad: When PowerGREP is run from a removable drive, check if there's a copy of EditPad on the same drive, and use that.
  • File Formats: *.xlsx and *.pptx extensions are now also recognized as Office Open XML Files.
  • File sectioning: The "do not section; count lines" option should not count lines in files that are detected as binary, and behave like "do not section" for those files.
  • Preferences, File Selection: Changed the labels of the radio buttons for remembering the file selection and action to make their function more obvious; their actual function has not changed.
  • Regex: \xFF now matches the specified 8-bit value when searching through a file using an 8-bit encoding. When searching through other files, \xFF is equivalent to \u00FF like in previous versions (3.x.x).
  • RegexBuddy: When PowerGREP is run from a removable drive, check if there's a copy of RegexBuddy on the same drive, and use that.
  • RegexBuddy: When the search type is a list of regular expressions, send all of them to RegexBuddy, and retrieve all of them back from RegexBuddy. This requires RegexBuddy 3.
  • Results: If the results options are changed because an action that groups matches is run, reset the options when an action that does not group matches is run.
  • Undo History: Multi-select actions to undo/delete them all at once.

Bug fixes:

  • Action: Group placeholders like %GROUP1:40L% in the replacement text ignored the padding option.
  • Action: PowerGREP would sometimes complain about invalid backup options when the target type was set to not save anything (and thus no backups are needed).
  • Action: Target file destination type "folder tree" failed to create subfolders in the target folder (3.3.3 only).
  • File formats: PowerGREP would hang with 100% CPU usage when trying to decode certain Excel files.
  • Regex: Redesigned internal backtracking system, to support repeated backtracking of groups nested inside other groups.
  • Undo History: Undoing a "find files" action that moved files caused the moved files to be deleted instead of moved back to their previous locations. This fix will only work for actions executed with PowerGREP 3.4.0 or later. Previous versions of PowerGREP did not store the location of the original file in the Undo History.
  • Undo Manager: Changes to files in newly added undoable actions were not tracked right away.

Documentation additions:

  • Example: Padding and unpadding .CSV files.
  • Example: Replace reserved characters in XML files.

PowerGREP 3.3.3 – 19 April 2007

Improvements:

  • PowerGREP now closes much faster.
  • Preferences, File Selector: Permanent exclusion file masks can now contain backslashes. Such masks will be applied to the full path of the file, allowing certain folders or certain files in certain folders to be permanently excluded. E.g. *\duplicates\* will exclude everything inside all folders called "duplicates".
  • Prevent the computer from going to sleep if PowerGREP is still busy executing an action. Gracefully abort the action if the computer is forced to go to sleep (e.g. low battery on a laptop).

Bug fixes:

  • Action: No files would be found if the "action type" was "find files", "search type" was "list of literal text", "non-overlapping search" turned on, "list only files matching all items" turned on and "file sectioning" set to "do not section".
  • Action: Target file destination type "folder tree" failed to create target files for files inside .zip archives.
  • Action: The "folder tree" backup option did not work properly (3.3.x only).
  • File Formats: Password-protected Excel files caused a harmless access violation error to appear in the results. PowerGREP still skipped the file as it should, it just didn't show the correct message in the results.
  • File Selector: Changes in files in a drive's root folder were not automatically picked up when collapsing and re-expanding its node in the File Selector or starting the search.
  • Files with invalid date stamps (i.e. without a date stamp in Windows Explorer) would cause a date encoding error if PowerGREP had to modify the file, causing the action to fail.
  • PowerGREP would get stuck on an error message when you tried to close it when running PowerGREP from a write-protected removable device.
  • Preferences, Action & Results: The option to preserve file dates now also works for target files inside .zip archives.
  • Preferences, Encoding: When processing a Unicode file without a byte order marker, the target file sometimes used the default encoding rather than the auto-detected Unicode encoding of the source file.
  • Preferences, File Selector: Permanent exclusion file masks are now also applied to files inside .zip archives.
  • Searching through .zip files sometimes caused an unexpected access denied error.
  • Vista: Checkboxes and buttons in dialog boxes like the Preferences screen no longer disappear when you press the Alt key.
  • Vista: Folder context menus didn't show up in Vista.
  • Zip archives inside other .zip archives were recompressed after being searched through, even if the nested .zip archive wasn't modified.

PowerGREP 3.3.2 – 14 December 2006

Improvements:

  • Files with the .wpd extension are now also decoded as WordPerfect files, in addition to .wp, .wp4, .wp5 and .wp6 files.
  • Help|Install on Removable Drive: Option to force PowerGREP to treat any drive as a removable drive.
  • Regex: Regular expressions starting with a non-alternated caret are now applied much faster than in previous versions of PowerGREP.
  • Vista: Installing syntax coloring schemes now works properly under Windows Vista with User Account Control enabled.

Bug fixes:

  • Action: If the backup file naming style was set to "path placeholders" and the backup file location started with a path placeholder instead of a drive letter, PowerGREP would falsely complain the backup path is invalid.
  • If a file in a proprietary file format was searched through, then modified in another application, and searched through again during the same PowerGREP session, PowerGREP searched its old cached copy of the decoded file instead of the modified file.
  • Preferences, Encoding: Up and Down buttons did not work.
  • Regex: The upper limit on a lazy quantifier {m,n}? was not respected; e.g. a{1,3}b would match aaaaab entirely.
  • Windows won't shut down while PowerGREP is running (3.3.x only).

PowerGREP 3.3.1 – 6 September 2006

Improvements:

  • Command Line: Show an error message when unrecognized command line switches are used.

Bug fixes:

  • Files with .xls extensions that weren't Excel files at all caused PowerGREP to freeze. Now, such files will be flagged as not being Excel files and skipped.
  • Regex: A regex starting with a word boundary caused an access violation when attempted on an empty file. (Starting with version 3.3.0, PowerGREP no longer skips empty files when the "file sectioning" option is set to "do not section".)
  • Undo History: Actions that overwrote files without creating backups caused a harmless access violation until the undo manager updated the undo history (version 3.3.0 only).

PowerGREP 3.3.0 – 18 August 2006

New features:

  • Action: Import File command on the right-click menu of all text boxes, to easily load the contents of a file as the search term. Useful for quickly loading delimited lists.
  • Archives: .jar (Java Archive), .ear (Java Enterprise Application Packaging unit) and .war (Java web archive) archives can now be searched through when the Search through Archives option in the File Selector menu is enabled. These archives are essentially .zip archives with an extra META-INF folder with files containing meta information about the files in the archive. PowerGREP treats these archives as .zip archives, without any special treatment for the META-INF folder.
  • Command line: /resultsoptions parameter for the options on the Results pane.
  • File Formats: Microsoft Office Open XML (*.docx) and XML Paper Specification files can now be searched (and replaced) through. DOCX and XPS files are essentially ZIP archives containing several XML files. PowerGREP cannot decode DOCX and XPS files, but lets you search through the raw XML. PowerGREP can also make replacements in DOCX and XPS files, though you'll have to be careful not to mess up the XML structure.
  • File Formats: OpenDocument Format files can now be searched (and replaced) through. ODF files are essentially ZIP archives containing several XML files. PowerGREP cannot decode ODF files, but lets you search through the raw XML. PowerGREP can also make replacements in ODF files, though you'll have to be careful not to mess up the XML structure.
  • Placeholders: Placeholders to insert section and match numbers and the section and match text.
  • Preferences, Action & Results: Default backup options. New actions will default to these backup settings. The Editor will always use these settings.
  • Preferences, Action and Results: Option to collapse files by default when showing matches grouped per file
  • Preferences, Editor: Option to make an editor the default editor for the file types it supports. Pressing Ctrl+E will then open the files in that editor instead of opening them in PowerGREP.
  • Results: Option to sort files by their last modification dates.
  • Sectioning: "line by line (include line breaks)" sectioning type that includes the line break after each line in the section. This sectioning mode makes it easy to delete matching lines by running a search-and-replace that replaces whole sections with nothing.
  • Undo History: The built-in editor now creates backup copies, and adds them to the undo history for easy undoing or cleanup.

Improvements:

  • Action: History list for search terms now also indicate the replacement text. Previously, the history items did save and restore the replacement text, but did not indicate it in the menu.
  • Action: PowerGREP no longer skips empty files when the sectioning type is set to "whole file". It still skips them when sectioning files, since an empty file has no sections. A regular expression like \A or \z is useful to prepend or append something to the start or end of all files, while ^ and $ all by themselves are useful to prepend or append something to the start or end of all lines in all files. Such regular expressions will now insert the replacement text once in empty files in search-and-replace actions.
  • Action: PowerGREP now aborts instantly when the Abort button is clicked, even when searching through a huge file without any search matches.
  • Archives: PowerGREP will now search through archives stored inside other archives. Previously, archives inside archives were treated as binary files rather than archives.
  • Archives: PowerGREP's built-in editor can now edit and save files inside zip archives. Only files that were opened from an archive can be saved back into that archive under the same name. When saving a file under a new name, the file cannot be saved into an archive.
  • Install on Removable Drive: The undo history can now be copied over to the removable drive.
  • Preferences, Editor: %LINE% and %COL% can be used on the command line when sections are indicated with line numbers. The "do not section; count line numbers" and "line by line" sectioning types use line numbers as section numbers. The first line and column have line and column number one. For all other sectioning types, %LINE% and %COL% will be substituted with zero.
  • Preferences, Encoding: Option to detect UTF-8 as well as UTF-16 files without a byte order marker.
  • Preferences, Encoding: Option to make writing the Unicode byte order marker optional.
  • Regex: Individual linear expansion of greedy tokens such as .* now uses considerably less memory when dealing with very large regex matches (100,000+ characters). This improvement makes the regular expression engine expand .* faster but backtrack slower. The net result is a speed gain if the .* needs to backtrack less than half the number of characters it first matched.
  • Regex: Individual linear expansion of lazy tokens such as .*? no longer counts towards the "catastrophic backtracking" prevention. This allows regular expressions to use .*? and similar tokens to find matches longer than 500,000 characters. As a trade-off, it will take PowerGREP much longer to detect catastrophic backtracking due to improper use of .*? as happens when start.*?middle.?end is applied with "dot matches newlines" to a huge files containing many occurrences of "start" and "middle" but none of "end".
  • Reopen menus and path history now show longer path names.
  • Results: If the action was aborted due to the catastrophic backtracking warning, the error message now indicates the file on which the error occurred. It is possible for a regular expression to show exponential behavior on only some files. Usually, these are files in which the regular expression matches partially at certain positions, but cannot find a complete match.
  • Results: Opening all files with results in EditPad Pro now automatically makes EditPad Pro select the first search match in each file.
  • Undo History: Detect the status of backup files in the background, instead of when starting PowerGREP and when switching from another application to PowerGREP.
  • Undo History: If the undo history references files on drives or network shares that are unavailable, mark those files as "drive not available" rather than as being deleted.

Bug fixes:

  • Action: Clicking Replace (as opposed to Quick Replace) for a search-and-replace action with a list of regular expressions and non-overlapping search turned on and file sectioning turned on caused PowerGREP to use and leak an unreasonable amount of memory. Memory usage is now a lot more reasonable in this situation (similar to when file sectioning is off), and memory will be released when you select Results|Clear in the menu.
  • Action: The action fails with an access violation if the backup file location is not a complete path when the backup destination type is "single folder". Now PowerGREP will show a proper message and will refuse to run the action.
  • File Selector: Typing extraneous trailing spaces into the Path field no longer causes empty nodes to be added to the folder tree.
  • File Selector: When the modification date option was set to "(not) modified during the past X hours/days/etc", the number of hours/days/etc was not saved.
  • Placeholders: When searching for a regular expression, placeholders in the text to be collected or the replacement text were not recognized unless they appeared at the start or after a \, $ or backreference.
  • Regex: If the regular expression started with a literal character repeated a fixed number of times with the {n} operator, followed by another literal character, RegexBuddy incorrectly expanded the quantifier when applying the "literal start" optimization. E.g. a{2}b would fail to match aab while \w{2}b, a{2}\w and a{2,3}b all matched properly.
  • Regex: Negative lookaround containing nothing except one of the anchors ^, $, \A, \z or \Z would match at any position, while it should fail at positions where the anchor matches.
  • Regex: PowerGREP did not backtrack repeated atomic groups. E.g. (?>[ab])+b did not match aab. PowerGREP incorrectly treated (?>group)+ as (group)++. In (?>group)+ the regex won't backtrack into the group, but will backtrack +. In (group)++ neither the group nor the + are backtracked. The equivalent of (group)++ using atomic grouping notation is (?>(group)+).
  • Regex: Zero-width match bump-along also needs to happen if a zero-width match if found at the position where the previous match ended.
  • Results: Search-and-replace and collect actions resulting in individual replacements larger than 64K were not handled properly, either resulting in truncated replacements or an access violation.
  • Results|Print, Edit|Print: Trying to print long results or certain files got PowerGREP stuck on a "list index out of bounds" error.
  • Undo History: If PowerGREP wasn't able to save the undo history due to it having remembered a now invalid path, PowerGREP would throw error messages without giving the opportunity to select another undo history file.

New examples in the help file and manual:

  • Capitalize the first letter of each word.
  • Collect a numbered list.
  • Collect paragraphs, where a paragraph is a block of lines delimited by one or more blank lines.
  • Find files NOT containing a search term.
  • Insert line numbers into the file.
  • Padding replacements.
  • Search through the printable content in Word .docx, XML Paper Specification and OpenDocument Format files.

PowerGREP 3.2.2 – 24 February 2006

Bug fixes:

  • Action: A collect data action saving the results into a single target file would fail to save the target file, triggering an access violoation error at the end of the search (version 3.2.1 only).
  • Scroll bars did not appear on the File Selector and Action panes when they were made too small to show all their contents (version 3.2.1 only).
  • Regex: Conditionals without an "else" alternative would fail if the conditional test failed. Since an empty regex always matches, the conditional should match if the "else" part is omitted or empty.
  • Regex: Groups with an empty alternative at the end were not made optional, i.e. (a|b|) was treated as (a|b) instead of (a|b)?
  • Sectioning: If the sectioning type was set to "search and collect sections", and "section collect" was set to a backreference to a non-existing capturing group, an access violation would occur.
  • Undo History: Actions that created some files and overwrote others were marked as partially undoable instead of not undoable at all if all the created files and all the backup copies of the modified files were deleted.

PowerGREP 3.2.1 – 31 January 2006

New features:

  • Help|Install on Removable Drive

Improvements:

  • Action: "Copy/move/delete matching files" target types for "find files" actions now also work on files inside .zip archives.
  • Action: Drop-down lists for delimiters, target location and backup location now show a history of recently used delimiters and target/backup locations.
  • Action: The option "list only sections matching all items" no longer requires the "collect/replace whole sections" option to be turned on for "search-and-replace" actions.
  • File Selector: Network drives that are mapped to a drive letter are now indicated with the mapped UNC path rather than the mapped drive's volume label. This change is purely cosmetic.
  • Results: Don't display matches with fewer than the "minimum number of occurrences" specified in the action when automatically updating the results during the search (i.e. when it is not yet known if a match will reach the minimum number in the end or not).
  • Undo History: If trying to open another undo history file fails, the error message now offers an option to revert to the previous undo history in addition to picking another history or retrying.

Bug fixes:

  • Action: In a search-and-replace action using a list of search terms, with file sectioning enabled (not set to "whole file"), with non-overlapping search disabled, an access violation error occurred if two search terms matched in the same section.
  • Action: In a search-and-replace action, with file sectioning enabled (not set to "whole file"), if the last match to be replaced was at the very end of the file, the last match's text would be copied into the target file after the last match's replacement.
  • Action: Loading a search-and-replace action using a list of binary data from a .pga file or library failed with an access violation.
  • Action: Search-and-replace actions with both "replace whole sections" and "list only sections matching all items" turned on in the file sectioning did not work properly.
  • Collect: Editing the file with the collected data messed up the highlighting of the collected matches in the editor.
  • Command line: When two files are specified right next to each other, PowerGREP concatenated the file names instead of opening both files.
  • Editor: On a few computers, PowerGREP would lock up when opening a file larger than 64K in the editor by double-clicking on a result in the Results pane.
  • Opening a .pga PowerGREP action file or a .pgf PowerGREP file selection file saved with PowerGREP 2 caused PowerGREP 3 to keep a lock on the file until you closed PowerGREP 3, making it impossible to overwrite the file.
  • Regex: If a single token was repeated and also made optional in a group all by itself, e.g. (a{3})?, PowerGREP incorrectly optimized the token as a{0,3}.
  • Regex: Initial lookbehind optimization caused regexes with a capturing group inside the initial lookbehind to fail if the capturing group was referenced later in the regular expression.
  • Regex: Octal escapes like \037 were not handled properly
  • Regex: PowerGREP's regular expression optimizer incorrectly made greedy tokens followed by lookbehind possessive, if the characters matched by the token and the lookbehind are mutually exclusive.
  • Results: Closing the Results pane after floating it no longer causes PowerGREP to crash (3.2.0 only)
  • Results: If the Automatic Update item in the Results menu was activated, PowerGREP would not list all skipped binary files if the action did not produce any other errors. Binary files are skipped when the Search Binary Files item in the File Selector menu is disabled. Skipped binary files are indicated in the results if that option is checked on the Action & Results tab in the Preferences.
  • Results: When saving search results that contained error messages into a .pgr file using Results|Save, PowerGREP would incorrectly claim the .pgr file is invalid when opening it with Results|Open.
  • Undo History: File names with ampersands and angle brackets in them were incorrectly saved into the undo history, causing PowerGREP to report an error the next time it tried to open the undo history.

PowerGREP 3.2.0 – 3 October 2005

New features:

  • Preferences, File Selection: Option to disable auto-detecting network servers and shares when expanding the Network node in the File Selector. When disabled, network shares can be searched by typing in their UNC paths. If your PC is connected to a large network, you can disable this option if you don't want a long list of network servers to clutter the File Selector.
  • Preferences, File Selection: Option to remember the File Selection and Action files that were in use, as an alternative to remember the file selection and action ("search terms") themselves. That option was moved from the Appearance tab to the new File Selector tab.
  • Windows Explorer context menu for folders now has an additional "search subfolders with PowerGREP" item to start PowerGREP with the folder marked with a double tick.

Improvements:

  • File Selector: Expanding a folder containing thousands of files that were already searched through no longer incurs a noticeable delay. The File Selector will overall feel a lot snappier now.
  • File Selector: Indicate volume labels next to drive letters.
  • Results: When activating the Results pane when results are listed, the edit box with the results instead of the Display drop-down list will now have keyboard focus. This makes it easy to keep track of where you were in the results.
  • Results: When choosing a display option that doesn't work in combination with other options (e.g. show context while grouping matches), automatically change the other options to make the selected option possible.
  • Results: When choosing a display option that is not possible (e.g. showing context when none was saved), show an explanation in the PowerGREP Assistant.
  • Regex: Empty alternatives in the main regex are now treated as an error. They will always find a zero-width match, effectively truncating the regular expression at that point. This is usually a typing error rather than the user's intention.
  • Windows Explorer context menu item "search with PowerGREP" now keeps the file masks and date settings in the File Selector when the option to remember search terms between sessions is on. Any remembered file and folder markings are cleared.

Bug fixes:

  • Action: Extra processing (any kind) caused an access violation if the main search-and-replace used literal text.
  • Action: Extra processing and file sectioning search terms were added to the history of the main action, rather than the extra processing and file sectioning histories. Histories can be accessed by clicking the black downward pointing triangle next to the Search labels in the main part of the action, the extra processing part and the file sectioning part.
  • Action: Extra processing using a regular expression that matches the extra processing replacement text caused PowerGREP to get stuck in an infinite loop.
  • Action: Extra processing with the extra processing replacement left blank and the extra processing search type set to regular expression, caused an access violation.
  • Action: Repeating a find files action twice after deleting a previously found file would, under some circumstances, list the deleted file among the results again.
  • Action: If the search type was a (delimited) list of regular expressions, and one of the regexes had more opening than closing brackets when clicking the Preview or Execute button, the error message would reappear each time, even after correcting the regex.
  • Action: The "search" box was not properly positioned when the search type was a list, on systems using large fonts.
  • Action: When the option to preserve search terms was off, and PowerGREP was closed with the search type set to "search and replace" or "collect data", the Execute and Quick Execute buttons would incorrectly preserve the "Replace" or "Collect" label the next time PowerGREP was started, until the search type was changed. This issue was purely cosmetic.
  • File Selector: Expanding the Network node caused PowerGREP to become unresponsive on systems running Windows XP SP2 with the Windows firewall enabled, if the network was very large.
  • File Selector: Loading a file selection with an invisible default network share marked (e.g. \\server\c$), would incorrectly show the share with a recycle bin icon indicating it doesn't exist.
  • Regex: (?:a|b|c)|d|e was optimized into a|d|e|b|c instead of a|b|c|d|e which would cause the wrong alternative to match if more than one could be matched at the same position
  • Regex: A group with an empty alternative such as (|a|b) caused an access violation
  • Docking 2 panes together did not preserve their relative sizes when restarting PowerGREP.
  • If PowerGREP was previously used on the second monitor, and is then run again with only one monitor available, PowerGREP will be displayed entirely off-screen.
  • When saving a file selection with a folder recursively marked, and a subfolder of it excluded, the exclusion mark is not saved into the file selection (version 3.1.0 only).
  • Copying and pasting from PowerGREP into another application did not work on Windows 95, 98 and ME (versions 3.x.x only).

More documentation:

  • Example: Find two or more words on the same line.
  • Example: Find two words separated by a certain number (min, max) of other words.

PowerGREP 3.1.0 – 16 July 2005

New features:

  • Action: Before searching a file, PowerGREP will now check if it starts with an XML declaration. If so, it will use the encoding indicated by the XML declaration. The XML header check can be disabled on the Text Encoding page in the Preferences.
  • File Selector and Results: The submenu of Edit File now has an item to explore the folder containing the file. If a folder is selected, Edit File explores the folder.
  • File Selector: Clear Folder and its Files and Subfolders: Clear the markings of the selected folder, and all files and subfolders in that folder.
  • File Selector: Replaced the "Use Files with Search Results" item with "Mark Files with Search Results" and Search Only through Files with Results".
    The "mark" option works like the old "use" option. It clears the file selection, and then marks the files that have search results.
    The "only" option does not change the file selection, but restricts the search to files that are both marked in the file selector and listed in the results.
  • Sectioning: Option to match only sections in which all search terms from the main part of the action can be matched.

Improvements:

  • Action: Search terms can now be labeled when the search type is a list
  • Action: The Execute and Quick Execute buttons on the Action toolbar now change their label to indicate what will happen, depending on the action type and target type settings.
    "Search" indicates a safe action that will not modify any files. "Collect", "Replace", "Move Files", "Copy Files" and "Delete Files" all indicate actions that will create and/or overwrite files.
  • Action: The option to show only files in which all search terms can be found is now also available when the action type is "display search matches"
  • File Selector: The "Open File in EditPad" menu item is now also enabled for folders, causing EditPad Pro to ask you if you want to open all files in the folder, or only files of a certain kind.
  • File Selector: The list of network servers is now built in the background, so there's no long wait when expanding the Network node

Bug fixes:

  • Action: A "find files" action without a search text and with the option to search archives turned off would list archive files that were modified outside the date range specified in the File Selector.
    When the option to search archives is off, "find files" actions without a search text treat .zip files as regular files rather than as compressed folders. All other actions skip .zip files when the option to search archives is off.
  • Action: Executing (not previewing) a "display search matches" action after executing a "collect data" or "find files" action with the "target file creation" option set to "single file" caused an access violation.
  • Action: If the search type was set to a list (e.g. "list of regular expressions") and only one item was added to the list, PowerGREP would refuse to run the action, incorrectly stating that the search text was left blank.
  • Action: Search-and-replace actions with the replacement text left blank and the file sectioning set to anything except "whole file" caused an access violation error.
  • Action: When encountering a password-portected Excel file, PowerGREP would pop up an error and abort the search instead of continuing the search, skipping the file and listing the error in the results.
  • Docking 2 panes together in a single tab made it impossible to activate either using the View menu.
  • File Selector: If the File Selector remembered markings for files on a removable drive that was disconnected, clearing the file selection caused an error.
  • File Selector: Opening a file selection or action file with files or folders on the network marked in the file selection or action file caused an error.
  • File Selector: When starting a search with some files or folders excluded, but none marked for inclusion, PowerGREP did not show the error that no files are marked for inclusion.
  • Files encoded in UTF-8 that contain non-ASCII characters were not handled properly by regular expression constructs that search backwards such as the caret and lookbehind.
  • Files encoded with code pages 932 (Japanese), 936 (simplified Chinese), 949 (Korean) or 950 (traditional Chinese) were not properly processed when searching or editing.
  • Find files: Executing a find files action with the target type set to copy or move files, and the option to search archives OFF, caused the action to be aborted with an "invalid typecast" error.
  • Regex: Alternation inside capturing groups did not always work properly, e.g. Z([ui]|ue)rich did not match Zuerich. This problem did not occur with non-capturing groups, e.g. Z(?:[ui]|ue)rich worked properly.
  • Regex: Due to an over-optimization, (a?) was treated like (a)? where "a" is a single regex token. The difference is that if "a" cannot be matched, \1 will successfully match (nothing) in the first case, but fail to match in the second case.
  • Results: Right-clicking on the bottom part of the results pane with error messages or match details and selecting the "copy" or "select all" items, copied or selected the text in the main results rather than the errors/details part.
  • Sectioning: When splitting files along delimiters, PowerGREP did not search the part of each file between the last delimiter in the file and the very end of the file.
  • Undo History: The prompt to select a new undo history file when the active undo history file cannot be read did not work.

New Examples:

  • Extract or delete lines matching one or more strings or regular expressions.
  • Save search matches into a CSV file.

PowerGREP 3.0.4 – 18 May 2005

Bug fixes:

  • Action: History items persisted but became inoperative after restarting PowerGREP.
  • Action: Previewing or executing a "collect data" action with the search type set to "regular expression", and some literal text entered as the search term, and a backreference used in the replacement text, would cause an access violation. Note that when searching for literal text with the search type set to "regular expression", using backreferences is pointless since there are no capturing groups.
  • Action: Search through files that another application is writing to, such as log files (was possible in PowerGREP 2.x).
  • Edit File submenu in the File Selector and Results menus did not show the Open item with the application associated with the file type if the file association lacked quotes around the path to the application, if that path contained spaces (e.g. "C:\Program Files\app.exe").
  • Editor: Intermittent access violations occurred when scrolling through files when the option to show line numbers was on.
  • File Selector: (Windows NT, 2000, XP and 2003 only) Under certain circumstances, PowerGREP would stop processing directory change notifications, causing both the File Selector and the actual grep operation to ignore new files until PowerGREP was restarted.
  • File Selector: Marking a folder without its subfolders, without expanding the folder in the File Selector, and then running the search, then expanding the folder in the File Selector, did not show the folder's subfolders.
  • File Selector: Typing in a UNC path now properly adds the server and share to the network node in the files and folders tree, even if the server is not on the same domain or workgroup as the local computer.
  • Preferences, Operation: PowerGREP did not refresh its list of files and folders in the File Selector after changing the list of files to be excluded from all actions in the Preferences, effectively requiring a restart for the change to take effect.

PowerGREP 3.0.3 – 26 April 2005

New features:

  • Histories for search terms, extra processing and file sectioning on the Action pane, and the path and file masks in the File Selector.

Improvements:

  • Command line: Relative paths and file:// URLs are now supported.
  • Command line: The second value for /save to indicate the encoding to save the results with is now optional.
  • File Selector: Folder and file information is now cached, noticeably increasing the speed of the File Selector, and eliminating the globbing phase for the second and following action executed on the same file selection. (Windows NT, 2000, XP and 2003 only)
  • File Selector: Files and folders with the "system" attribute set were always invisible. Now, they will be visible when the option to search through hidden files is on in the Operation Preferences.
  • File Selector: When typing a path into the Path field, the files and folders tree is now automatically expanded. Press Arrow Up and Arrow Down to navigate through the tree while keeping keyboard focus on the Path field.

Bug fixes:

  • Conversion cache for MS Word, Excel and PDF files did not keep the cached copies in certain circumstances.
  • PowerGREP did not remember its layout when one or more panes were made to float (e.g. by selecting the dual monitor layout in the View menu).

PowerGREP 3.0.2 – 16 April 2005

Improvements:

  • Action: Search-and-replace actions that make large numbers of replacements are now executed much faster compared with PowerGREP 3.0.x. Remember to use Quick Execute to execute such actions for maximum speed.
  • File Selector: Browsing files and folders on a network share should be slightly faster now
  • File Selector: When typing in a UNC path in the Path field, make the network share visible in the File Selector as long as it exists, even if the network server cannot be browsed
  • Results: Printing the results now prints the action definition before the results, like PowerGREP 1 and 2 do.
  • Results: When certain files were skipped because they are binary, inform that binary files can be search through by turning on the option "search binary files" in the File Selector menu.

Version 3.0.x bugs fixed:

  • Action: Keyboard shortcuts Ctrl+Z/X/C/V/A did not work for drop-down lists
  • Action: Search-and-replace actions using a list of three or more search-and-replace pairs with the non-overlapping search option turned off would fail with a "file in use" error and leave the temporary files behind.
  • Action Search-and-replace on Unicode files starting with a byte order marker resulted in target files with two byte order markers, and all replacements inserted two or three bytes shifted from the correct position.
  • Action: Unicode files were sometimes incorrectly flagged as binary files.
  • Dragging a docked or tabbed pane to the top of the screen to make it float no longer makes the caption bar of the floating pane invisible
  • Zip files: Trying to search through .zip files compressed with WinZip's new "enhanced compression" resulted in an popup error message for each file in the .zip. Now, PowerGREP will list the errors in the results without interruption.

PowerGREP 3.0.1 – 8 April 2005

PowerGREP 3.0 is a major upgrade. This version introduces many new features and significant enhancements, along with a completely redesigned interface. Migrating from PowerGREP 2.x to 3.0 will take a bit of getting used to. The PowerGREP 3.0 migration guide explains the most important differences.

Once you've made the move from PowerGREP 2.x to 3.0, you will find this new version a far superior and more capable tool. When it comes to power and flexibility, PowerGREP 3.0 stands head and shoulders above all other Windows grep tools.

That doesn't make PowerGREP 3.0 more difficult to use than previous version. Quite to the contrary, in fact. When you take advantage of the new file sectioning and extra processing features, you'll often be able to use much simpler regular expressions in PowerGREP 3.0 than in previous versions of PowerGREP (or any other grep tool, for that matter).

All-new file selector:

  • File selector is now a pane in the main window, rather than a pop up.
  • Include and exclude individual files, folders and archives on your PC or network.
  • Use different inclusion and exclusion file masks for each folder.
  • Indicates which files contain search matches, and enables subsequent actions to be limited to those files.
  • Limit the search for a date/time range of the modification date of a file.

Actions with more power and flexibility:

  • Search through files larger than 2 GB. New limit is 9 EB or 9 billion GB (2^63 bytes).
  • Search through Excel files (*.xls).
  • Multiple search terms or search-and-replace pairs: paste in an arbitrary set of search term, regexes or replacement pairs, with custom delimiters. Search for all items concurrently (non-overlapping search) or sequentially.
  • Sequence action was removed. All action types can now work with multiple regular expressions. You can enter sequence steps individually (like in the past), or all together in one edit box with custom delimiters.
  • Extra processing: Search and replace through the replacement text or the text to be collected after each search match.
  • Sections: Define sections or split boundaries to restrict search matches to certain sections, and/or to collect the context of search matches.
  • Move, copy or delete the files that are found during a "find files" action.
  • Invert Results: List files, lines or sections NOT matching the search text.
  • Collect search matches into target files, with one target file for the whole action, or individual target files for each source file.
  • Path placeholders can now be used in the search text or regular expression, in addition to the replacement text.
  • Easy way to insert path placeholders, without having to remember the actual tokens.
  • Comments in PowerGREP actions explaining what the action is all about.
  • Executing a PowerGREP action now takes place entirely in the background. PowerGREP's user interface remains fully responsive during the search, enabling you to fully inspect the results gathered so far while the operation continues.

Improved regular expression engine:

  • Unicode regex tokens \p{property}, \P{property}, \uFFFF and \X are now supported.
  • MBCS (multi-byte character set): PowerGREP's regular expression engine now treats multi-byte characters as single characters, making PowerGREP usable with languages such as Japanese, Chinese and Korean, whether working with Unicode files or not.
  • Multiple named capturing groups can now have the same name.
  • PowerGREP will no longer crash in case of "catastrophic backtracking" caused by a regular expression that is too complex. When PowerGREP detects catastrophic backtracking, it will abort the action and show an error message.

More informative results:

  • Results: Show/hide match context, group/ungroup and sort search matches in the results, without performing the search again.
  • Results: When results are grouped per file, the files and their results can now be collapsed like folders in a tree view.

All-new built-in file editor:

  • Basic text & hex editor with highlighted search matches
  • Step through search matches.
  • Make/undo individual replacements after previewing or executing a search-and-replace.
  • Print file or selected block with search matches highlighted.

All-new PowerGREP library:

  • Save multiple PowerGREP actions into a single file, for easy access and reuse.
  • Instantly search the captions and descriptions of all actions in a library.
  • Example actions are now included with PowerGREP as a PowerGREP library, including a significant number of brand new examples.

More configuration options:

  • Option to give target files the same file date as the original files when doing a search and replace.
  • Option to list file names in the results as relative to the search path instead of with absolute paths.
  • Option to make PowerGREP start with the last file selection and action, or to start with a blank action and file selection.
  • Option to specify default character encodings for files matching specific file masks, and the option to turn off automatic detection of Unicode files.

Other improvements:

  • Caption shows the file name of the last opened/saved file selection, action, results, library, sequence and editor file.
  • Double-clicking on a regular expression selects the entire regex token that was clicked on, rather than the entire word. (e.g. \bword\b highlights \b or word, rather than bword)
  • File types: Known backup extensions are ignored when determining the file type. E.g. myfile.html.bak should be treated as a .html file (unless a .bak file type has been defined).
  • The text version of decoded proprietary file formats (i.e. PDF and Word documents) is now saved during a PowerGREP session. When you search through the same file more than once, it will need to be decoded only once, speeding up the search.
  • Treat \t, \r and \n as regex tokens in the replacement text, when using regular expressions.
  • Unicode files: When PowerGREP encounters NULL characters in a file, it now first tries to determine if the file is a Unicode file without a byte order marker, before deciding the file is a binary file.
  • XML-based file formats for all files saved by PowerGREP.